Timing resilient and ultra-reliable low latency communications

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a radio access network (RAN) node may receive a time synchronization status (TSS) request message that includes a request to cause the RAN node to send TSS information. The RAN node may send an associated TSS response message after receiving the TSS request message. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Indian Patent Application No. 202341009722 filed on February 14, 2023, entitled “TIMING RESILIENCY AND ULTRA-RELIABLE LOW-LATENCY COMMUNICATIONS” and assigned to the assignee of the present application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for timing resiliency and ultra-reliable low-latency communications. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0007] Wireless communication systems such as 5G systems may need to support timing resilience and ultra-reliable low-latency communication (URLLC). One goal related to supporting timing resilience and URLLC is to support network timing synchronization status and reporting. Another goal related to supporting timing resilience and URLLC is to support adjustment of downlink and uplink scheduling based on RAN feedback for low-latency communication. Another goal related to supporting timing resilience and URLLC is to support interworking with TSN deployed in the transport network. Some aspects described herein provide techniques and apparatus for supporting timing resilience and URLLC.

[0008] Some aspects described herein relate to a method of wireless communication performed by a core network node. The method may include sending a time synchronization state (TSS) request message associated with a radio access network (RAN) node, the time synchronization state (TSS) request message including a request for the RAN node to send TSS information to the core network node. The method may include receiving a TSS response message associated with the RAN node after sending the TSS request message.

[0009] Some aspects described herein relate to a method of wireless communication performed by a RAN node. The method may include receiving a TSS request message including a request for the RAN node to send TSS information. The method may include sending a TSS response message after receiving the TSS request message.

[0010] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a system information block (SIB) including an indication to perform a random access channel (RACH) procedure to transition from operation in an idle mode in association with receiving clock quality information associated with a RAN node. The method may include performing the RACH procedure based at least in part on the indication and a randomized backoff time.

[0011] Some aspects described herein relate to a method of wireless communication performed by a core network node. The method may include sending a time-sensitive communication (TSC) assistance request message, the TSC assistance request message including an indication of at least one of: support for burst arrival time (BAT) adjustment, a BAT window, or a burst periodicity range. The method may include receiving a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0012] Some aspects described herein relate to a method of wireless communication performed by a RAN node. The method may include receiving a TSC assistance request message, the TSC assistance request message including an indication of at least one of: core network node support for BAT adjustment, a BAT window, or a burst periodicity range. The method may include sending a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0013] Some aspects described herein relate to a method of wireless communication performed by a core network node. The method may include sending a first message including a first talker and listener (TL) container, the first TL container including TL information associated with a time-sensitive network (TSN) node. The method may include receiving a second message including a second TL container including TL information associated with a RAN node.

[0014] Some aspects described herein relate to a method of wireless communication performed by a RAN node. The method may include receiving a first message including a first TL container including TL information associated with a TSN node. The method may include sending a second message including a second TL container including TL information associated with the RAN node.

[0015] Some aspects described herein relate to a core network node for wireless communications. The core network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a TSS request message associated with a RAN node, the TSS request message including a request for the RAN node to send TSS information to the core network node. The one or more processors may be configured to receive a TSS response message associated with the RAN node after sending the TSS request message.

[0016] Some aspects described herein relate to a RAN node for wireless communications. The RAN node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a TSS request message including a request for the RAN node to send TSS information. The one or more processors may be configured to send a TSS response message after receiving the TSS request message.

[0017] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a signaling interface (SIB) including an indication to perform a RACH procedure to transition from operation in an idle mode in association with receiving clock quality information associated with a RAN node. The one or more processors may be configured to perform the RACH procedure based at least in part on the indication and a randomized backoff time.

[0018] Some aspects described herein relate to a core network node for wireless communications. The core network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a TSC assistance request message, the TSC assistance request message including an indication of at least one of: support for BAT adjustment, a BAT window, or a burst periodicity range. The one or more processors may be configured to receive a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0019] Some aspects described herein relate to a RAN node for wireless communications. The RAN node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a TSC assistance request message, the TSC assistance request message including an indication of at least one of: core network node support for BAT adjustment, a BAT window, or a burst periodicity range. The one or more processors may be configured to send a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0020] Some aspects described herein relate to a core network node for wireless communications. The core network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a first message including a first TL container including TL information associated with a TSN node. The one or more processors may be configured to receive a second message including a second TL container including TL information associated with a RAN node.

[0021] Some aspects described herein relate to a RAN node for wireless communications. The RAN node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a first message including a first TL container including TL information associated with a TSN node. The one or more processors may be configured to send a second message including a second TL container including TL information associated with the RAN node.

[0022] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a core network node. The instruction set, when executed by one or more processors of the core network node, may cause the core network node to send a TSS request message associated with a RAN node, the TSS request message including a request for the RAN node to send TSS information to the core network node. The instruction set, when executed by one or more processors of the core network node, may cause the core network node to receive a TSS response message associated with the RAN node after sending the TSS request message.

[0023] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communications by a RAN node. The instruction set, when executed by one or more processors of the RAN node, may cause the RAN to receive a TSS request message that includes a request for the RAN node to send TSS information. The instruction set, when executed by one or more processors of the RAN node, may cause the RAN to send a TSS response message after receiving the TSS request message.

[0024] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a SIB including an indication to perform a RACH procedure in association with receiving clock quality information associated with a RAN node to transition from operating in an idle mode. The instruction set, when executed by the one or more processors of the UE, may cause the UE to perform a RACH procedure based at least in part on the indication and a randomized backoff time.

[0025] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a core network node. The instruction set, when executed by one or more processors of a UE, may cause the core network node to send a TSC assistance request message, the TSC assistance request message including an indication of at least one of: support for BAT adjustment, a BAT window, or a burst periodicity range. The instruction set, when executed by one or more processors of the core network node, may cause the core network node to receive a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0026] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communications by a RAN. The instruction set, when executed by one or more processors of a RAN node, may cause the RAN to receive a TSC assistance request message, the TSC assistance request message including an indication of at least one of: core network node support for BAT adjustment, a BAT window, or a burst periodicity range. The instruction set, when executed by one or more processors of the RAN node, may cause the RAN to send a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0027] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a core network node. The instruction set, when executed by one or more processors of the core network node, may cause the core network node to send a first message including a first TL container including TL information associated with a TSN node. The instruction set, when executed by one or more processors of the core network node, may cause the core network node to receive a second message including a second TL container including TL information associated with a RAN node.

[0028] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a RAN. The instruction set, when executed by one or more processors of a RAN node, may cause the RAN to receive a first message including a first TL container including TL information associated with a TSN node. The instruction set, when executed by one or more processors of the RAN node, may cause the RAN to send a second message including a second TL container including TL information associated with the RAN node.

[0029] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a TSS request message associated with a RAN node, the TSS request message including a request for the RAN node to send TSS information to the apparatus. The apparatus may include means for receiving a TSS response message associated with the RAN node after sending the TSS request message.

[0030] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a TSS request message including a request for the apparatus to send TSS information. The apparatus may also include means for sending a TSS response message after receiving the TSS request message.

[0031] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a SIB including an indication to perform a RACH procedure to transition from operating in an idle mode in association with receiving clock quality information associated with a RAN node. The apparatus may include means for performing the RACH procedure based at least in part on the indication and a randomized backoff time.

[0032] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a TSC assistance request message, the TSC assistance request message including an indication of at least one of: support for BAT adjustment, a BAT window, or a burst periodicity range. The apparatus may include means for receiving a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0033] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a TSC assistance request message, the TSC assistance request message including an indication of at least one of: core network node support for BAT adjustment, a BAT window, or a burst periodicity range. The apparatus may include means for sending a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0034] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a first message including a first TL container including TL information associated with a TSN node. The apparatus may include means for receiving a second message including a second TL container including TL information associated with a RAN node.

[0035] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a first message including a first TL container including TL information associated with a TSN node. The apparatus may also include means for sending a second message including a second TL container including TL information associated with the apparatus.

[0036] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include: TSS subscription information associated with the UE. The method may include: receiving clock quality information associated with a RAN node, wherein the clock quality information received by the UE is based at least in part on the TSS subscription information associated with the UE.

[0037] Some aspects described herein relate to a user equipment (UE) for wireless communication. The user equipment may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to send TSS subscription information associated with the UE. The one or more processors may be configured to receive clock quality information associated with a RAN node, wherein the clock quality information received by the UE is based at least in part on the TSS subscription information associated with the UE.

[0038] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to transmit TSS subscription information associated with the UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive clock quality information associated with a RAN node, wherein the clock quality information received by the UE is based at least in part on the TSS subscription information associated with the UE.

[0039] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving TSS subscription information associated with the apparatus. The apparatus may include means for receiving clock quality information associated with a RAN node, wherein the clock quality information received by the apparatus is based at least in part on the TSS subscription information associated with the apparatus.

[0040] The various aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to the accompanying drawings and description, and as illustrated in the accompanying drawings and description.

[0041] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the following detailed description may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0042] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporated into the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and compositions. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order that the above-mentioned features of the present disclosure may be fully understood, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0044] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0045] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0046] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0047] Figure 4 is a diagram of an example of a core network configured to provide network slicing.

[0048] Figures 5 to 9 is a diagram illustrating an example associated with network timing synchronization status and reporting according to the present disclosure.

[0049] Figure 10 is a diagram illustrating an example associated with adjusting downlink and uplink scheduling for low-latency communication based on radio access network (RAN) feedback according to the present disclosure.

[0050] Figure 11 is a diagram illustrating an example associated with time-sensitive network (TSN) interworking deployed in a transport network according to the present disclosure.

[0051] Figure 12 is a diagram illustrating an example process performed, for example, by a core network node according to the present disclosure.

[0052] Figure 13 is a diagram illustrating an example process performed, for example, by a RAN node according to the present disclosure.

[0053] Figure 14 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0054] Figure 15 is a diagram illustrating an example process performed, for example, by a core network node according to the present disclosure.

[0055] Figure 16 is a diagram illustrating an example process performed, for example, by a RAN node according to the present disclosure.

[0056] Figure 17 is a diagram illustrating an example process performed, for example, by a core network node according to the present disclosure.

[0057] Figure 18 is a diagram illustrating an example process performed, for example, by a RAN node according to the present disclosure.

[0058] Figure 19 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0059] Figure 20 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0060] Figure 21 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0061] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of protection of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice method. Furthermore, the scope of the present disclosure is intended to cover such apparatus or method that is practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claims.

