【IEEE802.1AS-2020】7.5 Differences between gPTP (IEEE Std 802.1AS) and PTP (IEEE Std 1588-2019)

a)
gPTP assumes all communication between PTP Instances is done only using IEEE 802 MAC PDUsand addressing, while IEEE Std 1588-2019 supports various layer 2 and layer 3-4 communicationmethods.
b)
gPTP specifies a media-independent sublayer that simplifies the integration within a single timingdomain of multiple different networking technologies with radically different media accessprotocols. gPTP specifies a media-dependent sublayer for each medium. The information exchangedbetween PTP Instances has been generalized to support different packet formats and managementschemes appropriate to the particular networking technology. IEEE Std 1588-2019, on the otherhand, has introduced a new architecture based on media-independent and media-dependentsublayers (see 6.5.2, Figure 5, and Figure 6 of IEEE Std 1588-2019); however, this architecture isoptional. The architecture of IEEE Std 1588-2008 [B10], which is not based on media-independentand media-dependent layers, has been retained for Internet Protocol (IP) version 4, IP version 6, Ethernet LANs, and several industrial automation control protocols. The intent in IEEE Std 1588-2019 is that the new architecture, based on media-independent and media-dependent layers, will beused for IEEE 802.11 networks, IEEE 802.3 EPON, and CSN using the specifications of gPTP, andthat the architecture must be used for transports that define native timing mechanisms if those nativetiming mechanisms are used.
c)
In gPTP there are only two types of PTP Instances: PTP End Instances and PTP Relay Instances, while IEEE Std 1588-2019 has Ordinary Clocks, Boundary Clocks, end-to-end Transparent Clocks, and P2P Transparent Clocks. A PTP End Instance corresponds to an IEEE 1588 Ordinary Clock, anda PTP Relay Instance is a type of IEEE 1588 Boundary Clock where its operation is very tightlydefined, so much so that a PTP Relay Instance with Ethernet ports can be shown to bemathematically equivalent to a P2P Transparent Clock in terms of how synchronization isperformed, as shown in 11.1.3. In addition, a PTP Relay Instance can operate in a mode (i.e., themode where the variable syncLocked is TRUE; see 10.2.5.15) where the PTP Relay Instance isequivalent to a P2P Transparent Clock in terms of when time-synchronization messages are sent. Atime-aware system measures link delay and residence time and communicates these in a correctionfield. In summary, a PTP Relay Instance conforms to the specifications for a Boundary Clock inIEEE Std 1588-2019, but a PTP Relay Instance does not conform to the complete specifications fora P2P Transparent Clock in IEEE Std 1588-2019 because:
1)When syncLocked is FALSE, the PTP Relay Instance sends Sync according to thespecifications for a Boundary Clock, and
2)The PTP Relay Instance invokes the BMCA and has PTP Port states.
d)
PTP Instances communicate gPTP information only directly with other PTP Instances. That is, agPTP domain consists ONLY of PTP Instances. Non-PTP Relay Instances cannot be used to relaygPTP information. In IEEE Std 1588-2019, it is possible to use non-IEEE-1588-aware relays in anIEEE 1588 domain, although this slows timing convergence and introduce extra jitter and wanderthat must be filtered by any IEEE 1588 clock.
e)
For full-duplex Ethernet links, gPTP requires the use of the peer-to-peer delay mechanism, whileIEEE Std 1588-2019 also allows the use of end-to-end delay measurement.
f)
For full-duplex Ethernet links, gPTP requires the use of two-step processing (use of Follow_Up andPdelay_Resp_Follow_Up messages to communicate timestamps), with an optional one-stepprocessing mode that embeds timestamps in the Sync “on the fly” as they are being transmitted(gPTP does not specify one-step processing for peer delay messages). IEEE Std 1588-2019 allowseither two-step or one-step processing to be required (for both Sync and peer delay messages)depending on a specific profile.
g)
All PTP Instances in a gPTP domain are logically syntonized; in other words, they all measure timeintervals using the same frequency. This is done by the process described in 7.3.3 and is mandatory. Syntonization in IEEE Std 1588-2019 is optional. The syntonization method used by gPTP issupported as an option in IEEE Std 1588-2019, but uses a TLV standardized as part ofIEEEStd1588-2019 (this feature is new for IEEE Std 1588-2019), while gPTP uses theORGANIZATION_EXTENSION TLV specified in 11.4.4.3.
h)
Finally, this standard includes formal interface definitions, including primitives, for the time-awareapplications (see Clause9). IEEE Std 1588-2019 describes external interfaces without describingspecific interface primitives.Authorized licensed use limited to: East China Normal University. Downloaded on July 08,2020 at 12:52:03 UTC from IEEE Xplore. Restrictions apply.