EP4666746A1

EP4666746A1 - Timing resiliency and ultra-reliable low-latency communications

Info

Publication number: EP4666746A1
Application number: EP24709949.2A
Authority: EP
Inventors: Geetha Priya Rajendran; Shankar Krishnan; Prasad Reddy KADIRI; Sebastian Speicher; Sherif ELAZZOUNI
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-02-14
Filing date: 2024-01-30
Publication date: 2025-12-24
Also published as: WO2024173030A1; CN120660408A

Abstract

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

Description

TIMING RESILIENCY AND ULTRA-RELIABLE

LOW-LATENCY COMMUNICATIONS

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to India Patent Application No. 202341009722, filed on February 14, 2023, entitled “TIMING RESILIENCY AND ULTRARELIABLE LOW-LATENCY COMMUNICATIONS,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.

FIELD OF THE DISCLOSURE

[0002] Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for timing resiliency and ultra-reliable low-latency communications.

BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various 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, or the like). 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 (3 GPP).

[0004] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to a communication link from the network node to the UE, and “uplink” (or “UL”) refers to a 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, among other examples). [0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate on a municipal, national, regional, 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 the 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using 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, 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

[0006] A wireless communication system, such as a 5G system, may need to support timing resiliency and ultra-reliable low-latency communications (URLLC). One objective related to support of timing resiliency and URLLC is support for network timing synchronization status and reporting. Another objective related to support of timing resiliency and URLLC is support for adaptation of downlink and uplink scheduling based on RAN feedback for low-latency communication. Another objective related to support of timing resiliency and URLLC is support for interworking with a TSN deployed in a transport network. Some aspects described herein provide techniques and apparatuses for support of timing resiliency and URLLC.

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

[0008] 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 transmit TSS information. The method may include transmitting a TSS response message after receiving the TSS request message.

[0009] 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.

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

[0011] 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 including an indication of at least one of support of a core network node for BAT adaptation, a BAT window, or a burst periodicity range. The method may include transmitting a TSC assistance response message after transmitting 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 core network node. The method may include transmitting a first message including a first talker and listener (TL) container that includes TL information associated with a time sensitive network (TSN) node. The method may include receiving a second message including a second TL container that includes TL information associated with a RAN node.

[0013] 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 that includes TL information associated with a TSN node. The method may include transmitting a second message including a second TL container that includes TL information associated with the RAN node.

[0014] Some aspects described herein relate to a core network node for wireless communication. 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 transmit a TSS request message associated with a RAN node, the TSS request message including a request for the RAN node to transmit 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 transmitting the TSS request message.

[0015] Some aspects described herein relate to a RAN node for wireless communication.

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 transmit TSS information. The one or more processors may be configured to transmit a TSS response message after receiving the TSS request message.

[0016] Some aspects described herein relate to a 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 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.

[0017] Some aspects described herein relate to a core network node for wireless communication. 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 transmit a TSC assistance request message including an indication of at least one of support for BAT adaptation, a BAT window, or a burst periodicity range. The one or more processors may be configured to receive a TSC assistance response message after transmitting the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset. [0018] Some aspects described herein relate to a RAN node for wireless communication. 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 including an indication of at least one of support of a core network node for BAT adaptation, a BAT window, or a burst periodicity range. The one or more processors may be configured to transmit a TSC assistance response message after transmitting 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 core network node for wireless communication. 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 transmit a first message including a first TL container that includes 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 that includes TL information associated with a RAN node.

[0020] Some aspects described herein relate to a RAN node for wireless communication. 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 that includes TL information associated with a TSN node. The one or more processors may be configured to transmit a second message including a second TL container that includes TL information associated with the RAN node. [0021] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a core network node. The set of instructions, when executed by one or more processors of the core network node, may cause the core network node to transmit a TSS request message associated with a RAN node, the TSS request message including a request for the RAN node to transmit TSS information to the core network node. The set of instructions, 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 transmitting the TSS request message.

[0022] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a RAN node. The set of instructions, when executed by one or more processors of the RAN node, may cause the RAN to receive a TSS request message including a request for the RAN node to transmit TSS information. The set of instructions, when executed by one or more processors of the RAN node, may cause the RAN to transmit a TSS response message after receiving the TSS request message.

[0023] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, 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 to transition from operation in an idle mode in association with receiving clock quality information associated with a RAN node. The set of instructions, when executed by one or more processors of the UE, may cause the UE to perform the RACH procedure based at least in part on the indication and a randomized backoff time.

[0024] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a core network node. The set of instructions, when executed by one or more processors of the core network node, may cause the core network node to transmit a TSC assistance request message including an indication of at least one of support for BAT adaptation, a BAT window, or a burst periodicity range. The set of instructions, 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 transmitting the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0025] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a RAN. The set of instructions, when executed by one or more processors of the RAN node, may cause the RAN to receive a TSC assistance request message including an indication of at least one of support of a core network node for BAT adaptation, a BAT window, or a burst periodicity range. The set of instructions, when executed by one or more processors of the RAN node, may cause the RAN to transmit a TSC assistance response message after transmitting 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 that stores a set of instructions for wireless communication by a core network node. The set of instructions, when executed by one or more processors of the core network node, may cause the core network node to transmit a first message including a first TL container that includes TL information associated with a TSN node. The set of instructions, 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 that includes TL information associated with a RAN node.

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

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

[0029] 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 transmit TSS information. The apparatus may include means for transmitting a TSS response message after receiving the TSS request message.

[0030] 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 operation 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.

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

[0032] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a TSC assistance request message including an indication of at least one of support of a core network node for BAT adaptation, a BAT window, or a burst periodicity range. The apparatus may include means for transmitting a TSC assistance response message after transmitting 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 transmitting a first message including a first TL container that includes TL information associated with a TSN node. The apparatus may include means for receiving a second message including a second TL container that includes TL information associated with a RAN node.

[0034] 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 that includes TL information associated with a TSN node. The apparatus may include means for transmitting a second message including a second TL container that includes TL information associated with apparatus.

[0035] 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.

[0036] Some aspects described herein relate to a 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 transmit 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.

[0037] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit TSS subscription information associated with the UE. The set of instructions, 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.

[0038] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for 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.

[0039] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

[0040] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.

[0041] While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-modulecomponent based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, rctail/purchasing devices, medical devices, and/or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components. Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers). It is intended that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.

BRIEF DESCRIPTION OF THE DRAWINGS

[0042] So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

[0043] Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0044] Fig. 2 is a diagram illustrating an example of a network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0045] Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

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

[0047] Figs. 5-9 are diagrams illustrating examples associated with network timing synchronization status and reporting, in accordance with the present disclosure.

[0048] Fig. 10 is a diagram illustrating an example associated with adaptation of downlink and uplink scheduling based on radio access network (RAN) feedback for low-latency communication, in accordance with the present disclosure.

[0049] Fig. 11 is a diagram illustrating an example associated with interworking with a time sensitive network (TSN) deployed in a transport network, in accordance with the present disclosure.

[0050] Fig. 12 is a diagram illustrating an example process performed, for example, by a core network node, in accordance with the present disclosure.

[0051] Fig. 13 is a diagram illustrating an example process performed, for example, by a RAN node, in accordance with the present disclosure.

