Frequency and Time Synchronization in Packet Based Networks

Frequency and Time Synchronization in
Packet Based Networks

BRKAGG-3000
Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 1
Topic of This Session
Transmit high quality frequency and/or time reference from one or
multiple sources…
sources
… to distinct consumers (applications, users, systems) with

specific synchronization requirements thru Service Provider packet
networks.
BRKAGG-3000 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 2
Background Expectation
This session is an Introductory level session.

It is well suited for
Packet experts with slight or no timing expertise.
Timing experts with slight or no packet expertise.
Any person having both expertise is welcome even so ☺

To get news about what standardization organizations are doing.
What Will NOT Be Discussed
Products and implementations

Tests and performance results
Conventions
Slides marked with logo are for Information.

Acronyms are usually given at the bottom of the slide.
Acronyms
y are also listed in Index.
References to standards are given throughout the
presentation.
List of key references and access links are given at the
end of the presentation.
Housekeeping
We value your feedback- don't forget to complete your

online session evaluations (20 Passport points each!)
after each session & complete the Overall Conference
Evaluation which will be available online.
Visit the World of Solutions.
Please switch off your mobile phones.
Please be green and make use of the recycling bins
provided.
Please remember to wear your badge at all times
including the Party.
Agenda
Synchronization Problem Statement

Overview of the Standardization Works
q y Transfer: techniques
Frequency q and deployment
p y
Synchronous Ethernet
Adaptive Clock Recovery
Challenges of Precise Time/Phase Distribution

Two-Way Transfer Time Protocols
Overview of IEEE Std 1588-2008 for Telecom

p
Conclusion & Next steps
Problem Statement
What and Why Do We Care About?
Synchronization
Why and How are Packet Switched Networks Involved?
Transition from TDM to Ethernet networks.

Subscriber Access Connect consumers requiring Frequency
Mobile
TDM /
and/or Time (F&T) synchronization.
TV
ATM
PSN is built with network elements that
DVB-T/H
3GPP/2 May have to support F&T distribution
WiMAX
May be consumers of F&T
Mobile user
Aggregation Backbone Peer

Ethernet TDM /
Femto-cell ATM ISP
DSLAM
xDSL P P P
PE
PE P Internet
OLT PE
Hub & Spoke or Ring
xPON
Residential P MSE Mesh
SoHO MS
M-CMTS A Content Network
SI
DOCSIS VoD TV P
Enterprise
Synchronization Service
Subscriber Access
Single domain vs. multiple domains
Mobile
M bil
TV
TDM / I t
Internet
t is
i a multi-domain
lti d i network.
t k
ATM
Wholesale Ethernet virtual link
DVB-T/H
3GPP/2
Frequency and time could use different
distribution methods.
WiMAX
Operators may provide synchronization services
Mobile user
to their customers.
Aggregation Backbone
Ethernet Peer ISP
S
TDM /
ATM UTC
Femto-cell
PRC
DSLAM
P P P
xDSL
PE
PE P
OLT PE
Hub & Spoke or Ring
xPON
Residential
P
MSE Mesh
SoHO MS
M-CMTS A Content Network Internet
DOCSIS
Enterprise UTC VoD TV SIP
PRC
Key Consumers
Frequency
TDM interoperability and Co-existence: Circuit Emulation, TDM,
MSAN (MGW)
Access: Wireless Base Stations
Stations, PON
PON, DSL
Time and Phase alignment

