Sync Solutions For LTE - 2

Synchronization Solutions for LTE Networks
Charlie Ferreira
February 2013
Confidential Copyright 2012
Agenda
Standards and Requirements Synchronisation in 3G networks Evolution and relationship between Mobile networks and synchronisation
Migrating to sync to support LTE requirements
Synchronization Distribution Architecture for LTE Symmetricom Solutions
Standards and Requirements
The Basic Question
How should I synchronize my LTE networks?

The answer is driven by service delivery network fundamentals:
Selection of LTE technology (LTE-FDD, LTE-TDD, LTE-Advanced) drives the synchronization requirements Mobile network equipment selection and cell site locations (particularly for small cells) define what can and cannot be done Backhaul network technologies, topology and performance drive decisions for sync equipment selection and deployment locations
Frequency, Time and Phase Synchronization

Frequency Synchronization
TA=1/fA
A
TB=1/fB
B fA=fB
Phase Synchronization
TA=1/fA
A
TB=1/fB
B fA=fB
Time Synchronization
01:00:00 01:00:10
TA=1/fA
A
TB=1/fB
t t
B
fA=fB
01:00:00
01:00:10 5
Structure of ITU-T Sync. Recommendations

Definitions / Terminology
G.8260: Definitions and Terminology for Synchronization in Packet Networks
Basic Aspects
Frequency
G.8261: Timing and Synchronization Aspects in Packet Networks (Frequency)
G.8261.1: PDV Network Limits Applicable to PacketBased Methods (Frequency)
G.8261.2: Reserved for future use
Time/phase
G.8271: Time and Phase Synchronization Aspects in Packet Networks
G.8271.1: Network Requirements for Time/Phase
G.8271.2: Reserved for future use
Network Requirements
G.8262: Timing Characteristics of a Synchronous Ethernet Equipment Slave Clock (EEC) G.8263: Timing Characteristics of Packet-Based Equipment Clocks (PEC)
G.8272: Timing Characteristics of a Primary Reference Time Clock (PRTC) G.8273: Packet-Based Equipment Clocks for Time/Phase: Framework G.8273.1: Telecom Grandmaster (T-GM) G.8273.2: Telecom Boundary Clock (T-BC)
G.8273.3: Telecom Transparent Clock (T-TC)
G.8273.4: Telecom Time Slave Clock (T-TSC)
Clocks
Methods
G.8264: Distribution of Timing Information through Packet Networks G.8265: Architecture and Requirements for PacketBased Frequency Delivery G.8265.1: Precision Time Protocol Telecom Profile for Frequency Synchronization
G.8265.2 PTP Telecom Profile for Frequency #2
G.8274: Reserved for future use
G.8275: Architecture and Requirements for Packet-Based Time and Phase Delivery G.8275.1: PTP Profile for Time and Phase Synchronization (full timing support) G.8275.2: PTP Profile for Time and Phase Synchronization (partial timing support)
Under development options
Profiles
New!
6
Completed
1st
version published
Mobile Network Requirements

Mobile Standard G.8261.1 network limits for traffic interfaces 16ppb Frequency sync for the air Interface 0.05ppm 0.05ppm 0.1ppm 0.1ppm 0.25ppm 0.25ppm 0.05ppm 0.25ppm 0.1ppm No requirements (but see hetnets for LTE-Advanced) N/A 0.25ppm 3usec - small cell (<3km radius) 10usec large cell (>3km radius) 3usec small cell (< 500m radius) 1.33 + Tpropagation s, for large cell (> 500m radius), Tpropagation: propagation delay between the Home BS and the cell selected as the network listening synchronization source 3GPP TS36.133 & TS36.922 3GPP TS36.104 Phase Sync Standards
2G - GSM 3G - UMTS/WCDMA Wide area BS Medium Range BS Local Area BS Home BS 3G Femtocells LTE (FDD) Wide Area BS Home BS LTE (FDD) Local Area & Medium Range BS
16ppb
No requirements
N/A 16ppb N/A
3GPP TS25.104(FDD) and TS25.105(TDD)
LTE (TDD) Wide Area BS

LTE (TDD) Home BS
16ppb
0.05ppm
LTE-Advanced (Release 11) Optional features*: MBSFN CoMP Carrier Aggregation Hetnets with eICIC
16ppb
0.05ppm
1s proposed 0.5s proposed ? 5s proposed
TBA
* As shown in the table, LTE-FDD local area base stations (Pico cells and small cells) do not require phase sync. However, when we get to LTE-A hetnets, there will be interference control between cells, which will place a 5 s phase sync requirement. The phase sync figures for these have been proposed but have yet to be fully agreed by the standards bodies.
Why is Synchronization Required?

