Apparatus and method for transmitting synchronization information in a communication system

Abstract

The disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system with a technology for Internet-of-Things (IoT). The disclosure is applicable to smart services based on 5G communication technologies and IoT-related technologies, such as smart home, smart building, smart city, smart car, connected car, health, digital education, smart retail, security and safety services. An apparatus and method for providing time synchronization between terminals connected by wired or wireless are disclosed by extending a function of supporting a Time-Sensitive Network (TSN) in a 5G system (5GS) of the 3rd Generation Partnership Project (3GPP).

Description

Technical Field

[0001] The present invention relates to a communication system, and more particularly, to an apparatus and method for providing time synchronization between terminals that are wired or wirelessly connected to each other by extending the functionality of Time Sensitive Networking (TSN) in the 3rd Generation Partnership Project (3GPP) 5G system (5GS). Background Technology

[0002] To meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "post-4G networks" or "post-LTE systems." 5G communication systems are considered to be implemented in higher frequency (mmWave) bands, such as the 60GHz band, to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies have been discussed in 5G communication systems. Furthermore, in 5G communication systems, development is underway for system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding and modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies, have been developed.

[0003] The Internet, a human-centric network for generating and consuming information, is evolving into the Internet of Things (IoT), where distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) is the combination of IoT technology and big data processing technology through connections to cloud servers. Recently, technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology have been explored for IoT implementation, sensor networks, machine-to-machine (M2M) communication, machine-type communication (MTC), and more. This IoT environment can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. Through the convergence and combination of existing information technology (IT) and various industrial applications, IT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart devices, and advanced medical services.

[0004] Consistent with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented using beamforming, MIMO, and array antennas. The application of cloud radio access networks (RAN), as a big data processing technology, can also be seen as an example of the convergence between 5G and IoT technologies.

[0005] The above information is presented as background information only to aid in understanding this disclosure. No determination is made, and no assertion is made, regarding whether any of the above constitutes prior art in relation to this disclosure. Summary of the Invention

[0006] Technical issues

[0007] When the 3GPP network (or 5GS) corresponds to the synchronization source, and the network-side TSN converter (NW-TT) or device-side TSN converter (DS-TT) generates a Universal Precision Time Protocol ((g)PTP) message and transmits the (g)PTP message to external wired and wireless nodes, it should be determined whether to send the (g)PTP message within the 3GPP network or within the 5GS.

[0008] Solution to the problem

[0009] According to one aspect of this disclosure, a method is provided performed by a terminal in a wireless communication system including a device-side Time-Sensitive Network (TSN) converter (DS-TT). The method involves receiving, from a first network function entity via a base station, time synchronization information associated with a fifth-generation system (5GS) capability for supporting time synchronization of the time-sensitive network (TSN) system, wherein the time synchronization information includes first information indicating the DS-TT's capability as a master clock for time synchronization and second information regarding the transmission type for time synchronization distribution; generating a first synchronization message based on the time synchronization information; and transmitting the first synchronization message for time synchronization to an external PTP port of the TSN system based on the transmission type.

[0010] In this method, the transmission type is associated with either General PTP (gPTP) or PTP.

[0011] In this method, the first network function entity includes at least one of a TSN Application Function (TSN AF) entity or a Network Open Function (NEF) entity.

[0012] Furthermore, the method includes sending a second synchronization message for time synchronization to a second network function entity in the 5GS, which includes a network-side TSN converter (NW-TT), based on the first synchronization message. The second synchronization message includes an entry timestamp corresponding to the time when the first synchronization message was generated and a rate ratio with a value set to 1.

[0013] In the method, a third synchronization message is sent to the external PTP port of the TSN system based on the second synchronization message, and the third synchronization message includes an exit timestamp corresponding to the time when the third synchronization message was sent, and a dwell time calculated as the difference between the exit time and the entry time.

[0014] According to another aspect of this disclosure, a method is provided performed by a second network function entity in a communication system, including a network-side Time-Sensitive Networking (TSN) converter (NW-TT). The method involves receiving time synchronization information from a first network function entity associated with a fifth-generation system (5GS) capability for supporting time synchronization of the TSN system, wherein the time synchronization information includes first information associated with the NW-TT's capability as a master clock for time synchronization and second information regarding the transmission type for time synchronization distribution; generating a first synchronization message based on the time synchronization information; and sending the first synchronization message for time synchronization to an external PTP port of the TSN system based on the transmission type.

[0015] In this method, the transmission type is associated with either General PTP (gPTP) or PTP.

[0016] In this method, the first network function entity includes at least one of a TSN Application Function (TSN AF) entity or a Network Open Function (NEF) entity.

[0017] Furthermore, the method includes sending a second synchronization message for time synchronization to a terminal including a device-side TSN converter (DS-TT) based on a first synchronization message, wherein the second synchronization message includes an entry timestamp corresponding to the time when the first synchronization message was generated and a rate ratio with a value set to 1.

[0018] In the method, a third synchronization message is sent to the external PTP port of the TSN system based on the second synchronization message, and the third synchronization message includes an exit timestamp corresponding to the time when the third synchronization message was sent, and a dwell time calculated as the difference between the exit time and the entry time.

[0019] According to another aspect of this disclosure, a terminal including a device-side Time-Sensitive Network (TSN) converter (DS-TT) is provided in a wireless communication system. The terminal includes a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver, and configured to: receive, via a base station, time synchronization information associated with a fifth-generation system (5GS) capability for supporting time synchronization of a time-sensitive network (TSN) system from a first network function entity, wherein the time synchronization information includes first information and second information, the first information indicating the capability of the DS-TT as a master clock for time synchronization, and the second information relating to the transmission type for time synchronization distribution; generate a first synchronization message based on the time synchronization information, and transmit the first synchronization message for time synchronization to an external Precision Time Protocol (PTP) port of the TSN system based on the transmission type.

[0020] According to another aspect of the present invention, a second network functional entity including a network-side Time-Sensitive Networking (TSN) converter (NW-TT) is provided in a communication system. The second network functional entity includes a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver and configured to: receive from a first network functional entity time synchronization information associated with a fifth-generation system (5GS) capability for supporting time synchronization of a time-sensitive network (TSN) system, wherein the time synchronization information includes first information associated with the NW-TT's capability as a master clock for time synchronization and second information regarding the transmission type for the distribution of the time synchronization; generate a first synchronization message based on the time synchronization information; and send the first synchronization message for time synchronization to an external Precision Time Protocol (PTP) port of the TSN system based on the transmission type.

