[go: up one dir, main page]

WO2024189862A1 - Dispositif de transfert, procédé de transfert et programme - Google Patents

Dispositif de transfert, procédé de transfert et programme Download PDF

Info

Publication number
WO2024189862A1
WO2024189862A1 PCT/JP2023/010183 JP2023010183W WO2024189862A1 WO 2024189862 A1 WO2024189862 A1 WO 2024189862A1 JP 2023010183 W JP2023010183 W JP 2023010183W WO 2024189862 A1 WO2024189862 A1 WO 2024189862A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
pdelay
time
resp
delay
Prior art date
Application number
PCT/JP2023/010183
Other languages
English (en)
Japanese (ja)
Inventor
佳祐 山形
慎一 吉原
尊広 久保
隆 中西
Original Assignee
日本電信電話株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電信電話株式会社 filed Critical 日本電信電話株式会社
Priority to PCT/JP2023/010183 priority Critical patent/WO2024189862A1/fr
Publication of WO2024189862A1 publication Critical patent/WO2024189862A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter

Definitions

  • This disclosure relates to a transfer device, a transfer method, and a program.
  • the Precision Time Protocol defined in the IEEE-1588 standard is a protocol that synchronizes the time (internal device time) of computers on a Local Area Network (LAN) with high precision (see Non-Patent Document 1).
  • Figures 4A and 4B show an example configuration of a time synchronization system 10A that uses PTP to synchronize the time of devices on a network.
  • the time synchronization system 10A includes a Grand Master Clock 1 and a Client device 2.
  • the Grand Master Clock 1 is equipped with a GNSS antenna 1a that receives signals (GNSS signals) from satellites of the Global Navigation Satellite System (GNSS), such as the Global Positioning System (GPS).
  • GNSS Global Navigation Satellite System
  • GPS Global Positioning System
  • the Grand Master Clock 1 receives the GNSS signals via the GNSS antenna 1a and acquires Universal Time Coordinated (UTC) from the received GNSS signals.
  • the Grand Master Clock 1 has a master function that distributes the acquired UTC as the reference time via the network.
  • the client device 2 has a slave function that synchronizes the internal time of the device with the time distributed from a device with a master function.
  • the client device 2 is a device used by a user, such as a base station device in a mobile phone network.
  • a relay device that relays signals may be installed between the Grand Master Clock 1 and the Client device 2 depending on the distance between the Grand Master Clock 1 and the Client device 2 and the number of Client devices 2 that are synchronized with the Grand Master Clock 1.
  • Relay devices that can be used with PTP include the Boundary Clock 3 shown in Figure 4A and the Transparent Clock 4 shown in Figure 4B.
  • the Boundary Clock 3 shown in FIG. 4A functions as a device with a slave function for synchronizing its own internal time with the time distributed from a higher-level device with a master function, and functions as a device with a master function for a lower-level device with a slave function.
  • the Boundary Clock 3 functions as a device with a slave function for the Grand Master Clock 1, and functions as a device with a master function for the Client device 2.
  • the Boundary Clock 3 measures the offset, which is the difference between the internal time of the higher-level device, Grand Master Clock 1, and the internal time of its own device (the difference between the internal time of the device with the master function and the internal time of the device with the slave function), by sending and receiving PTP packets with the Grand Master Clock 1, and synchronizes the internal time of its own device with the time distributed from the Grand Master Clock 1 (reference time) based on the measured offset.
  • the Boundary Clock 3 synchronizes the internal time of the Client device 2 with the internal time of its own device by sending and receiving PTP packets with the Client device 2.
  • Transparent Clock 4 shown in Figure 4B transfers PTP packets received from the higher-level device, Grand Master Clock 1, to the lower-level device, Client device 3, and transfers PTP packets received from the lower-level device, Client device 3, to the higher-level device, Grand Master Clock 1.
  • Transparent Clock 4 measures the time it takes for a PTP packet to pass through its own device, and writes the result into the PTP packet while transferring it. In this way, the internal time of Client device 2 can be synchronized with the internal time of Grand Master Clock 1.
  • IEEE Std 1588TM-2008 “IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems”
  • the purpose of this disclosure is to provide a transfer device, a transfer method, and a program that can enable time synchronization between devices using different profiles, in particular between a higher-level device that performs time synchronization by sending and receiving messages using a Peer-to-Peer method, and a lower-level device that performs time synchronization by sending and receiving messages using an End-to-End method.
  • the transfer device disclosed herein is a transfer device that transfers messages between a higher-level device that performs time synchronization by transmitting and receiving messages in a Peer to Peer manner and a lower-level device that performs time synchronization by transmitting and receiving messages in an End to End manner, and includes a first message processing unit that receives a Sync message transmitted from the higher-level device and transmits it to the lower-level device, and obtains the reception time dt1 of the Sync message and the transmission time dt2 of the Sync message to the lower-level device, a second message processing unit that receives a Follow_Up message transmitted from the higher-level device and transmits the Follow_Up message to the lower-level device, including the difference between the transmission time dt2 and the reception time dt1, and a Delay_Req transmitted from the lower-level device.
  • the device is provided with a third message processing unit that receives a message and acquires the reception time dt3 of the Delay_Req message, a first message conversion unit that converts the Delay_Req message into a Pdelay_Req message of the Peer to Peer method, transmits the message to the higher-level device, and acquires the transmission time dt4 of the Pdelay_Req message, a fourth message processing unit that receives a Pdelay_Resp message transmitted from the higher-level device, and includes in the Pdelay_Resp message the difference between the transmission time dt4 and the reception time dt3, and a second message conversion unit that converts the Pdelay_Resp message, including the difference between the transmission time dt4 and the reception time dt3, into a Delay_Resp message of the End to End method, and transmits the message to the lower-level device.
  • a third message processing unit that receives a message and acquires the reception time dt3 of the De
  • the transfer method disclosed herein is a transfer method by a transfer device that transfers messages between an upper device that performs time synchronization by transmitting and receiving messages using a Peer to Peer method and a lower device that performs time synchronization by transmitting and receiving messages using an End to End method, and includes the steps of receiving a Sync message transmitted from the upper device and transmitting it to the lower device, acquiring the reception time dt1 of the Sync message and the transmission time dt2 of the Sync message to the lower device, receiving a Follow_Up message transmitted from the upper device and transmitting the Follow_Up message to the lower device including the difference between the transmission time dt2 and the reception time dt1, and
  • the method includes the steps of receiving a Delay_Req message sent from the higher-level device and acquiring the reception time dt3 of the Delay_Req message, converting the Delay_Req message into a Pdelay_Req message of the Peer to Peer method, transmitting the message to the higher
  • the program disclosed herein causes a computer to operate as the above-mentioned transfer device.
  • the transfer device, transfer method, and program disclosed herein enable time synchronization between devices using different profiles, in particular between a higher-level device that performs time synchronization by sending and receiving messages using a Peer-to-Peer method, and a lower-level device that performs time synchronization by sending and receiving messages using an End-to-End method.
  • FIG. 2 is a diagram illustrating a configuration example of a transfer device according to an embodiment of the present disclosure.
  • 2 is a sequence diagram illustrating an example of an operation of the transfer device illustrated in FIG. 1 .
  • 2 is a sequence diagram illustrating an example of a hardware configuration of the transfer device illustrated in FIG. 1 .
  • FIG. 1 illustrates an example of a time synchronization system.
  • FIG. 11 illustrates another example of a time synchronization system.
  • This is a sequence diagram showing an example of the operation of a Transparent Clock when the End to End method is used.
  • This is a sequence diagram showing an example of the operation of a Transparent Clock when the Peer to Peer method is used.
  • FIG. 5 is a sequence diagram showing an example of the operation of Transparent Clock 4 when a Master device and a Client device perform time synchronization by sending and receiving messages using the End to End method.
  • the Master device is a device with a Master function, such as Grand Master Clock 1 shown in Figure 4B
  • the Client device is Client device 2 such as a wireless base station shown in Figure 4B.
  • Figure 5 explains the case where the two-step method is used.
  • the Master device sends a Sync message to Transparent Clock 4 (step S101).
  • Messages sent and received between devices in PTP include a field called correctionField (CF), which contains a correction value used for time correction (for example, a value obtained by adding the time it takes for a frame to pass through the device).
  • CF correctionField
  • Transparent Clock 4 When Transparent Clock 4 receives the Sync message at time dt1, it transmits the received Sync message to the Client device at time dt2 (step S102). Transparent Clock 4 leaves the CF of the Sync message at 0. Transparent Clock 4 also stores the reception time dt1 of the Sync message from the Master device and the transmission time dt2 of the Sync message to the Client device.
  • the client device receives the Sync message sent from Transparent Clock 4 at time T2.
  • the client device stores the time T2 when the Sync message was received.
  • the Master device After sending the Sync message, the Master device sends a Follow_Up message to Transparent Clock 4 (step S103).
  • the Master device includes the sending time T1 of the Sync message in the Follow_Up message.
  • the Master device also sets CF of the Follow_Up message to 0.
  • the client device When the client device receives the Sync message and the Follow_Up message, it transmits a Delay_Req message to Transparent Clock 4 at time T3 (step S105).
  • the client device includes the transmission time T3 of the Delay_Req message in the Delay_Req message.
  • the client device also sets CF of the Delay_Req message to 0.
  • Transparent Clock 4 When Transparent Clock 4 receives the Delay_Req message at time dt3, it transmits the received Delay_Req message to the Master device at time dt4 (step S106). Transparent Clock 4 leaves the CF of the Delay_Req message at 0. Transparent Clock 4 also stores the reception time dt3 of the Delay_Req message from the Client device and the transmission time dt4 of the Delay_Req message to the Master device.
  • the Master device receives the Delay_Req message sent from Transparent Clock 4.
  • the Master device stores the time T4 at which the Delay_Req message was received.
  • the master device When the master device receives the Delay_Req message, it sends a Delay_Resp message to Transparent Clock 4 (step S107).
  • the master device includes the reception time T4 of the Delay_Req message in the Delay_Resp message.
  • the client device sets CF of the Delay_Resp message to 0.
  • Offset ((T2-T1-(dt2-dt1))-(T4-T3-(dt4-dt3)))/2
  • the client device can synchronize its internal time with the internal time of the master device by correcting the internal time based on the calculated offset.
  • Figure 6 is a sequence diagram showing an example of the operation of Transparent Clock 4 when a Master device and a Client device perform time synchronization by sending and receiving messages using the Peer to Peer method.
  • Figure 6 explains the case where the two-step method is used.
  • Transparent Clock 4 transmits a Pdelay_Req message to the Master device at time t1 (step S201).
  • Transparent Clock 4 sets CF of the Pdelay_Req message to 0.
  • Transparent Clock 4 also stores the transmission time t1 of the Pdelay_Req message to the Master device.
  • the master device receives the Pdelay_Req message at time t2.
  • the master device stores the time t2 when it received the Pdelay_Req message from Transparent Clock 4.
  • the master device When the master device receives the Pdelay_Req message, it transmits a Pdelay_Resp message to Transparent Clock 4 at time t3 (step S202).
  • the master device includes the reception time t2 of the Pdelay_Req message in the Pdelay_Resp message.
  • the master device also sets the CF of the Pdelay_Resp message to 0.
  • the master device also stores the transmission time t3 of the Pdelay_Resp message to Transparent Clock 4.
  • the master device After sending the Pdelay_Resp message, the master device sends a Pdelay_Resp_Follow_Up message to Transparent Clock 4 (step S203).
  • the master device includes the sending time t3 of the Pdelay_Resp message to Transparent Clock 4 in the Pdelay_Resp_Follow_Up message.
  • the master device also sets CF of the Pdelay_Resp_Follow_Up message to 0.
  • the Transparent Clock 4 receives the Pdelay_Resp message at time t4.
  • the Transparent Clock 4 stores the reception time t4 of the Pdelay_Resp message from the Master device.
  • the Transparent Clock 4 also receives the Pdelay_Resp_Follow_Up message.
  • the Transparent Clock 4 calculates the transmission delay time pt1 between the Master device and the Transparent Clock 4 using the following formula (2) based on the transmission time t1 of the Pdelay_Req message by the Transparent Clock 4, the reception time t2 of the Pdelay_Req message by the Master device, which is included in the Pdelay_Resp message, the transmission time t3 of the Pdelay_Resp message by the Master device, which is included in the Pdelay_Resp_Follow_Up message, and the reception time t4 of the Pdelay_Resp message by the Transparent Clock 4.
  • pt1 ((t2-t1) + (t4-t3))/2 Equation (2)
  • the client device transmits a Pdelay_Req message to Transparent Clock 4 (step S204).
  • the client device sets CF of the Pdelay_Req message to 0.
  • the client device also stores the transmission time t5 of the Pdelay_Req message to Transparent Clock 4.
  • Transparent Clock 4 receives the Pdelay_Req message at time t6. Transparent Clock 4 stores the time t6 when the Pdelay_Req message was received from the Client device.
  • Transparent Clock 4 When Transparent Clock 4 receives the Pdelay_Req message, it transmits a Pdelay_Resp message to the Client device at time t7 (step S205).
  • Transparent Clock 4 includes the reception time t6 of the Pdelay_Req message from the Client device in the Pdelay_Resp message.
  • Transparent Clock 4 also sets CF of the Pdelay_Resp message to 0.
  • Transparent Clock 4 also stores the transmission time t7 of the Pdelay_Resp message to the Client device.
  • Transparent Clock 4 After transmitting the Pdelay_Resp message, Transparent Clock 4 transmits a Pdelay_Resp_Follow_Up message to the Client device (step S206). Transparent Clock 4 includes in the Pdelay_Resp_Follow_Up message the transmission time t7 of the Pdelay_Resp message to the Client device. Transparent Clock 4 also sets CF of the Pdelay_Resp_Follow_Up message to 0.
  • the client device receives the Pdelay_Resp message at time t8.
  • the client device stores the reception time t8 of the Pdelay_Resp message from Transparent Clock 4.
  • the client device also receives the Pdelay_Resp_Follow_Up message.
  • the client device calculates the transmission delay time pt2 between Transparent Clock 4 and the client device using the following formula (3) based on the transmission time t5 of the Pdelay_Req message by the client device, the reception time t6 of the Pdelay_Req message by Transparent Clock 4 which is included in the Pdelay_Resp message, the transmission time t7 of the Pdelay_Resp message by Transparent Clock 4 which is included in the Pdelay_Resp_Follow_Up message, and the reception time t8 of the Pdelay_Resp message by the client device.
  • pt2 ((t6-t5)+(t8-t7))/2
  • the Master device After the transmission delay times pt1 and pt2 are calculated, the Master device sends a Sync message to Transparent Clock 4 at time T1 (step S207). The Master device sets CF of the Sync message to 0.
  • Transparent Clock 4 When Transparent Clock 4 receives the Sync message at time dt1, it transmits the received Sync message to the Client device at time dt2 (step S208). Transparent Clock 4 leaves the CF of the Sync message at 0. Transparent Clock 4 also stores the reception time dt1 of the Sync message from the Master device and the transmission time dt2 of the Sync message to the Client device.
  • the client device receives the Sync message sent from Transparent Clock 4.
  • the Master device After sending the Sync message, the Master device sends a Follow_Up message to Transparent Clock 4 (step S209).
  • the Master device includes in the Follow_Up message the sending time T1 of the Sync message to Transparent Clock 4.
  • the Master device also sets CF of the Follow_Up message to 0.
  • T2 T1+pt1+(dt2-dt1)+pt2 Formula (4)
  • the client device synchronizes its internal time with the calculated reception time T2 of the Sync message. This allows the client device's internal time to be synchronized with the master device's internal time.
  • the transmission time T1 of the Sync message by the Master device can be included in the Sync message.
  • the CF of the Sync message can be set to the sum (pt1+(dt2-dt1)) of the transmission delay time pt1 between the Master device and Transparent Clock 4 and the processing time of the Sync message in Transparent Clock 4 (dt2-dt1).
  • the transmission time t3 of the Pdelay_Resp message by the Master device and the transmission time t7 of the Pdelay_Resp message by Transparent Clock 4, which were included in the Pdelay_Resp_Follow_Up message, can be set in the CF of the Pdelay_Resp message.
  • the transfer device 100 transfers messages between a Grand Master Clock 1 (higher-level device) which is a master device, and a Client device 2 (lower-level device) in a time synchronization system 10 in which the two perform time synchronization.
  • the Grand Master Clock 1 performs time synchronization by sending and receiving messages using the Peer to Peer method
  • the Client device 2 performs time synchronization by sending and receiving messages using the End to End method.
  • the transfer device 100 transfers messages between a higher-level device which performs time synchronization by sending and receiving messages using the Peer to Peer method, and a lower-level device which performs time synchronization by sending and receiving messages using the End to End method.
  • FIG. 2 is a sequence diagram showing an example of the operation of the transfer device 100 according to this embodiment, and is a diagram for explaining the transfer method by the transfer device 100.
  • the transfer device 100 transfers messages between a Master device (Grand Master Clock 1) that performs time synchronization by sending and receiving messages using the Peer to Peer method, and a Client device (Client device 2) that performs time synchronization by sending and receiving messages using the End to End method.
  • a Master device Gram Master Clock 1
  • Client device 2 Client device 2
  • Figure 2 describes the case where the two-step method is used.
  • the master device transmits a Sync message to the transfer device 100 (step S301).
  • the master device sets the CF of the Sync message to 0.
  • the transfer device 100 When the transfer device 100 receives a Sync message at time dt1, it transmits the Sync message to the Client device at time dt2 (step S302). The transfer device 100 leaves the CF of the Sync message at 0. The transfer device 100 also stores the time dt1 when the Sync message was received from the Master device and the time dt2 when the Sync message was transmitted to the Client device.
  • the client device receives the Sync message at time T2.
  • the client device stores the time T2 at which the Sync message was received from the transfer device 100.
  • the master device After sending the Sync message, the master device sends a Follow_Up message to the transfer device 100 (step S303).
  • the master device includes in the Follow_Up message the sending time T1 of the Sync message to the transfer device 100.
  • the master device also sets CF of the Follow_Up message to 0.
  • the client device When the client device receives the Follow_Up message, it transmits a Delay_Req message to the transfer device 100 at time T3 (step S305).
  • the client device includes the transmission time T3 of the Delay_Req message in the Delay_Req message.
  • the client device also sets CF of the Delay_Req message to 0.
  • the transfer device 100 receives a Delay_Req message at time dt3.
  • the transfer device 100 stores the reception time dt3 of the Delay_Req message from the client device. Because the Delay_Req message is an end-to-end message, the transfer device 100 converts the Delay_Req message into a peer-to-peer Pdelay_Req message that can be processed by the master device, and transmits the Pdelay_Req message to the master device at time dt4 (step S306).
  • the transfer device 100 sets the CF of the Pdelay_Req message to 0.
  • the transfer device 100 stores the transmission time dt4 of the Pdelay_Req message to the master device.
  • the master device When the master device receives the Pdelay_Req message at time T4, it transmits a Pdelay_Resp message to the transfer device 100 at time t5 (step S307).
  • the master device includes the reception time T4 of the Pdelay_Req message from the transfer device 100 in the Pdelay_Resp message.
  • the master device sets the CF of the Pdelay_Resp message to 0.
  • the master device also stores the transmission time t5 of the Pdelay_Resp message.
  • the master device After transmitting the Pdelay_Resp message, the master device transmits a Pdelay_Resp_Follow_Up message to the transfer device 100 (step S309).
  • the master device includes in the Pdelay_Resp_Follow_Up message the transmission time t5 of the Pdelay_Resp message to the transfer device 100.
  • the master device also sets the CF of the Pdelay_Resp_Follow_Up message to 0.
  • the transfer device 100 receives the Pdelay_Resp_Follow_Up message but does not forward it to the client device.
  • Offset ((T2-T1-(dt2-dt1))-(T4-T3-(dt4-dt3)))/2 (Equation 5)
  • the client device synchronizes its own internal time with the internal time of the master device based on the calculated offset.
  • the transmission time T1 of the Sync message by the Master device and the processing time of the Sync message by the transfer device 100 can be included in the Sync message.
  • the transmission time t5 of the Pdelay_Resp message by the Master device, which was included in the Pdelay_Resp_Follow_Up message can be included in the Pdelay_Resp message.
  • the above-described process enables messages to be virtually sent and received between the Master device and the Client device using the End to End method, thereby enabling time synchronization between devices using different profiles, in particular between a higher-level device using Peer to Peer and a lower-level device using End to End.
  • FIG. 1 shows an example in which the higher-level device is Grand Master Clock 1 and the lower-level device is Client device 2, but the present disclosure is not limited to this.
  • the higher-level device may be a device with a master function
  • the lower-level device may be a device with a slave function.
  • the higher-level device and the lower-level device may be Boundary Clock 3.
  • the transfer device 100 includes packet transmission/reception units 101, 102, a Sync message processing unit 103, a Follow_Up message processing unit 104, a Delay_Req message processing unit 105, a Pdelay_Req message conversion unit 106, a Pdelay_Resp message processing unit 107, a Delay_Resp message conversion unit 108, and a Pdelay_Resp_Follow_Up message processing unit 109.
  • the packet transmission/reception unit 101 transmits and receives PTP packets (messages) with the Grand Master Clock 1, which is a higher-level device.
  • the packet transmission/reception unit 102 transmits and receives PTP packets (messages) with the Client device 2, which is a lower-level device.
  • the Sync message processing unit 103 acting as the first message processing unit, receives the Sync message sent from the Grand Master Clock 1 via the packet transmitting/receiving unit 101, and transmits it to the Client device 2 via the packet transmitting/receiving unit 102.
  • the CF of the Sync message is set to 0, and the Sync message processing unit 103 transfers the Sync message to the Client device 2 with the CF of the Sync message remaining at 0.
  • the Sync message processing unit 103 also obtains the reception time dt1 of the Sync message by the transfer device 100 and the transmission time dt2 of the Sync message to the Client device 2, and outputs these to the Follow_Up message processing unit 104.
  • the Follow_Up message processing unit 104 which serves as the second message processing unit, receives the Follow_Up message transmitted from the Grand Master Clock 1 via the packet transmitting/receiving unit 101, and transmits it to the Client device 2 via the packet transmitting/receiving unit 102.
  • the Follow_Up message processing unit 104 includes in the Follow_Up message the processing time of the Sync message by the transfer device 100, i.e., the difference between the transmission time dt2 of the Sync message to the Client device 2 and the reception time dt1 of the Sync message by the transfer device 100, and transmits it to the Client device 2.
  • the Delay_Req message processing unit 105 which serves as a third message processing unit, receives the Delay_Req message sent from the Client device 2 via the packet transmitting/receiving unit 102, and outputs it to the Pdelay_Req message conversion unit 106.
  • the Delay_Req message processing unit 105 also acquires the reception time dt3 of the Delay_Req message by the transfer device 100, and outputs it to the Pdelay_Resp message processing unit 107.
  • the Pdelay_Req message conversion unit 106 acting as the first message conversion unit, converts the Delay_Req message output from the Delay_Req message processing unit 105 into a Peer to Peer type Pdelay_Req message that can be processed by the Grand Master Clock 1, and transmits it to the Grand Master Clock 1 via the packet transmission/reception unit 101.
  • the message header of a PTP packet has a field called "Message Type", in which a value indicating each message is set.
  • the Pdelay_Req message conversion unit 106 converts the Delay_Req message into a Pdelay_Req message by changing the Message Type of the Delay_Req message to a value indicating a Pdelay_Req message.
  • the CF of the Delay_Req message is set to 0, and the Pdelay_Req message conversion unit 106 leaves the CF of the Pdelay_Req message at 0.
  • the Pdelay_Req message conversion unit 106 also stores the transmission time dt4 of the Pdelay_Req message to Grand Master Clock 1.
  • the Pdelay_Resp message processing unit 107 acting as the fourth message processing unit, receives the Pdelay_Resp message transmitted from Grand Master Clock 1 via the packet transmitting/receiving unit 101, and outputs it to the Delay_Resp message conversion unit 108.
  • the Pdelay_Resp message processing unit 107 includes in the Pdelay_Resp message the processing time of the Delay_Req message by the transfer device 100, i.e., the difference between the transmission time dt4 of the Delay_Req message to Grand Master Clock 1 and the reception time dt3 of the Delay_Req message by the transfer device 100, and outputs it to the Delay_Resp message conversion unit 108.
  • the Delay_Resp message conversion unit 108 acting as the second message conversion unit, converts the Pdelay_Resp message output from the Pdelay_Resp message processing unit 107, which includes the difference between the transmission time dt4 of the Delay_Req message to Grand Master Clock 1 and the reception time dt3 of the Delay_Req message by the transfer device 100, into an end-to-end Delay_Resp message that can be processed by the Client device 2, and transmits it to the Client device 2 via the packet transmission/reception unit 102.
  • the message header of a PTP packet has a field called "Message Type", in which a value indicating each message is set.
  • the Pdelay_Resp_Follow_Up message processing unit 109 which serves as the fifth message processing unit, receives the Pdelay_Resp_Follow_Up message sent from the Grand Master Clock 1 via the packet transmitting/receiving unit 101, but does not forward it to the Client device.
  • the Master device (Grand Master Clock 1) transmits a Pdelay_Resp_Follow_Up message including the transmission time t3 of the Pdelay_Resp message.
  • the transmission time t3 of the Pdelay_Resp message is used to calculate the transmission delay time pt1 between the Master device and Transparent Clock 4.
  • the transmission time t5 of the Pdelay_Resp message by Grand Master Clock 1 is not necessary for calculating the offset, which is the difference between the device internal time of the Client device and the device internal time of the Master device. Therefore, by having the Pdelay_Resp_Follow_Up message processing unit 109 not transmit the Pdelay_Resp_Follow_Up message to the Client device 2, it is possible to reduce the transmission and reception of unnecessary messages. Also, Grand Master Clock 1 may transmit a Pdelay_Resp message after transmitting a Pdelay_Resp message, as in the case of using the conventional Peer to Peer method. Therefore, since Grand Master Clock 1 only needs to perform the same processing as when using the conventional Peer to Peer method, there is no need to modify Grand Master Clock 1, and it is possible to suppress increases in costs.
  • the transfer device 100 can virtually send and receive messages between the Master device and the Client device using the End to End method, thereby enabling time synchronization between devices using different profiles, in particular between a higher-level device using Peer to Peer and a lower-level device using End to End.
  • FIG. 3 is a diagram showing an example of the hardware configuration of the transfer device 100 according to this embodiment.
  • FIG. 3 shows an example of the hardware configuration of the transfer device 100 when the transfer device 100 is configured by a computer capable of executing program instructions.
  • the computer may be a general-purpose computer, a dedicated computer, a workstation, a PC (Personal computer), an electronic notepad, etc.
  • the program instructions may be program code, code segments, etc. for performing the required tasks.
  • the transfer device 100 has a processor 201, a ROM (Read Only Memory) 202, a RAM (Random Access Memory) 203, storage 204, an input unit 205, a display unit 206, and a communication interface (I/F) 207.
  • the processor 201 is a CPU (Central Processing Unit), MPU (Micro Processing Unit), GPU (Graphics Processing Unit), DSP (Digital Signal Processor), SoC (System on a Chip), etc., and may be composed of multiple processors of the same or different types.
  • the processor 201 is a control unit that controls each component and executes various calculation processes. That is, the processor 201 reads a program from the ROM 202 or the storage 204, and executes the program using the RAM 203 as a working area. The processor 201 controls each component and executes various calculation processes according to the program stored in the ROM 202 or the storage 204. In this embodiment, the ROM 202 or the storage 204 stores a program for operating a computer as the transfer device 100 according to the present disclosure.
  • the program is read and executed by the processor 201, thereby realizing each component of the transfer device 100, for example, the Sync message processing unit 103, the Follow_Up message processing unit 104, the Delay_Req message processing unit 105, the Pdelay_Req message conversion unit 106, the Pdelay_Resp message processing unit 107, the Delay_Resp message conversion unit 108, and the Pdelay_Resp_Follow_Up message processing unit 109.
  • the program may be provided in a form stored on a non-transitory storage medium such as a CD-ROM (Compact Disk Read Only Memory), a DVD-ROM (Digital Versatile Disk Read Only Memory), or a USB (Universal Serial Bus) memory.
  • a non-transitory storage medium such as a CD-ROM (Compact Disk Read Only Memory), a DVD-ROM (Digital Versatile Disk Read Only Memory), or a USB (Universal Serial Bus) memory.
  • the program may also be provided via a network.
  • ROM 202 stores various programs and data.
  • RAM 203 temporarily stores programs or data as a working area.
  • Storage 204 is composed of a HDD (Hard Disk Drive) or SSD (Solid State Drive), and stores various programs and data including the operating system.
  • the input unit 205 includes a pointing device such as a mouse and a keyboard, and is used to perform various input operations.
  • the display unit 206 is, for example, a liquid crystal display, and displays various information.
  • the display unit 206 may also function as the input unit 205 by adopting a touch panel system.
  • the communication interface 207 is an interface for communicating with other devices (e.g., the Grand Master Clock 1 and the Client device 2), and is, for example, an interface for a LAN.
  • the packet transmission/reception units 101 and 102 are, for example, configured with the communication interface 207.
  • a computer can be suitably used to function as each part of the transfer device 100 described above.
  • Such a computer can be realized by storing a program describing the processing contents for realizing the functions of each part of the transfer device 100 in the memory of the computer, and having the processor of the computer read and execute this program.
  • the program can cause the computer to function as the transfer device 100 described above.
  • the program can also be stored in a non-transitory storage medium.
  • the program can also be provided via a network.
  • a transfer device that transfers messages between a higher-level device that performs time synchronization by transmitting and receiving messages in a Peer-to-Peer manner and a lower-level device that performs time synchronization by transmitting and receiving messages in an End-to-End manner
  • a control unit is provided, The control unit is Receive a Sync message transmitted from a higher-level device and transmit it to the lower-level device, and obtain a reception time dt1 of the Sync message and a transmission time dt2 of the Sync message to the lower-level device; receiving a Follow_Up message transmitted from the higher-level device, and transmitting the Follow_Up message including the difference between the transmission time dt2 and the reception time dt1 to the lower-level device; Receive a Delay_Req message transmitted from the lower device, and obtain a reception time dt3 of the Delay_Req message; converting the Delay_Req message into a Pdelay_Req message of the Peer to Peer method
  • a method for transferring messages between a higher-level device that performs time synchronization by transmitting and receiving messages in a Peer-to-Peer manner and a lower-level device that performs time synchronization by transmitting and receiving messages in an End-to-End manner comprising: Receive a Sync message transmitted from the upper device and transmit it to the lower device, and obtain a reception time dt1 of the Sync message and a transmission time dt2 of the Sync message to the lower device; receiving a Follow_Up message transmitted from the higher-level device, and transmitting the Follow_Up message including the difference between the transmission time dt2 and the reception time dt1 to the lower-level device; Receive a Delay_Req message transmitted from the lower device, and obtain a reception time dt3 of the Delay_Req message; converting the Delay_Req message into a Pdelay_Req message of the Peer to Peer method and transmitting the Pdelay_Req message to the higher
  • a non-transitory storage medium storing a program executable by a computer, the non-transitory storage medium storing the program causing the computer to operate as the transfer device according to claim 1 or 2.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)

