Distribution of clock quality information to user equipment

Abstract

The apparatus includes one or more memories and one or more processors coupled to the one or more memories, the processor(s) configured to receive clock quality reporting control information, and the processor(s) configured to transmit clock quality information to a user equipment (UE) based on the clock quality reporting control information.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS)

[0001] This application claims priority to Greek Patent Application No. 20220100895, filed November 3, 2022, entitled "DELIVERY OF CLOCK QUALITY INFORMATION TO USER EQUIPMENT," the entire disclosure of which is expressly incorporated herein by reference.

[0002] FIELD OF THE DISCLOSURE

[0002] The present disclosure relates generally to wireless network time synchronization, and more particularly to efficient distribution of clock quality information to user equipment (UE). [Background technology]

[0003]

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP). Narrowband (NB) Internet of Things (IoT) and enhanced machine type communications (eMTC) are sets of extensions to LTE for machine type communications.

[0004] A wireless communication network may include multiple base stations (BSs) capable of supporting communication for multiple user equipments (UEs). The user equipments (UEs) may communicate with the base stations (BSs) via downlinks and uplinks. The downlink (or forward link) refers to the communication link from the BSs to the UEs, and the uplink (or reverse link) refers to the communication link from the UEs to the BSs. As described in more detail below, a BS may be referred to as a Node B, evolved Node B (eNB), gNB, access point (AP), radio head, transmit / receive point (TRP), new radio (NR) BS, 5G Node B, etc.

[0005]

[0005] The above multiple access technologies have been adopted in various telecommunications standards to provide common protocols that enable various user equipment to communicate at city, national, regional, or even global levels. New Radio (NR), sometimes referred to as 5G, is a set of extensions to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to improve spectral efficiency, lower costs, improve service, utilize new spectrum, and better support mobile broadband Internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink (UL), better integrating with other open standards, and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. Summary of the Invention

[0006] Aspects of the present disclosure are directed to an apparatus. The apparatus includes at least one memory and one or more processors coupled to the memory. The processor(s) are configured to receive clock quality reporting control information. The processor(s) are also configured to transmit clock quality information to a user equipment (UE) based on the clock quality reporting control information.

[0007] In an aspect of the present disclosure, a method for wireless communication by a network device includes receiving clock quality reporting control information, and transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information.

[0008] In another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon is disclosed. The program code, when executed by a processor, includes program code for receiving clock quality reporting control information. The program code also includes program code for transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information.

[0009] Another aspect of the present disclosure is directed to an apparatus, the apparatus including means for receiving clock quality reporting control information, and means for transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information.

[0010]

[0010] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and processing systems as fully described with reference to and illustrated by the accompanying drawings and this specification.

[0011] The foregoing has outlined rather broadly the features and technical advantages of embodiments of the present disclosure in order that the following Detailed Description may be better understood. Additional features and advantages are described. The concepts 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. The properties of the disclosed concepts, both their organization and method of operation, together with associated advantages, will be better understood by considering the following description in conjunction with the accompanying figures. Each of the figures is provided for purposes of illustration and description, and not as a definition of the limits of the claims. [Brief explanation of the drawings]

[0012]

[0012] In order to enable the features of the present disclosure to be understood in detail, a particular description may be made by referring to various embodiments, some of which are shown in the accompanying drawings. However, it should be noted that the accompanying drawings only show certain embodiments of the present disclosure, and therefore should not be considered as limiting the scope of the present disclosure, as the present description may admit of other equally effective embodiments. The same reference numbers in different drawings may identify the same or similar elements. [Figure 1]

[0013] FIG. 1 is a block diagram conceptually illustrating an example of a wireless communication network, in accordance with various aspects of the present disclosure. [Figure 2]

[0014] FIG. 1 is a block diagram conceptually illustrating an example of a base station communicating with a user equipment (UE) in a wireless communication network, in accordance with various aspects of the present disclosure. [Figure 3]

[0015] FIG. 2 is a block diagram illustrating an example disaggregated base station architecture, in accordance with various aspects of the present disclosure. [Figure 4]

[0016] FIG. 1 is a timing diagram illustrating communication of clock quality information in accordance with various aspects of the present disclosure. [Figure 5]

[0017] FIG. 1 is a block diagram of an example wireless communication device that supports distribution of clock quality information in accordance with various aspects of the present disclosure. [Figure 6]

[0018] FIG. 1 is a block diagram of an example wireless communication device that supports distribution of clock quality information in accordance with various aspects of the present disclosure. [Figure 7]

[0019] FIG. 1 is a flow diagram illustrating an example process performed, for example, by a network device, in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013]

[0020] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure may 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. Based on the teachings, those skilled in the art will understand that the scope of the present disclosure is intended to encompass any aspect of the present disclosure, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the described aspects. Furthermore, the scope of the present disclosure is intended to encompass such apparatuses or methods practiced using other structure, functions, or structure and functions in addition to or other than the various aspects of the present disclosure described. It should be understood that any aspect of the present disclosure disclosed may be embodied by one or more elements of a claim.

[0014]

[0021] Several aspects of telecommunications systems will now be presented with reference to various devices and techniques. These devices and techniques are described in the Detailed Description below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0015]

[0022] Although aspects may be described using terminology commonly associated with 5G and beyond wireless technologies, it should be noted that aspects of the present disclosure may also be applied in other generation-based communication systems such as and including 3G and / or 4G technologies.

[0016]

[0023] Network time synchronization allows network devices to accurately timestamp information based on clock information received from the network. For example, a bank may timestamp financial transactions based on network time. The quality of network time information required by a user equipment (UE) varies depending on the application. For example, a banking application may specify accuracy within 500 ms, while a scientific or utility application may specify accuracy to the nearest nanosecond. Different network components may provide different levels of clock accuracy. It would be desirable for the network to be able to efficiently indicate to the UE the accuracy of the network time provided by its network devices.

[0017]

[0024] Functionality is defined to enable a Next Generation Radio Access Network (NG-RAN) to provide a UE with network time (e.g., a reference time) for a fifth generation (5G) system or a sixth generation (6G) system using either a system information block (SIB) or unicast radio resource control (RRC) signaling. The UE makes the reference time available to devices attached to the UE. The time reference can be used as a primary or backup clock for time service consumers, such as financial institutions, public utilities, etc.

[0018]

