Clock quality information acquisition using small data transmission, sdt

Abstract

A method, system and apparatus are disclosed. A network node is provided. The network node is configured to receive, via a small data transmission, SDT, procedure, an indication from the wireless device that indicates the wireless device is requesting to receive clock quality information, and cause transmission of clock quality information to the wireless device based on the indication.

Description

[0001] CLOCK QUALITY INFORMATION ACQUISITION USING SMALL DATA TRANSMISSION, SDT

[0002] TECHNICAL FIELD The present disclosure relates to wireless communications, and in particular, to clock quality information acquisition using small data transmission (SDT).

[0003] BACKGROUND

[0004] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0005] The 3GPP SA working group 2 (SA2) group has been discussing a solution for 5G services (5GS) network timing synchronization and reporting, and normative work has started in radio access network (RAN) working groups according to the work item described in RP -230754:

[0006] This corresponds to Key Issue #1 found in the report of the corresponding SA2 study item 3GPP Technical Reference (TR) 23.700 (vl8.0.0): The SA2 intention is to inform about the 5GS timing synchronization status using system information by providing a report ID which the wireless device stores, and upon noticing that the report ID is changed, the wireless device understands the status has changed and obtains new information. If the wireless device is in RRC IDLE or RRC INACTIVE state, the intention is that the wireless device starts a RRC setup or resume procedure and transits to RRC CONNECTED mode to obtain the current timing synchronization information. The network node provides this information using dedicated signaling, as described in 3GPP TR 23.700-25.

[0007] During registration phase, AMF informs the wireless device that it needs to monitor for system information block (SIB) 9 indication, as described in 3GPP TR 23.700-25. RAN2 has started discussing the topic during RAN2#121bis and RAN2#122 and has made the following agreements:

[0008] RAN2#121bis: RAN2#122:

[0009] Agreements

[0010] 1. Update of event ID is informed to UE by normal SI modification procedure.

[0011] 2. Confirm the AS layer of the UE determines if there a change of event ID and / or gNB ID. If there is a change, the AS layer notifies the change in the RAN timing synchronization status to NAS layer. For both IDLE and INACTIVE mode, NAS layer may request the RRC layer to move to RRC CONNECTED

[0012] 3. For RRC_CONNECTED mode UEs, the NW has the necessary information to determine whether to send detailed clock quality information to the UE, (i.e. it may choose to always send update or only when needed) and the details can be left to NW implementation

[0013] 4. Event ID is optional. Under the same gNB, UE considers the change of timing synchronization if event ID field from SIB9 is different. For Further Study (FFS) if gNB always broadcasts event ID

[0014] 5. If the UE is in RRC IN ACTIVE, the UE can acquire clock quality information using the SDT procedure, if it supports and / is configured with SDT procedure.

[0015] Small data transmission (SDT)

[0016] In 3GPP Rel-17, Mobile Originated Small Data Transmission (MO-SDT) was introduced for NR to reduce the signaling overhead for small uplink data payloads, as further described in RP -200954 ‘New Work Item on NR small data transmissions in INACTIVE state’). Two solutions were introduced, random access based SDT (RA-SDT) and configured grant SDT (CG-SDT). RA-SDT means that either legacy 4-step random access channel (RACH) (or 2-step RACH) procedure is used as a baseline but that a userplane data payload can be appended (multiplexed with the RRCResumeRequest message) in Msg3 (or MsgA). CG-SDT means that the wireless device configured via RRC may have periodic CG-SDT occasions which can, contention-free, be used for uplink transmission. In this way, Msgl and Msg2 can be omitted but it is a requirement that the wireless device has a valid Timing Advance (TA) and is uplink synchronized to be able to use the resources for transmission.

[0017] In 3GPP TS 38.401, the FIG. 1 shows the flow in RACH based SDT. In 3GPP TS 38.300 V17.5.0, FIG. 2 shows a flow.

[0018] One of the agreements in RAN2#122 mentions:

[0019] If the UE is in RRC INACTIVE, the UE can acquire clock quality information using the SDT procedure, if it supports and / is configured with SDT procedure. It has not been discussed how the UE “acquires” the clock quality information using the small data transmission (SDT) procedure, as there is no existing method to indicate (during the SDT procedure or otherwise) from the wireless device to the network or network node that the wireless device is interested in receiving the most recent or any clock quality information.

[0020] SUMMARY

[0021] Some embodiments advantageously provide methods, systems, and apparatuses for clock quality information acquisition.

[0022] According to one or more embodiments, the SDT procedure is updated so that the wireless device may indicate through a SDT procedure that it is interested to receive clock quality information from the network node.

[0023] According to one or more embodiments, one or more methods are described to provide the clock quality information to wireless device using a SDT procedure.

[0024] According to one aspect of the present disclosure, a method implemented by a wireless device, that is configured to communicate with a network node is provided. An indication that indicates the wireless device is requesting to receive clock quality information is transmitted via a small data transmission, SDT, procedure. Clock quality information is received based on the indication. At least one action is performed based at least on the clock quality information.

[0025] According to one or more embodiments of this aspect, the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

[0026] According to one or more embodiments of this aspect, the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

[0027] According to one or more embodiments of this aspect, the indication is included in an initial message of the SDT procedure.