Application
Why You Need to Comply
Call Initiation
Impact of Non-compliance
Call Interference Dropped calls Packet loss/collisions Spectral efficiency Video broadcast interruption Poor signal quality at edge of cells, LBS accuracy Spectral inefficiency & Service degradation
LTE (FDD)
LTE (TDD)
Time slot alignment Proper time alignment of video signal decoding from multiple BTSs Coordination of signals to/from multiple base stations
LTE MBSFN
LTE-A MIMO/COMP
LTE-A eICIC
Interference coordination
Needs and Impacts are cumulative: plus all of the above
Synchronisation in 3G networks
3G Synchronisation Requirements
USER EQUIPMENT BASE STATION RADIO ACCESS NETWORK BASE STATION CONTROLLERS MASTER CONTROLLERS PUBLIC SERVICE NETWORKS
G.811 Traceable +/- 50ppb ETSI TS 125 104 TDM Transports Synchronisation
Core
Microwave/ WiMAX ITU-T G.823 Compliant TDM
TDM/ ATM
BSC
MSC
GMSC
BTS +/- 50 ppb Macro/Microcell +/- 100 ppb (PicoCell) 3GPP
AIR INTERFACE
IP Service Network
eNode B NodeB Timing Chain Interrupted
RNC
Ethernet
SGSN
GGSN
G.811 Traceable G.812 Holdover ETSI TS 125 402
OLT
250 ppb Accuracy Femtocell

DSLAM
AGW (LTE)
AGW (LTE)
G.811 PRC for TDM Transport
G.811 PRC for TDM Transport
NTP Overlay for event recording, Call Data Records & Femtocell Sync
Confidential Copyright 2012 10
3G Synchronisation in an all IP RAN using IEEE1588 PTP

Each RNC has a fully redundant TP5000 GrandMaster Hop count between the GrandMaster and clients should be kept to 10 max. Each TP5000 GM supports up to 1000 PTP clients Additional units may be considered should the number of PTP clients exceed 1000. SyncE is provided from the TP5000 E1/2MHz outputs which will connect to the router/switch BITS IN port. ITU-T specifies the number of hops in SyncE as 20. However, in practice, the number of hops from the GM to the end points should be kept to around 10. NOTE: If PTP is used to deliver sync to the RBS, it is not necessary to use SyncE. The TP5000s receive their main reference from built-in GPS. As an option, the TP5000 can receive a clock reference derived from another source such as Cesium clocks
RNC
GPS
SyncE PTP
Packet Network
TP5000 Grandmaster
PTP Flow
PTP Client 12
Evolution and relationship between Mobile networks and synchronisation
13
Evolution and relationship between Mobile networks and synchronisation

As the TDM platform is replaced by all IP networks, it is no longer possible to distribute sync in the same way as TDM
Packet network cannot pass sync in the traditional TDM way New sync methods are required to achieve sync delivery
New sync methods include:

IEEE15888v2 (or PTP) SyncE NTP
The current BSNL sync architecture is well planned and implemented However, sync delivery in TDM is completely different to sync delivery in the IP world, with the exception of SyncE which is similar in nature
How to migrate existing Sync to NG to meet LTE requirement

Planning Objectives & Rules The migration plan must allow seamless upgrade and support introduction of new applications
IP MBH LTE (TDD, LTE-A, etc)
The synchronisation platform must support all sync requirements

SyncE, IEEE1588 (PTP), NTP and TDM (E1/2MHz)
The packet network elements shall be able to deliver or support the new synchronisation technologies
SyncE, PTP, NTP
15
How to migrate existing Sync to NG to meet LTE requirement

Planning Objectives & Rules Identify the requirements of each application (2G/3G/4G) and transport media to that application to determine the type of synchronisation to be used
For example:
2G/3G base station needs 16ppb frequency sync Transport is CE Use SyncE if it is supported by the transmission path Use PTP if SyncE is not possible
16
Synchronisation in the TDM Network SDH

The PRC reference is distributed through the SDH network SSUs are used to regenerate the reference Ultimately, the reference is delivered to the BTS/NodeBs
TDM Access
SDH
SSU
SDH
SSU
SDH
SSU
SSU/PRC
SDH
TDM Sync flow
17
Migrating to a Hybrid Network TDM & IP with SyncE
TDM Access
Access
SDH
SSU SSU
Aggr
Access
Aggr SDH
SSU
SDH
SSU
SSU/PRC
IP Core
SSU
SSU
Aggr
SDH
TDM Sync flow
SyncE flow
18
Migrating to a Hybrid Network TDM & IP with SyncE

