Brkagg-3000 c1 Rev1

2009 Cisco Systems, Inc. All rights reserved.
Cisco Public Presentation_ID 1

Frequency and Time Synchronization in
Packet Based Networks
BRKAGG-3000
2009 Cisco Systems, Inc. All rights reserved. Cisco Public BRKAGG-3000 2
Topic of This Session
Transmit high quality frequency and/or time reference from one or
multiple sources
to distinct consumers (applications, users, systems) with
specific synchronization requirements thru Service Provider packet
networks.
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 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
Frequency Transfer: techniques and deployment
Synchronous Ethernet
Adaptive Clock Recovery
Challenges of Precise Time/Phase Distribution
Two-Way Transfer Time Protocols
Overview of IEEE Std 1588-2008 for Telecom
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.
Connect consumers requiring Frequency
and/or Time (F&T) synchronization.
PSN is built with network elements that
May have to support F&T distribution
May be consumers of F&T
Aggregation
Subscriber
Access
MSE
TDM /
ATM
Ethernet
WiMAX
OLT
xPON
xDSL
DSLAM
M-CMTS
DVB-T/H
3GPP/2
DOCSIS
Backbone
Hub & Spoke or Ring
P
P Internet
PE
PE
MS
A
PE
Peer
ISP
Mesh
P
TDM /
ATM
P P
VoD
Content Network
TV
SI
P
Mobile user
Femto-cell
Mobile
TV
Enterprise
Residential
SoHO
Synchronization Service
Single domain vs. multiple domains
Internet is a multi-domain network.
Wholesale Ethernet virtual link
Frequency and time could use different
distribution methods.
Operators may provide synchronization services
to their customers.
Aggregation
Subscriber
Access
MSE
TDM /
ATM
Ethernet
WiMAX
OLT
xPON
xDSL
DSLAM
M-CMTS
DVB-T/H
3GPP/2
DOCSIS
Backbone
Hub & Spoke or Ring
P
P
Internet
PE
PE
MS
A
PE
Peer ISP
Mesh
P
TDM /
ATM
P P
VoD
Content Network
TV SIP
Mobile user
Femto-cell
Mobile
TV
Enterprise
Residential
SoHO
Key Consumers
Frequency
TDM interoperability and Co-existence: Circuit Emulation, TDM,
MSAN (MGW)
Access: Wireless Base Stations, 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
Application Frequency
Phase Alignment
Time Synchronization
TDM support (e.g. CES, SDH
transformation), Access
PRC-traceability, jitter & wander
limitations
ITU-T G.8261/G.823/G.824/G.825
Mobile
Base
Stations
GSM, WCDMA
and LTE FDD
Frequency assignment (fractional
frequency accuracy) shall be better than
50ppb(macrocells)
100ppb (micro- & pico-cells)
250ppb (femtocells)
N/A (except for MBMS and SFN)
UMTS TDD
Phase alignment between base stations
must be < 2.5s
TD-SCDMA
must be < 3s
CDMA2K
Time alignment error should be less than 3 s
and shall be less than 10 s
LTE TDD
from 0.5s to 50s (service degradation)
WiMAX Mobile Shall be better than 15 ppb
must be < 1s
DVB-S/H/T2 SFN TBD
Cell synchronization accuracy for SFN support
must be < 3s
MB SFN Service
Phase/time alignment between base stations
requirement can vary but in order of s
One-way delay and jitter
Performance Measurement
To improve precision << 1 ms
for 10 to 100s measurement accuracy
need 1 s to 10s ToD accuracy
GPS
Cost
Limited utilization
Locations
Regulatory & Politics
Reliability
Geography
Vulnerability
https://www.gsw2008.net/files/Civ%20Vulne
rabilities_GSW2008.pdf
746th Test Squadron
Use of GPS (and GNSS alternatives)
raises some concerns:
GPS : Global Positioning System
GNSS : Global Navigation Satellite System
GPS provides many benefits to civilian users.
It is vulnerable, 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
increased efficiency made possible by GPS, is
developing a reliance on GPS that can lead to
serious consequences if the service is 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
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 15, 2004.
A Report Requires the Secretary of Transportation to:
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)
IP/MPLS
Central or Remote
Office
MSE
L1 / L2 L2/L3 Domain
PE-AGG
PE-AGG
N-PE
N-PE
P
P
Synchronization
Equipment
Three Areas Of Study
Inter-CO/LAN (WAN)
Intra-CO, LAN
Intra-node, -platform
External Integrated Time and
Frequency Server
Standardization Development
Organizations
Whos doing what?
SDOs 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
Wireless base stations: < 1 s phase alignment 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 (relative and absolute)
Radio Navigation (e.g., GPS, LORAN)
Packet-based solutions
Overview and Status of SDO Works
SDO Techno Status Scope Market
ITU-T
SG15 Q13
Synchronous
Ethernet
G.8261(2008)
G.8262(2007)+Amend.1
G.8264(2008)
G.781 (2008)
PHY-layer
frequency transfer
Service Provider
(SP) Metro & Core
Ethernet
Packet-based
timing
G.8261 (2006)
Multiple working
items: profile, metrics,
modeling
CES performance
Packet-based
frequency, phase
and time transfer
Service Provider
(SP)
IEEE
1588 PTP
IEEE1588-2002
IEEE1588-2008
No Telecom profile
Precise time
distribution
Enterprise: Time
SP: Frequency,
phase and time
ITU-T & IETF
802.1AS
Based on
PTP
Ballot
Precise time
distribution
Residential
IETF
NTP NTP
NTPv3 Standard
NTPv4 (CY09)
Time distribution
Internet
SP domain
TICTOC
NTPv5
PTP Profile(s)
New WG
(approved March 08)
Frequency and
time transfer
Internet
Specific SP areas
IEEE1588-2008 and Telecom SDOs
Relationships
IETF
TICTOC
ITU-T
Q13/15
IEEE1588-
2008
(PTPv2)
IEEE
802.1AS
IETF
NTP
AVB
Profile(s)
ATIS
Telcordia
ProfiNet: IEC 61158 Type10
DeviceNet: IEC 62026-3
ControlNet: IEC 61158 Type2
IEC
Profiles
Telecom
Profile(s)
On-going
IEEE 802.3
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
Cons: the network and the network traffic, not so simple!
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
Core Network
Aggregation and
Access Networks
PRC : Primary Reference Clock ( PRS)
SSU : Synchronization Supply Unit ( BITS)
SEC : SDH Equipment Clock
Distributed Timing Network Architecture
Receiver for
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.
Synchronization network connections are unidirectional and
generally point-to-multipoint.
Stratum 1 level
Stratum 2 level
NE
(Stratum level 3)
CO
CO Timing Distribution
Figure 4-2. Recommended BITS Implementation with SONET Timing Distribution
NEs
External
Timing
Output
NEs
External
Timing
Input
a.k.a.
BITS IN
Source: Telcordia GR-436-CORE . Digital Network Synchronization Plan
PHY-Layer Transfer Summary
SSU/BITS
NE
PRC/PRS
SSU/BITS
NE NE NE NE NE
Intra-
office
Intra-office
Intra-office
Inter-office
Inter-office
BITS
NE
PRS
BITS
NE NE NE
PRS
Intra-
office
Intra-
office
NE NE
Inter-office
Intra-office
Inter-office
Network Synchronization Trail : SSM
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-bit field in SDH/SONET frame overhead.
Purpose: Traceability (and help in prevention of timing loops)
Stratum 1 level
Stratum 2 level
NE level
What clock quality
do I get? Is that
the best source I
can use?
Synchronization Connection Model
SSM Allows Source Traceability
PRC synchronization network connection
SSU synchronization network connection
SEC synchronization network connection
Representation of the PRC
network connection
X
Fault
Representation of the
synchronization network
connection in case of
failure
Example of restoration
of the synchronization
ITU-T Synchronous Ethernet (SyncE)
PHY-layer frequency transfer solution for IEEE802.3 links
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 hierarchies
Expected to be fundamental to high quality time transfer
Drawback : hardware upgrades
All timing chain shall be SyncE capable.
ITU-T Synchronous Ethernet Support
PLL
Synchronous
Ethernet capable
Line Card
IEEE802.3
100ppm
ITU-T G.8261
SyncE interface
jitter & wander
ITU-T G.8262 (EEC):
Equipment Clock
ITU-T G.781:
Clock Selection Process
Synchronous
Ethernet capable
Line Card
Frequency
distribution
traces
External timing
interface inputs
External
Equipment
BITS/SSU)
External timing
interface inputs
PRC-traceable
signal from
BITS/SSU
ITU-T G.8264
ESMC and SSM-QL
External timing
interface outputs
capable Equipment
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.
OSSP : Organization Specific Slow Protocol
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 |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| Source MAC Address (continued) |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
|Slow Protocols Ethertype 0x8809| Subtype (10) | ITU-OUI Oct 1 |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| ITU-OUI Octets 2/3 (0x0019A7) | ITU Subtype (0x0001)* |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| Vers. |C| Reserved |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| Type: 0x01 | Length | Resvd | QL |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| Future TLV #n (extension TLV) |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| |
| Padding or Reserved |
| |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| FCS |
|-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
G.8264: ESMC Format
* Allocated by TSB
IEEE 802.3
OSSP
ITU-T OUI
Header
ESMC Header
QL-TLV
Future TLV
Extension
Payload
OSSP
ITU-T SyncE: Summary
Assuring The Continuity at PHY Layer
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.
ITU-T G.8262
(EEC) Node
BITS/SSU
SONET/SDH PHY SyncE
BITS/SSU
PRC/PRS
BITS/SSU
PHY SyncE
ITU-T G.8262
(EEC) Node
ITU-T G.8262
(EEC) Node
ITU-T G.8262
(EEC) Node
Packet-Based Frequency Distribution
Three key steps:
Generation: from signal to packet
Transfer: packet transmission over packet network(s)
Recovery: from packet to signal
Reference
Clock
Recovered
Clock
PSN
CES Frequency Recovery : ACR Mode
Timing Transferred Along the CES Traffic (in-band)
Note: In such mode, every individual TDM stream (Circuit
Emulation Service or TDM PWS) requires its own clock recovery.
TDM
TDM
ATM or
Packet
Network
TDM source
Clock Source
Service Clock
Recovered TDM
timing based on
the adaptive
clock recovery
Adaptive Clock Recovery
and TDM bit stream
TDM PWS IWF
ATM CES AAL1
TDM PWS IWF
ATM CES AAL1
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. Two-way
or one-way protocols can be used.
ACR Protocol / Method One-Way Two-Way Timestamp
CES (SAToP, CESoPSN) X
IETF NTP (X) X X
IEEE Std 1588-2008 PTP X X X
IETF RTP X X X
Packet-Based Frequency Transfer
PEC : Packet Equipment Clock
PSN
Clock Source
Recovered frequency signal
from packet-based timing
distribution protocol (ACR)
PEC
PEC
Packet-based Frequency Transfer and
CES
Independent Timing Stream
TDM TDM
IWF IWF
Recovered TDM
timing based on
the adaptive
clock recovery
ACR Packet Stream
Reference
Clock
TDM PW bit stream
Clocking method a.k.a. out-of-band (here, used for CES clocking)
TDM
TDM
IWF
&
PEC
IWF
&
PEC
ACR Packet Stream
TDM PW bit stream
PEC
Reference
Clock
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
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
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)
O O O O O O O
-0.1 -0.2
+0.1
-0.2
+0.1
O O O O O O O
Signal
Ref.
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
Frequency Jitter range 10 Hz
Analysis from Phase: Wander
Wander: Filter out high-frequency components with low-pass filter
Frequency Wander range 10 Hz
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, Telcordia/Bellcore, ETSI & 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 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 (for an external DS1 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 shall be less than or equal to the corresponding 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.
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.
Ex: Wander Generation of EEC-Option 2
Source : 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 of SyncE-capable NE and SyncE
interface are fully specified and metrics exist.
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?
PSN
Reference
Clock
Recovered
Clock
Slave/
Client
Master/
Server
?
OK
Packet Delay Variation is key impairment factor for timing.
DS1
DS1
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 is to reuse known tools to PDV
analysis/measurement.
Some can be applied to PDV as to 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. physical rate : low & high frequency?
MTIE is a peak detector: simple peak-to-peak analysis
Packet PDV peaks to highest delay.
TDEV is a highly averaged rmstype of calculation:
statistical analysis for spectral content (energy) of
phase noise.
Average (mean) value over observation window
Performance Metrics
Phase (Packet Delay vs. Time)
Basis for all calculations
MTIE (Maximum Time Interval Error)
Typically one dimensional for packet delay data
TDEV (Time Deviation)
Useful indicator of network traffic load
MTIE
TDEV
Crossover Hub Switch Router
Phase
Semtech
10 Switches, 40% Load
10 Switches, 80% Load
minTDEV
Effect of Load on Packet Delay
Key Outcomes on Metrics
One metric would not be sufficient characterizing the
various possible conditions.
Reference
Clock
Recovered
Clock
Classification
(metric)
Master/
Server
PSN
Common, generic PSN
metrics for timing performance
characterization?
Today, very close relationship between metric (packet
classification) and implementation specific algorithm.
Monitoring ACR Performance
Protocol parameters
Evolution of : the PSN design,
the HW & SW NE configuration
the traffic.
Master implementation
PSN
Reference
Clock
Recovered
Clock
Slave/
Client
Master/
Server
PSN Metrics
?
?
Slave implementation
Even with (still to be agreed) metrics, other parameters will
remain critical.
ACR Technical Challenges Summary
Application requirements
Client/Slave
Server/Master
Protocol and Protocol Configuration
Network
Network Design (nodes and links)
Node design
Network Traffic
Engineering
Assessing & Monitoring
Carrier Class
Frequency Distribution Network Design
1. PHY-layer Synchronization Distribution guarantees the quality.
2. Packet-based Synchronization Distribution provides the flexibility.
3. Mixing the option for getting best of both solutions.
BITS/SSU
PRC/PRS
Thru BITS/SSU
EEC
EEC
EEC
EEC
Consumer
Non-capable PHY Layer Synchronization Network
SEC
PHY-layer method
e.g., SDH/SONET, SyncE
Packet-based method (ACR)
PHY-layer Freq
Transfer
O
O
O
PHY-layer Freq
Transfer
PHY-layer
Freq Transfer
e.g. SyncE
PHY-layer
Freq Transfer
e.g. SyncE
SyncE
consumer
O
Packet-
based
consumer
Frequency Distribution Summary
Timing input
Relevant ITU-T
Specifications
Compliancy
EEC
Timing output
ESMC &
SSM-QL
SyncE Line
Card
Packet-based
timing protocol
Mediation function
What about Time?
French scientist B. Gitton
Water Clock (1979)
Quiz
John Harrison (1693-1776)
H1 (1730-1735)
H2 & H3 (1737-1759)
H4 (1755-1759)
What is that?
Who built them?
Why?
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.
Precise marine clocks
Longitude position
TWTT Protocols
What Specific Challenges
Does Time Distribution Introduce?
Time Synchronization
Time synchronization is the distribution of a time reference, all the
associated nodes sharing a common timescale and related epoch.
System A
System B
t
t
timing signal recovered by system A
timing signal recovered by system B
00:01:02 00:01:01 00:01:00
00:01:02 00:01:01 00:01:00
Ex.: UTC, UTC + n x hours
GPS Time, Local arbitrary Time
System A
System B
t
t
00:01:02 00:01:01 00:01:00
00:01:02 00:01:01 00:01:00
Ex.: UTC, UTC + n x hours
GPS Time, Local arbitrary Time
Figure xxx/G.8266 Time Synchronization
Absolute vs. Relative Time
Transmitting time reference can be absolute (from national
standards) or relative (bounded timekeeping system).
Time synchronization is one way achieving phase synchronization.
Phase alignment does not mandate giving a time value.
Phase Synchronization
This is not phase locking which is
often a result of a PLL in a
physical timing transfer.
Phase locking implies frequency
synchronization and allows phase
offset.
The term phase synchronization
(or phase alignment) implies that
all associated nodes have access
to a reference timing signal whose
significant events occur at the
same instant (within the relevant
phase accuracy requirement).
t
t
System A
System B
B
Reference timing signal
to system A
to system B
t
t
System A
System B
B
to system A
to system B
Figure xxx/G.8266 Phase Synchronization
Time Distribution for Mobile Wireless BS
Target from 1s to tens of s (alignment between BS)
Target from 0.5s to tens of s (from common reference)
O
O
Time Source
O
O
O
O
O
Accuracy, Stability and Precision
Syntonization and Synchronization
TWTT protocol client / slave has two processes:
The syntonization
The synchronization
Strictly speaking, the term synchronization applies to alignment
of time and the term syntonization applies to alignment of
frequency.
The master/server and slave/client clocks each have their own
time-base and own wall-clock and the intent is to make the
slave/client equal to the master/server.
The notion of frequency synchronization (or syntonization) is
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.
TWTT Protocols
NTP vs. PTP Message Exchange
Master
time
Slave
time
t
1
t
4
t
3
t
2
Timestamps
known by slave
t
2
t
1
, t
2
t
1
, t
2
, t
3
t
1
, t
2
, t
3
, t
4
t-ms
t-sm
Sync
Follow_Up
Delay_Req
Delay_Resp

NTP
PTP
Usual unidirectional
ACR protocol
As part of time recovery, theres always a frequency recovery process.
TWTT Protocol Basics
Basic NTP Message Exchange
SERVER
CLIENT
Time_REQ
Time_RESP
T
1
T
2
T
4
T
3
Timestamps
known
by client
T
1
, T
2
, T
3
, T
4
T
1
Real T
2
= T
1
+ Real Delay
But
T
SC
T
CS
Assumption := symmetry!
Offset = ((T
2
- T
1
) - (T
4
- T
3
))/2
Delay = ((T
2
- T
1
)+(T
4
- T
3
))/2
Server time = Ts Client time = Tc = Ts + offset
TWTT Protocol Basics
Basic PTP Message Exchange
MASTER SLAVE
Delay_Resp
t
1
t
3
t
4
Timestamps
known by
slave
t
1
, t
2
, t
3
, t
4
Delay
Delay
Offset = T
S
- T
M
t
2
t
1
, t
2
, t
3
t
1
, t
2
SYNC
Delay - Offset = B = t
4
t
3
t
2
= t
1
+ Offset + Delay
Offset + Delay = A = t2 t1
t
4
= t
3
- Offset + Delay
Delay_Req
Master time = T
M
Slave time = T
S
= T
M
+ offset
Offset = ((t
2
t
1
)(t
4
t
3
))/2 Delay = ((t
2
t
1
)+(t
4
t
3
))/2
PDV and Asymmetry
Forward and backward delays and delay variations are
not identical.
Asymmetry: A Closer Look
Each Node and Link can introduce asymmetry.
There are various sources of asymmetry.
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
Enabled features
Network
Traffic path inconsistency
Interface speed change
TWTT: Summary of Sources of Error
Asymmetry: introduce a mean time-error.
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 time-delay variation in the path(s) between
master and slave.
Inaccuracy of the slave time-base
Any frequency offset and/or frequency drift will color the measurements.
The standard deviation of the time-base and time-error error will
decrease with increasing rate of packet exchange between master
and 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!
time
frequency
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.
Assumes path symmetry and path consistency.
IEEE1588 incorporates some in-network correction
mechanisms to improve the quality of the transfer.
IEEE1588 has the concept of asymmetry 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.
IEEE Std 1588-2008
PTP Version 2
A set of event messages
consisting of:
- Sync
- Delay_Req
- Pdelay_Req
- Pdelay_Resp
A set of general messages
consisting of:
- Follow_Up
- Delay_Resp
- Pdelay_Resp_Follow_Up
- Announce
- Management
- Signaling
Transmission modes: either unicast or multicast (can be mixed)
Encapsulations: L2 Ethernet, IPv4, IPv6 (others possible)
Multiple possible values or range of 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.
One-step mode breaks IEEE/OSI/IETF/ITU layers.
Basic PTP Message Exchange
MASTER SLAVE
Delay_Resp
t
1
t
3
t
4
Timestamps
known by
slave
t
1
, t
2
, t
3
, t
4
SM_Delay
Master time = T
M
Slave time = T
S
t
2
t
1
, t
2
, t
3
t
1
, t
2
SYNC
Delay_Req
MS_Delay
Quality of the Timestamp
SYNC
MASTER SLAVE
Delay_REQ
Delay_RESP
MAC/PHY
MAC/PHY
P
P
Hardware assistance necessary to prevent insertion of errors or inaccuracies.
t
1
t
2
t
3
t
4
t
4
t
1
t
2
t
3
Need to inject the
timestamp into the
payload at the
time the packet
gets out.
Timestamps
known by
slave
t
1
, t
2
, t
3
, t
4
t
1
, t
2
, t
3
t
1
, t
2
Follow_Up
SYNC()
MASTER SLAVE
Delay_REQ()
Delay_RESP(t
4
)
MAC/PHY
MAC/PHY
P
P
Timestamps
known by
slave
Follow_Up(t
1
)
t
1
t
2
t
4
t
3
Two-step clock
mode
Vs.
One-step (a.k.a.
on-the-fly)
clock mode
t
1
, t
2
, t
3
, t
4
t
1
, t
2
, t
3
t
1
, t
2
t
2
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.
IEEE Std 1588-2008 Clocks
BC and TC aims correcting delay variation into intermediate nodes
between OCs.
Can correct link asymmetry if known.
Ref.
Clock
Recovered
Clock
Ordinary
Slave
Ordinary
Master
TC
BC
Transparent
Clock
Boundary
Clock
IEEE Std 1588-2008 BC
Can help on scalability when using unicast.
Equivalent to NTP Stratum (>1) Server UTC
Node by node: BC slave function is critical
Ref.
Clock
Recovered
Clock
Ordinary
Slave
Ordinary
Master
BC
Boundary
Clock
BC
Boundary
Clock
IEEE Std 1588-2008 TC
TC calculates Residence Time (forward / reverse intra node
delays).
TC are supposed to be transparent but:
One-step clock issue
Ref.
Clock
Recovered
Clock
Ordinary
Slave
Ordinary
Master
Transparent
Clock
Transparent
Clock
TC TC
IEEE1588-2008 Transparent Clocks
Residence Time and Correction Field
Preamble
Event message payload Network
protocol
headers
Correction
field
Preamble
PTP message payload Network
protocol
headers
Correction
field
Residence time bridge Ingress Egress
- +
Ingress timestamp Egress timestamp
+
+
Message at ingress Message at egress

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 interface types
IEEE 802.3, ITU-T G.709,
Multiple interface frequencies
10GE, 100GE, STM64, STM192
Multiple encapsulations
Ethernet, IP
MPLS, MPLS-TP, PBB-TE
E2E TC Operation
TC E2E shall calculate Residence Times for forward
AND reverse event messages.
Ordinary
Slave
Ordinary
Master
TC TC
P2P TC Operation
TC P2P shall calculate forward Residence Times only.
Ordinary
Slave
Ordinary
Master
TC TC
Multi Domain Deployment?
Ref.
Clock
Recovered
Clock
Ordinary
Slave
Ordinary
Master
TC
BC
Wholesale
Boundary
Clock
TC
BC
Who owns the master?
Who owns the slaves?
Who owns the intermediate nodes?
Monitoring the Performance
How to guarantee the recovered clock quality?
PSN
Ref.
Clock
Recovered
Clock
Slave/
Client
Master/
Server
?
?
?
TC
? ?
BC
Objective: accuracy and stability from reference
IEEE 1588-2008 (PTPv2) In A Nutshell
IEEE Std 1588-2008 is actually a toolbox !
What does support of IEEE 1588 really mean ?
IEEE Std 1588 itself is not sufficient for telecom
operator operations.
Node characterization, modeling, performance, metrics
For phase & time support, it is expected any telecom
standardization would take time.
About Telecom Profiles
Telecom profiles will require matching the consumer requirements to the
network design and 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)
Time Distribution
TWTT Technical Challenges Summary
Application requirements
Client/Slave
Server/Master
IEEE 1588-2008 Boundary &
Transparent Clocks
Protocol and Protocol Configuration
Network
Design, Traffic, Nodes
Node design includes BC & TC
Engineering
path symmetry
hardware assistance
path consistency
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 layer solutions required to upgrade routers and switches.
Packet-based solutions are more flexible but less deterministic.
Whatever the timing protocol, it must deal with the same network
constraints.
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 work.
Timing network engineering
Rules
Experience
Monitoring
Challenges
Cost-efficiency : TCO considerations
Multi-domain transfer
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
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
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
Complete Your Online
Session Evaluation
Give us your feedback and you
could win fabulous 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.
Dont forget to activate your
Cisco Live Virtual account for access to
all session material, communities, and
on-demand and live activities throughout
the year. Activate your account at the
Cisco booth in the World of Solutions or visit
www.ciscolive.com.
Appendix
Acronyms
Acronyms
ACR : Adaptive Clock Recovery
AVB : Audio Video Bridging
BITS : Building Integrated Timing System
BS : Base Station
CDMA : Code Division Multiple Access
CES : Circuit Emulation Service
DSL : Digital Subscriber Line
DTI : DOCSIS Timing Interface
DVB : Digital Video Broadcast
DVB-T/H : DVB Terrestrial / Handheld
ESMC : Ethernet Synchronization Messaging Channel
FDD : Frequency Division Duplexing
GNSS : Global Navigation Satellite System
GPS : Global Positioning System
GSM : Global System for Mobile communications
IPDV : Inter-Packet Delay Variation
IRIG : Inter Range Instrumentation Group
LORAN : LOng Range Aid to Navigation
LTE : Long Term Evolution
MAFE : Maximum Averaged Frequency Error
MATIE : Maximum Averaged Time Interval Error
MB(M)S : Multicast Broadcast (Multimedia) Services
MBSFN : Multicast Broadcast Single Frequency Network
M-CMTS : Modular Cable Modem Termination System
MSAN : Multi Service Access Node
MRTIE : Maximum Relative Time Interval Error
MTIE : Maximum Time Interval Error
NGN : Next Generation Network
NTP : Network Time Protocol
OLT : Optical Line Terminal (PON)
OSSP : Organization Specific Slow Protocol
PDV : Packet Delay Variation
PON : Passive Optical Network
PPS : Pulse Per Second
PRC : Primary Reference Clock
PRS : Primary Reference Source
PSN : Packet Switched Network
PTP : Precision Time Protocol
QL : Quality Level
SDO : Standardization Development Organizations
SDSL : Symmetric Digital Subscriber Line
SEC : SDH Equipment Clock
SFN : Single Frequency Network
SLA : Service Level Agreement
SP : Service Provider
SSM : Synchronization Status Message
SSU : Synchronization Supply Unit
SyncE : ITU-T Synchronous Ethernet
TDD : Time Division Duplexing
TDEV : Time DEViation
TDM : Time Division Multiplexing
TD-SCDMA : Time Division Synchronous CDMA
TIE : Time Interval Error
TWTT : Two Way Time Transfer (protocol)
UTC : Coordinated Universal Time
UTMS : Universal Mobile Telecommunications System
WCDMA : Wideband CDMA
WIP : Work In Progress

Brkagg-3000 c1 Rev1

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

Brkagg-3000 c1 Rev1

Uploaded by

Copyright:

Available Formats

2009 Cisco Systems, Inc. All rights reserved.

Cisco Public Presentation_ID 1

You might also like