[0028] According to one or more embodiments of this aspect, the clock quality information is received in one of a radio resource control, RRC, message generated by a central unit, CU, of the network node.

[0029] According to one or more embodiments of this aspect, the clock quality information is received in a layer 1 message from a distributed unit, DU, of the network node. According to one or more embodiments of this aspect, the wireless device does not transition to a radio resource control, RRC, connected mode during the SDT procedure.

[0030] According to one or more embodiments of this aspect, the wireless device receives the clock quality information while not in a radio resource control, RRC, connected mode.

[0031] According to another aspect of the present disclosure, a wireless device configured to communicate with a network node is provided. The wireless device is configured to: transmit, via a small data transmission, SDT, procedure, an indication that indicates the wireless device is requesting to receive clock quality information; receive clock quality information based on the indication; and perform at least one action based at least on the clock quality information.

[0032] According to one or more embodiments of this aspect, the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

[0033] According to one or more embodiments of this aspect, the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

[0034] According to one or more embodiments of this aspect, the indication is included in an initial message of the SDT procedure.

[0035] According to one or more embodiments of this aspect, the clock quality information is received in one of a radio resource control, RRC, message generated by a central unit, CU, of the network node.

[0036] According to one or more embodiments of this aspect, the clock quality information is received in a layer 1 message from a distributed unit, DU, of the network node.

[0037] According to one or more embodiments of this aspect, the wireless device does not transition to a radio resource control, RRC, connected mode during the SDT procedure.

[0038] According to one or more embodiments of this aspect, the wireless device receives the clock quality information while not in a radio resource control, RRC, connected mode.

[0039] According to another aspect of the present disclosure, a method implemented by a network node that is configured to communicate with a wireless device is provided. An indication from the wireless device that indicates the wireless device is requesting to receive clock quality information from the network node is received via a small data transmission, SDT. Clock quality information for the wireless device is transmitted where the clock quality information is based on the indication.

[0040] According to one or more embodiments of this aspect, the network node is a distributed unit, DU, that is configured to communicate with a central unit, CU.

[0041] According to one or more embodiments of this aspect, in response to the indication received from the wireless device, radio access network, RAN, time synchronization status, TSS, information is transmitted to the CU. The clock quality information is received from the CU, where the clock quality information is based on the RAN TSS information.

[0042] According to one or more embodiments of this aspect, clock quality information and clock quality control information are received from the CU. The received clock quality information is modified based on the clock quality control information and radio access network, RAN, time synchronization status, TSS, information. The transmitted clock quality information corresponds to the modified clock quality information.

[0043] According to one or more embodiments of this aspect, clock quality information and clock quality control information are received from the CU. The clock quality control information is stored in wireless device context.

[0044] According to one or more embodiments of this aspect, clock quality information and clock quality control information are received from the CU. The clock quality information is generated based on the received clock quality information and radio access network, RAN, time synchronization status, TSS, information. The clock quality information is transmitted to the CU for transmission to the wireless device.

[0045] According to one or more embodiments of this aspect, the network node is a central unit, CU, that is configured to communicate with a distributed unit, DU.

[0046] According to one or more embodiments of this aspect, radio access network, RAN, time synchronization status, TSS, information is received from the DU, the clock quality information is determined based on the RAN TSS information; and the clock quality information is transmitted to the DU.

[0047] According to one or more embodiments of this aspect, clock quality information and clock quality control information are transmitted to the DU.

[0048] According to one or more embodiments of this aspect, the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

[0049] According to one or more embodiments of this aspect, the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

[0050] According to one or more embodiments of this aspect, the clock quality information that is transmitted to the wireless device is included in one of a radio resource control, RRC, message or a layer 1 message.

[0051] According to another aspect of the present disclosure, a network node configured to communicate with a wireless device is provided. The network node is configured to receive, via a small data transmission, SDT, procedure, an indication from the wireless device that indicates the wireless device is requesting to receive clock quality information from the network node, and transmit clock quality information for the wireless device, the clock quality information being based on the indication.

[0052] According to one or more embodiments of this aspect, the network node is a distributed unit, DU, that is configured to communicate with a central unit, CU.

[0053] According to one or more embodiments of this aspect, the network node is configured to: in response to the indication received from the wireless device, transmit radio access network, RAN, time synchronization status, TSS, information to the CU; and receive the clock quality information from the CU, the clock quality information being based on the RAN TSS information.

[0054] According to one or more embodiments of this aspect, the network node is further configured to: receive clock quality information and clock quality control information from the CU; modify the received clock quality information based on the clock quality control information and radio access network, RAN, time synchronization status, TSS, information; and the transmitted clock quality information corresponding to the modified clock quality information.

[0055] According to one or more embodiments of this aspect, the network node is further to: receive clock quality information and clock quality control information from the CU; and store the clock quality control information in wireless device context. According to one or more embodiments of this aspect, the network node is further configured to: receive clock quality information and clock quality control information from the CU; generate the clock quality information based on the received clock quality information and radio access network, RAN, time synchronization status, TSS, information; and transmit the clock quality information to the CU for transmission to the wireless device.

[0056] According to one or more embodiments of this aspect, the network node is a central unit, CU, that is configured to communicate with a distributed unit, DU.

