Support for QoS flow-specific uncertainty attributes

Abstract

A method, a network node, and a core network node are provided. According to one aspect, a network node (16) configured to communicate with a wireless device (22) via an access network (12) is provided. The network node (16) includes processing circuitry, and the processing circuitry (68) is configured to: receive at least one parameter from a core network node (14), where the at least one parameter indicates a synchronization accuracy level required for a TSN clock in a time-sensitive network (TSN) (23); and implement, in the access network (12), one of a plurality of methods for distributing access network clock information to the wireless device (22) and for determining downlink propagation delay information, based on the synchronization accuracy level for the TSN clock, where each method is associated with a different synchronization accuracy level for the access network clock.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and in particular, to supporting uncertainty attributes specific to Quality of Service (QoS) flows. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) is developing the 5th Generation (5G) wireless network communication standard, also known as New Radio (NR), to support Time-Sensitive Networking (TSN). It is expected that TSN will be integrated into Ethernet-based industrial communication networks. Applications may include factory automation networks.

[0003] This disclosure relates to the problem of inaccuracy and / or uncertainty inherent in the method for relaying the 5G system clock (i.e., the access network clock used as the reference time) from a source node in the 5G system to a wireless device (WD) that supports IoT terminal devices. The inaccuracy of concern is the error introduced due to the attempt to identify the radio frequency (RF) propagation delay that occurs when the 5G base station (gNodeB or gNB) sends the 5G system clock over the radio interface within a message. This message can be, for example, within a System Information Block (SIB) or a Radio Resource Control (RRC) unicast message. The value of the 5G system clock should be compensated to ensure that the clock value received by the WD is as close as possible to the clock value in the corresponding gNB or other network nodes that know the 5G system clock. In other words, the better the accuracy of relaying the 5G system clock from its source node to the WD, the better the accuracy that will be achieved when the external TSN Grandmaster (GM) clock is relayed from the TSN master node through the 5G system to the WD (and subsequently to the terminal station):

[0004] · When the external TSN GM clock is received by the 5G system, an ingress timestamp is executed, and when the TSN GM clock (relayed through the 5G system) reaches the WD, an egress timestamp is executed. See Figure 1 . Note that since the TSN GM clock can have an arbitrary arrangement, the ingress timestamp can be executed at various locations within the 5GS system, for example, at the User Plane Function TSN Converter (UPF-TT) or at the DS-TT.

[0005] · The difference between the two timestamps is a reflection of the 5G dwell time experienced when relaying the TSN GM clock through the 5G system, and thus it is used to adjust the value of the external TSN GM clock when it is received at the egress point.

[0006] · Timestamp addition is based on the 5G system clock and improves the accuracy of delivering the clock to the WD by allowing a more precise determination of the propagation delay experienced when sending the clock from the network node to the WD.

[0007] Since WD subsequently distributes the clock to Internet of Things (IoT) end devices, there is an additional source of inaccuracy. This distribution is used to enable Time-Sensitive Networking (TSN) capabilities for IoT device operations specific to a working domain (a specific factory area) associated with a given working clock, such as time-aware scheduling.

[0008] Identification of WD that requires the 5G system clock

[0009] Currently, it is expected that network nodes such as gNBs will use implementation-specific methods to determine which WDs need to receive 5G system clock information. Standardization of such methods does not yet exist. The network node must then decide (a) which method to use to provide 5G system clock information to the WDs that require the system clock (i.e., SIB or RRC unicast), and (b) which method (if any) to use to allow the WDs to determine the downlink propagation delay (PD) compensation to apply to the 5G system clock received from the network node.

[0010] Methods available for determining downlink PD compensation

[0011] 3GPP Timing Advance Command

[0012] The 3GPP Timing Advance (TA) command is a traditional method used in cellular communication for uplink transmission synchronization for the following scenarios.

[0013] a) Initially, at connection establishment, the absolute timing parameter is passed to the WD using the Media Access Control (MAC) Radio Access Response (RAR) element;

[0014] b) After connection establishment, relative timing corrections can be sent to the WD using MAC Control Elements (CEs) (e.g., the WD may move due to RF channel changes caused by the environment).

[0015] The downlink propagation delay (PD) for a given WD can be estimated by: (a) first summing the TA values indicated by the RAR (Random Access Response) and all subsequent TA values sent using the MAC CE control element, and (b) taking a certain portion (e.g., 50% when assuming that the downlink and uplink propagation delays are substantially the same) of the total TA value resulting from the sum of all TA values. The estimated PD can then be used to understand the time synchronization dynamics, e.g., for accurately tracking the value of the clock at the WD relative to the value of the clock in some other network node.

[0016] Pre-compensation

[0017] In addition to the 3GPP TA method, a pre-compensation-based method can be designed to reduce the latency introduced by the round-trip time (RTT), where the compensation factor is derived using a specific criterion rather than the latency based on RTT (e.g., TA). The compensation factor can be known instead of being determined on the fly as in the RTT method. The same pre-compensation value can be sent to multiple WDs.

[0018] The current process for sending the 5G system clock from a network node to a WD includes:

[0019] c) SIB broadcast, where a specific SIB message includes the value for the 5G system clock, which has a value relative to a specific point in the superframe number (SFN) structure (e.g., the end of the last SFN for sending system information).

[0020] d) RRC unicast, where a dedicated RRC message is used to send the value for the 5G system clock to a specific WD, which has a value relative to a specific point in the SFN structure (e.g., the end of SFNx).

[0021] Since the above definition of the 5G system clock involves when the SFN reference point appears at the network node antenna, considering the potential impact of the downlink propagation delay on the synchronization (uncertainty) budget allowed for the TSN GM clock (i.e., for cases where it is important for the WD to accurately derive the value for the downlink PD and use this value to correct the 5G system clock time at the WD), for cells where the downlink transmission delay (PD) is significant, individual compensation for the RF air propagation delay (PD) between the network node and the WD will be required.

[0022] There are different methods available for estimating and compensating the 5G system clock based on the downlink delay propagation. In practice, one method may be the best during certain conditions and for a specific WD, while another method may be most suitable for another WD, even if both WDs are served by the same network node (gNB). However, 3GPP has not defined how to best select the most appropriate method among the numerous possibilities based on numerous input parameters for achieving end-to-end timing accuracy of the TSN GM clock and minimizing the signaling overhead.

[0023] To enable the network and the gNB to select between different methods for distributing 5GS timing (5G system clock) to the WDs while doing so in a resource-efficient manner, the network node (e.g., gNB) can obtain or derive the following information:

[0024] 1) Which specific WDs are involved in the TSN GM clock distribution:

[0025] · Since the TSN GM clock is delivered as user plane information through the 5G system, it can be assumed that the TSN network node (e.g., CNC) supports a method for determining which terminal stations (Ethernet Media Access Control (MAC) addresses) need to use any given TSN GM clock;

[0026] · When receiving a terminal station - specific Ethernet Packet Data Unit (PDU) containing TSN GM clock information, it is expected that the UPF uses the MAC - address - to - WD mapping function to identify the corresponding WD and deliver it as user plane information to the WD;

[0027] · Therefore, the present disclosure does not address the problem of determining which terminal stations need to use any given TSN GM clock and MAC - address - to - WD mapping when performing TSN GM clock distribution;

[0028] 2) What accuracy level is required for the distribution of any given TSN GM clock:

[0029] · This is considered to be determined based on the application using the given TSN GM clock, where the accuracy requirements can be the same regardless of the WD to which the TSN GM clock is delivered;

[0030] · However, for reasons of flexibility, the accuracy level required by the WD for any given TSN GM clock can be kept WD - specific, and thus, an appropriate method for sending 5G system clock information to the WD can be determined based on the accuracy requirements of the TSN GM clock it supports.

[0031] 3) Does the WD perform ingress timestamping for the case where the TSN GM clock is distributed in the uplink (the TSN GM clock resides in the terminal station behind the WD), or does the WD perform egress timestamping for the case where the TSN GM clock is distributed in the downlink (the TSN GM clock is delivered to the terminal station behind the WD):

[0032] · Whether the WD performs ingress timestamping or egress timestamping, the WD will need to receive 5G system clock information. If the WD receives the TSN GM clock information through a downlink 5G Quality of Service (QoS) flow, the WD performs egress timestamping, and if the WD receives the TSN GM clock information from the terminal station (for transmission through an uplink 5G QoS flow), the WD performs ingress timestamping;

[0033] · Therefore, the WD can use its knowledge of how it receives the TSN GM clock information (i.e., downlink 5G QoS flow or from the terminal station) to determine what type of timestamp to apply. Summary of the Invention

[0034] Some embodiments advantageously provide methods, network nodes, and core network nodes for supporting Quality of Service (QoS) flow-specific uncertainty attributes. Different methods that can be used by 5G network nodes to determine whether to send the 5G system clock to a wireless device (WD) are disclosed. Based on the configuration information of the core network (CN), it can be expected to (a) identify which WDs need which TSN GM clocks, and (b) identify which 5G QoS flow among one or more 5G QoS flows is dedicated to supporting the transmission of this information. This knowledge can be made available to the network node so that once the network node knows that a WD needs a TSN GM clock, the network node also implicitly knows that the WD needs to be sent the 5G system clock (for performing timestamping to measure the 5G dwell time experienced by the TSN GM clock). Thus, the network node provided with this knowledge avoids the need for the WD to explicitly send a notification to the network node indicating that it needs to receive the 5G system clock.

[0035] - It is also expected that for 3GPP 5G Release 17 (3GPP Rel-17), new round-trip time (RTT) procedures will be needed to improve the accuracy of determining the downlink propagation delay (PD) for a given WD. This means that the network node will need to know whether it should use the traditional RTT procedure (i.e., the traditional TA procedure) or the new RTT procedure to provide the downlink PD compensation information to the WD. Regardless of which of the traditional RTT procedure or the new RTT procedure is used, the network node will implicitly know that the corresponding WD needs to receive the 5G system clock.

[0036] - Some considerations provide that at least one dedicated 5G QoS flow will be used to send TSN GM clock information (i.e., General Precision Time Protocol (gPTP) signaling) to the WD. Thus, providing the network node with the knowledge of the existence of such a 5G QoS flow can be used to implicitly indicate that any WD receiving user plane information using this 5G QoS flow inherently needs 5G reference time information.

[0037] Some embodiments may include the following methods:

[0038] - Allowing a network node (e.g., gNB) to determine the accuracy level required by a WD to support any given TSN GM clock, and thus determine an appropriate method for sending 5G system clock information to that WD;

[0039] - Allowing the WD to determine whether it is to perform ingress timestamping or egress timestamping based on whether it receives the TSN GM clock information from a terminal station (in which case, perform ingress timestamping) or through a downlink 5G QoS flow (in which case, perform egress timestamping).

[0040] According to one aspect of the present disclosure, there is provided a network node configured to communicate with a wireless device via an access network. The network node includes processing circuitry configured to: receive at least one parameter from a core network node, wherein the at least one parameter indicates a synchronization accuracy level required for a TSN clock in a time-sensitive network (TSN); and implement, in the access network, one of a plurality of methods for distributing access network clock information to the wireless device and for determining downlink propagation delay information, based on the synchronization accuracy level for the TSN clock, wherein each of the plurality of methods is associated with a different synchronization accuracy level for the access network clock.

[0041] According to one or more embodiments of this aspect, the downlink propagation delay information is configured to allow updating of an access network clock associated with the access network clock information, wherein the updated access network clock is configured to allow timestamping of the TSN clock information for compensation of the TSN clock information. According to one or more embodiments of this aspect, the at least one parameter is time-sensitive communication assistance information (TSCAI), and the TSCAI has a master GM clock synchronization accuracy parameter. According to one or more embodiments of this aspect, the TSN clock information is relayed through the access network using at least one QoS flow for transmission to a terminal station in the TSN via the wireless device.

