NW-TT device, 5G system, TSCTSF device and message conversion method

Abstract

A network-side time-sensitive networking translator (NW-TT) device (30) in a 5 Generation (5G) system (100) acquires the data type of a packet data unit (PDU) session (60) from a time sensitive communication time synchronization function (TSCTSF) device (10). The NW-TT device (30) converts the content of a message body of a precision time protocol (PTP) message according to a combination of the data type acquired from the TSCTSF device (10) and the data type of PTP data received from the network side.

Description

Technical Field

[0001] The present disclosure relates to a technology for converting time synchronization protocols in a 5G system.

Background Art

[0002] In digital factories and Industry 4.0, mobile communications with real-time capabilities and predictable latency are required. In addition, a function is desired in which networks with different profiles and terminals with different profiles coexist in a PnP manner. PnP is an abbreviation for Plug aNd Play. Therefore, sharing of time is necessary. 3GPP (Registered Trademark) aims to expand the application target of the 5G system from mobile broadband services to industrial networks. 3GPP is an abbreviation for 3rd Generation Partnership Project. 5G is an abbreviation for 5 Generation. With local 5G URLLC, mobile bodies in industrial networks can communicate seamlessly. URLLC is an abbreviation for Ultra-Reliable and Low Latency Communications. Therefore, interest in time synchronization between devices with different profiles connected to the 5G system is increasing.

[0003] When a wired network or terminal having different time synchronization profiles coexists, it is necessary to add a translation function for time synchronization messages. Patent Document 1 describes a technique for converting a data format to be transmitted according to the type of network of a port of a relay device. Patent Document 2 describes a technique for generating a frame related to time synchronization using profile technology. It is conceivable to combine the techniques described in Patent Documents 1 and 2 and configure the relay device to convert time synchronization messages of different time synchronization profiles. Thereby, a translation function for time synchronization messages can be realized in the relay device.

Prior Art Documents

Patent Documents

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-212728 [Patent Document 2] Japanese Patent Application Laid-Open No. 2016-184809 [Summary of the Invention] [Problems to be Solved by the Invention]

[0005] Terminals with different time synchronization profiles may be connected through a 5G system. In this case, the 5G system needs to function as the relay device described above and realize the translation function of time synchronization messages. However, the 5G system is a system composed of multiple devices, and there is no device having the information necessary to realize the translation function of time synchronization messages. An object of the present disclosure is to enable the realization of a translation function for time synchronization messages in a 5G system. [Means for Solving the Problems]

[0006] The NW-TT device according to the present disclosure is an NW-TT (NetWork-side Time-sensitive networking Translator) device in a 5G (5 Generation) system, an information acquisition unit that acquires the data type of a PDU (Packet Data Unit) session from a TSCTSF (Time Sensitive Communication Time Synchronization Function) device, and a conversion unit that converts the PTP (Precision Time Protocol) message according to the combination of the data type acquired by the information acquisition unit and the data type of the PTP message received from the network side and includes. [Effects of the Invention]

[0007] In the present disclosure, the NW-TT device acquires the data type of the PDU session from the TSCTSF device. Thereby, the NW-TT device can identify the data type of the destination of the PTP data received from the network side. As a result, the NW-TT device can realize the translation function of the time synchronization message.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Mode for Carrying Out the Invention

[0009] Embodiment 1. ***Explanation of the Configuration*** With reference to FIG. 1, the configuration of the 5G system 100 according to Embodiment 1 will be described. The 5G system 100 includes a TSCTSF device 10, a UPF device 20, a NW-TT device 30, and a plurality of sets of a UE 40 and a DS-TT device 50. Here, the NW-TT device 30 is mounted on the UPF device 20, but it is not limited thereto. TSCTSF is the abbreviation of Time Sensitive Communication Time Synchronization Function. UPF is the abbreviation of User Plane Function. NW-TT is the abbreviation of NetWork-side Time-sensitive networking Translator. UE is the abbreviation of User Equipment. DS-TT is the abbreviation of Device-Side Time-sensitive networking Translator. A PDU session 60 is established between the UE 40 and the UPF device 20 in each set of the UE 40 and the DS-TT device 50. PDU is the abbreviation of Packet Data Unit.