Wireless Base Stations
SLA and Performance Measurements
BS : Base Station
PON : Passive Optical Network
DSL : Digital Subscriber Line
SLA : Service Level Agreement
Why Is Timing Important?
The Leading Requirements
Phase Alignment
Application Frequency
Time Synchronization
PRC traceability, jitter & wander
PRC-traceability,
TDM supportt ((e.g. CES
CES, SDH
limitations
transformation), Access
ITU-T G.8261/G.823/G.824/G.825
GSM, WCDMA
N/A (except for MBMS and SFN)
and LTE FDD
Phase alignment between base stations
UMTS TDD Frequency assignment (fractional must be < ±2.5µs
Mobile frequency accuracy) shall be better than
Base TD-SCDMA • ± 50ppb (macrocells)
must be < ±3µs
Stations • ± 100ppb (micro- & pico-cells)
• ± 250ppb
pp ((femtocells)) Time alignment error should be less than 3 μs
CDMA2K
and shall be less than 10 μs
LTE TDD
from ±0.5µs to ±50µs (service degradation)
WiMAX Mobile Shall be better than ± 15 ppb
must be < ±1µs
Cell synchronization accuracy for SFN support
DVB-S/H//T2 SFN TBD
must be < ± 3µs
Phase/time alignment between base stations
MB SFN Service
requirement can vary but in order of µs
To improve precision << 1 ms
One-way delay and jitter
for 10 to 100µs measurement accuracy
Performance Measurement
need ± 1 µs to ± 10µs ToD accuracy
GPS
Use of GPS (and GNSS alternatives)

raises some concerns:
Cost
Limited utilization
Locations
Regulatory & Politics
Reliability
Geography
V lnerabilit
Vulnerability
https://www.gsw2008.net/files/Civ%20Vulne
rabilities GSW2008 pdf
rabilities_GSW2008.pdf
GPS : Global Positioning System
746th Test Squadron GNSS : Global Navigation Satellite System
“GPS provides many benefits to civilian users.
It is vulnerable,
vulnerable however,
however to interference and
other disruptions that can have harmful
consequences. GPS users must ensure that
adequate independent backup systems or
procedures can be used when needed.”
GPS policy, applications, modernization, international cooperation February 01
Interagency GPS Executive Board
“The civil transportation infrastructure, seeking the
i
increasedd efficiency
ffi i maded possible
ibl b
by GPS
GPS, iis
developing a reliance on GPS that can lead to
serious consequences if the service is disrupted
disrupted,
and the applications are not prepared with
mitigating equipment and operational procedures.”
Vulnerability Assessment of the Transport Infrastructure Relying on GPS, Aug. 01
U.S. Department of Transportation
A Report Requires the Secretary of Transportation to:
“In
In coordination with the Secretary of Homeland Security, develop,
acquire, operate, and maintain backup position, navigation, and
timing capabilities that can support critical transportation,
homeland security, and other critical civil and commercial
infrastructure applications within the United States, in the event of
a disruption of the Global Positioning System or other space-
based positioning, navigation, and timing services…”
U.S. Space-Based Positioning, Navigation, and Timing Policy

Signed by the President of the United States on December 8, 2004, and published
December 1515, 2004
2004.
Alternative to GPS
As Replacement or Backup
Alternative Radio Navigation
LORAN-C ELORAN
Atomic Clock
Cheap Scale Atomic Clock
Molecular Clock
Network Clock
Main topic of this breakout session!
LORAN : LOng Range Aid to Navigation
Distribution in a PoP (e.g., Intra-CO)
Intra CO)
IP/MPLS
Central or Remote
Office
L1 / L2 L2/L3 Domain
PE-AGG N-PE P
N-PE
PE-AGG
MSE P
Synchronization
Equipment
Three Areas Of Study
External Integrated Time and
Frequency Server
Inter-CO/LAN (WAN)
Intra-CO, LAN
Intra-node, -platform
Standardization Development
Organizations
Who’s doing what?
SDO’s
SDO s Working Items
1. Frequency Distribution
Purpose: transition from TDM to Carrier Ethernet networks
TDM interoperability and co-existence: CES, Access, MSAN (MGW)
Target: High Quality Frequency: PRC-traceability
Mobile base stations
Target: Accuracy and stability of radio interface
2. Time Distribution
Purpose: get better result than with current NTP
Wi l
Wireless b
base stations:
t ti < 1 µs phase
h alignment
li t accuracy
Performance measurement: minimum 100 µs accuracy
Over constrained network (Service Provider domain)
Over Internet, over NGN CES : Circuit Emulation Service
MSAN: Multi Service Access Node
Technical Alternatives
Frequency transfer
Parallel (overlay) SDH/SONET network
Radio Navigation (e.g., GPS, LORAN)
PHY-layer mechanisms
Packet-based solutions
Time transfer
f (relative
( and absolute))
Radio Navigation (e.g., GPS, LORAN…)
P k tb
Packet-based
d solutions
l ti
Overview and Status of SDO Works
SDO Techno Status Scope Market
G.8261(2008)
G.8262(2007)+Amend.1 Service Provider
Synchronous PHY-layer
(SP) Metro & Core
Ethernet G.8264(2008) frequency transfer
Ethernet
ITU-T G.781 (2008)
SG15 Q13
G 8261 (2006)
G.8261 CES performance
Packet-based Multiple working Packet-based Service Provider
timing items: profile, metrics, frequency, phase (SP)
modeling… and time transfer
IEEE1588-2002 Enterprise: Time

Precise time SP: Frequency,
1588 PTP IEEE1588-2008
distribution phase and time
IEEE No “Telecom” profile ITU-T & IETF
Based on Precise time

802.1AS Ballot Residential
PTP distribution
NTPv3 Standard Internet
NTP NTP Time distribution
NTPv4: WIP ((CY08)) SP domain
IETF
NTPv5 New WG approved by Frequency and Internet
TICTOC
PTP Profile(s) March 08 time transfer Specific SP areas
IEEE1588-2008 and Telecom SDO’s
Relationships
ProfiNet: IEC 61158 Type10
DeviceNet: IEC 62026-3
ControlNet: IEC 61158 Type2
yp
IETF
IEC
NTP
Profiles
IEEE1588-
IETF 2008 IEEE
TICTOC ((PTPv2)) 802.1AS
AVB
Telecom
Profile(s)
Profile(s)
On-going
g g
ATIS ITU-T IEEE 802.3

Telcordia Q13/15 Timestamping
Frequency Transfer
Distribution of Frequency Reference
Frequency Transfer: The Two Options
Physical layer options

Ex: SONET/SDH, SDSL, GPON, Synchronous Ethernet
Pros: “carrier-class”, well defined, guaranteed results
Cons: node by node link bit timing, requires HW changes
Packet-based options
Ex: SAToP, CESoPSN, NTP, PTP (protocol of IEEE Std 1588)
Pros: flexible, looks simple, some can do time as well
C
Cons: th
the network
t k and
d th
the network
t k ttraffic,
ffi nott so simple!
i l !
Timing Network Engineering Principles
The task of network synchronization is to distribute the

reference signal from the PRC to all network elements
requiring synchronization.
The method used for propagating the reference signal
in the network is the master-slave method.
Slave clock must be slaved to clock of higher (or equal)
stability. hierarchical model
PRC : Primary Reference Clock
Source: ETSI EG 201 793 “Synchronization network engineering”

Hierarchical Physical Timing Distribution
PRS : Primary Reference Source

BITS : Building Integrated Timing System
Source: Telcordia GR-436-CORE “Digital Network Synchronization Plan”

Centralized Timing Network Architecture
PRC : Primary Reference Clock (≈ PRS)
SSU : Synchronization Supply Unit (≈ BITS)
SEC : SDH Equipment Clock
Core Network
Aggregation and
Access Networks

Distributed Timing Network Architecture
Receiver
R i ffor
synchronization
reference signal

Timing (Frequency) Architecture
Synchronization equipments
PRC (PRS) and SSU (BITS) do not belong to the Transport
network.
SEC (SDH/SONET Equipment Clock) belong to