[0057] According to one or more embodiments of this aspect, the network node is configured to: receive radio access network, RAN, time synchronization status, TSS, information from the DU; determine the clock quality information based on the RAN TSS information; and transmit the clock quality information to the DU.

[0058] According to one or more embodiments of this aspect, the network node is further configured to transmit clock quality information and clock quality control information to the DU.

[0059] According to one or more embodiments of this aspect, the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

[0060] According to one or more embodiments of this aspect, the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

[0061] According to one or more embodiments of this aspect, the clock quality information that is transmitted to the wireless device is included in one of a radio resource control, RRC, message or a layer 1 message.

[0062] BRIEF DESCRIPTION OF THE DRAWINGS

[0063] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein: FIG. 1 is an example signaling diagram according to 3GPP standard(s);

[0064] FIG. 2 is another example signaling diagram according to 3GPP standard(s);

[0065] FIG. 3 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0066] FIG. 4 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

[0067] FIG. 5 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

[0068] FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

[0069] FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

[0070] FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

[0071] FIG. 9 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0072] FIG. 10 is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure;

[0073] FIG. 11 is a signaling diagram of an example process according to some embodiments of the present disclosure; and

[0074] FIG. 12 is a signaling diagram of another example process according to some embodiments of the present disclosure.

[0075] DETAILED DESCRIPTION As discussed above, there is no existing method to indicate (during the SDT procedure or otherwise) from the wireless device to the network or network node that the wireless device is interested in receiving the most recent (or any) clock quality information.

[0076] The wireless device does not transition to RRC CONNECTED during the SDT, therefore, from a RAN2 perspective, the agreement which covers RRC_CONNECTED mode does not apply to the wireless device performing SDT for the purpose of acquiring the clock quality information.

[0077] At the Initial UE Context Setup procedure, the AMF sends the wireless device Clock Quality Reporting Control Information to NG-RAN node (i.e., network node such as gNB-CU). The clock quality reporting control information indicates the clock quality detail level to provide to the wireless device, i.e. “metrics” or “acceptable / not acceptable indication” and the clock quality acceptance criteria. For RAN TSS reporting towards the wireless device, the network node requires clock quality reporting control information to be stored in the wireless device context. In RRC_CONNECTED, it is the gNB-CU that provides the latest report towards the wireless device via dedicated RRC signaling, e.g., using a DLInformationTransfer procedure. Thus, it may be assumed that the Clock Quality Reporting Control Information is only available in gNB-CU. During SDT, the information about the wireless device's desire to receive the Clock quality information in SDT is missing in gNB-CU in the split NG-RAN node, if the wireless device indicates to gNB- DU, but gNB-DU does not have the wireless device clock quality reporting control information.

[0078] One or more embodiments described herein solve the problem(s) with existing systems at least in part by providing an updated SDT procedure so that the wireless device may indicate through a SDT procedure that it is interested to receive clock quality information from the network node. That is, one or more methods are described herien to provide the clock quality information to the wireless device using a SDT procedure.

[0079] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to clock quality information acquisition. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

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

[0081] In some embodiments, the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B, or one or both of A and B. In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and / or A, B, C or a combination thereof.

[0082] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0083] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0084] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

[0085] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and / or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0086] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

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

[0088] Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

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

[0090] Some embodiments provide clock quality information acquisition using SDT.

[0091] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 3 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

[0092] Also, it is contemplated that a WD 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN. The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and / or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

[0093] The communication system of FIG. 3 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and / or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

[0094] A network node 16 is configured to include a clock quality unit 32 which is configured to perform one or more network node 16 functions as described herein such as with respect to clock quality information acquisition. Network node 16 may also include a centralized unit (CU) 33 (also referred to as gNB-CU 33) and a distributed unit (DU) 34 (also referred to as gNB-DU 34) where a network node 16 is divided into CU 33 and one or more DUs 34. While CU 33 and DU 34 are illustrated in FIG. 4 as being part of a single network node 16, in one or more embodiments, CU 33 and one or more DUs 34 maybe part of different network nodes / entities. A wireless device 22 is configured to include an indication unit 31 which is configured to perform one or more wireless device 22 functions as described herein such as with respect to clock quality information acquisition.

[0095] Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 4. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

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

[0097] The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and / or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include an information unit 54 configured to enable the service provider to perform one or more of storing, receiving, transmitting, forwarding, relaying, determining, analyzing, etc., information related to clock quality information acquisition.

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

[0099] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0100] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include clock quality unit 32 configured to perform one or more network node 16 functions as described herein such as with respect to clock quality information acquisition. In another example, processing circuitry 68 of the network node 16 include CU 33 and DU 34 that are configured to perform one or more network node 16 functions as described herien such as with respect to clock quality acquisition.

[0101] The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0102] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0103] Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

[0104] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include an indication unit 31 configured to perform one or more wireless device 22 functions as described herein such as with respect to clock quality information acquisition.

[0105] In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 4 and independently, the surrounding network topology may be that of FIG. 3.

[0106] In FIG. 4, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

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

[0108] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

[0109] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and / or the network node’s 16 processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the WD 22, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the WD 22.

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