[0010] The terminal connected to the network side and the terminal connected to the device side communicate via the 5G system. The message sent from the terminal connected to the network side is input to the NW-TT device 30. This message is sent to the DS-TT device 50 via the PDU session 60 established between the UE 40 and the UPF device 20 in the set including the DS-TT device 50 to which the destination device is connected. Then, this message is sent from the DS-TT device 50 to the terminal connected to the device side. The message sent from the terminal connected to the device side is input to the DS-TT device 50. This message is sent to the NW-TT device 30 via the PDU session 60 established between the UE 40 and the UPF device 20 in the set including the DS-TT device 50. Then, this message is sent from the NW-TT device 30 to the terminal connected to the network side.

[0011] In Embodiment 1, the NW-TT device 30 realizes the function of translating time synchronization messages.

[0012] Referring to FIG. 2, the configuration of the TSCTSF device 10 according to Embodiment 1 will be described. The TSCTSF device 10 is a computer. The TSCTSF device 10 includes hardware such as a processor 11, a memory 12, a storage 13, and a communication interface 14. The processor 11 is connected to other hardware via signal lines and controls these other hardware.

[0013] The TSCTSF device 10 includes a type transmission unit 111 as a functional component. The functions of the functional components of the TSCTSF device 10 are realized by software. The storage 13 stores a program for realizing the functions of the functional components of the TSCTSF device 10. This program is read into the memory 12 by the processor 11 and executed by the processor 11. Thereby, the functions of the functional components of the TSCTSF device 10 are realized.

[0014] Referring to FIG. 3, the configuration of the NW-TT device 30 according to Embodiment 1 will be described. The NW-TT device 30 is a computer. The NW-TT device 30 includes hardware such as a processor 31, a memory 32, a storage 33, a first communication interface 34, a second communication interface 35, and a third communication interface 36. The processor 31 is connected to other hardware via signal lines and controls these other hardware.

[0015] The NW-TT device 30 includes a time synchronization unit 311, an information acquisition unit 312, a type determination unit 313, and a conversion unit 314 as functional components. The conversion unit 314 includes a protocol conversion unit 315 and a transmission processing unit 316. The functions of each functional component of the NW-TT device 30 are realized by software. The storage 33 stores a program for realizing the functions of each functional component of the NW-TT device 30. This program is read into the memory 32 by the processor 31 and executed by the processor 31. Thereby, the functions of each functional component of the NW-TT device 30 are realized.

[0016] The processors 11, 31 are ICs that perform processing. IC is an abbreviation for Integrated Circuit. Specific examples of the processors 11, 31 are a CPU, a DSP, and a GPU. CPU is an abbreviation for Central Processing Unit. DSP is an abbreviation for Digital Signal Processor. GPU is an abbreviation for Graphics Processing Unit.

[0017] The memories 12, 32 are storage devices that temporarily store data. Specific examples of the memories 12, 32 are SRAM and DRAM. SRAM is an abbreviation for Static Random Access Memory. DRAM is an abbreviation for Dynamic Random Access Memory.

[0018] The storages 13, 33 are storage devices that store data. Specific examples of the storages 13, 33 are HDDs. HDD is an abbreviation for Hard Disk Drive. Also, the storages 13, 33 may be portable recording media such as SD (registered trademark) memory cards, CompactFlash (registered trademark), NAND flash, flexible disks, optical disks, compact disks, Blu-ray (registered trademark) disks, and DVDs. SD is an abbreviation for Secure Digital. DVD is an abbreviation for Digital Versatile Disk.

[0019] The communication interface 14 is an interface for communicating with the NW-TT device 30. The first communication interface 34 is an interface for communicating with a device connected to the network side. The second communication interface 35 is an interface for communicating with a device connected to the 5G system 100 side. That is, the second communication interface 35 is an interface for communicating via the PDU session 60. The third communication interface 36 is an interface for communicating with the TSCTSF device 10. The communication interface 14, the first communication interface 34, the second communication interface 35, and the third communication interface 36 are, as a specific example, ports for communication.