[0062] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0063] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0064] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (illustrated as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (illustrated as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0065] In some examples, network node 110 is or includes a network node (such as an RU) that communicates with UE 120 via a radio access link. In some examples, network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, network node 110 (such as a converged network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0066] In some examples, network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​network node 110 and / or a network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femtocell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macrocell may be referred to as a macro network node. A network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0067] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0068] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110 d (e.g., a relay network node) may communicate with a network node 110 a (e.g., a macro network node) and a UE 120 d to facilitate communications between the network node 110 a and the UE 120 d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0069] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0070] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0071] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0072] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0073] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0074] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0075] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0076] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0077] With the above examples in mind, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0078] In some aspects, a RAN node (e.g., network node 110) may include a communications manager 150. As described in greater detail elsewhere herein, the communications manager 150 may receive a time synchronization state (TSS) request message including a request for the RAN node to send a TSS; and send a TSS response message after receiving the TSS request message. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0079] In some aspects, UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive a system information block (SIB) including an indication to perform a random access channel (RACH) procedure to transition from operation in idle mode in association with receiving clock quality information associated with a RAN node; and perform the RACH procedure based at least in part on the indication and a randomized backoff time. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0080] Additionally or alternatively, as described in greater detail elsewhere herein, communications manager 140 may send TSS subscription information associated with UE 120; and receive clock quality information associated with a RAN node, wherein the clock quality information received by UE 120 is based at least in part on the TSS subscription information associated with UE 120. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0081] Additionally or alternatively, as described in greater detail elsewhere herein, the communications manager 150 may receive a time-sensitive communication (TSC) assistance request message including an indication of at least one of: core network node support for burst arrival time (BAT) adjustment, a BAT window, or a burst periodicity range; and, after sending the TSC assistance request message, send a TSC assistance response message including an indication of a BAT offset. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0082] Additionally or alternatively, as described in greater detail elsewhere herein, the communications manager 150 may receive a first message including a first publisher and subscriber (TL) container including TL information associated with a time-sensitive network (TSN) node, and send a second message including a second TL container including TL information associated with a RAN node. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0083] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0084] Figure 2 2 is a diagram illustrating example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.

[0085] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or frequency upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0086] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine, among other things, a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0087] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0088] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and / or one or more antenna arrays, etc. An antenna panel, antenna group, group of antenna elements, and / or antenna array may include one or more antenna elements (within a single housing or multiple housings), a group of coplanar antenna elements, a group of non-coplanar antenna elements, and / or be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0089] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to execute the instructions herein (eg, reference Figures 5 to 21 ) any aspects of any of the methods described.

[0090] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component (shown as DEMOD) of modem 232), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to a data sink 239 and decoded control information to controller / processor 240. Network node 110 may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions herein (e.g., reference 242). Figures 5 to 21 ) any aspects of any of the methods described.

[0091] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with timing resilience and ultra-reliable low-latency communications (URLLC), as described in more detail elsewhere herein. Figure 2 Any other component of the may perform or direct e.g. Figure 13 The process of 1300 Figure 14 The process of 1400 Figure 16 The process of 1600 Figure 18 1800 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 13 The process of 1300 Figure 14 The process of 1400 Figure 16 The process of 1600 Figure 18 The operations of process 1800 and / or other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0092] In some aspects, a RAN node (e.g., network node 110) includes means for receiving a TSS request message including a request for the RAN node to send TSS information; and / or means for sending a TSS response message after receiving the TSS request message.

[0093] In some aspects, the RAN node (e.g., network node 110) includes means for receiving a TSC assistance request message including an indication of at least one of: core network node support for BAT adjustment, a BAT window, or a burst periodicity range; and / or means for sending a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0094] In some aspects, a RAN node (e.g., network node 110) includes means for receiving a first message including a first TL container including TL information associated with a TSN node; and / or means for sending a second message including a second TL container including TL information associated with the RAN node.

[0095] In some aspects, means for the RAN node to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0096] In some aspects, the UE 120 includes means for receiving a SIB including an indication to perform a RACH procedure to transition from operation in an idle mode in association with receiving clock quality information associated with a RAN node; and / or means for performing the RACH procedure based at least in part on the indication and a randomized backoff time.

[0097] In some aspects, the UE 120 includes means for transmitting TSS subscription information associated with the UE 120; and / or means for receiving clock quality information associated with a RAN node, wherein the clock quality information received by the UE 120 is based at least in part on the TSS subscription information associated with the UE 120. Means for the UE 120 to perform the operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0098] Although Figure 2 The blocks in FIG. 2 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0099] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0100] The deployment of a communication system such as a 5G NR system can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station or network equipment may be implemented in an aggregated architecture or a decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality may be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. A “network entity” or a “network node” may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0101] A converged base station (e.g., a converged network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually spread across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among others.

[0102] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0103] Figure 3FIG2 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as via an F1 interface). Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0104] Each of the units (including the CU 310, DU 330, RU 340) and the near-RT RIC 325, the non-RT RIC 315, and the SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0105] In some aspects, the CU 310 may host one or more higher-layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among others. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0106] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers, at least in part according to a functional split (such as that defined by 3GPP). In some aspects, the one or more higher PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and the like. In some aspects, the DU 330 may also host one or more lower PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0107] Each RU 340 may implement low-layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as low-layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0108] The SMO framework 305 can be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0109] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0110] In some implementations, the non-RT RIC 315 may receive parameters or external enrichment information from an external server in order to generate an AI / ML model to be deployed in the near-RT RIC 325. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to regulate RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or through the creation of RAN management policies (such as A1 interface policies).

[0111] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0112] Figure 4 is a diagram of an example 400 of a core network 405 configured to provide network slicing. Figure 4 As shown, example 400 may include UE 120, wireless communication network 100, and core network 405. The devices and / or networks of example 400 may be interconnected via wired connections, wireless connections, or a combination thereof.

[0113] For example, the wireless communication network 100 may support a cellular RAT. The network 100 may include one or more network nodes, such as a base station (e.g., a base transceiver station, a radio base station, a Node B, an eNodeB (eNB), a gNodeB (gNB), a base station subsystem, a cell site, a cell tower, an access point, a TRP, a radio access node, a macrocell base station, a microcell base station, a picocell base station, a femtocell base station, or similar types of devices) and other network nodes that may support wireless communication of the UE 120. The network 100 may communicate traffic between the UE 120 (e.g., using a cellular RAT), one or more network nodes (e.g., using a wireless interface or a backhaul interface, such as a wired backhaul interface), and / or the core network 405. The wireless communication network 100 may provide one or more cells covering a geographic area.

[0114] In some aspects, the wireless communication network 100 may perform scheduling and / or resource management for UEs 120 covered by the network 100 (e.g., UEs 120 covered by a cell provided by the wireless communication network 100). In some aspects, the wireless communication network 100 may be managed by a network controller (e.g., Figure 1 The network controller 130) controls or coordinates, and the network controller can perform load balancing and / or network level configuration, etc. Figure 1 As described, the network controller can communicate with the network 100 via wireless or wired backhaul. In some aspects, the network 100 may include a network controller, a self-organizing network (SON) module or component, or similar modules or components. Thus, the network 100 can perform network control, scheduling, and / or network management functions (e.g., for uplink, downlink, and / or sidelink communications for the UE 120 covered by the network 100).

[0115] In some aspects, the core network 405 may include an example functional architecture in which the systems and / or methods described herein may be implemented. For example, the core network 405 may include an example architecture of a 5G next generation (NG) core network included in a fifth generation (5G) wireless telecommunications system. Figure 4 The example architecture of the core network 405 shown may be an example of a service-based architecture, but in some aspects the core network 405 may be implemented as a reference point architecture and / or a 4G core network, among others.

[0116] like Figure 4As shown, the core network 405 may include multiple functional elements. The functional elements may include, for example, a network slice selection function (NSSF) 410, a network open function (NEF) 415, an authentication server function (AUSF) 420, a unified data management (UDM) component 425, a policy control function (PCF) 430, an application function (AF) 435, an access and mobility management function (AMF) 440, a session management function (SMF) 445, a user plane function (UPF) 450 and / or a time-sensitive communication and time synchronization function (TSCTSF) 455, etc. These functional elements may be communicatively connected via a message bus 460. Figure 4 Each of the functional elements shown may be implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more of these functional elements may be implemented on physical devices such as access points, base stations, and / or gateways. In some implementations, one or more of these functional elements may be implemented on a computing device in a cloud computing environment.

[0117] NSSF 410 may include one or more devices that select a network slice instance for UE 120. Network slicing is a network architecture model in which logically distinct network slices operate using a common network infrastructure. For example, several network slices may operate as isolated end-to-end networks that are customized to meet different target service standards for different types of applications executed at least in part by UE 120 and / or communications to and from UE 120. Network slices can efficiently provide communications for different types of services with different service standards.

[0118] The NSSF 410 may determine a set of network slicing policies to be applied at the wireless communication network 100. For example, the NSSF 410 may apply one or more UE Routing Selection Policy (URSP) rules. In some aspects, the NSSF 410 may select a network slice based on a mapping of a Data Network Name (DNN) field included in a Routing Description (RSD) to a DNN field included in a service descriptor selected by the UE 120. By providing network slicing, the NSSF 410 allows operators to potentially deploy multiple, substantially independent end-to-end networks over the same infrastructure. In some implementations, each slice may be customized for different services.

[0119] NEF 415 may include one or more devices that support the opening of capabilities and / or events in the wireless telecommunication system to help other entities in the wireless telecommunication system discover network services. AUSF 420 may include one or more devices that act as an authentication server and support the process of authenticating UE 120 in the wireless telecommunication system.

[0120] The UDM 425 may include one or more devices that store user data and profiles in a wireless telecommunications system. In some aspects, the UDM 425 may be used for fixed access and / or mobile access in the core network 405, among other things.

[0121] The PCF 430 may include one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing, and / or mobility management, among other things. In some aspects, the PCF 430 may include one or more URSP rules used by the NSSF 410 to select a network slice instance for the UE 120.

[0122] AF 435 may include one or more devices that support application influence on traffic routing, access and / or policy control to NEF 415, etc.

[0123] The AMF 440 may include one or more devices that act as a termination point for, among other things, non-access stratum (NAS) signaling and / or mobility management. In some aspects, the AMF may request the NSSF 410 to select a network slice instance for the UE 120, e.g., at least in part in response to a request for data services from the UE 120. In some aspects, the AMF 440 may perform one or more operations associated with timing resilience and URLLC, as described herein. In some aspects, the AMF 440 may include the communications manager 170.

[0124] As described in more detail elsewhere herein, the communications manager 170 may send a TSS request message associated with a RAN node, the TSS request message including a request for the RAN node to send TSS information to a core network node; and receive a TSS response message associated with the RAN node after sending the TSS request message.

[0125] Additionally or alternatively, as described in more detail elsewhere herein, the communications manager 170 may send a TSC assistance request message that includes an indication of at least one of: support for BAT adjustment, a BAT window, or a burst periodicity range; and receive a TSC assistance response message after sending the TSC assistance request message that includes an indication of a BAT offset.

[0126] Additionally or alternatively, as described in more detail elsewhere herein, the communication manager 170 may send a first message including a first TL container including TL information associated with a TSN node; and receive a second message including a second TL container including TL information associated with a RAN node.

[0127] Additionally or alternatively, communications manager 170 may perform one or more other operations described herein.

[0128] In some aspects, the AMF 440 includes means for sending a TSS request message associated with the RAN node, the TSS request message including a request for the RAN node to send TSS information to the core network node; and / or means for receiving a TSS response message associated with the RAN node after sending the TSS request message.