[0021] Beneficial effects of the invention

[0022] This disclosure can reduce the load on the terminal / network and the power consumption of the terminal by reducing the generation of unnecessary (g)PTP message traffic within 5GS.

[0023] Furthermore, this invention can provide 5GS synchronization for applications that do not support TSN (e.g., Video Image Audio Professional Application (VIAPA)).

[0024] In particular, the ports of DS-TT and NW-TT can provide clock synchronization in different domains, thus providing synchronization with synchronization accuracy in various synchronization message types to support environments that require various clock synchronization.

[0025] For example, 1μs synchronization for factory automation can be provided between wired networks, and 100μs synchronization for audio services can be provided between wireless terminals in the 5GS. Attached Figure Description

[0026] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein like reference numerals denote like parts:

[0027] Figure 1 A conceptual diagram illustrating the time synchronization principle in TSN's Ethernet is shown.

[0028] Figure 2 A conceptual diagram illustrating a scenario supporting TSN time synchronization in a 5G network according to an embodiment is shown.

[0029] Figure 3 A conceptual diagram illustrating a method for supporting TSN time synchronization in a 5G network is shown.

[0030] Figure 4 A conceptual diagram illustrating a method for generating synchronization messages in a communication system and providing synchronization to nodes located outside the 5GS, according to an embodiment, is shown.

[0031] Figure 5 A conceptual diagram illustrating a method for generating synchronization messages in a communication system using DS-TT and providing the synchronization messages to nodes located outside the 5GS, according to an embodiment;

[0032] Figure 6 A conceptual diagram is shown illustrating a method for each of NW-TT and DS-TT, according to an embodiment, to generate a synchronization message in a communication system and provide synchronization to nodes located outside the 5GS.

[0033] Figure 7 A conceptual diagram of a method for configuring 5GS as a synchronization source in a communication system according to an embodiment is shown.

[0034] Figure 8 A flowchart illustrating the generation of synchronization messages by NW-TT and the provision of a synchronization signal stream to nodes located outside the 5GS in the communication system, according to an embodiment, is shown.

[0035] Figure 9 A flowchart illustrating the generation of synchronization messages by DS-TT and the provision of a synchronization signal stream to nodes located outside the 5GS in the communication system, according to an embodiment, is shown.

[0036] Figure 10 A flowchart illustrating a synchronization message generated by DS-TT and a synchronization signal flow provided to a node located outside the 5GS during a UE-to-UE transmission interval in a communication system, according to an embodiment, is shown.

[0037] Figure 11A flowchart is shown illustrating a process in a communication system, according to one embodiment, in which each of NW-TT and DS-TT generates a synchronization message and provides a synchronization signal flow to nodes located outside the 5GS.

[0038] Figure 12 A flowchart is shown illustrating a process according to an embodiment of generating a synchronization message with equivalent NW-TT and DS-TT configurations in a communication system and providing a synchronized signal stream to nodes located outside the 5GS;

[0039] Figure 13 A block diagram of a terminal according to an embodiment is shown;

[0040] Figure 14 A block diagram of a base station according to an embodiment is shown;

[0041] Figure 15 A block diagram of a network function (NF) entity according to an embodiment is shown; and

[0042] Figure 16 A block diagram of a TSN node according to an embodiment is shown. Detailed Implementation

[0043] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used in this patent document: the terms “comprising” and “including” and their derivatives mean including but not limited to; the term “or” is inclusive, referring to and / or; the phrases “associated with” and “associated with” and their derivatives may mean including, being included, interconnected with, containing, being contained, connected to or connected to, linked to or connected to, able to communicate with, cooperate with, interleaved, juxtaposed, adjacent, bound to or bound to, having, having the nature of, etc.; and the term “controller” means any device, system or part thereof that controls at least one operation, such device may be implemented in hardware, firmware or software, or at least a combination of two. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether local or remote.

[0044] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and contained in a computer-readable medium. The terms "application program" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. A non-transitory computer-readable medium includes media that can permanently store data, as well as media that can store data and subsequently rewrite it, such as rewritable optical discs or erasable storage devices.

[0045] Definitions of certain words and phrases are provided throughout this patent document, and those skilled in the art will understand that, in many cases, if not most, such definitions apply to the existing and future use of the words and phrases defined therein.

[0046] The following discussion Figures 1 to 16 The various embodiments used to describe the principles of this disclosure in this patent document are merely exemplary and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of the invention can be implemented in any suitably arranged system or apparatus.

[0047] The operating principles of this disclosure will be described in detail below with reference to the accompanying drawings. In the following description of this disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where they may unnecessarily obscure the subject matter. The terminology described below is defined in consideration of the functions in this disclosure and may vary depending on the user, their intent, or habits. Therefore, the definition of terminology should be based on the entire contents of this specification.

[0048] As will be understood herein, each block of a flowchart, and combinations of blocks within a flowchart, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can direct the computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of writing comprising instruction means for implementing the functions specified in the flowchart blocks or blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus, thereby producing a computer-implemented process, whereby the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowchart blocks.

[0049] Furthermore, each block of a flowchart can represent a module, segment, or section of code, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions recorded in a block can occur sequentially. For example, two blocks shown consecutively may actually execute substantially simultaneously, or these blocks may sometimes execute in reverse order, depending on the functions involved.

[0050] As used herein, a “cell” refers to a software or hardware element that performs a predetermined function, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). However, a “cell” is not always limited to software or hardware. A “cell” can be configured to be stored in addressable memory or to execute one or more processors. Therefore, a “cell” includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a “cell” can be combined into a smaller number of elements or “cells”, or divided into a larger number of elements or “cells.” Furthermore, elements and “cells” may be implemented as one or more CPUs within a playback device or a secure multimedia card.

[0051] In the following description, for convenience, terms for identifying access nodes, terms relating to network entities, terms relating to messages, terms relating to interfaces between network entities, terms relating to various identification information, etc., are used by way of example. Therefore, this disclosure is not limited to the terms used below, and other terms relating to the subject matter having equivalent technical meaning may be used.

[0052] In the following description, for ease of description, the terms and names defined in the 5G and NR standards, which are the latest standards specified by the 3rd Generation Partnership Project (3GPP) group in existing communication standards, will be used to describe this disclosure. However, this disclosure is not limited to these terms and names and can be applied in the same manner to systems conforming to other standards.