[0042] According to one or more embodiments of this aspect, the at least one QoS flow includes a first QoS flow and a second QoS flow, wherein the TSN clock information is relayed through the access network using the first QoS flow associated with a first PDU session from the wireless device and the second QoS flow associated with a second PDU session from another wireless device connected to the terminal station that requires the TSN clock. According to one or more embodiments of this aspect, the at least one QoS flow is configured to indicate multiple accuracy levels for the TSN clock. According to one or more embodiments of this aspect, the TSN clock information is distributed in the user plane of the access network.

[0043] According to one or more embodiments of this aspect, the synchronization accuracy level for accessing the network clock corresponds to the end-to-end synchronization accuracy required by the TSN clock. According to one or more embodiments of this aspect, multiple methods include at least one of the following: a first method, which includes determining the propagation delay in the access network using a traditional TA process; a second method, which includes determining the propagation delay in the access network using a round-trip time (RTT) process, where the RTT process has a higher synchronization accuracy than the traditional TA process; and a third method, which does not include determining the propagation delay in the access network. The determined propagation delay is configured for access network clock compensation. According to one or more embodiments of this aspect, multiple methods include at least one of the following: a first method, which is configured to broadcast access network clock information to a wireless device using a system information block (SIB) broadcast; and a second method, which is configured to distribute access network clock information to a wireless device using a radio resource control (RRC) unicast.

[0044] According to another aspect of the present disclosure, a wireless device is provided, which is configured to communicate with a network node via an access network and communicate with a terminal station in a time-sensitive network (TSN). The wireless device includes a processing circuit, which is configured to: receive access network clock information and downlink propagation delay information via one of multiple methods that meet the synchronization accuracy level for the access network required by the wireless device for the TSN clock in the TSN, where each of the multiple methods is associated with a different synchronization accuracy level for the access network clock; and cause the TSN clock information to be transmitted to the terminal station in the TSN.

[0045] According to one or more embodiments of this aspect, the processing circuit is configured to: determine the propagation delay based at least on the downlink propagation delay; update the access network clock based on the determined propagation delay; perform adding an egress timestamp on the TSN clock information received from the network node, where the adding of the egress timestamp is performed using the updated access network clock; determine that the TSN clock information needs to be adjusted based at least on the added egress timestamp; and compensate the TSN clock information based on the determined adjustment. According to one or more embodiments of this aspect, the processing circuit is configured to: determine the propagation delay based at least on the downlink propagation delay; update the access network clock based on the determined propagation delay; and perform adding an ingress timestamp on the TSN clock information received from the terminal station in the TSN, where the adding of the ingress timestamp is performed using the updated access network clock, and where the ingress timestamp is configured to adjust the TSN clock information. According to one or more embodiments of this aspect, the TSN clock information is relayed through the access network using at least one QoS flow.

[0046] According to one or more embodiments of this aspect, at least one QoS flow includes a first QoS flow and a second QoS flow, and wherein, the TSN clock information is relayed through the access network using the first QoS flow associated with the first protocol data unit (PDU) session from the wireless device and the second QoS flow associated with the second PDU session from another wireless device connected to the terminal station that requires the TSN clock. According to one or more embodiments of this aspect, at least one QoS flow is configured to indicate multiple accuracy levels for the TSN clock. According to one or more embodiments of this aspect, the TSN clock information is received in the user plane of the access network.

[0047] According to one or more embodiments of this aspect, the synchronization accuracy level for the access network clock corresponds to the end-to-end synchronization accuracy required for the TSN clock. According to one or more embodiments of this aspect, multiple methods include at least one of the following: a first method that includes determining the propagation delay in the access network using a traditional TA process; a second method that includes determining the propagation delay in the access network using a round-trip time (RTT) process, wherein the RTT process has a higher synchronization accuracy than the traditional TA process; and a third method that does not include determining the propagation delay in the access network. The determined propagation delay is configured for access network clock compensation. According to one or more embodiments of this aspect, multiple methods include at least one of the following: a first method that is configured to broadcast the access network clock information to the wireless device using a system information block (SIB) broadcast; and a second method that is configured to distribute the access network clock information to the wireless device using a radio resource control (RRC) unicast.

[0048] According to another aspect of the present disclosure, a method implemented by a network node configured to communicate with a wireless device via an access network is provided. Receive at least one parameter from a core network node, wherein the at least one parameter indicates the synchronization accuracy level required for the TSN clock in a time-sensitive network (TSN). Based on the synchronization accuracy level for the TSN clock, implement one of multiple methods in the access network for distributing the access network clock information to the wireless device and for determining the downlink propagation delay information, wherein each of the multiple methods is associated with a different synchronization accuracy level for the access network clock.

[0049] According to one or more embodiments of this aspect, the downlink propagation delay information is configured to allow updating of the access network clock associated with the access network clock information, wherein the updated access network clock is configured to allow timestamping of the TSN clock information for compensation of the TSN clock information. According to one or more embodiments of this aspect, at least one parameter is time-sensitive communication assistance information TSCAI, and the TSCAI has a master GM clock synchronization accuracy parameter. According to one or more embodiments of this aspect, the TSN clock information is relayed through the access network using at least one QoS flow for transmission to a terminal station in the TSN via a wireless device.

[0050] According to one or more embodiments of this aspect, at least one QoS flow includes a first QoS flow and a second QoS flow. The TSN clock information is relayed through the access network using the first QoS flow associated with the first protocol data unit PDU session from the wireless device and the second QoS flow associated with the second PDU session from another wireless device connected to the terminal station that requires the TSN clock. According to one or more embodiments of this aspect, at least one QoS flow is configured to indicate multiple accuracy levels for the TSN clock. According to one or more embodiments of this aspect, the TSN clock information is distributed in the user plane of the access network.

[0051] According to one or more embodiments of this aspect, the synchronization accuracy level for the access network clock corresponds to the end-to-end synchronization accuracy required for the TSN clock. According to one or more embodiments of this aspect, multiple methods include at least one of the following: a first method that includes determining the propagation delay in the access network using a conventional TA process; a second method that includes determining the propagation delay in the access network using a round-trip time RTT process, wherein the RTT process has a higher synchronization accuracy than the conventional TA process; and a third method that does not include determining the propagation delay in the access network. The determined propagation delay is configured for access network clock compensation. According to one or more embodiments of this aspect, multiple methods include at least one of the following: a first method that is configured to broadcast the access network clock information to the wireless device using a system information block SIB broadcast; and a second method that is configured to distribute the access network clock information to the wireless device using a radio resource control RRC unicast.

[0052] According to another aspect of the present disclosure, a method implemented by a wireless device is provided. The wireless device is configured to communicate with a network node and a terminal station in a time-sensitive network (TSN) via an access network. Receive access network clock information and downlink propagation delay information via one of a plurality of methods that meet the synchronization accuracy level required by the wireless device for the TSN clock in the access network, wherein each of the plurality of methods is associated with a different synchronization accuracy level for the access network clock. Cause the TSN clock information to be transmitted to the terminal station in the TSN.

[0053] According to one or more embodiments of this aspect, determine the propagation delay based at least on the downlink propagation delay. Update the access network clock based on the determined propagation delay. Perform an add egress timestamp on the TSN clock information received from the network node, wherein the add egress timestamp is performed using the updated access network clock. Determine that the TSN clock information needs to be adjusted based at least on the add egress timestamp. Compensate the TSN clock information based on the determined adjustment. According to one or more embodiments of this aspect, determine the propagation delay based at least on the downlink propagation delay. Update the access network clock based on the determined propagation delay. Perform an add ingress timestamp on the TSN clock information received from the terminal station in the TSN, wherein the add ingress timestamp is performed using the updated access network clock, and wherein the add ingress timestamp is configured to determine an adjustment to the TSN clock information.

[0054] According to one or more embodiments of this aspect, relay the TSN clock information through the access network using at least one QoS flow. According to one or more embodiments of this aspect, the at least one QoS flow includes a first QoS flow and a second QoS flow. Relay the TSN clock information through the access network using the first QoS flow associated with the first protocol data unit (PDU) session from the wireless device and the second QoS flow associated with the second PDU session from another wireless device connected to the terminal station that requires the TSN clock. According to one or more embodiments of this aspect, the at least one QoS flow is configured to indicate multiple accuracy levels for the TSN clock.

[0055] According to one or more embodiments of this aspect, TSN clock information is received in the user plane of the access network. According to one or more embodiments of this aspect, the synchronization accuracy level for the access network clock corresponds to the end-to-end synchronization accuracy required by the TSN clock. According to one or more embodiments of this aspect, the various methods include at least one of the following: a first method, which includes determining the propagation delay in the access network using a conventional TA process; a second method, which includes determining the propagation delay in the access network using a round-trip time (RTT) process, where the RTT process has a higher synchronization accuracy than the conventional TA process; and a third method, which does not include determining the propagation delay in the access network. The determined propagation delay is configured for access network clock compensation. According to one or more embodiments of this aspect, the various methods include at least one of the following: a first method, which is configured to broadcast access network clock information to a wireless device using a system information block (SIB) broadcast; and a second method, which is configured to distribute access network clock information to a wireless device using a radio resource control (RRC) unicast. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] A more complete understanding of the present embodiments and their attendant advantages and features will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which:

[0057] Figure 1 is a block diagram showing ingress and egress timestamps for a TSN GM clock;

[0058] Figure 2 is a schematic diagram showing an example network architecture of a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure;

[0059] Figure 3 is a block diagram of a host computer communicating with a wireless device via a network node via at least a partial wireless connection according to some embodiments of the present disclosure;

[0060] Figure 4 is a flowchart of an example method for executing a client application at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0061] Figure 5 is a flowchart of an example method for receiving user data at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0062] Figure 6Flowchart of an example method for receiving user data from a wireless device at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0063] Figure 7 Flowchart of an example method for receiving user data at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0064] Figure 8 Flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0065] Figure 9 Flowchart of another example process in a network node according to some embodiments of the present disclosure;

[0066] Figure 10 Flowchart of an example process in a core network node according to some embodiments of the present disclosure;

[0067] Figure 11 Flowchart in a network node according to the principles set forth herein;

[0068] Figure 12 Flowchart in a wireless device according to the principles set forth herein;

[0069] Figure 13 Flowchart of an example process in a wireless device according to the principles set forth herein;

[0070] Figure 14 Diagram of an example of adding ingress and egress timestamps to a TSN GM clock according to the principles set forth herein; and

[0071] Figure 15 Diagram of a 5G QoS flow within a packet data unit (PDU) session. Detailed Description

[0072] Before describing the exemplary embodiments in detail, it should be noted that the embodiments mainly reside in combinations of apparatus components and processing steps related to supporting uncertainty attributes specific to quality of service (QoS) flows. Accordingly, components have been represented in the drawings by conventional symbols where appropriate, which show only those specific details relevant to understanding the embodiments so as not to obscure the present disclosure with details that will be apparent to those of ordinary skill in the art having the benefit of the description herein. Like reference numerals refer to like elements throughout the specification.

[0073] As used herein, relational terms such as "first" and "second", "top" and "bottom", etc. may be used solely to distinguish one entity or element from another entity or element, and do not necessarily require or imply any physical or logical relationship or order between such entities or elements. The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the concepts described herein. As used herein, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are intended to include the plural forms as well. It will also be understood that when used herein, the terms "comprises", "comprising", "includes", and / or "including" specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0074] In the embodiments described herein, connection terms such as "communicate with" may be used to indicate electrical or data communication, which may be accomplished, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those of ordinary skill in the art will understand that multiple components may interoperate, and modifications and variations can be made to achieve electrical and data communication.

[0075] In some embodiments described herein, the terms "coupled", "connected", etc. may be used herein to indicate a connection, but not necessarily directly, and may include wired and / or wireless connections.

[0076] The term "network node" as used herein may be any type of network node included in a radio network, which may further include any one of the following: base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g-node B (gNB), evolved node B (eNB or eNodeB), node B, multi-standard radio (MSR) radio node (such as MSR BS), multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling the relay, radio access point (AP), transmission point, transmission node, remote radio unit (RRU), remote radio head (RRH), core network node (e.g., mobility management entity (MME), self-organizing network (SON) node, coordination node, positioning node, MDT node, etc.), external node (e.g., third-party node, node outside the current network), node in a distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS), etc. A network node may also include test equipment. The term "radio node" as used herein may also be used to denote a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0077] In some embodiments, non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. WD herein can be any type of wireless device capable of communicating with a network node or another WD via a radio signal, such as a wireless device (WD). WD can also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine-type WD, or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a customer terminal device (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IOT) device, etc.