Sync in the SDH portion remains unchanged
Sync from the PRC is fed to the IP network as an E1/2MHz reference (into the NE BITS port) SyncE works in the same way as SDH sync
Physical layer Same planning rules PRC, SSU regeneration, 5 to 10 hops Delivers high quality sync, traceable to PRC According to G.8261
However Each NE is the chain has to support SyncE not always possible Only delivers frequency sync, no phase/time sync The cell site device (CSS, CSR) must be able to convert SyncE to E1 to synchronise the 2G/3G base station
Migrating to a Hybrid Network TDM & IP with PTP (optionally over SyncE)
TDM Access
Access
SDH
SSU
SSU 1588
Aggr
Access
SDH
SSU
SDH
SSU
SSU/PRC (PTP GM)
IP Core
SSU 1588
SSU 1588
Aggr
Aggr
SDH
TDM Sync flow
SyncE flow
PTP flow
20
Synchronisation in a Hybrid Network TDM & IP with PTP (optionally over SyncE)
Sync in the SDH portion remains unchanged
IEEE1588 GMs are added at the aggregation layer GM ports connect to Ethernet ports on the routers PTP flows are distributed to the base stations Uses Unicast mode, telecom profile according to ITU-T G.8265.1 NOTE The transmission network does not need to support PTP (on-path support) This method is highly suitable for delivery of frequency sync to 2G/3G 10 hops between GM and the clients Either the base station has a PTP client or the cell site device (CSS, CSR) must be able to convert PTP to E1 to synchronise the 2G/3G base station
21
ITU standardising use of PTP + SyncE

Running PTP Only Phase drift off as t2 during holdover when losing PTP
Frequency
Running PTP + SyncE Phase drift off linearly during holdover when losing PTP
Frequency
Phase
Phase
with PTP actively controlling PPS
without PTP NO PPS control
with PTP actively controlling PPS
without PTP NO PPS control
22
Current Architecture Directions
23
MBH Synchronisation in all IP LTE - TDD

G.8275.1 Submission Led by China Mobile with support from Huawei and ZTE G.8275.2 Submission Led by Symmetricom, AT&T, Cisco with support from Sprint, Verizon, T-Mobile, NSN, Juniper, and Ericsson.
24
CMCC Architecture (pre G.8275.1 ) PTPoL2 + Multicast + SyncE + BC at every node

Boundary Clock
Primary PTP GM PTP GM DSL modem
PTP Slave
PRTC
DSLAM
PTP Slave
PTP GM PRTC Secondary PTP GM
OLT
ONU
PTP Slave
PTP Slave
Edge Packet Network Access Network (packet time and frequency distribution)
End Equipment (e.g. Base stations)

25
Managing Asymmetry in BC Everywhere (China Mobile)

T a b a=b T = a+b/2
Perfectly symmetrical network time propagation is relatively easy
T a
a =/= b T = a+b/2 > T
Asymmetrical network time propagation is difficult
26
Issues: Managing Asymmetry in BC in Every Node (China Mobile)

The only solution to the problem of network asymmetry is to measure the delay on downstream and upstream for every fiber and every potential PTP path and put that compensation offset into every BC this has to be done Manually today
T a OFFSET injected
Asymmetrical network Manual offset calibration required
27
Other Issues: Managing Asymmetry in BC in Every Node

Legacy MPLS / CE networks do not have BC support in NE Not backward compatible it is difficult or impossible to upgrade a network without massive new investment in switches/routers
BC everywhere requires syncE

Legacy Ethernet networks so not usually support syncE
Multicast does not solve problems inherent in asymmetry when distributing time
Currently operator has to measure the time offset on every link manually and put a compensation factor into every BC in an attempt to manage time distribution
28
Why new architectures for Time/Phase G.8275.2

The G.8275.1 scheme is only suitable for green field networks Many Service Providers need an upgrade path from currently deployed G.8265.1 (Frequency) networks to Phase
Introducing Boundary clocks in every node is not practical Layer 3 operation is needed
Manual asymmetry compensation is not practical New architectures are being tested by many operators and introduced at the ITU
29
G.8275.2 - Segmented Architecture

Divides the macro network into smaller sectors each capable of accurate time transfer using G.8265.1 PTPoL3 Unicast , combined with SyncE TC possible in Access NEs for Asymmetry resolution
Primary PTP GM PTP GM PTP Timing Flows Edge GM Edge GM DSLAM DSL modem PTP Slave
PRTC
PTP Slave
Edge GM PTP GM PRTC Secondary PTP GM Protection Timing Flows Edge GM
OLT
ONU
PTP Slave
PTP Slave End Equipment (e.g. Base stations)

30
Edge Packet Network Access Network (packet time and frequency distribution)
G.8275.2 - Segmented Architecture

Strategically-placed BCs break timing path into segments
Simple network upgrade from Frequency Profile
Uses intelligent syntonized boundary clocks (EM)