[0129] In some aspects, the core network node includes means for sending a TSC assistance request message including an indication of at least one of: support for BAT adjustment, a BAT window, or a burst periodicity range; and / or means for receiving a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0130] In some aspects, the core network node includes means for sending a first message including a first TL container including TL information associated with the TSN node; and / or means for receiving a second message including a second TL container including TL information associated with the RAN node.

[0131] Means for the core network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0132] The SMF 445 may include one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, the SMF 445 may configure traffic steering policies and / or enforce user equipment IP address allocation and policies at the UPF 450, among other things. In some aspects, the SMF 445 may provision the UE 120 with a network slice instance selected by the NSSF 410.

[0133] The UPF 450 may include one or more devices that serve as anchor points for intra-RAT and / or inter-RAT mobility. In some aspects, the UPF 450 may apply rules to packets, such as rules related to packet routing, service reporting, and / or handling user plane QoS, among others.

[0134] TSCTSF 455 may include one or more devices that support determining traffic mode parameters and forwarding the traffic mode parameters in a TSC assistance container to one or more other devices such as SMF 445. In some aspects, TSCTSF 455 may receive traffic mode parameters from NEF 415.

[0135] The message bus 460 can be a logical communication structure and / or a physical communication structure for communicating between functional elements. Thus, the message bus 460 can allow communication between two or more functional elements, whether logically (e.g., using one or more application programming interfaces (APIs), etc.) and / or physically (e.g., using one or more wired connections and / or wireless connections).

[0136] Figure 4 The number and arrangement of devices and networks shown are provided as examples. In practice, there may be Figure 4 The devices and / or networks shown may include additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged differently than those shown. Figure 4 Two or more of the devices shown may be implemented in a single device, or Figure 4 The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, a collection of devices (eg, one or more devices) of example environment 400 may perform one or more functions described as being performed by another collection of devices of example environment 400.

[0137] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0138] Wireless communication systems such as 5G systems may need to support timing resilience and URLLC.

[0139] One goal related to supporting timing resilience and URLLC is to support network timing synchronization status and reporting. For example, the AMF function (e.g., AMF 440) may need to provide clock quality reporting control information to the RAN node (e.g., network node 110), and the RAN node may need to report clock quality information to the UE (e.g., UE 120) based on the clock quality reporting control information. In addition, the UE may need to be able to determine whether the clock quality information has changed (e.g., via information received in broadcast signaling). Additionally, the RAN node may need to report node-level TSS information to the AMF.

[0140] Examples of clock quality information include information associated with synchronization status (e.g., synchronized with a primary reference clock or in holdover), traceability information (e.g., traceable to Coordinated Universal Time (UTC)), accuracy information (e.g., in nanoseconds / milliseconds (ns / ms)), or frequency stability information. In practice, clock quality may change due to, for example, failures (e.g., due to failures in time distribution via the transport network) or targeted attacks (e.g., due to Global Navigation Satellite System (GNSS) jamming / spoofing). Furthermore, in some systems, operators may desire to control which UEs receive clock quality information, and the clock quality information may be delivered as a separate metric or implicitly (e.g., a RAN node may indicate whether the clock quality meets a threshold). In some systems, determining clock quality and delivering clock quality information to the UE depends on whether the UE receives time via RRC or via Precision Time Protocol (PTP).

[0141] Another goal related to supporting timing flexibility and URLLC is to support adjusting downlink and uplink scheduling based on RAN feedback for low-latency communication. Here, RAN enhancements may be needed to apply scheduling adjustments based on RAN feedback (e.g., feedback on burst arrival time, periodicity, etc.) for low-latency communication.

[0142] Another goal related to supporting timing resilience and URLLC is to support interworking with TSN deployed in transport networks.

[0143] Certain aspects described herein provide techniques and apparatus for supporting timing resilience and URLLC.

[0144] In some aspects, a core network node (e.g., AMF 440) may send a TSS request message associated with a RAN node, and the RAN node (e.g., network node 110) may receive the TSS request message. The TSS request message may include a request for the RAN node to send TSS information to the core network node. After sending the TSS request message, the RAN node may send a TSS response message associated with the RAN node, and the core network node may receive the TSS response message.

[0145] In some aspects, a UE (e.g., UE 120) may receive a SIB that includes an indication to perform a RACH procedure to transition from operating in idle mode in association with receiving clock quality information associated with a RAN node (e.g., network node 110). The UE may then perform the RACH procedure based at least in part on the indication and a randomized backoff time.

[0146] In some aspects, a core network node (e.g., AMF 440) may send a TSC Assistance Request message, and a RAN node (e.g., network node 110) may receive the TSC Assistance Request message, the TSC Assistance Request message including an indication of at least one of: support for BAT adjustment, a BAT window, or a burst periodicity range. After sending the TSC Assistance Request message, the RAN node may send a TSC Assistance Response message, and the core network node may receive the TSC Assistance Response message. The TSC Assistance Response message may include at least an indication of a BAT offset.

[0147] In some aspects, a core network node (e.g., AMF 440) may send a first message including a first TL container including TL information associated with a TSN node, and a RAN node (e.g., network node 110) may receive the first message. The RAN node may send a second message including a second TL container including TL information associated with the RAN node, and the core network node may receive the second message.

[0148] Figures 5 to 9 is a diagram illustrating an example associated with network timing synchronization status and reporting according to aspects of the present disclosure. Figures 5 to 8 In the illustrated example, a core network node such as the AMF 440 and a RAN node such as the network node 110 or the decomposed network node 110 perform operations associated with network timing synchronization status and reporting.

[0149] like Figure 5 As shown in example 500 of FIG. 5 , a core network node (e.g., AMF 440) registers for TSS with another core network node (e.g., TSC TSF 455) at reference 502. In some aspects, registering for TSS triggers AMF 440 to perform operations associated with time synchronization and status reporting described below.

[0150] As shown at reference 504, the AMF 440 may send a TSS information request message associated with the network node 110, and the RAN node (e.g., the network node 110) may receive the TSS information request message. In some aspects, the TSS information request message includes a request for the network node 110 to send TSS information (e.g., to the AMF 440, to the UE 120, etc.). In some aspects, the TSS information request message may be sent and received over an NGAP interface.

[0151] In some aspects, the TSS information request message may indicate one or more parameters associated with TSS information reporting. The one or more parameters may indicate, for example, a reporting periodicity or a reporting triggering event (e.g., an event that, when detected, triggers the network node 110 to send TSS information to the AMF 440). As another example, the one or more parameters may indicate one or more thresholds, such as a clock quality threshold. The one or more thresholds are thresholds used in association with triggering TSS information reporting. For example, with respect to a clock quality threshold, if the network node 110 detects that the clock quality satisfies the clock quality threshold (e.g., the clock quality is less than the threshold), then TSS information reporting by the network node 110 may be triggered. In some aspects, one or more parameters associated with TSS information reporting may be triggered in another manner. For example, in some aspects, a reporting triggering event associated with TSS information reporting may be configured on the network node 110 via operations and management (OAM).

[0152] As shown at reference 506, after the AMF sends the TSS Information Request message, the network node 110 may send a TSS Information Response message associated with the network node 110, and the AMF 440 may receive the TSS Information Response message. In some aspects, the TSS Information Response message may be sent and received over an NGAP interface.

[0153] In some aspects, the TSS response message includes clock information associated with the network node 110. The clock information may include information associated with the quality of a clock of the network node 110 used to support wireless communications. The clock quality information may include, for example, an indication of synchronization status, synchronization performance, time source, clock quality, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the clock information is valid, among other things.

[0154] In some aspects, the TSS information response message may indicate that the network node 110 does not support TSS information reporting or indicate a partial failure associated with TSS information reporting, as shown at reference 508. That is, if the network node 110 does not support TSS, the network node 110 may transmit a failure indication in response to the TSS information request message.

[0155] In some aspects, as shown at reference 510, the AMF 440 may send an activation message, and the network node 110 may receive the activation message, the activation message including an indication that the network node 110 will begin TSS information reporting. In some aspects, the activation message may indicate one or more parameters associated with TSS information reporting (e.g., one or more parameters as described above with respect to reference 504). In some aspects, the activation message may be sent and received over an NGAP interface.

[0156] In some aspects, as shown at reference 512, the network node 110 may send an activation failure, and the AMF 440 may receive the activation failure, indicating that the network node 110 does not support TSS information reporting as indicated in the activation message or indicating a partial failure associated with the TSS information reporting as indicated in the activation message. That is, if the network node 110 does not support TSS information reporting as indicated in the activation message, the network node 110 may transmit a failure indication in response to the activation message.

[0157] In some aspects, as shown at reference 514, the network node 110 may send TSS information associated with the network node 110, and the AMF 440 may receive the TSS information. That is, the network node 110 may initiate TSS information reporting in response to the activation message. In some aspects, the network node 110 may send TSS information based at least in part on one or more parameters associated with TSS reporting (e.g., the network node 110 may initiate TSS reporting at a periodicity indicated in the TSS information request message or the activation message). In some aspects, the TSS information may include information associated with at least one of: synchronization status, synchronization performance, time source, clock quality of a clock associated with the network node 110, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the clock information is valid. In some aspects, the TSS information may be sent and received over an NGAP interface.

[0158] In some aspects, as shown at reference 516, the AMF 440 may send, and the network node 110 may receive, a deactivation message including an indication that the network node 110 is to stop TSS information reporting.

[0159] In some aspects, the network node 110 may be a converged network node 110 , as illustrated in example 500 .

[0160] Alternatively, the network node 110 may be a decomposed network node, an example of which is shown in FIG. Figure 6600. In example 600, the AMF 440 communicates with the CU-CP component (e.g., CU 310 (CU-CP)) of the network node 110 via the NGAP interface. As shown in example 600, after receiving the message from the AMF 440, the CU 310 (CU-CP) forwards the message to the DU component (DU 330) of the network node 110 and the CU-UP component (CU 310 (CU-UP)) of the network node 110. As a specific example, at reference 504, the CU 310 (CU-CP) component may receive the TSS information request message and may forward the TSS information request message to the DU 330 via the F1AP interface and forward the TSS information request message to the CU 310 (CU-UP) via the E1AP interface.

[0161] As further shown, the network node 110 CU-UP may receive and forward messages from the CU 310 (CU-UP) and the DU 330. As shown in example 600, upon receiving a first message from the CU 310 (CU-UP) and a second message from the DU 330, the CU 310 (CU-CP) collects these messages and forwards them to the AMF 440. As a specific example, upon receiving a first TSS report from the CU 310 (CU-UP) via the E1AP interface and a second TSS report from the DU 330 via the F1AP interface, the CU 310 (CU-CP) may combine these TSS reports and forward the combined TSS report to the AMF 440 via the NGAP interface.

[0162] Figure 7 and Figure 8 An alternative example associated with TSS information reporting is illustrated. Figure 7 As shown in example 700 of FIG. 4 , at reference 702, the AMF 440 may register with the TSC TSF 455 for TSS. In some aspects, registering for TSS triggers the AMF 440 to perform operations associated with time synchronization and status reporting described below.

[0163] As shown at reference 704, the AMF 440 may send a TSS initiation request message associated with the network node 110, and the RAN node (e.g., the network node 110) may receive the TSS initiation request message. In some aspects, the TSS initiation request message includes a request for the network node 110 to send TSS information (e.g., to the AMF 440). In some aspects, the TSS initiation request message may be sent and received over an NGAP interface.