[0053] For ease of description below, the target for exchanging information for access control and state management is collectively referred to as NF in this disclosure. NF may include Access and Mobility Management Function (AMF) devices, Session Management Function (SMF) devices, Policy and Charging Function (PCF) devices, TSN Application Function devices, or similar devices operating in the core network. Furthermore, embodiments can be similarly applied to situations where NFs are actually implemented as instances (AMF instances, SMF instances, NSSF instances, etc.).

[0054] In this disclosure, an instance can represent a state in which a particular NF exists in the form of software code, in which physical and / or logical resources can be allocated from a computing system to perform NF functions and are executed by a physical computing system (e.g., a specific computing system existing in the core network). Therefore, all NF instances such as AMF instances, SMF instances, etc., can imply that physical and / or logical resources can be used for NF operations after being allocated from a specific computing system existing in the core network. As a result, the same operations can be performed when NF devices such as physical AMFs, SMFs, etc., are present, and when an NF instance receives physical and / or logical resources from a specific computing system for NF operations to use them.

[0055] To support scenarios such as factory automation, time synchronization of relevant nodes is required. In particular, high-precision time synchronization is needed in situations requiring precise operation. When using industrial Ethernet, Time-Sensitive Networking (TSN) technology, which corresponds to methods supporting time synchronization between nodes connected via Ethernet, has been researched, commercialized, and used.

[0056] Figure 1 A conceptual diagram illustrating the time synchronization principle in TSN's Ethernet is shown.

[0057] refer to Figure 1In a TSN, nodes can be designated as the standard master clock (GM). For example, TSN node 0 can input the current time of the GM into the timestamp field and input 0 into the correction field, generating a synchronization frame, which it then sends to the next node. TSN node 1, as the next node, can receive the synchronization frame reflecting the link delay 1, update the correction field considering the dwell time 1 (time spent within its own node), and then send the synchronization frame to the next node. TSN node 2, as the next node, can receive the synchronization frame reflecting the link delay 2, update the correction field considering the dwell time 2 (time spent within its own node), and then send the synchronization frame to the next node. Each node can periodically measure the link delay with the previous node and calculate the average. Furthermore, each node can calculate the time spent within its own node.

[0058] Figure 2 A conceptual diagram illustrating a scenario supporting TSN time synchronization in a 5G network according to an embodiment is shown.

[0059] Reference Figure 2 5G networks can support TSN in factory automation scenarios, enabling mobility through 5G network applications. (See reference...) Figure 2 The controller B of the factory network, connected to an external TSN node, can issue commands to the actuator A in the factory via the 3GPP network. In this case, the 3GPP network (i.e., 5GS) can act as a bridge for the TSN and provide time synchronization to the actuator. Therefore, Figure 2 The 3GPP network can correspond to Figure 1 TSN node 1, and actuator A can correspond to Figure 1 TSN node 2.

[0060] Figure 3 A conceptual diagram illustrating a method for supporting TSN time synchronization in a 5G network is shown.

[0061] Reference Figure 3 In the methods for supporting TSN in 5G networks, Figure 2 In the scenario shown, the 5G network can be modeled as Figure 1A TSN bridge (TSN node). For example, in a 5G network, the User Plane Function (UPF), gNB, and UE form a TSN node and can update synchronization frames to support TSN by correcting link latency and dwell time. For this purpose, it is assumed that the UPF, gNB, and UE within the 5G network are synchronized with the 5G GM. For example, the gNB can be connected to the Global Positioning System (GPS), and the UPF can connect to the gNB via Ethernet-based TSN to synchronize with the gNB, while the UE can synchronize with the gNB through the process of sending and receiving physical (PHY) frames (DL / UL synchronization). The UPF can connect to a wired network's TSN node, and the UE can connect to a wired network's TSN node. Because in... Figure 3 In the example, the TSN's GM is located on the TSN node connected to the UPF, so the UPF can receive synchronization frames from the previous TSN node. The UPF can record the time of the 5G GM based on the received synchronization frame as the ingress time. The UPF can periodically calculate the link delay with the TSN node. The UPF can transmit synchronization frames to the UE, including the ingress time and link delay. When sending a synchronization frame to the next TSN node, the UE can calculate the dwell time based on the time based on the 5G GM corresponding to the egress time, which is the time spent in the 5G network. The dwell time can be calculated as the time difference between the egress time and the ingress time (dwell time = egress time - ingress time). The UE can use the dwell time and link delay to update the correction field and send the synchronization frame to the next TSN node.

[0062] Figure 4 A conceptual diagram illustrating a method for generating synchronization messages in a communication system and providing synchronization to nodes located outside the 5GS, according to an embodiment, is shown.

[0063] Reference Figure 4 NW-TT can generate synchronization messages and send them in the access direction of the wired node. The timestamp of the synchronization message indicates the time when it was generated. Furthermore, NW-TT can perform actions such as... Figure 3 The operation of receiving TSN synchronization messages is shown. Here, details related to... Figure 3 The same description applies. NW-TT can input the time of generating the synchronization message into the ingress time field, and then send the synchronization message to DS-TT. At this time, the link delay included in the correction field can be 0. DS-TT can determine the dwell time of the synchronization message in the 5G network based on the egress time, which is the time when the synchronization message is sent to a communication node outside the 5GS. The UE can update the correction field based on the dwell time and link delay, and send the synchronization frame to the next TSN node.

[0064] Figure 5 A conceptual diagram illustrating a method for generating synchronization messages in a communication system using DS-TT and providing the synchronization messages to nodes located outside the 5GS, according to an embodiment, is shown.

[0065] Reference Figure 5 DS-TT can generate synchronization messages and send them to external nodes connected to it. The timestamp of the synchronization message indicates the time it was generated. Furthermore, DS-TT can receive synchronization messages from external nodes. Other operations of DS-TT can be combined with... Figure 3 The operations are performed in reverse order. DS-TT can input the time of generating the synchronization message into the ingress time field and send the synchronization message to NW-TT. At this time, the link latency included in the correction field can be 0. NW-TT can determine the dwell time of the synchronization message in the 5G network based on the egress time, which is the time when the synchronization message is sent to a node located outside the 5GS. NW-TT can update the correction field based on the dwell time and link latency and send the synchronization frame to the next TSN node.

[0066] Figure 6 A conceptual diagram of a method according to an embodiment is shown, in which each of the NW-TT and DS-TT generates a synchronization message in the communication system and provides synchronization to nodes located outside the 5GS.

[0067] NW-TT can generate synchronization messages and send them in the access direction of wired nodes. The timestamp of the synchronization message indicates the time it was generated. DS-TT can generate synchronization messages and send them to external nodes connected to the DS-TT. The timestamp of the synchronization message also indicates the time it was generated. NW-TT and DS-TT can... Figure 4 or Figure 5 The method shown can send synchronization messages, or it can choose not to send them. For example, when no synchronization messages are sent, service generation can be reduced, the load on terminals / devices can be reduced, and power consumption can be reduced.