[0025] To enable the use of the reference time as a primary or backup clock, clock quality information may be provided to the UE. The clock quality information may include information about the quality of the 5G clock, such as traceability to Coordinated Universal Time (UTC), clock accuracy, frequency stability, etc. By providing the clock quality information to the UE, a time service consumer can determine whether the quality of the 5G clock can meet its requirements.

[0019]

[0026] Clock synchronization can occur because some operations or processes depend on synchronization. For example, robotic arms in a factory may need to operate in coordination, which requires clock synchronization. Similarly, power grid substations may need to operate in phase, which requires clock synchronization. If synchronization cannot be guaranteed, operations may be suspended to prevent malfunctions. Clock quality information is an important decision criterion for determining whether an operation / process can safely continue. In another example, a bank may be required by regulation to document (e.g., by keeping log files) whether its clocks are UTC traceable. This documentation may be required by markets, for example, under the MIFID II regulations in Europe.

[0020]

[0027] Not only should clock quality information be provided to the UE, but also what type of clock quality information should be provided to the UE should be configured. Aspects of the present disclosure introduce a solution to increase the efficiency of providing clock quality information about individual radio access network nodes (e.g., base stations) to the UE. In some aspects, the network controls whether clock information should be provided at all, and if so, what level of detail of the clock quality information should be provided to the UE. That is, what information the UE receives is individually configured. Each UE may receive a different level of detail.

[0021]

[0028] Some aspects allow the network to indicate to a UE whether the network clock quality meets the clock quality requirements for a particular UE. For example, a base station may indicate to a UE whether the base station's clock quality meets an agreement with a particular time service consumer. In other words, the base station indicates whether the clock quality is acceptable for a particular UE.

[0022]

[0029] In some aspects, a unified data management (UDM) subscription may be configured with information regarding a clock quality detail level. The clock quality detail level indicates whether and what clock quality information should be provided to the UE. In some implementations, the clock quality detail level may specify a clock quality index, clock quality details, or an indication of whether the clock quality meets clock quality acceptance criteria for the UE (e.g., an acceptable / unacceptable indication). In aspects where the subscription does not provide clock quality configuration, the clock quality detail level may be provided based on an application program interface (API) request.

[0023]

[0030] In other aspects of the present disclosure, a default clock quality is signaled to a UE for an area in which the UE may be located. Signaling the default clock quality improves the efficiency of clock quality signaling. The area may be a cell of a base station, a tracking area shared by multiple base stations, or another type of area. In these aspects, the network provides a default clock quality to UEs located within the area. The network may override the default information, for example, by broadcasting more specific information from the base station. In this case, the UE connects to the network to receive clock quality details from a RAN node that broadcasts the more specific information.

[0024]

[0031] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages: In some examples, the described techniques, such as receiving clock quality reporting control information, transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information, and / or transmitting a default clock quality to the UE, may improve the efficiency of network time synchronization. For example, time synchronization becomes more efficient because signaling is reduced by avoiding an active connection from the UE to the network.

[0025]

[0032] 1 illustrates a network 100 in which aspects of the present disclosure can be practiced. Network 100 may be a 5G network, a NR network, or some other wireless network, such as an LTE network. Wireless network 100 may include a number of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with user equipment (UE) and may also be referred to as a base station, an NR BS, a Node B, a gNB, a 5G Node B, an access point, a transmit / receive point (TRP), a network node, a network entity, etc. A base station may be implemented as an aggregated base station, a disaggregated base station, an integrated access backhaul (IAB) node, a relay node, a sidelink node, etc. The base station may be implemented in a centralized or monolithic base station architecture, or alternatively in a non-centralized base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real time (near-RT) RAN intelligent controller (RIC), or a non-real time (non-RT) RIC.

[0026]

[0033] Each BS can provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS and / or the BS subsystem serving this coverage area, depending on the context in which the term is used.

[0027]

[0034] A BS may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs that have an association with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS for a macrocell may be referred to as a macro BS. A BS for a picocell may be referred to as a pico BS. A BS for a femtocell may be referred to as a femto BS or a home BS. 1, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “AP,” “Node B,” “5G NB,” “TRP,” and “cell” may be used interchangeably.

[0028]

[0035] In some aspects, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move according to the location of the mobile BS. In some aspects, the BSs may interconnect with each other and / or to one or more other BSs or network nodes (not shown) within wireless network 100 through various types of backhaul interfaces, such as direct physical connections, virtual networks, etc., using any suitable transport network.

[0029]

[0036] Wireless network 100 may also include relay stations. A relay station is an entity capable of receiving data transmissions from an upstream station (e.g., a BS or UE) and transmitting the data transmissions to a downstream station (e.g., a UE or BS). A relay station may also be a UE capable of relaying transmissions for other UEs. In the example shown in FIG. 1, relay station 110d may communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a repeater, etc.

[0030]

[0037] Wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different susceptibility to interference within wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5-40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1-2 watts).

[0031]

[0038] As an example, BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and core network 130 may exchange communications via backhaul links 132 (e.g., S1, etc.). Base stations 110 may communicate with each other via other backhaul links (e.g., X2, etc.), either directly or indirectly (e.g., through core network 130).

[0032]

[0039] The core network 130 may be an evolved packet core (EPC) that may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may be a control node that handles signaling between the UE 120 and the EPC. All user IP packets may be forwarded through the S-GW, which may itself be connected to a P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may connect to a network operator's IP services. The operator's IP services may include the Internet, intranets, IP multimedia subsystem (IMS), and packet-switched (PS) streaming services.

[0033]

[0040] The core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. One or more of the base stations 110 or access node controllers (ANCs) may interface with the core network 130 through backhaul links 132 (e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communications with the UEs 120. In some configurations, the various functions of each access network entity or base station 110 may be distributed across various network devices (e.g., radio heads and access network controllers) or may be integrated within a single network device (e.g., base station 110).

[0034]

[0041] The UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a mobile phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or satellite radio), a vehicle part or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate over a wireless or wired medium.

[0035]

[0042] One or more UEs 120 can establish a protocol data unit (PDU) session with respect to a network slice. In some cases, the UE 120 can select a network slice based on an application or subscription service. By having different network slices serving different applications or subscriptions, the UE 120 can improve its resource utilization within the wireless network 100 while also meeting the performance specifications of the UE 120's individual applications. In some cases, the network slice used by the UE 120 can be served by an AMF (not shown in FIG. 1 ) associated with one or both of the base station 110 or the core network 130. Furthermore, session management of the network slice can be performed by an access and mobility management function (AMF).