[0052] Fig. 14 is a diagram illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

[0053] Fig. 15 is a diagram illustrating an example process performed, for example, by a core network node, in accordance with the present disclosure. [0054] Fig. 16 is a diagram illustrating an example process performed, for example, by a RAN node, in accordance with the present disclosure.

[0055] Fig. 17 is a diagram illustrating an example process performed, for example, by a core network node, in accordance with the present disclosure.

[0056] Fig. 18 is a diagram illustrating an example process performed, for example, by a RAN node, in accordance with the present disclosure.

[0057] Fig. 19 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

[0058] Fig. 20 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

[0059] Fig. 21 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

DETAILED DESCRIPTION

[0060] Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than 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 a claim. [0061] Several aspects of telecommunication systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. [0062] While aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

[0063] Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as a network node 110a, a network node 110b, a network node 110c, and a network node 1 lOd), a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), and/or other entities. A network node 110 is a network node that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated 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, a 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 among 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)).

[0064] In some examples, a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU. In some examples, a network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and/or one or more DUs. A 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 transmission reception point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and/or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.

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

[0066] In some aspects, the terms “base station” or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, “base station” or “network node” may refer to a CU, a DU, an 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 terms “base station” or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110. In some aspects, the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity 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 duplicate performance of at least a portion of the function, and the terms “base station” or “network node” may refer to any one or more of those different devices. In some aspects, the terms “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 terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

[0067] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and send a transmission of the 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. In the example shown in Fig. 1, the network node 1 lOd (e.g., a relay network node) may communicate with the network node 110a (e.g., a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. 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, or the like.

[0068] The wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, or the like. 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, macro network nodes may have a high transmit power level (e.g., 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0069] A network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these 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 communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0070] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit. A UE 120 may be a cellular phone (e.g., a smart phone), 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, 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 a smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicular 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 that is configured to communicate via a wireless or wired medium.

[0071] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Intemet-of-Things (loT) devices, and/or may be implemented as NB-IoT (narrowband loT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

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

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

[0074] Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0075] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 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.

[0076] With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or 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 techniques described herein are applicable to those modified frequency ranges.

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

[0078] In some aspects, a UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication 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 an 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, the communication manager 140 may perform one or more other operations described herein.

[0079] Additionally, or alternatively, as described in more detail elsewhere herein, the communication manager 140 may transmit TSS subscription information associated with the UE 120; and receive 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. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

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

[0081] Additionally, or alternatively, as described in more detail elsewhere herein, the communication manager 150 may receive a first message including a first talker and listener (TL) container that includes TL information associated with a time sensitive network (TSN) node; and transmit a second message including a second TL container that includes TL information associated with the RAN node. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0082] As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

[0083] Fig. 2 is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with 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, a 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 that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.

[0084] At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple -input multiple -output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if 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 a modem 232. Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream 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.

[0085] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the 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 a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem 254 may use a 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 modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A 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 a controller/processor 280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RS SI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0086] 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.

[0087] One or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of Fig. 2.

[0088] 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 that include 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 precoded by a TX MIMO processor 266 if applicable, further processed by the modems 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 the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 5-21). [0089] At the network node 110, the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 5-21).

[0090] The controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component(s) of Fig. 2 may perform one or more techniques associated with timing resiliency and ultra-reliable low-latency communications (URLLC), as described in more detail elsewhere herein. For example, the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component(s) of Fig. 2 may perform or direct operations of, for example, process 1300 of Fig. 13, process 1400 of Fig. 14, process 1600 of Fig. 16, process 1800 of Fig. 18, and/or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and/or the 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 compiling, converting, and/or interpreting) by one or more processors of the network node 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the network node 110 to perform or direct operations of, for example, process 1300 of Fig. 13, process 1400 of Fig. 14, process 1600 of Fig. 16, process 1800 of Fig. 18, and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

[0091] In some aspects, a RAN node (e.g., a network node 110) includes means for receiving a TSS request message including a request for the RAN node to transmit TSS information; and/or means for transmitting a TSS response message after receiving the TSS request message. [0092] In some aspects, a RAN node (e.g., a network node 110) includes means for receiving a TSC assistance request message including an indication of at least one of support of a core network node for BAT adaptation, a BAT window, or a burst periodicity range; and/or means for transmitting a TSC assistance response message after transmitting the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset. [0093] In some aspects, a RAN node (e.g., a network node 110) includes means for receiving a first message including a first TL container that includes TL information associated with a TSN node; and/or means for transmitting a second message including a second TL container that includes TL information associated with the RAN node.

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

[0095] In some aspects, a 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. [0096] In some aspects, a 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. The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.

[0097] While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions 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. [0098] As indicated above, Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.

[0099] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated 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, among other examples), or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0100] An aggregated base station (e.g., an aggregated 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 disaggregated base station (e.g., a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among 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 distributed throughout one or multiple other network nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

[0101] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored 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 communication systems by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0102] Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both). A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through Fl interfaces. 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 simultaneously served by multiple RUs 340.

[0103] Each of the units, including the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with 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 providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0104] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with 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 (for example, Central Unit - User Plane (CU-UP) functionality), control plane functionality (for example, Central Unit - Control Plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.

[0105] Each DU 330 may correspond to a logical unit that includes one or more base station functions to control 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 high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3 GPP. In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

[0106] Each RU 340 may implement lower-layer functionality. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 3 GPP), such as a lower layer functional split. In such an architecture, each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120. In some implementations, real-time and non-real- time aspects of control and user plane communication with the RU(s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture. [0107] The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an 01 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective 01 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

[0108] The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy -based guidance of applications/features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-realtime control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

[0109] In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 325, the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an 01 interface) or via creation of RAN management policies (such as Al interface policies).

[0110] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

[0111] Fig. 4 is a diagram of an example 400 of a core network 405 configured to provide network slicing. As shown in Fig. 4, example 400 may include a UE 120, a wireless communication network 100, and a core network 405. Devices and/or networks of example 400 may interconnect via wired connections, wireless connections, or a combination thereof.

[0112] The wireless communication network 100 may support, for example, a cellular RAT. The network 100 may include one or more network nodes, such as base stations (e.g., base transceiver stations, radio base stations, node Bs, eNodeBs (eNBs), gNodeBs (gNBs), base station subsystems, cellular sites, cellular towers, access points, TRPs, radio access nodes, macrocell base stations, microcell base stations, picocell base stations, femtocell base stations, or similar types of devices) and other network nodes that can support wireless communication for the UE 120. The network 100 may transfer 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 that cover geographic areas.

[0113] In some aspects, the wireless communication network 100 may perform scheduling and/or resource management for the UE 120 covered by the network 100 (e.g., the UE 120 covered by a cell provided by the wireless communication network 100). In some aspects, the wireless communication network 100 may be controlled or coordinated by a network controller (e.g., network controller 130 of Fig. 1), which may perform load balancing and/or network-level configuration, among other examples. As described above in connection with Fig. 1, the network controller may communicate with the network 100 via a wireless or wireline backhaul. In some aspects, the network 100 may include a network controller, a self-organizing network (SON) module or component, or a similar module or component. Accordingly, the network 100 may perform network control, scheduling, and/or network management functions (e.g., for uplink, downlink, and/or sidelink communications of the UE 120 covered by the network 100). [0114] In some aspects, the core network 405 may include an example functional architecture in which systems and/or methods described herein may be implemented. For example, the core network 405 may include an example architecture of a fifth generation (5G) next generation (NG) core network included in a 5G wireless telecommunications system. Although the example architecture of the core network 405 shown in Fig. 4 may be an example of a servicebased architecture, in some aspects, the core network 405 may be implemented as a referencepoint architecture and/or a 4G core network, among other examples.