[0020] ***Description of the operation*** With reference to FIGS. 4 to 20, the operation of the 5G system 100 according to Embodiment 1 will be described. The operation procedure of the 5G system 100 according to Embodiment 1 corresponds to the message conversion method according to Embodiment 1. Also, the program for realizing the operation of the 5G system 100 according to Embodiment 1 corresponds to the message conversion program according to Embodiment 1.

[0021] In Embodiment 1, it is assumed that the time synchronization message is a PTP message. PTP is an abbreviation for Precision Time Protocol. In Embodiment 1, as data types of the PTP message, there are three types: IEEE1588-2019 of an IP packet, IEEE1588-2019 of an Ethernet frame, and IEEE802.1AS of an Ethernet frame. In the following description, IEEE1588-2019 of an IP packet is referred to as IP1588. IEEE1588-2019 of an Ethernet frame is referred to as Ethernet1588. IEEE802.1AS of an Ethernet frame is referred to as Ethernet1AS.

[0022] With reference to FIG. 4, the operation outline of the 5G system 100 according to Embodiment 1 will be described. As cases of protocol conversion, there are the following two cases of (1) and (2). (1) The NW-TT device 30 receives a PTP message from the network side, performs protocol conversion, and transmits it to the 5G system 100 side. (2) The NW-TT device 30 receives a PTP message from the 5G system 100 side, performs protocol conversion, and transmits it to the network side. For protocol conversion, the data type of the source and the data type of the destination are required. The data type of the source is the data type of the transmitted PTP message. Regarding the case of (1), although the NW-TT device 30 can identify the data type of the source, it cannot identify the data type of the 5G system 100 side, which is the destination. Regarding the case of (2), the NW-TT device 30 can identify the data types of both the source and the destination. Therefore, in Embodiment 1, regarding the case of (1), the NW-TT device 30 acquires information on the data type of the 5G system 100 side, which is the destination, from the TSCTSF device 10.

[0023] The TSCTSF device 10 is a device that manages time synchronization and deterministic communication services. Generally, in the 5G system 100, the TSCTSF device 10 always transmits TSC-related information to the NW-TT device 30. TSC is an abbreviation for Time Sensitive Communication. In Embodiment 1, in addition to the TSC-related information, the TSCTSF device 10 transmits information on the PDU session 60 established between each UE 40 and the UPF device 20 to the NW-TT device 30. The NW-TT device 30 receives a PTP message from the network side. The NW-TT device 30 acquires the data type of the PDU session 60 to which the destination terminal is connected from the information on the PDU session 60 transmitted from the TSCTSF device 10. Thereby, also regarding the case of (1), the NW-TT device 30 can identify the data types of both the source and the destination. The NW-TT device 30 converts PTP messages according to the combination of the data type of the source and the data type of the destination. Then, the NW-TT device 30 transmits the converted PTP message towards the destination.

[0024] Referring to FIG. 5, the overall operation of the NW-TT device 30 according to Embodiment 1 will be described. (Step S1: Time synchronization process) When the time synchronization unit 311 receives a PTP message, it executes processing related to time synchronization based on the PTP message.

[0025] (Step S2: Type determination process) The type determination unit 313 identifies the combination of the data type of the source and the data type of the destination. At this time, when a PTP message is received from the network side, the information acquisition unit 312 acquires the data type of the PDU session 60 to which the destination terminal is connected from the information of the PDU session 60 transmitted from the TSCTSF device 10. Then, the type determination unit 313 uses the data type acquired by the information acquisition unit 312 to identify the combination.

[0026] If the data type of the source and the data type of the destination are the same, the type determination unit 313 skips the processing of Steps S3 and S4 and advances the processing to Step S5. On the other hand, if the data type of the source and the data type of the destination are different, the type determination unit 313 advances the processing to Step S3. In Steps S3 and S4, the conversion unit 314 converts the PTP message according to the combination identified in Step S2.

[0027] (Step S3: Protocol conversion process) The protocol conversion unit 315 converts the content of the message body of the PTP message according to the combination specified in step S2. Specifically, the protocol conversion unit 315 converts the content of the message body of the PTP message into content that matches the data type of the PDU session 60 for the destination of the PTP message.