[0036]

[0043] The UEs 120 may include a clock quality module 140. For simplicity, only one UE 120d is shown as including a clock quality module 140. The clock quality module 140 may receive a first default clock quality for a first area and apply the first default clock quality when the UE is located within the first area. The clock quality module 140 may also receive a second default clock quality for the second area when the UE leaves the first area and enters a second area and apply the second default clock quality when the UE is located within the second area.

[0037]

[0044] The core network 130 or the base station 110 or any other network device (e.g., as shown in FIG. 3) may include a clock quality module 138 for network time synchronization. The clock quality module 138 may receive clock quality reporting control information and transmit clock quality information to a user equipment (UE) based on the clock quality reporting control information. In some aspects, the clock quality module 138 may transmit a default clock quality to the user equipment (UE), where the default clock quality applies to an area of ​​the network device.

[0038]

[0045] Some UEs may be considered machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and eMTC UEs may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, a location tag, etc., capable of communicating with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to a network (e.g., a wide area network such as the Internet or a cellular network) or network connectivity via, for example, a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component, a memory component, etc.

[0039]

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

[0040]

[0047] In some aspects, two or more UEs 120 (e.g., those shown as UE 120a and UE 120e) can communicate directly (e.g., without using a base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, the UEs 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, etc.), a mesh network, etc. In this case, the UEs 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere as being performed by the base station 110. For example, the base station 110 can configure the UEs 120 via downlink control information (DCI), radio resource control (RRC) signaling, a medium access control-control element (MAC-CE), or system information (e.g., a system information block (SIB)).

[0041]

[0048] As noted above, Figure 1 is provided as an example only. Other examples may differ from those described with respect to Figure 1.

[0042]

[0049] 2 shows a block diagram of a design 200 of a base station 110 and a UE 120, which may be one of the base stations and one of the UEs in FIG. 1. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0043]

[0050] At base station 110, transmit processor 220 may receive data from data source 212 for one or more UEs, select one or more modulation and coding schemes (MCSs) for each UE based at least in part on a channel quality indicator (CQI) received from that UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(es) selected for that UE, and provide data symbols for all UEs. Reducing the MCS reduces throughput but improves transmission reliability. Transmit processor 220 may also process system information (e.g., related to semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.) and provide overhead symbols and control symbols. Transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM), etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively. According to various aspects described in more detail below, location coding can be used to generate synchronization signals to convey additional information.

[0044]

[0051] At UE 120, antennas 252a through 252r may receive downlink signals from base station 110 and / or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols and provide decoded data for UE 120 to a data sink 260 and may provide decoded control and system information to a controller / processor 280. The channel processor may determine a reference signal received power (RSRP), a received signal strength indicator (RSSI), a reference signal received quality (RSRQ), a channel quality indicator (CQI), etc. In some aspects, one or more components of the UE 120 may be included within a housing.

[0045]

[0052] On the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from controller / processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for Discrete Fourier Transform-Spread OFDM (DFT-s-OFDM), CP-OFDM, etc.) and transmitted to base station 110. At base station 110, uplink signals from UE 120 and other UEs may be received by antenna 234, processed by demodulator 254, detected by MIMO detector 236 if applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and may provide the decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the core network 130 via the communication unit 244. The core network 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0046]

[0053] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component of FIG. 2 may perform one or more techniques associated with distributing clock quality information, as described in more detail elsewhere. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component(s) of FIG. 2 may perform or direct the operations of, for example, the processes of FIGS. 4 and 7 and / or other processes as described. The memories 242 and 282 may store data and program codes for the base station 110 and the UE 120, respectively. The scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0047]

[0054] In some aspects, the UE 120 and / or the base station 110 may include means for receiving, means for transmitting, means for sending, means for broadcasting, and means for applying. Such means may include one or more components of the UE 120 or the base station 110 described with respect to FIG.

[0048]

[0055] As noted above, Figure 2 is provided as an example only, and other examples may differ from those described with respect to Figure 2.

[0049]

[0056] The deployment of communication systems, such as 5G New Radio (NR) systems, can be configured in numerous ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, Radio Access Network (RAN) nodes, core network nodes, network elements, or network equipment such as base stations (BSs), or one or more units (or one or more components) performing base station functionality, can be implemented in a centralized or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell) can be implemented as a centralized base station (also known as a standalone BS or monolithic BS) or a disaggregated base station.

[0050]

[0057] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (e.g., one or more centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU or alternatively geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0051]

[0058] The operation of a base station type or network design may take into account the aggregation characteristics of base station functions. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration supported by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functions across two or more units in different physical locations, as well as virtually distributing the functions of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station, or a disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0052]

[0059] In some cases, different types of devices supporting different types of applications and / or services can coexist in a cell. Examples of different types of devices include UE handsets, customer premises equipment (CPE), vehicles, Internet of Things (IoT) devices, etc. Examples of different types of applications include ultra-reliable low-latency communications (URLLC) applications, massive machine-type communications (mMTC) applications, enhanced mobile broadband (eMBB) applications, vehicle-to-anything (V2X) applications, etc. Furthermore, in some cases, a single device can support different applications or services simultaneously.

[0053]

[0060] 3 shows a diagram illustrating the architecture of an exemplary disaggregated base station 300. The disaggregated base station 300 architecture may include one or more central units (CUs) 310 that can communicate directly with the core network 320 via a backhaul link or indirectly with the core network 320 through one or more disaggregated base station units (e.g., a near-real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CUs 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DUs 330 may communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. The RUs 340 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served by multiple RUs 340 simultaneously.

[0054]

[0061] Each of the units (e.g., CU 310, DU 330, RU 340, and quasi-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive signals from or transmit signals to one or more of the other units via a wired transmission medium. Furthermore, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit or receive signals via a wireless transmission medium to one or more of the other units.

[0055]

[0062] In some aspects, the CU 310 can host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may implement 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 functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface. The CU 310 may be implemented to communicate with the DU 330 as needed for network control and signaling.

[0056]

[0063] The DU 330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), at least in part according to a functional division such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 330 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0057]

[0064] The lower layer functions may be implemented by one or more RUs 340. In some deployments, the RUs 340 controlled by the DU 330 may correspond to logical nodes hosting RF processing functions, lower PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division, such as a lower layer functional division. In such an architecture, the RU(s) 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the DU(s) 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0058]

