Вы находитесь на странице: 1из 34

Synchronisation network

Aug 2015
Agenda
• Introduction to Synchronisation
9 Basic of TDM sync
9 Our Changing World
• Packet sync: SyncE and PTP
• Centralised vs distributed on a hybrid network
• New Sync Architecture
• Updated Frequency Synchronization Architectures
• Mobile Synchronization Requirement & Standards 
update
Introduction to Synchronisation
Types of Synchronisation
T1=T2
Frequency synchronisation T1
NE1 NE2 NE1
•TDM/Digital Telephony
•SDH transport T2
NE2
•2G, 3G Clock frequency of t
NE1 same as NE2

Phase synchronisation
•LTE-TDD NE1 NE2 NE1
•LTE-Advance
Digital Broadcasting (DVB-T, DAB) NE2
Phase of NE1 clock
t
same as NE2

Time synchronisation
NE1 NE2 20/10/05 20/10/05
NE1
•NTP (RFC 1305) 10:14:05 10:14:06

•PTP (IEEE 1588)


20/10/05 20/10/05 NE2
Time at NE1 same 10:14:05 10:14:06

NTP: Network Time Protocol as NE2


PTP: Precision Time Protocol t
Core & Regional Network‐SDH Sync concepts
• Primary Reference Clock(s) provide the network frequency reference.
• The SDH network transports the clock between nodes
• All TDM elements must be synchronized, they have the same frequency. 
• The clock quality degrades as it passes through the network
–SSUs deployed to remove the jitter/wander and regenerate PRC quality signals.
• Frequency dependent services derive timing from the transport clock

PRC Referenced
PRC Cesium Timing Out to BTS/Node B

Sync Flow Sync Flow


Sync Flow

ADM ADM ADM

To NE’s in
the local node

SSU SSU
5
Classical TDM Sync Distribution
PSTN/PLMN

CENTRAL TDM
OFFICE
SSU

TDM
TDM
TDM Wireless
Base Station

TDM
SSU

SSU Access
(CES/PWE)

SDH CORE 
E1 ACCESS & 
DISTRIBUTION

6
Transmission drive a change

IP network addresses the transport 
economics and bandwidth, but does  Sync

not distribute synchronization:  Sync

Network
ƒ Circuit interfaces are synchronous 
(require frequency reference)
ƒ Mobile base station’s need 
synchronization for mobility & 
spectral efficiency Timing Island

ƒ Synchronization (and QoS) must 
be engineered into the system
How do we keep the synch chain 
between central core and remote 
site?

7
Packet Sync: SyncE and PTP
Synchronous Ethernet
• High capacity Ethernet method that 
transports frequency at the physical 
layer. Sync-E
Sync-E Switch
• Higher Layers including IP layer are  Switch

asynchronous. Sync-E
Sync-E
Sync-E Switch
Network
• SyncE Switches & Routers will use  Switch

external, SSU, or line‐timing to 
recover the frequency for the 
Frequency Transported
Application layer. by SYNC-E PHY

• Line Timing & hop number  PRC/SSU
limitations (similar in concept to 
SDH).
• ITU‐T G.8261 defines Synchronous 
Ethernet. Frequency 
Time of Day X
Location Services X

9
How does Synchronous Ethernet work? 
How is Synchronous Ethernet different from normal Ethernet?

Normal Ethernet PHY


Tx
ƒ The Rx uses the line time Rx
ƒ The Tx uses the built-in 100ppm clock Line
100 ppm
ƒ There is no relationship between the Rx & Tx
ƒ Each link has a separate 100ppm clock.

Synchronous Ethernet PHY External From


ƒ The Rx uses the external or line time PRC/ SSU

ƒ The Rx clock disciplines the internal oscillator


ƒ The internal oscillator (4.6ppm) must be disciplined Rx Tx

and traceable to the PRC. Line


4.6 ppm
ƒ The Tx uses this traceable clock reference.
ƒ This allows each link to synchronize it’s clock to the
previous SyncE switch via the link, providing PRC
Frequency traceability to line timed end points.

10
Synchronous Ethernet Applications

ƒ Mobile Backhaul
ƒ Ethernet to SDH NETWORK
ƒ Circuit Emulation
PDH-Ethernet
CENTRAL
OFFICE SyncE