Transport network.
They are embedded in Network Element : NE.
Network Synchronization Trail
Synchronization information is transmitted through the network via
synchronization network connections
connections.
Synchronization network connections are unidirectional and
generally point-to-multipoint.
Stratum 1 level
CO
Stratum 2 level
NE
(Stratum level ≥ 3)
CO Timing Distribution
NE’s
External NE’s
Timing External
Input Timing
g
a.k.a. Output
BITS IN
Figure 4-2. Recommended BITS Implementation with SONET Timing Distribution
Source: Telcordia GR-436-CORE . Digital Network Synchronization Plan

PHY-Layer
PHY Layer Transfer Summary
PRC/PRS
Intra-office
Intra- Inter-office
office Inter-office
SSU/BITS SSU/BITS
Intra-office
NE NE NE NE NE NE
PRS PRS
Intra
Intra- Inter-office Intra
Intra- Inter-office
office office
BITS BITS
Intra-office
NE NE NE NE NE NE
Network Synchronization Trail : SSM
What clock quality

do I get? Is that
Stratum 1 level the best source I
can use?
Stratum 2 level
NE level
Some of these synchronized trail contain a communication channel, the

Synchronization Status Message (SSM) transporting a quality identifier,
the QL (quality level) value.
This is a 4
4-bit
bit field in SDH/SONET frame overhead
overhead.
Purpose: Traceability (and help in prevention of timing loops)
Synchronization Connection Model
SSM Allows Source Traceability
Representation
p of the PRC
network connection
Fault Representation of the

synchronization network
connection in case of
f il
failure
X
Example of restoration
of the synchronization
PRC synchronization network connection

SEC synchronization network connection
SSU synchronization network connection
ITU-T
ITU T Synchronous Ethernet (SyncE)
PHY-layer frequency transfer solution for IEEE802.3 links
Analogy: licensed vs. unlicensed radio frequency
Well-known design rules and metrics
Best fit for operators running SONET/SDH
Fully specified at ITU-T Working Group 15 Question 13
For both 2.048 and 1.544 kbps
p hierarchies
Expected to be fundamental to high quality time transfer
Drawback : hardware upgrades
All timing chain shall be SyncE capable.
ITU-T
ITU T Synchronous Ethernet Support
PRC-traceable
signal from
ITU-T G.8262 (EEC): BITS/SSU
External Equipment Clock
Equipment
BITS/SSU) ITU-T G.781:
Clock Selection Process
External timing
interface outputs
External timing External timing

interface inputs interface inputs
IEEE802.3
± 100ppm
ITU-T G.8261
SyncE interface Frequency
jitter & wander distribution
traces
PLL Synchronous
Ethernet capable
Line Card
Synchronous ITU-T G.8264 capable Equipment
Ethernet capable ESMC and SSM-QL
Line Card
G.8264: ESMC
Ethernet Synchronization Messaging Channel
Use OSSP from IEEE802.3ay (a revision to IEEE Std 802.3-2005)
Key purpose: transmit SSM (QL)
Outcome: Simple and efficient
But designed to support extensions
Protocol model: Event-driven with TLVs
Two message types
Event message sent when QL value change
Information message sent every second
TLVs
QL-TLV is currently the unique defined TLV.
Other functions can be developed.
p
OSSP : Organization Specific Slow Protocol
G.8264: ESMC Format
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| Slow Protocols MAC Address |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| Slow Protocol MAC Addr (cont) | Source MAC Addr | IEEE 802.3
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| OSSP
| Source MAC Address (continued) |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
|
|Slow | Subtype (10) | ITU-OUI Oct 1 |
Protocols Ethertype 0x8809| ITU-T OUI
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| ITU-OUI Octets 2/3 (0x0019A7) | ITU Subtype (0x0001)* | Header
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| Vers. |C| Reserved | ESMC Header
|
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| |
| Type: 0x01 | Length | Resvd | QL | QL-TLV
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| Future TLV #n (extension TLV) |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| Future TLV
| | Extension
| Padding or Reserved |
| | Payload
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| FCS | OSSP
| + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
* Allocated by TSB
ITU-T SyncE: Summary
Assuring The Continuity at PHY Layer
BITS/SSU BITS/SSU
PRC/PRS BITS/SSU
SONET/SDH PHY SyncE PHY SyncE
ITU-T G.8262 ITU-T G.8262 ITU-T G.8262 ITU-T G.8262

(EEC) Node (EEC) Node (EEC) Node (EEC) Node
Extension or replacement of SDH/SONET synchronization chain

Inherit from previous ITU-T (and Telcordia) recommendations
Difference: frequency transfer path engineering will define the necessary
upgrades.
Only the NE part of the engineered timing chain needs SyncE upgrades.
Packet-Based
Packet Based Frequency Distribution
Reference
Recovered
Clock
Clock
PSN
Three key steps:

Generation: from signal to packet
Transfer: packet transmission over packet network(s)
Recovery: from packet to signal
CES Frequency Recovery : ACR Mode
Timing Transferred Along the CES Traffic (“in-band”)
( in band )
ATM or
Packet
Network
TDM Adaptive Clock Recovery TDM

and TDM bit stream
TDM PWS IWF TDM PWS IWF

ATM CES AAL1 ATM CES AAL1
Recovered TDM
TDM source timing based on
Clock Source the adaptive
Service Clock clock recovery
Note: In such mode, every