[0065] 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 deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-cloud) 390) to perform lifecycle management of the network element (e.g., to instantiate virtualized network elements) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network elements may include, but are not limited to, the CU 310, the DU 330, the RU 340, and the quasi-RT RIC 325. In some implementations, the SMO framework 305 may communicate with hardware aspects of a 4G RAN, such as the open eNB (O-eNB) 311, via the O1 interface. Additionally, in some implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via an O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0059]

[0066] The non-RT RIC 315 may be configured to include logic functions that enable 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 / functions in the quasi-RT RIC 325. The non-RT RIC 315 may be coupled to or may communicate with the quasi-RT RIC 325 (e.g., via an A1 interface). The quasi-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and action via interfaces connecting one or more CUs 310, one or more DUs 330, or both, and the O-eNB 311 to the quasi-RT RIC 325 (e.g., via an E2 interface).

[0060]

[0067] In some implementations, the non-RT RIC 315 may receive parameters or external enrichment information from an external server to generate AI / ML models to be deployed in the quasi-RT RIC 325. Such information may be utilized by the quasi-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 quasi-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 may employ AI / ML models to monitor long-term trends and patterns in performance and implement corrective actions through the SMO framework 305 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0061]

[0068] Network time synchronization enables network devices to accurately time-stamp information based on clock information received from the network. A network typically has a primary reference time clock that provides time for other clocks within the network and is usually synchronized with an external time source that provides time according to a recognized time standard (e.g., UTC). The network makes this time signal available to network devices. For example, a bank may time-stamp financial transactions based on network time. The quality of network time information required by user equipment (UE) varies depending on the application. For example, a banking application may specify time accuracy to within 500 ms, while a scientific or utility application (e.g., power grid management) may specify accuracy to the nearest nanosecond. Different network components may provide different levels of clock accuracy. It would be desirable for the network to be able to efficiently indicate to the UE the accuracy of the network time provided by its network devices.

[0062]

[0069] In Release 16 (Rel-16), the 3rd Generation Partnership Project (3GPP) specified functionality to enable a Next Generation Radio Access Network (NG-RAN) to provide a UE with the time of a fifth-generation (5G) system (e.g., a reference time) using either a system information block (SIB) or unicast radio resource control (RRC) signaling. The UE makes the reference time available to devices attached to the UE, for example, using a 1 packet per second (PPS) output or via the Precision Time Protocol (PTP). The time reference can also be used as a primary or backup clock for time service consumers, e.g., financial institutions, utilities, etc.

[0063]

[0070] Clock quality information may be provided to the UE to enable use of the reference time as a primary or backup clock. The clock quality information may include information about the quality of the 5G clock, such as traceability to Coordinated Universal Time (UTC), clock accuracy, frequency stability, etc. By providing the clock quality information to the UE, a time service consumer can determine whether the quality of the 5G clock can meet its requirements.

[0064]

[0071] Different solutions have been proposed to provide UEs with clock quality information about individual Radio Access Network (RAN) nodes (e.g., base stations). For example, a base station may broadcast a flag and a report identification (ID) to inform the UE that a new report with network clock quality information is available. The base station may also broadcast a flag and a timestamp to inform the UE that a new report with network clock quality information is available. Upon receiving the broadcast, the UE determines whether a new report about the clock quality of the current cell is available based on the report ID or the timestamp. To obtain details about the actual clock quality of the cell, the UE establishes a radio resource control (RRC) connection with the base station to enable the base station to deliver clock quality reports to the UE.

[0065]

[0072] However, these solutions are inefficient due to the amount of signaling involved. A mobile UE using network time synchronization needs to be actively connected to the network to obtain a clock quality report for each cell the UE camps on. This process can result in a large amount of signaling depending on the number of UEs using network time synchronization. These solutions intentionally do not provide clock quality information, for example, in a system information broadcast (SIB) message, to prevent misuse of such information if it were made available to every UE.

[0066]

[0073] Not only should clock quality information be provided to the UE, but also what type of clock quality information should be provided to the UE should be considered. Aspects of the present disclosure introduce a solution for increasing the efficiency of providing clock quality information regarding individual radio access network nodes (e.g., base stations) to the UE. In some aspects, the network controls whether clock information should be provided at all, and if so, what level of detail of the clock quality information should be provided to the UE. That is, what information the UE receives is individually configured. Each UE may receive a different level of detail.

[0067]

[0074] Other aspects allow the network to indicate to the UE whether the network clock quality meets the clock quality requirements for a particular UE. In these aspects, the base station indicates to the UE whether the base station's clock quality meets an agreement with a particular time service consumer. In other words, the base station indicates whether the clock quality is acceptable for the particular UE.

[0068]

[0075] In some aspects, a unified data management (UDM) subscription may be configured with information regarding a clock quality detail level. The clock quality detail level indicates whether and which clock quality information should be provided to the UE. In some implementations, the clock quality detail level may specify a clock quality index, clock quality details, or an indication of whether the clock quality meets a clock quality acceptance criterion for the UE (an acceptable / unacceptable indication). The acceptance criterion may include multiple different criteria types to be verified to indicate whether the clock quality is acceptable. The UDM subscription holds information about all subscribers for authenticating and authorizing UEs for network access and also holds information about services the subscribers may use. For example, whether the UE can use time synchronization services is configured in the UDM. According to aspects of the present disclosure, clock quality reporting control information may be included in subscription information in the UDM.

[0069]

[0076] The clock quality index provides the UE with a quality index, such as a dimensionless value, that indicates a clock accuracy level for which details are known. For example, the information may be available separately from the network operator (e.g., using an offline process). If clock quality details are configured, the information provided to the UE may include, for example, clock accuracy, frequency stability, and / or traceability to UTC. The acceptable / unacceptable indication informs the UE whether the clock quality meets an acceptable clock quality for the UE, i.e., whether the clock quality meets a clock quality acceptance criterion for the UE. In some aspects, if the clock quality level is an acceptable / unacceptable indication, the network determines whether to indicate acceptable or unacceptable to the UE based on a set of acceptable clock indices configured in the network for the UE. These indices may be agreed upon in advance. In one example, a first index corresponds to 100 ms accuracy with a first level of frequency stability, and a second index corresponds to 500 ms accuracy with a second level of frequency stability. In some aspects, the clock quality level is an acceptable / unacceptable indication. Alternatively, the network determines whether to indicate acceptable or unacceptable to the UE based on clock quality acceptance criteria, which may include acceptable clock accuracy, acceptable frequency stability, etc.