[0111] Although FIGS. 3 and 4 show various “units” such as clock quality unit 32, and indication unit 31 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0112] FIG. 5 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 3 and 4, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 4. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block S106). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08). FIG. 6 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S 112). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

[0113] FIG. 7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block SI 24). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

[0114] FIG. 8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block SI 28). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block SI 30). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block S132).

[0115] FIG. 9 is a flowchart of an example process in a network node 16 according to one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the clock quality unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 is configured to receive (Block SI 34), via a small data transmission, SDT, procedure, an indication from the wireless device 22 that indicates the wireless device 22 is requesting to receive clock quality information from the network node 16, as described herein. Network node 16 is configured to transmit (Block S136) clock quality information to the wireless device 22 based on the indication, as described herein.

[0116] According to one or more embodiments, the network node 16 is a distributed unit, DU, that is configured to communicate with a central unit, CU.

[0117] According to one or more embodiments, the network node 16 is configured to: in response to the indication received from the wireless device, transmit radio access network, RAN, time synchronization status, TSS, information to the CU, and receive the clock quality information from the CU, the clock quality information being based on the RAN TSS information.

[0118] According to one or more embodiments, the network node 16 is further configured to: receive clock quality information and clock quality control information from the CU, modify the received clock quality information based on the clock quality control information and radio access network, RAN, time synchronization status, TSS, information, and the transmitted clock quality information corresponding to the modified clock quality information.

[0119] According to one or more embodiments, the network node 16 is further to receive clock quality information and clock quality control information from the CU, and store the clock quality control information in wireless device context.

[0120] According to one or more embodiments, the network node 16 is further configured to: receive clock quality information and clock quality control information from the CU, generate the clock quality information based on the received clock quality information and radio access network, RAN, time synchronization status, TSS, information, and transmit the clock quality information to the CU for transmission to the wireless device.

[0121] According to one or more embodiments, the network node 16 is a central unit, CU, that is configured to communicate with a distributed unit, DU.

[0122] According to one or more embodiments, the network node 16 is configured to receive radio access network, RAN, time synchronization status, TSS, information from the DU, determine the clock quality information based on the RAN TSS information, and transmit the clock quality information to the DU.

[0123] According to one or more embodiments, the network node 16 is further configured to transmit clock quality information and clock quality control information to the DU.

[0124] According to one or more embodiments, the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

[0125] According to one or more embodiments, the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

[0126] According to one or more embodiments, the indication is received in an initial message of the SDT procedure.

[0127] According to one or more embodiments, the indication is provided using one of random access preamble or random access resource during a random access procedure.

[0128] According to one or more embodiments, the clock quality information that is transmitted to the wireless device 22 is included one of a radio resource control, RRC, message from a central unit of the network node 16.

[0129] According to one or more embodiments, the clock quality information that is transmitted to the wireless device 22 is included in one of a layer 1 message or other message from a distributed unit of the network node 16.

[0130] FIG. 10 is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the indication unit 31), processor 86, radio interface 82 and / or communication interface 60. Wireless device 22 is configured to cause (Block SI 38) transmission, via a small data transmission, SDT, procedure, of an indication (e.g., from the wireless device 22) that indicates the wireless device is requesting to receive clock quality information (e.g., from the network node 16), as described herein. Wireless device 22 is configured to receive (Block SI 40) clock quality information based on the indication, as described herein. Wireless device 22 is configured to perform (Block SI 42) at least one action based at least on the clock quality information, as described herein.

[0131] According to one or more embodiments, the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

[0132] According to one or more embodiments, the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

[0133] According to one or more embodiments, the indication is received in an initial message of the SDT procedure.

[0134] According to one or more embodiments, the indication is provided using one of random access preamble or random access resource during a random access procedure.

[0135] According to one or more embodiments, the clock quality information that is transmitted to the wireless device 22 is included one of a radio resource control, RRC, message from a central unit of the network node 16.

[0136] According to one or more embodiments, the clock quality information that is transmitted to the wireless device 22 is included in one of a layer 1 message or other message from a distributed unit of the network node 16.

[0137] According to one or more embodiments, the wireless device 22 does not transition to a radio resource control, RRC, connected mode during the SDT procedure.

[0138] According to one or more embodiments, the wireless device 22 receives the clock quality information while not in a radio resource control, RRC, connected mode.

[0139] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for clock quality information acquisition. Some embodiments provide clock quality information acquisition.

[0140] One or more wireless device 22 functions described below may be performed by one or more of processing circuitry 84, processor 86, indication unit 31, radio interface 82, etc. One or more network node 16 functions described below may be performed by processing circuitry 68, clock quality unit 32, CU 33, DU 34, processor 70, etc.

[0141] Wireless device 22 side embodiments

[0142] The clock quality information discussed in the embodiments can comprise the information received from the core network 14 which may include for example some or all of the following information: Synchronization State, Parent time source, Clock Quality including: Traceability to GNSS, Traceability to UTC, Frequency stability, PTP (precision time protocol) clock class information and Clock Accuracy, e.g., as specified in 3GPP TS 23.501 V18.2.2 clause 27.2.1. (Table 5.27.1.12-1).

[0143] As used herein, an indication may refer to a flag or a bit or multiple bits in signaling from wireless device 22 to network node 16, which, when received by the network node, can be interpreted as indication of the wireless device 22's interest in receiving clock quality information from network node 16.