y individual TDM stream ((Circuit
Emulation Service or TDM PWS) requires its own clock recovery.
ACR Methods
ITU-T Recommendation G.8261 (2008) Adaptive Clock Recovery
Definition
“In this case the timing recovery process is based on the (inter-) arrival
time of the packets (e.g., timestamps or CES packets). The information
carried by the packets could be used to support this operation
operation. Two-way
Two way
or one-way protocols can be used.”
ACR Method One-Wayy Two-Wayy Timestamp

p
CES (SAToP, CESoPSN) X
IETF NTP (X) X X
IEEE Std 1588-2008 PTP X X X
IETF RTP X X X
Packet-Based
Packet Based Frequency Transfer
PSN
PEC PEC
Clock Source
Recovered frequency signal

from packet-based timing
distribution protocol (ACR)
PEC : Packet Equipment Clock
Packet-based Frequency Transfer and
CES
Independent Timing Stream
TDM PW bit stream

IWF IWF
TDM TDM
ACR Packet Stream Recovered TDM

Reference timing based on
Clock
the adaptive
Reference clock recovery
Clock
PEC
ACR Packet Stream
IWF IWF
TDM TDM PW bit stream &
& TDM
PEC PEC
Clocking method a.k.a. “out-of-band” (here, used for CES clocking)

Question
What does really count for a Service Provider?

Guaranteeing the quality of the timing service.
Stability and Accuracy
Source: Diagram from “Time Domain Representation of Oscillator Performance”,

Marc A. Weiss, Ph.D. NIST
Example: GSM Base Station
Frequency Accuracy
≤ ±50ppb at base station radio interface (specified)
Turns into ≤ ± 16ppb at base station traffic interface (not
specified*)
Frequency Stability
For T1, it shall comply to G.824 traffic mask (specification;
3GPP Rel8)
Sometimes* G.824 synchronization mask preferred
* Note: real requirements are variable as they are dependent on

base station clock servo.
Example: BS Requirements by MTIE
Frequency Accuracy
(Frequency Offset)
ITU T G.823
ITU-T G 823
Traffic Interface
(MRTIE mask)
ITU-T G.823
Synchronization
Interface (MTIE
mask)
Synchronization Measurements
Phase measurement
Measure signal under test against a reference signal
Phase deviation plot

TIE : Time Interval Error
Analysis
Step 1 : Phase Measurements
Ref.
Signal
+0.1 0
+0.1
-0.1 -0.2 -0.2
At a certain signal threshold, time stamp the edges of timing signal.

Signal edges are the significant instants.
PHY-layer signals have high frequency (e.g., 1544 kHz)
Step 2 : Phase Deviation
Phase deviation or TIE (Time Interval Error)
Step 3: Analysis
Analysis cover different aspects of the

Clock (oscillator)
e.g. in free-running or holdover mode
Signal
Primary used measurement analysis are:

Phase (TIE)
Frequency (fractional frequency offset)
Frequency accuracy
MTIE
TDEV
Analysis from Phase: Jitter & Wander
Signal with jitter and wander present
Analysis from Phase: Jitter
Jitter: Filter out low-frequency components with high-pass filter
10 Hz Jitter range Frequency
Analysis from Phase: Wander
Wander: Filter out high-frequency components with low-pass filter
Wander range 10 Hz Frequency
Key Stability Transfer Measures
Both MTIE and TDEV are measures of wander over

ranges of values.
From very short-term wander to long-term wander
MTIE and TDEV analysis shows comparison to

standard requirements.
Defined by ATIS/ANSI,
ATIS/ANSI Telcordia/Bellcore,
Telcordia/Bellcore ETSI & ITU-T
ITU T
E.g., ITU-T G.824, ANSI T1.101 or Telcordia GR-253-CORE
MTIE is a peak detector: simple peak-to-peak

peak to peak analysis.
TDEV is a highly averaged “rms”-type of calculation.
Ex: Wander Input Tolerance for DS1
“A stratum 3 clock in a SONET NE shall tolerate any arbitrary input

reference signal having wander TDEV characteristics less than or equal to
the input mask in Figure 5-15
5 15 (for an external DS1 reference).”
reference).
Source: GR-253-CORE (2005)

Ex: SONET Clock Wander Transfer
“R5-6 [61v2] When timed by any input signal whose TDEV is at or below the
wander tolerance mask in Figure 4-2, the TDEV of the output
signals
g shall be less than or equal
q to the corresponding
p g wander
transfer mask in Figure 5-6.”

Ex: Holdover Stability for Str3 Clocks
In the case of variable temperature holdover stability tests, this value

should be used only in calculating the fractional frequency offset limits
defined by the mask in Figure 5-2.
52

Ex: Wander Generation of SONET NE
Source : Telcordia GR-253-CORE /

5.4.4.3.2 Wander Generation
Wander generation is the process

whereby wander appears at the
output of a clock in the absence of
input wander.
wander
Ex: Wander Generation of EEC
EEC-Option
Option 2
Source : ITU-T
ITU T G.8262 (EEC)
Synchronous Ethernet Equipment Clock
Option 2 (1,544 kbps hierarchy)
Key Outcomes
Physical layer signals can be characterized.

Recommendations exist for node clock and interface
limits.
Synchronous Ethernet Equipment Clock (EEC) inherits
from SONET NE clock specifications.
The performance
Th f off SyncE-capable
S E bl NE and dSSyncE
E
interface are fully specified and metrics exist.
ITU-T
ITU T G.8261 CES Network Limits
Source : ITU-T G.8261 / 9.1 CES Network Limits

Wander Budget for 1544 kbps Signal for
G.8261 Deployment Case 1
The 1544 kbit/s jitter network limits shall comply with ITU-T Recommendation G.824 clause 5.1.
Monitoring ACR Performance
How to guarantee the packet-based recovered clock

quality?
OK
Reference Recovered
Clock DS1 Clock
DS1
PSN
Master/ Slave/
Server Client
?
Packet Delay Variation is key impairment factor for timing.

Timing Measurement with PSN
TIE is still a valid measurement for characterizing the