SyncE

GPS

E1/T1/SyncE SDH ADM


SSU
SyncE

SDH Ring
SyncE

SyncE
TDM
11
PTPv2 ‐ IEEE 1588 ‐ 2008 Overview
Master Clock Time Slave Clock Time IEEE 1588-2008 …
t1 Sync message
• Is a protocol definition, not a product
Data at
Slave Clock • Known as Precision Time Protocol
(PTP)
t2 t2
Follow_Up message • 2008 is also referred to as version 2
containing true value of t1 (with the Telecom Profile)
• Is the second version of a mature
t1, t2 IEEE standard,
t3 t1, t2, t3 • Defines how to transfer precise time
Delay_Req message
over networks. It does not define how
to recover frequency or high precision
t4 time of day.
Delay_Resp message
containing value of t4 • The challenge is to convert packets to
traceable Time & Frequency, and cost
effectively.
t1, t2, t3, t4
time
PTPv2 ‐ IEEE 1588 ‐ 2008 Overview
IEEE 1588‐2008 …
• The Grandmaster “reference clock” sends a series of time‐stamped messages 
to slaves
• Hardware time stamping allows for µs accuracy
• Slaves eliminate the round‐trip delay & synchronize to the Grandmaster.
• Frequency is recovered from the accurate time of day reference.
• Accuracy is enhanced by:
• Frequent packet send rate (up to 128 per second)
• Hardware time‐stamping (eliminate software processing delays)
Embedded
• Best Master Clock scheme Slave (Client)

Grandmaster
1588 Packets
(Server)
External
Slave (Client)
13
Packet Timing Architecture (G.8265)
• Packet Network Timing Protection
• General Packet Timing Architecture
PRC PRC
PRC
Physical layer 
sync network
Primary 
Primary  PTP  PTP  PTP GM
Secondary
PTP GM GM PTP Timing Flows PTP GM PTP  GM PTP Timing Flows
GM
Protection 
PTP  PTP 
Timing Flows
Slave Slave

Packet Network PTP  Packet Network PTP 


PTP  Slave PTP  Slave
Slave Slave
14
G.8265.1 Telecom Profile (Freq)

• Two‐way time transfer 
• One‐way is sufficient for Frequency 
• But using the reverse path often allows for higher performance

• One‐step and Two‐step both allowed
• Slaves have to handle both, GrandMaster may handle only one mode
• One step preferred for bandwidth efficiency, Two‐step may be required for security

• Unicast mandatory
• Hybrid Multicast considered for further revision of the Telecom Profile
• Unicast Negotiation required (clause 16.1 of IEEE1588‐2008)
• Supports Alternate BMCA mode (a slave can listen to N masters)

• PTP Mapping 
• PTP/UDP/IPv4 (IEEE1588‐2008 Annex D)

15
G.8265.1 Telecom Profile – Cont’d

• Message  rates
• Announce:  min 1 packet every 16 seconds, max  8 packets‐per‐second (default 
1packet/2sec)
• Sync (follow up):  min 1 packet every 16 seconds, max 128 packets‐per‐second
• Delay request/delay_response: min 1 packet every 16 seconds, max 128 packets‐per‐
second
• Typical: 16 to 64 packets/sec, depending on oscillator quality

• No On‐Path Support
• No use of boundary clocks nor transparent clocks for Frequency
• BC and TC are considered for the Time Profile (G.8275.1)

• Security Mechanisms
• Left for further study
• Rely on network security (VLAN type)

16
Other 1588 Features 
On‐Path Support
Transparent Clock Boundary Clock
• Switch, not a Clock • Switch with built-in clock
• Measures 1588 packet delay • Internal clock synchronized via 1588 to
inside the switch (residence time) the upstream master
• Modifies (adds) residence time to the • Slave on 1 port, master on other ports
correction field in the 1588 message • Interrupts the Grandmaster sync flow
– Limited to non-encrypted networks wRegenerates 1588 messages
– Switching scope violation concern?
• Correction field must be accurate
Residence Time =
Egress Time –Arrival Time

PTP PTP
Packet Packet Slave

Arrival Egress
Time Time

GMC

Transparent Clock Boundary Clock


17
SyncE and IEEE 1588‐2008 Summary
Attribute IEEE 1588 SyncE