[0028] (Step S4: Transmission Information Conversion Processing) The transmission processing unit 316 converts the configuration of the transmission information indicating the destination and source of the PTP message. Specifically, the transmission processing unit 316 converts the configuration of the transmission information of the PTP message into content that matches the data type of the PDU session 60 for the destination of the PTP message.

[0029] (Step S5: Transmission Processing) The transmission processing unit 316 transmits the PTP message to the destination.

[0030] Referring to FIG. 6, the operation of the type determination process (step S2 in FIG. 5) according to Embodiment 1 will be described. In the case where a PTP message is received from the 5G system 100 side, even an existing NW-TT device can identify the combination of the data type of the source and the data type of the destination. Therefore, here, the case where a PTP message is received from the network side will be described.

[0031] (Step S21: Message Extraction Processing) The type determination unit 313 extracts the message body of the PTP message. Then, the type determination unit 313 identifies the data type of the source from the configuration of the message body.

[0032] (Step S22: Information Acquisition Processing) The information acquisition unit 312 acquires the data type of the PDU session 60 to which the destination terminal is connected from the information of the PDU session 60 transmitted from the TSCTSF device 10. Thereby, the data type of the destination is identified.

[0033] (Step S23: Combination Identification Process) The type determination unit 313 identifies the combination of the data type of the source identified in step S21 and the data type of the destination identified in step S22. When the data type of the source and the data type of the destination are the same, the type determination unit 313 advances the process to step S5 in FIG. 5. On the other hand, when the data type of the source and the data type of the destination are different, the type determination unit 313 advances the process to step S3 in FIG. 5.

[0034] When the data type of the source and the data type of the destination are different, there are six types shown in (A) to (F) in FIG. 7. (A) The source is IP1588 and the destination is Ethernet1588. (B) The source is Ethernet1588 and the destination is IP1588. (C) The source is Ethernet1588 and the destination is Ethernet1AS. (D) The source is Ethernet1AS and the destination is Ethernet1588. (E) The source is IP1588 and the destination is Ethernet1AS. (F) The source is Ethernet1AS and the destination is IP1588.

[0035] Referring to FIG. 8, the protocol conversion process (step S3 in FIG. 5) according to Embodiment 1 will be described. (Step S31: Conversion Determination Process) The protocol conversion unit 315 determines whether the combination identified in step S2 is a combination that requires conversion of the message body. When the combination requires conversion of the message body, the protocol conversion unit 315 advances the process to step S32. On the other hand, when the combination does not require conversion of the message body, the protocol conversion unit 315 outputs the message body of the received PTP message as it is.

[0036] In Embodiment 1, among the six types from (A) to (F), the combinations of (A) and (B) in which both the destination and the source use IEEE1588-2019 as the protocol do not require conversion of the message body. The other combinations from (C) to (F) use different protocols for the source and the destination, and require conversion of the message body.

[0037] (Step S32: Message type determination process) The protocol conversion unit 315 determines the type of the message type of the PTP message. In Embodiment 1, the message types of the PTP message include a Sync message, a Follow_Up message, an Announce message, a Pdelay_Req message, a Pdelay_Resp, and a DelayReq message.

[0038] First, the protocol conversion unit 315 determines whether the message type of the source or the destination is a Sync message or a Follow_Up message. If the protocol conversion unit 315 determines that the message is a Sync message or a Follow_Up message, the process proceeds to step S33. If the message is neither a Sync message nor a Follow_Up message, the protocol conversion unit 315 determines whether the message type is an Announce message. If the protocol conversion unit 315 determines that the message is an Announce message, the process proceeds to step S34. If the message is not an Announce message, the protocol conversion unit 315 determines whether the message type is either a Pdelay_Req message or a Pdelay_Resp. If the protocol conversion unit 315 determines that the message type is either a Pdelay_Req message or a Pdelay_Resp, the process proceeds to step S35. If the message type is neither the Pdelay_Req message nor the Pdelay_Resp message, the protocol conversion unit 315 determines whether the message type is the DelayReq message. If the protocol conversion unit 315 determines that the message is the DelayReq message, the process proceeds to step S36. If the message is not the DelayReq message, the protocol conversion unit 315 ends the process as an error.