packet-based servo (slave).
Oscillators and timing interfaces
How can the PSN behavior be characterized?

Packet Delay Variation (PDV)
First approach
Fi h is
i to reuse known
k tools
l to PDV
analysis/measurement.
Some can be applied to PDV as to TIE
TIE.
Recall: Key Stability Transfer Measures
Both MTIE and TDEV are measures of wander over

ranges of values from very short-term wander to long-
term wander.
Packet flow rate vs
vs. physical rate : low & high frequency?
MTIE is a peak detector: simple peak-to-peak analysis

Packet PDV peaks to highest delay
delay.
TDEV is a highly averaged “rms”type of calculation:

statistical analysis for spectral content (energy) of
phase noise.
Average (mean) value over observation window
Performance Metrics
MTIE
Phase (Packet Delay vs. Time)
B i ffor allll calculations
Basis l l ti
MTIE (Maximum Time Interval Error)
Typically one dimensional for packet delay data
TDEV (Ti
(Time D
Deviation)
i ti )
Useful indicator of network traffic load
Phase
TDEV
Crossover Hub Switch Router
Semtech
Effect of Load on Packet Delay
minTDEV
10 Switches, 40% Load
10 Switches, 80% Load
Key Outcomes on Metrics
One metric would not be sufficient characterizing the

various possible conditions.
Reference Recovered
Cl k
Clock PSN Cl k
Clock
Master/
Server Classification
(metric)
Common, generic PSN
metrics for timing
gpperformance
characterization?
Today, very close relationship between metric (packet

classification) and implementation specific algorithm.
Monitoring ACR Performance
Even with (still to be agreed) metrics, other parameters will
remain
i critical.
iti l
Reference Recovered
Cl k
Clock PSN Metrics
Clock
PSN
Master/ Slave/
Client
Server ? ?
M t implementation
Master i l t ti Slave implementation
Protocol parameters
Evolution of : the PSN design,
the HW & SW NE configuration
the traffic.
ACR Technical Challenges – Summary
Application requirements
Client/Slave
Server/Master
Protocol and Protocol Configuration
C f
Network
Network Design (nodes and links)
Node design
Network Traffic
Engineering
Assessing & Monitoring
C i Cl
Carrier Class
Frequency Distribution Network Design
1. PHY-layer Synchronization Distribution guarantees the quality.
2. Packet-based Synchronization Distribution for flexibility.
3. Mixing the option for getting best of both solutions.
SyncE
consumer PHY-layer
Freq Transfer
SEC e.g. SyncE
PHY-layer
y PHY-layer method
EEC Freq Transfer e.g., SDH/SONET,
SDH/SONET SyncE
S E
e.g. SyncE
Packet-
based
consumer
EEC PHY-layer Freq

Consumer Transfer
PHY-layer Freq
Transfer
EEC
EEC
BITS/SSU
Non-capable PHY Layer Synchronization Network
Packet-based method (ACR) PRC/PRS
Thru BITS/SSU
Frequency Distribution Summary
ESMC &
Timing input SSM-QL
EEC Mediation function
Relevant ITU-T SyncE Line

Specifications Card
Compliancy
Timing output Packet-based

timing protocol
What about Time?
French scientist B. Gitton
Water Clock (1979)
Quiz
What is that? Precise marine clocks
Who built them? John Harrison (1693-1776)
Wh ?
Why? Longitude position
H4 (1755-1759)
H1 (1730-1735)
H2 & H3 (1737-1759)
The H4 watch's error was computed to be 39.2 seconds over a voyage of 47 days, three
times better than required to win the £20,000 longitude prize.
TWTT Protocols
What Specific Challenges
Does Time Distribution Introduce?
Time Synchronization
System A System B
timing signal recovered by system A

00:01:00 00:01:01 00:01:02
Ex.: UTC, UTC + n x hours

t GPS Time, Local arbitrary Time
ti i signal
timing i l recovered
d by
b system
t B
00:01:00 00:01:01 00:01:02
Figure xxx/G.8266 – Time Synchronization

t
Time synchronization is the distribution of a time reference, all the

associated
i t d nodes
d sharing
h i a common ti timescalel and
d related
l t d epoch.h
Absolute vs. Relative Time
Transmitting time reference can be absolute (from national
standards) or relative (bounded timekeeping system)
system).
Time synchronization
y is one wayy achieving
gpphase synchronization.
y
Phase alignment does not mandate giving a time value.
Phase Synchronization
This is not phase locking which is Reference timing signal
to system A System A
often a result of a PLL in a
physical timing transfer. Reference timing signal φB
to system B
Phase locking implies frequency System B
synchronization and allows phase
offset.
timing signal recovered by system A
The term phase synchronization
(or phase alignment) implies that
all associated nodes have access
t
to a reference timing signal whose timing signal recovered by system B
significant
g events occur at the
same instant (within the relevant
phase accuracy requirement).
t
Figure xxx/G.8266 – Phase Synchronization
Time Distribution for Mobile Wireless BS
Target from ±1µs to tens of µs (alignment between BS)
Target from ≤ ±0.5µs to tens of µs (from common reference)
Time Source
Accuracy, Stability and Precision
Syntonization and Synchronization
TWTT protocol client / slave has two processes:
The syntonization
The synchronization
Strictly speaking
speaking, the term synchronization applies to alignment
of time and the term syntonization applies to alignment of
frequency.
The master/server
Th t / andd slave/client
l / li t clocks
l k each hhhave th
their
i own
time-base and own wall-clock and the intent is to make the
slave/client “equal” to the master/server.
The notion
Th ti off frequency
f synchronization
h i ti ((or syntonization)
t i ti ) iis
making the time-bases “equal”, allowing a fixed (probably
unknown) offset in the wall-clocks. The notion of time
synchronization is making the wall-clocks “equal”
equal .
TWTT Protocols
NTP vs
vs. PTP Message Exchange
As part of time recovery, there’s always a frequency recovery process.
Master PTP Slave