Abstract

La présente divulgation concerne un dispositif de transfert (100) qui : reçoit un message Sync en provenance d'un dispositif d'ordre supérieur et transmet le message Sync à un dispositif subordonné ; reçoit un message Follow_Up transmis à partir du dispositif d'ordre supérieur ; transmet, au dispositif subordonné, le message Follow_Up dans lequel est incluse la différence entre le moment de transmission dt2 de la transmission du message Sync au dispositif subordonné et le moment de réception dt1 de la réception du message Sync ; reçoit un message Delay_Req en provenance du dispositif subordonné ; convertit le message Delay_Req en un message Pdelay_Req et transmet le message Pdelay_Req au dispositif d'ordre supérieur ; reçoit un message Pdelay_Resp en provenance du dispositif d'ordre supérieur ; inclut, dans le message Pdelay_Resp, la différence entre le moment de transmission dt4 de la transmission du message Pdelay_Req et le moment de réception dt3 de la réception du message Delay_Req ; et convertit le message Pdelay_Resp comprenant la différence entre le moment de transmission dt4 et le moment de réception dt3 en un message Delay_Resp, et transmet le message Delay_Resp au dispositif subordonné.
PCT/JP2023/010183 2023-03-15 2023-03-15 Dispositif de transfert, procédé de transfert et programme WO2024189862A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/010183 WO2024189862A1 (fr) 2023-03-15 2023-03-15 Dispositif de transfert, procédé de transfert et programme

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/010183 WO2024189862A1 (fr) 2023-03-15 2023-03-15 Dispositif de transfert, procédé de transfert et programme