[0144] In some embodiments, the small data transmission procedure and / or the messages and / or signaling during the procedure are modified (e.g., compared to existing 3GPP specification) to include an indication from wireless device 22 to network node 16 that wireless device 22 wants to receive clock quality information from the network / network node 16.

[0145] • In one example, the indication is included in the RRCResumeRequest message

[0146] • In one example, a new resume cause (e.g., new function for the ResumeCause field) in RRCResumeRequest is specified for the purpose of indicating wireless device 22 interest in receiving the clock quality information from network node 16 o The new resume cause can be specific to the SDT procedure, or it can be more general and used in other resume cases as well. o In the existing 3GPP specification (e.g., 3GPP TS 38.331 V17.5.0), there are five spare values for ResumeCause of which one could be used for this purpose

[0147] • In one example, a spare bit in the RRCResumeRequest message is used to indicate wireless device 22 interest in receiving the clock quality information from network node 16 o In the existing specification (e.g., 3GPP TS 38.331 V17.5.0), there is one spare bit in the RRCResumeRequest message

[0148] • In one example, a MAC Control Element (MAC CE, see 3GPP TS 38.321 V17.5.0) is used to indicate to network node 16 that wireless device 22 is interested in receiving the clock quality information from network node 16. The MAC CE can be included in the first scheduled message during SDT procedure from wireless device 22 to network node 16 (that is, in the message corresponding to the first step FIG. 1 and / or FIG. 2). Alternatively, the MAC CE is included in some of the subsequent transmissions after the first scheduled message from wireless device 22 to network node 16. o In one example, a new MAC CE is specified in 3GPP TS 38.321 for this purpose o In another example, an existing MAC CE is updated to include a possibility of sending an indication of wireless device 22 interest in receiving clock quality information during the SDT procedure

[0149] • In one example, a 3GPP Rel-18 version of UEAssistancelnformation information element is used thereby using an UL dedicated control channel (DCCH) logical channel message for the delivery of an indication or a new or additional cause value during a SDT procedure. As a variant to this example, an indication is added as an addition to the sequence of a nonSDT-Datalndication .

[0150] In some embodiments, a new procedure and an RRC message are specified which are used by wireless device 22 to trigger network node 16 to send clock quality information to wireless device 22. This new message could be sent in the first message in the SDT procedure, or alternatively it can be a message that wireless device 22 sends as a subsequent transmission after the first scheduled message

[0151] • In one example, a new procedure and RRC message can be used by a wireless device 22 in a general case, that is, also in RRC_CONNECTED mode to request that network node 16 send clock quality information to wireless device 22.

[0152] In one embodiment, wireless device 22 interest in receiving the clock quality information from network node 16 is indicated using a specific random access preamble or random access resources during the random access procedure

[0153] • In one example, a specific preamble or resources are used to indicate that wireless device 22 initiates the SDT procedure and is interested to acquire the clock quality information

[0154] • In another example, a specific preamble or resources are used to indicate that wireless device 22 is interested to acquire the clock quality information.

[0155] In some embodiments, a specific Access Category is used for the purpose of initiating or resuming a connection for the purpose of acquiring clock quality information. Wireless device 22 uses this Access Category in the unified access control procedure to determine whether wireless device 22 is allowed to initiate the connection resume or connection setup towards network node 16 / network.

[0156] Wireless device 22 AS layer determining a change of event ID or network node ID may notify the change in RAN timing synchronization status to NAS layer. For both RRC IDLE and RRC INACTIVE mode, NAS layer may as a result of this indication request the RRC layer to move to RRC CONNECTED. The transition to RRC CONNECTED may use a SDT procedure if configured while conditions for performing either RA-SDT or CG- SDT are fulfilled.

[0157] In one embodiment, wireless device 22 receives the Clock Quality Information via RRC message, for example, in RRCRelease message or through other message that are generated at gNB-CU 33 (e.g., network node 16).

[0158] In one embodiment, wireless device 22 receives the Clock Quality Information via LI message that is generated from gNB-DU 34 (e.g., network node 16).

[0159] In one embodiment, gNB-DU 34 is allowed to include the clock quality information when the message is sent to wireless device 22.

[0160] NG-RAN node (e.g., network node 16) embodiments

[0161] In some embodiments, wireless device 22 in RRC Inactive sends a RRCResumeRequest message using a SDT procedure including an indication that wireless device 22 is capable or interested in receiving clock quality information. As a result of receiving this indication, gNB-DU 34 provides the information to gNB-CU 33 in, e.g., Initial UL RRC Message Transfer or UL Message Transfer procedure. If the Clock Quality Information is sent to wireless device 22 via RRC message generated from gNB- CU, gNB-DU may include the latest RAN time synchronization status information (RAN TSS) . gNB-CU 33 uses this information and the stored UE Clock Quality Control Information to determine and send the clock quality information to wireless device 22. gNB-DU 34 includes the RAN TSS to send to gNB-CU 33 if RAN TSS has not been recently sent, gNB-DU 34 may always include the RAN TSS information. The RAN TSS information can be used to implicitly indicate that wireless device 22 is requesting clock quality information.