[0078] Moreover, in some embodiments, the general term "radio network node" is used. It can be any type of radio network node, including any of the following: base station, radio base station, base transceiver station, base station controller, network controller RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), relay node, access point, radio access point, remote radio unit (RRU) remote radio head (RRH).

[0079] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in the present disclosure, this should not be viewed as limiting the scope of the present disclosure to only the aforementioned systems. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from utilizing the ideas covered in the present disclosure.

[0080] Further note that the functions described herein as being performed by a wireless device or network node may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device, and in fact, may be distributed across multiple physical devices.

[0081] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will also be further understood that, unless explicitly defined herein, the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant art, and will not be interpreted in an idealized or overly formal sense.

[0082] This document discloses methods for enabling network nodes to determine when and / or how a WD should receive 5G system clock (e.g., access network clock) and / or TSN GM clock information. Advantages over other arrangements may include one or more of the following:

[0083] · WDs may not need to trigger radio interface signaling to provide an indication to the network node that they need 5G system clock information (i.e., save radio interface signaling capacity by avoiding unnecessary control plane signaling);

[0084] · Based on CN configuration information, it is expected to (a) identify which WDs need which TSN GM clocks, and (b) identify which one or more 5G QoS flows are dedicated to supporting the transmission of this information. The configuration of the dedicated 5G QoS flow for supporting TSN GM clock information can be enhanced to allow the network node to determine the accuracy level to be associated with any given TSN GM clock, and thus determine the appropriate method for sending 5G system clock information to any WD using that TSN GM clock;

[0085] · Thus, the 5G system internal signaling already required for 5G QoS flow configuration can also be used as a means to implicitly notify the network node about when a WD needs 5G system clock information; and /

[0086] or

[0087] · A WD can autonomously determine whether to perform ingress timestamping or egress timestamping based on whether it receives TSN GM clock information from a terminal station (in which case, perform ingress timestamping) or through a downlink 5G QoS flow (in some embodiments, in which case, perform egress timestamping).

[0088] Referring again to the drawings, where like elements are referred to by like reference numerals, in Figure 2FIG. 0 shows a schematic diagram of a communication system 10 according to an embodiment, such as a 3GPP type cellular network that can support standards such as LTE and / or NR (5G). The communication system includes an access network 12 (such as a radio access network) and a core network node 14. In some embodiments, the core network node 14 may be in the core network within the access network 12. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NB, eNB, gNB, or other types of wireless access points. Each network node 16a, 16b, 16c defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage areas 18). Each network node 16a, 16b, 16c can be connected to the core network node 14 through a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to be wirelessly connected to or called by the corresponding network node 16a. A second WD 22b in the coverage area 18b can be wirelessly connected to the corresponding network node 16b. Although a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to the case where one WD is in the coverage area or one WD is connected to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0089] Moreover, it is expected that the WD 22 can communicate with more than one network node 16 and more than one type of network node 16 simultaneously and / or be configured to communicate separately with more than one network node 16 and more than one type of network node 16. For example, the WD 22 can have a dual connection with a network node 16 that supports LTE and the same or different network nodes 16 that support NR. As an example, the WD22 can communicate with an eNB for LTE / E-UTRAN and a network node for NR / NG-RAN. Further, one or more WDs 22 can be configured to communicate with one or more time-sensitive networks 23a-23n (collectively referred to as time-sensitive networks 23 or TSN 23). Each TSN 23 can include or serve one or more terminal stations (not shown), where the communication between TSN 23s can be performed via the access network 12 as described herein. Although the TSN 23 is shown within the access network 12, the TSN 23 is a network that is logically separated from the access network 12.

[0090] The communication system 10 can connect to the host computer 24 on its own. The host computer 24 can be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 24 can be under the ownership or control of a service provider, or can be operated by or on behalf of a service provider. The connections 26, 28 between the communication system 10 and the host computer 24 can extend directly from the core network node 14 to the host computer 24, or can extend via an optional intermediate network 30. The intermediate network 30 can be one or a combination of one or more networks in a public, private, or managed network. The intermediate network 30 (if any) can be a backbone network or the Internet. In some embodiments, the intermediate network 30 can include two or more sub-networks (not shown).

[0091] Figure 2 The communication system as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. This connectivity can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to use the access network 1010, the core network node 14, any intermediate network, and possibly further infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of the routing of the uplink and downlink communications. For example, the network node 16 may not or need not be notified of the past routing of the incoming downlink communication with data originating from the host computer 24 that is to be forwarded (e.g., switched) to the connected WD 22a. Similarly, the network node 16 need not know the future routing of the outgoing uplink communication originating from the WD 22a towards the host computer 24.

[0092] In some embodiments, the core network node 14 may include a Time-Sensitive Communication Assistance Information (TSCAI) generator 15, which is configured to generate TSCAI with GM clock synchronization accuracy parameters. In some embodiments, the network node 16 is configured to include a determiner unit 32, which is configured to determine a method for sending 5G system clock information to the WD, which is at least partially based on the determined accuracy level required by the WD for a given TSN GM clock. In some embodiments, the WD 22 is configured to include a timestamp determiner 34, which is configured to determine whether to perform an ingress timestamp or an egress timestamp based on whether the WD receives the Time-Sensitive Network (TSN) master GM clock information from the terminal station (in this case, perform an ingress timestamp) or receives the TSN master GM clock information through a downlink 5G Quality of Service (QoS) flow (in this case, perform an egress timestamp).

[0093] Reference will now be made to Figure 3 an example implementation according to an embodiment of the WD 22, network node 16, and host computer 24 discussed in the foregoing paragraphs. In the communication system 10, the host computer 24 includes hardware (HW) 38, and the hardware 38 includes a communication interface 40 configured to establish and maintain a wired or wireless connection to interfaces of different communication devices of the communication system 10. The host computer 24 also includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. In particular, in addition to or instead of a processor (such as a central processing unit) and a memory, the processing circuit 42 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (Field Programmable Gate Array) and / or an ASIC (Application Specific Integrated Circuit) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to and / or read from) the memory 46, and the memory 46 may include any type of volatile and / or non-volatile memory, such as a cache and / or a buffer memory and / or a RAM (Random Access Memory) and / or a ROM (Read Only Memory) and / or an optical memory and / or an EPROM (Erasable Programmable Read Only Memory).

[0094] The processing circuit 42 may be configured to control any one of the methods and / or processes described herein and / or cause such methods and / or processes to be executed, for example, by the host computer 24. The processor 44 corresponds to one or more processors 44 for performing the functions of the host computer 24 described herein. The host computer 24 includes a memory 46 configured to store data, programming software code, and / or other information described herein. In some embodiments, the software 48 and / or the host application 50 may include instructions that, when executed by the processor 44 and / or the processing circuit 42, cause the processor 44 and / or the processing circuit 42 to perform the processes described herein with respect to the host computer 24. The instructions may be software associated with the host computer 24.

[0095] The software 48 may be executable by the processing circuit 42. The software 48 includes the host application 50. The host application 50 may be operable to provide services to a remote user (such as the WD 22 connected via the OTT connection 52 terminated at the WD 22 and the host computer 24). When providing services to the remote user, the host application 50 may provide user data transmitted using the OTT connection 52. "User data" may be data and information described herein as implementing the described functions. In one embodiment, the host computer 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control the network node 16 and / or the wireless device 22, send to and / or receive from the network node 16 and / or the wireless device 22.

[0096] The communication system 10 further includes a network node 16 provided in the communication system and including hardware 58 that enables the network node 16 to communicate with the host computer 24 and the WD 22. The hardware 58 may include a communication interface 60 for establishing and maintaining a wired or wireless connection for interfacing with different communication devices of the communication system 10, and a radio interface 62 for establishing and maintaining a wireless connection 64 at least with the WD 22 located in the coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate the connection 66 to the host computer 24. The connection 66 may be direct, or it may pass through the core network node 14 of the communication system 10 and / or one or more intermediate networks 30 external to the communication system 10.

[0097] In the illustrated embodiment, the hardware 58 of network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor (such as a central processing unit) and a memory, the processing circuitry 68 may include an integrated circuit for processing and / or control, e.g., one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application specific integrated circuit) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may include any type of volatile and / or non-volatile memory, e.g., cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read only memory) and / or optical memory and / or EPROM (erasable programmable read only memory).

[0098] Accordingly, network node 16 also has software 74, which is stored internally, e.g., in memory 72, or in an external memory (such as a database, a storage array, a network storage device, etc.) accessible by network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any one of the methods and / or processes described herein and / or to cause such methods and / or processes to be executed, e.g., by network node 16. The processor 70 corresponds to one or more processors 70 for performing the functions of network node 16 described herein. The memory 72 is configured to store data, programming software code, and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuitry 68, cause the processor 70 and / or the processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, the processing circuitry 68 of network node 16 may include a determiner unit 32 configured to determine a method for sending 5G system clock information to the WD, which is at least partially based on the determined accuracy level required for a given TSN GM clock.

[0099] The communication system 10 also includes the aforementioned WD 22. The WD 22 may have hardware 80 that may include a radio interface 82 configured to establish and maintain a wireless connection 64 with network node 16 of the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, e.g., one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0100] The hardware 80 of WD 22 further includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. In particular, in addition to or instead of a processor (such as a central processing unit) and a memory, the processing circuit 84 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application specific integrated circuit) suitable for executing instructions. The processor 86 may be configured to access (e.g., write to and / or read from) the memory 88, which may include any type of volatile and / or non-volatile memory, such as a cache and / or a buffer memory and / or a RAM (random access memory) and / or a ROM (read only memory) and / or an optical memory and / or an EPROM (erasable programmable read only memory).

[0101] Accordingly, WD 22 may further include software 90, which is stored in the memory 88, for example, at WD 22, or in an external memory (such as a database, a storage array, a network storage device, etc.) accessible by WD 22. The software 90 may be executable by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may be operable to provide services to a human or non-human user via WD 22 with the support of the host computer 24. In the host computer 24, the executed host application 50 may communicate with the executed client application 92 via an OTT connection 52 terminated at WD 22 and the host computer 24. When providing services to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transmit both the request data and the user data. The client application 92 may interact with the user to generate the user data it provides.

[0102] Processing circuit 84 may be configured to control any one of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by WD 22. Processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. WD 22 includes a memory 88 that is configured to store data, programming software code, and / or other information described herein. In some embodiments, software 90 and / or client application 92 may include instructions that, when executed by processor 86 and / or processing circuit 84, cause processor 86 and / or processing circuit 84 to perform the processes described herein with respect to WD 22. In some embodiments, processing circuit 84 is further configured to implement a timestamp determiner 34 that is configured to determine whether to perform an ingress timestamp or an egress timestamp based on whether the WD receives time-sensitive network TSN master GM clock information from a terminal station (in which case, perform an ingress timestamp) or receives time-sensitive network TSN master GM clock information via a downlink 5G quality of service QoS flow (in which case, perform an egress timestamp).

[0103] In some embodiments, the internal workings of network node 16, WD 22, and host computer 24 may be as Figure 3 shown, and independently, the surrounding network topology may be Figure 2 the network topology of.

[0104] In Figure 3 the OTT connection 52 has been abstractly drawn to illustrate the communication between host computer 24 and wireless device 22 via network node 16 without explicitly referring to any intermediate devices and the exact routing of messages via these devices. The network infrastructure may determine a route that may be configured to be hidden from WD 22 or the service provider operating host computer 24 or both. While the OTT connection 52 is active, the network infrastructure may further take decisions to dynamically change the route (e.g., based on network load balancing considerations or reconfiguration).