time time
Timestamps
Usual unidirectional known by slave
ACR p protocol t
1
Sync
t-ms
t2 t2
Follow_Up
t1, t2
t3 t1, t2, t3
Delay_Req
t-sm
t4
NTP
Delay_Resp
t1, t2, t3, t4
TWTT Protocol Basics
Basic NTP Message Exchange
SERVER CLIENT
Server time = Ts Client time = Tc = Ts + offset
“Real” T2 = T1 + “Real” Delay

Offset = ((T2 - T1) - (T4 - T3))/2
But… Delay = ((T2 - T1)+(T4 - T3))/2
Timestamps
known
by client
Time_REQ
T1
T1
T CS
T2
Time_RESP
T3
T SC
T1, T2, T3, T4
T4
Assumption := symmetry!
TWTT Protocol Basics
Basic PTP Message Exchange
MASTER SLAVE
Master time = TM Slave time = TS = TM + offset
Offset = TS - TM
Ti
Timestamps
t
known by
SYNC
Offset + Delay = A = t2 – t1 slave
Delay t1
t2 t1, t2
Delay - Offset = B = t4 – t3 t2 = t1 + Offset + Delay
t3
t1, t2, t3
Delay_Req
Delay
t4 t4 = t3 - Offset + Delay
Delay_Resp
t1, t2, t3, t4
Delay = ((t2 – t1)+(t4 – t3))/2 Offset = ((t2 – t1)–(t4 – t3))/2

Asymmetry
Forward and backward delays are not identical.
Asymmetry: A Closer Look
Each Node and Link can introduce asymmetry.
Th
There are various
i sources off asymmetry.
t
Sources of Asymmetry
Link
Link delays and asymmetry
Asymmetric (upstream/downstream) link techniques
Physical layer clock
Node
Different link speed (forward / reverse)
Node design
LC design
E bl d ffeatures
Enabled t
Network
Traffic p
path inconsistency
y
Interface speed change
TWTT: Summary of Sources of Error
frequency
Asymmetry: introduce a mean time-error. time
Also transit delay variation (a.k.a. PDV or packet jitter):
The standard deviation of the time-base and time-error error will
increase with increasing
g time-delayy variation in the p
path(s)
( ) between
master and slave.
Inaccuracy of the slave time-base
Any frequency offset and/or frequency drift will color the measurements
measurements.
The standard deviation of the time-base and time-error error will
decrease with increasing rate of packet exchange between master
and slave.
slave
Increasing the averaging time does reduce the standard deviation
of the time-base and time-error error.
Provided the quality of the oscillator is commensurate with the (long)
time constant!
Two Way Time Transfer Protocols
Summary and Introduction to IEEE Std 1588
Basis of all packet time transfer protocols (NTP,

IEEE1588) is the two way time transfer mechanism.
TWTT consists of a time transfer mechanism and a
time delay “radar”
radar .
Assumes path symmetry and path consistency.
IEEE1588 iincorporates
t some iin-network
t k correction
ti
mechanisms to improve the quality of the transfer.
IEEE1588 has the concept of asymmetry correction
correction.
But the correction values are not dynamically measured - they
need to be statically configured.
IEEE Std 1588-2008 for Telecom
Challenges of IEEE 1588-2008 applied
in Service Provider networks
“This standard specifies:
a) The Precision Time Protocol, and
b) The node, system, and communication properties
necessary to support PTP
PTP. “
IEEE Std 1588-2008
PTP Version 2
A set of event messages A set of general messages
consisting of: consisting of:
- Sync - Follow_Up
- Delay_Req - Delay_Resp
- Pdelay_Req - Pdelay_Resp_Follow_Up
- Pdelay_Resp - Announce
- Management
M
- Signaling
Transmission modes: either unicast or multicast (can be mixed)

Encapsulations: L2 Ethernet, IPv4, IPv6 (others possible)
Multiple possible values or range of values
values, TLVs (possible
extensions), …
PTP Device Types
Five basic types of PTP devices (“clocks”)
Ordinary clock (master or slave)
Boundary clock (“master and slave”)
End-to-end Transparent clock
Peer-to-peer Transparent clock
Management node
All five types implement one or more aspects of the PTP protocol.
OC Master, BC and TC running either in one-step or two-step
clock mode
mode.
One-step mode breaks IEEE/OSI/IETF/ITU layers.
Basic PTP Message Exchange
MASTER SLAVE
Master time = TM Slave time = TS
Timestamps
t1 SYNC known by
MS_Delay
slave
t2
t1, t2
t3
t 1 , t2 , t3
Delay_Req
SM Delay
SM_Delay
t4
Delay_Resp
t 1 , t2 , t3 , t4
Quality of the Timestamp
MASTER SLAVE
µP MAC/PHY MAC/PHY µP
t1
Timestamps
SYNC
Need to inject the known by
t1 slave
timestamp into the
payload at the t2
t2
time the packet t 1 , t2
gets out.
t3
t3 t 1 , t2 , t3
Delay_REQ
t4
t4
Delay_RESP
y_
t1, t2, t3, t4
Hardware assistance necessary to prevent insertion of errors or inaccuracies.