[0068] Figure 7 A conceptual diagram illustrating a method for configuring a 5GS as a synchronization source in a communication system according to an embodiment is shown.

[0069] Reference Figure 7When the 5GS is linked to the TSN system, the TSN Application Function (AF) can interact with the Centralized Network Configuration (CNC) server and exchange management information. The TSN AF can obtain management information from the NW-TT and DS-TT, transmit this information to the NW-TT and DS-TT, and modify their configurations. Through this process, the 5GS can be configured as follows: Figure 4 , Figure 5 or Figure 6 As shown.

[0070] When the 5GS is not operating in conjunction with the TSN system, a standalone AF, not a TSN AF, can be configured similarly for NW-TT and DS-TT. In this case, the AF can be connected to the 5GS's internal network via NEF. An example of connecting the AF via NEF is described below. This can be achieved through... Figure 4 , Figure 5 or Figure 6 The configuration procedures shown are for NW-TT and DS-TT to configure AF. In particular, when the 5GS is not interacting with the TSN system, the method for sending synchronization messages to nodes located outside the 5GS is not fixed to the gPTP scheme, but can be to send Precision Time Protocol (PTP) messages via Ethernet messages or UDP / IP messages.

[0071] In this disclosure, DS-TT can be implemented in a terminal. Furthermore, in this disclosure, NW-TT can be implemented in the network functions (NF_entities) of core networks such as UPF and AMF, and... Figures 8 to 12 In this process, NW-TT is implemented on the UPF.

[0072] Figure 8 A flowchart is shown according to an embodiment for generating synchronization messages by NW-TT in a communication system and providing a synchronization signal flow to nodes located outside the 5GS.

[0073] In Operation 801, DS-TT can establish the required connection with TSN AF, AF, or AF via Network Open Function (NEF), and simultaneously generate a PDU session. At this time, the DS-TT parameters and PDU session can be transmitted to TSN AF, AF, or AF via Network Open Function (NEF).

[0074] In Operation 802, associations can be established between the Session Management Function (SMF) and the Policy Control Function (PCF), as well as between the PCF and the TSN AF, AF, or AF via the Network Open Function (NEF).

[0075] In Operation 803, the TSN AF, AF, or AF via Network Open Function (NEF) can be configured for DS-TT and NW-TT. For example, for NW-TT, the AF can be configured to generate synchronization messages including parameters indicating that the 5GS or TSN GM is the synchronization source for synchronization activation and parameters indicating that the master port is NW-TT. Furthermore, the AF can specify the format of synchronization messages sent outside the DS-TT and NW-TT ports as gPTP / PTP. The AF can specify the supported synchronization domains. In the case of transmission via UDP / IP in PTP format, the destination IP address can be configured. (See reference...) Figure 8 DS-TT and NW-TT ports can support the same domain. The transmission period for synchronization messages can be common, therefore synchronization messages can include a common timestamp (TS) period as a parameter.

[0076] In operation 804, NW-TT can generate a synchronization message. As specified in operation 803, the synchronization message can have a gPTP message format or a PTP message format. At this time, the timestamp time can be determined based on the time the synchronization message was generated, and the time of future timestamp generation can be determined based on the configured timestamp period. Furthermore, the link delay 1 can be configured to 0, and the rate ratio 1 can be configured to 1. The ingress timestamp included in the gPTP message sent from NW-TT to DS-TT can be configured to the time the synchronization message was generated.

[0077] In Operation 805, NW-TT can send synchronization messages to external nodes. For example, in the case of a gPTP message, the Master Clock (GM) timestamp (TS) and correction field can be configured to 0, and the rate ratio 1 (rateRatio1) can be configured to 1. The PTP message can be corrected to the value obtained by adding the correction field to the GM TS. At this point, since the correction field value is 0, it actually only reflects the GM TS value.

[0078] Before sending the generated synchronization message in (g)PTP format to DS-TT in operation 807, NW-TT can insert the entry timestamp into the synchronization message in operation 806.

[0079] In Operation 807, NW-TT can send a synchronization message to DS-TT. In the synchronization message, the GMTS and correction fields can be configured to 0, the rate ratio 1 (rateRatio1) can be configured to 1, and the entry timestamp can be configured to GMTS.

[0080] In operation 808, DS-TT can determine the dwell time 1 before sending the (g)PTP message received from NW-TT to the external node. The dwell time 1 can be calculated as (exit time - ingress time) * rateRatio1 based on the exit time when the synchronization message is sent to the external node. In this case, both the exit time and ingress time are based on 5GS GM, and the rate ratio 1 (rateRatio1) can be the value received from NW-TT in operation 807, which is 1. The ingress timestamp field of the synchronization message eventually sent to the external node can be deleted.

[0081] In operation 809, DS-TT can send synchronization messages to external nodes. In the gPTP format, the GM TS and correction field values ​​can represent 1, as calculated in operation 808 for the dwell time 1 and rate ratio. In the PTP format, the GM TS and correction field values ​​can be updated to the values ​​obtained by adding the dwell times 1 calculated in operation 808 and reflected in the timestamp.

[0082] Figure 9 A flowchart is shown according to an embodiment for generating synchronization messages by DS-TT in a communication system and providing a synchronization signal flow to nodes located outside the 5GS.

[0083] In Operation 901, DS-TT can generate a PDU session and establish the necessary connection with the TSN AF, AF, or AF via NEF. At this time, the DS-TT parameters and PDU session can be transmitted to the TSN AF, AF, or AF via Network Open Function (NEF).

[0084] In Operation 902, associations can be established between SMF and PCF, as well as between PCF and TSN AF, AF, or AF via Network Open Function (NEF).

[0085] In Operation 903, the TSN AF, AF, or AF via Network Open Function (NEF) can be configured for DS-TT and NW-TT. In this case, the AF can configure the generation of synchronization messages, which include parameters for synchronization activation indicating that the 5GS or TSN GM is the synchronization source, and parameters indicating that the master port is DS-TT. Furthermore, the AF can specify the format of synchronization messages sent externally from the DS-TT port and NW-TT port as gPTP / PTP. The AF can specify the supported synchronization domains. In the case of PTP format, when sending synchronization messages via UDP / IP, the AF can configure the destination IP address. (See reference) Figure 9DS-TT and NW-TT ports can support the same domain. Since synchronization messages can have a common transmission period, the common TS period can be included as a parameter.

