Apparatus and method for supporting busrt arrival time reference clock based on time sensitive communication assistance information in wireless communication network
By adjusting burst arrival times based on TSN clocks, the method ensures accurate clock synchronization for base stations, facilitating efficient resource management in wireless communication networks.
Patent Information
- Application Number
- KR1020200001070
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-05-03
- Filing Date
- 2020-01-03
- Publication Date
- 2026-11-06
- Estimated Expiration
- 2040-01-03
AI Technical Summary
In wireless communication networks, base stations lack synchronization with the time-sensitive networking (TSN) clock, preventing accurate resource allocation for time-sensitive communication traffic.
A method for obtaining clock synchronization information at a base station involves processes to adjust burst arrival times based on a TSN clock, including calculating an offset between the TSN and wireless communication system clocks, and converting burst arrival times to the 5GS clock standard.
Enables clock synchronization between nodes, allowing efficient resource allocation and management for time-sensitive communication traffic, particularly in factory automation applications.
Smart Images

Figure 112020000818250-PAT00007_ABST
Abstract
Description
Technology Field
[0001] The present invention generally relates to a wireless communication system, and more specifically, to an apparatus and method for providing additional information to a base station for efficient processing of traffic for time-sensitive communication when providing clock synchronization between nodes in a wireless communication system. Background Technology
[0003] 4G(4 th To meet the increasing demand for wireless data traffic following the commercialization of the (generation) communication system, improved 5G (5 th Efforts are being made to develop a 5G communication system or a pre-5G communication system. For this reason, the 5G communication system or the pre-5G communication system is referred to as a communication system beyond the 4G network or a system after the LTE (Long Term Evolution) system.
[0004] To achieve high data transmission rates, 5G communication systems are being considered for implementation in the mmWave band (e.g., the 60 GHz band). To mitigate path loss and increase the transmission distance of radio waves in the mmWave band, beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large-scale antenna technologies are being discussed for 5G communication systems.
[0005] In addition, to improve the network of the system, the development of technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation is taking place in 5G communication systems.
[0006] In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (Non-Orthogonal Multiple Access), and SCMA (Sparse Code Multiple Access) are being developed in 5G systems.
[0007] Meanwhile, in a 5G wireless communication system, clock synchronization between each node within the system is required for normal use of the system. The problem to be solved
[0009] In order to enable wireless communication networks to support clock synchronization, which was previously supported only in wired networks, a method was proposed for exchanging clock information between a gateway (e.g., UPF (user plane function)) and a terminal (e.g., UE (user equipment)). According to this method, the nodes of the wireless communication network—gateways, terminals, and base stations (e.g., gNB)—are all synchronized with a common clock (e.g., 5GS clock), but the base station is not synchronized with the clock of the wired network (e.g., TSN (time sensitive networking) clock).
[0010] Meanwhile, periodic traffic is a representative type of time-sensitive communication (TSC) traffic, which features traffic patterns including periodicity, burst size, and burst arrival time; a standard for centrally collecting and managing this data already exists. By utilizing this standard, wireless network base stations (gNBs) can achieve efficient resource management by leveraging TSC traffic pattern information (time-sensitive communication assistance information; TSCAI). For instance, resources sufficient to transmit a burst size in accordance with the burst arrival time can be allocated at preset intervals.
[0011] If the clock synchronization method utilizing the wireless communication network proposed above is used, the wireless communication network gateway (UPF) and terminal (UE) know the wired network clock (TSC clock), but the base station (gNB) does not, so a problem arises in which the base station cannot know the exact reference clock of the TSCAI.
[0012] Based on the discussion described above, the present invention provides an apparatus and method for providing additional information to a base station for efficient processing of traffic for time-sensitive communication, so that the base station can know the accurate reference clock of TSCAI in a wireless communication system. means of solving the problem
[0014] According to various embodiments of the present invention, a method for obtaining clock synchronization information at a base station operating based on a reference clock of a wireless communication system comprises: a process of obtaining a burst arrival time of times sensitive communication assistance information (TSCAI) based on a time sensitive networking (TSN) clock; a process of obtaining offset information indicating the difference between the TSN clock and the reference clock of the wireless communication system; and a process of adjusting the burst arrival time based on the offset to obtain an adjusted burst arrival time based on the reference clock of the wireless communication system.
[0015] According to various embodiments of the present invention, a method for obtaining clock synchronization information at a base station operating based on a reference clock of a wireless communication system includes the process of obtaining an adjusted burst arrival time by adjusting the burst arrival time of TSCAI (times sensitive communication assistance information) based on a TSN (time sensitive networking) clock based on the reference clock of the wireless communication system. Effects of the invention
[0018] The apparatus and method according to various embodiments of the present invention have the effect of enabling clock synchronization between nodes of a wireless communication network.
[0019] The apparatus and method according to various embodiments of the present invention can be utilized in applications requiring clock synchronization between nodes, such as factory automation.
[0020] The apparatus and method according to various embodiments of the present invention have the effect of enabling efficient resource allocation at a base station of a wireless communication network when time-sensitive communication traffic passes through a wireless communication network.
[0021] The effects obtainable from the present invention are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present invention belongs from the description below. Brief explanation of the drawing
[0023] FIG. 1a illustrates a wireless communication system according to various embodiments of the present invention. FIG. 1b illustrates the configuration of a base station in a wireless communication system according to various embodiments of the present invention. FIG. 1c illustrates the configuration of a terminal in a wireless communication system according to various embodiments of the present invention. FIG. 1d illustrates the configuration of a core network object in a wireless communication system according to various embodiments of the present invention. FIG. 2a is a diagram showing clock synchronization of a wireless network that does not support TSN (time sensitive networking) of a wired network, which is used for reference to explain the present invention, and the problem of the TSCAI reference clock that the present invention aims to solve. FIG. 2b is a diagram illustrating an example of time-sensitive communication assistance information (TSCAI) transmitted between TSN-supported nodes. Figure 3a is a diagram illustrating additional information that needs to be transmitted to gNB to solve the problem raised in Figure 2a. Figure 3b is a diagram illustrating an example of a burst arrival time adjusted based on TSCAI. Figures 4a and 4b illustrate embodiments of an information transmission flow to solve the problem of the TSCAI reference clock using a wireless communication network. Figures 5, 6, and 7 are flowcharts illustrating the initial flow of the method in which gNB uses an offset, showing that AF, PCF, and SMF perform adjustments, respectively. Figures 8, 9, 10, 11, 12, and 13 show a method in which gNB uses an offset, and are flowcharts representing the UE->gNB, UE->SMF, UE->SMF->PCF, UE->SMF-PCF->AF, AF, and UE->UPF flows, respectively. Figures 14, 15, 16, 17, and 18 show the gNB's use of an offset and are flowcharts representing the UPF->AF, UPF->SMF, UPF->SMF->AF, UPF->SMF->PCF, and UPF->UE flows, respectively. Figures 19, 20, and 21 are flowcharts illustrating the initial flow of a method using the adjusted burst arrival time of gNB, in which AF, PCF, and SMF perform the adjustment, respectively. Figures 22 and 23 are flowcharts illustrating the UE->gNB flow among the methods using the adjusted burst arrival time of the gNB, showing that the UE or gNB performs the adjustment, respectively. Figures 24, 25, and 26 are flowcharts illustrating the UE->SMF flow among the methods using the gNB to adjust the burst arrival time, showing the UE, SMF, and gNB performing adjustments, respectively. Figures 27, 28, 29, and 30 are flowcharts illustrating the UE ->SMF ->PCF flow among the methods using the gNB to adjust the burst arrival time, in which the UE, PCF, SMF, and gNB each perform adjustment. Figures 31, 32, 33, 34, and 35 are flowcharts illustrating the UE->SMF->PCF->AF flow among the methods using the gNB to adjust the burst arrival time, in which the UE, AF, PCF, SMF, and gNB each perform adjustment. Figures 36, 37, 38, 39, and 40 are flowcharts illustrating the use of the UE->AF flow among the methods using the adjusted burst arrival time of gNB, wherein UE, AF, PCF, SMF, and gNB each perform adjustment. FIG. 41 is a flowchart illustrating the use of the UE (40)->UPF (30) flow among the methods using the gNB adjusted burst arrival time. Figures 42, 43, 44, and 45 are flowcharts illustrating the use of the UPF -> AF flow among the methods using the adjusted burst arrival time of gNB, where AF, PCF, SMF, and gNB respectively perform adjustment. Figures 46 and 47 are flowcharts illustrating the use of the UPF->SMF flow among the methods using the adjusted burst arrival time of gNB, showing that SMF or gNB performs the adjustment, respectively. Figures 48, 49, and 50 are flowcharts illustrating the use of the UPF->SMF->PCF flow among the methods for using the gNB adjusted burst arrival time, in which PCF, SMF, or gNB performs the adjustment, respectively. Figures 51, 52, 53, and 54 are flowcharts illustrating the method of utilizing the UPF ->SMF ->PCF ->AF flow among the methods of using the gNB adjusted burst arrival time, in which AF, PCF, SMF, or gNB perform adjustment, respectively. Figure 55 is a flowchart illustrating the use of the UPF->UE flow among the methods using the gNB adjusted burst arrival time. Specific details for implementing the invention
[0024] The operating principle of the present invention will be described in detail below with reference to the attached drawings. In describing the present invention below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the invention. Furthermore, the terms described below are defined considering their functions in the present invention, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout this specification.
[0025] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0026] Additionally, in this disclosure, expressions such as "greater than" (or "larger" or "greater") or "less than" (or "below" or "smaller") may be used to determine whether a specific condition is satisfied or fulfilled; however, this is merely for the purpose of expressing an example and does not exclude descriptions of "greater than" or "less than." Conditions described as "greater than" may be replaced with "greater than," conditions described as "less than" may be replaced with "less than," and conditions described as "greater than and less than" may be replaced with "greater than and less than."
[0027] For the convenience of the following explanation, the present invention refers to 5GS (5), which is the latest standard defined by the 3GPP (The 3rd Generation Partnership Project) among currently existing communication standards. th The terms and names defined in the generation system and NR (new radio) standards are used. However, the present invention is not limited by the above terms and names and can be applied in the same way to wireless communication networks according to other standards. In particular, the present invention can be applied to the 5th generation wireless communication standard, 3GPP 5GS / NR.
[0029] FIG. 1a illustrates a wireless communication system according to various embodiments of the present invention.
[0030] Referring to FIG. 1a, the wireless communication system includes a radio access network (RAN) (102) and a core network (CN) (104).
[0031] A wireless access network (102) is a network directly connected to a user device, for example, a terminal (40), and is an infrastructure that provides wireless access to the terminal (40). The wireless access network (102) includes a set of multiple base stations including a base station (50), and the multiple base stations can perform communication through interfaces formed between them. At least some of the interfaces between the multiple base stations may be wired or wireless. The base station (50) may have a structure separated into a central unit (CU) and a distributed unit (DU). In this case, one CU can control multiple DUs. In addition to being a base station, the base station (50) may be referred to as an 'access point (AP)', 'gNB (next generation node B)', '5G node (5th generation node)', 'wireless point', 'transmission / reception point (TRP)', or other terms having an equivalent technical meaning. The terminal (40) connects to a wireless access network (102) and communicates with a base station (50) via a wireless channel. The terminal (40) may be referred to as 'user equipment (UE)', 'mobile station', 'subscriber station', 'remote terminal', 'wireless terminal', or 'user device', or other terms having an equivalent technical meaning.
[0032] The core network (104) is a network that manages the entire system, controls the wireless access network (102), and processes data and control signals for terminals (40) transmitted and received through the wireless access network (102). The core network (104) performs various functions such as controlling the user plane and control plane, processing mobility, managing subscriber information, billing, and interoperability with other types of systems (e.g., LTE (long term evolution) systems). To perform the various functions described above, the core network (104) may include a plurality of functionally separated entities having different network functions (NFs). For example, the core network (104) may include an access and mobility management function (AMF) (90), a session management function (SMF) (80), a user plane function (UPF) (30), a policy and charging function (PCF) (85), a network repository function (NRF) (95), a unified data management function (UDM) (75), a network exposure function (NEF) (65), and a unified data repository (UDR) (55). The core network (104) may be linked with an application function (AF) (70), a central network controller (CNC) (60), and a TSN system. The core network (104) may be referred to as the 5GC (5G core), which is the core network of the 5G system.
[0033] The terminal (40) is connected to the wireless access network (102) and connects to an AMF (90) that performs the mobility management function of the core network (104). The AMF (90) is a function or device responsible for both the connection to the wireless access network (102) and the mobility management of the terminal (40). The SMF (80) is an NF that manages sessions. The AMF (90) is connected to the SMF (80), and the AMF (90) routes session-related messages for the terminal (40) to the SMF (80). The SMF (80) is connected to the UPF (30) to allocate user plane resources to be provided to the terminal (40) and establishes a tunnel for transmitting data between the base station (50) and the UPF (30). The SMF (80) is the entity that manages the PDU session and can be responsible for QoS settings / updates for QoS flows within the PDU session. PCF (85) controls information related to policy and charging for the session used by the terminal (40). NRF (95) stores information about NFs installed in the wireless communication operator network and performs the function of providing the stored information. NRF (95) can be connected to all NFs. When each NF starts operating in the operator network, it registers with NRF (95) to notify NRF (95) that the NF is operating within the network. UDM (75) is an NF that performs a role similar to the HSS (home subscriber server) of a 4G network and stores the subscription information of the terminal (40) or the context used by the terminal (40) within the network.
[0034] NEF (65) is a third party (3 rdIt performs the role of connecting the server (party) and the NF within the 5G wireless communication system. It also performs the role of providing data to, updating, or acquiring data from the UDR (55). The UDR (55) stores subscription information of the terminal (40), stores policy information, stores data exposed to the outside, or stores data for a third-party application (3 rd It performs the function of storing information required by the party application. In addition, UDR (55) also performs the role of providing the stored data to other NFs.
[0035] UDM (75), PCF (85), SMF (80), AMF (90), NRF (95), NEF (65), and UDR (55) are connected via a service-based interface, and other NFs can exchange control messages with each other by utilizing the services or APIs (application program interfaces) provided by each NF. The NFs define the services they provide, which are defined in the standard as Nudm, Npcf, Nsmf, Namf, Nnrf, Nnef, Nudr, etc. For example, when AMF (90) transmits a session-related message to SMF (80), it may use the service or API called Nsmf_PDUSession_CreateSMContext. The AF can be configured in various ways. Although the AF is not explicitly shown in FIG. 1a, the AF may be associated with 5GC (104). The AF is 3 outside the operator network rd It may be an entity of the party or an entity within the operator network. For example, since TSN AF corresponds to a function essential for 5GC to support TSN, it may be an entity within 5GC, which is the operator network.
[0036] FIG. 1b illustrates the configuration of a base station in a wireless communication system according to various embodiments of the present invention. The configuration exemplified in FIG. 1b can be understood as the configuration of a base station (50). Terms such as '... unit', '... unit' used below refer to a unit that processes at least one function or operation, and this can be implemented in hardware or software, or a combination of hardware and software.
[0037] Referring to FIG. 1b, the base station (50) includes a wireless communication unit (210), a backhaul communication unit (220), a storage unit (230), and a control unit (240).
[0038] The wireless communication unit (210) performs functions for transmitting and receiving signals through a wireless channel. For example, the wireless communication unit (210) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the wireless communication unit (210) generates complex symbols by encoding and modulating the transmitted bit sequence. Also, when receiving data, the wireless communication unit (210) restores the received bit sequence by demodulating and decoding the baseband signal.
[0039] Additionally, the wireless communication unit (210) upconverts a baseband signal into an RF (radio frequency) band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. To this end, the wireless communication unit (210) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC (digital to analog converter), an ADC (analog to digital converter), etc. Additionally, the wireless communication unit (210) may include a plurality of transmission and reception paths. Furthermore, the wireless communication unit (210) may include at least one antenna array composed of a plurality of antenna elements.
[0040] In terms of hardware, the wireless communication unit (210) may be composed of a digital unit and an analog unit, and the analog unit may be composed of a plurality of sub-units depending on operating power, operating frequency, etc. The digital unit may be implemented with at least one processor (e.g., a digital signal processor (DSP)).
[0041] The wireless communication unit (210) transmits and receives signals as described above. Accordingly, all or part of the wireless communication unit (210) may be referred to as a 'transmitter', a 'receiver', or a 'transceiver'. Furthermore, in the following description, transmission and reception performed through a wireless channel are used to mean that processing as described above is performed by the wireless communication unit (210).
[0042] The backhaul communication unit (220) provides an interface for communicating with other nodes within the network. That is, the backhaul communication unit (220) converts a bit sequence transmitted from a base station to another node, e.g., another connection node, another base station, an upper node, a core network, etc., into a physical signal, and converts a physical signal received from another node into a bit sequence.
[0043] The storage unit (230) stores data such as basic programs, application programs, and configuration information for the operation of the base station. The storage unit (230) may be composed of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. Additionally, the storage unit (230) provides the stored data upon request from the control unit (240).
[0044] The control unit (240) controls the overall operations of the base station. For example, the control unit (240) transmits and receives signals through the wireless communication unit (210) or through the backhaul communication unit (220). Additionally, the control unit (240) writes and reads data to and from the storage unit (230). Furthermore, the control unit (240) can perform the functions of a protocol stack required by the communication standard. According to other implementation examples, the protocol stack may be included in the wireless communication unit (210). To this end, the control unit (240) may include at least one processor. According to various embodiments, the control unit (240) can control the base station to perform operations according to the various embodiments described below.
[0045] FIG. 1c illustrates the configuration of a terminal in a wireless communication system according to various embodiments of the present invention. The configuration exemplified in FIG. 1c can be understood as the configuration of a terminal (40). Terms such as '...part', '...unit', etc. used below refer to a unit that processes at least one function or operation, and this can be implemented as hardware or software, or a combination of hardware and software.
[0046] Referring to FIG. 1c, the terminal (40) includes a communication unit (310), a storage unit (320), and a control unit (330).
[0047] The communication unit (310) performs functions for transmitting and receiving signals through a wireless channel. For example, the communication unit (310) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (310) generates complex symbols by encoding and modulating the transmitted bit sequence. Also, when receiving data, the communication unit (310) restores the received bit sequence by demodulating and decoding the baseband signal. Additionally, the communication unit (310) up-converts the baseband signal into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the communication unit (310) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.
[0048] Additionally, the communication unit (310) may include a plurality of transmission and reception paths. Furthermore, the communication unit (310) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (310) may be composed of a digital circuit and an analog circuit (e.g., a radio frequency integrated circuit (RFIC)). Here, the digital circuit and the analog circuit may be implemented as a single package. Additionally, the communication unit (310) may include a plurality of RF chains. Furthermore, the communication unit (310) may perform beamforming.
[0049] The communication unit (310) transmits and receives signals as described above. Accordingly, all or part of the communication unit (310) may be referred to as a 'transmitter', a 'receiver', or a 'transmitter / receiver'. Additionally, in the following description, transmission and reception performed via a wireless channel are used to mean that processing as described above is performed by the communication unit (310).
[0050] The storage unit (320) stores data such as basic programs, application programs, and setting information for the operation of the terminal. The storage unit (320) may be composed of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. Additionally, the storage unit (320) provides the stored data upon the request of the control unit (330).
[0051] The control unit (330) controls the overall operations of the terminal. For example, the control unit (330) transmits and receives signals through the communication unit (310). Additionally, the control unit (330) writes and reads data to and from the storage unit (320). Furthermore, the control unit (330) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (330) may include at least one processor or microprocessor, or be part of a processor. Additionally, part of the communication unit (310) and the control unit (330) may be referred to as a communication processor (CP). According to various embodiments, the control unit (330) can control the terminal to perform operations according to the various embodiments described below.
[0052] FIG. 1d illustrates the configuration of a core network object in a wireless communication system according to various embodiments of the present invention. The configuration exemplified in FIG. 1d can be understood as the configuration of a device having at least one function among the AMF (90), SMF (80), UPF (30), PCF (85), NRF (95), UDM (75), AF (70), NEF (65), and UDR (55) of FIG. 1. Terms such as '...part', '...unit', etc. used below refer to a unit that processes at least one function or operation, and this may be implemented in hardware or software, or a combination of hardware and software.
[0053] Referring to FIG. 1d above, the core network object is configured to include a communication unit (410), a storage unit (420), and a control unit (430).
[0054] The communication unit (410) provides an interface for performing communication with other devices within the network. That is, the communication unit (410) converts a bit sequence transmitted from a core network object to another device into a physical signal, and converts a physical signal received from another device into a bit sequence. That is, the communication unit (410) can transmit and receive signals. Accordingly, the communication unit (410) may be referred to as a modem, a transmitter, a receiver, or a transceiver. At this time, the communication unit (410) enables the core network object to communicate with other devices or systems via a backhaul connection (e.g., wired backhaul or wireless backhaul) or via a network.
[0055] The storage unit (420) stores data such as basic programs, application programs, and configuration information for the operation of core network objects. The storage unit (420) may be composed of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. Additionally, the storage unit (420) provides the stored data upon the request of the control unit (430).
[0056] The control unit (430) controls the overall operations of the core network object. For example, the control unit (430) transmits and receives signals through the communication unit (410). Additionally, the control unit (430) writes and reads data to and from the storage unit (420). To this end, the control unit (430) may include at least one processor. According to various embodiments, the control unit (430) may control the core network object to perform operations according to the various embodiments described below.
[0057] FIG. 2a is a diagram showing clock synchronization of a wireless network that does not support time sensitive networking (TSN) of a wired network, which is used as a reference for explaining the present invention, and the problem of the TSCAI reference clock that the present invention intends to solve, and FIG. 2b is a diagram illustrating an example of time sensitive communication assistance information (TSCAI) transmitted between TSN-supporting nodes.
[0058] Referring to FIG. 2a, in order to support TSN in a wired network, TSN nodes (21, 23) support a protocol that transmits the clock of the TSN GM (Grand Master) (10) through an Ethernet frame. To extend this to a wireless network, the gateway UPF (user plane function) (30) and the terminal UE (user equipment) (40) have a TSN translator function to support the aforementioned protocol. A method has also been proposed to support the transmission of the TSN clock between the UPF (30) and the UE (40). This method involves the terminal (UE) (40), base station (gNB) (50), and gateway (UPF) (30) within the 5G system being synchronized with the 5G system clock, and using this, the UPF (30) and the UE (40) transmit the TSN clock value by time stamping it with the 5GS clock. That is, when using this method, UPF (30) and UE (40) know the TSN clock and the 5GS clock at the same time, but the base station only knows the 5GS clock.
[0059] Meanwhile, for effective TSC traffic transmission between TSN support nodes, each TSN node (21, 23) transmits traffic pattern information to the CNC (central network controller) (60), and the CNC (60) can share the traffic pattern information with other TSN nodes (21, 23) to help with the scheduling of all nodes. The 5G system is considered as a single TSN node and receives traffic patterns flowing into the 5G system from an external TSN node through the UE (40) and UPF (30) from the CNC (60) via AF (70). Similarly, traffic patterns going out of the 5G system to an external TSN node through the UE (40) and UPF (30) are shared with the CNC (60) via AF (70). When TSCAI (TSC assistance information), which is traffic characteristic information including periodicity, burst size, and burst arrival time as shown in FIG. 2b, is transmitted to the gNB (50) for traffic entering the 5G system, the gNB (50) can utilize this information for scheduling and efficiently use resources. For example, resources sufficient to transmit the burst size according to the burst arrival time are allocated at preset periods. In fact, since the information coming from the CNC (60) is the pattern of traffic arriving at the UPF (30) in the case of the downlink (DL), the maximum UPF residence time and the CN PDB (packet delay budget) must be corrected in order to change it based on the input end of the gNB (50). Likewise, since the information coming from the CNC (60) is the pattern of traffic arriving at the UE (40) in the case of the uplink (UL), the UE residence time must be corrected in order to change it based on the input of the gNB (50).The TSN reference time refers to a reference time used to express the time of the TSN clock. For example, it may include a time epoch associated with the TSN.
[0060] When using the clock synchronization method utilizing the wireless communication network proposed above, the wireless communication network gateway (UPF) (30) and terminal (UE) (40) know the wired network clock (TSC clock), but the base station (gNB) (50) does not, so a problem arises in that the exact reference clock of TSCAI cannot be known. In particular, since the burst arrival time is displayed based on the TSN clock, the gNB (50), which only knows the 5GS clock, cannot utilize this information.
[0061] FIG. 3a is a diagram illustrating information that needs to be additionally transmitted to the gNB (50) to solve the problem raised in FIG. 2a, and FIG. 3b is a diagram illustrating an example of a burst arrival time adjusted based on TSCAI. The 5GS reference time refers to a reference time to express the time of the 5G clock. For example, it may include a time epoch associated with 5GS.
[0062] As a first solution, the problem can be solved by transmitting an offset, which is the difference between the 5GS clock and the TSN clock, to the gNB (50). In one embodiment, the offset = T_5GS - T_TSN (the difference between the 5GS clock and the TSN clock) is calculated in the UPF (30) or UE (40) and transmitted to the gNB (50). Then, the gNB (50) maps the burst arrival time based on the TSN clock to the 5GS clock and uses it for scheduling.
[0063] As a second solution, the problem can be solved by transmitting the burst arrival time converted to the 5GS clock standard to the gNB (50). The problem can be solved at any node in the information transmission process to the UE (40), UPF (30), or gNB (50) by converting the burst arrival time based on the TSN clock standard to the burst arrival time based on the 5GS clock standard. The gNB (50) can also process the burst arrival time by converting (mapping) the standard from the TSN clock standard to the 5GS clock standard. In this case, the difference from the first method is the difference in who manages the burst arrival time based on the TSN clock of the corresponding domain. In the first solution, the gNB (50) must manage the list of burst arrival times for each TSN domain, whereas in the second solution, a network function other than the gNB (50) manages this. A TSN domain refers to nodes that use the same TSN GM as a standard, and multiple TSN domains may exist in a wired network. Current wired network standards support up to 256 networks, and current 5GS standards support up to 32 networks simultaneously.
[0064] FIGS. 4a and 4b are diagrams illustrating embodiments of an information flow to solve the problem of the TSCAI standard clock using a wireless communication network. There are two methods for transmitting the offset or the burst arrival time converted to the 5GS clock standard to the gNB (50): one in which the UE (40) initiates the information flow, and another in which the UPF (30) initiates the information flow.
[0065] Referring to FIG. 4a, the cases in which the UE (40) initiates information flow can be divided as follows.
[0066] 1.1 For gNB (50) via RRC (newly defined RRC (radio resource control)) (311): In this case, the burst arrival time in UE (40) and gNB (50) can be changed from the TSN clock standard to the 5GS clock standard.
[0067] 1.2 For SMF (80) via NAS (PDU (protocol data unit) Session Modification) (312): In this case, the burst arrival time in UE (40), SMF (80), or gNB (50) can be changed from the TSN clock standard to the 5GS clock standard.
[0068] 1.3 For SMF (80) via NAS (PDU Session Modification)-(Notification)-PCF (85) path (313): In this case, the burst arrival time in UE (40), PCF (85), SMF (80), or gNB (50) can be changed from the TSN clock standard to the 5GS clock standard.
[0069] 1.4 For SMF (80) via the NAS (PDU Session Modification)-(Notification)-PCF (85)-(Notification)-AF (70) path (314): In this case, the burst arrival time in UE (40), AF (70), PCF (85), SMF (80), or gNB (50) can be changed from the TSN clock standard to the 5GS clock standard.
[0070] 1.5 For AF (70) via non-3GPP method (315): In this case, the burst arrival time in U UE (40), AF (70), PCF (85), SMF (80), or gNB (50) can be changed from the TSN clock standard to the 5GS clock standard.
[0071] 1.6 Piggyback of the synchronization procedure or for UPF (30) through a new interface (316): In this case, depending on the flow after the subsequent UPF (30), adjustments to change the burst arrival time from the TSN clock reference to the 5GS clock reference can be performed in various NF (network function).
[0072] Referring to Fig. 4b, the cases in which UPF (30) initiates information flow can be divided as follows.
[0073] 2.1 AF (70) via a non-3GPP method (including AF (70)-UPF (30) integration) (321): In this case, an adjustment can be made to change the burst arrival time in AF (70), PCF (85), SMF (80), or gNB (50) from the TSN clock reference to the 5GS clock reference.
[0074] 2.2 To SMF (80) (322) via N4 interface (N4 Report / Notification): In this case, an adjustment can be made to change the burst arrival time from the TSN clock standard to the 5GS clock standard in SMF (80) or gNB (50).
[0075] 2.3 PCF (85) via the path UPF (30)-(N4)-SMF (80)-(Notification)-PCF (85) (323): In this case, an adjustment can be made to change the burst arrival time from the TSN clock reference to the 5GS clock reference at PCF (85), SMF (80), or gNB (50).
[0076] 2.4 From AF(70) to AF(70) via the path UPF(30)-(N4)-SMF(80)-(Notification)-PCF(85)-(Notification)-AF(70) (324): In this case, adjustments can be made to change the burst arrival times from the TSN clock standard to the 5GS clock standard in AF(70), PCF(85), SMF(80), and gNB(50).
[0077] 2.5 Piggyback to the synchronization procedure or to the UE (40) via a new interface: In this case, depending on the flow from the subsequent UE (40), adjustments to change the burst arrival time from the TSN clock reference to the 5GS clock reference can be performed at various NFs.
[0078] [Table 1] is a drawing illustrating a corresponding embodiment by comprehensively reviewing the information that must be additionally transmitted in the wireless network, the flow of information transmission, and the adjustment aspects of TSCAI in order to solve the problems of the TSCAI reference clock using a wireless communication network. It illustrates the contents described in Figure 2 and Figure 3 above in combination, and simultaneously describes the figure numbers of the corresponding embodiments.
[0080] Flow options Adjustment Options (Related Drawing Number) Solution #1. gNB receives offset Solution #2. gNB receives burst arrival times based on the 5GS clock common Initial flow adjusted by AF gNB (Fig. 5) AF (Fig. 19) Initial flow adjusted by PCF gNB (Fig. 6) PCF (Fig. 20) Initial flow adjusted by SMF gNB (Fig. 7) SMF (Fig. 21) 1. UE transmits information 1.1 UE -> gNB gNB (Fig. 8) UE, gNB (Figs. 22, 23) 1.2 UE -> SMF gNB (Fig. 9) UE, SMF, gNB (Figs. 24, 25, 26) 1.3 UE -> SMF -> PCF gNB (Fig. 10) UE, PCF, SMF, gNB (Figs. 27, 28, 29, 30) 1.4 UE -> SMF -> PCF -> AF gNB (Fig. 11) UE, AF, PCF, SMF, gNB (Figs. 31, 32, 33, 34, 35) 1.5 UE -> AF gNB (Fig. 12) UE, AF, PCF, SMF, gNB (Figs. 36, 37, 38, 39, 40) 1.6 UE -> UPF gNB (Fig. 13) UPF~ (Fig. 41) 2. UPF transmits information 2.1 UPF -> AF gNB (Fig. 14) AF, PCF, SMF gNB (Figs. 42, 43, 44, 45) 2.2 UPF -> SMF gNB (Fig. 15) SMF, gNB (Figs. 46, 47) 2.3 UPF -> SMF -> PCF gNB (Fig. 16) PCF, SMF, gNB (Figs. 48, 49, 50) 2.4 UPF -> SMF -> PCF -> AF gNB (Fig. 17) AF, PCF, SMF, gNB (Figs. 51, 52, 53, 54) 2.5 UPF -> UE gNB (Fig. 18) UE~ (Fig. 55)
[0081] Hereinafter, embodiments by operating entity and information flow for the transmission of an offset or the application of an offset for adjusting the time are described through FIGS. 5 to 55. Meanwhile, the signalings illustrated in FIGS. 5 to 55 are merely examples for each embodiment, and some signalings between specific entities (e.g., notification, request, response) are not to be interpreted as limiting the embodiments described in the drawings.
[0082] Hereinafter, the offset between the 5GS clock (5G clock) and the TSN clock mentioned in the present disclosure may include at least one of a time offset, which is a time difference, or a frequency offset, which is a rate difference. The time offset may be determined based on the time of the 5GS clock (5G clock) (e.g., 5GS_time) / the time of the TSN clock (e.g., TSN_time). For example, it may be determined based on the difference between the time of the 5GS clock and the time of the TSN clock. According to one embodiment, the UPF (NW-TT) may calculate and update the time offset value. The UPF may update the time offset to the core network entities (e.g., SMF, AF). The time offset may be used to map the burst arrival time based on the TSN clock to the 5GS clock. Network entities associated with the core network (5GC) (e.g., SMF, AF, PCF, AMF) may map the burst arrival time from the TSN clock to the 5GS clock based on the time offset. A base station (e.g., gNB) can obtain the burst arrival time associated with the 5GS clock through TSCAI.
[0083] The frequency offset can be determined based on the frequency of the 5GS clock (5G clock) (e.g., Frequency_5GS) / the frequency of the TSN clock (e.g., Frequency_TSN). For example, it can be determined based on the ratio of the frequency of the TSN clock to the frequency of the 5GS clock. According to one embodiment, the UPF (NW-TT) can calculate and update the frequency offset value. The UPF can update the frequency offset to the core network entities (e.g., SMF, AF). The frequency offset can be used to convert the periodicity based on the TSN clock to the periodicity based on the 5GS clock. Network entities associated with the core network (5GC) (e.g., SMF, AF, PCF, AMF) can map the periodicity from the TSN clock to the 5GS clock based on the frequency offset. A base station (e.g., gNB) can obtain the periodicity associated with the 5GS clock through TSCAI. The behaviors and related descriptions of each entity regarding time offsets can be applied to frequency offsets in the same or similar manner, modified accordingly.
[0085] FIGS. 5, 6, and 7 are flowcharts illustrating that AF (70), PCF (85), and SMF (80), respectively, perform adjustments corresponding to the initial flow of the method in which gNB (50) uses an offset. The signalings shown in FIGS. 5, 6, and 7 are merely examples to explain embodiments in which AF (70), PCF (85), and SMF (80), respectively, perform adjustments corresponding to the initial flow of the method in which gNB (50) uses an offset, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. In this case, a separate stream ID is not required, and a TSCAI including the burst arrival time for each domain is transmitted to gNB (50). The UE (40) manages the TSN domain-specific offset for UL traffic, manages the TSCAI received from the CNC (60) for the TSN domain, and knows the maximum UE Residence Time. The UPF (30) manages the domain-specific offset for DL traffic, and the AF (70) manages the domain-specific TSCAI for DL traffic and knows the maximum UPF Residence Time and the CN PDB. Since the AF (70) can also be responsible for exchanging information with the CNC (60) regarding UL and DL traffic, it knows the domain-specific TSCAI for UL and DL traffic, and knows the maximum UE Residence Time, the maximum UPF Residence Time, and the CN PDB.
[0086] Referring to FIG. 5, information may be transmitted along the following flow to obtain the burst arrival time for the gNB (50). The TSN system transmits TSCAI information (511) to the CNC (60) via CNC management messages, and the CNC (60) transmits TSCAI information (513) to the AF (70) via TSN bridge management messages. The AF (70) may perform adjustments (515) to the burst arrival time of the TSCAI by applying the UL residence time in the case of UL or the UPF residence time and CN PDB in the case of DL. Separately, the initial domain-specific default offset value may be applied. This value is known to the AF (70). Next, AF (70) transmits TSCAI information and default offset to PCF (85) via NR request / response messages (517), PCF (85) transmits TSCAI information and default offset to SMF (80) via N7 PDU session modification request (N7 PDU session modification Req.) (519), SMF (80) transmits default offset to UPF (30) via N4 PDU session modification request and response (N4 PDU session modification Req. / Res) (521, 523), SMF (80) transmits TSCAI information and default offset to AMF (90) via N11 request (N11 Req.) messages (525), and AMF (90) transmits TSCAI information and default offset to gNB (50) via N2 session request (N2 session Req.) messages (527). gNB (50) can modify resources (529) to be used for data transmission with terminal (40) based on the received TSCAI information and default offset, and gNB (50) can also provide an N2 session response (N2 session Res.) to the AMF (90).A message is transmitted (531), and AFM (90) can transmit an N11 Res. message to SMF (80). Upon receiving the N11 Res. message, SMF (80) can transmit an N1 PDU session modification Req. message to UE (40) (535) to inform UE (40) of the default offset, and UE (40) can respond to this message by transmitting an N1 PDU session Modify Res. message to SMF (80) (537). Subsequently, SMF (80) can transmit an N7 notification message to PCF (85) (539), and PCF (85) can transmit an N5 notification message to AF (70) (541).
[0087] In FIG. 6, the PCF (85) performs adjustment (617), the PCF (85) uses the domain-specific default offset transmitted from AF (70), and the PCF (85) knows the maximum UE residence time, the maximum UPF residence time, and the CN PDB. The other operations for the gNB (50) to obtain the burst arrival time are similar to those in FIG. 5.
[0088] In FIG. 7, the SMF (80) performs adjustment (723), and the SMF (80) uses the domain-specific default offset transmitted through AF (70) and PCF (85). Also, in this case, the SMF (80) knows the maximum UE residence time, the maximum UPF residence time, and the CN PDB. The other operations for the gNB (50) to obtain the burst arrival time are similar to those in FIG. 5.
[0089] FIGS. 8, 9, 10, 11, 12, and 13 illustrate a method in which gNB (50) uses an offset, and are flowcharts showing the flow of UE (40)->gNB (50), UE (40)->SMF (80), UE (40)->SMF (80)->PCF (85), UE (40)->SMF (80)-PCF (85)->AF (70), AF (70), UE (40)->UPF (30), respectively. The signalings shown in FIGS. 8, 9, 10, 11, 12, and 13 represent a method in which gNB (50) uses an offset, and are merely examples to explain embodiments for the flow of UE (40)->gNB (50), UE (40)->SMF (80), UE (40)->SMF (80)->PCF (85), UE (40)->SMF (80)-PCF (85)->AF (70), AF (70), UE (40)->UPF (30), respectively, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure.
[0090] In the process of exchanging sync frames with UPF (30) for TSN clock synchronization with UPF (30), UE (40) calculates an offset (e.g., time offset = 5GS-TSN (difference between 5GS clock and TSN clock), e.g., frequency offset) (811, 911, 1011, 1111, 1211, 1311). At this time, if the difference (or change) between the old offset, which is the offset previously used for adjustment, and the new offset, which is newly calculated (measured), exceeds a specific threshold, information transmission is triggered. This threshold is determined by the accuracy difference between the 5GS clock and the TSN clock, or by the size of the period of the stream or the latency requirements. For example, if the accuracy difference between the 5GS clock and the TSN clock is large, the threshold may be set high to prevent too much (i.e., frequent) signaling. Additionally, if the period of the stream is large or the latency requirement is high, this threshold can be set high. In addition to this, the conditions under which the UE (40) sends information may include sending at regular intervals or sending when the signaling load does not exceed a certain threshold. In this case, since the gNB (50) knows the burst arrival time(s) of the streams associated with each domain, if the domain and offset_diff (the difference between the old offset and the new offset) are transmitted to the gNB (50) without considering a separate stream ID, the gNB (50) can adjust the burst arrival times of all streams associated with that domain by utilizing the offset_diff. This process may be implemented by having a separate clock that differs by the offset, synchronized with the 5GS clock for each domain. The operation through the comparison of such offset differences and thresholds can be applied in Solution #2 as well as in FIGS. 22 through 41, as illustrated in FIGS. 8, 9, 10, 11, 12, and 13.
[0092] FIG. 8 illustrates the flow from UE (40) to gNB (50) in a method in which gNB (50) uses offsets. UE (40) transmits only the domain and offset_difference (difference between the old offset and the new offset) information to gNB (50) using RRC (813). gNB (50) adjusts the burst arrival times of all streams corresponding to the domain using offsets (815). At this time, UE (40) sends the domain and offset to AF (70) (819), and the domain-specific offsets managed by AF (70) can be updated.
[0093] FIG. 9 illustrates the UE (40) -> SMF (80) flow in the method in which gNB (50) uses offsets. UE (40) sends a request to SMF (80) using a PDU session modification message, and the domain and offset difference information is transmitted to gNB (50) via N2 message (931). SMF (80) shares the domain and offset difference with PCF (85) and AF (70) through a notification process (915 to 923). Additionally, SMF (80) may share the domain and offset difference with UPF (30) via N4 message (925, 927).
[0094] FIG. 10 shows the UE (40) -> SMF (80) -> PCF (85) flow among the methods in which gNB (50) uses an offset. In FIG. 9, SMF (80) immediately performs the PDU session modification request, but in FIG. 10, PCF (85) performs the judgment regarding the terminal's PDU session modification request.
[0095] FIG. 11 shows the UE (40) -> SMF (80) -> PCF (85) -> AF (70) flow among the methods in which gNB (50) uses an offset. In FIG. 9, SMF (80) immediately performs the PDU session modification request, and in FIG. 10, PCF (85) performs the judgment on the terminal's PDU session modification request, but in FIG. 11, AF (70) makes the judgment on the terminal's PDU session modification request.
[0096] FIG. 12 (70) shows the UE (40) -> AF (70) flow among the methods in which the gNB (50) uses an offset. In FIG. 11, information was transmitted via a NAS message sent by the UE (40) to the SMF (80), but FIG. 12 uses direct communication at the application stage between the UE (40) and the AF. The rest of the process is the same as in FIG. 11.
[0097] FIG. 13 illustrates the UE (40) -> UPF (30) flow in the method in which the gNB (50) uses an offset. Between the UE (40) and the UPF (30), an offset is sent to the UPF (30) whenever a TSN synchronization frame is received for TSN synchronization. Although it may be implemented in other ways, it can be mapped to a process in which an offset is logically transmitted. At this time, if the criteria for triggering information transmission are satisfied, this offset is transmitted to the UPF (30) (1313) with a separate indication that it must be transmitted to the gNB (50). Upon receiving the offset with this indication, the UPF (30) begins the process of transmitting the corresponding domain and offset_difference to the gNB (50). This process can be referenced in FIG. 14, 15, 16, or 17.
[0098] FIGS. 14, 15, 16, 17, and 18 show a method in which gNB (50) uses an offset, and are flowcharts showing the flow of UPF (30)->AF (70), UPF (30)->SMF (80), UPF (30)->SMF (80)->AF (70), UPF (30)->SMF (80)->PCF (85), and UPF (30)->UE (40), respectively. The signalings in FIGS. 14, 15, 16, 17, and 18 represent a method in which gNB (50) uses an offset, and are merely examples to explain embodiments for the UPF (30)->AF (70), UPF (30)->SMF (80), UPF (30)->SMF (80)->AF (70), UPF (30)->SMF (80)->PCF (85), and UPF (30)->UE (40) flows, respectively, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure.
[0099] UPF (30) calculates an offset (e.g., time offset = 5GS-TSN (difference between 5GS clock and TSN clock). e.g., frequency offset) (1411, 1511, 1611, 1711, 1811) during the process of exchanging synchronization frames with UE (40) for TSN clock synchronization. At this time, if the difference between the old offset, which is the offset previously used for adjustment, and the new offset, which is newly calculated (measured), exceeds a specific threshold, it triggers information transmission. This threshold is determined by the accuracy difference between the 5GS clock and the TSN clock, or by the size of the period of the stream or the delay requirements. For example, if the accuracy difference between the 5GS clock and the TSN clock is large, the threshold may be set high to prevent too much (i.e., frequent) signaling. Also, if the period of the stream is large or the delay requirements are high, this threshold may be set high. In addition to the above, the conditions under which the UPF (30) sends information may also be sent at regular intervals or when the signaling load does not exceed a certain threshold. In this case, since the gNB (50) manages the domain-specific streams, there is no need to separately transmit an ID to distinguish the streams. Upon receiving the domain and offset_difference information, the gNB (50) selects all burst arrival time(s) related to the domain and performs adjustments by the offset_difference. This process can also be implemented by having a separate clock that differs by the offset, synchronized with the 5GS clock for each domain. This operation through comparison of the previous offset and current offset difference with a threshold value can be applied in Solution #2 as well as in FIGS. 14, 15, 16, 17, and 18, as well as FIGS. 42 through 55.
[0100] FIG. 14 illustrates the flow of UPF (30) -> AF (70) among the methods in which gNB (50) utilizes an offset. The process (1413) in which UPF (30) is directly connected to the application stage of AF (70) is a new one and requires a separate definition. At this time, UPF (30) must transmit information including the domain and offset difference to AF (70). When the information transmission request triggered by AF (70) is transmitted to SMF (80) via PCF (85) (1417, 1419), SMF (80) transmits this information to gNB (50) via N2 message (1421, 1423).
[0101] FIG. 15 illustrates the flow of UPF (30) -> SMF (80) in the method in which gNB (50) uses offsets. When UPF (30) transmits the domain-specific offset difference (1513, 1515) using N4 Report messages, etc., SMF (80) transmits the domain and offset difference information to gNB (50) via N2 messages using the PDU session modification procedure based on this. In this process, SMF (80) transmits the domain and offset difference to PCF (85), and PCF (85) transmits it to AF (70) as a notification message (1517, 1519, 1523, 1525).
[0102] FIG. 16 shows the flow of UPF (30) -> SMF (80) -> PCF (85) among the methods in which gNB (50) uses an offset. In FIG. 15, SMF (80) decides whether to modify the PDU session, but in FIG. 16, PCF (85) decides whether to modify the PDU session.
[0103] FIG. 17 shows the flow of UPF (30) -> SMF (80) -> PCF (85) -> AF (70) among the methods in which gNB (50) uses an offset. In FIG. 15, SMF (80) decides to modify the PDU session, and in FIG. 16, PCF (85) determines whether to modify the PDU session, but in FIG. 17, AF (70) performs the determination to modify the PDU session.
[0104] FIG. 18 illustrates the flow from UPF (30) to UE (40) in the method by which gNB (50) utilizes an offset. To synchronize TSN with UE (40), UPF (30) sends an offset to UE (40) whenever it receives a TSN synchronization frame from an external TSN node. Although it may be implemented in other ways, it can be mapped to a process in which an offset is logically transmitted. At this time, if the criteria for triggering information transmission are satisfied, this offset is transmitted to UE (40) with a separate indication that it must be transmitted to gNB (50). Upon receiving an offset with this indication, UE (40) initiates the process of transmitting the corresponding domain and offset_difference to gNB (50). This process may be referenced in FIG. 8, 9, 10, 11, or 12.
[0105] FIGS. 19, 20, and 21 are flowcharts illustrating the initial flow of a method in which the gNB (50) utilizes the adjusted burst arrival time, with AF (70), PCF (85), and SMF (80) performing the adjustment, respectively. The signalings in FIGS. 19, 20, and 21 correspond to the initial flow of a method in which the gNB (50) utilizes the adjusted burst arrival time, and are merely examples to explain embodiments in which AF (70), PCF (85), and SMF (80) perform the adjustment, respectively; some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. In this case, a separate stream ID is not required, and a TSCAI including the burst arrival time is transmitted to the gNB (50) for each domain. The UE (40) manages the TSN domain-specific offset for UL traffic, manages the TSCAI received from the CNC (60) for each TSN domain, and knows the maximum UE residence time. The UPF (30) manages the domain-specific offset for DL traffic, and the AF (70) manages the domain-specific TSCAI for DL traffic and knows the maximum UPF residence time and the CN PDB. Since the AF (70) can also be responsible for exchanging information with the CNC (60) regarding UL and DL traffic, it knows the domain-specific TSCAI for UL and DL traffic, and knows the maximum UE residence time, the maximum UPF residence time, and the CN PDB. In FIGS. 5, 6, and 7, the gNB (50) receives the domain and offset as input, whereas in FIGS. 19, 20, and 21, the gNB (50) receives the adjusted burst arrival time as input.
[0106] FIG. 19 corresponds to the initial flow of a method in which gNB (50) uses the adjusted burst arrival time, and AF (70) performs the adjustment (1915). The burst arrival time included in the flow after the adjustment is performed by AF (70) refers to the adjusted burst arrival time.
[0107] FIG. 20 corresponds to the initial flow of a method in which gNB (50) uses the adjusted burst arrival time, and PCF (85) performs the adjustment (2017). From AF (70) to PCF (85), the burst arrival time before adjustment is transmitted, and the burst arrival time included in the flow after the adjustment is performed at PCF (85) refers to the adjusted burst arrival time.
[0108] Figure 21 corresponds to the initial flow of a method in which gNB (50) uses the adjusted burst arrival time, and SMF (80) performs the adjustment (2123). From AF (70) to SMF (80), the burst arrival time before adjustment is transmitted, and the burst arrival time included in the flow after the adjustment is performed at SMF (80) refers to the adjusted burst arrival time.
[0109] As described in FIGS. 19 to 21, the entity performing the conversion operation and the entity transmitting the TSCAI may be the same or different. According to one embodiment (e.g., FIG. 21), an SMF may perform a conversion operation and transmit the TSCAI based on the conversion result. For example, the SMF may determine the transmission of the TSCAI. That is, the SMF may trigger the transmission of the TSCAI. The SMF may generate the TSCAI. The SMF may transmit the generated TSCAI to a 5G-AN, i.e., a base station. Additionally, according to one embodiment (e.g., FIG. 19), a node other than the SMF (e.g., AF) may determine the transmission of the TSCAI. That is, the other node may trigger the transmission of the TSCAI. In this case, the SMF of the 5GC may transmit the TSCAI by the other node to a 5G-AN, i.e., a base station. This is because the SMF is the entity managing the PDU Session and can handle the configuration / update of QoS Flows within the PDU Session. Since TSCAI is transmitted through the QoS update procedure, the 5G-AN and base station SMF can ultimately transmit TSCAI.
[0110] FIGS. 22 and 23 are flowcharts illustrating the UE (40) -> gNB (50) flow utilizing the method of using the adjusted burst arrival time in which the gNB (50) utilizes the adjusted burst arrival time, and that the UE (40) or gNB (50) performs the adjustment (2211, 2315), respectively. The signalings shown in FIGS. 22 and 23 are merely examples to explain embodiments in which the UE (40) -> gNB (50) flow utilizing the adjusted burst arrival time utilizes the method of using the adjusted burst arrival time, and that the UE (40) or gNB (50) performs the adjustment (2211, 2315), respectively; some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. The criteria for the UE (40) to trigger information transmission are the same as those in FIGS. 8, 9, 10, 11, 12, and 13. In this case, since the gNB (50) does not manage streams by domain, the old burst arrival time is used as an ID to distinguish the streams.
[0111] FIG. 22 illustrates a method in which the UE (40)->gNB (50) utilizes the UE (40)->gNB (50) flow to use the adjusted burst arrival time, and the UE (40) performs the adjustment. When the information transfer condition is satisfied, the UE (40) selects all streams related to the domain and performs the adjustment using the offset_difference (2211). When the burst arrival time before adjustment is denoted as the old burst arrival time and the burst arrival time after adjustment is denoted as the new burst arrival time, the UE (40) transmits both of these pieces of information to the gNB (50) (2213). The gNB (50) replaces the old burst arrival time with the new burst arrival time.
[0112] FIG. 23 illustrates a method in which gNB (50) utilizes the UE (40)->gNB (50) flow to use adjusted burst arrival times, and shows a case where gNB (50) performs adjustment. When the information transfer condition is satisfied, UE (40) selects all streams related to the domain and transmits them to gNB (50) with the offset_difference, specifying them as the old burst arrival times (2313). gNB (50) adjusts the old burst arrival times to new burst arrival times (2315) by applying the offset_difference.
[0113] FIGS. 24, 25, and 26 are flowcharts illustrating the UE (40) -> SMF (80) flow, which utilizes the method of gNB (50) utilizing the adjusted burst arrival time, and the UE (40), SMF (80), and gNB (50) respectively performing adjustments (2411, 2525, 2635). The signalings shown in FIGS. 24, 25, and 26 are merely examples to explain embodiments in which the UE (40), SMF (80), and gNB (50) respectively perform adjustments (2411, 2525, 2635), which utilize the UE (40) -> SMF (80) flow, which utilizes the method of gNB (50) utilizing the adjusted burst arrival time, are used, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure.
[0114] The criteria for triggering information transmission by the UE (40) are the same as those described above, and in FIG. 24, the UE (40), and in FIG. 25 and 26, the SMF (80), select all domain-specific streams and use the stream ID instead of the old burst arrival time.
[0115] FIGS. 27, 28, 29, and 30 are flowcharts illustrating the UE (40), PCF (85), SMF (80), and gNB (50) performing adjustments, respectively, in a method in which gNB (50) utilizes the UE (40) -> SMF (80) -> PCF (85) flow of the method in which gNB (50) utilizes the adjusted burst arrival time. The signalings in FIGS. 27, 28, 29, and 30 are merely examples to explain embodiments in which UE (40), PCF (85), SMF (80), and gNB (50) perform adjustments, respectively, in a method in which gNB (50) utilizes the UE (40) -> SMF (80) -> PCF (85) flow of the method in which gNB (50) utilizes the adjusted burst arrival time, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. In FIGS. 24, 25, and 26, the SMF (80) determines the PDU session modification, but in FIGS. 27, 28, 29, and 30, the PCF (85) determines the PDU session modification. In FIG. 27, the UE (40), and in FIGS. 28, 29, and 30, the PCF (85) select all domain-specific streams and use the stream ID instead of the old burst arrival time.
[0116] FIGS. 31, 32, 33, 34, and 35 are flowcharts illustrating the UE (40) -> SMF (80) -> PCF (85) -> AF (70) flow, in which the gNB (50) utilizes the adjusted burst arrival time, and the UE (40), AF (70), PCF (85), SMF (80), and gNB (50) each perform adjustments. The signalings in FIGS. 31, 32, 33, 34, and 35 utilize the UE (40) -> SMF (80) -> PCF (85) -> AF (70) flow among the methods in which gNB (50) uses the adjusted burst arrival time, and are merely examples to explain embodiments in which UE (40), AF (70), PCF (85), SMF (80), and gNB (50) each perform adjustments, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. In FIGS. 24, 25, and 26, SMF (80) determines the PDU session modification, and in FIGS. 27, 28, 29, and 30, PCF (85) determines the PDU session modification, but in FIGS. 31, 32, 33, 34, and 35, AF (70) determines the PDU session modification. In FIG. 31, UE (40), and in FIG. 32, 33, 34, and 35, AF (70) select all domain-specific streams and use the stream ID instead of the old burst arrival time.
[0117] FIGS. 36, 37, 38, 39, and 40 are flowcharts illustrating the UE (40)->AF (70) flow, which utilizes the method of gNB (50) utilizing the adjusted burst arrival time, and respectively, the UE (40), AF (70), PCF (85), SMF (80), and gNB (50) performing adjustments. The signalings in FIGS. 36, 37, 38, 39, and 40 are merely examples to explain embodiments in which the UE (40), AF (70), PCF (85), SMF (80), and gNB (50) perform adjustments, which utilize the UE (40)->AF (70) flow, which utilizes the method of gNB (50) utilizing the adjusted burst arrival time, and respectively, some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. In FIGS. 31, 32, 33, 34, and 35, the information transmitted by the UE (40) to the SMF (80) via a NAS message is transmitted to the AF (70) via the PCF (85) using a notification, whereas in FIGS. 36, 37, 38, 39, and 40, the UE (40) transmits the information to the AF (70) using an application-level message.
[0118] FIG. 41 is a flowchart illustrating the use of the UE (40) -> UPF (30) flow among the methods using the adjusted burst arrival time in gNB (50). The signalings in FIG. 41 are merely examples to explain an embodiment using the UE (40) -> UPF (30) flow among the methods using the adjusted burst arrival time, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. Adjustment is shown in the case where it is combined with the UPF (30) -> AF (70) flow among various flows from the subsequent UPF (30), and adjustment is performed at PCF (85) (4123). For other processes of transmitting information from UPF (30), refer to FIG. 42 through 54.
[0119] FIGS. 42, 43, 44, and 45 are flowcharts illustrating the use of the UPF (30)->AF (70) flow among the methods in which gNB (50) utilizes the adjusted burst arrival time, and respectively, AF (70), PCF (85), SMF (80), and gNB (50) perform adjustment. The signalings in FIGS. 42, 43, 44, and 45 are merely examples to explain embodiments in which AF (70), PCF (85), SMF (80), and gNB (50) perform adjustment among the methods in which gNB (50) utilizes the UPF (30)->AF (70) flow among the methods in which gNB (50) utilizes the adjusted burst arrival time, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. The criteria for triggering information transmission are the same as those in FIGS. 14 through 18. After the adjustment is performed, the old burst arrival time is used as the stream ID.
[0120] FIGS. 46 and 47 are flowcharts illustrating the use of the UPF (30) -> SMF (80) flow among the methods using the adjusted burst arrival time of gNB (50), and showing that SMF (80) or gNB (50) performs the adjustment, respectively. The signalings in FIGS. 46 and 47 are merely examples to explain embodiments in which SMF (80) or gNB (50) performs the adjustment among the methods using the UPF (30) -> SMF (80) flow among the methods using the adjusted burst arrival time, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. The criteria for triggering information transmission are the same as those in FIGS. 14 through 18. After the adjustment is performed, the old burst arrival time is used as the stream ID.
[0121] FIGS. 48, 49, and 50 are flowcharts illustrating the method in which gNB (50) utilizes the UPF (30) -> SMF (80) -> PCF (85) flow, respectively, to utilize the adjusted burst arrival time, and in which PCF (85), SMF (80), or gNB (50) perform adjustment, respectively. The signalings in FIGS. 48, 49, and 50 are merely examples to explain embodiments in which PCF (85), SMF (80), or gNB (50) perform adjustment, respectively, utilizing the UPF (30) -> SMF (80) -> PCF (85) flow, respectively, to utilize the adjusted burst arrival time, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. The criteria for triggering information transmission are the same as in FIGS. 14 through 18. After the adjustment is performed, the old burst arrival time is used as the stream ID.
[0122] FIGS. 51, 52, 53, and 54 are flowcharts illustrating the method of using the UPF (30)->SMF (80)->PCF (85)->AF (70) flow among the methods of using the adjusted burst arrival time of gNB (50), and illustrating that AF (70), PCF (85), SMF (80), or gNB (50) perform the adjustment, respectively. The signalings of FIGS. 51, 52, 53, and 54 utilize the UPF (30)->SMF (80)->PCF (85) flow among the methods in which gNB (50) utilizes the adjusted burst arrival time, and utilize the UPF (30)->SMF (80)->PCF (85)->AF (70) flow among the methods in which gNB (50) utilizes the adjusted burst arrival time, and are merely examples to explain embodiments in which AF (70), PCF (85), SMF (80), or gNB (50) perform adjustment, respectively, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. The criteria for triggering information transmission are the same as those in FIGS. 14 through 18. After the adjustment is performed, the old burst arrival time is used as the stream ID.
[0123] FIG. 55 illustrates a method in which gNB (50) utilizes the UPF (30)->UE (40) flow among methods utilizing the adjusted burst arrival time, combined with the UE (40)->gNB (50) flow among subsequent flows from UE (40), and performs adjustment (5519) at gNB (50). The signalings in FIG. 55 are merely examples to explain an embodiment in which gNB (50) utilizes the UPF (30)->UE (40) flow among methods utilizing the adjusted burst arrival time, and some signalings between specific entities are not to be interpreted as limiting the operation of the embodiments to be described in each figure. For other processes of transmitting information from UE (40), refer to FIG. 22 through 40.
[0124] As described through FIGS. 42 to 55, depending on which entity (e.g., AF, SMF, etc.) performs the mapping operation, the path by which the UPF transmits and updates the difference between the 5G clock and the TSN clock (e.g., time offset, period offset) varies. For example, as shown in FIG. 51, the UPF can transmit information regarding the difference between the 5G clock and the TSN clock (hereinafter, difference information) to the SMF. The SMF can transmit the difference information to the AF. The AF performs the mapping operation based on the difference information and can obtain the burst arrival time converted to the 5G clock or the converted period. The AF transmits information regarding the converted burst arrival time or the converted period to the SMF, and the SMF can transmit information regarding the 5G clock (e.g., burst arrival time, period) to the base station (e.g., gNB (50)) through the PDU session procedure. For example, as shown in FIG. 52, the UPF can transmit information regarding the difference between the 5G clock and the TSN clock (hereinafter referred to as difference information) to the SMF. The SMF can transmit the difference information to the AF. The AF can transmit the difference information to the PCF. The PCF can perform a mapping operation based on the difference information and obtain a burst arrival time or a converted period based on the 5G clock. The PCF transmits information regarding the converted burst arrival time or the converted period to the SMF, and the SMF can transmit information regarding the TSN clock (in respect to) to a base station (e.g., gNB (50)) through a PDU session procedure. For example, as shown in FIG. 53, the UPF can transmit information regarding the difference between the 5G clock and the TSN clock (hereinafter referred to as difference information) to the SMF. The SMF can perform a mapping operation based on the difference information and obtain a burst arrival time or a converted period based on the 5G clock.The SMF transmits information regarding the converted burst arrival time or converted period to the SMF, and the SMF can transmit information regarding the TSN clock to the base station (e.g., gNB (50)) through the PDU session procedure. Additionally, for example, as shown in FIG. 54, the UPF can transmit information regarding the difference between the 5G clock and the TSN clock (hereinafter, difference information) to the SMF. The SMF can transmit the difference information to the base station. The base station can obtain the converted burst arrival time or converted period based on the 5G clock. Additionally, for example, as shown in FIG. 55, the UPF can transmit information regarding the difference between the 5G clock and the TSN clock (hereinafter, difference information) to the terminal. The terminal can transmit the difference information to the base station. The base station can obtain the converted burst arrival time or converted period based on the 5G clock.
[0126] Since the base station (e.g., gNB) does not know the TSN clock, signaling between entities of the core network is described to transmit the offset, which is the difference between the 5G clock and the TSN clock, to the base station, or to transmit information reflecting the offset (e.g., burst arrival time related to the 5G clock reference). At this time, the offset, which is the difference between the 5GS clock and the TSN clock, may be indicated by distinguishing between the absolute time difference and the speed difference. In one embodiment, the time offset = T_5GS - T_TSN (the difference between the 5GS clock and the TSN clock) can be calculated at the UPF (30) or UE (40), and the frequency offset = Frequency_5GS / Frequency_TSN can be calculated. In this case, the time offset can be used to convert the burst arrival time based on the TSN clock to the 5GS clock reference. The frequency offset can be used to convert the periodicity based on the TSN clock to the 5GS clock reference.
[0127] When the UPF (30) or UE (40) transmits an offset to the SMF / PCF / AF, etc., either one of them may transmit it, or both may support it. In some embodiments, the UPF (30) and the UE (40) may transmit the offset to at least one of the SMF, PCF, or AF. Additionally, in some embodiments, the UPF (30) may transmit the offset to at least one of the SMF, PCF, or AF. When either one transmits it, only the UPF may support it, or the UE may support it; however, since the UE uses Air resources when transmitting, the UPF has the advantage of saving resources when transmitting. Additionally, in some embodiments, the UE (40) may transmit the offset to at least one of the SMF, PCF, or AF. In special cases, such as when TSC traffic is transmitted from one UE to another, where the UPF does not know the TSN Clock and only the UE knows the TSN Clock, the UE may transmit the offset.
[0128] When deriving TSCAI, the difference between the 5GS clock and the TSN clock must be reflected, and the CN PDB (packet delay budget) or UE residence time must be corrected. These two processes may be performed in one network entity (NE) or in another NE. The NE may be an entity of 5GC (e.g., the core network (104) of FIG. 1a). In one embodiment, AF may reflect the difference between the 5GS clock and the TSN clock, and SMF may correct the CN PDB (packet delay budget) or UE residence time. AF may convert the periodicity based on the TSN clock to the 5GS clock standard using a frequency offset, and SMF may convert the burst arrival time based on the TSN clock to the 5GS clock standard using a time offset, and may be responsible for mapping the Burst Arrival Time reflecting the CN-PDB, UE-Residence Time, etc. Additionally, in one embodiment, AF may reflect the difference between the 5GS clock and the TSN clock, and AMF may correct the CN PDB or UE residence time. Additionally, in one embodiment, AF may reflect the difference between the 5GS clock and the TSN clock, and AF may correct the CN PDB or UE residence time. Additionally, in one embodiment, AF may reflect the difference between the 5GS clock and the TSN clock, and PCF may correct the CN PDB or UE residence time. Additionally, in one embodiment, SMF may reflect the difference between the 5GS clock and the TSN clock, and SMF may correct the CN PDB or UE residence time. Additionally, in one embodiment, SMF may reflect the difference between the 5GS clock and the TSN clock, and AMF may correct the CN PDB or UE residence time. Additionally, in one embodiment, SMF may reflect the difference between the 5GS clock and the TSN clock, and AF may correct the CN PDB or UE residence time.In addition, as an example, the SMF may reflect the difference between the 5GS clock and the TSN clock, and the PCF may correct the CN PDB or UE residence time.
[0129] In this disclosure, the roles / signaling of each entity regarding the entity mapping time offsets and period offsets have been described. However, the various embodiments of this disclosure are not limited thereto. In some embodiments, the entity responsible for the function of mapping time offsets and the entity responsible for the function of mapping frequency offsets may be configured independently of each other. That is, in order to obtain information within TSCAI related to the TSN clock, functional separation between AF and SMF may be performed. According to one embodiment, AF may perform time conversion using time offsets (e.g., mapping related to the burst arrival time of TSCAI), and SMF may perform period conversion using frequency offsets (e.g., mapping related to the period of TSCAI). AF may perform time conversion of TSCAI, and SMF may only reflect CN-PDB, UE-Residence Time, etc. within 5GS. In addition, according to one embodiment, AF maps only Periodicity (mapping periodic information from the TSN clock to the 5G clock) by reflecting only the period offset (e.g., Frequency Ratio), and SMF can be responsible for mapping the Burst Arrival Time including CN-PDB, UE-Residence Time, etc.
[0131] In this disclosure, a gNB is described by way of example as a base station of an access network (AN), but the embodiments of this disclosure are not limited thereto. That is, the embodiments of this disclosure can be applied in the same or similar manner to base stations using a 5G core network in addition to a gNB. For example, when a base station associated with LTE RAT (radio access technology) (e.g., eNB) is connected to 5GC (5G core) instead of EPC, the base station can acquire TSSAI according to Solution 1 or Solution 2 described through FIGS. 5 to 55.
[0133] Methods according to the embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.
[0134] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present invention.
[0135] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.
[0136] In addition, the above program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present invention through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present invention.
[0138] In the specific embodiments of the present invention described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present invention is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, or even if a component is expressed in the singular form, it may be composed in the plural form.
[0139] Meanwhile, although specific embodiments have been described in the detailed description of the present invention, it is understood that various modifications are possible within the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.
Claims
Claim 1 A method performed by a session management function (SMF) in a wireless communication system comprises: receiving information regarding an offset between a 5th generation system (5GS) time and a time-sensitive networking (TSN) time from a user-plane function (UPF); mapping a burst arrival time from a TSN clock to a 5th generation clock based on the offset; and transmitting time-sensitive communication assistant information (TSCAI) including information regarding the burst arrival time mapped to the 5G clock to a node of an access network, wherein if the difference between the previous offset and the offset is greater than a threshold value, the information regarding the offset is received from the UPF. Claim 2 delete Claim 3 delete Claim 4 A method according to claim 1, wherein the TSCAI is transmitted based on a PDU (protocol data unit) session modification procedure. Claim 5 A method according to claim 1, wherein the burst arrival time is determined based on the CN (core network) PDB (packet delay budget) when the burst arrival time is related to a downlink, and based on the UE residence time when the burst arrival time is related to an uplink. Claim 6 The method of claim 1, wherein the method further comprises the step of receiving information from an application function (AF); and the step of determining the TSCAI based on the received information. Claim 7 The method of claim 1 further comprises the step of mapping a period of a TSN clock to a 5G clock based on a frequency offset between a 5GS time and a TSN time, wherein the frequency offset is received from the UPF, and the TSCAI includes information regarding the period mapped to the 5G clock. Claim 8 A method according to claim 7 in which, when the change from the previous frequency offset between the TSN time and the 5GS time to the frequency offset is greater than a threshold value, information regarding the frequency offset is received from the UPF. Claim 9 A method performed by a node of an access network in a wireless communication system, wherein the method comprises the step of receiving time-sensitive communication assistant information (TSCAI) containing information regarding burst arrival times related to a 5G (5th generation) clock from a session management function (SMF), wherein the information regarding burst arrival times is determined based on an offset between a 5GS (5th generation system) time and a time-sensitive networking (TSN) time provided by a user-plane function (UPF), and wherein if the difference between the offset and the previous offset is greater than a threshold value, the information regarding the offset is provided by the UPF. Claim 10 delete Claim 11 delete Claim 12 delete Claim 13 In a session management function (SMF) of a wireless communication system, the SMF comprises at least one transceiver and at least one processor coupled to the at least one transceiver, wherein the at least one processor receives information regarding an offset between a 5GS (5th generation system) time and a TSN (time-sensitive networking) time from a user-plane function (UPF), maps a burst arrival time from a TSN clock to a 5G (5th generation) clock based on the offset, transmits time-sensitive communication assistant information (TSCAI) including information regarding the burst arrival time mapped to the 5G clock to a node of an access network, and if the difference between the previous offset and the offset is greater than a threshold value, the information regarding the offset is received from the UPF. Claim 14 delete Claim 15 delete Claim 16 In claim 13, the SMF is transmitted based on a protocol data unit (PDU) session modification procedure. Claim 17 In claim 13, the burst arrival time is determined based on the CN (core network) PDB (packet delay budget) when the burst arrival time is related to a downlink, and based on the UE residence time when the burst arrival time is related to an uplink, in the SMF. Claim 18 The SMF of claim 13, wherein the at least one processor is additionally configured to control the at least one transceiver to receive information from an application function (AF) and to determine the TSCAI based on the received information. Claim 19 In claim 13, the at least one processor maps the period of the TSN clock to the 5G clock based on a frequency offset between the 5GS time and the TSN time, the frequency offset is received from the UPF, and the TSCAI includes information regarding the period mapped to the 5G clock, SMF. Claim 20 In claim 19, when the change from the previous frequency offset between the TSN time and the 5GS time to the frequency offset is greater than a threshold value, the information regarding the frequency offset is received from the UPF, the SMF. Claim 21 An access network node of a wireless communication system, wherein the access network node comprises at least one transceiver and at least one processor coupled to the at least one transceiver, and the at least one processor receives time-sensitive communication assistant information (TSCAI) containing information regarding burst arrival times related to a 5G (5th generation) clock from a session management function (SMF), wherein the information regarding burst arrival times is determined based on an offset between a 5GS (5th generation system) time and a time-sensitive networking (TSN) time provided by a user-plane function (UPF), and wherein if the difference between the offset and the previous offset is greater than a threshold value, the information regarding the offset is provided by the UPF. Claim 22 delete Claim 23 delete Claim 24 delete Claim 25 delete Claim 26 delete Claim 27 delete Claim 28 delete Claim 29 delete Claim 30 delete Claim 31 delete Claim 32 delete