[0039] (Step S33: First conversion process) The protocol conversion unit 315 processes the Sync message and the Follow_Up message together. Here, there are one-step synchronization and two-step synchronization in the synchronization process. In one-step synchronization, synchronization is performed only with the Sync message. In contrast, in two-step synchronization, synchronization is performed with the Sync message and the Follow_Up message. There are four patterns, (a) to (d), for the conversion here. (a) Conversion between the one-step Sync message of IEEE1588-2019 and the one-step Sync message of IEEE802.1AS. (b) Conversion between the two-step Sync message of IEEE1588-2019 and the two-step Sync message of IEEE802.1AS. (c) Conversion between the one-step Sync message of IEEE1588-2019 and the two-step Sync message of IEEE802.1AS. (d) Conversion between the two-step Sync message of IEEE1588-2019 and the one-step Sync message of IEEE802.1AS.

[0040] Referring to FIG. 9, the conversion between the one-step Sync message of IEEE1588-2019 and the one-step Sync message of IEEE802.1AS will be described. When the message type of the source is the Sync message in IEEE 1588-2019, the protocol conversion unit 315 adds a Follow_Up information TLV. TLV is the abbreviation of Type Length Value. Here, the protocol conversion unit 315 assumes that the clock deviation between the NW-TT device 30 and the master device for time synchronization is 0. Then, as shown in FIG. 9, the protocol conversion unit 315 adds a Follow_Up information TLV. On the other hand, when the message type of the source is the Sync message in IEEE 802.1AS, the protocol conversion unit 315 changes the frame length and deletes the Follow_Up information TLV.

[0041] Referring to FIG. 10, the conversion between (b) the two-step Sync message of IEEE 1588-2019 and the two-step Sync message of IEEE 802.1AS will be described. When the message type of the source is the Sync message in IEEE 1588-2019, the protocol conversion unit 315 adds a Follow_Up information TLV to the Follow_Up message. Also, when the message type of the source is the Sync message in IEEE 1588-2019, the protocol conversion unit 315 sets all the fields with originTimestamp to 0. On the other hand, when the message type of the source is the Sync message in IEEE 802.1AS, the protocol conversion unit 315 changes the frame length and deletes the Follow_Up information TLV in the Follow_Up message.

[0042] Referring to FIG. 11, the conversion between (c) the one-step Sync message of IEEE 1588-2019 and the two-step Sync message of IEEE 802.1AS will be described. When the message type of the source is the Sync message in IEEE 1588-2019, the protocol conversion unit 315 generates a Follow_Up message in IEEE 802.1AS. At this time, the protocol conversion unit 315 sets the value in the originTimestamp field of the Sync message to the PreciseoriginTimestamp field of the Follow_Up message. Also, the protocol conversion unit 315 sets the Follow_Up information TLV. Further, when the message type of the source is the Sync message in IEEE 1588-2019, the protocol conversion unit 315 sets all the fields with originTimestamp to 0. On the other hand, when the message type of the source is the Sync message in IEEE 802.1AS, the protocol conversion unit 315 sets the value in the PreciseoriginTimestamp field of the Follow_Up message in IEEE 802.1AS to the reserved field of the Sync message.

[0043] Referring to FIG. 12, (d) describes the conversion between the two-step Sync message of IEEE 1588-2019 and the one-step Sync message of IEEE 802.1AS. When the message type of the source is the Sync message in IEEE 1588-2019, the protocol conversion unit 315 adds the Follow_Up information TLV. Also, the protocol conversion unit 315 sets the value in the PreciseoriginTimestamp field of the Follow_Up message to the originTimestamp field of the Sync message. On the other hand, when the message type of the source is the Sync message in IEEE802.1AS, the protocol conversion unit 315 generates a Follow_Up message. At this time, the protocol conversion unit 315 sets the value in the originTimestamp field of the Sync message to the PreciseoriginTimestamp field of the Follow_Up message. Also, the protocol conversion unit 315 sets all fields in the originTimestamp field of the Sync message to 0.