[0086] In Operation 904, DS-TT can generate a synchronization message. As specified in Operation 903, the synchronization message can have either a gPTP message format or a PTP message format. In this case, the initial timestamp can be determined based on the time the synchronization message is generated, and future timestamps can be determined based on the configured timestamp period. Furthermore, the link delay 1 for the synchronization message can be configured to 0, and the rate ratio 1 can be configured to 1. The ingress timestamp included in the gPTP message sent from DS-TT to NW-TT can be configured based on the time the synchronization message is generated.

[0087] In Operation 905, DS-TT can send synchronization messages to external nodes. The GM TS and correction field values ​​of the gPTP message can be configured to 0, and the rate ratio 1 (rateRatio1) can be configured to 1. The GM TS of the PTP message can be corrected to the value obtained by adding the correction field values. In this case, since the correction field value is 0, the GM TS value can be the same as the value before correction.

[0088] Before sending the generated synchronization message in (g)PTP format to NW-TT in operation 907, DW-TT can configure the entry timestamp value in operation 906.

[0089] In Operation 907, DS-TT can send a synchronization message to NW-TT. In the synchronization message, the GM TS and correction field values ​​can be configured to 0, the rate ratio 1 (rateRatio1) can be configured to 1, and the entry timestamp value can be configured to GM TS.

[0090] In operation 908, NW-TT can determine the dwell time 1 before sending the gPTP message received from DS-TT to the external node. For example, the dwell time 1 can be calculated as (exit time - ingress time) * rateRatio1 based on the exit time when the synchronization message is sent to the external node. In this case, both the exit time and the ingress time are based on 5GS GM, and the rate ratio 1 (rateRatio1) can be the value received from DS-TT in operation 907, which is 1. The ingress timestamp field of the synchronization message that is eventually sent to the external node can be deleted.

[0091] In Operation 909, NW-TT can send synchronization messages to external nodes. In gPTP format, the GM TS and correction fields of the synchronization message can be configured to 1, corresponding to the dwell time 1 and rate ratio 1 determined in Operation 908. In PTP format, the GM TS and correction field values ​​of the synchronization message can be updated to the values ​​obtained by adding the dwell time 1 determined in Operation 908 and reflected in the timestamp.

[0092] Figure 10 A flowchart is shown according to an embodiment for generating a synchronization message by DS-TT and providing a synchronization signal flow to a node located outside the 5GS during a UE-to-UE transmission interval in a communication system.

[0093] Reference Figure 10 In Operation 1001, the DS-TT1 can establish the required connection with the TSN AF, AF, or AF via NEF, and simultaneously generate a PDU session. At this time, the parameters of the DS-TT1 and the PDU session can be transmitted to the TSN AF, AF, or AF via Network Open Function (NEF).

[0094] In Operation 1002, associations can be established between SMF and PCF, as well as between PCF and TSN AF, AF, or AF via Network Open Function (NEF).

[0095] In operation 1003, DS-TT 2 can establish the required connection with TSN AF, AF, or AF via Network Open Function (NEF) while generating a PDU session. At this time, the parameters of DS-TT2 and the PDU session can be transmitted to TSN AF, AF, or AF via Network Open Function (NEF).

[0096] In Operation 1004, associations can be established between SMF and PCF, as well as between PCF and TSN AF, AF, or AF via Network Open Function (NEF).

[0097] In Operation 1005, the TSN AF, AF, or AF via Network Open Function (NEF) can be configured for DS-TT1 and NW-TT. In this case, the AF can configure the generation of synchronization messages, which include parameters for synchronization activation indicating that 5GS or TSN GM is the synchronization source and parameters indicating that the master port is DS-TT1. Furthermore, the AF can specify the format of synchronization messages sent externally from the DS-TT1 port and NW-TT port as gPTP / PTP. The AF can specify the supported synchronization domains. In the case of PTP format, when sending synchronization messages via UDP / IP, the AF can configure the destination IP address. (See reference) Figure 10DS-TT port 1 and NW-TT port can support the same domain. Since synchronization messages can have a common transmission period, the common TS period can be configured as a parameter.

[0098] In Operation 1006, the TSN AF, AF, or AF via Network Open Function (NEF) can be configured for DS-TT 2 and NW-TT. At this time, the AF can configure the generation of synchronization messages, which include parameters for synchronization activation indicating that 5GS or TSN GM is the synchronization source, and parameters indicating that the master port is DS-TT1. Furthermore, the AF can specify the format of synchronization messages sent externally from the DS-TT 2 port and NW-TT port as gPTP / PTP. The AF can specify the supported synchronization domains. In the case of PTP format, when sending synchronization messages via UDP / IP, the AF can configure the destination IP address. (See reference) Figure 10 DS-TT port 2 and NW-TT port can support the same domain. Since synchronization messages can have a common transmission period, parameters for the common TS period can be configured.

[0099] In operation 1007, DS-TT1 can generate a synchronization message. As specified in operation 1005, the synchronization message can have either gPTP or PTP message format. At this time, the timestamp can be determined based on the generation time, and the time of future generated timestamps can be configured based on the configured TS period. Furthermore, the link delay 1 can be configured to 0, and the rate ratio 1 can be configured to 1. The ingress timestamp included in the gPTP message sent from DS-TT1 to NW-TT can also be configured based on the generation time.

[0100] In Operation 1008, DS-TT1 can send synchronization messages to external nodes. The GM TS and correction field values ​​of the gPTP message can be configured to 0, and the rate ratio (rateRatio1) can be configured to 1. The GM TS of the PTP message can be corrected to the value obtained by adding the correction field values. In this case, since the correction field value is 0, the GM TS value can be the same as the value before correction.

[0101] Before sending the generated synchronization message in (g)PTP format to NW-TT in operation 1010, DS-TT1 can configure the entry timestamp value in operation 1009.

[0102] In Operation 1010, DS-TT 1 can send synchronization messages to NW-TT. The GM TS and correction field values ​​of the synchronization message can be configured to 0, the rate ratio 1 can be configured to 1, and the entry timestamp value can be configured to GM TS.

[0103] In Operation 1011, NW-TT can send the synchronization message received in Operation 10 to DS-TT 2 without any changes. In the synchronization message, the GM TS value and correction field value can be configured to 0, the rate ratio 1 can be configured to 1, and the entry timestamp value can be configured to the GM TS value.