[0070]

[0077] In aspects where the subscription does not provide clock quality configuration, the clock quality detail level may be provided based on an application program interface (API) request. In these aspects, an application function (AF) provides the network with the clock quality detail level and a set of allowable clock indices or clock quality acceptance criteria. This information may be provided, for example, when requesting time synchronization for the UE.

[0071]

[0078] The network may inform each UE whether the clock quality meets the acceptable clock quality for the UE. In a first base station-based configuration, the clock quality detail level and, optionally, a set of acceptable clock indices (also referred to as clock classes or clock levels) or clock quality acceptance criteria are configured in the subscription or signaled by the AF. In this first base station-based configuration, the core network provides the base station with the clock quality detail level, the acceptable clock classes or the set of clock quality acceptance criteria. The core network may provide the information, for example, when establishing the UE context in the RAN.

[0072]

[0079] In another base station-based configuration, the base station receives clock quality detail level information and, optionally, a set of acceptable clock indexes or clock quality acceptance criteria from the core network. In this second base station-based configuration, the base station provides the UE with the following information based on the received clock quality detail level: The clock quality detail level can be a clock quality index, a clock quality detail, or an acceptable / unacceptable indication. If a clock quality index is configured, the base station provides the UE with a quality index that reflects the current clock quality of the RAN node (e.g., the base station). If clock quality detail is configured, the base station provides the UE with the clock quality detail, which reflects the current clock quality of the RAN node. If an acceptable / unacceptable indication is configured, the base station indicates "acceptable" to the UE if the network's clock quality matches one of the acceptable clock classes or clock quality acceptance criteria received from the core network. Otherwise, the base station indicates "unacceptable."

[0073]

[0080] In a core network-based configuration, the core network, e.g., an Access and Mobility Management Function (AMF), evaluates clock quality detail level information and, optionally, a set of acceptable clock indices or clock quality acceptance criteria received from the subscription or from the AF. The core network then provides the clock quality index, clock quality detail, or an acceptable / unacceptable indication to the UE. In some implementations, the core network provides the information to the UE using non-access stratum (NAS) signaling.

[0074]

[0081] In other aspects of the present disclosure, a default clock quality is signaled to the UE for the area in which the UE is located. Signaling the default clock quality improves the efficiency of providing clock quality information to the UE. The area may be a cell of a base station, a tracking area shared by multiple base stations, or another type of area. In these aspects, the network provides the UE with a default clock quality that applies unless the base station broadcasts more specific information. In these aspects, the UE only connects to the network to receive clock quality details for a RAN node when the clock quality details deviate from the default clock quality, as indicated by the more specific information. Either the base station or the core network, e.g., the AMF, may signal the default clock quality to the UE.

[0075]

[0082] In implementations in which the base station signals the default network clock quality, the base station is configured (e.g., using operation, administration, and maintenance (OAM) procedures) with a default clock quality index and associated default clock quality details. If the base station has received clock quality detail level information and, optionally, a set of acceptable clock indices or clock quality acceptance criteria from the core network, the base station provides default network clock quality information to the UE based on the received clock quality detail level. The clock quality information may include a clock quality index that provides the UE with the configured default network clock quality index. The clock quality information may alternatively include clock quality details that provide the UE with the configured default network clock details. The clock quality information may alternatively include an acceptable / unacceptable indication that indicates "acceptable" to the UE if the configured default clock quality matches one of the acceptable clock classes or clock quality acceptance criteria received from the core network, and "unacceptable" otherwise.

[0076]

[0083] If the UE is receiving a default clock quality from a base station, in some aspects, the UE uses the same default clock quality for other base stations that broadcast the same tracking area as the base station that provided the default clock quality. Thus, the UE does not need to communicate with each base station to obtain clock quality information. In these aspects, the area covered by the default clock quality is a tracking area, as opposed to a cell. If the UE enters a tracking area for which it does not have a default network clock quality, the UE may establish a connection (e.g., an RRC connection) with the base station to enable the base station to provide the UE with default network clock quality information for the new tracking area.

[0077]

[0084] In some aspects, the base station (or core network) may further include a list of tracking areas to which the default clock quality applies. For example, the list may include neighboring tracking areas. If the UE has received the default clock quality and list of tracking areas from the base station or core network, the UE uses the same default clock quality for all base stations that broadcast one of the listed tracking areas. If the UE enters a tracking area for which it does not have default network clock quality, the UE may establish a connection (e.g., an RRC connection) to enable the RAN or core network to provide the UE with default network clock quality information for the new tracking area.

[0078]

[0085] Although this disclosure is described with respect to default clock quality, the disclosure is not so limited. The disclosure can also be generalized and used to efficiently provide other cell-specific information that is common to most base stations in an area (e.g., most base stations in a tracking area), but where the cell-specific information for some base stations in the area deviates from the default value.

[0079]

[0086] 4 is a timing diagram illustrating communication of clock quality information in accordance with various aspects of the present disclosure. In the example of FIG. 4, a wireless network 400 includes a base station 110, a UE 120, and a timing information consumer 450. At 402, clock quality reporting control information is processed at the base station 110. The clock quality reporting control information may be received, for example, from an AF or a subscription database.

[0080]

[0087] At 404, the base station 110 transmits clock quality information to the UE 120. The base station 110 may provide the information to the UE 120 based on the received clock quality report control information. For example, the base station 110 may not transmit clock quality information (not shown in FIG. 4) based at least in part on the clock quality report information for the UE indicating not to transmit clock quality information to the UE. In the example of FIG. 4, the clock quality information may include a clock quality index, clock quality details, or an acceptable / unacceptable indication. If a clock quality index is configured, the base station 110 provides the UE 120 with a quality index that reflects the current clock quality of the RAN node (e.g., base station). If a clock quality detail is configured, the base station 110 provides the clock quality detail to the UE 120, and the clock quality detail reflects the current clock quality of the RAN node. If an acceptable / unacceptable indication is configured, and the network's clock quality meets one of the acceptable clock classes received from the core network, the base station 110 indicates a first value (e.g., “0” or “acceptable”) to the UE 120. Otherwise, the base station 110 indicates a second value (e.g., “1” or “unacceptable”). In some aspects, the network provides a default clock quality. If a default clock quality is configured, the base station 110 transmits default clock quality information at 404. If the clock quality of the current area (e.g., cell) deviates from the default clock quality, the base station 110 provides the first UE-1 with additional clock quality information of the current cell at 406.