Follow Up
Follow_Up
MASTER SLAVE
µP MAC/PHY MAC/PHY µP
t1
SYNC() Timestamps
known by
t2 slave
Follow_Up(t1)
Two-step clock t2
mode
Vs. t 1 , t2
One-step (a.k.a.
“on-the-fly”) t3 t 1 , t2 , t3
clock mode Delay_REQ()
t4
Delay
y_RESP(t
( 4)
t 1 , t2 , t3 , t4
Timestamp Generation Model
Need to timestamp timing packet from timestamp point.

Timestamp point shall be identical at ingress and egress.
Location is not so important if consistent.
Need to classify a packet as timing packet.
Telecom Timestamp Generation Issues
If IEEE 1588-2008 is not planned node to node, with
every node IEEE 1588 aware and in unique
domain…
Multiple
p interface types
yp
IEEE 802.3, ITU-T G.709, …
Multiple interface frequencies
10GE, 100GE, STM64, STM192…
Multiple encapsulations
Ethernet, IP
MPLS, MPLS-TP, PBT…
IEEE Std 1588-2008
1588 2008 Clocks
BC and TC aims correcting delay variation into intermediate nodes
between OCs
OCs.
Can correct link asymmetry if known.
Ordinary Ordinary
Slave Master Ref.
Clock
Recovered
Clock
TC BC
Transparent Boundary
Clock Clock
IEEE Std 1588-2008
1588 2008 BC
Equivalent to NTP Stratum (>1) Server
Can help on scalability when using unicast.
Issue: time dispersion? BC slave function is critical.
Ordinary
Ordinar Ordinary
O di
Slave Master Ref.
Clock
Recovered
Clock
BC BC
Boundary Boundary
Clock Clock
IEEE Std 1588-2008
1588 2008 TC
TC calculates Residence Time (forward / reverse intra node
delays).
delays)
TC are supposed to be transparent but:
One-step
p clock issue
Path consistency
Ordinary
Ordinar Ordinary
O di
Slave Master Ref.
Clock
Recovered
Clock
TC TC
Transparent Transparent
Clock Clock
IEEE1588-2008 Transparent Clocks
Residence Time and Correction Field
Message at ingress Message at egress
Event message payload Network PTP message payload Network

protocol Preamble protocol Preamble
Correction Correction
headers headers
field field
+
+
Ingress timestamp -+ Egress timestamp
Ingress Residence time bridge Egress
About Telecom Profiles
Telecom profiles will require matching the consumer requirements to the
network design and behavior
behavior.
It will involves a set of IEEE Std 1588-2008 parameters as such as
Messages
Options and TLVs
Mode of transmission
Values (e.g., message rates)
Specification of new timestamp points (telecom encapsulation)
But Service Providers will also need
Metrics
Node characterization
New Node modeling (IEEE Std 1588-2008 document includes some sort of clock
modeling)
Support of new routing functions (e.g. traffic engineering)
…
Monitoring the Performance
How to guarantee the recovered clock quality?
Slave/ Master/
Client ? ? Ref.
Server
Clock
Recovered
Clock PSN
TC BC
? ?
?
IEEE 1588-2008
1588 2008 (PTPv2) In A Nutshell
IEEE Std 1588-2008 is actually a “toolbox”.
The protocol can use various encapsulations, transmission modes,
messages, parameters and parameter values…
Multiple “Clocks”
Clocks are defined: OC (slave/master)
(slave/master), BC
BC, TC P2P
P2P, TC
E2E, with specific functions and possible implementations.
IEEE 1588-2008 added the concept of PTP profile.
Moreover, IEEE1588 recommendations are not sufficient for
telecom operator operations.
Node characterization, interoperability, performance and metrics…
What does “support of IEEE 1588” mean ?
Time Distribution
TWTT Technical Challenges – Summary
path symmetry Application requirements
path consistency Client/Slave

Server/Master
hardware assistance
IEEE 1588-2008
1 88 2008 Boundary &
Transparent Clocks
Protocol and Protocol Configuration
Network
Design, Traffic, Nodes
Node design includes BC & TC
Engineering
Time To Conclude
Challenges for Sync Architectures
Timing is a new service many networks shall have to support.
Different solutions are necessary to cover disparate requirements,
network designs and conditions.
Physical
y layer
y solutions required
q to upgrade
pg routers and switches.
Packet-based solutions are more flexible but less deterministic.
Whatever the timing protocol, it must deal with the same network
constraints.
t i t
How can the network better support timing service?
Hardware upgrade?
Software functions?
Metrics and characterizations?
Conclusion
Technical alternatives are known.
Their pros & cons are also known.
Nothing prevents using packet-based solutions.
But packet-based solutions need further
f work.
Timing network engineering
Rules
Experience
Monitoring
Challenges
Cost-efficiency : TCO considerations
M lti d
Multi-domain
i ttransfer
f
Next Steps
Frequency transfer can be achieved.

Time transfer needs to be improved.
Sub-millisecond is a reachable target.
Sub-microsecond objective is challenging.
Next Steps
Network element functions and metrics
Protocol “profile”
Architecture
Combining packet-based timing protocol functions with routing
capabilities
p
Some References
ITU-T* : http://www.itu.int/rec/T-REC-G/e
G.803, G.823, G.8261, G.8262, G.8264, G.781
Telcordia : http://telecom-info.telcordia.com/site-cgi/ido/index.html
GR-253-CORE, GR-1244-CORE, GR-436-CORE
ETSI : http://pda.etsi.org/pda/queryform.asp
eg_201 793-010101 (2000) Synchronization network engineering
IEEE Std 1588-2008
1588 2008
http://www.ieee.org/web/publications/standards/index.html
IETF**
NTP : http://www.ietf.org/html.charters/ntp-charter.html
TICTOC : http://www.ietf.org/html.charters/tictoc-charter.html
*Free for enforced recommendations