[0104] In operation 1012, DS-TT 2 can determine the dwell time 2 before sending the gPTP message received from NW-TT in operation 1011 to the external node. For example, DS-TT 2 can calculate the dwell time 2 as (exit time - ingress time) * rateRatio1 based on the exit time 2, which is the time when the synchronization message is sent to the external node. In this case, both the exit time 2 and the ingress time can be based on 5GS GM, and rateRatio1 can be the value configured by DS-TT1 in operation 1008, i.e., 1. DS-TT 2 can remove the ingress timestamp field from the synchronization message that is eventually sent to the external node.

[0105] In Operation 1012a, NW-TT can determine the dwell time 1 before sending the gPTP message received from DS-TT1 to the external node. NW-TT can calculate the dwell time 1 as (exit time 1 - ingress time) * rateRatio1 based on the exit time 1, which is the time the synchronization message is sent to the external node. In this case, both the exit time 1 and the ingress time can be based on 5GS GM, and rateRatio1 can be the value configured by DS-TT1 in Operation 1008, which is 1. NW-TT can remove the ingress timestamp field from the synchronization message that is ultimately sent to the external node.

[0106] In operation 1013, DS-TT 2 can send a synchronization message to an external node. In gPTP format, the GM TS value and correction field of the synchronization message can be configured to 1, corresponding to the dwell time 2 and rate ratio 1 calculated in operation 1008. In PTP format, the GM TS value and correction field value of the synchronization message can be updated to the value obtained by adding the dwell time 2 calculated in operation 1008 and reflected in the timestamp.

[0107] In Operation 1013a, NW-TT can send synchronization messages to external nodes. In gPTP format, the GM TS value and correction field value of the synchronization message can be configured to 1, corresponding to the dwell time 1 and rate ratio 1 calculated in Operation 1008. In PTP format, the GM TS and correction field values ​​of the synchronization message can be updated to the values ​​obtained by adding the dwell time 1 calculated in Operation 8 and reflected in the timestamp.

[0108] Figure 11 A flowchart is shown according to one embodiment for generating a synchronization message by each of NW-TT and DS-TT and providing a synchronization signal flow to a node located outside the 5GS in the communication system.

[0109] Reference Figure 11 In operation 1101, DS-TT can establish the required connection with TSN AF, AF, or AF via NEF, and generate a PDU session. At this time, the parameters of DS-TT and the PDU session can be transmitted to TSN AF, AF, or AF via Network Open Function (NEF).

[0110] In Operation 1102, associations can be established between SMF and PCF, as well as between PCF and TSN AF, AF, or AF via Network Open Function (NEF).

[0111] In Operation 1103, the TSN AF, AF, or AF via Network Open Function (NEF) can be configured for DS-TT and NW-TT. In this case, the AF can be configured to generate a synchronization message from either DS-TT or NW-TT, DS-TT, or NW-TT. This synchronization message includes a synchronization activation parameter indicating that 5GS or TSN GM is the synchronization source and a parameter indicating that the master port is DS-TT and / or NW-TT. Furthermore, the format of the synchronization message sent externally from the DS-TT port and NW-TT port can be specified as gPTP / PTP. Additionally, the supported synchronization domains can be specified in the synchronization message. In the case of PTP format, when the transmission is performed via UDP / IP, the destination IP address can be configured in the synchronization message. (See reference...) Figure 11 Each of the DS-TT and NW-TT ports can support a separate domain. Furthermore, synchronization messages can have separate transmission cycles and therefore include parameters for each TS cycle.

[0112] In operation 1104, DS-TT can generate a synchronization message. As specified in operation 1103, the synchronization message can have either a gPTP message format or a PTP message format. In this case, the TS 1 corresponding to the timestamp can be configured based on the generation time and can be configured based on the TS period 1 to determine the future generation time e. Furthermore, the link delay 1 can be configured to 0, and the rate ratio 1 (rateRatio1) can be configured to 1. The ingress timestamp included in the gPTP message sent from DS-TT to NW-TT can also be configured based on the generation time.

[0113] In operation 1104a, NW-TT can generate synchronization messages. As specified in operation 1103, the synchronization messages can have gPTP message format or PTP message format. In this case, the TS 2 corresponding to the timestamp can be based on the generation time, and the future generation time can be configured based on the configured TS period 2. Furthermore, link delay 2 can be configured to 0, and rate ratio 2 (rateRatio2) can be configured to 1. The ingress timestamp included in the gPTP message sent from NW-TT to DS-TT can be configured based on the generation time.

[0114] In Operation 1105, DS-TT can send synchronization messages to external nodes. The GM TS 1 value and correction field value of the gPTP message can be configured to 0, and the rate ratio 1 value can be configured to 1. The GM TS 1 value of the PTP message can be corrected to a value obtained by adding the correction field values. Since the correction field value is 0, the GM TS 1 value can be the same as the value before correction.

[0115] In Operation 1105a, NW-TT can send synchronization messages to external nodes. The GM TS 2 value and correction field value of the gPTP message can be configured to 0, and the rate ratio 2 value can be configured to 1. The GM TS 2 value of the PTP message can be corrected to the value obtained by adding the correction field values. Since the correction field value is 0, the GM TS 2 value can be the same as the value before correction.

[0116] and Figure 8 Operations 804, 806, 807, and 808 or Figure 9 Similar to operations 904, 906, 907, and 908, in operation 1106, gPTP format synchronization messages can be sent from NW-TT to DS-TT or from DS-TT to NW-TT. Alternatively, gPTP format synchronization messages can be left unsent between NW-TT and DS-TT. When no synchronization messages are sent, service generation is reduced, terminal / device load is decreased, and power consumption is reduced.

[0117] Figure 12 A flowchart is shown, according to an embodiment, for generating synchronization messages with equivalent NW-TT and DS-TT configurations in a communication system and providing a synchronized signal stream to nodes located outside the 5GS.

[0118] Reference Figure 12 In Operation 1201, the DS-TT can establish the required connection with the TSN AF, AF, or AF via NEF, and simultaneously generate a PDU session. At this time, the DS-TT parameters and PDU session can be transmitted to the TSN AF, AF, or AF via Network Open Function (NEF).

[0119] In Operation 1202, associations can be established between SMF and PCF, as well as between PCF and TSN AF, AF, or AF via Network Open Function (NEF).