[0115] As shown in Fig. 4, the core network 405 may include a number of functional elements. The functional elements may include, for example, a network slice selection function (NSSF) 410, a network exposure 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, among other examples. These functional elements may be communicatively connected via a message bus 460. Each of the functional elements shown in Fig. 4 may be implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more of the functional elements may be implemented on physical devices, such as an access point, a base station, and/or a gateway, among other examples. In some implementations, one or more of the functional elements may be implemented on a computing device of a cloud computing environment.

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

[0117] The NSSF 410 may determine a set of network slice policies to be applied at the wireless communication network 100. For example, the NSSF 410 may apply one or more UE route 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 route selection description (RSD) to the DNN field included in a traffic descriptor selected by the UE 120. By providing network slicing, the NSSF 410 allows an operator to deploy multiple substantially independent end-to-end networks potentially with the same infrastructure. In some implementations, each slice may be customized for different services.

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

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

[0120] 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 examples. In some aspects, the PCF 430 may include one or more URSP rules used by the NSSF 410 to select network slice instances for the UE 120.

[0121] The AF 435 may include one or more devices that support application influence on traffic routing, access to the NEF 415, and/or policy control, among other examples.

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

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

[0124] Additionally, or alternatively, as described in more detail elsewhere herein, the communication manager 170 may transmit a TSC assistance request message including an indication of at least one of support for BAT adaptation, a BAT window, or a burst periodicity range; and receive a TSC assistance response message after transmitting the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

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

[0126] Additionally, or alternatively, the communication manager 170 may perform one or more other operations described herein.

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

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

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

[0130] The means for the core network node to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246. [0131] The SMF 445 may include one or more devices that support the establishment, modification, and release of communication sessions in the wireless telecommunications system. For example, the SMF 445 may configure traffic steering policies at the UPF 450 and/or enforce user equipment IP address allocation and policies, among other examples. In some aspects, the SMF 445 may provision the network slice instances selected by the NSSF 410 for the UE 120.

[0132] The UPF 450 may include one or more devices that serve as an anchor point for intraRAT and/or interRAT mobility. In some aspects, the UPF 450 may apply rules to packets, such as rules pertaining to packet routing, traffic reporting, and/or handling user plane QoS, among other examples.

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

[0134] The message bus 460 may be a logical and/or physical communication structure for communication among the functional elements. Accordingly, the message bus 460 may permit communication between two or more functional elements, whether logically (e.g., using one or more application programming interfaces (APIs), among other examples) and/or physically (e.g., using one or more wired and/or wireless connections).

[0135] The number and arrangement of devices and networks shown in Fig. 4 are provided as an example. In practice, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown in Fig. 4. Furthermore, two or more devices shown in Fig. 4 may be implemented within a single device, or a single device shown in Fig. 4 may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of example 400 may perform one or more functions described as being performed by another set of devices of example environment 400.

[0136] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.

[0137] A wireless communication system, such as a 5G system, may need to support timing resiliency and URLLC.

[0138] One objective related to support of timing resiliency and URLLC is support for network timing synchronization status and reporting. For example, an AMF function (e.g., AMF 440) may need to provide clock quality reporting control information to a RAN node (e.g., a network node 110), and the RAN node may need to report clock quality information to a UE (e.g., a UE 120) based on the clock quality reporting control information. Further, the UE may need to be capable of determining 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.

[0139] Examples of clock quality information include information associated with a synchronization state (e.g., synchronized to a primary reference clock or in hold-over state), traceability information (e.g., to coordinated universal time (UTC)), accuracy information (e.g., in nanoseconds per millisecond (ns/ms)), or frequency stability information. In practice, clock quality can change due to, for example, a malfunction (e.g., due to a failure of time distribution via a transport network) or a targeted attack (e.g., due to global navigation satellite system (GNSS) jamming/spoofing). Further, in some systems, an operator may desire to control which UEs receive clock quality information, and clock quality information can be delivered as individual metrics or implicitly (e.g., a RAN node can indicate whether a clock quality satisfies 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).

[0140] Another objective related to support of timing resiliency and URLLC is support for adaptation of downlink and uplink scheduling based on RAN feedback for low-latency communication. Here, RAN enhancements may be needed in order for an application to adapt scheduling based on RAN feedback (e.g., feedback regarding burst arrival time, periodicity, or the like) for low-latency communication.

[0141] Another objective related to support of timing resiliency and URLLC is support for interworking with a TSN deployed in a transport network.

[0142] Some aspects described herein provide techniques and apparatuses for support of timing resiliency and URLLC.

[0143] In some aspects, a core network node (e.g., an AMF 440) may transmit, and a RAN node (e.g., a network node 110) may receive, a TSS request message associated with the RAN node. The TSS request message may include a request for the RAN node to transmit TSS information to the core network node. The RAN node may transmit, and the core network node may receive, a TSS response message associated with the RAN node after transmitting the TSS request message.

[0144] In some aspects, a UE (e.g., a UE 120) may receive 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 (e.g., a network node 110). The UE may then perform the RACH procedure based at least in part on the indication and a randomized backoff time. [0145] In some aspects, a core network node (e.g., an AMF 440) may transmit, and a RAN node (e.g., a network node 110) may receive, a TSC assistance request message including an indication of at least one of support for BAT adaptation, a BAT window, or a burst periodicity range. The RAN node may transmit, and the core network node may receive, a TSC assistance response message after transmitting the TSC assistance request message. The TSC assistance response message may include at least an indication of a BAT offset.

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

[0147] Figs. 5-9 are diagrams illustrating examples associated with network timing synchronization status and reporting, in accordance with aspects of the present disclosure. In the examples shown in Figs. 5-8, a core network node, such as an AMF 440, and a RAN node, such as a network node 110 or a disaggregated network node 110, perform operations associated with network timing synchronization status and reporting.

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

[0149] As shown at reference 504, the AMF 440 may transmit, and the RAN node (e.g., the network node 110) may receive a TSS information request message associated with the network node 110. In some aspects, the TSS information request message includes a request for the network node 110 to transmit TSS information (e.g., to the AMF 440, to a UE 120, or the like). In some aspects, the TSS information request message may be transmitted and received on an NGAP interface.