Combine sync from any available source: PTP, SyncE, SDH, GPS etc. Effectively a multi-source sync clean-up and re-generation SSU function Implemented as a Standalone box - Edge GM
Design rules
No more than 3 switch/routers between BCs No more than 10 network elements between GM and Slave
PTP GM
PTP BC
PTP BC
PTP Slave
31
ITU-T Submission G.8275.2: A Cost Effective Alternative to BC in every NE

PRTC GM Edge GM
PTP Slave
eNodeB
No change out for network hardware

Can run time/phase services over existing MPLS / CE network
Preserves MPLS value proposition
Leverages existing investment made in GPS at eNodeB sites

Leverages any existing PTP deployments for FDD architectures
No change to back office engineering and operations processes

Removes BC engineering
Deploys highest quality PTP client

Compliant to all existing FDD and TDD standards
Driving the standards forward
Stand alone sync not dependent on embedded NE

Quality of BC design not an issue
Simple and easy to deploy for all LTE architectures

32
Guidelines
1. Use an independent source for sync
Best in class solutions Efficient operation in a multi-vendor network
2. Protect your sync for service assurance

GNSS, PTP & Stable frequency source High performance holdover
3. Deploy a PTP master where the network needs it for accuracy

Network supports accuracy: PTP GMs in aggregation network Uncertain network: PTP Grandmaster at or near the edge
Basic Network Scenarios

1. LTE frequency, managed Ethernet backhaul
Consistent, known backhaul performance
2. LTE frequency, high PDV, noisy backhaul

Diverse transport technologies, 3rd Parties, many hops
3. LTE phase, retrofitted or new Ethernet backhaul

SyncE and Boundary Clocks in every network element
4. LTE phase, existing backhaul, possibly high PDV, noisy

No BC, probably no SyncE, diverse transport, 3rd party
Setting and Holding

Two aspects of synchronization
Frequency
Deliver and set frequency Hold frequency
Phase
Deliver and set phase Hold phase
35
1. LTE Frequency: G.8265.1 Architecture

Managed Ethernet backhaul
consistent, known performance
CORE AGGREGATION ACCESS
PTP GM Macro eNodeB
PTP GM
Small Cell Agg. Metro Small Cells
Set frequency with PTP (GNSS primary source) Hold frequency with high quality oscillator
1. LTE Frequency: G.8265.1 Architecture

Managed Ethernet backhaul
consistent, known performance
Synchronization Distribution Architecture
Sync equipment and deployment
Macro agg. site: high capacity PTP grandmaster, redundant equip. configuration and network protected Macro eNodeB: PTP client & high quality oscillator (or GPS/GNSS) Metro Small Cell: PTP client (softGPS)
Pros
Fully protected synchronization Proven in networks worldwide Fully standards based
PTP delivery: engineered QoS/CoS or EVC/VPN, shortest path PTP profile: G.8265.1, layer 3, unicast 1 or 2-step clock
37
2. LTE Frequency: Edge Overlay Architecture

Uncertain performance, noisy backhaul
Multiple technologies, many hops/paths, high delay variation, alternate access vendors, etc.
High PDV / 3rd Party edge GM PTP GM Microwave Macro eNodeB
PON
OLT ONU
edge GM
PTP GM
DSLAM
DSL
modem
Set frequency with PTP or GNSS Hold frequency with PTP or GNSS
Consistent with G.8265.1

38
2. LTE Frequency: Edge Overlay Architecture

Uncertain performance, noisy backhaul
Macro agg. site: high capacity PTP grandmaster, redundant equip. configuration and network protected Macro eNodeB site: PTP Master with GNSS Metro Small Cell: PTP client (softGPS)
Pros
Fully protected synchronization Mobile network sync is unaffected by backhaul technology or quality Proven technology, fully standards based
PTP delivery: engineered QoS/CoS or EVC/VPN, shortest path PTP profile: G.8265.1, layer 3, unicast 1 or 2-step clock
39
3. LTE Phase: Pre-stand G.8275.1 Architecture

Retrofit existing equip. or build new network
Managed Ethernet, synchronous Ethernet, boundary clocks
SyncE PTP GM
BC
SyncE
BC
SyncE
BC
SyncE
BC
SyncE
BC
SyncE
BC
SyncE
Rb
Macro eNodeB
BC
SyncE
BC
SyncE
BC BC
SyncE
SyncE PTP GM
BC
SyncE
BC
SyncE
SyncE
Set time/phase with PTP (GNSS at primary source) Hold time/phase with rubidium
3. LTE Phase: Pre-stand G.8275.1 Architecture