[0120] In Operation 1203, the TSN AF, AF, or AF via Network Open Function (NEF) can be configured for DS-TT and NW-TT. In this case, the AF can be configured to generate synchronization messages, which include parameters for synchronization activation indicating that the 5GS or TSN GM is the synchronization source, and parameters indicating that the master port is DS-TT or NW-TT. Furthermore, the format of synchronization messages sent externally from the DS-TT port and NW-TT port can be specified as gPTP / PTP. Additionally, the same synchronization domain can be specified in the synchronization messages. In the case of PTP format, when the transmission is performed via UDP / IP, the destination IP address can be configured in the synchronization message. (Reference) Figure 12 Each of the DS-TT and NW-TT ports can support a separate domain. (See reference...) Figure 12 Synchronization messages can have a common transmission period and therefore include parameters for the common TS period. Synchronization messages may include parameters for initial TSs to have the same timestamp.

[0121] In operation 1204, DS-TT can generate a synchronization message. As specified in operation 1203, the synchronization message can have either a gPTP message format or a PTP message format. In this case, TS1, as a timestamp, can start from the initial TS and can be generated based on the TS period, with future generation times configured based on the configured TS period. Alternatively, the timestamp of the synchronization message can be configured based on a common TS period, independent of the initial TS. Furthermore, the link delay 1 can be configured to 0, and the rate ratio 1 can be configured to 1. The ingress timestamp included in the gPTP message sent from DS-TT to NW-TT can also be configured based on the message generation time.

[0122] In Operation 1204a, NW-TT can generate synchronization messages. As specified in Operation 1203, the synchronization message can have either gPTP message format or PTP message format. In this case, TS2, as a timestamp, can start from the initial TS and can be generated based on the TS period time, and future generation times can be configured based on the configured TS period. Alternatively, the timestamp of the synchronization message can be configured based on a common TS period, independent of the initial TS. Furthermore, link delay 2 can be configured to 0, and rate ratio 2 (rateRatio2) can be configured to 1. The ingress timestamp included in the gPTP message sent from NW-TT to DS-TT can be configured based on the generation time.

[0123] In operation 1205, DS-TT can send synchronization messages to external nodes. The GM TS 1 value and correction field value of the gPTP message can be configured to 0, and the rate ratio 1 value can be configured to 1. The GM TS 1 value of the PTP message can be corrected to the value obtained by adding the correction field values. Since the correction field value is 0, the GM TS 1 value can be the same as the value before correction.

[0124] In Operation 1205a, NW-TT can send synchronization messages to external nodes. The GM TS 2 value and correction field value of the gPTP message can be configured to 0, and the rate ratio 2 value can be configured to 1. The GM TS 2 value of the PTP message can be corrected to the value obtained by adding the correction field values. Since the correction field value is 0, the GM TS 2 value can be the same as the value before correction.

[0125] and Figure 8 Operations 804, 806, 807, and 808 or Figure 9 Similar to operations 904, 906, 907, and 908, in operation 1206, gPTP format synchronization messages can be sent from NW-TT to DS-TT or from DS-TT to NW-TT. Alternatively, gPTP format synchronization messages can be left unsent between NW-TT and DS-TT. When no synchronization messages are sent, service generation is reduced, the load on terminals / devices is decreased, and power consumption is reduced.

[0126] Figure 13 A block diagram of a terminal according to an embodiment is shown.

[0127] refer to Figure 13The terminal (UE) may include a transceiver 1310, a controller 1320, and a memory 1330. Depending on the implementation, the terminal may also have more components. For example, it may further include various additional devices for a user interface, such as a display, input unit, sensors, etc. There are no limitations on such additional components in this disclosure.

[0128] based on Figures 1 to 12 In the illustrated embodiment, transceiver 1310 can be connected to a base station via a radio channel. It can transmit signals and / or messages to and receive signals and / or messages from various network function devices via the base station. For example, the terminal may be a DS-TT. When the terminal communicates with a 5G network, transceiver 1310 may be a device capable of performing transmit / receive operations with the 5G communication network. Furthermore, transceiver 1310 may include a communication processor as needed.

[0129] When the transceiver 1310 does not include a communication processor, the controller can handle all signals and / or messages.

[0130] The controller 1320 can control the basic operations of the terminal and control the reception and storage of the aforementioned messages. For example, the controller 1320 can control the operation of the terminal based on the above description.

[0131] The memory 1330 can store various data required by the control terminal, and can have areas for storing various commands for the aforementioned operations of the terminal.

[0132] Figure 14 A block diagram of a base station according to an embodiment is shown.

[0133] refer to Figure 14 The base station (gNB) may include a network interface 1410, a controller 1420, and a memory 1430. Depending on the implementation, the base station may have additional components. For example, it may further include various additional devices for the user interface, such as displays, input units, sensors, etc. There are no limitations on such additional components in this disclosure.

[0134] based on Figures 1 to 12 In the illustrated embodiment, network interface 1410 can be connected to a terminal via a radio channel. It can send signals and / or messages to and receive signals and / or messages from various network function devices. When the base station communicates with a 5G network, network interface 1410 can be a device capable of performing send / receive operations with the 5G communication network and can be referred to as a transceiver. Furthermore, network interface 1410 may include a communication processor as needed.

[0135] When the network interface 1410 does not include a communication processor, the controller can handle all signals and / or messages.

[0136] The controller 1420 can control the basic operations of the base station and control the reception and storage of the aforementioned messages. For example, the controller 1420 can control the operation of the base station based on the above description.

[0137] The memory 1430 can store various data segments required to control the base station, and can have areas for storing various commands for base station operation.

[0138] Figure 15 A block diagram of a network function (NF) entity according to an embodiment is shown. Figure 15 The NF entities shown are entities that perform network functions of the core network and include at least one of AFM, SMF, UPF, PCF, and TSN AF, but are not limited to a specific NF. Meanwhile, the UPF, as one of the NF entities disclosed herein, can be based on... Figures 1 to 12 The illustrated embodiment performs the operation. For example, the UPF could be an NW-TT.

[0139] Reference Figure 15 NF entities can communicate with other network entities in the core network through network interface 1510. For example, an NF entity can communicate with a UE, gNB, or other NF entities such as AMF, SMF, UPF, PCF, TSN AF, etc. Network interface 1510 can send signals and / or messages to and receive signals and / or messages from various network entities, and can be referred to as a transceiver.

[0140] The controller 1520 can be implemented as at least one processor and / or program for performing operations on NF entities. For example, the controller 1520 can perform operations on NF entities.

[0141] The memory 1530 can store the programs and various control information required by the controller 1520, as well as other information described in this disclosure. Other network entities can also store the information required for the above operations.

[0142] In addition to the elements described above, the NF entity may also include various interfaces for accessing the operator. There are no particular limitations on such additional elements in this disclosure.

[0143] Figure 16 A block diagram of a TNS node according to an embodiment is shown.