[0150] 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 trigger event (e.g., an event that upon detection is trigger network node 110 to transmit 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, in the case of a clock quality threshold, if the network node 110 detects that a clock quality satisfies the clock quality threshold (e.g., that a 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 paratemrs associated with TSS information reporting may be triggered in another manner. For example, in some aspects, a reporting trigger event associated with TSS information reporting may be configured on the network node 110 via operations and management (0 AM).

[0151] As shown at reference 506, the network node 110 may transmit, and the AMF 440 may receive, a TSS information response message associated with the network node 110 after the AMF transmits the TSS information request message. In some aspects, the TSS information response message may be transmitted and received on the NGAP interface.

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

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

[0154] In some aspects, as shown at reference 510, the AMF 440 may transmit, and the network node 110 may receive, an activation message including an indication that the network node 110 is to start 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 transmitted and received on an NGAP interface.

[0155] In some aspects, as shown at reference 512, the network node 110 may transmit, and the AMF 440 may receive, an activation failure indicating that the network node 110 does not support TSS information reporting as indicated in the activation message or indicates a partial failure associated with 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, then the network node 110 may send a failure indication in response to the activation message.

[0156] In some aspects, as shown at reference 514, the network node 110 may transmit, and the AMF 440 may receive, TSS information associated with the network node 110. That is, the network node 110 may begin TSS information reporting in response to the activation message. In some aspects, the network node 110 may transmit the TSS information based at least in part on one or more parameters associated with TSS reporting (e.g., the network node 110 may begin 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 a synchronization state, a synchronization performance, a time source, a clock quality of a clock associated with the network node 110, a clock frequency stability, a clock accuracy, a parent time source, a clock traceability, or a list of cells for which the clock information is valid. In some aspects, the TSS information may be transmitted and received on an NGAP interface.

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

[0158] In some aspects, the network node 110 may be an aggregated network node 110, as illustrated in example 500.

[0159] Alternatively, the network node 110 may be a disaggregated network node, an example of which is shown in example 600 of Fig. 6. In example 600, the AMF 440 communicates with a CU-CP component of the network node 110 (e.g., CU 310 (CU-CP)) via an NGAP interface. As shown in example 600, upon receiving a message from the AMF 440, the CU 310 (CU-CP) forwards the message to the DU component of the network node 110 (DU 330) and to the CU-UP component of the network node 110 (CU 310 (CU-UP)). As one particular 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 an F1AP interface and to the CU 310 (CU-UP) via an E1AP interface.

[0160] 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 and forwards the messages to the AMF 440. As one particular example, upon receiving a first TSS report from the CU 310 (CU-UP) via an El AP interface and a second TSS report from the DU 330 via an F1AP interface, the CU 310 (CU-CP) may combine the TSS reports and forward the combined TSS reports to the AMF 440 via an NGAP interface.

[0161] Alternative examples associated with TSS information reporting are illustrated Figs. 7 and 8. As shown in example 700 of Fig. 7, at reference 702, the AMF 440 may register for TSS with the TSCTSF 455. In some aspects, registering for TSS triggers the AMF 440 to perform operations associated with time synchronization and status reporting described below.

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

[0163] In some aspects, the TSS initiation request message includes an indication that the network node 110 is to start 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 can 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).

[0164] As shown at reference 706, the network node 110 may transmit, and the AMF 440 may receive, a TSS initiation response message associated with the network node 110 after the AMF 440 transmits the TSS initiation request message. In some aspects, the TSS initiation response message may be transmitted and received on the NGAP interface.

[0165] 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 a quality of a clock of the network node 110 used in support of wireless communication. The clock quality information may include, for example, an indication of a synchronization state, a synchronization performance, a time source, a clock quality, a clock frequency stability, a clock accuracy, a parent time source, a clock traceability, or a list of cells for which the clock information is valid, among other examples.

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

[0167] In some aspects, as shown at reference 710, the network node 110 may transmit, and the AMF 440 may receive, TSS information associated with the network node 110. That is, the network node 110 may begin TSS information reporting in response to the TSS initiation request. In some aspects, the network node 110 may transmit the TSS information based at least in part on one or more parameters associated with TSS reporting (e.g., the network node 110 may begin 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 a synchronization state, a synchronization performance, a time source, a clock quality of a clock associated with the network node 110, a clock frequency stability, a clock accuracy, a parent time source, a clock traceability, or a list of cells for which the clock information is valid. In some aspects, the TSS information may be transmitted and received on an NGAP interface. [0168] In some aspects, as shown at reference 712, the AMF 440 may transmit, and the network node 110 may receive, a termination command including an indication that the network node 110 is to stop TSS information reporting.

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

[0170] In some aspects, the network node 110 may be an aggregated network node 110, as illustrated in example 700.

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

[0172] As further shown, the 310 CU-CP 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 and forwards the messages to the AMF 440. As one particular example, upon receiving a first TSS report from the CU 310 (CU-UP) via an El AP interface and a second TSS report from the DU 330 via an F1AP interface, the CU 310 (CU-CP) may combine the TSS reports and forward to the AMF 440.

[0173] Fig. 9 is a diagram illustrating an example operation of a UE 120 with respect to timing synchronization status and reporting. In example 900 shown in Fig. 9 a RAN node, such as a network node 110 and a UE 120 perform operations associated with network timing synchronization status and reporting.

[0174] As shown at reference 902, the UE 120 may transmit, and the AMF 440 may receive, TSS subscription information associated with the UE 120. The TSS subscription information may include, for example, an indication of whether the UE 120 is authorized to receive clock quality information associated with the network node 110, information indicating a format in which UE 120 is to be provided with clock quality information, or the like. For example, the TSS subscription information may indicate one or more items of TSS information (e.g., actual clock quality values, actual values of one or more items of TSS related information, or the like) that are to be included in clock quality information provided to the UE 120. As another example, the TSS subscription information may indicate that the UE 120 is to receive an indication of whether a clock quality is acceptable (e.g., a binary indication of whether clock quality is to be accepted by the UE 120, rather than or in addition to one or more items of TSS information being provided to the UE 120).

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

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

[0177] As shown at reference 906, the network node 110 may detect a trigger to transmit 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 upon detection triggers the network node 110 to transmit clock quality information to the UE 120). In one example, the event-based trigger may be a determination that a clock quality fails to satisfy a clock quality threshold. Here, if the network node 110 detects that a clock quality satisfies the clock quality threshold (e.g., that a clock quality is less than the threshold), then the network node 110 may be triggered to transmit 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 transmit clock quality information to the UE 120 on a periodic basis)

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

[0179] As shown at reference 910, the UE 120, if operating in idle mode, may perform the 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 so as to reduce PRACH collisions that would result from multiple UEs 120 concurrently performing the RACH procedure.

[0180] In some aspects, the UE 120 may be configured with a wait time between a time of receiving the SIB (e.g., SIB9 indicating availability of TSS information to be provided to the UE 120) and a time at which to perform the RACH procedure. That is, the UE 120 may, in some aspects, receive an indication of the randomized backoff time during operation of the UE 120 in a connected mode (e.g., prior to operation in the idle mode). In some aspects, the UE 120 may receive the indication of the randomized backoff time via RRC signaling.

Additionally, or alternatively, the UE 120 may receive the indication of the randomized backoff time via NAS layer signaling.

[0181] In some aspects, the UE 120 may determine the randomized backoff time. For example, to obtain the randomized backoff time (and minimize collision probability), the UE 120 may in some aspect use UE network identifier as a seed to generate the randomized backoff time before performing the RACH procedure. This can provide randomization of backoff times across UEs 120 without relying on a large backoff window that could otherwise cause access delay. 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 other examples.

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

[0183] As shown at reference 912, the network node 110 may transmit, and the UE 120 may receive (e.g., after transitioning to the connected mode, if needed), the clock quality information associated with the network node 110. In some aspects, the clock quality information may include one or more items of TSS information, such as information associated with a synchronization state, a clock frequency stability, a clock accuracy, a parent time source, a clock traceability, or a list of cells for which the TSS information is valid, among other examples. 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. [0184] In some aspects, the clock quality information transmitted by the network node 110 to the UE 120 is based at least in part on the TSS subscription information associated with the UE 120. For example, the clock quality information transmitted by the network node 110 may include one or more items of TSS information as specified by the TSS subscription information associated with the UE 120. As another example, if the TSS subscription information associated with the UE 120 indicates that clock quality information provided to the UE 120 is to include an indication of whether the clock quality is acceptable, then the network node 110 determine clock quality acceptance criteria configured for the 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 a clock quality can be evaluated. In some aspects, the clock quality acceptance criteria can be configured for the network node 110 (e.g., by a core network device). In this example, the network node 110 may then transmit clock quality information including an indication of whether the clock quality is be acceptable (e.g., an indication of whether the clock quality satisfied the clock quality acceptance criteria). In some aspects, the network node 110 may transmit, and the UE 120 may receive, the clock quality information via an RRC message.

[0185] As indicated above, Figs. 5-9 are provided as examples. Other examples may differ from what is described with regard to Figs. 5-9.

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

[0187] As shown at reference 1002, the AMF 440 may transmit, and the network node 110 may receive, a TSC assistance request message including an indication of at least one of support for BAT adaptation, 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 adaptation of downlink or uplink scheduling by indicating support for BAT adaptation, 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) in a packet data unit (PDU) session resource setup or modify request transfer. In some aspects, the TSC assistance request message may be communicated over an NGAP interface.