[0164] In some aspects, the TSS initiation request message includes an indication that the network node 110 will initiate TSS information reporting. Notably, in example 700, initiation of TSS reporting is provided by the TSS initiation request message (e.g., rather than by a separate activation message), which may reduce overhead associated with TSS information reporting. In some aspects, the TSS initiation request message may indicate one or more parameters associated with TSS information reporting (e.g., one or more parameters as described above with respect to reference 504).

[0165] As shown at reference 706, after the AMF 440 sends the TSS Initiation Request message, the network node 110 may send a TSS Initiation Response message associated with the network node 110, and the AMF 440 may receive the TSS Initiation Response message. In some aspects, the TSS Initiation Response message may be sent and received over an NGAP interface.

[0166] In some aspects, the TSS initiation response message includes clock information associated with the network node 110. The clock information may include information associated with the quality of a clock of the network node 110 used to support wireless communications. The clock quality information may include, for example, an indication of synchronization status, synchronization performance, time source, clock quality, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the clock information is valid, among other things.

[0167] In some aspects, the TSS initiation response message may indicate that the network node 110 does not support TSS information reporting or may indicate a partial failure associated with TSS information reporting, as shown in reference 708. That is, if the network node 110 does not support TSS information reporting, the network node 110 may transmit a failure indication in response to the TSS initiation request message.

[0168] In some aspects, as shown at reference 710, the network node 110 may send TSS information associated with the network node 110, and the AMF 440 may receive the TSS information. That is, the network node 110 may initiate TSS information reporting in response to the TSS initiation request. In some aspects, the network node 110 may send TSS information based at least in part on one or more parameters associated with TSS reporting (e.g., the network node 110 may initiate TSS reporting at a periodicity indicated in the TSS initiation request message). In some aspects, the TSS information may include information associated with at least one of: synchronization status, synchronization performance, a time source, clock quality of a clock associated with the network node 110, clock frequency stability, clock accuracy, a parent time source, clock traceability, or a list of cells for which the clock information is valid. In some aspects, the TSS information may be sent and received over an NGAP interface.

[0169] In some aspects, as shown at reference 712, the AMF 440 may send, and the network node 110 may receive, a terminate command including an indication that the network node 110 is to stop TSS information reporting.

[0170] In some aspects, as shown at reference 714, the network node 110 may send a termination failure, and the AMF 440 may receive the termination failure, indicating that the network node 110 is unable to stop TSS information reporting as indicated in the termination command.

[0171] In some aspects, the network node 110 may be a converged network node 110 , as illustrated in example 700 .

[0172] Alternatively, in some aspects, the network node 110 may be a decomposed network node, an example of which is shown in FIG. Figure 8 800. In example 800, the AMF 440 communicates with the CU 310 (CU-CP) of the network node 110 via the NGAP interface. As shown in example 800, upon receiving the message from the AMF 440, the CU 310 (CU-CP) forwards the message to the DU 330 of the network node 110 and the CU 310 (CU-UP) of the network node 110. As a specific example, at reference 704, the CU 310 (CU-CP) component may receive a TSS initiation request message and may forward the TSS initiation request message to the DU 330 via the F1AP interface and forward the TSS initiation request message to the CU 310 (CU-UP) via the E1AP interface.

[0173] As further shown, the CU-CP 310 may receive and forward messages from the CU 310 (CU-UP) and the DU 330. As shown in example 800, upon receiving a first message from the CU 310 (CU-UP) and a second message from the DU 330, the CU 310 (CU-CP) collects these messages and forwards them to the AMF 440. As a specific example, upon receiving a first TSS report from the CU 310 (CU-UP) via the E1AP interface and a second TSS report from the DU 330 via the F1AP interface, the CU 310 (CU-CP) may combine these TSS reports and forward them to the AMF 440.

[0174] Figure 9 is a diagram illustrating example operations of UE 120 regarding timing synchronization status and reporting. Figure 9 In the illustrated example 900, RAN nodes such as the network node 110 and the UE 120 perform operations associated with network timing synchronization status and reporting.

[0175] As shown at reference 902, UE 120 may send TSS subscription information associated with UE 120, and AMF 440 may receive the TSS subscription information. The TSS subscription information may include, for example, an indication of whether UE 120 is authorized to receive clock quality information associated with network node 110, information indicating a format in which the clock quality information will be provided to UE 120, and the like. For example, the TSS subscription information may indicate one or more items of TSS information (e.g., an actual clock quality value, actual values ​​of one or more TSS-related information, etc.) to be included in the clock quality information provided to UE 120. For another example, the TSS subscription information may indicate that UE 120 will receive an indication of whether the clock quality is acceptable (e.g., a binary indication of whether UE 120 will accept the clock quality, instead of or in addition to providing one or more items of TSS information to UE 120).

[0176] In some aspects, UE 120 may send TSS subscription information during operation in connected mode. In some aspects, UE 120 may send TSS subscription information to AMF 440 via the network node 110 to which UE 120 is connected.

[0177] As shown at reference 904, the AMF 440 may send TSS subscription information associated with the UE 120, and the network node 110 may receive the TSS subscription information. In some aspects, the AMF 440 may send the TSS subscription information associated with the UE 120 in an NG UE context setup message or a modification message.

[0178] As shown at reference 906, the network node 110 may detect a trigger to send clock quality information associated with the network node 110 to the UE 120. In some aspects, the trigger may be an event-based trigger (e.g., an event that, when detected, triggers the network node 110 to send the clock quality information to the UE 120). In one example, the event-based trigger may be a determination that the clock quality fails to meet a clock quality threshold. Here, if the network node 110 detects that the clock quality meets the clock quality threshold (e.g., the clock quality is less than the threshold), the network node 110 may be triggered to send the clock quality information to the UE 120. Additionally or alternatively, the trigger may be a periodic trigger (e.g., such that the network node 110 is configured to send the clock quality information to the UE 120 on a periodic basis).

[0179] In some aspects, UE 120 may be operating in idle mode. In such a scenario, UE 120 should transition to connected mode to enable UE 120 to receive clock quality information associated with network node 110. Thus, as shown at reference 908, in some aspects, network node 110 may transmit an SIB, and UE 120 (if in idle mode) may receive the SIB, which includes an indication to perform a RACH procedure to transition from operating in idle mode in association with receiving clock quality information associated with network node 110. That is, network node 110 may transmit an SIB (e.g., SIB9) for receipt by idle mode UE 120, and the SIB may include an indication that UE 120 is to perform a RACH procedure to transition from idle mode to connected mode to enable UE 120 to receive clock quality information associated with network node 110.

[0180] As shown at reference 910, if operating in idle mode, the UE 120 may perform a RACH procedure based at least in part on the indication. In some aspects, the UE 120 performs the RACH procedure based at least in part on a randomized backoff time. In some aspects, the randomized backoff time is utilized to reduce PRACH collisions that would result from multiple UEs 120 concurrently performing RACH procedures.

[0181] In some aspects, UE 120 may be configured with a wait time between the time a SIB is received (e.g., SIB9 indicating the availability of TSS information to be provided to UE 120) and the time a RACH procedure is performed. That is, in some aspects, UE 120 may receive an indication of a randomized backoff time while UE 120 is operating in connected mode (e.g., prior to operating in idle mode). In some aspects, UE 120 may receive an indication of a randomized backoff time via RRC signaling. Additionally or alternatively, UE 120 may receive an indication of a randomized backoff time via NAS layer signaling.

[0182] In some aspects, the UE 120 may determine a randomized backoff time. For example, to achieve a randomized backoff time (and minimize the probability of collision), in some aspects, the UE 120 may use the UE network identifier as a seed to generate a randomized backoff time before performing a RACH procedure. This may provide for randomization of backoff times across the UE 120 without relying on a large backoff window that may otherwise result in access delays. The UE network identifier may be, for example, a Paging Radio Network Temporary Identifier (P-RNTI), a Globally Unique Temporary Identity (GUTI), a Subscriber Permanent Identifier (SUPI), a Temporary Mobile Subscriber Identity (TMSI), an International Mobile Subscriber Identity (IMSI), or an International Mobile Equipment Identity (IMEI), among others.

[0183] In some aspects, after successfully performing a RACH procedure based at least in part on the randomized backoff time (e.g., such that the UE 120 operates in connected mode), the UE 120 can receive clock quality information from the network node 110. Notably, the connected mode UE 120 need not perform operations associated with references 908 and 910, as the connected mode UE 120 may be able to receive the clock quality information (e.g., via an RRC message).

[0184] As shown at reference 912, the network node 110 may transmit clock quality information associated with the network node 110, and the UE 120 may receive (e.g., after transitioning to connected mode, if desired) the clock quality information. In some aspects, the clock quality information may include one or more items of TSS information, such as information associated with synchronization status, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the TSS information is valid. Additionally or alternatively, the clock quality information may include <> Additionally or alternatively, the clock quality information may include an indication of whether the clock quality is acceptable.

[0185] In some aspects, the clock quality information sent by network node 110 to UE 120 is based at least in part on TSS subscription information associated with UE 120. For example, the clock quality information sent by network node 110 may include one or more items of TSS information, as specified by the TSS subscription information associated with UE 120. For another example, if the TSS subscription information associated with UE 120 indicates that the clock quality information provided to UE 120 will include an indication of whether the clock quality is acceptable, network node 110 determines clock quality acceptance criteria configured for network node 110 and may determine whether the clock quality is acceptable based at least in part on the clock quality acceptance criteria. The clock quality acceptance criteria may include, for example, a clock quality threshold or one or more other criteria based at least in part on which clock quality may be evaluated. In some aspects, the clock quality acceptance criteria may be configurable for network node 110 (e.g., by a core network device). In this example, network node 110 may then send clock quality information including an indication of whether the clock quality is acceptable (e.g., an indication of whether the clock quality meets the clock quality acceptance criteria). In some aspects, network node 110 may send clock quality information via an RRC message, and UE 120 may receive the clock quality information via the RRC message.

[0186] As indicated above, Figures 5 to 9 are provided as examples. Other examples can be found in the Figures 5 to 9 The examples described are different.

[0187] Figure 10 is a diagram illustrating an example 1000 associated with adjusting downlink and uplink scheduling for low-latency communication based on RAN feedback in accordance with aspects of the present disclosure. In example 1000, a core network node, such as the AMF 440, and a RAN node, such as the network node 110 or a decomposed network node 110, perform operations associated with adjusting downlink and uplink scheduling for low-latency communication based on RAN feedback.

[0188] As shown at reference 1002, the AMF 440 may send a TSC Assistance Request message, and the network node 110 may receive the TSC Assistance Request message, the TSC Assistance Request message including an indication of at least one of: support for BAT adjustment, a BAT window, or a burst periodicity range. That is, in some aspects, the AMF 440 may request the network node 110 to provide TSC assistance associated with adjusting downlink or uplink scheduling by indicating support for BAT adjustment, by indicating a BAT window, or by indicating a burst periodicity range. In some aspects, such information may be carried in a TSC Assistance Information Information Element (IE) conveyed in a Packet Data Unit (PDU) Session Resource Establishment or Modification Request. In some aspects, the TSC Assistance Request message may be communicated via an NGAP interface.