[0162] FIG. 11 is a signaling diagram of an example process according to one or more embodiments of the present disclosure.

[0163] In some embodiments, if the Clock Quality Information is sent to wireless device 22 via LI messages that are generated by gNB-DU 34, or in the message generated by gNB-CU 33, but the UE clock quality information can be added / overwritten by gNB-DU 34 before it is sent to wireless device 22, the gNB-CU 33 includes the early stored UE Clock Quality Control Information when it sets up the UE context in gNB-DU 34. gNB- DU 34 could use the Clock Quality Control information and the latest radio access network time synchronization status (RAN TSS) to determine and send the clock quality information to wireless device 22.

[0164] FIG. 12 is a signaling diagram of another example process according to one or more embodiments of the present disclosure.

[0165] In another embodiment, to prepare for providing wireless device 22 using SDT to obtain the clock quality information, gNB-CU 33 sends the UE clock quality control information to gNB-DU 34. gNB-DU 34 could store it in the UE context for CG based SDT, or gNB-DU 34 stores the information with certain UE ID in RACH based SDT or both.

[0166] In another embodiment, during SDT operation, gNB-DU 34 receives the UE Indication for wireless device 22, the UE clock Quality Control Information from gNB- CU 33 (or stored early), uses the latest RAN TSS to generate the UE clock quality information and send it to gNB-CU 33. gNB-CU 33 further sends it to wireless device 22. In another embodiment, if UE does not indicate its capability / interest to obtain clock quality information in SDT, NG-RAN node assumes UE s interest in obtain clock quality information during SDT operation, if the UE has been configured with Clock Quality Control information during RRC-Connected. gNB-CU 33 stores this information and sends the clock quality information in e.g. RRC Release or other RRC message during SDT operation. If in this case the clock quality information is sent in message generated by gNB-DU 34, or the UE clock quality information can be added / overwritten by gNB- DU 34 even if the message is generated by gNB-CU 33, gNB-DU 34 if not received early, receives the UE clock quality control information from gNB-CU 33 during SDT context setup, gNB-DU 34 generates and sends to UE the clock quality information.

[0167] In another embodiment, UE indicates its interest to obtain the clock quality information in SDT via NAS or subscription data. During the Initial Context Setup procedure, CN(e.g. AMF) sends the information to NG-RAN node. NG-RAN node stores the information and uses it later when wireless device 22 uses SDT.

[0168] Below is an existing (3GPP TS 38.331 V17.5.0) definition of the RRCResumeRequest message.

[0169] The following is the definition of the ResumeCause information element (IE), where the bold indicates on example of how to update the existing standard according to one or more embodiments described herein.

[0170] Therefore, according to one or more embodiments, during the SDT procedure, the wireless device is configured to include an explicit indication in the signaling or alternatively a message from wireless device 22 to network node 16 that it wants to receive clock quality information.

[0171] One or more embodiments described herein provide one or more of the following advantages. There will be no ambiguity as to whether wireless device 22 initiating the SDT procedure wants to receive clock quality information. Thus, network node 16 can prepare to send that immediately once network node 16 receives the signaling and messages related to SDT from wireless device 22. Network node 16 can provide a timely reply and include the clock quality information, if needed, and release wireless device 22 back to RRC INACTIVE (i.e. end the SDT procedure). Also, one or more embodiments avoids wireless device 22 from having to go or enter connected mode unnecessarily to acquire the clock quality information.

[0172] Examples

[0173] Example Al . A network node configured to communicate with a wireless device, the network node configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: receive, via a small data transmission, SDT, procedure, an indication from the wireless device that indicates the wireless device is requesting to receive clock quality information from the network node; and cause transmission of clock quality information to the wireless device based on the indication.

[0174] Example A2. The network node of Example Al , wherein the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

[0175] Example A3. The network node of any one of Examples A1-A2, wherein the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

[0176] Example A4. The network node of any one of Examples A1-A3, wherein the indication is received in an initial message of the SDT procedure.

[0177] Example A5. The network node of any one Examples A1-A4, wherein the indication is provided using one of random access preamble or random access resource during a random access procedure.

[0178] Example A6. The network node of any one of Examples A1-A5, wherein the clock quality information that is transmitted to the wireless device is included one of a radio resource control, RRC, message from a central unit of the network node.

[0179] Example A7. The network node of any one of Examples A1-A5, wherein the clock quality information that is transmitted to the wireless device is included in one of a layer 1 message or other message from a distributed unit of the network node. Example Bl. A method implemented in a network node that is configured to communicate with a wireless device, the method comprising: receiving, via a small data transmission, SDT, procedure, an indication from the wireless device that indicates the wireless device is requesting to receive clock quality information from the network node; and causing transmission of clock quality information to the wireless device based on the indication.

[0180] Example B2. The method of Example Bl, wherein the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

[0181] Example B3. The method of Example Bl, wherein the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

[0182] Example B4. The method of any one of Examples B1-B3, wherein the indication is received in an initial message of the SDT procedure.

[0183] Example B5. The method of any one Examples B1-B4, wherein the indication is provided using one of random access preamble or random access resource during a random access procedure.

[0184] Example B6. The method of any one of Examples B1-B5, wherein the clock quality information that is transmitted to the wireless device is included one of a radio resource control, RRC, message from a central unit of the network node.