[0188] As shown at reference 1004, the network node 110 may transmit, and the AMF 440 may receive, a 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 a start of the BAT window. In some aspects, the TSC assistance response message includes an indication of a burst periodicity within the burst periodicity range.

[0189] In one example, if the TSC assistance request message indicates a BAT window and a burst periodicity range, then 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 setup/modify response).

[0190] In some aspects, the network node 110 may transmit an indication of the BAT offset based at least in part on the network node 110 being unable to satisfy one or more TSC characteristics indicated in the TSC assistance request message. For example, in some aspects, the network node 110 may indicate a BAT offset if the network node 110 is not able to meet a TSC characteristic for downlink or uplink indicated in a PDU session resource modify indication.

[0191] Fig. 11 is a diagram illustrating an example associated with interworking with a TSN deployed in a transport network, in accordance with aspects of the present disclosure. In example 1100 a core network node, such as an AMF 440, and a RAN node, such as a network node 110 or a disaggregated network node 110, perform operations associated with interworking with a TSN deployed in a transport network.

[0192] As shown at reference 1102, the AMF 440 may transmit, and the network node 110 may receive, a first message including a first TL container that includes TL information associated with a 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, an SMF 445 or the TSN node.

[0193] As shown at reference 1104, the network node 110 may transmit, and the AMF 440 may receive, a second message including a second TL container that includes 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 transmit the TL information associated with the network node 110 to, for example, an SMF 445 or the TSN node.

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

[0195] Fig. 12 is a diagram illustrating an example process 1200 performed, for example, by a core network node, in accordance with the present disclosure. Example process 1200 is an example where the core network node (e.g., AMF 440) performs operations associated with timing resiliency and URLLC.

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

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

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

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

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

[0201] 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. [0202] In a fourth aspect, alone or in combination with one or more of the first through third aspects, process 1200 includes receiving the TSS information associated with the RAN node. [0203] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the TSS information includes information associated with at least one of a synchronization state, a clock frequency stability, a clock accuracy, a parent time source, a clock traceability, or a list of cells for which the TSS information is valid.

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

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

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

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

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

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

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

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

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

[0213] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the RAN node is a disaggregated RAN node.

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

[0215] Although Fig. 12 shows example blocks of process 1200, in some aspects, process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0216] Fig. 13 is a diagram illustrating an example process 1300 performed, for example, by a RAN node, in accordance with the present disclosure. Example process 1300 is an example where the RAN node (e.g., network node 110) performs operations associated with timing resiliency and URLLC.

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

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

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

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

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

[0222] 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. [0223] In a fourth aspect, alone or in combination with one or more of the first through third aspects, process 1300 includes transmitting the TSS information associated with the RAN node. [0224] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the TSS information includes information associated with at least one of a synchronization state, a clock frequency stability, a clock accuracy, a parent time source, a clock traceability, or a list of cells for which the TSS information is valid. [0225] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the TSS information is transmitted based at least in part on a detection of a reporting trigger event associated with TSS information reporting.

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

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

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

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

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

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

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

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

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

[0235] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, process 1300 includes transmitting a deactivation response message including an indication that the RAN node is unable to stop TSS information reporting.

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

[0238] In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, process 1300 includes transmitting clock quality information for reception by the UE based at least in part on the TSS subscription information associated with the UE, wherein the clock quality information is transmitted via an RRC message.

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

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

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

[0242] Although Fig. 13 shows example blocks of process 1300, in some aspects, process 1300 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 13. Additionally, or alternatively, two or more of the blocks of process 1300 may be performed in parallel.

[0243] Fig. 14 is a diagram illustrating an example process 1400 performed, for example, by a UE, in accordance with the present disclosure. Example process 1400 is an example where the UE (e.g., UE 120) performs operations associated with timing resiliency and URLLC.

[0244] As shown in Fig. 14, in some aspects, process 1400 may include transmitting TSS subscription information associated with the UE (block 1410). For example, the UE (e.g., using transmission component 2104 and/or communication manager 2106, depicted in Fig. 21) may transmit TSS subscription information associated with the UE, as described above.

[0245] As further shown in Fig. 14, 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 the TSS subscription information associated with the UE (block 1420). For example, the UE (e.g., using reception component 2102 and/or communication manager 2106, depicted in Fig. 21) may 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, as described above. [0246] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

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

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

[0249] 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 a clock quality is acceptable.

[0250] In a fourth aspect, alone or in combination with one or more of the first through third aspects, process 1400 includes receiving a SIB including an indication to perform a RACH procedure to transition from operation in an 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.

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

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

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

[0254] Although Fig. 14 shows example blocks of process 1400, in some aspects, process 1400 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 14. Additionally, or alternatively, two or more of the blocks of process 1400 may be performed in parallel.

[0255] Fig. 15 is a diagram illustrating an example process 1500 performed, for example, by a core network node, in accordance with the present disclosure. Example process 1500 is an example where the core network node (e.g., AMF 440) performs operations associated with timing resiliency and URLLC.

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

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

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

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

[0260] In a second aspect, alone or in combination with the first aspect, the TSC assistance response message includes an indication of a burst periodicity within the burst periodicity range. [0261] Although Fig. 15 shows example blocks of process 1500, in some aspects, process 1500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 15. Additionally, or alternatively, two or more of the blocks of process 1500 may be performed in parallel.

[0262] Fig. 16 is a diagram illustrating an example process 1600 performed, for example, by a RAN node, in accordance with the present disclosure. Example process 1600 is an example where the RAN node (e.g., network node 110) performs operations associated with timing resiliency and URLLC.

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

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

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

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