[0044] (Step S34: Second conversion process) The protocol conversion unit 315 adds or deletes TLV fields to / from the Announce message.

[0045] With reference to FIG. 13, the case of the Announce message will be specifically described. When the message type of the source is the Announce message in IEEE1588-2019, the protocol conversion unit 315 adds a PATH TRACE TLV. Also, the protocol conversion unit 315 sets all fields that are the originTimestamp to 0. On the other hand, when the message type of the source is the Announce message in IEEE802.1AS, the protocol conversion unit 315 changes the frame length and deletes the PATH TRACE TLV.

[0046] Here, the protocol conversion unit 315 constructs the information of the PATH TRACE TLV from the MAC address of the master device for time synchronization in the Announce message, the MAC address of the NW-TT device 30, and the stepRemoved information of the Announce message. Since the MAC address of the device between the master device and the NW-TT device 30 is unknown, the protocol conversion unit 315 sets it to a specific value (for example, all 0). As a specific example, the information of the PATH TRACE TLV is configured as shown in FIG. 13. Here, the stepRemoved information of the Announce message is set to N.

[0047] (Step S35: Third conversion process) The protocol conversion unit 315 performs item conversion of the Pdelay_Req message.

[0048] A specific description will be given with reference to FIG. 14. When the message type of the source is the Pdelay_Req message in IEEE1588-2019, the protocol conversion unit 315 sets all columns with originTimestamp to 0. Note that for the Pdelay_Resp message, conversion is not required.

[0049] (Step S36: Fourth conversion process) The protocol conversion unit 315 transmits a Delay_Resp message to the source.

[0050] A specific description will be given with reference to FIG. 15. In IEEE1588-2019, there are Delay_Req messages and Delay_Resp messages. However, these messages do not exist in IEEE802.1AS. Therefore, when a Delay_Req message is received, the protocol conversion unit 315 does not transmit a Delay_Req message to the destination but transmits a Delay_Resp message to the source. At this time, the protocol conversion unit 315 sets the delay value from the grandmaster calculated by the 5G system to the value of the timestamp obtained in the 5G system 100 in the receiveTimestamp column of the Delay_Resp message.

[0051] Here, the protocol conversion between IEEE1588-2019 and IEEE802.1AS has been described. However, protocol conversion can also be performed according to the above-mentioned concept between other protocols. The above-mentioned concept consists of four steps from (S) to (V). (S) The protocol conversion unit 315 converts a message with TLV into a message without TLV. In this case, the protocol conversion unit 315 deletes the TLV. (T) The protocol conversion unit 315 converts a message without TLV into a message with TLV. In this case, the protocol conversion unit 315 sets TLVs such as the Follow_Up information TLV described in step S33 and the PATH TRACE TLV described in step S34. (U) The protocol conversion unit 315 changes the timestamp between a one-step synchronization message and a two-step synchronization message. Specifically, the protocol conversion unit 315 uses the originTimestamp of the Sync message in the case of one-step synchronization and uses the PreciseoriginTimestamp of the Follow_Up message in the case of two-step synchronization. (V) When a message that does not exist in the data type of the destination and requests a reply is received, a reply message is sent to the destination. Specifically, when the Delay_Req message and the Delay_Resp message do not exist in the data type of the destination, when the Delay_Req message is received, a Delay_Resp message is sent to the source.

[0052] Referring to FIG. 16, the transmission information conversion process (step S4 in FIG. 5) according to Embodiment 1 will be described. (Step S41: Combination determination process) The transmission processing unit 316 determines which combination in FIG. 7 the combination specified in step S2 is. When it is the combination of (A), the transmission processing unit 316 advances the process to step S42. When it is the combination of (B), the transmission processing unit 316 advances the process to step S43. When it is the combination of (C), the transmission processing unit 316 advances the process to step S44. When it is the combination of (D), the transmission processing unit 316 advances the process to step S45. When it is the combination of (E), the transmission processing unit 316 advances the process to step S46. When it is the combination of (F), the transmission processing unit 316 advances the process to step S47.