Retrofit existing equip. or build new network
Managed Ethernet, synchronous Ethernet, boundary clocks
Macro agg. site: high capacity PTP grandmaster, SyncE, redundant equip. configuration and network protected Macro eNodeB: PTP client and Rb Metro Small Cell: PTP client (softGPS)
Cautions
Asymmetry may require hop by hop, manual adjustments to time offset Quality of PTP client affects performance No upgrade path from G.8265 frequency architecture
PTP delivery:
SyncE and boundary clocks, possibly with segmented architecture
Design Rules
SyncE through entire transmission path for stability Boundary clock on all transmission network elements
41
PTP profile: pre-G.8275.1, layer 2 multicast 1-step clock
4a. LTE Phase: Hybrid GPS/PTP Arch.

Existing backhaul, good performance
Last mile of network supports accuracy needed for phase to macro
CORE
AGGREGATION
ACCESS
edge GM
PTP GM
Rb
Macro eNodeB High PDV / 3rd Party edge GM
Microwave
PTP GM Small Cell Agg. Metro Small Cells
Set time/phase with PTP Hold time/phase with PTP or Rb

Pre-G.8275.2 (consistent with G.8265.1) Requires high quality PTP slave Once set, asymmetry is not an issue
42
4a. LTE Phase: Hybrid GPS/PTP Arch.

Existing backhaul, good performance
Last mile of network supports accuracy needed for phase to macro
Macro agg. site: high capacity PTP grandmaster, redundant equip. configuration and network protected Access network site: PTP master/ BC with GPS/GNSS Macro eNodeB: high quality PTP client and Rb Metro Small Cell: high quality PTP client (softGPS)
Pros
Saves deploying master at the cell site Fully protected synchronization No network retrofit: mobile network sync is unaffected by backhaul technology or quality Asymmetry not an issue Proven technology, standards based
PTP delivery: engineered QoS/CoS or EVC/VPN, shortest path PTP profile: pre8275.2 (G.8265.1), layer 3 unicast 1 or 2-step clock
43
4b. LTE Phase: Edge Overlay Architecture

Existing backhaul, diverse tech and/or noisy
Multiple technologies, many hops/paths, high PDV, 3rd party, etc.
CORE
AGGREGATION
ACCESS
PTP BC
PTP GM Macro eNodeB High PDV / 3rd Party edge GM Microwave PTP GM Small Cell Agg. Metro Small Cells
Set time/phase with GNSS Hold time/phase with PTP

Pre-G.8275.2 (consistent with G.8265.1) Requires intelligent, high quality implementations of BC at aggregation site and PTP slave at macro 44
4b. LTE Phase: Edge Overlay Architecture

Pros
Fully protected synchronization No network retrofit: mobile network Macro agg. site: high capacity PTP grandmaster, sync is unaffected by backhaul redundant equip. configuration and network protected technology or quality Access network site: high quality PTP BC Asymmetry not an issue Macro eNodeB: high quality PTP client & GNSS/GPS Proven technology, fully standards Metro Small Cell: high quality PTP client (softGPS) based PTP delivery: engineered QoS/CoS or EVC/VPN, shortest path PTP profile: pre-8275.2 (G.8265.1), layer 3 unicast 1 or 2-step clock
Residential and Enterprise Indoor Small Cells

Wireline network backhaul
DSL, PON, Cable, Metro Ethernet
INTEROFFICE FACILITIES
NTP Server PTP GM
WIRELINE ACCESS NETWORK

PON
OLT ONU
DSL
DSLAM
modem
Cable
CMTS
modem
NTP Server PTP GM

Core: high capacity, carrier grade NTP server (or PTP grandmaster); redundant equip. configuration and network protected High quality embedded clients in the small cell; with or without softGPS
46
Summary
LTE technologies drive new requirements for synchronization Backhaul network technologies, topology and performance drives synchronization equipment and deployment decisions Emerging boundary clock solutions will work for some scenarios but not all GPS/GNSS requires back up and is not feasible for some deployment scenarios An alternative architecture that places a PTP master at or near the edge is the solution for many of these situations
47
Symmetricom Solutions for LTE Networks
48
NGN Product Family

TimeCesium
Primary Reference Source ITU-T G.811 compliant 12 year warranty tube
TimePictra Next Gen EMS TP10

Full FCAPS Platform independent PTP Performance monitoring Resiliency, northbound interfaces and much more
SSU2000
Carrier Class Performance, G.811 compliant PTP GrandMaster Modules NTP Modules GNSS support, SyncE outputs
49
NGN Product Family

Time Provider 5000 (TP5000) PTP GM
G.811 Compliance Timing Distribution System (TDM, 1588, SyncE, NTP) Management software
EdgeMaster - TimeProvider 2000 Series

Delivers G.8272 PRTC time/phase accuracy within 100ns of UTC Boundary Clock function PTP, SyncE, TDM interfaces GNSS support Rubidium or OCXO holdover
Time Provider 500 (TP500)

Stand-alone client PTP input - E1/2MHz, 1pps and 10MHz outputs
TimeCesium Primary Reference Source (PRS)