[0189] As shown at reference 1004, the network node 110 may send a TSC assistance response message, and the AMF 440 may receive the TSC assistance response message. In some aspects, the TSC assistance response message may include an indication of a BAT offset. In some aspects, the BAT offset is an offset relative to the start of the BAT window. In some aspects, the TSC assistance response message includes an indication of a burst periodicity within a burst periodicity range.

[0190] In one example, if the TSC assistance request message indicates a BAT window and a burst periodicity range, the network node 110 may indicate a BAT offset within the BAT window and may indicate a burst periodicity within the burst periodicity range (e.g., in a PDU session resource establishment / modification response).

[0191] In some aspects, network node 110 may send an indication of a BAT offset based at least in part on an inability of network node 110 to meet one or more TSC characteristics indicated in the TSC assistance request message. For example, in some aspects, network node 110 may indicate a BAT offset if network node 110 is unable to meet TSC characteristics for the downlink or uplink indicated in the PDU session resource modification indication.

[0192] Figure 111 is a diagram illustrating an example associated with TSN interworking deployed in a transport network according to aspects of the present disclosure. In example 1100, a core network node, such as AMF 440, and a RAN node, such as network node 110 or decomposed network node 110, perform operations associated with TSN interworking deployed in a transport network.

[0193] As shown at reference 1102, the AMF 440 may send a first message including a first TL container, and the network node 110 may receive the first message, the first TL container including TL information associated with the TSN node. In some aspects, the TL information associated with the TSN node includes, for example, a time-aware offset associated with the TSN node, an interface configuration associated with the TSN node, or information associated with another configuration associated with the TSN node. In some aspects, the AMF 440 may obtain the TL information associated with the TSN node from, for example, the SMF 445 or the TSN node.

[0194] As shown at reference 1104, the network node 110 may send a second message including a second TL container, and the AMF 440 may receive the second message, the second TL container including TL information associated with the network node 110. In some aspects, the TL information associated with the network node 110 includes, for example, interface capability information associated with the network node 110, end station interface information associated with the network node 110, or information associated with another configuration or capability of the network node 110. In some aspects, the AMF 440 may send the TL information associated with the network node 110 to, for example, the SMF 445 or a TSN node.

[0195] In some aspects, the exchange of TL information associated with TSN nodes and TL information associated with network node 110 enables interworking of TSN networks deployed in a transport network (e.g., to support end-to-end determinism and low-latency communication and efficient transmission).

[0196] Figure 12 1 is a diagram illustrating an example process 1200 performed, for example, by a core network node in accordance with the present disclosure. The example process 1200 is an example in which a core network node (e.g., AMF 440) performs operations associated with timing resilience and URLLC.