[0105] The wireless connection 64 between WD 22 and network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT services provided to WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last leg. More precisely, the teachings of some of these embodiments may improve data rate, latency, and / or power consumption, thereby providing benefits such as reduced user wait time, relaxed file size limitations, better responsiveness, and extended battery life.

[0106] In some embodiments, a measurement process may be provided for the purpose of monitoring data rate, latency, and other factors for improving one or more embodiments. There may also be optional network functions for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to changes in the measurement results. The measurement process and / or the network function for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22 or in both. In an embodiment, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement process by supplying values of the monitored quantities exemplified above or by supplying values of other physical quantities from which the software 48, 90 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 52 may include message format, retransmission settings, preferred routing, etc.; the reconfiguration need not affect the network node 16, and the reconfiguration may be unknown or imperceptible to the network node 16. Some such processes and functions may be known and practiced in the art. In certain embodiments, the measurement may involve proprietary WD signaling that facilitates the measurement of throughput, propagation time, latency, etc. of the host computer 24. In some embodiments, the measurement may be implemented because the software 48, 90 causes messages (in particular empty or "dummy" messages) to be sent using the OTT connection 52 while it monitors propagation time, error, etc.

[0107] Thus, in some embodiments, the host computer 24 includes: a processing circuit 42 configured to provide user data; and a communication interface 40 configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network further includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 is configured to and / or the processing circuit 68 of the network node 16 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the WD 22 and / or for preparing / terminating / maintaining / supporting / ending a reception of a transmission from the WD 22.

[0108] In some embodiments, the host computer 24 includes a processing circuit 42 and a communication interface 40 configured to receive user data sourced from a transmission from the WD 22 to the network node 16. In some embodiments, the WD 22 is configured to and / or includes a radio interface 82 and / or a processing circuit 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the network node 16 and / or for preparing / terminating / maintaining / supporting / ending a reception of a transmission from the network node 16.

[0109] Figure 3Also shown is a core network node 14 having a communication interface 94 configured to communicate with one or more network nodes 16 via wired and / or wireless communication. The core network node 14 further includes processing circuitry 96 which may include a memory 98 and a processor 100. The processor 100 is configured to include a TSCAI generator 15 which is configured to generate a TSCAI with GM clock synchronization accuracy parameters.

[0110] Although Figure 2 and Figure 3 various “units” such as the TSCAI generator 15, the determiner unit 32, and the timestamp determiner 334 are shown within the respective processors, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0111] Figure 4 is a flowchart showing an example method implemented in a communication system (such as, for example, Figure 2 and Figure 3 the communication system). The communication system may include a host computer 24, a network node 16, and a WD 22 which may be the host computer 24, network node 16, and WD 22 described with reference to Figure 3 In a first step of the method, the host computer 24 provides user data (block S100). In an optional sub-step of the first step, the host computer 24 provides user data by executing a host application (such as, for example, the host application 50) (block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block S104). In an optional third step, according to the teachings of the embodiments described throughout this disclosure, the network node 16 sends the user data carried in the transmission initiated by the host computer 24 to the WD 22. In an optional fourth step, the WD 22 executes a client application, such as, for example, a client application 92 associated with the host application 50 executed by the host computer 24 (block S108).

[0112] Figure 5 is a flowchart showing an example method implemented in a communication system (such as, for example, Figure 2 the communication system). The communication system may include a host computer 24, a network node 16, and a WD 22 which may be the host computer 24, network node 16, and WD 22 described with reference to Figure 2 and Figure 3The described host computer 24, network node 16, and WD 22. In a first step of the method, the host computer 24 provides user data (block S110). In an optional sub-step (not shown), the host computer 24 provides user data by executing a host application (such as, for example, host application 50). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block S112). According to the teachings of the embodiments described throughout this disclosure, the transmission may be relayed via the network node 16. In an optional third step, the WD 22 receives the user data carried in the transmission (block S114).

[0113] Figure 6 is a flowchart showing an example method implemented in a communication system (such as, for example, Figure 2 the communication system). The communication system may include a host computer 24, a network node 16, and a WD 22, which may be the host computer 24, network node 16, and WD 22 described with reference to Figure 2 and Figure 3 In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (block S116). In an optional sub-step of the first step, the WD 22 executes a client application 92 that provides user data in response to the received input data provided by the host computer 24 (block S118). Additionally or alternatively, in an optional second step, the WD 22 provides user data (block S120). In an optional sub-step of the second step, the WD provides user data by executing a client application (such as, for example, client application 92) (block S122). When providing user data, the executed client application 92 may further consider user input received from the user. Regardless of the particular manner of providing user data, in an optional third sub-step, the WD 22 may initiate a transmission of the user data to the host computer 24 (block S124). In a fourth step of the method, according to the teachings of the embodiments described throughout this disclosure, the host computer 24 receives the user data sent from the WD 22 (block S126).

[0114] Figure 7 is a flowchart showing an example method implemented in a communication system (such as, for example, Figure 2 the communication system). The communication system may include a host computer 24, a network node 16, and a WD 22, which may be the host computer 24, network node 16, and WD 22 described with reference to Figure 2 and Figure 3The described host computer 24, network node 16, and WD 22. In an optional first step of the method, the network node 16 receives user data from the WD 22 (block S128) according to the teachings of the embodiments described throughout this disclosure. In an optional second step, the network node 16 initiates the transmission of the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).