[0267] In a second aspect, alone or in combination with the first aspect, the TSC assistance response message includes an indication of a burst periodicity within the burst periodicity range. [0268] In a third aspect, alone or in combination with one or more of the first and second aspects, the BAT offset is transmitted based at least in part on the RAN node being unable to satisfy one or more TSC characteristics indicated in the TSC assistance request message.

[0269] Although Fig. 16 shows example blocks of process 1600, in some aspects, process 1600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 16. Additionally, or alternatively, two or more of the blocks of process 1600 may be performed in parallel.

[0270] Fig. 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 where the core network node (e.g., AMF 440) performs operations associated with timing resiliency and URLLC.

[0271] As shown in Fig. 17, in some aspects, process 1700 may include transmitting a first message including a first TL container that includes TL information associated with a TSN node (block 1710). For example, the core network node (e.g., using transmission component 1904 and/or communication manager 1906, depicted in Fig. 19) may transmit a first message including a first TL container that includes TL information associated with a TSN node, as described above.

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

[0273] Process 1700 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein. [0274] In a first aspect, the TL information associated with the TSN node includes at least one of a time aware offset or an interface configuration.

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

[0276] Although Fig. 17 shows example blocks of process 1700, in some aspects, process 1700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 17. Additionally, or alternatively, two or more of the blocks of process 1700 may be performed in parallel.

[0277] Fig. 18 is a diagram illustrating an example process 1800 performed, for example, by a RAN node, in accordance with the present disclosure. Example process 1800 is an example where the RAN node (e.g., network node 110) performs operations associated with timing resiliency and URLLC.

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

[0279] As further shown in Fig. 18, in some aspects, process 1800 may include transmitting a second message including a second TL container that includes TL information associated with the RAN node (block 1820). For example, the RAN node (e.g., using transmission component 2004 and/or communication manager 2006, depicted in Fig. 20) may transmit a second message including a second TL container that includes TL information associated with the RAN node, as described above.

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

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

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

[0283] Although Fig. 18 shows example blocks of process 1800, in some aspects, process 1800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 18. Additionally, or alternatively, two or more of the blocks of process 1800 may be performed in parallel. [0284] Fig. 19 is a diagram of an example apparatus 1900 for wireless communication, in accordance with the present disclosure. The apparatus 1900 may be a core network node (e.g., AMF 440), or a core network node may include the apparatus 1900. In some aspects, the apparatus 1900 includes a reception component 1902, a transmission component 1904, and/or a communication manager 1906, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager 1906 is the communication manager 170 described in connection with Fig. 4. As shown, the apparatus 1900 may communicate with another apparatus 1908, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 1902 and the transmission component 1904.

[0285] In some aspects, the apparatus 1900 may be configured to perform one or more operations described herein in connection with Figs. 5-11. Additionally, or alternatively, the apparatus 1900 may be configured to perform one or more processes described herein, such as process 1200 of Fig. 12, process 1500 of Fig. 15, process 1700 of Fig. 17, or a combination thereof. In some aspects, the apparatus 1900 and/or one or more components shown in Fig. 19 may include one or more components of the core network node described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 19 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the 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 stored in a non-transitory computer- readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0286] The reception component 1902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1908. The reception component 1902 may provide received communications to one or more other components of the apparatus 1900. In some aspects, the reception component 1902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1900. In some aspects, the reception component 1902 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the core network node described in connection with Fig. 2. In some aspects, the reception component 1902 and/or the transmission component 1904 may include or may be included in a network interface. The network interface may be configured to obtain and/or output signals for the apparatus 1900 via one or more communications links, such as a backhaul link, a midhaul link, and/or a fronthaul link.

[0287] The transmission 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 transmission component 1904 for transmission to the apparatus 1908. In some aspects, the transmission component 1904 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1908. In some aspects, the transmission component 1904 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the core network node described in connection with Fig.

2. In some aspects, the transmission component 1904 may be codocated with the reception component 1902 in a transceiver.

[0288] The communication manager 1906 may support operations of the reception component 1902 and/or the transmission component 1904. For example, the communication manager 1906 may receive information associated with configuring reception of communications by the reception component 1902 and/or transmission of communications by the transmission component 1904. Additionally, or alternatively, the communication manager 1906 may generate and/or provide control information to the reception component 1902 and/or the transmission component 1904 to control reception and/or transmission of communications. [0289] The transmission component 1904 may transmit a TSS request message associated with a RAN node, the TSS request message including a request for the RAN node to transmit TSS information to the core network node. The reception component 1902 may receive a TSS response message associated with the RAN node after transmitting the TSS request message.

[0290] The reception component 1902 may receive the TSS information associated with the RAN node.

[0291] The transmission component 1904 may transmit a termination command including an indication that the RAN node is to stop TSS information reporting.

[0292] The reception component 1902 may receive a termination command response including an indication that the RAN node is unable to stop TSS information reporting.

[0293] The transmission component 1904 may transmit an activation message including an indication that the RAN node is to start TSS information reporting.

[0294] The transmission component 1904 may transmit a deactivation message including an indication that the RAN node is to stop TSS information reporting. [0295] The reception component 1902 may receive a deactivation response message including an indication that the RAN node is unable to stop TSS information reporting. [0296] The transmission component 1904 may transmit TSS subscription information associated with a UE connected to the RAN node.

[0297] The transmission component 1904 may transmit a TSC assistance request message including an indication of at least one of support for BAT adaptation, a BAT window, or a burst periodicity range. The reception component 1902 may receive a TSC assistance response message after transmitting the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0298] The transmission component 1904 may transmit a first message including a first TL container that includes TL information associated with a TSN node. The reception component 1902 may receive a second message including a second TL container that includes TL information associated with a RAN node.

[0299] The number and arrangement of components shown in Fig. 19 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 19. Furthermore, two or more components shown in Fig. 19 may be implemented within a single component, or a single component shown in Fig. 19 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 19 may perform one or more functions described as being performed by another set of components shown in Fig. 19.

[0300] Fig. 20 is a diagram of an example apparatus 2000 for wireless communication, in accordance with the present disclosure. The apparatus 2000 may be a RAN node (e.g., a network node 110), or a RAN node may include the apparatus 2000. In some aspects, the apparatus 2000 includes a reception component 2002, a transmission component 2004, and/or a communication manager 2006, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager 2006 is the communication manager 150 described in connection with Fig. 1. As shown, the apparatus 2000 may communicate with another apparatus 2008, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 2002 and the transmission component 2004.

[0301] In some aspects, the apparatus 2000 may be configured to perform one or more operations described herein in connection with Figs. 5-11. Additionally, or alternatively, the apparatus 2000 may be configured to perform one or more processes described herein, such as process 1300 of Fig. 13, process 1600 of Fig. 16, process 1800 of Fig. 18, or a combination thereof. In some aspects, the apparatus 2000 and/or one or more components shown in Fig. 20 may include one or more components of the RAN node described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 20 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the 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 instmctions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0302] The reception component 2002 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 2008. The reception component 2002 may provide received communications to one or more other components of the apparatus 2000. In some aspects, the reception component 2002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 2000. In some aspects, the reception component 2002 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the RAN node described in connection with Fig. 2.