[0053] (Step S42: A conversion process) As shown in FIG. 17, the transmission processing unit 316 converts the IP header and the UDP header into DA, SA, and EtherType. DA is the abbreviation of Destination MAC Address. SA is the abbreviation of Source MAC Address. MAC is the abbreviation of Media Access Control. Specifically, the transmission processing unit 316 prepares in advance DA, SA, and EtherType in which the information shown in FIG. 17 is set. Then, the transmission processing unit 316 replaces the IP header and the UDP header with the prepared DA, SA, and EtherType.

[0054] (Step S43: B conversion process) As shown in FIG. 18, the transmission processing unit 316 converts DA, SA, and EtherType into the IP header and the UDP header. Specifically, the transmission processing unit 316 prepares in advance the IP header and the UDP header shown in FIG. 18. Then, the transmission processing unit 316 replaces DA, SA, and EtherType with the prepared IP header and UDP header.

[0055] (Step S44: C conversion process) As shown in FIG. 19, the transmission processing unit 316 replaces the DA for Ethernet 1588 with the DA for Ethernet 1AS.

[0056] (Step S45: D conversion process) As shown in FIG. 20, the transmission processing unit 316 replaces the DA for Ethernet1AS with the DA for Ethernet1588.

[0057] (Step S46: E conversion process) The E conversion process can be realized by a combination of the A conversion process and the C conversion process. Therefore, after performing the process of step S42, the transmission processing unit 316 performs the process of step S44. That is, after converting IP1588 to Ethernet1588, Ethernet1588 is converted to Ethernet1AS.

[0058] (Step S47: F conversion process) The F conversion process can be realized by a combination of the D conversion process and the B conversion process. Therefore, after performing the process of step S45, the transmission processing unit 316 performs the process of step S43. That is, after converting Ethernet1AS to Ethernet1588, Ethernet1588 is converted to IP1588.

[0059] ***Effect of Embodiment 1*** As described above, in the 5G system 100 according to Embodiment 1, the TSCTSF device 10 transmits the data type of the PDU session 60 to the NW-TT device 30. As a result, the NW-TT device 30 can identify the data type of the conversion destination of the PTP data received from the network side. As a result, the NW-TT device 30 can realize the translation function of the time synchronization message.

[0060] The NW-TT device 30 according to Embodiment 1 converts the content of the message body of the PTP message according to the method corresponding to the combination of the data type of the transmission source and the data type of the transmission destination so as to match the data type of the transmission destination. Thereby, protocol conversion of the time synchronization message can be realized.

[0061] The NW-TT device 30 according to Embodiment 1 converts the configuration of the transmission information of the PTP message according to the combination of the data type of the transmission source and the data type of the transmission destination so as to match the data type of the transmission destination. Thereby, it is possible to realize the conversion of the transmission information of the time synchronization message.

[0062] In the 5G system 100 according to Embodiment 1, when the protocol of the transmission destination of the NW-TT device 30 is IEEE802.1AS, when receiving a Delay_Req message in IEEE1588-2019, a Delay_Resp message is transmitted to the transmission source. Thereby, it becomes possible to appropriately respond to the Delay_Req message received from the transmission source.

[0063] ***Other configurations*** <Modification Example 1> In Embodiment 1, each functional component is realized by software. However, as Modification Example 1, each functional component may be realized by hardware. The differences from Embodiment 1 will be described for this Modification Example 1.

[0064] When each functional component is realized by hardware, the TSCTSF device 10 includes an electronic circuit instead of the processor 11, the memory 12, and the storage 13. The electronic circuit is a dedicated circuit that realizes the functions of each functional component, the memory 12, and the storage 13.

[0065] When each functional component is realized by hardware, the NW-TT device 30 includes an electronic circuit instead of the processor 31, the memory 32, and the storage 33. The electronic circuit is a dedicated circuit that realizes the functions of each functional component, the memory 32, and the storage 33.