[0115] Figure 8 is a flowchart of an example process in the network node 16 for conditionally sending propagation delay identification information (also referred to as propagation delay information) of a QoS flow suitable for supporting the delivery of TSN-GM clock information with specific accuracy requirements. One or more of the boxes described herein may be performed by one or more units of the network node 16, such as one or more of the processing circuitry 68 (including the determiner unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 is configured to receive time-sensitive communication assistance information TSCAI having a master GM clock synchronization accuracy parameter from the core network node 14, such as via the processing circuitry 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60 (block S134). The process further includes: determining, based on the accuracy parameter, when the network node 16 supports sending downlink propagation delay identification information using a method of a quality of service QoS flow suitable for supporting the delivery of time-sensitive network TSN GM clock information with specific accuracy requirements (block S136). When the network node 16 supports sending access network clock and downlink propagation delay identification information using a method of a specific accuracy requirement of a QoS flow suitable for supporting the delivery of TSN GM clock information, the process includes: sending the downlink propagation delay identification information to the WD and adjusting the access network clock to compensate for the identified downlink propagation delay (block S138).

[0116] In other words, the 5G clock at the wireless device 22 (i.e., the access network clock) needs to be compensated for the RF air propagation time between the network node 16 and the wireless device 22, because it is defined at the network node 16 antenna when distributed from the network node 16. When a TSN timing packet (i.e., TSN GM clock information) is sent through the access network, the 5GS clock at the wireless device 22 can be used to timestamp the dwell time (entry or exit).

[0117] Figure 9FIG. is a flowchart of another example process in network node 16 according to some embodiments of the present disclosure. One or more of the boxes described herein may be performed by one or more units of network node 16, such as one or more of processing circuitry 68 (including determiner unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 is configured to receive (block S140) at least one parameter from core network node 14, where the at least one parameter indicates the synchronization accuracy level required for the access network clock for the TSN clock of wireless device 22, as described herein. Network node 16 is configured to implement (block S142) one of a plurality of methods for distributing access network clock information and for determining downlink propagation delay information in access network 12 based on the synchronization accuracy level required by the wireless device for the TSN clock, where each of the plurality of methods is associated with a different synchronization accuracy level for the access network clock, as described herein.

[0118] According to one or more embodiments, the downlink propagation delay information is configured to allow updating of the access network clock associated with the access network clock information, where the updated access network clock is configured to allow timestamping of the TSN clock information for compensation of the TSN clock information. According to one or more embodiments, the at least one parameter is time-sensitive communication assistance information TSCAI, which has a primary GM clock synchronization accuracy parameter. According to one or more embodiments, the TSN clock information is relayed through access network 12 using at least one QoS flow for delivery to a terminal station in TSN 23 via wireless device 22.

[0119] According to one or more embodiments, the at least one QoS flow includes a first QoS flow and a second QoS flow, and wherein the TSN clock information is relayed through the access network using the first QoS flow associated with a first PDU session from wireless device 22 and the second QoS flow associated with a second PDU session from another wireless device 22 connected to a terminal station that requires the TSN clock. According to one or more embodiments, the at least one QoS flow is configured to indicate multiple accuracy levels for the TSN clock. According to one or more embodiments, the TSN clock information is distributed in the user plane of access network 12.

[0120] According to one or more embodiments, the synchronization accuracy level for accessing the network clock corresponds to the end-to-end synchronization accuracy required by the TSN clock. According to one or more embodiments, the various methods include at least one of the following: a first method that includes determining the propagation delay in the access network using a conventional TA process; a second method that includes determining the propagation delay in the access network 12 using a round-trip time (RTT) process, where the RTT process has a higher synchronization accuracy than the conventional TA process; and a third method that does not include determining the propagation delay in the access network 12. The determined propagation delay is configured for access network clock compensation. According to one or more embodiments, the various methods include at least one of the following: a first method that is configured to broadcast access network clock information to the wireless device 22 using a system information block (SIB) broadcast; and a second method that is configured to distribute access network clock information to the wireless device 22 using a radio resource control (RRC) unicast.

[0121] Figure 10 FIG. 4 is a flowchart of an example process in the core network node 14 according to some embodiments of the present disclosure for generating a TSCAI having a GM clock synchronization accuracy parameter indicating an allowable error in distributing / delivering the TSN GM clock to the TSN terminal station. One or more of the blocks described herein may be performed by one or more units of the core network node 14, such as one or more of the processing circuitry 96 (including the TSCAI generator 15), the processor 100, and / or the communication interface 94. The core network node 14 is configured to generate time-sensitive communication assistance information (TSCAI) having a master GM clock synchronization accuracy parameter via, for example, the processing circuitry 96 and / or the processor 100 and / or the communication interface 94, the GM clock synchronization accuracy parameter indicating when a quality of service (QoS) flow supports the delivery of time-sensitive network (TSN) GM clock information with a specific accuracy requirement (block S144). The process further includes sending the TSCAI to at least one of one or more network nodes 16 (block S146).

[0122] Figure 11It is a flowchart of an example process in network node 16 according to the principles set forth herein. One or more of the boxes described herein may be performed by one or more elements of network node 16, such as one or more of processing circuitry 68 (including determiner unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 is configured, such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60, to determine an uncertainty level of an access network clock for use at WD 22 to perform one of ingress timestamping and egress timestamping of a TSN timing packet (i.e., TSN clock information) (block S148). The method further includes determining a method for sending the access network clock information to WD 22, the determination being at least partially based on the determined uncertainty level for the access network clock (block S150). In other words, delivering the TSN GM clock within a particular accuracy requires WD 22 to have a particular accuracy of the access network clock. In one or more embodiments, the sending of the access network clock information may include any of broadcast and unicast for distributing the information, wherein the determined method may be associated with a particular process for determining propagation delay.

[0123] Figure 12 It is a flowchart of an example process in wireless device 22 according to some embodiments of the present disclosure. One or more of the boxes described herein may be performed by one or more elements of wireless device 22, such as one or more of processing circuitry (including TSCAI generator 15), processor 86, radio interface 82, and / or communication interface 60. Wireless device 22 is configured, such as via processing circuitry 84 and / or processor 86 and / or radio interface 82, to determine whether to perform ingress timestamping or egress timestamping (block S152) based on whether the WD is receiving time-sensitive network TSN master GM clock information from a terminal station (in which case, perform ingress timestamping) or receiving time-sensitive network TSN master GM clock information via a downlink 5G quality of service QoS flow (in which case, perform egress timestamping).

[0124] Figure 13FIG. is a flowchart of another example process in wireless device 22 according to some embodiments of the present disclosure. One or more of the boxes described herein may be performed by one or more elements of wireless device 22, such as one or more of processing circuitry (including TSCAI generator 15), processor 86, radio interface 82, and / or communication interface 60. Wireless device 22 is configured to receive (block S154) access network clock information and downlink propagation delay information via one of a plurality of methods that meet the synchronization accuracy level required for the TSN clock in TSN 23 for access network 12, wherein each of the plurality of methods is associated with a different synchronization accuracy level for the access network clock, as described herein. Wireless device 22 is configured to cause (block S156) the TSN clock information to be transmitted to the end stations in TSN 23, as described herein.

[0125] According to one or more embodiments, the processing circuitry 84 is configured to: determine the propagation delay based at least on the downlink propagation delay; update the access network clock based on the determined propagation delay; perform add egress timestamp on the TSN clock information received from the network node, wherein the add egress timestamp is performed using the updated access network clock; determine that the TSN clock information needs to be adjusted based at least on the add egress timestamp; and compensate the TSN clock information based on the determined adjustment. According to one or more embodiments, the processing circuitry 84 is configured to: determine the propagation delay based at least on the downlink propagation delay, update the access network clock based on the determined propagation delay, and perform add ingress timestamp on the TSN clock information received from the end stations in the TSN, wherein the add ingress timestamp is performed using the updated access network clock, and the add ingress timestamp is configured to adjust the TSN clock information.

[0126] According to one or more embodiments, the TSN clock information is relayed through the access network 12 using at least one QoS flow. According to one or more embodiments, the at least one QoS flow includes a first QoS flow and a second QoS flow. The TSN clock information is relayed through the access network 12 using the first QoS flow associated with the first protocol data unit PDU session from the wireless device 22 and the second QoS flow associated with the second PDU session from another wireless device 22 connected to the end station that requires the TSN clock. According to one or more embodiments, the at least one QoS flow is configured to indicate multiple accuracy levels for the TSN clock.

[0127] According to one or more embodiments, TSN clock information is received in the user plane of access network 12. According to one or more embodiments, the synchronization accuracy level for the access network clock corresponds to the end-to-end synchronization accuracy required for the TSN clock. According to one or more embodiments, the various methods include at least one of the following: a first method that includes determining the propagation delay in access network 12 using a conventional TA process; a second method that includes determining the propagation delay in access network 12 using a round-trip time (RTT) process, where the RTT process has a higher synchronization accuracy than the conventional TA process; and a third method that does not include determining the propagation delay in access network 12. The determined propagation delay is configured for access network clock compensation. According to one or more embodiments, the various methods include at least one of the following: a first method that is configured to broadcast access network clock information to wireless device 22 using a system information block (SIB) broadcast; and a second method that is configured to distribute access network clock information to wireless device 22 using a radio resource control (RRC) unicast.

[0128] The general processing flow of the arrangements of the present disclosure has been described and examples of the hardware and software arrangements for implementing the processes and functions of the present disclosure have been provided. The following sections provide details and examples of arrangements for supporting service quality (QoS) flow-specific uncertainty attributes.

[0129] One or more of the functions of network node 16 described below can be performed by one or more of processing circuitry 68, processor 70, determiner unit 32, radio interface 62 (e.g., air interface), communication interface 60, etc. One or more of the functions of wireless device 22 described below can be performed by one or more of processing circuitry 84, processor 86, radio interface 82, timestamp determiner 34, etc. One or more of the functions of core network node 14 described below can be performed by one or more of processing circuitry 96, processor 100, TSCAI generator 15, communication interface 94, etc.

[0130] In one configuration, the TSN GM clock is located in the end station of the TSN, where the TSN GM clock information can be relayed to one or more end stations connected to one or more WDs 22 in the 5G system using a user plane function (UPF) / network TSN converter (NW-TT).

[0131] In this case, the 5G QoS flow includes a data radio bearer (DRB) on the radio interface and a General Packet Radio Service (GPRS) Tunneling Protocol - User (GTP-U) tunnel on the network node 16 to the user plane function (UPF) interface. In some embodiments, at least one specific 5G QoS flow will be configured to support the TSN GM clock for the delivery of user plane payloads sent through the 5G system.

[0132] When the TSN GM clock is received by the 5G system (e.g., at the UPF / NW-TT), an ingress timestamp is performed, and when the same TSN GM clock has been relayed (through the 5G system) to the WD 22, an egress timestamp is performed.

[0133] In another configuration, the TSN GM clock is located in the terminal station of the WD 22 connected to the 5G system, which means that the TSN GM clock information is relayed to other terminal stations connected to one or more WD 22s that are part of the same 5G system.

[0134] Figure 14 It is a schematic diagram of adding ingress and egress timestamps to the TSN GM clock.

[0135] · In Figure 14 In the case shown, there are two 5G QoS flows for the delivery of the TSN GM clock through the 5G system, where the first 5G QoS flow is implemented using a PDU session from the first WD

[0136] (which is connected to the terminal station where the TSN GM clock is located) to the user plane function (UPF), and the second 5G QoS flow is implemented using a PDU session from the second WD (which is connected to the terminal station that requires the TSN GM clock) to the UPF.

[0137] · Therefore, for this case, the total 5G system path for delivering the TSN GM clock can consist of two different PDU sessions, where each PDU session includes a data radio bearer (i.e., one for each WD-gNB interface, where one is an UL data radio bearer (DRB) and one is a DL DRB) and a GTP-U tunnel (i.e., one for each gNB-UPF interface).

[0138] · Two different GTP-U tunnels can be associated with this case, regardless of whether the first WD and the second WD are connected to the same network node, as Figure 14As shown. In one or more embodiments, the path for TSN GM clock delivery involves two different network nodes (i.e., the inter-network-node option). Note that the TSN GM clock delivery path may also involve a single network node (i.e., the intra-network-node option); and / or

[0139] · When receiving the TSN GM clock by the 5G system (e.g., at the first WD 22 / DS-TT), perform ingress timestamp addition, and when the same TSN GM clock has been relayed (by the 5G system) to the second WD 22, perform egress timestamp addition;

[0140] Regardless of the configuration, i.e., regardless of where the TSN GM clock is located, the amount of uncertainty introduced when the TSN GM clock is relayed by the 5G system will be affected by the accuracy of the 5G system clock used to perform timestamp addition at the ingress and egress points.

[0141] · When a set of terminal stations connected to one or more WD 22s (reachable via the 5G system) requires the TSN GM clock, an end-to-end synchronization (uncertainty) requirement for the TSN GM clock can be assumed (e.g., known at the centralized network controller (CNC)) and a TSN network-based determination of the associated 5GS budget.

[0142] · This end-to-end uncertainty requirement can be relayed to the 5G system and made available to network node 16 such that network node 16 can deliver the 5G system clock to the ingress and egress points at an uncertainty level suitable for supporting the end-to-end uncertainty requirement of the corresponding TSN GM clock.

[0143] · For example, each TSN GM clock may also have an attribute indicating whether it is located at a terminal station reachable via the WD of the 5G system (e.g., known at the CNC). When the end-to-end uncertainty requirement is relayed to the 5G system, this attribute can be considered (i.e., if the TSN GM clock is located at a terminal station reachable via the WD, the end-to-end uncertainty requirement identified by the TSN network and relayed to the 5G system will be more demanding).

[0144] · If the TSN GM is located at a terminal station reachable via the WD of the 5G system, the WD manages the further distribution of the TSN GM clock in the uplink and thus must receive a more accurate 5G system clock for performing ingress timestamp addition (to the TSN GM clock information it receives from the terminal station).

[0145] Whether WD uses the 5G system clock for ingress or egress timestamps is determined based on whether it receives TSN GM clock information via a downlink 5G QoS flow (in which case it performs egress timestamping) or receives TSN GM clock information from the terminal station for transmission via an uplink 5G QoS flow (in which case it performs ingress timestamping).

[0146] Method 1 – New Time-Sensitive Communication (TSC) Assistance Information

[0147] The TSN GM clock information (regarded as user plane traffic) expected to be delivered to WD 22 is expected to be received periodically by the 5G system and has prior-known traffic characteristics, allowing the establishment of a corresponding QoS flow to support this traffic. For example, Time-Sensitive Communication (TSC) Assistance Information (TSCAI) as defined in Table 5.27.2-1 of 3GPP Technical Standard (TS) 23.501 is provided from the Service Management Function (SMF) to network node 16 (e.g., at QoS flow establishment). The TSCAI parameters can be set according to the QoS flow-specific traffic parameters obtained from the Application Function (AF). Thus, the TSCAI parameters allow network node 16 to schedule data radio bearer (DRB) resources suitable for the transmission of TSN-GM clock information supported by a given QoS flow.

[0148] In some embodiments, the method requires the introduction of a new "GM Clock Synchronization Accuracy" parameter (optionally included) as part of the 5GS QoS flow-specific information provided to network node 16 as part of the TSCAI, allowing network node 16 to determine when a given QoS flow supports the delivery of TSN GM clock information with specific synchronization accuracy (uncertainty) requirements. This then allows network node 16 to determine which radio interface signaling method (e.g., the traditional TA procedure) network node 16 should use to provide the corresponding WD 22 with information that allows it to identify the downlink PD. This method is applicable regardless of where the TSN GM clock is located, as the method assumes that the source node providing the TSCAI knows whether any given TSN-GM clock supported by a given 5G QoS flow is located at a terminal station reachable via WD 22. In other words, if the terminal station is reachable via WD 22, the new parameter will indicate a higher value for the clock synchronization accuracy requirement, as two radio interfaces will be involved in delivering the TSN GM clock from the source terminal station to the target terminal station. Thus, this parameter allows network node 16 to determine the best method for distributing 5G system clock information via the air interface to a specific WD 22 configured with such a 5G QoS flow (e.g., a PD determined using a round-trip time (RTT)-based method may be suitable for certain TSN GM clock synchronization accuracy requirements).

[0149] It is useful to identify the downlink PD applicable to the WD at an appropriate level of accuracy, as it may be necessary to compensate the 5G system clock sent to the WD 22 to reflect the downlink PD, thereby improving the accuracy (reducing the uncertainty) of measuring the 5G dwell time. That is, when sending the TSN GM clock to the WD 22 via the 5G system, the TSN GM clock should be adjusted to reflect the 5G dwell time measured using timestamping based on the 5G system clock. Examples of possible values for this new TSCAI parameter are as follows:

[0150] · Clock synchronization accuracy 1: Relax the radio interface uncertainty requirement (e.g., ≥5 μs), so that 5G information does not need to be compensated to reflect the downlink PD. In this case, the broadcast method of distributing 5G system clock information may be sufficient;

[0151] · Clock synchronization accuracy 2: 500 ns ≤ radio interface uncertainty requirement < 5 μs. Therefore, the network node 16 can determine (a) that PD compensation is not required due to a small cell radius (e.g., radius < 30 m), or (b) that pre-compensation can be used for a specific range of cell radii (e.g., 30 m ≤ radius ≤ 300 m), or (c) that the traditional RTT method is suitable (e.g., cell radius > 300 m). For (c), the broadcast method may also be sufficient to distribute 5G system clock information;

[0152] · Clock synchronization accuracy 3: 200 ns ≤ radio interface uncertainty requirement < 500 ns. Therefore, the network node 16 can determine (a) that PD compensation is not required due to a small cell radius (e.g., radius < 30 m), or (b) that pre-compensation can be used for a specific range of cell radii (e.g., 30 m ≤ radius ≤ 60 m), or (c) that an enhanced RTT method is required (e.g., cell radius > 60 m). For (c), an enhanced radio resource control (RRC) unicast-based method can be used to distribute 5G system clock information; and

[0153] · Clock synchronization accuracy 4: Radio interface uncertainty requirement < 200 ns. Therefore, the network node 16 can determine (a) that PD compensation is not required due to a small cell radius (e.g., radius < 30 m), or (b) that pre-compensation can be used for a specific range of cell radii (e.g., 30 m ≤ radius ≤ 60 m), or (c) that an advanced RTT method is required (e.g., cell radius > 60 m). For (c), an advanced RRC unicast-based method may be required to distribute 5G system clock information.

[0154] Method 2 - 5G QoS Indicator (5QI) Table Entry Attributes

[0155] This method provides a new "uncertainty" parameter for the 5G QoS Indicator (5QI) table currently used to identify QoS flow specific characteristics (see example Table 1 below). This parameter (optionally included) allows a network node 16 accessing the 5G QoS Indicator (5QI) table parameters to determine when a given QoS flow supports the delivery of TSN GM clock information with specific synchronization accuracy (uncertainty) requirements. Using this information, the network node 16 can determine the best method (e.g., traditional TA procedure, broadcast, or optimized RRC unicast procedure) for distributing 5G system clock information to a specific WD over the air interface. The network node 16 can be used to provide the information required to identify the downlink PD applicable to the WD 22 configured to use such a QoS flow. Identifying the downlink PD is useful because the 5G system clock sent to the WD 22 may need to be compensated to reflect the downlink PD to improve the accuracy of measuring the 5G dwell time (reduce uncertainty). For example, when sending a TSN GM clock to the WD 22 via the 5G system, the TSN GM clock should be adjusted to reflect the 5G dwell time measured using the timestamp based on the 5G system clock.

[0156] · One option is to allow a set of 5G QoS flows to be used to support the delivery of TSN GM clock information, where each 5G QoS flow is associated with a different 5QI table entry / index. This means that TSN GM clocks with different uncertainty requirements can be treated as separate TSN flow categories, such that each category maps to a different QoS flow and thus to a different 5QI table index / entry. Conversely, all TSN GM clocks with the same uncertainty requirements needed by a given WD can be supported using a common 5G QoS flow (i.e., they can be mapped to the same 5QI table entry / index - see Example 1 in Table 1 below);

[0157] · A variant of this option is to allow TSN GM clocks to be grouped according to the maximum uncertainty tolerable by all TSN GM clocks in the group. This means that TSN GM clocks with different values for their maximum allowed uncertainty can be treated as separate TSN flow categories, such that each category maps to a different 5QI table index / entry (see Example 2 in Table 1 below).

[0158] Table 1

[0159]

[0160]

[0161]

[0162] Method 3 - Multiple GTP-U Tunnels

[0163] The method introduces a new "uncertainty" attribute associated with each GTP-U tunnel used within the context of a single packet data unit (PDU) session (i.e., the PDU session is configured to include multiple GPRS tunneling protocol - user (GTP-U) tunnels). This allows a network node 16 configured with multiple GTP-U tunnels within the context of a PDU session to use this new attribute to determine the most suitable radio interface signaling method (e.g., the traditional TA procedure) that the network node 16 should use to provide the downlink PD information for adjusting the 5G system clock to the corresponding WD 22, which allows the WD 22 to identify the downlink PD. The method can be applicable to the case where a set of GTP-U tunnels is used to send TSN GM clock information to a terminal station reachable through a given WD 22. Each GTP-U tunnel in the set of GTP-U tunnels has a corresponding "uncertainty" requirement for the TSN GM clock information carried by that GTP-U tunnel. A common DRB to the WD through the radio interface can support all GTP-U tunnels. In other words, the network node 16 knows through which GTP-U tunnel it has received the TSN GM clock information and thus knows the corresponding "uncertainty" requirement so that it can thereby determine a suitable method for delivering the 5G system clock information to the WD 22.

[0164] Identifying the downlink PD can be useful because the 5G system clock sent to the WD 22 may need to be compensated to reflect the downlink PD in order to improve the accuracy (uncertainty) of measuring the 5G dwell time (i.e., when sending the TSN-GM clock to the WD22 through the 5G system, the TSN-GM clock distributed through the 5G system needs to be adjusted to reflect the 5G dwell time measured using the plus timestamp (i.e., using ingress and egress timestamps) based on the 5G system clock (i.e., the updated 5G system clock)).

[0165] · Figure 15 An example of the current situation is shown where the PDU session is configured to use a single GTP-U tunnel while still allowing multiple 5G QoS flows;

[0166] · However, for this method, a set of multiple different GTP-U tunnels can be dedicated to sending the TSN GM clock information. Each GTP-U tunnel in the set can be used within the context of a single PDU session, where the same or different DRBs can be used for each member of the set of GTP-U tunnels;

[0167] · The new "uncertainty" attribute can be implicitly indicated based on the Tunnel Endpoint Identifier (TEID) value (i.e., different TEIDs can be reserved for indicating different uncertainty requirements). Therefore, all TSN GM clocks with the same uncertainty requirement can be supported using a common GTP-U tunnel.

[0168] · For example, 4 different TEID values can be assigned to support the delivery of TSN GM clock information as follows:

[0169] i) TEID1: The radio interface uncertainty requirement is large (e.g., ≥5 μs), so the 5G reference time does not need to be compensated to reflect the downlink PD;

[0170] ii) TEID2: 500 ns ≤ radio interface uncertainty requirement < 5 μs, so the network node 16 can determine (a) that no PD compensation is required due to a small cell radius (e.g., radius < 30 m), or (b) pre-compensation can be used for a specific range of cell radii (e.g., 30 m ≤ radius ≤ 300 m), or (c) the traditional RTT method is suitable (e.g., cell radius > 300 m);

[0171] iii) TEID3: 200 ns ≤ radio interface uncertainty requirement < 500 ns, so the network node 16 can determine (a) that no PD compensation is required due to a small cell radius (e.g., radius < 30 m), or (b) pre-compensation can be used for a specific range of cell radii (e.g., 30 m ≤ radius ≤ 60 m), or (c) an enhanced RTT method is required (e.g., cell radius > 60 m); and