Primary Reference Clock By Definition Cesium PRS designed for Telecommunication applications. Install and forget autonomous technology with no antenna installation. Compliant with G.811 accuracy requirements Single chassis for NEBS (rear access) or ETSI (front access) Field Changeable Panels for Reversible front/rear access. CE Mark, ETSI and NEBS certified. Dual -48 volt DC Power Inputs. Standard 12 Year Warranty on the Cesium Tube.
Precision Time Protocol (PTP)

PROVEN STANDARDIZED
IEEE 1588-2008 (also called v.2) approved in 2008 Introduction of PTP Profile concept ITU-T PTP Telecom Profile for frequency (G.8265.1) Approved in 2010
Deployed over 100 networks globally Deployedin in over 150 networks globally
INTEROPERABLE
SyncWorld EcoSystem Program

Flexible PTP Grandmaster Platforms

SSU PTP Blade SSU blades support your network when: An SSU is installed on site When the BSC/RNC is co-located at Mobile Switching Centers. TimeProvider 5000 For applications beyond the Central Office, a cost-effective stand-alone GM is available: At remote BSC/RNCs, POPs and offices without an existing SSU2000 / where TDM port count does not require an SSU
Added carrier class NTP
53
TimeProvider 5000 Release 2.0

Carrier grade NTP server Rel. 2.0 new SW features Expansion shelf support, new IMC required Input priority switching NTP Server (optional SW license) 500 VLAN support (optional SW license) PTP probe (optional SW license) TimeProvider Expansion 1RU Rack-and-Stack with TP 5000 PTP GM Up to 10 expansion shelves, Flexible, NGN Building Blocks TimeProvider Expansion10: SyncE and PTP (L2 multicast) TimeProvider Expansion30: E1 and 1PPS/TOD
Ultra high capacity High precision Hardware redundancy

Two versions to sell
Dedicated NTP server Dual PTP/NTP (TP5k option)
TP 5000 TPE10 TPE30

Strategic Program Enabling the Mobile Edge

WHAT
Deploy the PTP master to edge aggregation sites
VALUE
Delivers PTP closer to edge of the network Enables precise sync for LTE-Adv and Small Cells
SYMM Advantage
Performance assurance for LTE phase delivery Not dependant on full on-path support
Core
Aggregation
Edge
Small Cells
Metro
PTP/SyncE
IEEE 1588 (PTP)
PTP/SyncE
Metro
Enabling the Mobile Edge Introducing Time Provider 2000 Series
Precise network timing solutions optimized for small cells

Accelerates adoption of cost-effective partial-path PTP sync (G.8275.2) Delivers frequency & phase timing services for up to 64 clients
Time Provider 2700 PTP Grandmaster Clock

Delivers G.8272 PRTC time/phase accuracy within 100ns of UTC Delivers G.811 PRC frequency accuracy to within 1 x 10 -11 1588v2 PTP support for 1-step, 2-step methods (unicast, multicast*) GNSS support with GPS and optional GLONASS
Target Availability Q2 2013
Time Provider 2300 PTP Carrier-Grade Boundary Clock

Best-in-class PTP client provides outstanding performance in noisy networks Converts PTP to L1 Frequency Sync (G.8265.1 Telecom Profile) and/or T1/E1 Used available frequency inputs (Sync-E or E1/T1) to reduce system recovery time
Both 2700 and 2300 employ a common PTP SW architecture, our most advanced PTP timing algorithms, and high quality oscillators (OCXO or Confidential Copyright 2012 that together deliver excellent operational performance. Rubidium)
*Future56
Time Provider 2700 Hardware Features

Model 2700 Grand Master PTP Clock
GNSS (GPS) L1 input 2 oscillator options: OCXO, Rubidium 2 x 100/1000 Copper (RJ45) Ethernet Interfaces (PTP, Sync-E) PTP Output (with 8 clients, upgradeable to 64) Sync-E (Input / Output) 1 x 10MHz or 1PPS programmable BNC output Redundant-DC Power, 1RU, 19 rack, 224mm deep Same hardware features as Model 2700 E1/T1 Frequency Support (input/output) 2 x 100/1000 Optical SFP Ethernet Interfaces (PTP, Sync-E) 1 x PPS+TOD (RJ45, RS422) Interfaces (output) AC Power Option NEBS-compliant
Model 2750 Grand Master PTP Clock with Legacy TDM Support
SW License Options
PTP Input License (alternate or backup to GPS, provides asymmetry compensation) PTP Output Capacity Upgrades (16, 32, 64) GLONASS GNSS Upgrade

Model 2700 Grand Master PTP Clock
Model 2750 Grandmaster Clock with Legacy TDM Support
58