[0081]

[0088] At 408, the UE 120 provides clock quality information to the timing information consumer 450. If a default clock quality is configured and current, the UE 120 signals the default clock quality information.

[0082]

[0089] 5 is a block diagram of an example wireless communication device 500 that supports efficient distribution of clock quality information in accordance with various aspects of the present disclosure. In some implementations, the wireless communication device 500 is configured to perform one or more steps of the process 700 described with reference to FIG. 7 or the process described with reference to FIG. 4. The wireless communication device 500 may be an example implementation of the base station 110 described above with reference to FIG. 1. For example, the wireless communication device 500 may be a chip, SoC, chipset, package, or device that includes at least one modem (e.g., a Wi-Fi (IEEE 802.11) modem or a cellular modem), at least one processor, at least one radio, and at least one memory.

[0083]

[0090] The wireless communication device 500 includes a transmitting component 502 and a receiving component 504. One or more portions of the components 502, 504 may be implemented at least partially in hardware or firmware. For example, the transmitting component 502 and the receiving component 504 may be implemented at least partially by a modem. In some implementations, at least some of the components 502, 504 are implemented at least partially as software stored in a memory. For example, one or more portions of the components 502, 504 may be implemented as non-transitory instructions (or “code”) executable by a processor to perform the functions or operations of the respective modules.

[0084]

[0091] The transmitting component 502 is configured to transmit clock quality information to a user equipment (UE) based on the clock quality reporting control information. The receiving component 504 is configured to receive the clock quality reporting control information. In another aspect, the transmitting component 502 is configured to transmit a default clock quality to the UE, the default clock quality applying to an area of ​​the network device.

[0085]

[0092] 6 is a block diagram of an example wireless communication device 600 that supports efficient distribution of clock quality information in accordance with various aspects of the present disclosure. In some implementations, the wireless communication device 600 is configured to perform one or more steps of the process described with reference to FIG. 4. The wireless communication device 600 may be an example implementation of the UE 120 described above with reference to FIG. 1. For example, the wireless communication device 600 may be a chip, SoC, chipset, package, or device that includes at least one modem (e.g., a Wi-Fi (IEEE 802.11) modem or a cellular modem), at least one processor, at least one radio, and at least one memory.

[0086]

[0093] The wireless communication device 600 includes a receiving component 602 and an applying component 604. One or more portions of the components 602, 604 may be implemented at least partially in hardware or firmware. For example, the receiving component 602 and the applying component 604 may be implemented at least partially by a modem and / or a processor and memory. In some implementations, at least some of the components 602, 604 are implemented at least partially as software stored in memory. For example, one or more portions of the components 602, 604 may be implemented as non-transitory instructions (or “code”) executable by a processor to perform the functions or operations of the respective modules.

[0087]

[0094] The receiving component 602 is configured to receive a first default clock quality for a first area. The receiving component 602 is also configured to receive a second default clock quality for a second area when the UE 120 leaves the first area and enters the second area. The applying component 604 is configured to apply the first default clock quality when the UE 120 is located in the first area and apply the second default clock quality when the UE 120 is located in the second area.

[0088]

[0095] 7 is a flow diagram illustrating an example process 700, performed by, for example, a network device, in accordance with various aspects of the present disclosure. The example process 700 is an example of efficient distribution of clock quality information to user equipment (UE).

[0089]

[0096] As shown in FIG. 7 , in some aspects, at block 702, process 700 may include receiving clock quality reporting control information. For example, a base station (e.g., using antennas 234, MOD / DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, etc.) or a core network may receive the clock quality reporting control information. The clock quality reporting control information may indicate a clock quality detail level including information to be provided to the UE. The clock quality detail level may include a clock quality index, clock quality details, and / or an indication of whether the clock quality meets a clock quality acceptance criterion for the UE. The network device may receive a clock quality acceptance criterion associated with the indication of whether the clock quality meets the clock quality acceptance criterion for the UE. In some aspects, the clock quality details include clock accuracy, frequency stability, and / or traceability to Coordinated Universal Time (UTC). The clock reporting control information may be received from UE subscription information or an application function. When the network device comprises a base station, the network device may receive the clock quality reporting control information from a core network component upon establishing a context for the UE.

[0090]

[0097] In some aspects, at block 704, process 700 may include transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information. For example, the base station may transmit the clock quality information (e.g., using antennas 234, MOD / DEMOD 232, TX MIMO processor 230, transmit processor 220, controller / processor 240, memory 242, etc.). In other aspects, transmitting the clock quality information includes transmitting the clock quality information to the UE based at least in part on the clock quality detail level. In yet other aspects, transmitting the clock quality information includes transmitting the clock quality information via non-access stratum signaling when the network device comprises a core network component.

[0091] Exemplary Embodiments

[0098] Aspect 1: An apparatus for wireless communication by a network device, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to receive clock quality reporting control information and transmit clock quality information to a user equipment (UE) based on the clock quality reporting control information.

[0092]

[0099] Aspect 2: The apparatus described in aspect 1, wherein the clock quality reporting control information indicates a clock quality detail level including information to be provided to the UE, and the at least one processor configured to transmit is further configured to transmit clock quality information to the UE based at least in part on the clock quality detail level.

[0093]

[0100] Aspect 3: The apparatus of aspect 1 or 2, wherein the clock quality detail level includes at least one of a clock quality detail or an indication of whether the clock quality meets a clock quality acceptance criterion for the UE.

[0094]

[0101] Aspect 4: The apparatus of any of Aspects 1 to 3, wherein the indication of whether the clock quality meets a clock quality acceptance criterion for the UE includes an acceptable / unacceptable indication.

[0095]

[0102] Aspect 5: The apparatus of any of Aspects 1 to 4, wherein the at least one processor is further configured to receive a clock quality acceptance criterion associated with an indication of whether the clock quality satisfies the clock quality acceptance criterion for the UE, and the at least one processor configured to transmit is further configured to transmit, to the UE, clock quality information based at least in part on the clock quality acceptance criterion and a clock quality detail level including the indication of whether the clock quality satisfies the clock quality acceptance criterion for the UE.

[0096]

[0103] Aspect 6: The apparatus of any of Aspects 1 to 5, wherein the clock quality details include at least one of clock accuracy, frequency stability, and traceability to Coordinated Universal Time (UTC).

