Post on 03-Jul-2015
IEEE 1588 Timing for Mobile Backhaul
A Light Reading Webinar Sponsored by
R
Robert Synnestvedt, Cisco
The World is on the M.O.VE. By 2015…
There will be 5B mobile devices and
1.5B M2M nodes
Video will be 66% of all mobile traffic
Global mobile traffic will grow 26X to 6.3 EB/mo
Source: Cisco Visual Networking Index (VNI) Global Mobile Data Forecast, 2010–2015
www.cisco.com/go/vni
Cost & Capacity Advantage of Ethernet
$37,044
$6,887
14 Mbps
17 Mbps
19 Mbps
22 Mbps 23 Mbps
24 Mbps 28 Mbps 35 Mbps 42 Mbps 49 Mbps
$0
$10,000
$20,000
$30,000
$40,000
CY09 CY10 CY11 CY12 CY13
Move to IP/ Ethernet
Stay on TDM TDM Costs
Escalate Directly with Bandwidth
Ethernet Costs Less per Bit, Flat Cost Structure
Backhaul Charges per Connection TDM IP/Ethernet
Internet Capacity Transformation
Web2.0 ’04
IP NGN
W3C ‘94
CSCO ‘84
4G=IP
4G=IP
Regional Demand by Volume & Technology
5
Unified Insight • Backhaul networks must
make rapid evolution to Ethernet/IP in order handle traffic loads, and cut operational costs
SP Content
Traditional Mobile Architecture Linear transport for linear Subscriber Growth
Core
RAN
Basic WAP Content
Business
CG
v6
Car
rier G
rade
IPv6
Cloud
Network
Client
SP Content Third-Party
Content
National Data Center/ Cloud/VHO
National Data Center/ Cloud/VHO
Regional Data
Center/VSO
Regional Data
Center/VSO
Mobile Internet Architecture Distributed to Scale with non-linear M.O.VE Demands
IP Core
EPC/Edge
Unified RAN
Nir Halachmi, Telco Systems
TDM migration needs
• TDM technology imposes heavy OPEX and CAPEX issues on the mobile operators
• TDM bandwidth scaling results linear escalated costs
• TDM equipment is getting obsolete, as long as the people expertise in the technology
TDM migration path
Carrier Ethernet Network
Legacy Network
Non-Ethernet
I/F
UNI Non-Ethernet
I/F
UNI GIWF RAN BS
RAN NC
GIWF
Carrier Ethernet Network Non-
Ethernet I/F
UNI Non-Ethernet
I/F
UNI GIWF RAN BS
RAN NC
GIWF
• Move from dual backbone network into a converged packet based network
Migration challenge – time synchronization
• Migrating the backhaul to packet based network while using Circuit Emulation Service (CES) will require clock synchronization on both ends
• Multiple clock domains can be supported by use of “differential clock”
• CES requires only frequency synchronization, that can be achieved by using ACR, SyncE and 1588v2 technologies
Sample Deployment
2G / 3G / 4G Cell Site Design
• 2G / 3G Cell site
• 4G cell site
Why use 1588v2 for the migration
• Not a bookended solution • New mechanisms to increase accuracy
– 1588v2 Transparent Clock – 1588v2 Boundary Clock
• Future proof for 4G support – can support phase synchronization as well
Manish Gupta, Symmetricom
Base Station
microwave backhaul
SSU
TDM
Grandmaster IEEE 1588
PTP / IEEE 1588
SyncE
Network Synchronization
TDM
IEEE 1588
LTE Cluster SyncE
IEEE 1588
SyncE
Frequency and Time Specifications Application Frequency Time
LTE (FDD)
LTE (TDD)
LTE MBSFN
LTE-A CoMP (Network MIMO)
WiMAX (TDD)
CDMA2000
TD-SCDMA
GSM / UMTS / W-CDMA
UMTS/ W-CDMA Femtocells
GSM, UMTS, LTE Network Interface
N/A
+/- 1.5 µs small cell, +/- 5µs large cell
+/- 1-32 µs, implementation dependent
+/- 500 ns (0.5 µs), pre-standard
+/-1 - 8 µs, implementation dependent
50 ppb
50 ppb
50 ppb
50 ppb
50 ppb
50 ppb
250 ppb
50 ppb
N/A
50 ppb
50 ppb
+/-3 – 10 µs
+/- 1.5 µs
Synchronization Options
From Frequency to Frequency + Time (Phase)
GNSS with PTP (SyncE) Holdover
GNSS with Rubidium (SyncE) Holdover
GNSS, PTP, Rubidium - You Need 2 Out of 3
PTP with Rubidium (SyncE) Holdover
IEEE 1588–2008 is the second version of a mature IEEE standard
IEEE 1588-2008 (PTP) Defined
Protocol Specification ratified by IEEE for providing precise timing and frequency over packet-based networks
IEEE 1588 PTP History
1588 PTP 2002 (also called v.1) - approved in 2002 1588 PTP 2008 (also called v.2) - approved in 2008
• Introduction of PTP Profile concept
ITU-T Telecom Profile for frequency (G.8265.1) • Approved in 2010
IEEE 1588-2008 & Interoperability
Telecom Profile Objectives
• Meet the performance criteria for synchronization of cellular basestations when operating over managed networks
• Allow interoperability between PTP Grandmasters and PTP Slave clocks
• Allow co-existence with other sync networks (such as SyncE and SDH)
• To enable the design of protection schemes compatible with existing sync networks
G.8265.1 Telecom Profile defines the key parameters for interoperability among vendors
SyncWorld™ Ecosystem Program
Symmetricom® has established the
SyncWorld™ Ecosystem Program to enable
interoperability and cooperation among the
vendors to ensure delivery of precise timing and
synchronization services across the network
Symmetricom IEEE 1588 Deployments
PTP PTP
PTP
PTP
PTP PTP
PTP
PTP PTP
PTP
PTP
PPT PPT PTP
PTP
PTP
PTP
PTP PTP
PTP
PTP PTP
PTP
PTP
PTP PTP
PTP PTP
PTP PTP PTP
PTP
PTP
PTP
PTP
65 + Live IEEE 1588 Network Deployments
Errol Binda, Aviat
Carrier Ethernet Maturity Alongside 1588/1588v2
• Carrier Ethernet maturity has provided a foundation for available and predictable CE backhaul services in the last few years in parallel with 1588/1588v2 maturity
– Standards maturity e.g. MEF – Vendor adoption e.g. networking, testing, management – Interoperability testing e.g. EANTC, ecosystems – Competitive CE services
Heavy Reading
1588v2 Adaption to all Forms of Backhaul Transport
• 1588v2 being supported across all Ethernet transport options • Microwave dominates global mobile backhaul –> migrating to Hybrid & All Ethernet • 1588v2 deployment ease is dependent on a reliable and predictable backhaul network,
including microwave
Heavy Reading Dec. 2010
Some Unique Attributes of Microwave Backhaul for Supporting 1588v2
• Microwave ‘last mile’ is typically many miles over multiple hops - > engineer for delay and jitter to support 1588v2
2G/3G/4G
~
~ Primary
Reference Clock
~
1588v2 Grandmaster Clock
1588v2 Slave Clock
1588v2 over Ethernet Microwave Over Multiple Hops
~
~ ~
~ ~
~
Primary Reference Clock
~
1588v2 Grandmaster Clock
1588v2 Slave Clocks
1588v2 over Ethernet Microwave over Protected
Rings
Some Unique Attributes of Microwave Backhaul for Supporting 1588v2 Cont.
• Microwave transport is designed to accommodate a variable radio path -> ACM prioritization for 1588v2
Microwave Adaptive Coding and Modulation
Some Guidelines to Ease 1588v2 over Microwave Deployment
For more info, see Light Reading’s Mobile Backhaul Synchronization Briefing Center: “Deploying IEEE 1588v2 Synchronization over Packet Microwave Networks” Application Note http://www.lightreading.com/mobile_bh/
Proper engineering eases 1588v2 over microwave deployments, for example: - Maintain an end to end link delay between 100-500uS per link - Prioritize 1588v2 over other traffic and ensure consistent traffic management (QoS
policy, scheduling, shaping etc.) across the entire radio network - Ensure that Synchronization traffic receives the highest priority in any ACM state
Patrick Donegan, Heavy Reading
“On a scale of 1 to 5, where 5 is “highly likely” and 1 is “not likely at all,” please rate the likelihood that your company will adopt the following synchronization solutions as its preferred approaches to provide synchronization of packet backhaul over the next three years”
0
200,000
400,000
600,000
800,000
1,000,000
1,200,000
End 2010 End 2011 End 2012 End 2013 End 2014 End 2015
Glob
al c
ell s
ites
in li
ve s
ervi
ce w
ith E
ther
net B
ackh
aul
IEEE 1588 Synchronous Ethernet T1/E1 GPS Other
Heavy Reading’s Backhaul Synchronization Forecast
Q&A Session
Please submit your questions!
Back up
Backhaul Network Transformation
From Single Service TDM Hub and Spoke Access…
… to Optimized IP/Ethernet Multi-service Mesh Network
Unified Insight • Backhaul networks must
simultaneously support Any combination of 2G, 3G, 4G cell sites
The Global Cell Site Market
Source: Equipment vendors, service providers, press, and Heavy Reading estimates 35