[0303] The transmission 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 transmission component 2004 for transmission to the apparatus 2008. In some aspects, the transmission component 2004 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 2008. In some aspects, the transmission component 2004 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the RAN node described in connection with Fig. 2. In some aspects, the transmission component 2004 may be co-located with the reception component 2002 in a transceiver.

[0304] The communication manager 2006 may support operations of the reception component 2002 and/or the transmission component 2004. For example, the communication manager 2006 may receive information associated with configuring reception of communications by the reception component 2002 and/or transmission of communications by the transmission component 2004. Additionally, or alternatively, the communication manager 2006 may generate and/or provide control information to the reception component 2002 and/or the transmission component 2004 to control reception and/or transmission of communications. [0305] The reception component 2002 may receive a TSS request message including a request for the RAN node to transmit TSS information. The transmission component 2004 may transmit a TSS response message after receiving the TSS request message.

[0306] The transmission component 2004 may transmit the TSS information associated with the RAN node.

[0307] The reception component 2002 may receive a termination command including an indication to stop TSS information reporting.

[0308] The transmission component 2004 may transmit a termination command response including an indication that the RAN node is unable to stop TSS information reporting.

[0309] The reception component 2002 may receive an activation message including an indication to start TSS information reporting.

[0310] The reception component 2002 may receive a deactivation message including an indication to stop TSS information reporting.

[0311] The transmission component 2004 may transmit a deactivation response message including an indication that the RAN node is unable to stop TSS information reporting.

[0312] The reception component 2002 may receive TSS subscription information associated with a UE connected to the RAN node.

[0313] The transmission component 2004 may transmit clock quality information for reception by the UE based at least in part on the TSS subscription information associated with the UE, wherein the clock quality information is transmitted via an RRC message.

[0314] The communication manager 2006 may determine whether a 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.

[0315] The transmission component 2004 may transmit the TSS subscription information associated with the UE to another RAN node.

[0316] The reception component 2002 may receive a TSC assistance request message including an indication of at least one of support of a core network node for BAT adaptation, a BAT window, or a burst periodicity range. The transmission component 2004 may transmit a TSC assistance response message after transmitting the TSC assistance request message, the TSC assistance response message including an indication of a BAT offset.

[0317] The reception component 2002 may receive a first message including a first TL container that includes TL information associated with a TSN node. The transmission component 2004 may transmit a second message including a second TL container that includes TL information associated with the RAN node.

[0318] The number and arrangement of components shown in Fig. 20 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 20. Furthermore, two or more components shown in Fig. 20 may be implemented within a single component, or a single component shown in Fig. 20 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 20 may perform one or more functions described as being performed by another set of components shown in Fig. 20.

[0319] Fig. 21 is a diagram of an example apparatus 2100 for wireless communication, in accordance with the present disclosure. The apparatus 2100 may be a UE, or a UE may include the apparatus 2100. In some aspects, the apparatus 2100 includes a reception component 2102, a transmission component 2104, and/or a communication manager 2106, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager 2106 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 2100 may communicate with another apparatus 2108, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 2102 and the transmission component 2104.

[0320] In some aspects, the apparatus 2100 may be configured to perform one or more operations described herein in connection with Figs. 5-11. Additionally, or alternatively, the apparatus 2100 may be configured to perform one or more processes described herein, such as process 1400 of Fig. 14. In some aspects, the apparatus 2100 and/or one or more components shown in Fig. 21 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 21 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the 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 stored in a non-transitory computer- readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0321] The reception component 2102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 2108. The reception component 2102 may provide received communications to one or more other components of the apparatus 2100. In some aspects, the reception component 2102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 2100. In some aspects, the reception component 2102 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.

[0322] The transmission component 2104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 2108. In some aspects, one or more other components of the apparatus 2100 may generate communications and may provide the generated communications to the transmission component 2104 for transmission to the apparatus 2108. In some aspects, the transmission component 2104 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 2108. In some aspects, the transmission component 2104 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 2104 may be co-located with the reception component 2102 in a transceiver.

[0323] The communication manager 2106 may support operations of the reception component 2102 and/or the transmission component 2104. For example, the communication manager 2106 may receive information associated with configuring reception of communications by the reception component 2102 and/or transmission of communications by the transmission component 2104. Additionally, or alternatively, the communication manager 2106 may generate and/or provide control information to the reception component 2102 and/or the transmission component 2104 to control reception and/or transmission of communications. [0324] The transmission component 2104 may transmit TSS subscription information associated with the UE. The reception component 2102 may 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.

[0325] The reception component 2102 may receive a SIB including an indication to perform a RACH procedure to transition from operation in an idle mode in association with receiving the clock quality information associated with the RAN node. The communication manager 2106 may perform the RACH procedure based at least in part on the indication and a randomized backoff time. [0326] The reception component 2102 may receive an indication of the randomized backoff time, the indication of the randomized backoff time being received during operation in a connected mode prior to operation in the idle mode.

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

[0328] The number and arrangement of components shown in Fig. 21 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 21. Furthermore, two or more components shown in Fig. 21 may be implemented within a single component, or a single component shown in Fig. 21 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 21 may perform one or more functions described as being performed by another set of components shown in Fig. 21.

[0329] The following provides an overview of some Aspects of the present disclosure: [0330] Aspect 1 : A method of wireless communication performed by a core network node, comprising: transmitting a time synchronization status (TSS) request message associated with a radio access network (RAN) node, the TSS request message including a request for the RAN node to transmit TSS information to the core network node; and receiving a TSS response message associated with the RAN node after transmitting the TSS request message.

[0331] Aspect 2: The method of Aspect 1, wherein the TSS response message includes clock information associated with the RAN node.

[0332] Aspect 3 : The method of Aspect 2, wherein the clock information includes an indication of at least one of a synchronization state, a synchronization performance, a clock frequency stability, a clock accuracy, a parent time source, a clock traceability, or a list of cells for which the clock information is valid.

[0333] Aspect 4: The method of any of Aspects 1-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.

[0334] Aspect 5: The method of any of Aspects 1-4, further comprising receiving the TSS information associated with the RAN node.

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

[0336] Aspect 7: The method of any of Aspects 1-6, wherein the TSS request message indicates one or more parameters associated with TSS information reporting. [0337] Aspect 8: The method of Aspect 7, wherein the one or more parameters indicate at least one of a reporting periodicity, a reporting trigger event, or a threshold associated with TSS information reporting.

[0338] Aspect 9: The method of any of Aspects 1-8, wherein the TSS request message includes an indication that the RAN node is to start TSS information reporting.

[0339] Aspect 10: The method of Aspect 9, further comprising transmitting a termination command including an indication that the RAN node is to stop TSS information reporting. [0340] Aspect 11 : The method of Aspect 10, further comprising receiving a termination command response including an indication that the RAN node is unable to stop TSS information reporting.

[0341] Aspect 12: The method of any of Aspects 1-11, further comprising transmitting an activation message including an indication that the RAN node is to start TSS information reporting.

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

[0343] Aspect 14: The method of Aspect 12, further comprising transmitting a deactivation message including an indication that the RAN node is to stop TSS information reporting.

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

[0345] Aspect 16: The method of any of Aspects 1-15, wherein the RAN node is a disaggregated RAN node.