[0097]

[0104] Aspect 7: The apparatus of any one of Aspects 1 to 6, wherein the at least one processor is further configured to receive clock reporting control information from UE subscription information.

[0098]

[0105] Aspect 8: The apparatus of any of Aspects 1 to 6, wherein the at least one processor is further configured to receive clock quality reporting control information from an application function (AF).

[0099]

[0106] Aspect 9: The apparatus of any of Aspects 1 to 6, wherein the at least one processor is further configured to receive clock quality reporting control information from a core network component, and wherein the network device comprises a base station.

[0100]

[0107] Aspect 10: The apparatus of any of Aspects 1 to 9, wherein the at least one processor is further configured to transmit the clock quality information via non-access stratum signaling based at least in part on a network device comprising a core network component.

[0101]

[0108] Aspect 11: A method of wireless communication by a network device, the method including receiving clock quality reporting control information and transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information.

[0102]

[0109] Aspect 12: The method of aspect 11, wherein the clock quality reporting control information indicates a clock quality detail level including information to be provided to the UE, and transmitting the clock quality information includes transmitting the clock quality information to the UE based at least in part on the clock quality detail level.

[0103]

[0110] Aspect 13: The method of aspect 11 or 12, wherein the clock quality detail level includes at least one of a clock quality detail or an indication of whether the clock quality meets a clock quality acceptance criterion for the UE.

[0104]

[0111] Aspect 14: The method of any one of aspects 11 to 13, wherein the indication of whether the clock quality meets a clock quality acceptance criterion for the UE includes an acceptable / unacceptable indication.

[0105]

[0112] Aspect 15: The method of any of aspects 11 to 14, further comprising receiving a clock quality acceptance criterion associated with an indication of whether the clock quality satisfies the clock quality acceptance criterion for the UE, wherein the method transmits clock quality information to the UE based at least in part on the clock quality acceptance criterion and a clock quality detail level including the indication of whether the clock quality satisfies the clock quality acceptance criterion for the UE.

[0106]

[0113] Aspect 16: The method of any one of aspects 11 to 15, wherein the clock quality details include at least one of clock accuracy, frequency stability, and traceability to Coordinated Universal Time (UTC).

[0107]

[0114] Example 17: The method of any one of Examples 11 to 16, further comprising receiving clock reporting control information from UE subscription information.

[0108]

[0115] Aspect 18: The method of any one of aspects 11 to 16, further comprising receiving clock quality reporting control information from the application function.

[0109]

[0116] Aspect 19: The method of any one of aspects 11 to 16, further comprising receiving clock quality reporting control information from a core network component when a context is established for the UE, wherein the network device comprises a base station.

[0110]

[0117] Aspect 20: The method of any of aspects 11 to 19, wherein transmitting the clock quality information includes transmitting the clock quality information via non-access stratum signaling based at least in part on a network device comprising a core network component.

[0111]

[0118] Aspect 21: A non-transitory computer-readable medium having program code recorded thereon, the program code being executed by a processor and including program code for receiving clock quality reporting control information and for transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information.

[0112]

[0119] Aspect 22: A non-transitory computer-readable medium as described in aspect 21, wherein the clock quality reporting control information indicates a clock quality detail level including information to be provided to the UE, and the program code for transmitting the clock quality information further includes program code for transmitting the clock quality information to the UE based at least in part on the clock quality detail level.

[0113]

[0120] Aspect 23: The non-transitory computer-readable medium of aspect 21 or 22, wherein the clock quality detail level includes at least one of clock quality details or an indication of whether the clock quality meets a clock quality acceptance criterion for the UE.

[0114]

[0121] Aspect 24: The non-transitory computer-readable medium of any of aspects 21 to 23, wherein the indication of whether the clock quality meets a clock quality acceptance criterion for the UE includes an acceptable / unacceptable indication.

[0115]

[0122] Aspect 25: A non-transitory computer-readable medium described in any of aspects 21 to 24, wherein the program code further includes program code for receiving a clock quality acceptance criterion associated with an indication of whether the clock quality satisfies the clock quality acceptance criterion for the UE, and the program code for transmitting the clock quality information to the UE is based at least in part on the clock quality acceptance criterion and a clock quality detail level including the indication of whether the clock quality satisfies the clock quality acceptance criterion for the UE.

[0116]

[0123] Aspect 26: An apparatus for wireless communication by a network device, comprising: means for receiving clock quality reporting control information; and means for transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information.

[0117]

[0124] Aspect 27: The apparatus described in aspect 26, wherein the clock quality reporting control information indicates a clock quality detail level including information to be provided to the UE, and the means for transmitting the clock quality information further comprises means for transmitting the clock quality information to the UE based at least in part on the clock quality detail level.

[0118]

[0125] Aspect 28: The apparatus of aspect 26 or 27, wherein the clock quality detail level includes at least one of the clock quality detail or an indication of whether the clock quality meets a clock quality acceptance criterion for the UE.

[0119]

[0126] Example 29: The apparatus of any of Examples 26 to 28, wherein the indication of whether the clock quality meets a clock quality acceptance criterion for the UE includes an acceptable / unacceptable indication.

[0120]

[0127] Aspect 30: The apparatus of any of aspects 26 to 29, further comprising: means for receiving a clock quality acceptance criterion associated with an indication of whether the clock quality satisfies the clock quality acceptance criterion for the UE; and means for transmitting clock quality information to the UE based at least in part on the clock quality acceptance criterion and a clock quality detail level including the indication of whether the clock quality satisfies the clock quality acceptance criterion for the UE.

[0121]

[0128] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the embodiments.

[0122]

[0129] When used, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. When used, a processor is implemented in hardware, firmware, and / or a combination of hardware and software.

[0123]

[0130] Some aspects are described in relation to thresholds. When used, meeting a threshold can 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, etc., depending on the context.

[0124]

[0131] It will be apparent that the described systems and / or methods may be implemented in various forms of hardware, firmware, and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of aspects. Thus, the operation and behavior of the present systems and / or methods will be described without reference to specific software code. It will be understood that software and hardware can be designed to implement the present systems and / or methods based at least in part on the present description.

[0125]

[0132] Although particular combinations of features are recited in the claims and / or disclosed herein, such combinations are not intended to limit the disclosure of various aspects. Indeed, many of these features can be combined in ways not specifically recited in the claims and / or disclosed herein. Although each dependent claim listed below may depend directly on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to "at least one of" a list of items refers to any combination of those items, including single elements. By way of example, "at least one of a, b, or c" is intended to encompass a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other permutation of a, b, and c).