[0197] like Figure 12 As shown, in some aspects, process 1200 may include sending a TSS request message associated with a RAN node, the TSS request message including a request for the RAN node to send TSS information to a core network node (block 1210). For example, the core network node (e.g., using Figure 19The sending component 1904 and / or the communication manager 1906 depicted in may send a TSS request message associated with the RAN node, the TSS request message comprising a request for the RAN node to send TSS information to the core network node, as described above.

[0198] like Figure 12 As further shown, in some aspects, process 1200 may include receiving a TSS response message associated with a RAN node after sending the TSS request message (block 1220). For example, a core network node (e.g., using Figure 19 The receiving component 1902 and / or the communication manager 1906 depicted in FIG. 1 may receive a TSS response message associated with the RAN node after sending the TSS request message, as described above.

[0199] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0200] In a first aspect, the TSS response message includes clock information associated with the RAN node.

[0201] In a second aspect, alone or in combination with the first aspect, the clock information comprises an indication of at least one of: synchronization status, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the clock information is valid.

[0202] In a third aspect, alone or in combination with one or more of the first and second aspects, the TSS response message indicates that the RAN node does not support TSS information reporting or indicates a partial failure associated with TSS information reporting.

[0203] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1200 includes receiving TSS information associated with a RAN node.

[0204] In a fifth aspect, either alone or in combination with one or more of aspects one to four, the TSS information comprises information associated with at least one of: synchronization status, clock frequency stability, clock accuracy, a parent time source, clock traceability, or a list of cells for which the TSS information is valid.

[0205] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the TSS request message indicates one or more parameters associated with the TSS information report.

[0206] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the one or more parameters indicate at least one of: a reporting periodicity, a reporting triggering event, or a threshold associated with TSS information reporting.

[0207] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the TSS request message includes an indication that the RAN node is to start TSS information reporting.

[0208] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the process 1200 includes sending a termination command including an indication that the RAN node is to stop TSS information reporting.

[0209] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the process 1200 includes receiving a terminate command response including an indication that the RAN node is unable to stop TSS information reporting.

[0210] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the process 1200 includes sending an activation message including an indication that the RAN node will start TSS information reporting.

[0211] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the activation message indicates one or more parameters associated with TSS information reporting.

[0212] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the process 1200 comprises sending a deactivation message including an indication that the RAN node is to stop TSS information reporting.

[0213] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the process 1200 includes receiving a deactivation response message including an indication that the RAN node cannot stop TSS information reporting.

[0214] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the RAN node is a decomposed RAN node.

[0215] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the process 1200 includes sending TSS subscription information associated with a UE connected to a RAN node.

[0216] although Figure 12 Example blocks of process 1200 are shown, but in some aspects, process 1200 may include Figure 12 1200. In some embodiments, the process 1200 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1200 may be executed in parallel.

[0217] Figure 13 is a diagram illustrating an example process 1300 performed, for example, by a RAN node in accordance with the present disclosure. The example process 1300 is an example in which a RAN node (eg, network node 110) performs operations associated with timing resilience and URLLC.

[0218] like Figure 13 As shown, in some aspects, process 1300 may include receiving a TSS request message including a request for a RAN node to send TSS information (block 1310). For example, a RAN node (e.g., using Figure 20 The receiving component 2002 and / or the communication manager 2006 depicted in FIG. 2004 may receive a TSS request message comprising a request for the RAN node to send TSS information, as described above.

[0219] like Figure 13 As further shown, in some aspects, process 1300 may include sending a TSS response message after receiving the TSS request message (block 1320). For example, a RAN (e.g., using Figure 20 The sending component 2004 and / or the communication manager 2006 depicted in may send a TSS response message after receiving the TSS request message, as described above.

[0220] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0221] In a first aspect, the TSS response message includes clock information associated with the RAN node.

[0222] In a second aspect, alone or in combination with the first aspect, the clock information comprises an indication of at least one of: synchronization status, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the clock information is valid.

[0223] In a third aspect, alone or in combination with one or more of the first and second aspects, the TSS response message indicates that the RAN node does not support TSS information reporting or indicates a partial failure associated with TSS information reporting.

[0224] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1300 includes sending TSS information associated with a RAN node.

[0225] In a fifth aspect, either alone or in combination with one or more of aspects one to four, the TSS information comprises information associated with at least one of: synchronization status, clock frequency stability, clock accuracy, a parent time source, clock traceability, or a list of cells for which the TSS information is valid.

[0226] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, TSS information is sent based at least in part on detection of a reporting triggering event associated with TSS information reporting.

[0227] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, TSS information is sent based at least in part on a reporting periodicity associated with TSS information reporting.

[0228] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the TSS request message indicates one or more parameters associated with the TSS information report.

[0229] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the one or more parameters indicate at least one of: a reporting periodicity, a reporting triggering event, or a threshold associated with TSS information reporting.

[0230] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the TSS request message includes an indication to start TSS information reporting.

[0231] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the process 1300 includes receiving a termination command including an indication to stop TSS information reporting.

[0232] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the process 1300 comprises sending a terminate command response including an indication that the RAN node is unable to stop TSS information reporting.

[0233] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the process 1300 includes receiving an activation message including an indication to start TSS information reporting.

[0234] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the activation message indicates one or more parameters associated with TSS information reporting.

[0235] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the process 1300 includes receiving a deactivation message including an indication to stop TSS information reporting.

[0236] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the process 1300 comprises sending a deactivation response message including an indication that the RAN node cannot stop TSS information reporting.

[0237] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the RAN node is a decomposed RAN node.

[0238] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the process 1300 includes receiving TSS subscription information associated with a UE connected to a RAN node.

[0239] In a nineteenth aspect, alone or in combination with one or more of aspects one to eighteen, process 1300 comprises sending clock quality information for receipt by the UE based at least in part on TSS subscription information associated with the UE, wherein the clock quality information is sent via an RRC message.

[0240] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the clock quality information includes one or more items of TSS information.

[0241] In a twenty-first aspect, alone or in combination with one or more of aspects one to twentieth, TSS subscription information associated with the UE indicates that the UE will receive an indication of whether the clock quality is acceptable, and process 1300 includes: determining a clock quality acceptance criterion configured for the RAN node; and determining whether the clock quality is acceptable based at least in part on the clock quality acceptance criterion, wherein the clock quality information includes an indication of whether the clock quality is acceptable.

[0242] In a twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, the process 1300 includes sending TSS subscription information associated with the UE to another RAN node.

[0243] although Figure 13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Figure 131300. In some embodiments, the process 1300 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1300 may be executed in parallel.

[0244] Figure 14 is a diagram illustrating an example process 1400, performed, for example, by a UE, according to the present disclosure. Example process 1400 is an example in which a UE (eg, UE 120) performs operations associated with timing flexibility and URLLC.

[0245] like Figure 14 As shown, in some aspects, process 1400 may include sending TSS subscription information associated with a UE (block 1410). For example, a UE (e.g., using Figure 21 The sending component 2104 and / or the communication manager 2106 depicted in may send TSS subscription information associated with the UE, as described above.

[0246] like Figure 14 As further shown, in some aspects, process 1400 may include receiving clock quality information associated with a RAN node, wherein the clock quality information received by the UE is based at least in part on TSS subscription information associated with the UE (block 1420). For example, the UE (e.g., using Figure 21 The receiving component 2102 and / or the communication manager 2106 depicted in may receive clock quality information associated with the RAN node, wherein the clock quality information received by the UE is based at least in part on TSS subscription information associated with the UE, as described above.

[0247] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0248] In a first aspect, clock quality information is received via an RRC message.

[0249] In a second aspect, alone or in combination with the first aspect, the clock quality information includes one or more items of TSS information.

[0250] In a third aspect, alone or in combination with one or more of the first and second aspects, the TSS subscription information indicates that the UE is to receive at least one of: one or more clock quality values, or an indication of whether the clock quality is acceptable.

[0251] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1400 comprises: receiving a SIB comprising an indication to perform a RACH procedure to transition from operating in an idle mode in association with receiving clock quality information associated with a RAN node; and performing the RACH procedure based at least in part on the indication and a randomized backoff time.

[0252] In a fifth aspect, alone or in combination with one or more of aspects 1 to 4, process 1400 may include receiving an indication of a randomized backoff time, the indication of the randomized backoff time being received during operation in connected mode prior to operation in idle mode.

[0253] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 1400 includes determining a randomized backoff time based at least in part on information associated with the UE.

[0254] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the information associated with the UE includes a UE network identifier.

[0255] although Figure 14 Example blocks of process 1400 are shown, but in some aspects, process 1400 may include Figure 14 1400. In some embodiments, the process 1400 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1400 may be executed in parallel.

[0256] Figure 15 1 is a diagram illustrating an example process 1500 performed, for example, by a core network node in accordance with the present disclosure. The example process 1500 is an example in which a core network node (e.g., AMF 440) performs operations associated with timing resilience and URLLC.

[0257] like Figure 15 As shown, in some aspects, process 1500 may include sending a TSC assistance request message including an indication of at least one of: support for BAT adjustment, BAT window, or burst periodicity range (block 1510). For example, a core network node (e.g., using Figure 19 The transmitting component 1904 and / or the communication manager 1906 depicted in may send a TSC assistance request message comprising an indication of at least one of: support for BAT adjustment, a BAT window, or a burst periodicity range, as described above.

[0258] like Figure 15As further shown, in some aspects, process 1500 may include, after sending the TSC assistance request message, receiving a TSC assistance response message, the TSC assistance response message including an indication of the BAT offset (block 1520). For example, a core network node (e.g., using Figure 19 The receiving component 1902 and / or the communication manager 1906 depicted in FIG. 1 may receive a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of the BAT offset, as described above.

[0259] Process 1500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0260] In a first aspect, the BAT offset is an offset relative to the start of the BAT window.

[0261] In a second aspect, alone or in combination with the first aspect, the TSC assistance response message comprises an indication of a burst periodicity within a burst periodicity range.

[0262] although Figure 15 Example blocks of process 1500 are shown, but in some aspects, process 1500 may include Figure 15 1500. In some embodiments, the process 1500 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1500 may be executed in parallel.

[0263] Figure 16 is a diagram illustrating an example process 1600 performed, for example, by a RAN node in accordance with the present disclosure. The example process 1600 is an example in which a RAN node (eg, network node 110) performs operations associated with timing resilience and URLLC.

[0264] like Figure 16 As shown, in some aspects, process 1600 may include receiving a TSC assistance request message including an indication of at least one of: core network node support for BAT adjustment, BAT window, or burst periodicity range (block 1610). For example, a RAN node (e.g., using Figure 20 The receiving component 2002 and / or the communication manager 2006 depicted in may receive a TSC assistance request message comprising an indication of at least one of: core network node support for BAT adjustment, a BAT window, or a burst periodicity range, as described above.

[0265] like Figure 16As further shown, in some aspects, process 1600 may include sending a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of the BAT offset (block 1620). For example, a RAN (e.g., using Figure 20 The transmitting component 2004 and / or the communication manager 2006 depicted in FIG. 2004 may send a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of the BAT offset, as described above.

[0266] Process 1600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0267] In a first aspect, the BAT offset is an offset relative to the start of the BAT window.

[0268] In a second aspect, alone or in combination with the first aspect, the TSC assistance response message comprises an indication of a burst periodicity within a burst periodicity range.

[0269] In a third aspect, alone or in combination with one or more of the first and second aspects, the BAT offset is sent based at least in part on the RAN node being unable to meet one or more TSC characteristics indicated in the TSC assistance request message.

[0270] although Figure 16 Example blocks of process 1600 are shown, but in some aspects, process 1600 may include Figure 16 1600. In some embodiments, the process 1600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1600 may be executed in parallel.

[0271] Figure 17 17 is a diagram illustrating an example process 1700 performed, for example, by a core network node in accordance with the present disclosure. Example process 1700 is an example in which a core network node (e.g., AMF 440) performs operations associated with timing resilience and URLLC.

[0272] like Figure 17 As shown, in some aspects, process 1700 may include sending a first message including a first TL container including TL information associated with a TSN node (block 1710). For example, a core network node (e.g., using Figure 19 The sending component 1904 and / or the communication manager 1906 depicted in can send a first message including a first TL container including TL information associated with the TSN node, as described above.

[0273] like Figure 17 As further shown, in some aspects, process 1700 may include receiving a second message including a second TL container including TL information associated with a RAN node (block 1720). For example, a core network node (e.g., using Figure 19 The receiving component 1902 and / or the communication manager 1906 depicted in may receive a second message including a second TL container including TL information associated with the RAN node, as described above.

[0274] Process 1700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0275] In a first aspect, TL information associated with a TSN node includes at least one of a time-aware offset or an interface configuration.

[0276] In a second aspect, alone or in combination with the first aspect, the TL information associated with the RAN node comprises at least one of interface capability information or end station interface information.

[0277] although Figure 17 Example blocks of process 1700 are shown, but in some aspects, process 1700 may include Figure 17 1700. In some embodiments, the process 1700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1700 may be executed in parallel.

[0278] Figure 18 is a diagram illustrating an example process 1800 performed, for example, by a RAN node in accordance with the present disclosure. The example process 1800 is an example in which a RAN node (eg, network node 110) performs operations associated with timing resilience and URLLC.

[0279] like Figure 18 As shown, in some aspects, process 1800 may include receiving a first message including a first TL container including TL information associated with a TSN node (block 1810). For example, a RAN node (e.g., using Figure 20 The receiving component 2002 and / or the communication manager 2006 depicted in can receive a first message including a first TL container including TL information associated with a TSN node, as described above.

[0280] like Figure 18As further shown, in some aspects, process 1800 may include sending a second message including a second TL container including TL information associated with a RAN node (block 1820). For example, a RAN node (e.g., using Figure 20 The sending component 2004 and / or the communication manager 2006 depicted in may send a second message including a second TL container including TL information associated with the RAN node, as described above.

[0281] Process 1800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0282] In a first aspect, TL information associated with a TSN node includes at least one of a time-aware offset or an interface configuration.

[0283] In a second aspect, alone or in combination with the first aspect, the TL information associated with the RAN node comprises at least one of interface capability information or end station interface information.

[0284] although Figure 18 Example blocks of process 1800 are shown, but in some aspects, process 1800 may include Figure 18 1800. In some embodiments, the process 1800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1800 may be executed in parallel.

[0285] Figure 19 1 is a diagram of an example apparatus 1900 for wireless communication according to the present disclosure. Apparatus 1900 may be a core network node (e.g., AMF 440), or a core network node may include apparatus 1900. In some aspects, apparatus 1900 includes a receiving component 1902, a sending component 1904, and / or a communication manager 1906, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1906 is in conjunction with Figure 4 As shown, the device 1900 can communicate with another device 1908, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 1902 and a sending component 1904.

[0286] In some aspects, the apparatus 1900 may be configured to perform Figures 5 to 11 Additionally or alternatively, the apparatus 1900 may be configured to perform one or more of the processes described herein, such as Figure 12The process of 1200 Figure 15 The process of 1500 Figure 17 In some aspects, Figure 19 The device 1900 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the core network node described. Figure 19 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0287] The receiving component 1902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1908. The receiving component 1902 may provide the received communications to one or more other components of the device 1900. In some aspects, the receiving component 1902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1900. In some aspects, the receiving component 1902 may include in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the core network nodes described. In some aspects, the receiving component 1902 and / or the transmitting component 1904 may include or be included in a network interface. The network interface may be configured to obtain and / or output signals for the device 1900 via one or more communication links, such as a backhaul link, a midhaul link, and / or a fronthaul link.

[0288] The transmitting component 1904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1908. In some aspects, one or more other components of the apparatus 1900 may generate communications and may provide the generated communications to the transmitting component 1904 for transmission to the apparatus 1908. In some aspects, the transmitting component 1904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 1908. In some aspects, the transmitting component 1904 may include a combination of Figure 2One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described core network nodes. In some aspects, the transmit component 1904 can be co-located with the receive component 1902 in a transceiver.

[0289] The communications manager 1906 can support the operation of the receiving component 1902 and / or the sending component 1904. For example, the communications manager 1906 can receive information associated with configuring the receipt of communications by the receiving component 1902 and / or the sending of communications by the sending component 1904. Additionally or alternatively, the communications manager 1906 can generate and / or provide control information to the receiving component 1902 and / or the sending component 1904 to control the receipt and / or sending of communications.

[0290] The sending component 1904 can send a TSS request message associated with the RAN node, the TSS request message including a request for the RAN node to send TSS information to the core network node. The receiving component 1902 can receive a TSS response message associated with the RAN node after sending the TSS request message.

[0291] Receiving component 1902 can receive TSS information associated with a RAN node.

[0292] Sending component 1904 can send a termination command including an indication that the RAN node is to stop TSS information reporting.

[0293] Receiving component 1902 can receive a terminate command response including an indication that the RAN node cannot stop TSS information reporting.

[0294] Sending component 1904 can send an activation message including an indication that the RAN node will begin TSS information reporting.

[0295] Sending component 1904 can send a deactivation message including an indication that the RAN node is to stop TSS information reporting.

[0296] Receiving component 1902 can receive a deactivation response message including an indication that the RAN node cannot stop TSS information reporting.

[0297] Transmitting component 1904 can transmit TSS subscription information associated with a UE connected to a RAN node.

[0298] The sending component 1904 can send a TSC assistance request message including an indication of at least one of: support for BAT adjustment, a BAT window, or a burst periodicity range. The receiving component 1902 can receive a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0299] The sending component 1904 can send a first message including a first TL container including TL information associated with a TSN node. The receiving component 1902 can receive a second message including a second TL container including TL information associated with a RAN node.

[0300] Figure 19 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 19 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 19 Two or more components shown may be implemented in a single component, or Figure 19 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 19 The illustrated set of components (one or more) may be described as being executable by Figure 19 Another group of components is shown performing one or more functions.

[0301] Figure 20 2 is a diagram of an example apparatus 2000 for wireless communication according to the present disclosure. Apparatus 2000 may be a RAN node (e.g., network node 110), or a RAN node may include apparatus 2000. In some aspects, apparatus 2000 includes a receiving component 2002, a sending component 2004, and / or a communication manager 2006, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 2006 is incorporated into Figure 1 The described communication manager 150. As shown, the apparatus 2000 can communicate with another apparatus 2008, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 2002 and a sending component 2004.

[0302] In some aspects, the apparatus 2000 may be configured to perform Figures 5 to 11 Additionally or alternatively, the apparatus 2000 may be configured to perform one or more of the processes described herein, such as Figure 13 The process of 1300 Figure 16 The process of 1600 Figure 18In some aspects, the apparatus 2000 and / or Figure 20 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the RAN node described. Figure 20 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0303] Receive component 2002 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from apparatus 2008. Receive component 2002 may provide the received communications to one or more other components of apparatus 2000. In some aspects, receive component 2002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of apparatus 2000. In some aspects, receive component 2002 may include processing the received communications in conjunction with one or more other components of apparatus 2000. Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described RAN nodes.

[0304] The transmitting component 2004 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 2008. In some aspects, one or more other components of the apparatus 2000 may generate communications and may provide the generated communications to the transmitting component 2004 for transmission to the apparatus 2008. In some aspects, the transmitting component 2004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 2008. In some aspects, the transmitting component 2004 may include a processor in conjunction with a processor. Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described RAN nodes. In some aspects, the transmitting component 2004 can be co-located with the receiving component 2002 in a transceiver.

[0305] The communications manager 2006 can support the operation of the receiving component 2002 and / or the sending component 2004. For example, the communications manager 2006 can receive information associated with configuring the receipt of communications by the receiving component 2002 and / or the sending of communications by the sending component 2004. Additionally or alternatively, the communications manager 2006 can generate and / or provide control information to the receiving component 2002 and / or the sending component 2004 to control the receipt and / or sending of communications.

[0306] Receiving component 2002 can receive a TSS request message comprising a request for a RAN node to transmit TSS information. Sending component 2004 can transmit a TSS response message after receiving the TSS request message.

[0307] Transmitting component 2004 can transmit TSS information associated with the RAN node.

[0308] Receiving component 2002 can receive a termination command including an indication to stop TSS information reporting.

[0309] Sending component 2004 can send a terminate command response including an indication that the RAN node cannot stop TSS information reporting.

[0310] Receiving component 2002 can receive an activation message including an indication to begin TSS information reporting.

[0311] Receiving component 2002 can receive a deactivation message including an indication to stop TSS information reporting.

[0312] Sending component 2004 can send a deactivation response message including an indication that the RAN node cannot stop TSS information reporting.

[0313] Receiving component 2002 can receive TSS subscription information associated with a UE connected to a RAN node.

[0314] Transmitting component 2004 can transmit clock quality information for receipt by the UE based at least in part on TSS subscription information associated with the UE, wherein the clock quality information is transmitted via an RRC message.

[0315] The communications manager 2006 may determine whether the clock quality is acceptable based at least in part on clock quality acceptance criteria configured for the RAN node, wherein the clock quality information includes an indication of whether the clock quality is acceptable.

[0316] Transmitting component 2004 can transmit TSS subscription information associated with the UE to another RAN node.

[0317] Receiving component 2002 can receive a TSC assistance request message including an indication of at least one of: core network node support for BAT adjustment, a BAT window, or a burst periodicity range. Sending component 2004 can send a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0318] Receiving component 2002 can receive a first message including a first TL container including TL information associated with a TSN node. Sending component 2004 can send a second message including a second TL container including TL information associated with a RAN node.

[0319] Figure 20 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 20 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 20 Two or more components shown may be implemented in a single component, or Figure 20 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 20 The illustrated set of components (one or more) may be described as being executable by Figure 20 Another group of components is shown performing one or more functions.

[0320] Figure 21 2 is a diagram of an example apparatus 2100 for wireless communication according to the present disclosure. Apparatus 2100 may be a UE, or a UE may include apparatus 2100. In some aspects, apparatus 2100 includes a receiving component 2102, a sending component 2104, and / or a communication manager 2106, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 2106 is a communication manager that is configured to communicate with one another. Figure 1 The described communication manager 140. As shown, the device 2100 can communicate with another device 2108 such as a UE or a network node (such as a CU, DU, RU, or base station) using a receiving component 2102 and a sending component 2104.

[0321] In some aspects, the apparatus 2100 may be configured to perform Figures 5 to 11 Additionally or alternatively, the apparatus 2100 may be configured to perform one or more of the processes described herein, such as Figure 14 The process 1400. In some aspects, Figure 21 The device 2100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, one or more components of the UE described. Figure 21 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0322] The receiving component 2102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 2108. The receiving component 2102 may provide the received communications to one or more other components of the device 2100. In some aspects, the receiving component 2102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 2100. In some aspects, the receiving component 2102 may include in conjunction with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0323] The transmitting component 2104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 2108. In some aspects, one or more other components of the device 2100 may generate communications and may provide the generated communications to the transmitting component 2104 for transmission to the device 2108. In some aspects, the transmitting component 2104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 2108. In some aspects, the transmitting component 2104 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmitting component 2104 can be co-located with the receiving component 2102 in a transceiver.

[0324] The communications manager 2106 can support the operation of the receiving component 2102 and / or the sending component 2104. For example, the communications manager 2106 can receive information associated with configuring the receipt of communications by the receiving component 2102 and / or the sending of communications by the sending component 2104. Additionally or alternatively, the communications manager 2106 can generate and / or provide control information to the receiving component 2102 and / or the sending component 2104 to control the receipt and / or sending of communications.

[0325] Transmitting component 2104 can transmit TSS subscription information associated with the UE.Receiving component 2102 can receive clock quality information associated with the RAN node, wherein the clock quality information received by the UE is based at least in part on the TSS subscription information associated with the UE.

[0326] Receiving component 2102 can receive a SIB including an indication to perform a RACH procedure to transition from operating in idle mode in association with receiving clock quality information associated with a RAN node. Communications manager 2106 can perform the RACH procedure based at least in part on the indication and a randomized backoff time.

[0327] Receiving component 2102 can receive an indication of a randomized backoff time, the indication of the randomized backoff time being received during operation in connected mode prior to operation in idle mode.

[0328] The communications manager 2106 may determine the randomized backoff time based at least in part on information associated with the UE.

[0329] Figure 21 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 21 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 21 Two or more components shown may be implemented in a single component, or Figure 21 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 21 The illustrated set of components (one or more) may be described as being executable by Figure 21 Another group of components is shown performing one or more functions.

[0330] The following provides an overview of some aspects of the disclosure:

[0331] Aspect 1: A method of wireless communication performed by a core network node, the method comprising: sending a time synchronization state (TSS) request message associated with a radio access network (RAN) node, the TSS request message comprising a request for the RAN node to send TSS information to the core network node; and receiving a TSS response message associated with the RAN node after sending the TSS request message.

[0332] Aspect 2: The method according to aspect 1, wherein the TSS response message includes clock information associated with the RAN node.

[0333] Aspect 3: A method according to aspect 2, wherein the clock information includes an indication of at least one of the following: synchronization status, synchronization performance, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the clock information is valid.

[0334] Aspect 4: The method according to any one of aspects 1 to 3, wherein the TSS response message indicates that the RAN node does not support TSS information reporting or indicates a partial failure associated with TSS information reporting.

[0335] Aspect 5: The method according to any one of aspects 1 to 4, further comprising: receiving the TSS information associated with the RAN node.

[0336] Aspect 6: The method according to aspect 5, wherein the TSS information includes information associated with at least one of the following: synchronization status, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the TSS information is valid.

[0337] Aspect 7: The method according to any one of aspects 1 to 6, wherein the TSS request message indicates one or more parameters associated with TSS information reporting.

[0338] Aspect 8: The method according to aspect 7, wherein the one or more parameters indicate at least one of the following: a reporting periodicity, a reporting triggering event, or a threshold associated with TSS information reporting.

[0339] Aspect 9: The method according to any one of aspects 1 to 8, wherein the TSS request message includes an indication that the RAN node will start TSS information reporting.

[0340] Aspect 10: The method according to aspect 9, further comprising: sending a termination command, the termination command including an indication that the RAN node will stop TSS information reporting.

[0341] Aspect 11: The method according to aspect 10, further comprising: receiving a termination command response, the termination command response including an indication that the RAN node is unable to stop TSS information reporting.

[0342] Aspect 12: The method according to any one of aspects 1 to 11, further comprising: sending an activation message, the activation message including an indication that the RAN node will start TSS information reporting.

[0343] Aspect 13: The method according to aspect 12, wherein the activation message indicates one or more parameters associated with TSS information reporting.

[0344] Aspect 14: The method according to aspect 12, further comprising: sending a deactivation message, the deactivation message including an indication that the RAN node will stop TSS information reporting.

[0345] Aspect 15: The method according to aspect 14, further comprising: receiving a deactivation response message, the deactivation response message including an indication that the RAN node is unable to stop TSS information reporting.

[0346] Aspect 16: The method according to any one of aspects 1 to 15, wherein the RAN node is a decomposed RAN node.

[0347] Aspect 17: The method according to any one of aspects 1 to 16, further comprising: sending TSS subscription information associated with a user equipment (UE) connected to the RAN node.

[0348] Aspect 18: A method of wireless communication performed by a radio access network (RAN) node, the method comprising: receiving a time synchronization status (TSS) request message, the time synchronization status (TSS) request message comprising a request for the RAN node to send TSS information; and sending a TSS response message after receiving the TSS request message.

[0349] Aspect 19: The method according to aspect 18, wherein the TSS response message includes clock information associated with the RAN node.

[0350] Aspect 20: The method of aspect 19, wherein the clock information comprises an indication of at least one of: synchronization status, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the clock information is valid.

[0351] Aspect 21: The method according to any one of aspects 18 to 20, wherein the TSS response message indicates that the RAN node does not support TSS information reporting or indicates a partial failure associated with TSS information reporting.

[0352] Aspect 22: The method according to any one of aspects 18 to 21, further comprising: sending the TSS information associated with the RAN node.

[0353] Aspect 23: The method according to aspect 22, wherein the TSS information includes information associated with at least one of the following: synchronization status, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the TSS information is valid.

[0354] Aspect 24: The method of aspect 22, wherein the TSS information is sent based at least in part on detection of a reporting triggering event associated with TSS information reporting.

[0355] Aspect 25: The method of aspect 22, wherein the TSS information is sent based at least in part on a reporting periodicity associated with TSS information reporting.

[0356] Aspect 26: The method according to any one of aspects 18 to 25, wherein the TSS request message indicates one or more parameters associated with TSS information reporting.

[0357] Aspect 27: The method according to aspect 26, wherein the one or more parameters indicate at least one of the following: a reporting periodicity, a reporting triggering event, or a threshold associated with TSS information reporting.

[0358] Aspect 28: The method according to any one of aspects 18 to 27, wherein the TSS request message includes an indication to start TSS information reporting.

[0359] Aspect 29: The method according to aspect 28, further comprising: receiving a termination command, the termination command including an instruction to stop TSS information reporting.

[0360] Aspect 30: The method according to aspect 29, further comprising: sending a terminate command response, the terminate command response including an indication that the RAN node is unable to stop TSS information reporting.

[0361] Aspect 31: The method according to any one of aspects 18 to 30, further comprising: receiving an activation message, the activation message including an indication to start TSS information reporting.

[0362] Aspect 32: The method according to aspect 31, wherein the activation message indicates one or more parameters associated with TSS information reporting.

[0363] Aspect 33: The method according to aspect 31, further comprising: receiving a deactivation message, the deactivation message including an instruction to stop TSS information reporting.

[0364] Aspect 34: The method according to aspect 33, further comprising: sending a deactivation response message, the deactivation response message including an indication that the RAN node is unable to stop TSS information reporting.

[0365] Aspect 35: The method according to any one of aspects 18 to 34, wherein the RAN node is a decomposed RAN node.

[0366] Aspect 36: The method according to any one of aspects 18 to 35, further comprising: receiving TSS subscription information associated with a user equipment (UE) connected to the RAN node.

[0367] Aspect 37: The method according to aspect 36 further includes: sending clock quality information for receipt by the UE based at least in part on the TSS subscription information associated with the UE, wherein the clock quality information is sent via an RRC message.

[0368] Aspect 38: The method according to Aspect 37, wherein the clock quality information includes one or more items of TSS information.

[0369] Aspect 39: A method according to aspect 37, wherein the TSS subscription information associated with the UE indicates that the UE will receive an indication of whether the clock quality is acceptable, wherein the method further includes: determining a clock quality acceptance criterion configured for the RAN node; and determining whether the clock quality is acceptable based at least in part on the clock quality acceptance criterion, wherein the clock quality information includes an indication of whether the clock quality is acceptable.

[0370] Aspect 40: The method according to aspect 36, further comprising: sending the TSS subscription information associated with the UE to another RAN node.

[0371] Aspect 41: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a system information block (SIB), the system information block (SIB) comprising an indication to perform a random access channel (RACH) procedure to transition from operating in an idle mode in association with receiving clock quality information associated with a radio access network (RAN) node; and performing the RACH procedure based at least in part on the indication and a randomized backoff time.

[0372] Aspect 42: The method according to Aspect 41 further comprises: receiving an indication of the randomized backoff time via radio resource control (RRC) signaling, the indication of the randomized backoff time being received during operation in connected mode before operation in idle mode.

[0373] Aspect 43: The method according to any one of aspects 41 to 42, further comprising: determining the randomized backoff time based at least in part on information associated with the UE.

[0374] Aspect 44: The method of aspect 43, wherein the information associated with the UE comprises a UE network identifier.

[0375] Aspect 45: A method of wireless communication performed by a core network node, the method comprising: sending a time-sensitive communication (TSC) assistance request message, the time-sensitive communication (TSC) assistance request message including an indication of at least one of: support for burst arrival time (BAT) adjustment, a BAT window, or a burst periodicity range; and receiving a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0376] Aspect 46: The method of aspect 45, wherein the BAT offset is an offset relative to the start of the BAT window.