[0144] TSN nodes can communicate with other network entities in the core network through network interface 1610 and can be referred to as transceivers. For example, TSN nodes can communicate with UEs, gNBs, or other NF entities such as UPF, AMF, SMF, PCF, TSN AF, etc.

[0145] The controller 1620 can be implemented as at least one processor and / or program for performing operations of the TSN node. For example, the controller 1620 can perform the operations of the TSN node described above.

[0146] The memory 1630 can store the programs and various control information required by the controller 1620, as well as other information described in this disclosure. Other network entities can also store the information required for the above operations.

[0147] In addition to the components described above, a TSN node may also include various interfaces for accessing the operator. A TSN node can be a normal network node. There are no particular limitations on such additional components in this disclosure.

[0148] The methods disclosed in the claims and / or the methods according to the various embodiments described in this disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0149] When the method is implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). The one or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within an electronic device. The at least one program may include instructions that cause the electronic device to perform the method as defined in the appended claims and / or as disclosed herein, according to various embodiments of this disclosure.

[0150] The program (software module or software) can be stored in non-volatile memory including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc ROM (CD-ROM), digital versatile disc (DVD), or other types of optical storage devices, or magnetic tape cassettes. Alternatively, any combination of some or all of these can form the memory in which the program is stored. Furthermore, multiple such memories can be included in an electronic device.

[0151] Furthermore, the program can be stored on a connectable storage device that can access the electronic device via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN), or a combination thereof. This storage device can access the electronic device via an external port. Additionally, a separate storage device on a communication network can access portable electronic devices.

[0152] In the detailed embodiments described above, elements included in this disclosure are represented in a singular or plural form according to the presented embodiments. However, for ease of description, singular or plural forms have been suitably chosen as presented, and this disclosure is not limited to elements represented in a singular or plural form. Thus, an element represented in a plural form may also include a single element, or an element represented in a singular form may include multiple elements.

[0153] Although specific embodiments have been described in this disclosure, various modifications and changes can be made thereto without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the embodiments, but should be defined by the appended claims and their equivalents.

[0154] Although this disclosure has been described with reference to various embodiments, those skilled in the art can suggest various changes and modifications. This disclosure is intended to include such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a first network function entity including a network-side Time-Sensitive Networking (TSN) converter (NW-TT) in a fifth-generation system (5GS), the method comprising: Time synchronization information is received from the second network function entity, the time synchronization information including first information instructing the NW-TT to send a synchronization message to the device-side TSN converter DS-TT in the 5GS and second information associated with the transmission type for time synchronization distribution; Generate a synchronization message for the DS-TT based on the time synchronization information; Add an entry timestamp corresponding to the entry time when the synchronization message was generated to the synchronization message; and The synchronization message is sent to the terminal including the DS-TT.

2. The method according to claim 1, in, The synchronization message also includes a rate ratio with a value set to 1.

3. The method according to claim 2, in, The dwell time is calculated based on the difference between the exit time and the entry time, the difference being indicated by the entry timestamp and the rate ratio. The dwell time is added to the synchronization message, and The synchronization message is sent from the terminal to the external Precision Time Protocol (PTP) port of the TSN system.

4. The method according to claim 3, in, After the dwell time is calculated, the entry timestamp is removed from the synchronization message.

5. A method performed by a terminal in a fifth-generation system (5GS) including a device-side Time-Sensitive Network (TSN) converter (DS-TT), the method comprising: A synchronization message is received from a first network function entity including a network-side time-sensitive network (TSN) converter NW-TT, the synchronization message including an entry timestamp corresponding to the entry time when the synchronization message is generated; The dwell time is calculated based on the difference between the exit time and the entry time indicated by the entry timestamp; Add the dwell time to the synchronization message; as well as The synchronization message is sent to the external Precision Time Protocol (PTP) port of the TSN system.

6. The method according to claim 5, in, The synchronization message includes a rate ratio with a value set to 1, and The dwell time is also calculated based on the rate ratio.

7. The method according to claim 5, further comprising: After calculating the dwell time, the entry timestamp is removed from the synchronization message.

8. The method according to claim 5, further comprising: Time synchronization information is received from a second network function entity, the time synchronization information including first information indicating that the NW-TT is the master clock and second information associated with the transmission type for time synchronization distribution.

9. The fifth-generation system 5GS includes a first network function entity for a network-side time-sensitive network (TSN) converter NW-TT, the first network function entity comprising: A transceiver is configured to send and receive signals; as well as The controller, connected to the transceiver and configured to: Time synchronization information is received from the second network function entity, the time synchronization information including first information instructing the NW-TT to send a synchronization message to the device-side TSN converter DS-TT in the 5GS and second information associated with the transmission type for time synchronization distribution; A synchronization message for the DS-TT is generated based on the time synchronization information. Add an entry timestamp corresponding to the entry time when the synchronization message was generated to the synchronization message, and The synchronization message is sent to the terminal including the DS-TT.

10. The first network functional entity according to claim 9, in, The synchronization message also includes a rate ratio with a value set to 1.

11. The first network functional entity according to claim 10, in, The dwell time is calculated based on the difference between the exit time and the entry time, indicated by the entry timestamp and the rate ratio. The dwell time is added to the synchronization message, and The synchronization message is sent from the terminal to the external Precision Time Protocol (PTP) port of the TSN system.

12. The first network functional entity according to claim 11, in, After the dwell time is calculated, the entry timestamp is removed from the synchronization message.

13. A terminal in a fifth-generation system (5GS) including a device-side Time-Sensitive Network (TSN) converter (DS-TT), the terminal comprising: A transceiver is configured to send and receive signals; as well as A controller, which is connected to the transceiver and configured to: A synchronization message is received from a first network function entity including a network-side time-sensitive network (TSN) converter NW-TT, the synchronization message including an entry timestamp corresponding to the entry time when the synchronization message is generated; The dwell time is calculated as the difference between the exit time and the entry time indicated by the entry timestamp. Add the dwell time to the synchronization message, and The synchronization message is sent to the external Precision Time Protocol (PTP) port of the TSN system.

14. The terminal according to claim 13, in, The synchronization message includes a rate ratio with a value set to 1, and The dwell time is also calculated based on the rate ratio.

15. The terminal according to claim 13, in, The controller is also configured to: After calculating the dwell time, the entry timestamp is removed from the synchronization message, and Time synchronization information is received from a second network function entity, the time synchronization information including first information indicating that the NW-TT is the master clock and second information associated with the transmission type for time synchronization distribution.

Images