Precision Time Protocol

From HandWiki
Short description: Network time synchronization protocol


The Precision Time Protocol (PTP) is a protocol used to synchronize clocks throughout a computer network. On a local area network, it achieves clock accuracy in the sub-microsecond range, making it suitable for measurement and control systems.[1] PTP is employed to synchronize financial transactions, mobile phone tower transmissions, sub-sea acoustic arrays, and networks that require precise timing but lack access to satellite navigation signals.

The first version of PTP, IEEE 1588-2002, was published in 2002. IEEE 1588-2008, also known as PTP Version 2 is not backward compatible with the 2002 version. IEEE 1588-2019 was published in November 2019 and includes backward-compatible improvements to the 2008 publication. IEEE 1588-2008 includes a profile concept defining PTP operating parameters and options. Several profiles have been defined for applications including telecommunications, electric power distribution and audiovisual. IEEE 802.1AS is an adaptation of PTP for use with Audio Video Bridging and Time-Sensitive Networking.

History

According to John Eidson, who led the IEEE 1588-2002 standardization effort, "IEEE 1588 is designed to fill a niche not well served by either of the two dominant protocols, NTP and GPS. IEEE 1588 is designed for local systems requiring accuracies beyond those attainable using NTP. It is also designed for applications that cannot bear the cost of a GPS receiver at each node, or for which GPS signals are inaccessible."[2]

PTP was originally defined in the IEEE 1588-2002 standard, officially entitled Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, and published in 2002. In 2008, IEEE 1588-2008 was released as a revised standard; also known as PTP version 2 (PTPv2), it improves accuracy, precision and robustness but is not backward compatible with the original 2002 version.[3] IEEE 1588-2019 was published in November 2019,[4] is informally known as PTPv2.1 and includes backwards-compatible improvements to the 2008 publication.[5]

Architecture

The IEEE 1588 standards describe a hierarchical master–slave architecture for clock distribution. Under this architecture, a time distribution system consists of one or more communication media (network segments), and one or more clocks. An ordinary clock is a device with a single network connection and is either the source of (master or leader) or destination for (slave or follower) a synchronization reference. A boundary clock has multiple network connections and can accurately synchronize one network segment to another. A synchronization master is selected for each of the network segments in the system. The root timing reference is called the grandmaster.[6] The grandmaster transmits synchronization information to the clocks residing on its network segment. The boundary clocks with a presence on that segment then relay accurate time to the other segments to which they are also connected.

A simplified PTP system frequently consists of ordinary clocks connected to a single network, and no boundary clocks are used. A grandmaster is elected and all other clocks synchronize directly to it.

IEEE 1588-2008 introduces a clock associated with network equipment used to convey PTP messages. The transparent clock modifies PTP messages as they pass through the device.[7] Timestamps in the messages are corrected for time spent traversing the network equipment. This scheme improves distribution accuracy by compensating for delivery variability across the network.

PTP typically uses the same epoch as Unix time (start of 1 January 1970).[lower-alpha 1] While the Unix time is based on Coordinated Universal Time (UTC) and is subject to leap seconds, PTP is based on International Atomic Time (TAI). The PTP grandmaster communicates the current offset between UTC and TAI, so that UTC can be computed from the received PTP time.

Protocol details

Synchronization and management of a PTP system is achieved through the exchange of messages across the communications medium. To this end, PTP uses the following message types.

  • Sync, Follow_Up, Delay_Req and Delay_Resp messages are used by ordinary and boundary clocks and communicate time-related information used to synchronize clocks across the network.
  • Pdelay_Req, Pdelay_Resp and Pdelay_Resp_Follow_Up are used by transparent clocks to measure delays across the communications medium so that they can be compensated for by the system. Transparent clocks and these messages associated with them are not available in original IEEE 1588-2002 PTPv1 standard, and were added in PTPv2.
  • Announce messages are used by the best master clock algorithm in IEEE 1588-2008 to build a clock hierarchy and select the grandmaster.[lower-alpha 2]
  • Management messages are used by network management to monitor, configure and maintain a PTP system.
  • Signaling messages are used for non-time-critical communications between clocks. Signaling messages were introduced in IEEE 1588-2008.