[0377] Aspect 47: The method according to any one of aspects 45 to 46, wherein the TSC assistance response message includes an indication of a burst periodicity within the burst periodicity range.

[0378] Aspect 48: A method of wireless communication performed by a radio access network (RAN) node, the method comprising: receiving a time-sensitive communication (TSC) assistance request message, the time-sensitive communication (TSC) assistance request message including an indication of at least one of: core network node support for burst arrival time (BAT) adjustment, a BAT window, or a burst periodicity range; and sending a TSC assistance response message after sending the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0379] Aspect 49: The method of aspect 48, wherein the BAT offset is an offset relative to the start of the BAT window.

[0380] Aspect 50: The method according to any one of aspects 48 to 49, wherein the TSC assistance response message includes an indication of a burst periodicity within the burst periodicity range.

[0381] Aspect 51: The method of any one of aspects 48 to 50, wherein the BAT offset is sent based at least in part on the RAN node being unable to meet one or more TSC characteristics indicated in the TSC assistance request message.

[0382] Aspect 52: A method of wireless communication performed by a core network node, the method comprising: sending a first message including a first publisher and subscriber (TL) container, the first publisher and subscriber (TL) container including TL information associated with a time sensitive network (TSN) node; and receiving a second message including a second TL container, the second TL container including TL information associated with a radio access network (RAN) node.