**Free
Please Visit the Cisco Booth in the
World of Solutions
See the technology in action
Mobility
MOB1 – Collaboration in Motion
MOB2 – Cisco Unified Wireless Network
MOB3 – Mobile High-Speed
g p Performance
with 802.11n
Complete Your Online
Session Evaluation
Give us your feedback and you
could win fabulous prizes
prizes.
Winners announced daily.
Receive 20 Passport points for
each session evaluation you
complete.
Complete your session evaluation
online now ((open a browser
through our wireless network to
access our portal) or visit one of
the Internet stations throughout
the Convention Center.
Don’t forget
f to activate your
Cisco Live Virtual account for access to
all session material, communities, and
on-demand and live activities throughout
the
h year. AActivate
i your account at the
h
Cisco booth in the World of Solutions or visit
www.ciscolive.com.
Appendix
Acronyms
Acronyms
ACR : Adaptive Clock Recovery OLT : Optical Line Terminal (PON)
AVB : Audio Video Bridging OSSP : Organization Specific Slow Protocol
BITS : Building Integrated Timing System PDV : Packet Delay Variation
BS : Base Station PON : Passive Optical Network
CDMA : Code Division Multiple Access PPS : Pulse Per Second
CES : Circuit Emulation Service PRC : Primary Reference Clock
DSL : Digital Subscriber Line PRS : Primary Reference Source
DTI : DOCSIS Timing Interface PSN : Packet Switched Network
DVB : Digital Video Broadcast PTP : Precision Time Protocol
DVB-T/H : DVB Terrestrial / Handheld QL : Quality Level
ESMC : Ethernet Synchronization Messaging Channel SDO : Standardization Development Organizations
FDD : Frequency Division Duplexing SDSL : Symmetric Digital Subscriber Line
GNSS : Global Navigation Satellite System SEC : SDH Equipment Clock
GPS : Global Positioning System SFN : Single Frequency Network
GSM : Global System for Mobile communications SLA : Service Level Agreement
IPDV : Inter-Packet Delay Variation SP : Service Provider
IRIG : Inter Range Instrumentation Group SSM : Synchronization Status Message
LORAN : LOng Range Aid to Navigation SSU : Synchronization Supply Unit
LTE : Long Term Evolution SyncE : ITU-T Synchronous Ethernet
MAFE : Maximum Averaged Frequency Error TDD : Time Division Duplexing
MATIE : Maximum Averaged Time Interval Error TDEV : Time DEViation
MB(M)S : Multicast Broadcast (Multimedia) Services TDM : Time Division Multiplexing
MBSFN : Multicast Broadcast Single Frequency Network TD-SCDMA : Time Division – Synchronous CDMA
M-CMTS : Modular Cable Modem Termination System TIE : Time Interval Error
MSAN : Multi Service Access Node TWTT : Two Way Time Transfer (protocol)
MRTIE : Maximum Relative Time Interval Error UTC : Coordinated Universal Time
MTIE : Maximum Time Interval Error UTMS : Universal Mobile Telecommunications System
NGN : Next Generation Network WCDMA : Wideband CDMA
NTP : Network Time Protocol WIP : Work In Progress

Frequency and Time Synchronization in Packet Based Networks

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Frequency and Time Synchronization in Packet Based Networks

Hochgeladen von

Copyright:

Verfügbare Formate

Frequency and Time Synchronization in

Packet Based Networks

… to distinct consumers (applications, users, systems) with

This session is an Introductory level session.

Any person having both expertise is welcome even so ☺

Products and implementations

Slides marked with logo are for Information.

We value your feedback- don't forget to complete your

Synchronization Problem Statement

Challenges of Precise Time/Phase Distribution

Overview of IEEE Std 1588-2008 for Telecom

Transition from TDM to Ethernet networks.

Aggregation Backbone Peer

Time and Phase alignment

Use of GPS (and GNSS alternatives)

U.S. Space-Based Positioning, Navigation, and Timing Policy

LORAN : LOng Range Aid to Navigation

IEEE1588-2002 Enterprise: Time

Based on Precise time

ATIS ITU-T IEEE 802.3

Physical layer options

The task of network synchronization is to distribute the

PRC : Primary Reference Clock

Source: ETSI EG 201 793 “Synchronization network engineering”

PRS : Primary Reference Source

Source: Telcordia GR-436-CORE “Digital Network Synchronization Plan”

Source: ETSI EG 201 793 “Synchronization network engineering”

Source: ETSI EG 201 793 “Synchronization network engineering”

SEC (SDH/SONET Equipment Clock) belong to

Figure 4-2. Recommended BITS Implementation with SONET Timing Distribution

Source: Telcordia GR-436-CORE . Digital Network Synchronization Plan

What clock quality

Some of these synchronized trail contain a communication channel, the

Fault Representation of the

PRC synchronization network connection

External timing External timing

SONET/SDH PHY SyncE PHY SyncE

ITU-T G.8262 ITU-T G.8262 ITU-T G.8262 ITU-T G.8262

Extension or replacement of SDH/SONET synchronization chain

Three key steps:

TDM Adaptive Clock Recovery TDM

TDM PWS IWF TDM PWS IWF

Note: In such mode, every

ACR Method One-Wayy Two-Wayy Timestamp

CES (SAToP, CESoPSN) X

IETF NTP (X) X X

IEEE Std 1588-2008 PTP X X X

Recovered frequency signal

PEC : Packet Equipment Clock

TDM PW bit stream

ACR Packet Stream Recovered TDM

Clocking method a.k.a. “out-of-band” (here, used for CES clocking)

What does really count for a Service Provider?

Source: Diagram from “Time Domain Representation of Oscillator Performance”,

* Note: real requirements are variable as they are dependent on

Phase deviation plot

At a certain signal threshold, time stamp the edges of timing signal.

Phase deviation or TIE (Time Interval Error)

Analysis cover different aspects of the

Primary used measurement analysis are:

Both MTIE and TDEV are measures of wander over

MTIE and TDEV analysis shows comparison to

MTIE is a peak detector: simple peak-to-peak