Model 2300 Carrier Grade Boundary Clock
2 oscillator options: OCXO, Rubidium 2 x 100/1000 Copper (RJ45) Ethernet Interfaces (PTP, Sync-E) PTP (Input and Output with 8 clients, upgradeable to 64) Sync-E (Input / Output) 1 x 10MHz or 1PPS programmable BNC output Redundant-DC Power, 1RU, 19 rack, 224mm deep
Model 2350 Carrier Grade Boundary Clock with Legacy TDM Support
Same hardware features as Model 2300 Legacy E1/T1 Frequency Support (input/output) 2 x 100/1000 Optical SFP Ethernet Interfaces (PTP, Sync-E) 1 x PPS+TOD (RJ45, RS422) Interfaces (output) AC Power Option NEBS-Compliant
SW License Options
PTP Output Capacity Upgrades (16, 32, 64)
Time Provider 2300 Hardware Variants

Model 2300 PTP Boundary Clock
Model 2350 Boundary Clock with Legacy TDM Support
60
TimeProvider 2000 Series Flexible Deployment Options

TP2000 can be deployed in a wide range of environments.
Outdoor Enclosures
Indoor Data Centers
Wide temperature range -40C to +60C* allows deployment in many non-air conditioned cabinets Dual DC Power feeds simplify connecting to battery backup systems AC Power option** helps with deployment in enterprise locations NEBS compliance** enables deployment in central office locations
* OCXO Oscillator only, Rubidium is -5 to +55C. 61 ** Models 2350 and 2750.
Platform positioning based on network location

Core
Up to 1000 Clients GM Indoor TDM, PTP, Sync-E
Aggregation
Up to 64 clients GM or BC Indoor / Outdoor TDM, PTP, Sync-E
Edge
Up to 8 Clients GM or BC Indoor / Outdoor PTP, Sync-E
Small Cells
SSU2000
TP5000
Metro Outdoor Large Venues Enterprise
TP2700 / TP 2300
62
Platform Functional Comparison

TP 5000 Grand Master
Inputs T1/E1, GPS, 1PPS PTP, NTP, T1/E1, 1PPS, Sync-E (w/TPE10) 1,000 per shelf
- Telecom unicast - G.8265.1 unicast - Default L3 multicast - Hybrid
SSU 2000 Grand Master

T1/E1, GPS, (TimeHub 1pps)
TP2750 Grand Master

GPS T1/E1, SyncE, PTP PTP, T1/E1, SyncE 10MHz, 1PPS Up to 64 (license options)
- Telecom unicast - G.8265.1 unicast - Default L3 multicast - Pre G.8275.1, L2 MC
TP2350 Boundary Clock

T1/E1, SyncE, PTP PTP, T1/E1, SyncE 10MHz/1PPS Up to 64 (license options)
- Telecom unicast - G.8265.1 unicast - Default L3 multicast - Pre G.8275.1, L2 MC
Outputs
Client capacity
PTP, (SSU SyncE)

400 / blade SSU
- Telecom unicast - G.8265.1 unicast - Default L3 multicast - Hybrid
Profiles
Redundancy VLAN Boundary Clock
Yes
(card, port, power)
Yes
(card, port, power)
No
(Rdnt DC w/AC opt)
No (Rdnt DC PWR)
Up to 66 Yes
500 per port No
4 No
Up to 66 Yes (license option)
Op Temp Range
Availability
-5 to 55 C
GA
0 to 50 C
GA
-40 to 60C (OCXO) -5 to 55C (Ru)

Q2-CY2013
-40 to 60C (OCXO) -5 to 55C (Ru)

Q2-CY2013
63
TimeProvider 2000 Series Use Cases

Multiple technologies, many hops/paths, high PDV, 3rd party, etc.
CORE
AGGREGATION
ACCESS
PTP BC
PTP GM Macro eNodeB High PDV / 3rd Party edge GM Microwave PTP GM Small Cell Agg. Metro Small Cells
Set time/phase with GNSS Hold time/phase with PTP

Pre-G.8275.2 (consistent with G.8265.1) Requires intelligent, high quality implementations of BC in access network and PTP slave at macro 64
Use Cases Deploy a 2700 Grandmaster near the Edge

Allows adoption of G.8275.2 sync approaches Cost effective standards-compliant GM at edge aggregation sites Ensures 1.5 us phase accuracy required for LTE network evolution Outputs Time/Phase w/accuracy under 100ns when locked to GPS Outputs Frequency (Sync-E) and/or T1/E1 Fully protected input reference suite If GPS fails, system can fall back seamlessly to other input clock sources:
PTP 1588v2 (Boundary Clock Mode) with automatic asymmetry path compensation based on GPS measurement history Sync-E, T1/E1
Robust oscillator options (high quality OCXO and Rubidium) Ensures the best quality boundary clock operation for backup Provides outstanding hold-over Hardware acceleration (such as time stamping) delivers optimal performance Wide temperature range enables flexible deployment options
Use Cases Deploy a 2300 Carrier Grade Boundary Clock

