Conversion device, conversion program, and conversion method
The conversion device addresses the challenge of achieving time synchronization between PTP devices with different transmission delay measurement methods by converting delay measurement methods, facilitating synchronization and reducing network costs.
Patent Information
- Application Number
- PCT/JP2024/017885
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-29
- Filing Date
- 2024-05-15
- Publication Date
- 2024-12-05
AI Technical Summary
The Precision Time Protocol (PTP) communication between higher-level and lower-level devices fails to achieve time synchronization due to differences in transmission delay measurement methods, such as End-to-End and Peer-to-Peer, which necessitates separate time distribution networks, increasing costs.
A conversion device that processes and converts the transmission delay measurement method of the higher-level device to match that of the lower-level device, enabling time synchronization by calculating and storing necessary delay times in correction fields of messages, allowing for the use of different delay measurement methods between devices.
Enables time synchronization between devices using different transmission delay measurement methods without modifying the higher-level or lower-level devices, reducing the need for separate time distribution networks and lowering equipment costs.
Smart Images

Figure JP2024017885_05122024_PF_FP_ABST
Abstract
Description
Conversion device, conversion program, and conversion method
[0001] The present disclosure relates to a conversion device, a conversion program, and a conversion method for converting a transmission delay measurement method of a higher-level device that performs PTP (Precision Time Protocol) communication into a transmission delay measurement method of a lower-level device when the transmission delay measurement methods differ between the higher-level device and the lower-level device that performs PTP communication.
[0002] The Precision Time Protocol (hereinafter referred to as PTP) defined in Non-Patent Document 1 is a protocol that realizes accurate synchronization of clocks in a packet-based network system.
[0003] In PTP, a format called a profile is defined for each field, and time synchronization cannot be achieved between different profiles. This requires the construction of a separate time distribution network for each field, which increases costs. One of the reasons why time synchronization cannot be achieved between different profiles is the difference in the transmission delay measurement method. Transparent Clock has two types of transmission delay measurement methods, end-to-end and peer-to-peer, and time synchronization is not possible because the messages used for each method are different.
[0004] IEEE Std 1588TM-2019 IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems
[0005] The present disclosure aims to provide a device that enables time synchronization even when two different transmission delay measurement methods, such as end-to-end and peer-to-peer, are used between a higher-level device and a lower-level device that is synchronized with the time of the higher-level device.
[0006] The conversion device according to the present disclosure is a conversion device that converts the transmission delay measurement method of a higher-level device that performs PTP (Precision Time Protocol) communication into the transmission delay measurement method of a lower-level device that performs the PTP communication when the transmission delay measurement methods of the higher-level device and the lower-level device that performs the PTP communication are different. The conversion device according to the present disclosure includes: a Sync message processing unit that receives a Sync message transmitted from the higher-level device and records a reception time dt1, and records a transmission time dt2 of the Sync message when transmitting the Sync message to the lower-level device for relay; a Follow_Up message processing unit that extracts the transmission time T1 of the Sync message from the higher-level device from a Follow_Up message transmitted from the higher-level device in which the transmission time T1 of the Sync message from the higher-level device is stored; a Delay_Req message processing unit that transmits a Delay_Req message to the higher-level device and records the transmission time T3 of the Delay_Req message; and a Delay_Resp message processing unit that extracts the reception time T4 of the Delay_Req message from a Delay_Resp message transmitted from the higher-level device in which the reception time T4 of the Delay_Req message is stored. a Pdelay_Req message processing unit that records a reception time t2 of a Pdelay_Req message transmitted from the lower device; a Pdelay_Resp message processing unit that stores the reception time t2 of the Pdelay_Req message in a Pdelay_Resp message and transmits the Pdelay_Resp message that stores the reception time t2 of the Pdelay_Req message to the lower device; a Pdelay_Resp_Follow_Up message processing unit that stores a transmission time t3 of the Pdelay_Resp message in a Pdelay_Resp_Follow_Up message and transmits the Pdelay_Resp_Follow_Up message that stores the transmission time t3 of the Pdelay_Resp message to the lower device;an upper-side transmission delay calculation unit that calculates a transmission delay time pt1 between the upper device and the conversion device using the reception time dt1 of the Sync message, the transmission time T1 of the Sync message by the upper device, the transmission time T3 of the Delay_Req message, and the reception time T4 of the Delay_Req message; an internal processing time calculation unit that calculates an internal processing time of the conversion device using the reception time dt1 of the Sync message and the transmission time dt2 for relaying the Sync message; and a total value storage unit that stores the sum of the transmission delay time pt1 between the upper device and the conversion device and the internal processing time of the conversion device in a Correction Field of the Follow_Up message, and transmits the Follow_Up message with the stored sum to the lower device for relaying.
[0007] The conversion device according to the present disclosure includes a Delay_Req message processing unit, a Delay_Resp message processing unit, an upper-side transmission delay calculation unit, and a total value storage unit, and therefore enables time synchronization between an upper device and a lower device synchronized with the time of the upper device, even when two different transmission delay measurement methods, such as end-to-end and peer-to-peer, are used.
[0008] 1 is a diagram of the first embodiment, showing the operation of TC101 as a first comparative example of the conversion device 100. FIG. 2 is a diagram of the first embodiment, showing the operation of TC102 as a second comparative example of the conversion device 100. FIG. 3 is a diagram of the first embodiment, explaining the outline of the operation of the conversion device 100, showing an image of converting End to End to Peer to Peer. FIG. 4 is a diagram of the first embodiment, explaining the details of the operation of the conversion device 100. FIG. 5 is a diagram of the first embodiment, explaining each time shown in FIG. 4. FIG. 6 is a diagram of the first embodiment, showing the block configuration of the conversion device 100. FIG. 7 is a diagram of the first embodiment, showing a case of 1 step without a Follow_Up message. FIG. 8 is a diagram of the first embodiment, showing the hardware configuration of the conversion device 100. FIG. 9 is a diagram of the first embodiment, showing a configuration in which the functions of the conversion device 100 are realized by hardware.
[0009] In the description of the embodiments and drawings, the same and corresponding elements are denoted by the same reference numerals. The description of elements denoted by the same reference numerals will be omitted or simplified as appropriate. In the following embodiments, the word "unit" may be read as "circuit," "step," "procedure," "process," or "circuitry" as appropriate.
[0010] Embodiment 1. A conversion device 100 according to embodiment 1 will be described below with reference to the drawings. The conversion device 100 is a device that converts the transmission delay measurement method of a higher-level device performing PTP communication into the transmission delay measurement method of a lower-level device when the transmission delay measurement methods differ between the higher-level device and the lower-level device performing PTP communication. In embodiment 1, the higher-level device is assumed to be a master device 200, and the lower-level device is assumed to be a client device 300. Furthermore, CF described below indicates a "CorrectionField" in a PTP message.
[0011] 1, a transparent clock 101 will be described as a comparative example 1 of the conversion device 100. In FIG. 2, a transparent clock 102 will be described as a comparative example 2 of the conversion device 100. Hereinafter, the transparent clock will be abbreviated as TC.
[0012] FIG. 1 is a diagram illustrating the operation of TC101 in Comparative Example 1. In FIG. 1, a master device 201 and a client device 301 perform a transmission delay measurement method based on end-to-end. TC101 transmits packets based on end-to-end. In FIG. 1, messages are exchanged as follows:
[0013] <Message Exchange from End to End> Step 2 will be explained below. In step 1, the Follow_Up message indicated by the dashed arrow is not used. (1) In step S11, the master device 201 sends a Sync message. (2) In step S12, the master device 201 stores the sending time T1 of the Sync message in the Follow_Up message and sends it. (3) In step S13, TC101 records the time dt1 when the Sync message was received and the time dt2 when the Sync message was sent. (4) In step S14, TC101 stores the internal processing time (dt2 - dt1) in the CF of the Follow_Up message as the processing time within TC101's device (hereinafter referred to as internal processing time) and sends it. (5) In step S15, the client device 301 records the time T2 when it received the Sync message. (6) In step S16, the client device 301 sends a Delay_Req message, storing the transmission time T3 in the Delay_Req message before sending it. (7) In step S17, the TC101 records the time dt3 when it received the Delay_Req message and the time dt4 when it sent it. (8) In step S18, the master device 201 records the time T4 when it received the Delay_Req message. (9) In step S19, the master device 201 sends a Delay_Resp message with T4 included. (10) In step S20, the TC101 stores the internal processing time of TC101 (dt4 - dt3) in the CF of the Delay_Resp message before sending it.
[0014] <Method of Calculating Offset Between Master Device 201 and Client Device 301> Using "T1, T2, T3, T4, dt2-dt1, dt4-dt3" obtained in the above message exchange, the client device 301 can calculate the following offset: Offset = {(T2-T1-(dt2-dt1))-(T4-T3-(dt4-dt3))} / 2 By correcting the time on the client device based on the offset, the client device can synchronize with the time on the master device.
[0015] In the case of 1 step, T1 and the internal processing time (=dt2-dt1) stored in the Follow_Up message are sent in the Sync message.
[0016] 2 is a diagram illustrating the operation of TC 102 in Comparative Example 2. In FIG. 2, a master device 202 and a client device 302 implement a transmission delay measurement method based on peer-to-peer. TC 102 transmits packets based on peer-to-peer. In FIG. 2, messages are exchanged as follows:
[0017] <Peer-to-Peer Message Exchange> Step 2 will be explained below. In step 1, the Follow_Up message indicated by the dashed arrow and the Pdelay_Resp_Follow_Up message indicated by the two dashed arrows are not used. (1) In step S31, TC 102 transmits a Pdelay_Req message to master device 202 and records the transmission time t1. (2) In step S32, master device 202 records the time t2 at which the Pdelay_Req message is received. (3) In step S33, master device 202 transmits a Pdelay_Resp message and records the transmission time t3, and at this time, stores the reception time t2 of the Pdelay_Req message in the Pdelay_Resp message and transmits it. (4) In step S34, the master device 202 stores time t3 in the Pdelay_Resp_Follow_Up message and transmits it. (5) In step S35, the TC 102 records time t4 at which it received the Pdelay_Resp message. (6) In step S36, the TC 102 uses each time (t1, t2, t3, t4) to calculate the transmission delay time pt1 between the master device 20 and the TC 102 using the following formula: Transmission delay time pt1 = {(t2 - t1) + (t4 - t3)} / 2 (7) In step S37, the client device 302 similarly calculates the transmission delay time pt2 between the TC 102 and the client device 302. The same exchanges as in steps S31 to S35 are exchanged between the TC 102 and the client device 302. 2. Transmission delay time pt2={(t6-t5)+(t8-t7)} / 2 (8) In step S38, the master device 202 transmits the Sync message. (9) In step S39, the master device 202 transmits the Sync message transmission time T1 in a Follow_Up message. (10) In step S40, the TC 102 records the time dt1 when the Sync message was received and the time dt2 when the Sync message was transmitted.(11) In step S41, TC102 stores the sum pt1+(dt2-dt1) of the transmission delay time pt1 between the master device 202 and TC102 and the internal processing time (dt2-dt1) of TC102 in the CF of the Follow_Up message and transmits it. (12) Using the transmission delay time pt2 calculated in step S37 and the sum pt1+(dt2-dt1) stored in the CF of the Follow_Up message, client device 302 calculates the time T2 of the client device, which should be synchronized with the transmission time T1 of the Sync message, using the following formula: Client device time T2=T1+pt1+(dt2-dt1)+pt2 The time T2 calculated using the above formula is the time synchronized with the master device 202.
[0018] In the case of 1 step, transmission is performed as follows: The time T1 and the total value (pt1 + (dt2 - dt1)) that were stored and transmitted in the Follow_Up message are transmitted in the Sync message. In this case, the total value is stored in the CF of the Sync message. Furthermore, the times t3 and t7 that were stored and transmitted in the Pdelay_Resp_Follow_Up message are transmitted in the CF of the Pdelay_Resp message.
[0019] 3 is a diagram illustrating an outline of the operation of the conversion device 100 according to the first embodiment. In FIGS. 1 and 2, TC101 (Comparative Example 1) that implements end-to-end and TC102 (Comparative Example 1) that implements peer-to-peer have been described as comparative examples of the conversion device 100. When the master device uses a transmission delay measurement method that supports end-to-end and the client device uses a transmission delay measurement method that supports peer-to-peer, TC101 and TC102 cannot synchronize the time between the master device and the client device.
[0020] In contrast, the conversion device 100 enables time synchronization between the master device and the client device even when the master device uses a transmission delay measurement method corresponding to end-to-end and the client device uses a transmission delay measurement method corresponding to peer-to-peer. In Fig. 3, the transmission delay measurement method is converted from end-to-end to peer-to-peer using the conversion device 100. This allows the client device 300 to synchronize with the time of the master device 200 even in sections using different transmission delay measurement methods.
[0021] According to the conversion device 100, no modifications or settings are required for the master device 200 and the client device 300; message conversion and value rewriting are performed solely by the conversion device 100. In other words, the master device 201 (FIG. 1), which uses an end-to-end transmission delay measurement method, can be used as is for the master device 200. Furthermore, the client device 302 (FIG. 2), which uses a peer-to-peer transmission delay measurement method, can be used as is for the client device 300. The master device 200 exchanges messages as usual (end-to-end). The client device 300 exchanges messages as usual (peer-to-peer). Since there are no restrictions on the master device 200 and the client device 300, the conversion device 100 can be installed between any PTP devices. The time required for the conversion process by the conversion device 100 is added to the normal internal processing time for time synchronization. Therefore, there is no degradation in time accuracy due to the conversion process.
[0022] Fig. 4 is a diagram illustrating the details of the operation of the conversion device 100 according to the first embodiment. Fig. 5 is a table illustrating each time shown in Fig. 4. Fig. 6 shows a block diagram of the conversion device 100.
[0023] ***Description of Configuration*** The configuration of the conversion device 100 will be described with reference to Fig. 6. The conversion device 100 includes a Sync message processing unit 11, a Follow_Up message processing unit 12, a Delay_Req message processing unit 13, a Delay_Resp message processing unit 14, a Pdelay_Req message processing unit 21, a Pdelay_Resp message processing unit 22, a Pdelay_Resp_Follow_Up message processing unit 23, a master-side packet communication unit 30M, a client-side packet communication unit 30C, an upper-side transmission delay calculation unit 40, an internal processing time calculation unit 50, and a CF processing unit 60.
[0024] The Sync message processing unit 11 is a first processing means. The Follow_Up message processing unit 12 is a second processing means. The Delay_Req message processing unit 13 is a third processing means. The Delay_Resp message processing unit 14 is a fourth processing means. The Pdelay_Req message processing unit 21 is a fifth processing means. The Pdelay_Resp message processing unit 22 is a sixth processing means. The Pdelay_Resp_Follow_Up message processing unit 23 is a seventh processing means. The master device 200 is a higher-level device. The client device 300 is a lower-level device. The CF processing unit 60 is a total value storage unit.
[0025] In the following description, each message processing unit will be referred to as a Sync processing unit 11, for example.
[0026] The functions of each component are as follows: (1) <Master-side packet communication unit 30M, client-side packet communication unit 30C> The master-side packet communication unit 30M and client-side packet communication unit 30C send and receive PTP packets to and from the master device 200 and client device 300, respectively. (2) <Sync processing unit 11> Receives a Sync message from the master device 200, records the reception time dt1 and the transmission time dt2 of the Sync message to the client device 300, and performs the following: (a) sends the reception time dt1 to the upper-side transmission delay calculation unit 40, (b) sends the reception time dt1 and transmission time dt2 to the internal processing time calculation unit 50, and (c) sends the Sync message to the CF processing unit 60. (3) <Follow_Up Processing Unit 12> Receives a Follow_Up message (storing the Follow_Up message sending time T1) from the master device 200 and sends the Follow_Up message to the CF processing unit 60. It also extracts the sending time T1 and sends it to the upper-level transmission delay calculation unit 40. (4) <Delay_Req Processing Unit 13> The Delay_Req processing unit 13 performs the following: (a) Sends a Delay_Req message to the master device 200, (b) Records the sending time T3 of the Delay_Req message, and (c) Sends the sending time T3 to the upper-level transmission delay calculation unit 40. (5) <Delay_Resp Processing Unit 14> The Delay_Resp processing unit 14 performs the following: (a) Receives a Delay_Resp message (which stores the reception time T4 of the Delay_Req message) from the master device 200, (b) extracts the reception time T4 from the Delay_Resp message, and sends it to the upper-level transmission delay calculation unit 40. (6) <Pdelay_Req Processing Unit 21> The Pdelay_Req processing unit 21 performs the following: (a) receives a Pdelay_Req message from the client device 300, (b) records the reception time t2 of the Pdelay_Req message, and (c) sends the reception time t2 to the Pdelay_Resp processing unit 22. (7) <Pdelay_Resp Processing Unit 22> The Pdelay_Resp processing unit 22 performs the following:(a) Stores the reception time t2 of the Pdelay_Req in a Pdelay_Resp message and transmits it to the client device 300, (b) Records the transmission time t3 of the Pdelay_Resp message and transmits it to the Pdelay_Resp_Follow_Up unit 23. (8) <Pdelay_Resp_Follow_Up Processing Unit 23> The Pdelay_Resp_Follow_Up processing unit 23 performs the following: (a) Stores the transmission time t3 received from the Pdelay_Resp processing unit 22 in a Pdelay_Resp_Follow_Up message and transmits it to the client device 300. (9) <Upstream Side Transmission Delay Calculation Unit 40> The upstream side transmission delay calculation unit 40 performs the following. (a) Calculates the transmission delay time pt1 between the master device 200, which is the higher-level device, and the conversion device 100. As will be described in detail later, the transmission delay time pt1 is calculated as follows, where f is the calculation formula: pt1 = f (dt1, T1, T3, T4). (b) Sends the transmission delay time pt1 to the CF processing unit 60. (10) <Internal Processing Time Calculation Unit 50> The internal processing time calculation unit 50 performs the following: (a) Calculates the internal processing time (dt2 - dt1) of the conversion device 100 using the reception time dt1 and transmission time dt2 received from the Sync processing unit 11, and (b) sends the internal processing time (dt2 - dt1) to the CF processing unit 60. (11) <CF Processing Unit 60> The CF processing unit 60 stores a value in the CF of each message.
[0027] ***Description of Operation*** The operation of the conversion device 100 will be described with reference to Fig. 4. The operation of the conversion device 100 corresponds to a conversion method. The operation of the conversion device 100 also corresponds to the processing performed by the conversion program 131.
[0028] <Flow of Message Exchange> Step 2 will be explained with reference to Fig. 4. In step 1, the Follow_Up message and Pdelay_Resp_Follow_Up message indicated by the dashed arrows are not used. Step 1 will be explained later with reference to Fig. 7.
[0029] End-to-end communication is performed between the master device 200 and the conversion device 100. Across the entire network, i.e., between the master device 200 and the client device 300, the time of the client device 300 is synchronized with the time of the master device 200 using a peer-to-peer method.
[0030] <Steps S101 and S102> In step S101, the master device 200 transmits a Sync message. In step S102, the master device 200 stores the transmission time T1 of the Sync message in a Follow_Up message and transmits the message. The following processes A and B are performed in parallel by the conversion device 100.
[0031] <Processing A> The following describes processing A. Processing A includes steps S103A and S104A.
[0032] <Step S103A> The master-side packet communication unit 30M receives the Sync message. In step S103A, the Sync processing unit 11 records the reception time dt1 of the Sync message and transmits the Sync message to the client device 300 via the client-side packet communication unit 30C. The Sync processing unit 11 records the transmission time dt2 of the Sync message to the client device 300.
[0033] <Step S104A> The master-side packet communication unit 30M receives the Follow_Up message. The Follow_Up processing unit 12 transmits the received Follow_Up message to the CF processing unit 60. The CF processing unit 60 stores the sum pt1+(dt2-dt1) of the transmission delay time pt1 between the master device 200 and the conversion device 100 and the internal processing time (dt2-dt1) in the CF of the Follow_Up message. In step S104A, the CF processing unit 60 transmits the Follow_Up message in which the sum is registered to the client device 300 via the client-side packet communication unit 30C.
[0034] Normally, the CF value of an End to End Follow_Up message is "dt2-dt1." If the entire message exchange between the master device 200 and the converter 100 on the left side of Figure 4 is considered as one set, then the transmission delay time pt1 uses the value calculated for the previous set.
[0035] <Process B> The following describes Process B. Process B includes steps S105B to S109B.
[0036] <Step S105B> In step S105B, the Delay_Req processing unit 13 transmits a Delay_Req message to the master device 200 via the master-side packet communication unit 30M. At this time, the Delay_Req processing unit 13 stores the transmission time T3 of the Delay_Req message in the Delay_Req message. Note that the TC normally does not transmit the Delay_Req message but only transfers it.
[0037] <Steps S106B to S108B> In step S106B, the master device 200 records the reception time T4 of the Delay_Req message. In step S107B, the master device 200 stores the reception time T4 in a Delay_Resp message and transmits it. In step S108B, the Delay_Resp processing unit 14 receives and terminates the Delay_Resp message via the master-side packet communication unit 30M. Normally, the TC does not terminate the Delay_Resp message but only forwards it. The Delay_Resp processing unit 14 transmits the reception time T4 to the upper-side transmission delay calculation unit 40.
[0038] <Step S109B> In step S109B, the upper-side transmission delay calculation unit 40 calculates the transmission delay time pt1 between the master device 200 and the conversion device 100. The upper-side transmission delay calculation unit 40 calculates the transmission delay time pt1 using Equation 1: pt1={(dt1-T1)+(T4-T3)} / 2 (Equation 1)
[0039] The above is the process B.
[0040] (1) In step S110, the client device 300 sends a Pdelay_Req message to the conversion device 100 and records the sending time t1. (2) In step S111, the Pdelay_Req processing unit 21 records the receiving time t2 of the Pdelay_Req message. (3) In step S112, the Pdelay_Resp processing unit 22 sends a Pdelay_Resp message and records the sending time t3, storing the receiving time t2 in the Pdelay_Resp message for sending. (4) In step S113, the Pdelay_Resp_Follow_Up processing unit 23 stores the sending time t3 in the Pdelay_Resp_Follow_Up message for sending. (5) In step S114, the client device 300 records the reception time t4 of the Pdelay_Resp message. (6) In step S115, the client device 300 uses the transmission time t1, reception time t2, transmission time t3, and reception time t4 to calculate the transmission delay time pt2 between the conversion device 100 and the client device 300 using equation 2. Transmission delay time pt2={(t2-t1)+(t4-t3)} / 2 (equation 2) The client device 300 performs time synchronization using equation 3. Time T2 is the reception time of the Sync message at the client device 300. T2=T1+pt1+(dt2-dt1)+pt2 (equation 3)
[0041] Figure 7 is a diagram showing the case of one step. Figure 4 shows two steps, but in the case of one step, the operation is as follows, as shown in Figure 7. (1) The transmission time T1 to be stored in the Follow_Up message and transmitted is stored in the Sync message. (2) (dt2 - dt1) stored in the CF of the Follow_Up message is placed in the CF of the Sync message and transmitted as CF = pt1 + (dt2 - dt1). (3) The transmission time t3 stored in the Pdelay_Resp_Follow_Up message is placed in the CF of the Pdelay_Resp message and transmitted.
[0042] <Hardware Configuration of Conversion Device 100> Fig. 8 shows the hardware configuration of the conversion device 100. The hardware configuration of the conversion device 100 will be described with reference to Fig. 8 .
[0043] The conversion device 100 is a computer. The conversion device 100 includes a processor 110. In addition to the processor 110, the conversion device 100 also includes multiple pieces of hardware. The multiple pieces of hardware are a main memory device 120, an auxiliary memory device 130, an input interface 140, an output interface 150, and a communication interface 160. The processor 110 is connected to the other hardware via a signal line 170 and controls the other hardware.
[0044] The conversion device 100 has the following functional elements: a Sync processing unit 11, a Follow_Up processing unit 12, a Delay_Req processing unit 13, a Delay_Resp processing unit 14, a Pdelay_Req processing unit 21, a Pdelay_Resp processing unit 22, a Pdelay_Resp_Follow_Up processing unit 23, a master side packet communication unit 30M, a client side packet communication unit 30C, an upper side transmission delay calculation unit 40, an internal processing time calculation unit 50, and a CF processing unit 60. The functions of the Sync processing unit 11, Follow_Up processing unit 12, Delay_Req processing unit 13, Delay_Resp processing unit 14, Pdelay_Req processing unit 21, Pdelay_Resp processing unit 22, Pdelay_Resp_Follow_Up processing unit 23, master side packet communication unit 30M, client side packet communication unit 30C, upper side transmission delay calculation unit 40, internal processing time calculation unit 50 and CF processing unit 60 are realized by the conversion program 131.
[0045] The processor 110 is a device that executes the conversion program 131. When the processor 110 executes the conversion program 131, the functions of the Sync processing unit 11, Follow_Up processing unit 12, Delay_Req processing unit 13, Delay_Resp processing unit 14, Pdelay_Req processing unit 21, Pdelay_Resp processing unit 22, Pdelay_Resp_Follow_Up processing unit 23, master-side packet communication unit 30M, client-side packet communication unit 30C, upper-side transmission delay calculation unit 40, internal processing time calculation unit 50, and CF processing unit 60 are realized. The processor 110 is an integrated circuit (IC) that performs arithmetic processing. Specific examples of the processor 110 include a CPU (Central Processing Unit), a DSP (Digital Signal Processor), and a GPU (Graphics Processing Unit).
[0046] Examples of the main memory device 120 include a static random access memory (SRAM) and a dynamic random access memory (DRAM). The main memory device 120 stores the results of calculations performed by the processor 110.
[0047] The auxiliary storage device 130 is a storage device that stores data in a nonvolatile manner. A specific example of the auxiliary storage device 130 is a hard disk drive (HDD). The auxiliary storage device 130 may also be a portable recording medium. Examples of portable recording media include a Secure Digital (SD) (registered trademark) memory card, a NAND flash, a flexible disk, an optical disk, a compact disk, a Blu-ray (registered trademark) disk, and a Digital Versatile Disk (DVD). The auxiliary storage device 130 stores a conversion program 131.
[0048] The input interface 140 is a port through which data is input from each device. The output interface 150 is connected to various devices. The output interface 150 is a port through which data is output by the processor 110 to the various devices. The communication interface 160 is a communication port through which the processor communicates with the master device 200 and the client device 300.
[0049] The processor 110 loads the conversion program 131 from the auxiliary storage device 130 into the main storage device 120. The processor 110 reads the loaded conversion program 131 from the main storage device 120 and executes it. In addition to the conversion program 131, an operating system (OS) is also stored in the main storage device 120. The processor 110 executes the conversion program 131 while running the OS. The conversion device 100 may include multiple processors that replace the processor 110. These multiple processors share the execution of the conversion program 131. Each processor is a device that executes the conversion program 131, just like the processor 110. Data, information, signal values, and variable values used, processed, or output by the conversion program 131 are stored in the main storage device 120, the auxiliary storage device 130, or a register or cache memory in the processor 110.
[0050] The conversion program 131 is a program that causes a computer to execute each process, procedure, or step of the Sync processing unit 11, Follow_Up processing unit 12, Delay_Req processing unit 13, Delay_Resp processing unit 14, Pdelay_Req processing unit 21, Pdelay_Resp processing unit 22, Pdelay_Resp_Follow_Up processing unit 23, master side packet communication unit 30M, client side packet communication unit 30C, upper side transmission delay calculation unit 40, internal processing time calculation unit 50, and CF processing unit 60, with the "part" replaced with "process," "procedure," or "step."
[0051] The conversion method is performed by the conversion device 100, which is a computer, executing the conversion program 131. The conversion program 131 may be provided by being stored in a computer-readable recording medium, or may be provided as a program product.
[0052] <Supplementary Information on Hardware Configuration> In FIG. 8 , the functions of the conversion device 100 are implemented by software. However, the functions of the conversion device 100 may also be implemented by hardware. FIG. 9 shows a configuration in which the functions of the conversion device 100 are implemented by hardware. The electronic circuit 500 in FIG. 9 is a dedicated electronic circuit that implements the functions of the Sync processing unit 11, Follow_Up processing unit 12, Delay_Req processing unit 13, Delay_Resp processing unit 14, Pdelay_Req processing unit 21, Pdelay_Resp processing unit 22, Pdelay_Resp_Follow_Up processing unit 23, master-side packet communication unit 30M, client-side packet communication unit 30C, upper-side transmission delay calculation unit 40, internal processing time calculation unit 50, and CF processing unit 60 of the conversion device 100. The electronic circuit 500 is connected to a signal line 501. Specifically, the electronic circuit 500 is a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array. ASIC is an abbreviation for Application Spec Interface IC Integrated Circuit. FPGA is an abbreviation for Field-Programmable Gate Array. The functions of the components of the conversion device 100 may be realized by a single electronic circuit or may be distributed and realized across multiple electronic circuits. Furthermore, some of the functions of the components of the conversion device 100 may be realized by electronic circuits, and the remaining functions may be realized by software.
[0053] Each of the processor 110 and the electronic circuit 500 is also called a processing circuitry or a circuitry. In the conversion device 100, the functions of the Sync processing unit 11, the Follow_Up processing unit 12, the Delay_Req processing unit 13, the Delay_Resp processing unit 14, the Pdelay_Req processing unit 21, the Pdelay_Resp processing unit 22, the Pdelay_Resp_Follow_Up processing unit 23, the master-side packet communication unit 30M, the client-side packet communication unit 30C, the upper-side transmission delay calculation unit 40, the internal processing time calculation unit 50, and the CF processing unit 60 may be realized by the circuitry.
[0054] ***Explanation of the Effects of the First Embodiment*** One of the reasons time synchronization cannot be achieved between different profiles is the difference in the transmission delay measurement method (end to end, peer to peer). However, by using the conversion device 100 of the first embodiment, even if the master device 200 and the client device 300 use different transmission delay measurement methods, the client device 300 can achieve time synchronization with the master device 200. As a result, by using the conversion device 100, it is possible to connect profiles that use different transmission delay measurement methods, which eliminates the need to build separate time distribution networks and reduces equipment costs.
[0055] The first embodiment of the present disclosure has been described above. Several of the first embodiment may be combined and implemented. Also, one or several of the first embodiment may be implemented partially. Note that the present disclosure is not limited to the first embodiment described above, and various modifications are possible as needed.
[0056] REFERENCE SIGNS LIST 11 Sync processing unit, 12 Follow_Up processing unit, 13 Delay_Req processing unit, 14 Delay_Resp processing unit, 21 Pdelay_Req processing unit, 22 Pdelay_Resp processing unit, 23 Pdelay_Resp_Follow_Up processing unit, 30M Master side packet communication unit, 30C Client side packet communication unit, 40 Upper side transmission delay calculation unit, 50 Internal processing time calculation unit, 60 CF processing unit, 100 Conversion device, 101, 102 TC, 110 Processor, 120 Main memory device, 130 Auxiliary memory device, 131 Conversion program, 140 Input interface, 150 Output interface, 160 Communication interface, 170 Signal line, 200, 201, 202 Master device, 300 Client device.
Claims
1. A conversion device for converting a transmission delay measurement method of a higher-level device performing PTP (Precision Time Protocol) communication into a transmission delay measurement method of a lower-level device when the transmission delay measurement methods differ between the higher-level device and the lower-level device performing the PTP communication, the conversion device comprising: a Sync message processing unit that receives a Sync message transmitted from the higher-level device, records a reception time dt1, and records a transmission time dt2 of the Sync message when transmitting the Sync message to the lower-level device for relay; a Follow_Up message processing unit that extracts the transmission time T1 of the higher-level device of the Sync message from a Follow_Up message transmitted from the higher-level device in which the transmission time T1 of the Sync message of the higher-level device is stored; and a Delay_Req message processing unit that transmits a Delay_Req message to the higher-level device and records the transmission time T3 of the Delay_Req message. a Delay_Resp message processing unit that extracts the receiving time T4 of the Delay_Req message from a Delay_Resp message that stores the receiving time T4 of the Delay_Req message and is transmitted from the higher-level device; a Pdelay_Req message processing unit that records the receiving time t2 of the Pdelay_Req message transmitted from the lower-level device; a Pdelay_Resp message processing unit that stores the receiving time t2 of the Pdelay_Req message in a Pdelay_Resp message and transmits the Pdelay_Resp message in which the receiving time t2 of the Pdelay_Req message is stored to the lower-level device; a Pdelay_Resp_Follow_Up message processing unit that stores a transmission time t3 of the Pdelay_Resp message in a Pdelay_Resp_Follow_Up message and transmits the Pdelay_Resp_Follow_Up message in which the transmission time t3 of the Pdelay_Resp message is stored to the lower device;a higher-level transmission delay calculation unit that calculates a transmission delay time pt1 between the higher-level device and the conversion device using the reception time dt1 of the Sync message, the transmission time T1 of the Sync message by the higher-level device, the transmission time T3 of the Delay_Req message, and the reception time T4 of the Delay_Req message; an internal processing time calculation unit that calculates an internal processing time of the conversion device using the reception time dt1 of the Sync message and the transmission time dt2 for relaying the Sync message; and a total value storage unit that stores a total value of the transmission delay time pt1 between the higher-level device and the conversion device and the internal processing time of the conversion device in a Correction Field of the Follow_Up message, and transmits the Follow_Up message in which the total value is stored to the lower device for relaying.
2. In the case where a transmission delay measurement method is different between a higher-level device performing PTP (Precision Time Protocol) communication and a lower-level device performing the PTP communication, a conversion device, which is a computer that converts the transmission delay measurement method of the higher-level device into the transmission delay measurement method of the lower-level device, includes: a Sync message process that receives a Sync message transmitted from the higher-level device, records a reception time dt1, and records a transmission time dt2 of the Sync message when the Sync message is transmitted to the lower-level device for relaying; a Follow_Up message process that extracts the transmission time T1 of the Sync message of the higher-level device from a Follow_Up message transmitted from the higher-level device in which the transmission time T1 of the Sync message of the higher-level device is stored; and a Delay_Req message process that transmits a Delay_Req message to the higher-level device and records the transmission time T3 of the Delay_Req message. a Delay_Resp message process for extracting the receiving time T4 of the Delay_Req message from a Delay_Resp message in which the receiving time T4 of the Delay_Req message is stored and transmitted from the upper device; a Pdelay_Req message process for recording the receiving time t2 of the Pdelay_Req message transmitted from the lower device; a Pdelay_Resp message process for storing the receiving time t2 of the Pdelay_Req message in a Pdelay_Resp message and transmitting the Pdelay_Resp message in which the receiving time t2 of the Pdelay_Req message is stored to the lower device; a Pdelay_Resp_Follow_Up message process for storing a transmission time t3 of the Pdelay_Resp message in a Pdelay_Resp_Follow_Up message and transmitting the Pdelay_Resp_Follow_Up message storing the transmission time t3 of the Pdelay_Resp message to the lower device;an upper-side transmission delay calculation process that calculates a transmission delay time pt1 between the upper device and the conversion device using the reception time dt1 of the Sync message, the transmission time T1 of the Sync message by the upper device, the transmission time T3 of the Delay_Req message, and the reception time T4 of the Delay_Req message; an internal processing time calculation process that calculates an internal processing time of the conversion device using the reception time dt1 of the Sync message and the transmission time dt2 for relaying the Sync message; and a total value storage process that stores the total value of the transmission delay time pt1 between the upper device and the conversion device and the internal processing time of the conversion device in a Correction Field of the Follow_Up message, and transmits the Follow_Up message in which the total value has been stored to the lower device for relaying.
3. When a transmission delay measurement method is different between a higher-level device performing PTP (Precision Time Protocol) communication and a lower-level device performing the PTP communication, a conversion device, which is a computer that converts the transmission delay measurement method of the higher-level device into the transmission delay measurement method of the lower-level device, includes: a Sync message processing step of receiving a Sync message transmitted from the higher-level device, recording a reception time dt1, and recording a transmission time dt2 of the Sync message when the Sync message is transmitted to the lower-level device for relaying; a Follow_Up message processing step of extracting the transmission time T1 of the Sync message of the higher-level device from a Follow_Up message transmitted from the higher-level device in which the transmission time T1 of the Sync message of the higher-level device is stored; and a Delay_Req message processing step of transmitting a Delay_Req message to the higher-level device and recording the transmission time T3 of the Delay_Req message. a Delay_Resp message processing step of extracting the receiving time T4 of the Delay_Req message from a Delay_Resp message in which the receiving time T4 of the Delay_Req message is stored and transmitted from the upper device; a Pdelay_Req message processing step of recording the receiving time t2 of the Pdelay_Req message transmitted from the lower device; a Pdelay_Resp message processing step of storing the receiving time t2 of the Pdelay_Req message in a Pdelay_Resp message and transmitting the Pdelay_Resp message in which the receiving time t2 of the Pdelay_Req message is stored to the lower device; a Pdelay_Resp_Follow_Up message processing step of storing a transmission time t3 of the Pdelay_Resp message in a Pdelay_Resp_Follow_Up message and transmitting the Pdelay_Resp_Follow_Up message storing the transmission time t3 of the Pdelay_Resp message to the lower device;an upper-side transmission delay calculation step of calculating a transmission delay time pt1 between the upper device and the conversion device using the reception time dt1 of the Sync message, the transmission time T1 of the Sync message by the upper device, the transmission time T3 of the Delay_Req message, and the reception time T4 of the Delay_Req message; an internal processing time calculation step of calculating an internal processing time of the conversion device using the reception time dt1 of the Sync message and the transmission time dt2 for relaying the Sync message; and a total value storage step of storing a total value of the transmission delay time pt1 between the upper device and the conversion device and the internal processing time of the conversion device in a Correction Field of the Follow_Up message, and transmitting the Follow_Up message in which the total value has been stored to the lower device for relaying.
Citation Information
Patent Citations
Communication apparatus and time synchronizing method therefor
JP2017098694A
Communication control device and communication control method
JP2020184710A