[0346] Aspect 17: The method of any of Aspects 1-16, further comprising transmitting TSS subscription information associated with a user equipment (UE) connected to the RAN node.

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

[0348] Aspect 19: The method of Aspect 18, wherein the TSS response message includes clock information associated with the RAN node.

[0349] Aspect 20: The method of Aspect 19, wherein the clock information includes an indication of at least one of a synchronization state, a clock frequency stability, a clock accuracy, a parent time source, a clock traceability, or a list of cells for which the clock information is valid. [0350] Aspect 21: The method of any of Aspects 18-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.

[0351] Aspect 22: The method of any of Aspects 18-21, further comprising transmitting the TSS information associated with the RAN node.

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

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

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

[0355] Aspect 26: The method of any of Aspects 18-25, wherein the TSS request message indicates one or more parameters associated with TSS information reporting.

[0356] Aspect 27: The method of Aspect 26, wherein the one or more parameters indicate at least one of a reporting periodicity, a reporting trigger event, or a threshold associated with TSS information reporting.

[0357] Aspect 28: The method of any of Aspects 18-27, wherein the TSS request message includes an indication to start TSS information reporting.

[0358] Aspect 29: The method of Aspect 28, further comprising receiving a termination command including an indication to stop TSS information reporting.

[0359] Aspect 30: The method of Aspect 29, further comprising transmitting a termination command response including an indication that the RAN node is unable to stop TSS information reporting.

[0360] Aspect 31 : The method of any of Aspects 18-30, further comprising receiving an activation message including an indication to start TSS information reporting.

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

[0362] Aspect 33 : The method of Aspect 31 , further comprising receiving a deactivation message including an indication to stop TSS information reporting.

[0363] Aspect 34: The method of Aspect 33, further comprising transmitting a deactivation response message including an indication that the RAN node is unable to stop TSS information reporting. [0364] Aspect 35: The method of any of Aspects 18-34, wherein the RAN node is a disaggregated RAN node.

[0365] Aspect 36: The method of any of Aspects 18-35, further comprising receiving TSS subscription information associated with a user equipment (UE) connected to the RAN node. [0366] Aspect 37: The method of Aspect 36, further comprising transmitting clock quality information for reception by the UE based at least in part on the TSS subscription information associated with the UE, wherein the clock quality information is transmitted via an RRC message.

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

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

[0369] Aspect 40: The method of Aspect 36, further comprising transmitting the TSS subscription information associated with the UE to another RAN node.

[0370] Aspect 41 : A method of wireless communication performed by a user equipment (UE), comprising: 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 radio access network (RAN) node; and performing the RACH procedure based at least in part on the indication and a randomized backoff time.

[0371] Aspect 42: The method of Aspect 41, further comprising 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 a connected mode prior to operation in the idle mode.

[0372] Aspect 43: The method of any of Aspects 41-42, further comprising determining the randomized backoff time based at least in part on information associated with the UE.

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

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

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

[0376] Aspect 47: The method of any of Aspects 45-46, wherein the TSC assistance response message includes an indication of a burst periodicity within the burst periodicity range.

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

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

[0379] Aspect 50: The method of any of Aspects 48-49, wherein the TSC assistance response message includes an indication of a burst periodicity within the burst periodicity range.

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

[0381] Aspect 52: A method of wireless communication performed by a core network node, comprising: transmitting a first message including a first talker and listener (TL) container that includes TL information associated with a time sensitive network (TSN) node; and receiving a second message including a second TL container that includes TL information associated with a radio access network (RAN) node.

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

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

[0384] Aspect 55: A method of wireless communication performed by a radio access network (RAN) node, comprising: receiving a first message including a first talker and listener (TL) container that includes TL information associated with a time sensitive network (TSN) node; and transmitting a second message including a second TL container that includes TL information associated with the RAN node.

[0385] Aspect 56: The method of Aspect 55, wherein the TL information associated with the TSN node includes at least one of a time aware offset or an interface configuration. [0386] Aspect 57: The method of any of Aspects 55-56, wherein the TL information associated with the RAN node includes at least one of interface capability information or end station interface information.

[0387] Aspect 58: A method of wireless communication performed by a user equipment (UE), comprising: transmitting 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 based at least in part on the TSS subscription information associated with the UE.

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

[0389] Aspect 60: The method of any of Aspects 58-59, wherein the clock quality information includes one or more items of TSS information.

[0390] Aspect 61: The method of any of Aspects 58-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 a clock quality is acceptable.

[0391] Aspect 62: The method of any of Aspects 58-61, further comprising: 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 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.

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

[0393] 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.

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

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

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

[0397] Aspect 68: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-65. [0398] Aspect 69: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instmctions executable by a processor to perform the method of one or more of Aspects 1-65.

[0399] Aspect 70: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-65.

[0400] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. [0401] As used herein, the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.

[0402] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

[0403] Even though particular combinations of features are recited 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 ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every 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 those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (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 ordering of a, b, and c).

[0404] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’).

Claims

WHAT IS CLAIMED IS:

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

2. The RAN node of claim 1, wherein the TSS response message includes clock information associated with the RAN node, wherein the clock information includes an indication of at least one of a synchronization state, a clock frequency stability, a clock accuracy, a parent time source, a 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 transmit the TSS information associated with the RAN node, wherein the TSS information includes information associated with at least one of a synchronization state, a clock frequency stability, a clock accuracy, a parent time source, a 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 transmitted based at least in part on at least one of a detection of a reporting trigger 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 trigger event, or a threshold associated with TSS information reporting.

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

8. The RAN node of 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 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 transmit a termination command response including an indication that the RAN node is unable to 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 including 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 transmit a deactivation response message including an indication that the RAN node is unable to stop TSS information reporting.

14. The RAN node of claim 1, wherein the RAN node is a disaggregated 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 transmit clock quality information for reception 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 transmitted via a radio resource control (RRC) message.

18. The RAN node of claim 16, wherein the clock quality information includes 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 a clock quality is acceptable, and the one or more processors are further configured to: determine clock quality acceptance criteria configured for the RAN node, and determine whether the clock quality is acceptable based at least in part on the clock quality acceptance criteria, wherein 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 transmit the TSS subscription information associated with the UE to another RAN node.

22. A user equipment (UE) for wireless communication, comprising: a memory; and one or more processors, coupled to the memory, configured to: transmit time synchronization status (TSS) subscription information associated with the UE; and receive clock quality information associated with a radio access network (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.

23. The UE of claim 22, wherein the clock quality information is received via a radio resource control (RRC) message.

24. The UE of claim 22, wherein the clock quality information includes one or more items of TSS information.

25. The UE of claim 22, 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 a clock quality is acceptable.

26. The UE of claim 22, wherein the one or more processors are further configured to: receive a system information block (SIB) including an indication to perform a random access channel (RACH) procedure to transition from operation in an idle mode to a connected mode in association with receiving the clock quality information associated with the RAN node; and perform the RACH procedure 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 a 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, comprising: receiving a time synchronization status (TSS) request message including a request for the RAN node to transmit TSS information; and transmitting a TSS response message after receiving the TSS request message.

30. A method of wireless communication performed by a user equipment (UE), comprising: transmitting 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 based at least in part on the TSS subscription information associated with the UE.