Messages are categorized as event and general messages. Event messages are time-critical in that accuracy in transmission and receipt timestamp accuracy directly affects clock distribution accuracy. Sync, Delay_Req, Pdelay_Req and Pdelay_resp are event messages. General messages are more conventional protocol data units in that the data in these messages is of importance to PTP, but their transmission and receipt timestamps are not. Announce, Follow_Up, Delay_Resp, Pdelay_Resp_Follow_Up, Management and Signaling messages are members of the general message class.[8]:Clause 6.4

Message transport

PTP messages may use the User Datagram Protocol over Internet Protocol (UDP/IP) for transport. IEEE 1588-2002 uses only IPv4 transports,[9]:Annex D but this has been extended to include IPv6 in IEEE 1588-2008.[8]:Annex F In IEEE 1588-2002, all PTP messages are sent using multicast messaging, while IEEE 1588-2008 introduced an option for devices to negotiate unicast transmission on a port-by-port basis.[8]:Clause 16.1 Multicast transmissions use IP multicast addressing, for which multicast group addresses are defined for IPv4 and IPv6 (see table).[8]:Annex D and E Time-critical event messages (Sync, Delay_req, Pdelay_Req and Pdelay_Resp) are sent to port number 319. General messages (Announce, Follow_Up, Delay_Resp, Pdelay_Resp_Follow_Up, management and signaling) use port number 320.[8]:Clause 6.4

Multicast group addresses
Messages IPv4 IPv6 IEEE 802.3 Ethernet[8]:Annex F[lower-alpha 3] Type
All except peer delay messages 224.0.1.129[lower-alpha 4] FF0x::181[lower-alpha 5] 01-1B-19-00-00-00[lower-alpha 6] Forwardable
Peer delay messages: Pdelay_Req, Pdelay_Resp and Pdelay_Resp_Follow_Up[lower-alpha 7] 224.0.0.107[lower-alpha 8] FF02::6B 01-80-C2-00-00-0E Non-forwardable

In IEEE 1588-2008, encapsulation is also defined for DeviceNet,[8]:Annex G ControlNet[8]:Annex H and PROFINET.[8]:Annex I

Domains

A domain[lower-alpha 9] is an interacting set of clocks that synchronize to one another using PTP. Clocks are assigned to a domain by virtue of the contents of the Subdomain name (IEEE 1588-2002) or the domainNumber (IEEE 1588-2008) fields in PTP messages they receive or generate. Domains allow multiple clock distribution systems to share the same communications medium.

Subdomain name field contents (IEEE1588-2002) IPv4 multicast address
(IEEE1588-2002)[lower-alpha 10] 		domainNumber
(IEEE1588-2008) 		Notes
_DFLT 224.0.1.129 0 Default domain
_ALT1 224.0.1.130 1 Alternate domain 1
_ALT2 224.0.1.131 2 Alternate domain 2
_ALT3 224.0.1.132 3 Alternate domain 3
Application specific up to 15 octets[9]:Clause 6.2.5.1 224.0.1.130, 131 or 132 as per hash function on Subdomain name[9]:Annex C 4 through 127 User-defined domains

Best master clock algorithm

The best master clock algorithm (BMCA) performs a distributed selection of the best candidate clock based on the following clock properties:

  • Identifier – A universally unique numeric identifier for the clock. This is typically constructed based on a device's MAC address.
  • Quality – Both versions of IEEE 1588 attempt to quantify clock quality based on expected timing deviation, technology used to implement the clock or location in a clock stratum schema, although only V1 (IEEE 1588-2002) knows a data field stratum. PTP V2 (IEEE 1588-2008) defines the overall quality of a clock by using the data fields clockAccuracy and clockClass.
  • Priority – An administratively assigned precedence hint used by the BMC to help select a grandmaster for the PTP domain. IEEE 1588-2002 used a single Boolean variable to indicate precedence. IEEE 1588-2008 features two 8-bit priority fields.
  • Variance – A clock's estimate of its stability based on observation of its performance against the PTP reference.

IEEE 1588-2008 uses a hierarchical selection algorithm based on the following properties, in the indicated order:[8]:Figure 27

  1. Priority 1 – the user can assign a specific static-designed priority to each clock, preemptively defining a priority among them. Smaller numeric values indicate higher priority.
  2. Class – each clock is a member of a given class, each class getting its own priority.
  3. Accuracy – precision between clock and UTC, in nanoseconds (ns)
  4. Variance – variability of the clock
  5. Priority 2 – final-defined priority, defining backup order in case the other criteria were not sufficient. Smaller numeric values indicate higher priority.
  6. Unique identifier – MAC address-based selection is used as a tiebreaker when all other properties are equal.