[0066] As the electronic circuit, a single circuit, a composite circuit, a programmed processor, a parallel-programmed processor, a logic IC, a GA, an ASIC, or an FPGA is assumed. GA is an abbreviation of Gate Array. ASIC is an abbreviation of Application Specific Integrated Circuit. FPGA is an abbreviation of Field-Programmable Gate Array. Each functional component may be realized by one electronic circuit, or each functional component may be realized by being distributed among a plurality of electronic circuits.

[0067] <Modification Example 2> As Modification Example 2, some of each functional component may be realized by hardware, and the other each functional component may be realized by software.

[0068] The processors 11 and 31, the memories 12 and 32, the storages 13 and 33, and the electronic circuit are referred to as a processing circuit. That is, the functions of each functional component are realized by the processing circuit.

[0069] Further, the "section" in the above description may be read as "circuit", "step", "procedure", "process", or "processing circuit".

[0070] The embodiments and modification examples of the present disclosure have been described above. Some of these embodiments and modification examples may be implemented in combination. Also, any one or some of them may be partially implemented. Note that the present disclosure is not limited to the above embodiments and modification examples, and various changes can be made as needed.

Explanation of Reference Numerals

[0071] 100 5G system, 10 TSCTSF device, 11 processor, 12 memory, 13 storage, 14 communication interface, 111 type transmission unit, 20 UPF device, 30 NW-TT device, 31 processor, 32 memory, 33 storage, 34 first communication interface, 35 second communication interface, 36 third communication interface, 311 time synchronization unit, 312 information acquisition unit, 313 type determination unit, 314 conversion unit, 315 protocol conversion unit, 316 transmission processing unit, 40 UE, 50 DS-TT device, 60 PDU session.

Claims

1. An NW-TT (Network-side Time-sensitive networking Translator) device in a 5G (5 Generation) system, an information acquisition unit that acquires the data type of a PDU (Packet Data Unit) session from a TSCTSF (Time Sensitive Communication Time Synchronization Function) device, and a conversion unit that converts the PTP (Precision Time Protocol) message according to the combination of the data type acquired by the information acquisition unit and the data type of the PTP message received from the network side The NW-TT device comprising.

2. The conversion unit is a protocol conversion unit that converts the content of the message body of the PTP message according to the combination of the data type of the PDU session regarding the destination of the PTP message and the data type of the PTP message The NW-TT device according to claim 1, comprising.

3. The protocol conversion unit converts the content of the message body of the PTP message into content adapted to the data type of the PDU session regarding the destination of the PTP message The NW-TT device according to claim 2.

4. The protocol conversion unit converts the content of the message body according to the message type of the PTP message The NW-TT device according to claim 2.

5. When the protocol conversion unit receives a message that does not exist in the data type of the destination and requires a reply, it sends a reply message to the source The NW-TT device according to claim 2.

6. The conversion unit further has a transmission processing unit that converts the configuration of the transmission information indicating the destination and source of the PTP message according to the combination The NW-TT device according to claim 1, comprising.

7. A 5G (5 Generation) system comprising a TSCTSF (Time Sensitive Communication Time Synchronization Function) device and an NW-TT (Network-side Time-sensitive networking Translator) device, The TSCTSF device transmits the data type of a PDU (Packet Data Unit) session to the NW-TT device, The NW-TT device is a 5G system that converts the content of the message body of the PTP (Precision Time Protocol) message according to the combination of the data type of the PTP message received from the network side and the data type transmitted from the TSCTSF device. **Claim 8** A TSCTSF (Time Sensitive Communication Time Synchronization Function) device in a 5G (5 Generation) system, A type transmission unit that transmits the data type of a PDU (Packet Data Unit) session to an NW-TT (Network-side Time-sensitive networking Translator) device that converts the content of the message body of a PTP (Precision Time Protocol) message received from the network side TSCTSF device comprising the same. **Claim 9** A message conversion method in a 5G (5 Generation) system, The TSCTSF (Time Sensitive Communication Time Synchronization Function) device transmits the data type of a PDU (Packet Data Unit) session to an NW-TT (Network-side Time-sensitive networking Translator) device, A message conversion method in which the NW-TT device converts the content of the message body of the PTP message according to the combination of the data type transmitted from the TSCTSF device and the data type of the PTP (Precision Time Protocol) message received from the network side.

Images