Use in locations where GNSS is not available or not robust. Use to boost PTP reliability at sites where embedded boundary clocks, offered by Cell Site Routers (CSR), are not delivering sufficient performance. TP2300 Carrier Grade Boundary Clock Advantage
External compact solution ensures predicable performance across the network Advanced clock algorithms & hardware acceleration deliver optimized performance High phase accuracy delivers robust LTE network operation and enables network evolution to advanced LTE features (eICIC, COMP). Optimized hybrid mode operation leverages available frequency inputs such as Sync-E and/or T1/E1* Robust oscillator options (high quality OCXO and Rubidium) Provides outstanding hold-over if the northbound PTP fails Ensures the best quality boundary clock operation
* If available 66
Deployment of a TP2750 at an mobile network aggregation site

Solution is deployed out-of-band from bearer traffic
TP5000 or SSU2000 (GM)
OC
OC
OC
LTE EPC
MPLS / Ethernet
OC VLAN 5 VLAN 3
VLAN 6
Cell Site Router
VLAN 3
BS OC
GPS TP2750 (GM, w/BC Backup)

VLAN 8 VLAN 3
(required for GM operation)
IP A IP B (OC) IP C (GM) Main Bearer Traffic (VLAN5, VLAN6) North Bound: PTP Traffic and/or Sync-E (TP5000 GM to 4500 OC)
South Bound PTP Traffic and/or Sync-E (4500 GM to BS OC) Management Traffic
67
Thank You
Synchronization Solutions for LTE Networks
Charlie Ferreira
cferreira@symmetricom.com
Symmetricom, Inc. 2300 Orchard Parkway San Jose, CA 95131-1017 Tel: +1 408-428-7907 Fax: +1 408-428-6960
www.symmetricom.com
68

Sync Solutions For LTE - 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sync Solutions For LTE - 2

Uploaded by

Copyright:

Available Formats

Synchronization Solutions for LTE Networks

Confidential Copyright 2012

Synchronization Distribution Architecture for LTE Symmetricom Solutions

Confidential Copyright 2012

Standards and Requirements

Confidential Copyright 2012

The Basic Question

How should I synchronize my LTE networks?

Confidential Copyright 2012

Frequency, Time and Phase Synchronization

Structure of ITU-T Sync. Recommendations

G.8274: Reserved for future use

Mobile Network Requirements

N/A 16ppb N/A

3GPP TS25.104(FDD) and TS25.105(TDD)

LTE (TDD) Wide Area BS

1s proposed 0.5s proposed ? 5s proposed

Confidential Copyright 2012

Why is Synchronization Required?

Needs and Impacts are cumulative: plus all of the above

Confidential Copyright 2012

Confidential Copyright 2012

BTS +/- 50 ppb Macro/Microcell +/- 100 ppb (PicoCell) 3GPP

G.811 Traceable G.812 Holdover ETSI TS 125 402

250 ppb Accuracy Femtocell

G.811 PRC for TDM Transport

G.811 PRC for TDM Transport

3G Synchronisation in an all IP RAN using IEEE1588 PTP

Evolution and relationship between Mobile networks and synchronisation

Confidential Copyright 2012

Evolution and relationship between Mobile networks and synchronisation

New sync methods include:

How to migrate existing Sync to NG to meet LTE requirement

The synchronisation platform must support all sync requirements

Confidential Copyright 2012

How to migrate existing Sync to NG to meet LTE requirement

Confidential Copyright 2012

Synchronisation in the TDM Network SDH

TDM Sync flow

Migrating to a Hybrid Network TDM & IP with SyncE

TDM Sync flow

Migrating to a Hybrid Network TDM & IP with SyncE

SSU/PRC (PTP GM)

TDM Sync flow

Confidential Copyright 2012

ITU standardising use of PTP + SyncE

with PTP actively controlling PPS

without PTP NO PPS control

with PTP actively controlling PPS

without PTP NO PPS control

Confidential Copyright 2012

Current Architecture Directions

Confidential Copyright 2012

MBH Synchronisation in all IP LTE - TDD

Confidential Copyright 2012

CMCC Architecture (pre G.8275.1 ) PTPoL2 + Multicast + SyncE + BC at every node

Primary PTP GM PTP GM DSL modem

PTP GM PRTC Secondary PTP GM

End Equipment (e.g. Base stations)

Managing Asymmetry in BC Everywhere (China Mobile)

Perfectly symmetrical network time propagation is relatively easy

a =/= b T = a+b/2 > T

Confidential Copyright 2012