[0383] Aspect 53: The method according to aspect 52, wherein the TL information associated with the TSN node includes at least one of a time-aware offset or an interface configuration.

[0384] Aspect 54: The method according to any one of aspects 52 to 53, wherein the TL information associated with the RAN node includes at least one of interface capability information or end station interface information.

[0385] Aspect 55: A method of wireless communication performed by a radio access network (RAN) node, the method comprising: receiving a first message including a first publisher and subscriber (TL) container, the first publisher and subscriber (TL) container including TL information associated with a time sensitive network (TSN) node; and sending a second message including a second TL container, the second TL container including TL information associated with the RAN node.

[0386] Aspect 56: The method of aspect 55, wherein the TL information associated with the TSN node comprises at least one of a time-aware offset or an interface configuration.

[0387] Aspect 57: The method according to any one of aspects 55 to 56, wherein the TL information associated with the RAN node includes at least one of interface capability information or end station interface information.

[0388] Aspect 58: A method of wireless communication performed by a user equipment (UE), the method comprising: sending time synchronization status (TSS) subscription information associated with the UE; and receiving clock quality information associated with a radio access network (RAN) node, wherein the clock quality information received by the UE is at least partially based on the TSS subscription information associated with the UE.

[0389] Aspect 59: The method of aspect 58, wherein the clock quality information is received via a radio resource control (RRC) message.

[0390] Aspect 60: The method according to any one of aspects 58 to 59, wherein the clock quality information comprises one or more items of TSS information.

[0391] Aspect 61: The method according to any one of aspects 58 to 60, wherein the TSS subscription information indicates that the UE is to receive at least one of: one or more clock quality values, or an indication of whether the clock quality is acceptable.

[0392] Aspect 62: The method according to any one of aspects 58 to 61, further comprising: receiving a system information block (SIB), the system information block (SIB) comprising an indication to perform a random access channel (RACH) procedure to transition from operating in idle mode in association with receiving the clock quality information associated with the RAN node; and performing the RACH procedure based at least in part on the indication and a randomized backoff time.

[0393] Aspect 63: The method according to aspect 62, further comprising: receiving an indication of the randomized backoff time, the indication of the randomized backoff time being received during operation in connected mode prior to operation in idle mode.

[0394] Aspect 64: The method of aspect 62, further comprising determining the randomized backoff time based at least in part on information associated with the UE.

[0395] Aspect 65: The method of aspect 64, wherein the information associated with the UE comprises a UE network identifier.

[0396] Aspect 66: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 65.

[0397] Aspect 67: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 65.

[0398] Aspect 68: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 65.

[0399] Aspect 69: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 65.

[0400] Aspect 70: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 65.

[0401] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0402] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of different forms of hardware and / or hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0403] As used herein, "satisfying a threshold" may mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0404] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other arrangement of a, b, and c).

[0405] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only want to refer to a project, then use the phrase "only one" or similar terms. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A radio access network (RAN) node for wireless communication, the radio access network (RAN) node comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a time synchronization state (TSS) request message, the time synchronization state (TSS) request message including a request for the RAN node to send TSS information; and A TSS response message is sent after receiving the TSS request message.

2. The RAN node of claim 1 , wherein the TSS response message comprises clock information associated with the RAN node, wherein the clock information comprises an indication of at least one of: synchronization status, clock frequency stability, clock accuracy, a parent time source, clock traceability, or a list of cells for which the clock information is valid.

3. The RAN node of claim 1 , wherein the TSS response message indicates that the RAN node does not support TSS information reporting or indicates a partial failure associated with TSS information reporting.

4. The RAN node of claim 1 , wherein the one or more processors are further configured to send the TSS information associated with the RAN node, wherein the TSS information comprises information associated with at least one of: synchronization status, clock frequency stability, clock accuracy, parent time source, clock traceability, or a list of cells for which the TSS information is valid.

5. The RAN node of claim 4, wherein the TSS information is sent based at least in part on at least one of detection of a reporting triggering event associated with TSS information reporting or a reporting periodicity associated with TSS information reporting.

6. The RAN node of claim 1 , wherein the TSS request message indicates one or more parameters associated with TSS information reporting, wherein the one or more parameters indicate at least one of: a reporting periodicity, a reporting triggering event, or a threshold associated with TSS information reporting.

7. The RAN node of claim 1 , wherein a reporting triggering event associated with TSS information reporting is configured on the RAN node via operations and management (OAM).

8. The RAN node according to claim 1, wherein the TSS request message includes an indication to start TSS information reporting.

9. The RAN node of claim 8, wherein the one or more processors are further configured to receive a termination command, the termination command including an indication to stop TSS information reporting.

10. The RAN node of claim 9, wherein the one or more processors are further configured to send a terminate command response including an indication that the RAN node cannot stop TSS information reporting.

11. The RAN node of claim 1 , wherein the one or more processors are further configured to receive an activation message, the activation message comprising an indication to start TSS information reporting, wherein the activation message indicates one or more parameters associated with TSS information reporting.

12. The RAN node of claim 11, wherein the one or more processors are further configured to receive a deactivation message including an indication to stop TSS information reporting.

13. The RAN node of claim 12, wherein the one or more processors are further configured to send a deactivation response message including an indication that the RAN node cannot stop TSS information reporting.

14. The RAN node of claim 1, wherein the RAN node is a decomposed RAN node.

15. The RAN node of claim 1, wherein the one or more processors are further configured to receive TSS subscription information associated with a user equipment (UE) connected to the RAN node.

16. The RAN node of claim 15, wherein the one or more processors are further configured to send clock quality information for receipt by the UE based at least in part on the TSS subscription information associated with the UE.

17. The RAN node of claim 16, wherein the clock quality information is sent via a Radio Resource Control (RRC) message.

18. The RAN node according to claim 16, wherein the clock quality information comprises one or more items of TSS information.

19. The RAN node of claim 16 , wherein the TSS subscription information associated with the UE indicates that the UE is to receive an indication of whether clock quality is acceptable, and the one or more processors are further configured to: determining clock quality acceptance criteria for said RAN node configuration, and determining whether the clock quality is acceptable based at least in part on the clock quality acceptance criteria, The clock quality information includes an indication of whether the clock quality is acceptable.

20. The RAN node of claim 16, wherein the TSS subscription information associated with the UE indicates that the UE is to receive one or more clock quality values.

21. The RAN node of claim 16, wherein the one or more processors are further configured to send the TSS subscription information associated with the UE to another RAN node.

22. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: sending time synchronization state (TSS) subscription information associated with the UE; as well as Clock quality information associated with a radio access network (RAN) node is received, wherein the clock quality information received by the UE is based at least in part on the TSS subscription information associated with the UE.

23. The UE of claim 22, wherein the clock quality information is received via a radio resource control (RRC) message. The UE according to claim 22 , wherein the clock quality information comprises one or more items of TSS information.

25. The UE of claim 22, wherein the TSS subscription information indicates that the UE will receive at least one of: one or more clock quality values, or an indication of whether clock quality is acceptable.

26. The UE of claim 22, wherein the one or more processors are further configured to: receiving a system information block (SIB) comprising an indication to perform a random access channel (RACH) procedure to transition from operating in an idle mode to a connected mode in association with receiving the clock quality information associated with the RAN node; and The RACH procedure is performed based at least in part on the indication and a randomized backoff time.

27. The UE of claim 26, wherein the one or more processors are further configured to receive an indication of the randomized backoff time, the indication of the randomized backoff time being received during operation in connected mode prior to operation in the idle mode.

28. The UE of claim 26, wherein the one or more processors are further configured to determine the randomized backoff time based at least in part on a UE network identifier associated with the UE.

29. A method of wireless communication performed by a Radio Access Network (RAN) node, the method comprising: receiving a time synchronization state (TSS) request message, the time synchronization state (TSS) request message including a request for the RAN node to send TSS information; as well as A TSS response message is sent after receiving the TSS request message.

30. A method of wireless communication performed by a user equipment (UE), the method comprising: sending time synchronization state (TSS) subscription information associated with the UE; as well as Clock quality information associated with a radio access network (RAN) node is received, wherein the clock quality information received by the UE is based at least in part on the TSS subscription information associated with the UE.

Images