Publications (1)

Publication Number Publication Date
WO2024189862A1 true WO2024189862A1 (fr) 2024-09-19

Family

ID=92754936

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/010183 WO2024189862A1 (fr) 2023-03-15 2023-03-15 Dispositif de transfert, procédé de transfert et programme

Country Status (1)

Country Link
WO (1) WO2024189862A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014505444A (ja) * 2011-02-10 2014-02-27 アルカテル−ルーセント パケット交換ネットワークのためのネットワーク要素
JP2019146060A (ja) * 2018-02-22 2019-08-29 オムロン株式会社 通信システム、通信装置および通信方法
JP2020184710A (ja) * 2019-05-09 2020-11-12 株式会社日立製作所 通信制御装置および通信制御方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014505444A (ja) * 2011-02-10 2014-02-27 アルカテル−ルーセント パケット交換ネットワークのためのネットワーク要素
JP2019146060A (ja) * 2018-02-22 2019-08-29 オムロン株式会社 通信システム、通信装置および通信方法
JP2020184710A (ja) * 2019-05-09 2020-11-12 株式会社日立製作所 通信制御装置および通信制御方法

Similar Documents

Publication Publication Date Title
US8081663B2 (en) Time synchronization method and relay apparatus
US20090086764A1 (en) System and method for time synchronization on network
WO2013051447A1 (fr) Dispositif de commande temporelle, procédé de commande temporelle et programme
WO2021077289A1 (fr) Procédé et dispositif de synchronisation
EP3541123A1 (fr) Dispositif sans fil, procédé de traitement de dispositif sans fil, et programme
CN113645686A (zh) 一种带运动补偿的无线自组织网络时间同步方法
US11336510B2 (en) Information processing system, information processing method, and non-transitory recording medium
WO2024189862A1 (fr) Dispositif de transfert, procédé de transfert et programme
WO2024189860A1 (fr) Dispositif de transfert, procédé de transfert et programme
JP7545099B2 (ja) 測定器、測定方法および時刻同期システム
WO2025104815A1 (fr) Dispositif de communication, système de communication, et procédé de communication
WO2025104816A1 (fr) Dispositif de communications, système de communications et procédé de communications
JP7506351B2 (ja) 測定器、測定方法および時刻同期システム
WO2025104814A1 (fr) Dispositif de communication, système de communication et procédé de communication
JP7587194B2 (ja) 時刻同期装置、時刻同期方法およびプログラム
WO2023238203A1 (fr) Dispositif de synchronisation temporelle, système de synchronisation temporelle et procédé de synchronisation temporelle
JP2015117941A (ja) 通信システム、及び時刻同期方法
EP4295514A1 (fr) Détermination d'un temps de séjour dans une partie d'un réseau
KR20220153158A (ko) 링 토폴로지 네트워크에서 정밀 시각 동기 프로토콜에 따른 동기화를 수행하기 위한 방법 및 이를 위한 장치
JP5239752B2 (ja) 同期メッセージ発行システム、同期メッセージ発行方法および同期メッセージ発行プログラム
JP7610168B2 (ja) 時刻同期装置、時刻同期方法およびプログラム
JP2018125768A (ja) データ伝送装置及びプログラム
CN112600641A (zh) 一种网络设备时间同步方法、装置、设备及存储介质
US11968638B2 (en) Providing a clock value to a client device
CN118466691B (zh) 时钟同步方法、装置、设备、介质和产品

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23927481

Country of ref document: EP

Kind code of ref document: A1