[0172] iv) TEID4: Radio interface uncertainty requirement < 200 ns, so the network node 16 can determine (a) that no PD compensation is required due to a small cell radius (e.g., radius < 30 m), or (b) pre-compensation can be used for a specific range of cell radii (e.g., 30 m ≤ radius ≤ 60 m), or (c) an advanced RTT method is required (e.g., cell radius > 60 m).

[0173] According to one aspect, a network node 16 is provided that is configured to communicate with a wireless device WD 22. The network node 16 includes a radio interface 62 and / or processing circuitry 68, which are configured to receive time-sensitive communication assistance information TSCAI having a master GM clock synchronization accuracy parameter from a core node; determine, at least in part based on the accuracy parameter, when a quality of service QoS flow supports the delivery of time-sensitive network TSN GM clock information with a specific accuracy requirement; and when the QoS flow supports the delivery of TSN GM clock information with a specific accuracy requirement, send identification information to the WD 22 such that the WD 22 can identify the downlink propagation delay between the network node 16 and the WD 22 and adjust the 5GS clock for the RF propagation delay between the network node 16 and the wireless device 22 (i.e., update the access network clock).

[0174] According to this aspect, in some embodiments, the GM clock synchronization is at least in part based on radio interface uncertainty requirements. In some embodiments, the network node 16 and / or the processing circuitry 68 are further configured to determine one of the following: that no propagation delay is required due to cell size; that pre-compensation of the transmitted identification information can be used for a specific range of cell sizes; and that a round-trip time method can be used for cell sizes above a threshold. In some embodiments, the network node 16 and / or the radio interface 62 and / or the processing circuitry 68 are further configured to associate an uncertainty attribute with each of a plurality of GTP-U tunnels, the uncertainty attribute being used by the network node 16 to determine which of a plurality of radio interface signaling methods to use to send the identification information.

[0175] According to another aspect, a method implemented in the network node 16 includes: receiving time-sensitive communication assistance information TSCAI having a master GM clock synchronization accuracy parameter via a communication interface 60 or via an interface to a core network node 14. The method further includes: determining, via the processing circuitry 68, at least in part based on the accuracy parameter, when a quality of service QoS flow supports the delivery of time-sensitive network TSN GM clock information with a specific accuracy requirement. When the network node 16 supports sending downlink propagation delay identification information using a method that is suitable for supporting the delivery of TSN GM clock information with a specific accuracy requirement with a QoS flow, the method further includes: sending identification information to the WD 22 via the radio interface 62 such that the WD 22 can identify the downlink propagation delay between the network node 16 and the WD 22 and adjust the access network clock to compensate for the downlink propagation delay. In one or more embodiments, the network node 16 can determine which PD method to implement.

[0176] According to this aspect, in some embodiments, the GM clock synchronization is at least partially based on radio interface uncertainty requirements. In some embodiments, the method further includes: determining, via processing circuitry 68, one of the following: that the downlink propagation delay is not required due to the cell size; that pre-compensation of the transmitted identification information can be used for a specific range of cell sizes; and that the round-trip time RTT method can be used for cell sizes above a threshold. In some embodiments, the method further includes: associating, via processing circuitry 68, an uncertainty attribute with each GTP-U tunnel among a plurality of GTP-U tunnels, the uncertainty attribute being used by network node 16 to determine which one of a plurality of radio interface signaling methods to use to transmit the identification information.

[0177] According to another aspect, there is provided a core network node 14 configured to communicate with one or more network nodes 16 that communicate with one or more WD 22s. The core network node 14 includes a communication interface 94 and / or processing circuitry 96 configured to generate time-sensitive communication assistance information TSCAI having a primary GM clock synchronization accuracy parameter that indicates when a quality of service QoS flow supports the delivery of time-sensitive network TSN GM clock information with a specific accuracy requirement. The communication interface is further configured to transmit the TSCAI to at least one of the one or more network nodes 16 via the communication interface 94.

[0178] According to yet another aspect, a method implemented in a core network node 14 that communicates with one or more network nodes 16 includes: generating, via a TSCAI generator 15, TSCAI having a primary GM clock synchronization accuracy parameter that indicates when a quality of service QoS flow supports the delivery of time-sensitive network TSN GM clock information with a specific accuracy requirement. The method further includes: transmitting the TSCAI to at least one of the one or more network nodes 16 via the communication interface 94.

[0179] According to one aspect, a network node 16 configured to communicate with a wireless device WD 22 is configured to perform the following and / or includes a radio interface 62 and / or processing circuitry 68 configured to perform the following: determining an accuracy level for the WD 22 to support a time-sensitive network TSN primary GM clock; and determining a method for transmitting system clock information to the WD 22, the determination being at least partially based on the determined accuracy level.

[0180] According to this aspect, in some embodiments, the network node 16 / radio interface 62 / processing circuitry 68 is further configured to send system clock information via two streams, where the first stream of the two streams is implemented using a first packet data unit PDU session from the first WD 22, and the second stream of the two streams is implemented using a second PDU session from the second WD 22. In some embodiments, each of the first and second PDU sessions includes a data radio bearer. In some embodiments, the first and second GTP-U tunnels are associated with the first and second PDU sessions, respectively.

[0181] According to another aspect, a method implemented in the network node 16 includes: determining an accuracy level for the WD 22 to support a time-sensitive network TSN master GM clock; and determining a method for sending system clock information to the WD 22, where the determination is at least partially based on the determined accuracy level.

[0182] According to this aspect, in some embodiments, the network node 16 / radio interface / processing circuitry is further configured to send system clock information via two streams, where the first stream of the two streams is implemented using a first packet data unit PDU session from the first WD 22, and the second stream of the two streams is implemented using a second PDU session from the second WD 22. In some embodiments, each of the first and second PDU sessions includes a data radio bearer. In some embodiments, the first and second GTP-U tunnels are associated with the first and second PDU sessions, respectively.

[0183] According to yet another aspect, the WD 22 configured to communicate with the network node 16 is configured to perform the following and / or includes a radio interface 82 and / or processing circuitry 84 configured to perform the following: determining whether to perform ingress timestamping or egress timestamping based on whether the WD 22 receives time-sensitive network TSN master GM clock information from a terminal station (in which case, perform ingress timestamping) or receives time-sensitive network TSN master GM clock information via a downlink 5G quality of service QoS flow (in which case, perform egress timestamping).

[0184] According to this aspect, the WD 22 / radio interface 82 / processing circuitry 84 is further configured to: receive TSN GM clock information via at least one GTP-U tunnel, where each of the at least one GTP-U tunnels has a corresponding uncertainty requirement for the TSN-GM clock information carried by the at least one GTP-U.