Capability Frequency, Time Frequency

Layer UDP/IP or Layer 2 Physical

Distribution In-band 1588 Packets Physical layer

Schema Point to multi-point Point to point

Distribution In-band 1588 Packets Physical layer

Transport Media Native Ethernet, xDSL, Microwave Native Ethernet

Standards based Grandmaster &


Standard based SyncE
Inter-Operability slave. Independent of intermediate
switches only
nodes.

Relevant Standards IEEE 1588, ITU G.8261, G.8265.1 ITU G.8261/2/4

18
Updated Frequency Synchronization Architectures
(G.8261, G.803) 
Frequency Synchronization Architecture for SDH (TDM) 
network
G.803 Synchronization Reference Chain:

Chain of up to Chain of up to Chain of up to


PRC SSU 1 SSU k-1◊ SSU k◊ NE
20 SECs* 20 SECs* 20 SECs*

SSU

SDH CORE 
TDM
PRC

GPS TDM
TDM

SSU TDM

TDM

SSU
SSU
E1 ACCESS & DISTRIBUTION

20
Frequency Synchronization Architecture SDH & SyncE 
networks
G.803 Synchronization Reference Chain:

Chain of up to Chain of up to Chain of up to


PRC SSU 1 SSU k-1◊ SSU k◊ NE
20 SECs* 20 SECs* 20 SECs*

Modified Reference Chain to include Synchronous Ethernet Clocks (EEC):

Chain of up to Mixed Chain of up to Mixed Chain of up to


PRC SSU 1
20 EECs*
SSU k-1◊ 20 SECs*
SSU k◊ 20 SECs & EECs*
NE
Frequency Synchronization Architecture for SyncE 
network
Modified  G.803 Reference Chain to include Synchronous Ethernet Clocks (EEC):

Chain of up to Mixed Chain of up to Mixed Chain of up to


PRC SSU 1
20 EECs*
SSU k-1◊ 20 SECs*
SSU k◊ 20 SECs & EECs*
NE

Cesium

SyncE or
PTP
SSU SyncE

GPS

E1
SyncE

SyncE or
PTP
SSU
Frequency Synchronization Architecture 
Using PTP Packet Timing

M Packet Network S

Chain of up to Mixed Chain of up to PTP Master and Slave connected by


PRC SSU 1 SSU k-1◊ SSU k◊ NE
20 EECs* 20 SECs & EECs* packet network
* Maximum number of SECs or EECs in total chain = 60
◊ Maximum number of SSUs (k) in total chain = 10

Reference Reference Reference Reference


Point Point Point Point
A B C D

PEC- PEC-
M S-F

PRC Physical Layer Synchronization  Packet Network PTP Slave End


PTP GM
Network Equipment
Max # hops  PEC‐M to PEC‐S‐F = 10

Packet Timing System
Frequency Synchronization Architecture 
Using PTP Packet Timing 
Packet Timing System

PEC- PEC-
M S-F

PRC Physical Layer Synchronization  Packet Network PTP Slave End


PTP GM
Network Equipment
Max # hops  PEC‐M to PEC‐S‐F = 10

Cesium TP5000

PTP

PTP
SSU

GPS SyncE
E1

TP5000 PTP
PTP
SSU
Network Timing for Billing and Logging
NTP for Billing, Logging
For good NTP performance deploy NTP servers that meet stability requirements 
For good accuracy reduce the number of hops between the NTP server and the SNTP client to 
limit network jitter and asymmetric delays. 
For maximum NTP service availability, distribute NTP servers across the network. 

SSU2000 w/
NTP Blades

26
LTE‐A, LTE‐TDD Phase synchronizaiton
Phase Synchronization Using Edge BC and GM

CORE AGGREGATION ACCESS


Edge BC

PTP GM

Macro eNodeB
3rd Party tx

Edge Grand 
Master

Microwave
AG
PTP GM
Metro Small Cells

• Deploy PTP grandmaster or boundary clock at the edge to support 
LTE‐A Services
Mobile Synchronization Requirement & Standards 
update
Wireless Synch Requirements
G.811 Traceable Accuracy G.811 PRC with
Requires G.811 PRC G.811 PRC
+/‐ 5E‐8 Over a G.812 Holdover
Transport
ETSI TS 125 104 Circuit Switched Core Network