[0126]

[0133] No element, act, or instruction used should be construed as essential or required unless expressly described as such. Also, where used, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Furthermore, where used, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) 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, where used, terms such as "has," "have," and "having" are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on," unless expressly specified otherwise.

Claims

1. 1. An apparatus for wireless communication by a network device, comprising: at least one memory; at least one processor coupled to the at least one memory; wherein the at least one processor: receiving clock quality reporting control information; transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information; The apparatus is configured to:

2. the clock quality reporting control information indicates a clock quality detail level including information to be provided to the UE; 2. The apparatus of claim 1, wherein the at least one processor configured to transmit is further configured to transmit the clock quality information to the UE based at least in part on the clock quality detail level.

3. The apparatus of claim 2 , wherein the clock quality detail level includes at least one of a clock quality detail or an indication of whether the clock quality meets a clock quality acceptance criterion for the UE.

4. The apparatus of claim 3 , wherein the indication of whether the clock quality meets the clock quality acceptance criteria for the UE includes an acceptable / unacceptable indication.

5. the at least one processor is further configured to receive the clock quality acceptance criterion associated with the indication of whether the clock quality meets the clock quality acceptance criterion for the UE; 4. The apparatus of claim 3, wherein the at least one processor configured to transmit is further configured to transmit the clock quality information to the UE based at least in part on the clock quality acceptance criteria and the clock quality detail level including the indication of whether the clock quality meets the clock quality acceptance criteria for the UE.

6. The apparatus of claim 3 , wherein the clock quality details include at least one of clock accuracy, frequency stability, and traceability to Coordinated Universal Time (UTC).

7. The apparatus of claim 1 , wherein the at least one processor is further configured to receive the clock reporting control information from UE subscription information.

8. The apparatus of claim 1 , wherein the at least one processor is further configured to receive the clock quality reporting control information from an application function (AF).

9. 10. The apparatus of claim 1, wherein the at least one processor is further configured to receive the clock quality reporting control information from a core network component, and the network device comprises a base station.

10. 10. The apparatus of claim 1, wherein the at least one processor is further configured to transmit the clock quality information via non-access stratum signaling based at least in part on the network device comprising a core network component.

11. 1. A method of wireless communication by a network device, comprising: receiving clock quality reporting control information; transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information; A method comprising:

12. the clock quality reporting control information indicates a clock quality detail level including information to be provided to the UE; 12. The method of claim 11, wherein the transmitting the clock quality information comprises transmitting the clock quality information to the UE based at least in part on the clock quality detail level.

13. 13. The method of claim 12, wherein the clock quality detail level includes at least one of a clock quality detail or an indication of whether the clock quality meets a clock quality acceptance criterion for the UE.

14. The method of claim 13 , wherein the indication of whether the clock quality meets the clock quality acceptance criteria for the UE includes an acceptable / unacceptable indication.

15. receiving the clock quality acceptance criterion associated with the indication of whether the clock quality meets the clock quality acceptance criterion for the UE; 14. The method of claim 13, wherein the method transmits clock quality information to the UE based at least in part on the clock quality acceptance criteria and the clock quality detail level that includes the indication of whether the clock quality meets the clock quality acceptance criteria for the UE.

16. 14. The method of claim 13, wherein the clock quality details include at least one of clock accuracy, frequency stability, and traceability to Coordinated Universal Time (UTC).

17. The method of claim 11 , further comprising receiving the clock reporting control information from a UE subscription information.

18. The method of claim 11 , further comprising receiving the clock quality reporting control information from an application function.

19. 12. The method of claim 11, further comprising receiving the clock quality reporting control information from a core network element once a context for the UE is established, the network device comprising a base station.

20. 12. The method of claim 11, wherein the transmitting the clock quality information comprises transmitting the clock quality information via non-access stratum signaling based at least in part on the network device comprising a core network component.

21. A non-transitory computer-readable medium having program code recorded thereon, the program code being executed by a processor; and program code for receiving clock quality reporting control information; and program code for transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information.

22. the clock quality reporting control information indicates a clock quality detail level including information to be provided to the UE; 22. The non-transitory computer-readable medium of claim 21, wherein the program code for transmitting the clock quality information further comprises program code for transmitting the clock quality information to the UE based at least in part on the clock quality detail level.

23. 23. The non-transitory computer-readable medium of claim 22, wherein the clock quality detail level includes at least one of a clock quality detail or an indication of whether the clock quality meets a clock quality acceptance criterion for the UE.

24. 24. The non-transitory computer-readable medium of claim 23, wherein the indication of whether the clock quality meets the clock quality acceptance criteria for the UE includes an acceptable / unacceptable indication.

25. the program code further comprising: program code for receiving the clock quality acceptance criterion associated with the indication of whether the clock quality meets the clock quality acceptance criterion for the UE; 24. The non-transitory computer-readable medium of claim 23, wherein the program code for transmitting clock quality information to the UE is based at least in part on the clock quality acceptance criteria and the clock quality detail level that includes the indication of whether the clock quality meets the clock quality acceptance criteria for the UE.

26. 1. An apparatus for wireless communication by a network device, comprising: means for receiving clock quality reporting control information; means for transmitting clock quality information to a user equipment (UE) based on the clock quality reporting control information; An apparatus comprising:

27. the clock quality reporting control information indicates a clock quality detail level including information to be provided to the UE; 27. The apparatus of claim 26, wherein the means for transmitting the clock quality information further comprises means for transmitting the clock quality information to the UE based at least in part on the clock quality detail level.

28. 28. The apparatus of claim 27, wherein the clock quality detail level includes at least one of a clock quality detail or an indication of whether the clock quality meets a clock quality acceptance criterion for the UE.

29. 30. The apparatus of claim 28, wherein the indication of whether the clock quality meets the clock quality acceptance criteria for the UE includes an acceptable / unacceptable indication.

30. 29. The apparatus of claim 28, further comprising: means for receiving the clock quality acceptance criterion associated with the indication of whether the clock quality meets the clock quality acceptance criterion for the UE, wherein the means for transmitting clock quality information to the UE is based at least in part on the clock quality acceptance criterion and the clock quality detail level that includes the indication of whether the clock quality meets the clock quality acceptance criterion for the UE.

Images