[0185] According to another aspect, a method implemented in a WD 22 communicating with a network node 16 includes determining whether to perform ingress timestamping or egress timestamping based on whether the WD 22 receives time-sensitive network TSN master GM clock information from a terminal station (in which case, ingress timestamping is performed) or receives time-sensitive network TSN master GM clock information via a downlink 5G quality of service QoS flow (in which case, egress timestamping is performed).

[0186] According to this aspect, in some embodiments, the method further includes receiving TSN GM clock information via at least one GTP-U tunnel, each of the at least one GTP-U tunnels having a corresponding uncertainty requirement for the TSN-GM clock information carried by the at least one GTP-U, the uncertainty requirement to be used by the network node 16 to select a method for delivering 5G system clock information to the WD 22.

[0187] Some examples

[0188] Example A1. A network node (16) configured to communicate with a wireless device (22) WD (22), the network node (16) being configured to perform the following and / or including a radio interface (62) and / or including a processing circuit (68) configured to perform the following:

[0189] Determine an accuracy level for the WD (22) to support a time-sensitive network TSN (23) master GM clock; and

[0190] Determine a method for sending system clock information to the WD (22), the determination being at least partially based on the determined accuracy level.

[0191] Example A2. The network node (16) according to Example A1, wherein the network node (16) / radio interface (62) / processing circuit (68) is further configured to send the system clock information via two streams, a first stream of the two streams being implemented using a first packet data unit PDU session from a first WD (22), and a second stream of the two streams being implemented using a second PDU session from a second WD (22).

[0192] Example A3. The network node (16) according to Example A2, wherein each of the first and second PDU sessions includes a data radio bearer.

[0193] Example A4. The network node (16) according to Example A3, wherein first and second GTP-U tunnels are respectively associated with the first and second PDU sessions.

[0194] Example B1. A method implemented in a network node (16), the method comprising:

[0195] Determine an accuracy level for the WD (22) to support the time-sensitive network TSN master GM clock; and

[0196] Determine a method for sending system clock information to the WD (22), the determination being at least partially based on the determined accuracy level.

[0197] Example B2. The method according to Example B1, wherein the network node (16) / radio interface (62) / processing circuit (68) is further configured to send the system clock information via two streams, a first stream of the two streams being implemented using a first packet data unit PDU session from a first WD (22), and a second stream of the two streams being implemented using a second PDU session from a second WD (22).

[0198] Example B3. The method according to Example B2, wherein each PDU session of the first and second PDU sessions includes a data radio bearer.

[0199] Example B4. The method according to Example B3, wherein first and second GTP-U tunnels are respectively associated with the first and second PDU sessions.

[0200] Example C1. A wireless device WD (22) configured to communicate with a network node (16), the WD (22) being configured to perform the following and / or include a radio interface (82) and / or include a processing circuit (84) configured to perform the following:

[0201] Determine whether to perform ingress timestamping or egress timestamping based on whether the WD (22) receives time-sensitive network TSN master GM clock information from a terminal station (in which case, perform ingress timestamping) or receives time-sensitive network TSN master GM clock information via a downlink 5G quality of service QoS flow (in which case, perform egress timestamping).

[0202] Example C2. The WD (22) according to Example C1, wherein the WD (22) / radio interface (82) / processing circuit (84) is further configured to receive TSN-GM clock information via at least one GTP-U tunnel, each of the at least one GTP-U tunnels having a corresponding uncertainty requirement for the TSN-GM clock information carried by the at least one GTP-U.

[0203] Example D1. A method implemented in a WD (22) communicating with a network node (16), the method comprising:

[0204] Determine whether to perform ingress timestamping or egress timestamping based on whether the WD (22) receives time-sensitive network TSN master GM clock information from the terminal station (in which case, perform ingress timestamping) or receives time-sensitive network TSN master GM clock information through a downlink 5G quality of service QoS flow (in which case, perform egress timestamping).

[0205] Example D2. The method according to Example D1 further includes: receiving TSN GM clock information through at least one GTP-U tunnel, each of the at least one GTP-U tunnels having a corresponding uncertainty requirement for the TSN-GM clock information carried by the at least one GTP-U, and the uncertainty requirement is to be used by the network node (16) to select a method for delivering 5G system clock information to the WD (22).

[0206] Embodiment AA1. A network node (16) configured to communicate with a wireless device WD (22), the network node (16) being configured to perform the following and / or include a radio interface (62) and / or include a processing circuit (68) configured to perform the following:

[0207] Receive time-sensitive communication assistance information TSCAI from a core network node (14), the TSCAI having a master GM clock synchronization accuracy parameter;

[0208] Determine, at least in part based on the accuracy parameter, when a quality of service QoS flow supports the delivery of time-sensitive network TSN GM clock information with a specific accuracy requirement; and

[0209] When the QoS flow supports the delivery of the TSN GM clock information of the grandson Shu with the specific accuracy requirement and the network node 16 supports using a method suitable for the specific accuracy requirement to deliver downlink propagation delay identification information, send identification information to the WD (22) so that the WD (22) can identify the downlink propagation delay between the network node (16) and the WD (22) and adjust the access network clock to compensate for the identified downlink propagation delay.

[0210] Embodiment AA2. The network node (16) according to Embodiment AA1, wherein the network node (16) and / or the radio interface (62) and / or the processing circuit (68) are further configured to: determine one of the following: no propagation delay is required due to cell size; pre-compensation of the sent identification information can be used for a specific range of cell sizes; and the round-trip time method can be used for cell sizes above a threshold.

[0211] Example AA3. The network node (16) according to any one of Examples AA1 to AA2, wherein the network node (16) and / or the radio interface (62) and / or the processing circuit (68) are further configured to associate an uncertainty attribute with each of a plurality of GTP-U tunnels, the uncertainty attribute being used by the network node (16) to determine which one of a plurality of radio interface signaling methods to use to send the identification information.

[0212] Example BB1. A method implemented in a network node (16), the method comprising:

[0213] Receiving time-sensitive communication assistance information TSCAI from a core network node (14), the TSCAI having a primary GM clock synchronization accuracy parameter;

[0214] Determining, at least in part based on the accuracy parameter, when a quality of service QoS flow supports delivery of time-sensitive network TSN GM clock information with a specific accuracy requirement;

[0215] When the QoS flow supports delivery of the TSN GM clock information with the specific accuracy requirement and the network node 16 supports using a method suitable for the specific accuracy requirement to deliver downlink propagation delay identification information, sending the identification information to the WD (22) such that the WD (22) can identify the downlink propagation delay between the network node (16) and the WD (22) and adjust the access network clock to compensate for the identified downlink propagation delay.

[0216] Example BB2. The method according to Example BB1, further comprising: determining one of: that a downlink propagation delay is not required due to cell size; that pre-compensation of the sent identification information can be used for a specific range of cell sizes; and that a round-trip time RTT method can be used for cell sizes above a threshold.

[0217] Example BB3. The method according to any one of Examples BB1 to BB2, further comprising: associating an uncertainty attribute with each of a plurality of GTP-U tunnels, the uncertainty attribute being used by the network node (16) to determine which one of a plurality of radio interface signaling methods to use to send the identification information.

[0218] Example CC1. A core network node (14) configured to communicate with one or more network nodes (16) that communicate with one or more wireless devices (22) WD, the core network node (14) being configured to perform the following and / or include a communication interface (94) and / or include a processing circuit (96) configured to perform the following:

[0219] Generate time-sensitive communication assistance information TSCAI, the TSCAI having a master GM clock synchronization accuracy parameter that indicates when a quality of service QoS flow supports the delivery of time-sensitive network TSN GM clock information with a specific accuracy requirement; and

[0220] Send the TSCAI to at least one of the one or more network nodes (16).

[0221] Example DD1. A method implemented in a core network node (14) that communicates with one or more network nodes (16), the method comprising:

[0222] Generate time-sensitive communication assistance information TSCAI, the TSCAI having a master GM clock synchronization accuracy parameter that indicates when a quality of service QoS flow supports the delivery of time-sensitive network TSN GM clock information with a specific accuracy requirement; and

[0223] Send the TSCAI to at least one of the one or more network nodes (16).

[0224] Thus, in one or more embodiments, the 5GS clock / access network clock is used to timestamp TSN timing packets at the ingress and egress for TSN timing packet 5GS dwell time compensation between the ingress and egress. Delivering the 5GS clock to WD 22 can take into account the RF propagation delay to allow WD 22 to have a more accurate copy of the 5GS time, thereby improving end-to-end TSN timing accuracy delivery.

[0225] As will be understood by those skilled in the art, the concepts described herein can be implemented as a method, a data processing system, a computer program product, and / or a computer storage medium storing executable computer programs. Thus, the concepts described herein can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects, all generally referred to herein as a "circuit" or "module". Any process, step, action, and / or function described herein can be performed and / or associated with a corresponding module implemented using software and / or firmware and / or hardware. In addition, the present disclosure can take the form of a computer program product on a tangible computer-usable storage medium having computer program code executable by a computer. Any suitable tangible computer-readable medium can be used, including a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device.

[0226] Some embodiments are described herein with reference to flowcharts and / or block diagrams of methods, systems, and computer program products. It will be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer (resulting in a special-purpose computer), a processor of a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions executed via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the flowchart and / or block diagram block(s).

[0227] These computer program instructions can also be stored in a computer-readable memory or storage medium, which can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means for implementing the functions / actions specified in the flowchart and / or block diagram block(s).

[0228] 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 to produce a computer-implemented process, such that the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions / actions specified in the flowchart and / or block diagram block(s).

[0229] It should be understood that the functions / actions marked in the boxes can occur in the order marked in the operation diagram. For example, two boxes shown consecutively can actually be executed substantially concurrently, or the boxes can sometimes be executed in the reverse order, depending on the functions / actions involved. Although some figures include arrows indicating the main direction of communication on the communication path, it should be understood that communication can occur in the direction opposite to the depicted arrows.

[0230] The computer program code for performing the operations of the concepts described herein can be written in an object-oriented programming language (such as or C++). However, the computer program code for performing the operations of the present disclosure can also be written in a conventional procedural programming language, such as the "C" programming language. The program code can run entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter scenario, the remote computer can be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0231] Numerous different embodiments have been disclosed herein in connection with the above description and the accompanying drawings. It will be understood that a literal description and illustration of every combination and sub-combination of these embodiments would be overly repetitive and ambiguous. Accordingly, all embodiments can be combined in any manner and / or combination, and the present specification including the accompanying drawings should be construed as constituting a complete written description of all combinations and sub-combinations of the embodiments described herein and the ways and processes of making and using them, and should support claims to any such combination or sub-combination.

[0232] Abbreviations that may be used in the foregoing description include:

[0233] Abbreviation Explanation

[0234] 3GPP Third Generation Partnership Project

[0235] 5G Fifth Generation

[0236] 5QI 5G QoS Indicator

[0237] CE Control Element

[0238] CN Core Network

[0239] CNC Centralized Network Controller

[0240] DRB Data Radio Bearer

[0241] DS-TT Device-side TSN Converter

[0242] D2D Device-to-Device

[0243] DL Downlink

[0244] GM Master

[0245] GPRS General Packet Radio Service

[0246] gNB Next Generation Node B

[0247] gPTP General Precision Time Protocol

[0248] GTP-U GPRS Tunneling Protocol-User

[0249] LTE Long Term Evolution

[0250] MAC Media Access Control

[0251] NR New Radio

[0252] NW-TT Network TSN Converter

[0253] OTA Over-the-Air

[0254] PD Propagation Delay

[0255] ppb Parts Per Billion

[0256] PTP Precision Time Protocol

[0257] RAR Radio Access Response

[0258] RRC Radio Resource Control

[0259] RTT Round-Trip Time

[0260] SFN Superframe Number

[0261] SIB System Information Block

[0262] SMF Session Management Function

[0263] TEID Tunnel Endpoint Identifier

[0264] TSCAI Time-Sensitive Communication Auxiliary Information

[0265] TSN AF Time-Sensitive Network Application Function

[0266] TA Timing Advance

[0267] TS Time Synchronization

[0268] TTI Transmission Time Interval

[0269] UE User Equipment

[0270] UL Uplink

