Home > other >  IEEE1588 protocol P2PTC port clock module is what role
IEEE1588 protocol P2PTC port clock module is what role

Time:10-08

Want to know to answer the following
6.5.5 Peer - to - Peer transparent clocks
The peer - to - peer transparent clock has an additional per port block as indicated in Figure 7. This block is
2 compute the link delay between each port and a similarly equipped port on another node sharing the
, i.e. for the link, the link peer. The link peer exists in another clock supporting the peer delay mechanism since
Non - peer - to - peer devices are not expected between peer - to - peer transparent clocks. The computation of The link
Delay is on an exchange of Pdelay_Req, Pdelay_Resp, and possibly Pdelay_Resp_Follow_Up
The messages with the link peer. As a result of these exchanges, the link delay is known for each port of the
Peer - to - peer transparent clock. Unlike the end - to - end transparent clock, which corrects and recently all
Inhibits PTP timing messages, the peer - to - peer transparent clock only corrects the and recently Sync and Follow_Up
Messages. The appropriate correctionField in these messages is for both The residence time of The
The Sync message within the peer - to - peer transparent clock and the link delay on the port identifiers the Sync
Message.
Is this section, the meaning of P2P and E2ETC have time module, just the way to handle the message, but P2P meet Follow - up news will lose directly, how correction, another As a result of these exchanges, the link delay is known for each port of the peer - to - peer transparent clock. P2P know link delay, E2ETC also know, so don't understand why can from these two aspects to illustrate the high precision time synchronization of P2P than E2E

CodePudding user response:

I just see the 1588 agreement, in theory, the master clock is need to send contains real sync frame send follow_up of time frame, in fact, many products are hardware realizing the function of the timestamp, timestamp can record actually sent moments of sync, so there is no need for follow_up, end - to - end of transparent clock is fixed and forward all inhibits PTP time information, peer - to - peer transparent clock correction and forward only
  • Related