IEEE 1588-2002 uses a selection algorithm based on similar properties.

Clock properties are advertised in IEEE 1588-2002 Sync messages and in IEEE 1588-2008 Announce messages. The current clock master transmits this information at regular interval. A clock which considers itself a better master clock will transmit this information in order to invoke a change of master clock. Once the current master recognises the better clock, the current master stops transmitting Sync messages and associated clock properties (Announce messages in the case of IEEE 1588-2008) and the better clock takes over as master.[10] The BMC algorithm only considers the self-declared quality of clocks and does not take network link quality into consideration.[11]

Synchronization

Through use of the BMC algorithm, PTP selects a master source of time for an IEEE 1588 domain and for each network segment in the domain.

Clocks determine the offset between themselves and their master.[12] Let the variable [math]\displaystyle{ t }[/math] represent physical time. For a given slave device, the offset [math]\displaystyle{ o(t) }[/math] at time [math]\displaystyle{ t }[/math] is defined by:

[math]\displaystyle{ \ o(t) = s(t) - m(t) }[/math]

where [math]\displaystyle{ s(t) }[/math] represents the time measured by the slave clock at physical time [math]\displaystyle{ t }[/math], and [math]\displaystyle{ m(t) }[/math] represents the time measured by the master clock at physical time [math]\displaystyle{ t }[/math].

The master periodically broadcasts the current time as a message to the other clocks. Under IEEE 1588-2002 broadcasts are up to once per second. Under IEEE 1588-2008, up to 10 per second are permitted.

IEEE 1588 synchronisation mechanism and delay calculation