PSTN
MSC GMSC
UTRAN BSC

RNS BTS
NSS
G.811 Traceable 
G.812  Holdover Requires G.811 PRC
E/Net
ATM RNC
ETSI TS 125 402
IP
ATM
NodeB

RNS

ATM
E/Net RNC SGSN GGSN

NodeB
IP SERVICE
NETWORKS
+/‐ 50 ppb Macro/Microcell AGW
+/‐ 100 ppb (PicoCell)
ETSI TS 125 104 IP
XPORT
eNodeB
Relative Phase Difference
AGW LTE Access
Between two TTD (e)nodeB’s  
2.5uS Network
ETSI TS 125 402 Packet Switched Core Network
eNodeB
Wireless Synch Requirements
USER EQUIPMENT BASE STATION RADIO ACCESS BASE STATION MASTER PUBLIC
NETWORK CONTROLLERS CONTROLLERS SERVICE NETWORKS

G.811 Traceable
+/‐ 50ppb 
ETSI TS 125 104
PSTN

Microwave/ BSC MSC GMSC


BTS WiMAX
ITU‐T G.823 
+/‐ 50 ppb Macro/Microcell Compliant TDM
+/‐ 100 ppb (PicoCell)
3GPP  TDM/
ATM
IP Service
AIR INTERFACE

Network

Node RNC SGSN GGSN


B Ethernet
Node G.811 Traceable 
B G.812  Holdover
ETSI TS 125 402

OLT

250 ppb Accuracy AGW AGW


(NTP for Frequency  (LTE) (LTE)
recover) FemtoCell DSLAM

G.811 PRC for TDM  G.811 PRC for TDM 
Transport Transport

NTP Overlay for event recording/Call Data Records
Synchronization Requirements ‐ Standards

Frequency: 
Mobile Standard  Phase 
Transport  / Air Interface

GSM / UMTS / W‐CDMA  16 ppb    /    50 ppb
N/A
UMTS/ W‐CDMA Femtocells N/A  / 250 ppb

CDMA2000  16 ppb /    50 ppb  +/‐3 – 10 µs 

TD‐SCDMA 16 ppb   /    50 ppb  +/‐ 1.5 µs 

LTE (FDD)  16 ppb /    50 ppb  N/A 


LTE (TDD) 16 ppb /    50 ppb  +/‐ 1.5 µs  
LTE MBSFN  16 ppb /    50 ppb  +/‐ 1‐32 µs
LTE‐Advanced 16 ppb   /    50 ppb  +/‐ 0.5 µs
WiMAX (TDD)  16 ppb /    50 ppb  +/‐1 ‐ 8 µs
Structure of ITU‐T Recommendations
Definitions / G.8260: Definitions and Terminology for
Terminology Synchronization in Packet Networks

Frequency Time/Phase
Basic Aspects G.8261: Timing and Synchronization Aspects in Packet G.8271: Time and Phase Synchronization Aspects in
Networks (Frequency) Packet Networks

G.8261.1: PDV Network Limits Applicable to Packet- G.8271.1: Network Requirements for Time/Phase
Network Based Methods (Frequency)
Requirements G.8271.2: Network Requirements for Time/Phase
G.8261.2: Reserved for future use
Partial On Path Support

G.8262: Timing Characteristics of a Synchronous G.8272: PRTC (Primary Reference Time Clock)
Ethernet Equipment Slave Clock (EEC) Performance
G.8263: Timing Characteristics of Packet-Based G.8273: Packet-Based Equipment Clocks for
Equipment Clocks (PEC) Time/Phase: Framework
Clocks 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)

G.8264: Distribution of Timing Information through


G.8274: Reserved for future use
Packet Networks
Methods
G.8265: Architecture and Requirements for Packet- G.8275: Architecture and Requirements for
Based Frequency Delivery Packet-Based Time and Phase Delivery

G.8265.1: Precision Time Protocol Telecom G.8275.1: PTP Telecom Profile for Time and
Profile for Frequency Synchronization Phase Synchronization
Profiles
G.8275.2 PTP Telecom Profile for
G.8265.2 PTP Telecom Profile for Frequency #2
Time/Phase Partial On Path Support

agreed ongoing options


Thank You 
Q&A