[0271] UPF User Plane Function

[0272] URLLC Ultra-Reliable Low-Latency Communication

[0273] Those skilled in the art will understand that the embodiments described herein are not limited to what has been particularly shown and described above. Additionally, unless stated to the contrary above, it should be noted that all the drawings are not to scale. Various modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

1. A network node (16) configured to communicate with a wireless device (22) via an access network (12), the wireless device (22) being configured to communicate with a terminal station via a time-sensitive network TSN (23) separate from the access network, the network node (16) comprising: Processing circuitry (68) configured to: Receive at least one parameter from a core network node (14), the at least one parameter indicating a synchronization accuracy level required for a TSN clock in the TSN (23); And Based on the synchronization accuracy level for the TSN clock, implement one of a plurality of methods in the access network (12) for distributing access network clock information to the wireless device (22) and for determining downlink propagation delay information, each of the plurality of methods being associated with a different synchronization accuracy level for the access network clock, the TSN clock being based on the access network clock; Wherein the plurality of methods include: A first method that includes determining a downlink propagation delay in the access network using a conventional TA process, the determined downlink propagation delay being configured for access network clock compensation; a second method that includes determining a downlink propagation delay in the access network (12) using a round-trip time RTT process, the RTT process having a higher synchronization accuracy than the conventional TA process, the determined downlink propagation delay being configured for access network clock compensation; and A third method that does not include determining a downlink propagation delay in the access network (12).

2. The network node (16) according to claim 1, wherein, The downlink propagation delay information is configured to allow updating of the access network clock associated with the access network clock information, the updated access network clock being configured to allow timestamping of TSN clock information for compensation of the TSN clock information.

3. The network node (16) according to claim 1, wherein, The at least one parameter is time-sensitive communication assistance information TSCAI, the TSCAI having a master GM clock synchronization accuracy parameter.

4. The network node (16) according to any one of claims 1 to 3, wherein, The processing circuitry (68) is configured to use at least one QoS flow to relay the TSN clock information through the access network (12) for delivery to the terminal station in the TSN (23) via the wireless device (22).

5. The network node (16) according to claim 4, wherein, The at least one QoS flow includes a first QoS flow and a second QoS flow; and The processing circuitry (68) is configured to: Relay the TSN clock information through the access network (12) using the first QoS flow associated with a first protocol data unit PDU session from the wireless device (22) and the second QoS flow associated with a second PDU session from another wireless device (22) connected to the terminal station that requires the TSN clock.

6. The network node (16) according to claim 4, wherein, The at least one QoS flow is configured to indicate multiple accuracy levels for the TSN clock.

7. The network node (16) according to any one of claims 1 to 3, wherein, The processing circuitry (68) is configured to distribute TSN clock information in the user plane of the access network (12).

8. The network node (16) according to any one of claims 1 to 3, wherein, The synchronization accuracy level for the access network clock corresponds to the end-to-end synchronization accuracy required by the TSN clock.

9. The network node (16) according to any one of claims 1 to 3, wherein, The multiple methods include at least one of the following: A first method configured to broadcast the access network clock information to the wireless device (22) using a system information block SIB broadcast; and A second method configured to distribute the access network clock information to the wireless device (22) using a radio resource control RRC unicast.

10. A wireless device (22) configured to communicate with a network node (16) via an access network (12) and with a terminal station in a time-sensitive network TSN (23), the TSN (23) being separate from the access network (12), the wireless device (22) comprising: Processing circuitry (84) configured to: Receive access network clock information and downlink propagation delay information via one of multiple methods that meet the synchronization accuracy level for the access network (12) required by the TSN clock in the TSN (23), each of the multiple methods being associated with a different synchronization accuracy level for the access network clock; and Cause the TSN clock information to be transmitted to the terminal station in the TSN (23), the TSN clock information being based on the access network clock information; wherein the multiple methods include: A first method that includes determining the downlink propagation delay in the access network using a conventional TA procedure, the determined downlink propagation delay being configured for access network clock compensation; a second method that includes determining the downlink propagation delay in the access network (12) using a round-trip time RTT procedure, the RTT procedure having a higher synchronization accuracy than the conventional TA procedure, the determined downlink propagation delay being configured for access network clock compensation; and A third method that does not include determining the downlink propagation delay in the access network (12).

11. The wireless device (22) according to claim 10, wherein, The processing circuitry (84) is configured to: Determine a propagation delay based at least on the downlink propagation delay; Update the access network clock based on the determined propagation delay; Perform an add egress timestamp on the TSN clock information received from the network node (16), wherein the add egress timestamp is performed using the updated access network clock; Determine that the TSN clock information needs to be adjusted based at least on the add egress timestamp; and Compensate the TSN clock information based on the determined adjustment.

12. The wireless device (22) according to claim 10, wherein, The processing circuitry (84) is configured to: Determine a propagation delay based at least on the downlink propagation delay; Update the access network clock based on the determined propagation delay; and Perform an add ingress timestamp on the TSN clock information received from the terminal station in the TSN, wherein the add ingress timestamp is performed using the updated access network clock, the add ingress timestamp being configured to adjust the TSN clock information.

13. The wireless device (22) according to any one of claims 10 to 12, wherein, The processing circuit (84) is configured to relay the TSN clock information through the access network (12) using at least one QoS flow.

14. The wireless device (22) according to claim 13, wherein, The at least one QoS flow includes a first QoS flow and a second QoS flow; and The processing circuit (84) is configured to: relay the TSN clock information through the access network (12) using the first QoS flow associated with a first protocol data unit PDU session from the wireless device (22) and the second QoS flow associated with a second PDU session from another wireless device (22) connected to a terminal station that requires the TSN clock.

15. The wireless device (22) according to claim 13, wherein, The at least one QoS flow is configured to indicate multiple accuracy levels for the TSN clock.

16. The wireless device (22) according to any one of claims 10 to 12, wherein, The processing circuit (84) is configured to receive the TSN clock information in the user plane of the access network (12).

17. The wireless device (22) according to any one of claims 10 to 12, wherein, The synchronization accuracy level for the access network clock corresponds to the end-to-end synchronization accuracy required for the TSN clock.

18. The wireless device (22) according to any one of claims 10 to 12, wherein, The multiple methods include at least one of the following: A first method, which is configured to broadcast the access network clock information to the wireless device (22) using a system information block SIB broadcast; And A second method, which is configured to distribute the access network clock information to the wireless device (22) using a radio resource control RRC unicast.

19. A method implemented by a network node (16), the network node (16) being configured to communicate with a wireless device (22) via an access network (12), the wireless device (22) being configured to communicate with a terminal station via a time-sensitive network TSN (23) separate from the access network, the method comprising: Receiving (S140) at least one parameter from a core network node (14), the at least one parameter indicating a synchronization accuracy level required for a TSN clock in the TSN (23); And Based on the synchronization accuracy level for the TSN clock, implementing (S142) one of multiple methods in the access network (12) for distributing access network clock information to the wireless device (22) and for determining downlink propagation delay information, each of the multiple methods being associated with a different synchronization accuracy level for the access network clock, the TSN clock being based on the access network clock; Wherein the multiple methods include: A first method, which includes determining the downlink propagation delay in the access network using a conventional TA process, the determined downlink propagation delay being configured for access network clock compensation; A second method, which includes determining the downlink propagation delay in the access network (12) using a round-trip time RTT process, the RTT process having a higher synchronization accuracy than the conventional TA process, the determined downlink propagation delay being configured for access network clock compensation; and A third method, which does not include determining the downlink propagation delay in the access network (12).

20. The method according to claim 19, wherein The downlink propagation delay information is configured to allow updating of the access network clock associated with the access network clock information, wherein the updated access network clock is configured to allow timestamping of the TSN clock information for compensation of the TSN clock information.

21. The method according to claim 19, wherein, The at least one parameter is time-sensitive communication assistance information TSCAI, and the TSCAI has a master GM clock synchronization accuracy parameter.

22. The method according to any one of claims 19 to 21, wherein, Use at least one QoS flow to relay the TSN clock information through the access network (12) for delivery to the terminal station in the TSN (23) via the wireless device (22).

23. The method according to claim 22, wherein, The at least one QoS flow includes a first QoS flow and a second QoS flow; and Relay the TSN clock information through the access network (12) using the first QoS flow associated with a first protocol data unit PDU session from the wireless device (22) and the second QoS flow associated with a second PDU session from another wireless device (22) connected to the terminal station that requires the TSN clock.

24. The method according to claim 22, wherein, The at least one QoS flow is configured to indicate multiple accuracy levels for the TSN clock.

25. The method according to any one of claims 19 to 21, wherein, Distribute the TSN clock information in the user plane of the access network (12).

26. The method according to any one of claims 19 to 21, wherein, The synchronization accuracy level for the access network clock corresponds to the end-to-end synchronization accuracy required for the TSN clock.

27. The method according to any one of claims 19 to 21, wherein, The multiple methods include at least one of the following: A first method configured to broadcast the access network clock information to the wireless device (22) using system information block SIB broadcast; And A second method configured to distribute the access network clock information to the wireless device (22) using radio resource control RRC unicast.

28. A method implemented by a wireless device (22), the wireless device being configured to communicate with a network node (16) via an access network (12) and with a terminal station in a time-sensitive network TSN (23), the TSN (23) being separated from the access network (12), the method comprising: Receiving (S154) access network clock information and downlink propagation delay information via one of multiple methods that meet the synchronization accuracy level for the access network (12) required for the TSN clock in the TSN (23), each of the multiple methods being associated with a different synchronization accuracy level for the access network clock; And Causing (S156) the TSN clock information to be transmitted to the terminal station in the TSN (23), the TSN clock information being based on the access network clock information; Wherein the multiple methods include: A first method that includes determining the downlink propagation delay in the access network using a conventional TA process, the determined downlink propagation delay being configured for access network clock compensation; A second method, which includes determining a downlink propagation delay in the access network (12) using a round-trip time (RTT) process that has a higher synchronization accuracy than the conventional timing advance (TA) process, and the determined downlink propagation delay is configured for access network clock compensation; and A third method, which does not include determining a downlink propagation delay in the access network (12).

29. The method according to claim 28, further comprising: Determining a propagation delay based at least on the downlink propagation delay; Updating the access network clock based on the determined propagation delay; Performing an add egress timestamp on the TSN clock information received from the network node (16), wherein the add egress timestamp is performed using the updated access network clock; Determining that the TSN clock information needs to be adjusted based at least on the add egress timestamp; and Compensating the TSN clock information based on the determined adjustment.

30. The method according to claim 28, further comprising: Determining a propagation delay based at least on the downlink propagation delay; Updating the access network clock based on the determined propagation delay; and And Performing an add ingress timestamp on the TSN clock information received from the terminal station in the TSN, wherein the add ingress timestamp is performed using the updated access network clock, and the add ingress timestamp is configured to adjust the TSN clock information.

31. The method according to any one of claims 28 to 30, wherein, Relaying the TSN clock information through the access network (12) using at least one QoS flow.

32. The method according to claim 31, wherein The at least one QoS flow includes a first QoS flow and a second QoS flow; and Relaying the TSN clock information through the access network (12) using the first QoS flow associated with a first protocol data unit (PDU) session from the wireless device (22) and the second QoS flow associated with a second PDU session from another wireless device (22) connected to the terminal station that requires the TSN clock.

33. The method according to claim 31, wherein, The at least one QoS flow is configured to indicate multiple accuracy levels for the TSN clock.

34. The method according to any one of claims 28 to 30, wherein Receiving the TSN clock information in the user plane of the access network (12).

35. The method according to any one of claims 28 to 30, wherein The synchronization accuracy level for the access network clock corresponds to the end-to-end synchronization accuracy required for the TSN clock.

36. The method according to any one of claims 28 to 30, wherein, The multiple methods include at least one of the following: A first method, which is configured to broadcast the access network clock information to the wireless device (22) using a system information block (SIB) broadcast; And A second method, which is configured to distribute the access network clock information to the wireless device (22) using a radio resource control (RRC) unicast.

Images