Each broadcast begins at time [math]\displaystyle{ T_1 }[/math] with a Sync message sent by the master to all the clocks in the domain. A clock receiving this message takes note of the local time [math]\displaystyle{ T_1' }[/math] when this message is received.

The master may subsequently send a multicast Follow_Up with accurate [math]\displaystyle{ T_1 }[/math] timestamp. Not all masters have the ability to present an accurate timestamp in the Sync message. It is only after the transmission is complete that they are able to retrieve an accurate timestamp for the Sync transmission from their network hardware. Masters with this limitation use the Follow_Up message to convey [math]\displaystyle{ T_1 }[/math]. Masters with PTP capabilities built into their network hardware are able to present an accurate timestamp in the Sync message and do not need to send Follow_Up messages.

In order to accurately synchronize to their master, clocks must individually determine the network transit time of the Sync messages. The transit time is determined indirectly by measuring round-trip time from each clock to its master. The clocks initiate an exchange with their master designed to measure the transit time [math]\displaystyle{ d }[/math]. The exchange begins with a clock sending a Delay_Req message at time [math]\displaystyle{ T_2 }[/math] to the master. The master receives and timestamps the Delay_Req at time [math]\displaystyle{ T_2' }[/math] and responds with a Delay_Resp message. The master includes the timestamp [math]\displaystyle{ T_2' }[/math] in the Delay_Resp message.

Through these exchanges a clock learns [math]\displaystyle{ T_1 }[/math], [math]\displaystyle{ T_1' }[/math], [math]\displaystyle{ T_2 }[/math] and [math]\displaystyle{ T_2' }[/math].

If [math]\displaystyle{ d }[/math] is the transit time for the Sync message, and [math]\displaystyle{ \tilde{o} }[/math] is the constant offset between master and slave clocks, then

[math]\displaystyle{ \ T_1' - T_1 = \tilde{o} + d \text{ and } \ T_2' - T_2 = - \tilde{o} + d }[/math]

Combining the above two equations, we find that

[math]\displaystyle{ \tilde{o} = \frac 1 2 (T_1'-T_1-T_2'+T_2) }[/math]

The clock now knows the offset [math]\displaystyle{ \tilde{o} }[/math] during this transaction and can correct itself by this amount to bring it into agreement with their master.

One assumption is that this exchange of messages happens over a period of time so small that this offset can safely be considered constant over that period. Another assumption is that the transit time of a message going from the master to a slave is equal to the transit time of a message going from the slave to the master. Finally, it is assumed that both the master and slave can accurately measure the time they send or receive a message. The degree to which these assumptions hold true determines the accuracy of the clock at the slave device.[8]:Clause 6.2

Optional features

IEEE 1588-2008 standard lists the following set of features that implementations may choose to support:

  • Alternate Time-Scale
  • Grand Master Cluster
  • Unicast Masters
  • Alternate Master
  • Path Trace

IEEE 1588-2019 adds additional optional and backward-compatible features:[5]

  • Modular transparent clocks
  • Special PTP ports to interface with transports with built-in time distribution
  • Unicast Delay_Req and Delay_Resp messages
  • Manual port configuration overriding BMCA
  • Asymmetry calibration
  • Ability to utilize a physical layer frequency reference (e.g. Synchronous Ethernet)
  • Profile isolation
  • Inter-domain interactions
  • Security TLV for integrity checking
  • Standard performance reporting metrics
  • Slave port monitoring

Related initiatives

  • The International IEEE Symposium on Precision Clock Synchronization for Measurement, Control and Communication (ISPCS) is an IEEE organized annual event that includes a plugtest and a conference program with paper and poster presentations, tutorials and discussions covering several aspects of PTP.[13]
  • The Institute of Embedded Systems (InES) of the Zurich University of Applied Sciences/ZHAW is addressing the practical implementation and application of PTP.
  • IEEE 1588 is a key technology in the LXI Standard for Test and Measurement communication and control.
  • IEEE 802.1AS-2011 is part of the IEEE Audio Video Bridging (AVB) group of standards.[lower-alpha 11] It specifies a profile for use of IEEE 1588-2008 for time synchronization over a virtual bridged local area network as defined by IEEE 802.1Q. In particular, 802.1AS defines how IEEE 802.3 (Ethernet), IEEE 802.11 (Wi-Fi), and MoCA can all be parts of the same PTP timing domain.[14]
  • SMPTE 2059-2 is a PTP profile for use in synchronization of broadcast media systems.[15]
  • The AES67 audio networking interoperability standard includes a PTPv2 profile compatible with SMPTE ST2059-2.[16]
  • Dante uses PTPv1 for synchronization.[17]
  • Q-LAN[18] and RAVENNA[17] use PTPv2 for time synchronization.
  • The White Rabbit Project combines Synchronous Ethernet and PTP.
  • Precision Time Protocol Industry Profile PTP profiles (L2P2P and L3E2E) for industrial automation in IEC 62439-3
  • IEC/IEEE 61850-9-3 PTP profile for substation automation adopted by IEC 61850
  • Parallel Redundancy Protocol use of PTP profiles (L2P2P and L3E2E) for industrial automation in parallel networks
  • PTP is being studied to be applied as a secure time synchronization protocol in power systems' Wide Area Monitoring[19]

See also

Notes

  1. ↑ The profile capability under IEEE 1588-2008 allows the use of application-specific epochs.[8]:Annex B
  2. ↑ In IEEE 1588-2002, information carried by Announce messages is carried in the Sync messages. In IEEE 1588-2008, the Sync message has been optimized and this information is no longer carried here.
  3. ↑ PTP over bare IEEE 802.3 Ethernet using Ethertype 0x88F7
  4. ↑ IEEE 1588-2002 non-default domains use destination addresses 224.0.1.130 through 224.0.1.132 (see #Domains).
  5. ↑ Where x is the address scope (2 for link-local) as per RFC 2373 (see IPv6 multicast address)
  6. ↑ In some PTP applications it is permissible to send all PTP messages to 01-1B-19-00-00-00
  7. ↑ Peer delay messages are intended to propagate to the immediately connected neighbor. The multicast addresses for these messages are designed to be link-local in scope and are not passed through a router. IEEE 1588-2008 also recommends setting time to live to 1 (IPv4) or hop limit to 0 (IPv6) as further insurance that the messages will not be routed.
  8. ↑ Peer delay messaging is not present in IEEE 1588-2002
  9. ↑ IEEE 1588-2002 defines a domain as any interconnected set of clocks (regardless of whether they synchronized to one another) and uses subdomain to refer to what is known as a domain in IEEE 1588-2008.
  10. ↑ IEEE 1588-2008 uses 224.0.1.129 as the address for all multicast messages.
  11. ↑ AVB is further extended by the IEEE 802.1 Time-Sensitive Networking (TSN) Task Group.

References

  1. ↑ Eidson, John (10 October 2005). "IEEE-1588 Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, a Tutorial". National Institute of Standards and Technology (NIST). https://www.nist.gov/document/tutorial-basicpdf. 
  2. ↑ Eidson, John C. (April 2006). Measurement, Control and Communication Using IEEE 1588. Springer. ISBN 978-1-84628-250-8. 
  3. ↑ Eidson, John (2 October 2006). "IEEE 1588 Standard Version 2 - A Tutorial". https://ieee1588.nist.gov/2006%20IEEE1588%20Agenda/Eidson_1588_Version%202.pdf. 
  4. ↑ "1588-2019 - IEEE Approved Draft Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems". IEEE. https://standards.ieee.org/content/ieee-standards/en/standard/1588-2019.html. 
  5. ↑ 5.0 5.1 Douglas Arnold (24 September 2017). "What's coming In the Next Edition of IEEE 1588?". https://blog.meinbergglobal.com/2017/09/24/whats-coming-next-edition-ieee-1588/. 
  6. ↑ "Meanings of common terms used in IEEE 1588". National Institute of Standards and Technology. https://ieee1588.nist.gov/terms.htm. 
  7. ↑ "AN-1838 IEEE 1588 Boundary Clock and Transparent Clock Implementation Using the DP83640". Texas Instruments. https://www.ti.com/lit/an/snla104a/snla104a.pdf. 
  8. ↑ 8.00 8.01 8.02 8.03 8.04 8.05 8.06 8.07 8.08 8.09 8.10 8.11 IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, IEEE, 24 July 2008, doi:10.1109/IEEESTD.2008.4579760, ISBN 978-0-7381-5400-8 
  9. ↑ 9.0 9.1 9.2 IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, IEEE, 8 November 2002, doi:10.1109/IEEESTD.2002.94144, ISBN 978-0-7381-3369-0 
  10. ↑ Watt, Steve T.; Achanta, Shankar; Abubakari, Hamza; Sagen, Eric (March 2014), Understanding and Applying Precision Time Protocol, https://cdn.selinc.com/assets/Literature/Publications/Technical%20Papers/6650_UnderstandingApplying_SA_20140206_Web3.pdf, retrieved 2017-09-09 
  11. ↑ FSMLabs Technical Staff (September 2015), Smart and Dumb PTP Client and the "so-called"Best Master Clock Algorithm, https://www.fsmlabs.com/news/2015/09/18/socalledbestmasterclock.html, retrieved 2018-05-17 
  12. ↑ International standard IEC 61588: Precision clock synchronization protocol for networked measurement and control systems. 2004.
  13. ↑ ISPCS website
  14. ↑ Geoffrey M. Garner (28 May 2010), IEEE 802.1AS and IEEE 1588, https://www.itu.int/dms_pub/itu-t/oth/06/38/T06380000040002PDFE.pdf 
  15. ↑ SMPTE Publishes First Two Parts of Standard Enabling Deployment of PTP-Timed Equipment in Existing SDI Plants, Society of Motion Picture and Television Engineers, 2015-04-13, https://www.smpte.org/news-events/news-releases/smpte%C2%AE-publishes-first-two-parts-standard-enabling-deployment-ptp-timed, retrieved 2015-05-21 
  16. ↑ AES-R16-2016: AES Standards Report - PTP parameters for AES67 and SMPTE ST 2059-2 interoperability, Audio Engineering Society, 2016-05-02, https://www.aes.org/publications/standards/search.cfm?docID=105 
  17. ↑ 17.0 17.1 https://www.smpte.org/sites/default/files/users/user27446/AES67%20for%20Audio%20Production-Background%20Applications%20and%20Challenges.pdf[|permanent dead link|dead link}}]
  18. ↑ "PTPv2 Timing protocol in AV networks". Luminex. 6 June 2017. https://www.luminex.be/improve-your-timekeeping-with-ptpv2/. "Q-LAN updated to PTPv2 approximately two years ago." 
  19. ↑ Pepiciello, Antonio; Vaccaro, Alfredo (2018-12-17), "A reliable architecture based on Precision Time Protocol for WAMPAC synchronization", 2018 AEIT International Annual Conference, IEEE, pp. 1–5, doi:10.23919/AEIT.2018.8577414, ISBN 978-8-8872-3740-5 

External links



Retrieved from "https://handwiki.org/wiki/index.php?title=Precision_Time_Protocol&oldid=3370251"