[0185] Example B7. The method of any one of Examples B1-B5, wherein the clock quality information that is transmitted to the wireless device is included in one of a layer 1 message or other message from a distributed unit of the network node.

[0186] Example Cl . A wireless device (WD) configured to communicate with a network node, the WD configured to, and / or comprising a radio interface and / or processing circuitry configured to: cause transmission, via a small data transmission, SDT, procedure, of an indication from the wireless device that indicates the wireless device is requesting to receive clock quality information from the network node; receive clock quality information to the wireless device based on the indication; and perform at least one action based at least on the clock quality information.

[0187] Example C2. The wireless device of Example Cl, wherein the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

[0188] Example C3. The wireless device of any one of Examples C1-C2, wherein the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

[0189] Example C4. The wireless device of any one of Examples C1-C3, wherein the indication is received in an initial message of the SDT procedure.

[0190] Example C5. The wireless device of any one Examples C1-C4, wherein the indication is provided using one of random access preamble or random access resource during a random access procedure.

[0191] Example C6. The wireless device of any one of Examples C1-C5, wherein the clock quality information that is transmitted to the wireless device is included one of a radio resource control, RRC, message from a central unit of the network node.

[0192] Example C7. The wireless device of any one of Examples C1-C5, wherein the clock quality information that is transmitted to the wireless device is included in one of a layer 1 message or other message from a distributed unit of the network node.

[0193] Example DI . A method implemented in a wireless device that is configured to communicate with a network node, the method comprising: causing transmission, via a small data transmission, SDT, procedure, of an indication from the wireless device that indicates the wireless device is requesting to receive clock quality information from the network node; receiving clock quality information to the wireless device based on the indication; and performing at least one action based at least on the clock quality information.

[0194] Example D2. The method of Example DI, wherein the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

[0195] Example D3. The method of any one of Examples D1-D2, wherein the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

[0196] Example D4. The method of any one of Examples D1-D3, wherein the indication is received in an initial message of the SDT procedure.

[0197] Example D5. The method of any one Examples D1-D4, wherein the indication is provided using one of random access preamble or random access resource during a random access procedure.

[0198] Example D6. The method of any one of Examples D1-D5, wherein the clock quality information that is transmitted to the wireless device is included one of a radio resource control, RRC, message from a central unit of the network node.

[0199] Example D7. The method of any one of Examples D1-D5, wherein the clock quality information that is transmitted to the wireless device is included in one of a layer 1 message or other message from a distributed unit of the network node.

[0200] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

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

[0202] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0203] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0204] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0205] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0206] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0207] Abbreviations that may be used in the preceding description include:

[0208] Abbreviation Explanation gNB Base station in NR

[0209] IE Information Element

[0210] NR New Radio

[0211] QoS Quality of Service

[0212] RRC Radio Resource Control

[0213] TR Technical Report

[0214] TS Technical Specification

[0215] UE User Equipment (Wireless device in 3GPP systems)

[0216] UL Uplink

[0217] URLLC Ultra-Reliable Low Latency Communication

[0218] 3GPP 3rd generation partnership project

[0219] 5GS 5G System

[0220] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

CLAIMS:

1. A method implemented by a wireless device (22), that is configured to communicate with a network node (16), the method comprising: transmitting (SI 38), via a small data transmission, SDT, procedure, an indication that indicates the wireless device (22) is requesting to receive clock quality information; receiving (S140) clock quality information based on the indication; and performing (S142) at least one action based at least on the clock quality information.

2. The method of Claim 1, wherein the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

3. The method of any one of Claims 1-2, wherein the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

4. The method of any one of Claims 1-3, wherein the indication is included in an initial message of the SDT procedure.

5. The method of any one of Claims 1-4, wherein the clock quality information is received in one of a radio resource control, RRC, message generated by a central unit, CU (33), of the network node (16).

6. The method of any one of Claims 1-5, wherein the clock quality information is received in a layer 1 message from a distributed unit, DU (34), of the network node (16).

7. The method of any one of Claims 1-6, wherein the wireless device (22) does not transition to a radio resource control, RRC, connected mode during the SDT procedure.

8. The method of Claims 1-7, wherein the wireless device (22) receives the clock quality information while not in a radio resource control, RRC, connected mode.

9. A wireless device (22) configured to communicate with a network node (16), the wireless device (22) configured to: transmit, via a small data transmission, SDT, procedure, an indication that indicates the wireless device (22) is requesting to receive clock quality information; receive clock quality information based on the indication; and perform at least one action based at least on the clock quality information.

10. The wireless device (22) of Claim 9, wherein the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

11. The wireless device (22) of any one of Claims 9-10, wherein the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

12. The wireless device (22) of any one of Claims 9-11, wherein the indication is included in an initial message of the SDT procedure.

13. The wireless device (22) of any one of Claims 9-12, wherein the clock quality information is received in one of a radio resource control, RRC, message generated by a central unit, CU (33), of the network node (16).

14. The wireless device (22) of any one of Claims 9-13 wherein the clock quality information is received in a layer 1 message from a distributed unit, DU (34), of the network node (16).

15. The wireless device (22) of any one of Claims 9-14, wherein the wireless device (22) does not transition to a radio resource control, RRC, connected mode during the SDT procedure.

