Upload
phungthuan
View
249
Download
13
Embed Size (px)
Citation preview
© 2016 Microsemi Corporation. SMPTE San Francisco 1
Power Matters.TM
SMPTE ST-2059-2 (IEEE1588) February 9, 2016 http://www.microsemi.com/timing-and-synchronization
Power Matters.TM 2 © 2016 Microsemi Corporation. SMPTE Montreal
Introduction to IEEE1588-2008 • Precision Time Protocol (PTP)
• Concept of Industry Profiles
Introduction to SMPTE ST-2059-2 Profile
Deployment Scenarios • Greenfield, all new Ethernet/IP switches/routers
• Brownfield, existing Ethernet/IP switches/routers
• Challenges
Equipment Design
Agenda
Power Matters.TM 4 © 2016 Microsemi Corporation. SMPTE Montreal
Packet
Network
IEEE1588 Basic Operation: Ordinary Clock
In the network there is a source of frequency, phase & time
An Ordinary Clock operating as a Master/Server encodes the source information into PTP packets
An OC operating as a Slave/Client decodes the source information from PTP packets to recover the original source information
The challenge is the degradation of the information as it traverses the packet network and is affected by packet delay variation
Source of
Time
Ordinary Clock
Master/Server
Ordinary Clock
Slave/Client
Power Matters.TM 5 © 2016 Microsemi Corporation. SMPTE Montreal
Packet
Network
Source of
Time
Ordinary Clock
Slave/Client
IEEE1588 Basic Operation: Boundary Clock
To decrease the degradation of information as it traverses the network, a Boundary Clock may be installed
A BC terminates the PTP connection from the Master/Server and creates a new PTP connection towards the Slave Client
A BC removes PDV between itself and the next upstream clock
BCs may be installed in every network element for the highest level of performance at the Slave/Client
Boundary
Clock
Ordinary Clock
Master/Server
Power Matters.TM 6 © 2016 Microsemi Corporation. SMPTE Montreal
Packet
Network
Source of
Time
Ordinary Clock
Slave/Client
IEEE1588 Basic Operation: Transparent Clock
A Transparent Clock does not terminate the PTP connection.
A TC is able to minimize the information degradation (e.g. PDV) that it’s own network element causes (by modifying the PTP packet as it flows through the network element)
• A TC may be configured to remove only its own PDV (end-to-end operation)
• A TC may be configured to additionally remove the path delay on its upstream, adjacent cable/link (peer-to-peer operation) if all nodes in the network are TC
Transparent
Clock
Upstream,
Adjacent
Cable/Link
Ordinary Clock
Master/Server
Power Matters.TM 7 © 2016 Microsemi Corporation. SMPTE Montreal
Packet
Network
Source of
Time
Ordinary Clock
Slave/Client
Boundary
Clock
IEEE1588 Basic Operation: Management Node
A Management Node communicates with Ordinary Clocks, Boundary Clocks and Transparent Clocks
A Management Node may either configure or monitor these Clocks from a centralized location using PTP management messages
Management
Node
Ordinary Clock
Master/Server
Power Matters.TM 8 © 2016 Microsemi Corporation. SMPTE Montreal
IEEE1588 Basic Operation: Synchronization
A Slave/Client will synchronize using the following information • The transmission time (t1) and
reception time (t2) of a Sync event message, sent from Master to Slave
• The transmission time (t3) and reception time (t4) of a Delay_Req event message, sent from Slave to Master
A Slave/Client will use this general method to find the time offset:
• meanPathDelay = [(t2-t1) + (t4-t3)]/2
• offsetFromMaster = [(t2-t1) – meanPathDelay]
• slave time offset = [(t2-t1) – (t4-t3)]/2
A Slave/Client assumes the meanPathDelay is symmetrical upstream & downstream. It cannot determine path asymmetry without additional assistance.
t1
t4
t2
t3
Power Matters.TM 9 © 2016 Microsemi Corporation. SMPTE Montreal
Path Delay: End-to-end vs. Peer-to-peer
End-to-end • Sync
– Provides t1, t2
– Terminated by OC, BC
• Delay_Req, Delay_Resp
– Provides t3, t4
– Terminated by OC, BC
Peer-to-peer • Sync
– Provides t1, t2
– Terminated by OC, BC
• Pdelay_Req, Pdelay_Resp
– Provides t1, t2, t3, t4
– Terminated by OC, BC, TC
Delay_Req, Delay_Resp
Sync
Delay_Req, Delay_Resp
Sync
PDelay_Req, PDelay_Resp PDelay_Req, PDelay_Resp
PDelay_Req, PDelay_Resp
Sync
PDelay_Req, PDelay_Resp
Sync
Sync Sync
Sync Sync
Delay_Req, Delay_Resp Delay_Req, Delay_Resp
Clock Name
OC-Master
BC
TC
OC-Slave
Power Matters.TM 10 © 2016 Microsemi Corporation. SMPTE Montreal
Profiles in IEEE 1588-2008
A PTP profile is a set of required options, prohibited options, and the ranges and defaults of configurable attributes
• “A PTP profile may be developed by external organizations, including:
• a) A recognized standards organization with jurisdiction over the industry, e.g. IEC, IEEE, IETF, ANSI, ITU, or;
• b) An industry trade association or other similar organization recognized within the industry as having standards authority for the industry
• c) Other organizations as appropriate.”
According to IEEE 1588-2008, a profile should define:
• Best master clock algorithm options
• Configuration management options
• Path delay measurement option (delay request-response or peer delay)
• Range and default values of all configurable attributes and data set members
• Transport mechanisms required, permitted, or prohibited
• Node types required, permitted, or prohibited
• Options required, permitted, or prohibited
• It also allows to extend the standard
Different applications need different profiles
• Need to understand the application requirements
But… in addition to IEEE 1588 profile parameters, other aspects need to be considered
• Clock requirements
– What is the clock bandwidth?
– What is the frequency and holdover accuracy?
• Functions to be implemented
– One-step versus two-step
– Does it support Boundary Clocks?
– Does it support Transparent Clocks?
– Does it support Synchronous Ethernet?
• Network Metrics
– Unicast versus Multicast
– Does the network support QoS?
– Characterization of the network – ITU-T is studying metrics to characterize the network (e.g., FPP)
– Traffic load
– Number of hops
Power Matters.TM 11 © 2016 Microsemi Corporation. SMPTE Montreal
Industry SDO Profile SDO
Status
Clocks Delay
Mechanism
Network
Aware
Transport Notes
Default IEEE 1588 Annex J.3 Default Delay Request-Response 2008 OC,BC,TC E2E Undefined Undefined
Default IEEE 1588 Annex J.4 Default Peer-to-Peer 2008 OC,BC,TC P2P Full Undefined
Telecom ITU-T G.8265.1 Telecom Profile for Frequency 2010 OC E2E Non IPv4, IPv6
Telecom ITU-T G.8275.1 Telecom Profile for Phase Aware 2014 OC, BC E2E Full Ethernet SyncE
Telecom ITU-T G.8275.2 Telecom Profile for Phase Unaware Draft OC, BC E2E Non/Partial IPv6, IPv6 SyncE/GPS
Financial/Enterprise IETF TICTOC Enterprise Draft OC, BC, TC E2E Non/Partial IPv4, IPv6
Cable CableLabs Remote DOCSIS Timing Interface Draft OC, BC E2E Non/Partial/Full IPv4, IPv6 ETH SyncE
Power IEEE C37.238 Power Profile 2011 OC, TC P2P Full Ethernet/VLAN
Power IEEE C37.238 Power Profile Revision (Level 2) Draft OC, BC, TC P2P Full Ethernet(/VLAN)
Power IEC 61850-9-3 Power Utility Automation (Level 1) Draft OC, BC, TC P2P Full Ethernet
Power/Industrial IEC 62493-3 Annex A.2 Automation Networks using PRP & HSR 2012 OC, TC, (BC) P2P Full Ethernet
Industrial Automation IEC 62439-3 Annex B “U” Utility Automation Profile Draft OC, BC, TC P2P Full Ethernet
Industrial Automation IEC 62439-3 Annex C “D” Drives & Process Automation Profile Draft OC, BC, TC E2E Full IPv4
Audio/Video IEEE TSN/AVB IEEE 802.1AS gPTP 2011 OC, BC P2P Full Ethernet
Audio/Video IEEE TSN/AVB IEEE 802.1AS gPTP Revision Draft OC, BC P2P Full Ethernet
Audio AES AES67 Media Profile 2013 OC, BC E2E, (P2P) Undefined IPv4
Video SMPTE ST-2059-2 Professional Broadcast Environment Profile 2015 OC, BC, TC, M E2E, (P2P) Undefined IPv4, IPv6
Video SMPTE ST-2059-2 Professional Broadcast Environment Profile Amd1 Draft OC, BC, TC, M E2E, (P2P) Undefined IPv4, IPv6
Nuclear CERN White Rabbit v2.0 2011 OC, BC E2E Full Undefined SyncE
Automotive AVNu Automotive (based on IEEE802.1AS) Draft OC, BC P2P Full Ethernet
Instrumentation LXI IEEE 1588 Profile for LXI Instrumentation 2008 OC, BC, TC E2E, (P2P) Undefined IPv4, (IPv6)
IEEE 1588-2008 Industry Profiles
The following industries have established profiles
Useful to review deployment ideas from others
Power Matters.TM 12 © 2016 Microsemi Corporation. SMPTE Montreal
IEEE 1588 Profiles, One Part of Solution
The overall IEEE 1588 solution includes • Timestamp Unit
• Transport Layer This is the one standardized in “profiles”
• IEEE 1588 Protocol This is the one standardized in “profiles”
• Algorithm/Servo Mostly independent of “profile”
• PLL Independent of “profile”
Single Board Equipment
PHY/
Switch
Host Software
PHY/
Switch
XO TCXO
System
Synchronizer
IEEE 1588
PLL
1588 Clock
1588 PPS
1588 ToD
1588 Clock
1588 PPS
1588 ToD
1588
Packets
CID w/TS
XO
Timestamp
Unit
(TSU)
Timestamp
Unit
(TSU)
ToD
Counter
ToD
Counter
Time
Sync
Algorithm
IEEE 1588 BC / Client /
Server
BMCA / Alternate BMCA
Power Matters.TM 14 © 2016 Microsemi Corporation. SMPTE Montreal
Committee/Group • Standards Committee: TC-32NF Network/Facilities Architecture
• Contributing Groups: TC-32NF-80 WG Time Labeling and Synchronization
Standards • IEEE Standard 1588-2008 Precision Time Protocol
• SMPTE ST 12-1:2014, Time and Control Code
• SMPTE ST 2059-1:2015x Generation and Alignment of Interface Signals to the SMPTE Epoch
• SMPTE ST 2059-2:2015x SMPTE Profile for use of IEEE-1588 Precision Time Protocol in Professional Broadcast Applications
• SMPTE ST 2059-2:201X, SMPTE Profile for use of IEEE-1588 Precision Time Protocol in Professional Broadcast Applications — Amendment 1
Engineering Guidelines • SMPTE EG 2059-10:201x, Introduction to the New Synchronization System
• SMPTE EG 2059-11:201x, Synchronization System – Management of Timescale Discontinuities
• SMPTE EG 2059-12:201x, Systemization Considerations for using SMPTE ST 2059 (Informative)
• SMPTE EG 2059-13:201x, Best Practices for Large Scale SMPTE 2059-2 PTP Deployments
• SMPTE EG 2059-15:201x, Date and Time Related Terms and Definitions
Inter-operability • Golden Results, Profile Test Plan, Test Report
References
Power Matters.TM 15 © 2016 Microsemi Corporation. SMPTE Montreal
Professional Broadcast Environment Profile (SMPTE ST-2059-2) Profile Details
• ID 68-97-E8-00-01-00
• Default BMCA
• Permits management messages
• Path delay: Default E2E, May P2P
• Priority1: 128 [0..255], Priority2: 128 [0..255]
• Domain: 127 [0..127]
• logAnnounceInterval: -2 [-3 .. +1]
• AnnounceReceiptTimeout: 3 [2..10]
• logSyncInterval: -3 [-7..-1]
• logMinDelayReqInterval: logSyncInt [S..S+5]
• logMinPDelayReqInterval: logSyncInt [S..S+5]
• Variance algorithm: 1.0s default
• timeSource: 0xF0 or 0xF1
• clocKClass:
– 150 (1ppm), 158 (10ppm)
– 220(1ppm+ARB), 228(10ppm+ARB)
• Slaves support 1-step and 2-step
Clocks • Required OC,
• Permitted BC, E2E TC, P2P TC, MGMT
Misc • Permitted: Alternate master, Path trace, unicast negotiation,
alternate timescales, Acceptable master table
• Prohibited: Grandmaster clusters, unicast discovery
Custom • Custom Alternate Master operation
– Responds to Delay_Req, does not use TLV
• TLV: Synchronization Metadata (organization extension)
Performance • Network lock < 1 µs between any two slave devices with
respect to master
– Slave lock < ±500 ns
• Slave lock time < 5 seconds
• Master < ±5 ppm
Notes • PTP epoch/SMPTE epoch:
– 63072010 seconds before
– 1972-01-01T00:00:00Z (UTC).
Transport • Permitted: IPv4 (Annex D), IPv6 (Annex E)
– IPv4 multicast must support IGMPv3, may IGMPv3
– IPv6 multicast must support MLDv2, may MLDv1
• Announce, Sync & Follow_Up
– Required: Announce, Sync & Follow_Up as multicast
– Permitted: Announce, Sync & Follow_Up as unicast
– Unicast negotiation optional for Announce & Sync
• Delay_Req
– Delay_Req may be multicast or unicast
– Unicast negotiation optional for Delay_Req
• Pdelay_Req & Resp
– Pdelay_Req may be multicast or unicast
– Pdealy_Resp & Follow_Up must be unicast
Power Matters.TM 16 © 2016 Microsemi Corporation. SMPTE Montreal
Professional Broadcast Environment Profile (SMPTE ST-2059-2)
Profile Details
• ID 68-97-E8-00-01-00
• Default BMCA
• Permits management messages
• Path delay: Default E2E, May P2P
• Priority1: 128 [0..255], Priority2: 128 [0..255]
• Domain: 127 [0..127]
• logAnnounceInterval: -2 [-3 .. +1]
• AnnounceReceiptTimeout: 3 [2..10]
• logSyncInterval: -3 [-7..-1]
• logMinDelayReqInterval: logSyncInt [S..S+5]
• logMinPDelayReqInterval: logSyncInt [S..S+5]
• Variance algorithm: 1.0s default
• timeSource: 0xF0 or 0xF1
• clocKClass:
– 150 (1ppm), 158 (10ppm)
– 220(1ppm+ARB), 228(10ppm+ARB)
• Slaves support 1-step and 2-step
Clocks
• Required OC,
• Permitted BC, E2E TC, P2P TC, MGMT
Power Matters.TM 17 © 2016 Microsemi Corporation. SMPTE Montreal
Professional Broadcast Environment Profile (SMPTE ST-2059-2)
Transport
• Permitted: IPv4 (Annex D), IPv6 (Annex E)
– IPv4 multicast must support IGMPv3, may IGMPv3
– IPv6 multicast must support MLDv2, may MLDv1
• Announce, Sync & Follow_Up
– Required: Announce, Sync & Follow_Up as multicast
– Permitted: Announce, Sync & Follow_Up as unicast
– Unicast negotiation optional for Announce & Sync
• Delay_Req
– Delay_Req may be multicast or unicast
– Unicast negotiation optional for Delay_Req
• Pdelay_Req & Resp
– Pdelay_Req may be multicast or unicast
– Pdealy_Resp & Follow_Up must be unicast
Performance
• Network lock < 1 µs between any two slave devices with respect to master
– Slave lock < ±500 ns
• Slave lock time < 5 seconds
• Master < ±5 ppm
Notes
• PTP epoch/SMPTE epoch:
– 63072010 seconds before
– 1972-01-01T00:00:00Z (UTC).
Misc
• Permitted: Alternate master, Path trace, unicast negotiation, alternate timescales, Acceptable master table
• Prohibited: Grandmaster clusters, unicast discovery
Custom
• Custom Alternate Master operation
– Responds to Delay_Req, does not use TLV
• TLV: Synchronization Metadata (organization extension)
Power Matters.TM 19 © 2016 Microsemi Corporation. SMPTE Montreal
ST2059 Deployment
Source: Draft Proposal ST2059-2 Inter-op Test Plan 5-29-15 32NF-80.pdf
Power Matters.TM 20 © 2016 Microsemi Corporation. SMPTE Montreal
Deployment Scenario: Legacy (Brownfield) Network
Scenario • Legacy Ethernet/IP switch/router infrastructure already
installed
• Add IEEE1588 synchronization ‘over the top’
• Network may support QoS to prioritize IEEE1588 packets
• Advantages • Do not need to modify existing infrastructure
• Dis-advantages • Performance depends on the packet network
infrastructure, such as number of hops, traffic loading, QoS, asymmetry, etc.
• Slave clocks may require more expensive oscillator
• Performance • Wide ranging from less than 1 us to over 10 us.
OC-Slave
GNSS
OC-Master
Clock Clock Role
GNSS/
GPS
Time
Source
System
OC Master System
OC Slave IC
Power Matters.TM 21 © 2016 Microsemi Corporation. SMPTE Montreal
Deployment Scenario: Legacy (Brownfield) Network [with BC clean-up]
Clock Clock Role
GNSS/
GPS
Time
Source
System
OC Master System
BC Boundary System/IC
OC Slave IC
OC-Slave
GNSS
OC-Master Boundary
Clock
Scenario • Legacy Ethernet/IP switch/router infrastructure already installed
• Add IEEE1588 synchronization ‘over the top’
• Network may support QoS to prioritize IEEE1588 packets
• A Boundary Clock may be installed as a demarcation point between WAN and LAN, between buildings or between operators
• Advantages • Do not need to modify existing infrastructure
• Dis-advantages • Performance depends on the packet network infrastructure, such
as number of hops, traffic loading, QoS, asymmetry, etc.
• Slave clocks may require more expensive oscillator
• Performance • Wide ranging from less than 1 us to over 10 us.
Power Matters.TM 22 © 2016 Microsemi Corporation. SMPTE Montreal
Clock Clock Role
GNSS/
GPS
Time
Source
System
OC Master System
BC Boundary IC
OC Slave IC
Deployment Scenario: New (Greenfield) Network
GNSS
OC-Master OC-Slave
Scenario • New Ethernet/IP switch/router infrastructure with
IEEE1588 capability
• Advantages • With proper Boundary Clock design, performance
is not dependent on network loading
• Reduced cost of equipment oscillator in slave
• Dis-advantages • Requires new switch/router hardware
• Performance • Typically less than 1 microsecond
Boundary
Clock
Power Matters.TM 23 © 2016 Microsemi Corporation. SMPTE Montreal
Clock Clock Role
GNSS/
GPS
Time
Source
System
OC Master System
TC Transparent IC
OC Slave IC
Deployment Scenario: New (Greenfield) Network
Scenario • New Ethernet/IP switch/router infrastructure with
IEEE1588 capability
• Advantages • With proper Transparent Clock design,
performance is not dependent on network loading
• Reduced cost of equipment oscillator in slave
• Dis-advantages • Requires new switch/router hardware
• Performance • Typically less than 1 microsecond
GNSS
OC-Master OC-Slave
Transparent
Clock
Power Matters.TM 24 © 2016 Microsemi Corporation. SMPTE Montreal
Budgeting Exercise: ± 1µs Performance
End-to-end performance target of ± 1 µs over 10 BC • GPS GM 10 BC End Application
How much of the error should be allocated to each element?
Element Budget [ns] # Elements Total [ns]
GPS 100 100
Cables 10 11 110
BC (constant noise) 50 10 500
BC (dynamic noise) 50 10 158
End Application 100 1 100
968
Power Matters.TM 25 © 2016 Microsemi Corporation. SMPTE Montreal
Equipment Design
Pizza Box with IEEE1588
Power Matters.TM 26 © 2016 Microsemi Corporation. SMPTE Montreal
End Applications • Cameras
• Microphones
• Storage devices
• SDI to IP encapsulators
• IP to SDI de-capsulators
• Production switching
• Encoders
Transport • Switches
• Routers
Equipment using ST2059
Power Matters.TM 27 © 2016 Microsemi Corporation. SMPTE Montreal
Single Board Equipment
PHY/
Switch
Host Software
PHY/
Switch
XO TCXO
System
Synchronizer
IEEE 1588
PLL
1588 Clock
1588 PPS
1588 ToD
1588 Clock
1588 PPS
1588 ToD
PPS
Clock (optional)
ToD (optional)
GPS
Receiver
1588
Packets
CID w/TS
XO
Timestamp
Unit
(TSU)
Timestamp
Unit
(TSU)
ToD
Counter
ToD
Counter
Time
Sync
Algorithm
IEEE 1588 BC / Client /
Server
BMCA / Alternate BMCA
Equipment Design: OC-Master, OC-Slave, BC, TC
Major components
• Ethernet PHY or Switch with integrated timestamp unit
• System Synchronizer PLL with associated local oscillator
• Host with IEEE1588 protocol engine and software synchronization servo
Active SyncE
Active PTP
Monitored
Power Matters.TM 28 © 2016 Microsemi Corporation. SMPTE Montreal
Single Board Equipment
PHY/
Switch
Host Software
PHY/
Switch
XO TCXO
System
Synchronizer
IEEE 1588
PLL
1588 Clock
1588 PPS
1588 ToD
1588 Clock
1588 PPS
1588 ToD
PPS
Clock (optional)
ToD (optional)
GPS
Receiver
1588
Packets
CID w/TS
XO
Timestamp
Unit
(TSU)
Timestamp
Unit
(TSU)
ToD
Counter
ToD
Counter
Time
Sync
Algorithm
IEEE 1588 BC / Client /
Server
BMCA / Alternate BMCA
Equipment Design: OC-Master
OC-Master or GM will synchronize to a GNSS / GPS receiver, either internal or external to the equipment
System PLL will distributed clock and 1PPS to all timestamp to ensure cross-system alignment of ToD counters
Timestamp units will timestamp IEEE1588 packets
Active SyncE
Active PTP
Monitored
Power Matters.TM 29 © 2016 Microsemi Corporation. SMPTE Montreal
Single Board Equipment
PHY/
Switch
Host Software
PHY/
Switch
XO TCXO
System
Synchronizer
IEEE 1588
PLL
1588 Clock
1588 PPS
1588 ToD
1588 Clock
1588 PPS
1588 ToD
PPS
Clock (optional)
ToD (optional)
GPS
Receiver
1588
Packets
CID w/TS
XO
Timestamp
Unit
(TSU)
Timestamp
Unit
(TSU)
ToD
Counter
ToD
Counter
Time
Sync
Algorithm
IEEE 1588 BC / Client /
Server
BMCA / Alternate BMCA
Equipment Design: BC, OC-Slave
BC or OC-Slave will synchronize to an IEEE1588 source
IEEE1588 engine and synchronization servo will align system PLL with the synchronization source by adjusting frequency & phase
System PLL will distributed clock and 1PPS to all timestamp to ensure cross-system alignment of ToD counters
Timestamp units will timestamp IEEE1588 packets
Active SyncE
Active PTP
Monitored