16. The wireless device (22) of Claims 9-15, wherein the wireless device (22) receives the clock quality information while not in a radio resource control, RRC, connected mode.

17. A method implemented by a network node (16) that is configured to communicate with a wireless device (22), the method comprising: receiving (SI 34), via a small data transmission, SDT, procedure, an indication from the wireless device that indicates the wireless device is requesting to receive clock quality information from the network node (16); and transmitting (SI 36) clock quality information for the wireless device (22), the clock quality information being based on the indication.

18. The method of Claim 17, wherein the network node (16) is a distributed unit, DU (34), that is configured to communicate with a central unit, CU (33).

19. The method of Claim 18, further comprising: in response to the indication received from the wireless device (22), transmitting radio access network, RAN, time synchronization status, TSS, information to the CU (33); and receiving the clock quality information from the CU (33), the clock quality information being based on the RAN TSS information.

20. The method of any one of Claims 18-19, further comprising: receiving clock quality information and clock quality control information from the CU (33);modifying the received clock quality information based on the clock quality control information and radio access network, RAN, time synchronization status, TSS, information; and the transmitted clock quality information corresponding to the modified clock quality information.

21. The method of any one of Claims 18-20, further comprising: receiving clock quality information and clock quality control information from the CU (33); and storing the clock quality control information in wireless device context.

22. The method of any one of Claims 18-21, further comprising: receiving clock quality information and clock quality control information from the CU; generating the clock quality information based on the received clock quality information and radio access network, RAN, time synchronization status, TSS, information; and transmitting the clock quality information to the CU (33) for transmission to the wireless device (22).

23. The method of Claim 17, wherein the network node (16) is a central unit, CU (33), that is configured to communicate with a distributed unit, DU (34).

24. The method of Claim 23, further comprising: receiving radio access network, RAN, time synchronization status, TSS, information from the DU (34); determining the clock quality information based on the RAN TSS information; and transmitting the clock quality information to the DU (34).

25. The method of any one of Claims 23-24, further comprising transmitting clock quality information and clock quality control information to the DU (34).

26. The method of any one of Claims 17-25, wherein the clock quality information comprises at least one of: synchronization state information, parent timesource, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

27. The method of any one of Claims 17-26, wherein the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

28. The method of any one of Claims 17-27, wherein the clock quality information that is transmitted to the wireless device (22) is included in one of a radio resource control, RRC, message or a layer 1 message.

29. A network node (16) configured to communicate with a wireless device (22), the network node (16) configured to: receive, via a small data transmission, SDT, procedure, an indication from the wireless device (22) that indicates the wireless device (22) is requesting to receive clock quality information from the network node (16); and transmit clock quality information for the wireless device (22), the clock quality information being based on the indication.

30. The network node (16) of Claim 28, wherein the network node (16) is a distributed unit, DU (34), that is configured to communicate with a central unit, CU (33).

31. The network node (16) of Claim 30, wherein the network node (16) is configured to: in response to the indication received from the wireless device (22), transmit radio access network, RAN, time synchronization status, TSS, information to the CU (33); and receive the clock quality information from the CU (33), the clock quality information being based on the RAN TSS information.

32. The network node (16) of any one of Claims 30-31, wherein the network node (16) is further configured to:receive clock quality information and clock quality control information from the CU (33); modify the received clock quality information based on the clock quality control information and radio access network, RAN, time synchronization status, TSS, information; and the transmitted clock quality information corresponding to the modified clock quality information.

33. The network node (16) of any one of Claims 30-32, wherein the network node (16) is further to: receive clock quality information and clock quality control information from the CU (33); and store the clock quality control information in wireless device context.

34. The network node (16) of any one of Claims 30-33, wherein the network node (16) is further configured to: receive clock quality information and clock quality control information from the CU (33); generate the clock quality information based on the received clock quality information and radio access network, RAN, time synchronization status, TSS, information; and transmit the clock quality information to the CU (33) for transmission to the wireless device (22).

35. The network node (16) of Claim 29, wherein the network node (16) is a central unit, CU (33), that is configured to communicate with a distributed unit, DU (34).

36. The network node (16) of Claim 35, wherein the network node (16) is configured to: receive radio access network, RAN, time synchronization status, TSS, information from the DU (34); and determine the clock quality information based on the RAN TSS information; and transmit the clock quality information to the DU (34).

37. The network node (16) of any one of Claims 35-36, wherein the network node (16) is further configured to transmit clock quality information and clock quality control information to the DU (34).

38. The network node (16) of any one of Claims 29-37, wherein the clock quality information comprises at least one of: synchronization state information, parent time source, clock quality, traceability to global navigation satellite system, GNSS, information, traceability to universal time coordinated, UTC, information, frequency stability information, precision time protocol, PTP, clock class information, or clock accuracy information.

39. The network node (16) of any one of Claims 29-38, wherein the indication is included in one of a radio resource control, RRC, request message, a resume cause field in RRC signaling, medium access control, MAC, signaling or wireless device assistance information.

40. The network node (16) of any one of Claims 29-39, wherein the clock quality information that is transmitted to the wireless device is included in one of a radio resource control, RRC, message or a layer 1 message.

Images