Time-quality delivery in wireless communications

Abstract

Time synchronization can be maintained during UE movement by utilizing communication with the target base station. The target base station may receive a time distribution configuration or time distribution area from the network. The time distribution configuration or time distribution area is used to determine the distribution of time quality information that can be utilized by the UE. The distribution of time quality information is directed to the UE. Reception occurs during the UE handover procedure or during the base station path switching procedure for UE handover.

Description

Technical Field

[0001] Technical Field This specification generally relates to wireless communication. More specifically, time synchronization is provided to devices on a network.

Background Art

[0002] Background Wireless communication technology is leading the world towards a more connected and networked society. Wireless communication relies on efficient network resource management and allocation between user mobile stations and wireless access network nodes (including, but not limited to, wireless base stations). The new generation of networks is expected to provide high-speed, low-latency, and ultra-high reliability communication capabilities to meet the requirements from various industries and users. User mobile stations or user equipment (UE) are becoming more complex, and the amount of data to be communicated is constantly increasing. To improve communication, meet the reliability requirements of vertical industries, and support new generation network services, it is necessary to make improvements to maintain and guarantee service quality standards.

Summary of the Invention

Means for Solving the Problems

[0003] Summary This document relates to a method, system, and device for time synchronization between a network and a user equipment (UE). By utilizing communication with a target base station, time synchronization can be maintained during the movement of the UE. The target base station may receive a time distribution configuration or a time distribution area from the network. The time distribution configuration or the time distribution area is used to determine the distribution of time quality information that can be utilized by the UE.

[0004] In one embodiment, a wireless communication method includes receiving a time distribution configuration at a target base station and the target base station deciding to distribute time quality information based on the time distribution configuration. The distribution of time quality information is to a user equipment (UE). Reception occurs during a UE handover procedure or during a base station path switching procedure for a UE handover. The time distribution configuration is transmitted from a source base station or a core network (CN). The time distribution configuration includes clock quality acceptance criteria and / or clock quality levels. The user equipment (UE) can then determine whether it needs to switch to a different clock source or whether the current value of the clock quality level meets the requirements of an ongoing time-constrained service. The clock quality acceptance criteria include traceability to a parent time source, Coordinated Universal Time (UTC) or a Global Navigation Satellite System (GNSS), synchronization status, clock accuracy, or frequency stability. The clock quality level includes a clock quality metric or an instruction for acceptance, which instructs what should be provided to the user equipment (UE). The instruction for acceptance indicates the current timing synchronization status based on the clock quality acceptance criteria. The bit sequence indicates one or more clock quality metrics to be reported to the UE, and each position in the bitmap indicates which clock quality metric is required. The method includes the source base station sending a handover request message containing the time distribution configuration to the core network (CN), and the target base station receiving the time distribution configuration provided by the source base station in the handover request message sent by the CN. The method includes the core network (CN) determining the time distribution configuration after receiving the handover request message or path switching request message, and the target base station receiving the time distribution configuration contained in the handover request message or path switching acknowledgment message from the CN. The method includes the source base station sending a handover request message containing the time distribution configuration, and the target base station receiving the time distribution configuration from the source base station.The core network (CN) provides the source base station with a time distribution configuration before it is received at the target base station. The method involves receiving an NG Application Protocol (NGAP) message from the core network (CN) that includes a time distribution start or stop instruction for the user equipment (UE), the start or stop instruction activating or deactivating the time-quality distribution function for the UE.

[0005] In another embodiment, a wireless communication method includes, at a target base station, receiving a time distribution area and, at the target base station, deciding to distribute time quality information based on the time distribution area. The distribution of time quality information is to a user device (UE). Reception occurs during a UE handover procedure or during a base station path switching procedure for a UE handover procedure. The time distribution area is transmitted from a source base station or a core network (CN). The time distribution area includes a list of tracking areas, a list of cells, a list of standalone non-public networks (SNPNs), or a list of closed access groups (CAGs) for integrated non-public networks. The method includes sending time quality information to a user device (UE) when the UE is within a coverage area indicated by the time distribution area. The method includes, at the source base station, sending a handover request message containing the time distribution area to the core network (CN), and at the target base station, receiving the time distribution area provided by the source base station in a handover request message sent by the CN. The method includes the Core Network (CN) determining a time distribution area after receiving a handover request message or a path switching request message, and the target base station receiving the time distribution area contained in the handover request message or path switching acknowledgment message from the CN. The method also includes the source base station sending a handover request message containing the time distribution area, and the target base station receiving the time distribution area from the source base station. The Core Network (CN) provides the time distribution area to the source base station before reception at the target base station. The method also includes receiving an NG Application Protocol (NGAP) message from the Core Network (CN) containing a time distribution start or stop instruction for a user equipment (UE), the start or stop instruction activating or deactivating the time-quality distribution function for the UE.In another embodiment, the wireless communication device comprises a processor and memory, the processor being configured to read code from the memory and to perform one of the methods for wireless communication described herein.

[0006] In another embodiment, the wireless communication device comprises a processor and memory, and the processor is configured to read code from the memory and implement one of the embodiments described above.

[0007] In another embodiment, the computer program product includes computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the embodiments described above.

[0008] In some embodiments, there exists a wireless communication device comprising a processor and memory, the processor being configured to read code from memory and to perform any method described in any of the embodiments. In some embodiments, a computer program product includes computer-readable program medium code stored thereon, the code causing the processor to perform any method described in any of the embodiments when executed by the processor. The above and other embodiments and their implementations are described in more detail in the drawings, the text of the specification and the claims. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 shows an example of a base station. [Figure 2] Figure 2 shows an example of a random access (RA) messaging environment. [Figure 3] Figure 3 shows one embodiment of a wireless network system architecture. [Figure 4] Figure 4 shows an example of time-based delivery configuration information. [Figure 5] Figure 5 shows an example of time-based distribution area information. [Figure 6]Figure 6 shows one embodiment of a network that provides information to base stations for time synchronization. [Figure 7] Figure 7 shows one embodiment of a network for updating information to base stations for time synchronization. [Figure 8] Figure 8 shows one embodiment for time-quality delivery during handover. [Figure 9] Figure 9 shows another embodiment for time-quality delivery during handover with network-based information storage. [Figure 10] Figure 10 shows one embodiment for continuity of time-quality delivery during handover. [Figure 11] Figure 11 shows another embodiment for continuity of time-quality delivery during handover with network-based information storage. [Figure 12] Figure 12 shows one embodiment for starting / stopping time distribution to user equipment (UE). [Modes for carrying out the invention]

[0010] Detailed explanation This disclosure is described below in detail with reference to the accompanying drawings, which constitute part of this disclosure and illustrate specific examples of embodiments. However, it should be noted that this disclosure may be embodied in various different forms, and therefore the subject matter covered or claimed is not limited to any of the embodiments described below.

[0011] Throughout this specification and the claims, terms may have nuances implied or suggested in context beyond their expressly stated meanings. Similarly, the phrases “in one embodiment” or “in several embodiments” used herein do not necessarily refer to the same embodiment, and the expressions “in another embodiment” or “in other embodiments” used herein do not necessarily refer to different embodiments. The phrases “in one implementation” or “in several implementations” used herein do not necessarily refer to the same implementation, and the expressions “in another implementation” or “in other implementations” used herein do not necessarily refer to different implementations. For example, the claimed subject matter is intended to include typical embodiments or combinations of implementations, either in whole or in part.

[0012] In general, terms can be understood at least partially from their use in context. For example, terms such as “and,” “or,” and “and / or,” when used herein, may have a variety of meanings that may at least partially depend on the context in which such terms are used. Typically, when “or” is used to relate a list such as A, B, or C, it is intended to mean A, B, and C, used here in an inclusive sense, as well as A, B, or C, used here in an exclusive sense. Furthermore, the terms “one or more” or “at least one” as used herein may be used at least partially, depending on the context, to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” and “the” can also be understood, at least partially, depending on the context, to convey either a singular or plural usage. Furthermore, the terms “based on” or “determined by” may be understood not necessarily to convey an exclusive set of factors, but rather, depending at least partially on the context, may allow for the presence of additional factors that are not necessarily explicitly stated.

[0013] Radio Resource Control ("RRC") is a protocol layer between the UE and the base station at the IP level (network layer). Various Radio Resource Control (RRC) states can exist, including the RRC_CONNECTED state, the RRC_INACTIVE state, and the RRC_IDLE state. RRC messages are transmitted via the Packet Data Convergence Protocol ("PDCP"). As described, the UE can transmit data using the Random Access Channel ("RACH") protocol scheme or the Configuration Grant ("CG") scheme. CG can be used to reduce waste of periodically allocated resources by allowing multiple devices to share periodic resources. A base station or node may allocate CG resources to eliminate packet transmission delays and increase the utilization of allocated periodic radio resources. The CG scheme is just one example of a protocol scheme for communication; other examples are possible, including but not limited to RACH. Wireless communication described herein may be via radio access.

[0014] New radio access ("NR") includes the ability to have time synchronization. Time synchronization between the network and user equipment (UE) becomes more efficient by considering the UE's time synchronization area. A time synchronization area is a location where the UE can receive on-demand time synchronization. When a time synchronization area is communicated, such as through notice or instruction, time synchronization signals may only be sent when the UE is within the area. Time synchronization instructions may be used during handover.

[0015] There can be different ways to provide a time synchronization service to a device (e.g., a user equipment). The time synchronization signal may be referred to as access stratum time allocation. The access stratum time allocation may be deployed from a preconfigured radio access network (RAN) node. User equipment (UE) within an area may receive precise time information when it is within the RAN coverage. When the UE leaves the area, the time synchronization signal is area-limited and can no longer be accessed. The embodiments described below enable the transmission of a time synchronization area for more efficient time synchronization distribution. In addition, UEs with mobility (e.g., handover) can also have time synchronization. The RAN may be part of a wireless communication system that connects UE devices to other parts of the network via a wireless or wireline connection. FIG. 1 illustrates an example of an NG-RAN or a base station. FIG. 2 illustrates an example of a random access messaging environment. FIG. 3 illustrates an example of an architecture for time synchronization signaling. FIGS. 6 to 12 illustrate examples of wireless communication for improving time synchronization using information from FIGS. 4 to 5.

[0016] FIG. 1 shows an example of a base station 102. The base station 102 may also be referred to as a wireless network node or a next-generation radio access network (「NG-RAN」) node. In the context of mobile communication, the base station 102 may be further identified as a nodeB (NB, e.g., eNB or gNB). An example of a base station may include a wireless Tx / Rx circuit 113 for communicating with a user equipment (UE) 104. The base station may also include a network interface circuit 116 for coupling the base station to a core network 110, e.g., an optical or wired interconnect, Ethernet (registered trademark), and / or other data transmission media / protocols.

[0017] The base station may also include a system circuit 122. The system circuit 122 may include (one or more) processors 124 and / or memory 126. Memory 126 may include arithmetic operations 128 and control parameters 130. Arithmetic operations 128 may include instructions to be executed on one or more of the processors 124 to support the functions of the base station. For example, the arithmetic operations may process random access transmission requests from multiple UEs. Control parameters 130 may include parameters or support the execution of arithmetic operations 128. For example, control parameters may include network protocol settings, random access messaging format rules, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0018] Figure 2 shows an example of a random access messaging environment 200. In a random access messaging environment, UE 104 can communicate with base station 102 via random access channel 252. In this example, UE 104 supports one or more subscriber identification modules (SIMs), such as SIM1 202. Electrical and physical interfaces 206 connect SIM1 202 to the rest of the user equipment hardware, for example, via system bus 210.

[0019] Mobile device 200 includes a communication interface 212, system logic 214, and a user interface 218. System logic 214 can include any combination of hardware, software, firmware, or other logic. System logic 214 can be implemented, for example, using one or more system-on-chips (SoCs), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. System logic 214 is part of an implementation of any desired functionality in UE104. In this regard, examples of system logic 214 can include logic for decoding and playing music and video, such as decoding and playing MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV, executing applications, receiving user input, storing and retrieving application data, establishing, maintaining, and terminating a data connection for a cellular phone call or, as an example, an Internet connection, establishing, maintaining, and terminating a wireless network connection, a Bluetooth® connection, or other connections, and facilitating the display of relevant information on user interface 218. User interface 218 and input 228 can include a graphical user interface, a touch-sensitive display, tactile feedback or other tactile output, voice or face recognition input, buttons, switches, speakers, and other user interface elements. Further examples of input 228 include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (such as IR sensors), and other types of input.

[0020] The system logic 214 may include one or more processors 216 and memory 220. Memory 220 stores, for example, control instructions 222 that the processor 216 executes to perform a desired function of the UE 104. Control parameters 224 provide and specify configuration and operation options for the control instructions 222. Memory 220 may also store BT, WiFi, 3G, 4G, 5G, or other data 226 that the UE 104 sends or receives via the communication interface 212. In various implementations, system power may be supplied by an energy storage device such as a battery 282.

[0021] In the communication interface 212, the radio frequency (RF) transmit (Tx) and receive (Rx) circuit 230 handles the transmission and reception of signals via one or more antennas 232. The communication interface 212 may include one or more transceivers. The transceivers may be wireless transceivers that include modulation / demodulation circuits, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving via one or more antennas or (in the case of some devices) via a physical (e.g., wired) medium.

[0022] The transmitted and received signals may conform to any of a diverse array of formats, protocols, modulation (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. One specific example is that the communication interface 212 may include transceivers supporting transmission and reception in 2G, 3G, BT, WiFi, Universal Mobile Communications System (UMTS), High-Speed ​​Packet Access (HSPA)+, and 4G / Long-Term Evolution (LTE) standards. However, the technologies described below are applicable to other wireless communication technologies, whether they originate from the Third Generation Partnership Project (3GPP®), the GSM® Association, 3GPP2, IEEE, or other partnerships or standardization bodies.

[0023] Figure 3 shows one embodiment of a wireless network system architecture. This architecture is merely an example, and there may be more or fewer components to implement the embodiments described herein. Interconnections or communications between components are identified as N1, N2, N4, N6, N7, N8, N10, and N11, which may be referenced in the text or other figures of the specification. Figure 2 illustrates an example of a user device ("UE") 104. UE 302 is a device that accesses the wireless network (e.g., 5GS) and obtains services via an NG-RAN node or base station 304. UE 302 interacts with the core network's Access and Mobility Control Function ("AMF") 306 via NAS signaling. Figure 1 illustrates an example of a base station or NG-RAN 102. The NG-RAN node 304 is responsible for air interface resource scheduling and air interface connection management of the network accessed by the UE. The base station 304 may also be referred to as a Next Generation Radio Access Network ("NG-RAN") node and can provide time synchronization signals to user equipment (UEs). These time synchronization signals may be provided via system information blocks (SIBs) or radio resource control (RRC) messages.

[0024] The AMF306 includes the following functions: registration management, connection management, reachability management, and mobility management. The AMF306 also performs access authentication and access permission. The AMF306 is the NAS security termination and relays session management NAS between the UE302 and SMF308, etc.

[0025] The SMF308 includes the following functions: session establishment, modification and release; UE IP address assignment and management (including permission for arbitrary selection); uplink function selection and control; and downlink data notification. The User Plane Functions ("UPF") 310 includes the following functions: anchor points for intra-RAT / inter-RAT mobility; packet routing and forwarding; traffic usage reporting; QoS processing for the user plane; and buffering of downlink packets and triggering of downlink data notification. The Integrated Data Management ("UDM") 312 manages subscription profiles for UEs. Subscriptions include data used for mobility management (e.g., restricted areas) and session management (e.g., QoS profiles). Subscription data also includes slice selection parameters used by the AMF306 to select the appropriate SMF308. The AMF306 and SMF308 obtain subscriptions from the UDM312. Subscription data may be stored in an integrated data repository with the UDM312, which uses such data when it receives a request from the AMF306 or SMF308. The Policy Control Function ("PCF") 314 includes the following functions: supporting an integrated policy framework for managing network behavior; providing policy rules for controlling (one or more) plane functions to enforce policy rules; and implementing a front-end for accessing subscription information related to policy decisions in the user data repository. The Network Exposure Function ("NEF") 316 is deployed to exchange information with external third parties as needed. In one embodiment, the Application Function ("AF") 316 can store application information in the integrated data repository via the NEF. The UPF 310 communicates with the data network 318.

[0026] When a time synchronization service is configured for a UE, the NG-RAN (Next Generation Radio Access Network) or base station may need to provide the UE with precise time information and network time synchronization status (e.g., clock quality level). The precise time information sent to the UE may be generated by the NG-RAN based on a time source used in the NG-RAN, which can receive its clock information from a Global Navigation Satellite System (GNSS) receiver. Alternatively, the time source in 5G may be the General Purpose Precision Time Protocol (gPTP) or the IEEE standard for precision clock synchronization protocols (IEEE Std 1588). The clock quality level of these time sources may also be provided to the UE as part of the network time synchronization status.

[0027] When a user equipment (UE) subscribes to a time synchronization service within a specific area, the network may need to ensure that the UE can continuously receive the time synchronization service within the designated area while the UE is mobile. In some embodiments, the target base station may not know whether the UE has access to the time synchronization service. Therefore, the UE's time synchronization service may be maintained by utilizing communications of time information or the configuration of the time distribution area.

[0028] Figures 4 and 5 illustrate examples of information that may be communicated to maintain time synchronization for user equipment (UEs). Figure 4 shows an example of time distribution configuration information. The time distribution configuration may include time distribution instructions that indicate the need to provide timing information to the UE. The time distribution configuration may include an air interface time synchronization error budget. The UE may use this value to assess the correct time. The time distribution configuration may include a clock quality acceptance criterion. This criterion may be defined based on at least one of the following attributes: parent time source, traceability to UTC and / or GNSS, synchronization status, clock accuracy, and / or frequency stability. The time distribution configuration may include a clock quality level report type that indicates whether and what clock quality information should be provided to the UE. The time distribution configuration may include a clock quality metric or an acceptable / unacceptable instruction. The clock quality metric may be used to reflect the current base station timing synchronization status. The metric may include at least one of the following information: clock accuracy, traceability to UTC and GNSS, frequency stability, parent time source, and synchronization status, and / or an acceptable indication indicates that the current timing synchronization status matches the clock quality acceptance criteria.

[0029] The following table contains an example of time-delivery configuration information for a UE. As described, a base station can provide time quality information to the UE based on the time-delivery configuration information. In the table, a bit sequence can be used to indicate one or more clock quality metrics that need to be reported to the UE, with each position in the bitmap indicating whether one type of metric is required. [Table 1]

[0030] Figure 5 shows an example of time-delivery area information. Time-delivery areas can provide timing information to UEs when they are within a specific coverage area. This may include a list of tracking areas (TAs), a list of cells, a list of standalone non-public networks (SNPNs), and / or a list of closed access groups (CAGs) for integrated non-public networks.

[0031] Figure 6 shows one embodiment of a network that provides information to a base station for time synchronization. In block 602, the user equipment (UE) initiates the initial packet data unit (PDU) session setup procedure. The session may be between the UE, the base station, and the core network (CN). In block 604, the Access and Mobility Control Function (AMF) sends a context setup message (e.g., an initial context setup request) to the base station. The context setup message requests the setup of the UE context. This message may include the time distribution configuration and / or time distribution area information described with respect to Figures 4 and 5. In block 606, the PDU session is successfully established between the UE, the base station, and the CN. The UE can receive or transmit data to and from the base station. In block 608, the time distribution configuration and / or time distribution area information described with respect to Figures 4 and 5 is used to determine when to send time quality information. For example, when a UE connection is first established and the UE enters a connected state (e.g., an RRC connection), when the base station's current time synchronization status changes, when the base station determines the UE's clock quality metric, whether the clock quality is acceptable to the UE or not, and / or when the UE is within a coverage area indicated by a time distribution area, the base station decides to send time quality information to the UE. The time quality information may include at least one of the air interface time synchronization error budget or the clock quality level. In block 610, the base station sends a message (e.g., an RRC message) to the UE that contains time quality information.

[0032] Figure 7 shows one embodiment of a network for updating information to a base station for time synchronization. In block 702, one or more sessions (e.g., PDU sessions) are successfully established between the UE, the base station, and the core network (CN). In block 704, a context correction message (e.g., a UE context correction request) may include time distribution configuration and / or time distribution area information as described with respect to Figures 4 and 5. The CN may use the new time distribution configuration and / or time distribution area information for the UE. The CN sends a context correction request message to the base station to request a correction of the UE context. In block 706, upon receiving the updated time distribution configuration and / or UE time distribution area information, the base station updates the information in the stored UE context. In block 708, the base station sends a context correction response (e.g., a UE context correction response) to the CN.

[0033] Figure 8 shows one embodiment for time-quality delivery during handover. Figure 9 illustrates an alternative embodiment in which the CN stores information as described later. Both embodiments support continuity of time-quality delivery to the UE during handover. In block 802, the UE connects to the source base station. In block 804, the source base station determines the target base station for handover. This determination may occur during UE mobility. If there is no interface connection (e.g., Xn interface) between the source base station and the target base station, the source base station may send a handover message (e.g., Handover Required) to the core network (CN) requesting a handover to the target base station. This handover message to the CN in block 804 may include time-delivery configuration and / or time-delivery area information as described with respect to Figures 4-5.

[0034] After receiving a handover message (e.g., a handover request message), the CN sends a handover request message (e.g., a handover request message via the NG interface) to the target base station in block 806 to request resources for the UE at the target base station. This message includes the UE's time-delivery configuration and / or time-delivery area information. In block 808, if the target base station is able to accept the handover, the target base station sends an acknowledgment message (e.g., a handover request acknowledgment message) to the CN. In block 810, the handover from the source base station to the target base station takes place.

[0035] Time distribution configuration and / or time distribution area information are used in block 812 to determine when to send time quality information. For example, the decision may be that, after a handover, when the base station's current time synchronization status changes, when the base station determines the UE's clock quality metric, whether the clock quality is acceptable to the UE or not, and / or when the UE is within the coverage area indicated by the time distribution area, the base station decides to send time quality information to the UE. The time quality information may include at least one of the air interface time synchronization error budget or the clock quality level. In block 814, the target base station sends a message (e.g., an RRC message) to the UE that contains time quality information in the message. Based on the received time quality information, the UE can determine whether it needs to switch to a different clock source or whether the current time quality meets the requirements of an ongoing time-constrained service.

[0036] Figure 9 shows another embodiment for time-quality delivery during handover with network-based information storage. In Figure 9, the core network (CN) stores the time-delivery configuration and / or time-delivery area information described in relation to Figures 4-5, rather than the information being transmitted from the source base station to the CN along with the handover requirement message, as in the embodiment of Figure 8. In this embodiment, the CN can directly transfer this stored information to the target base station.

[0037] In block 902, the UE connects with the source base station. In block 904, the source base station determines the target base station for handover. This determination may occur during UE mobility. If there is no interface connection (e.g., Xn interface) between the source base station and the target base station, the source base station may send a handover message (e.g., Handover Required) to the core network (CN) to request a handover to the target base station. In this embodiment, this message does not include time distribution configuration and / or time distribution area information stored by the CN.

[0038] After receiving a handover message (e.g., a handover required message), in block 906, the CN sends a handover request message (e.g., a handover request message via the NG interface) to the target base station to request resources for the UE at the target base station. This message includes the time-delivery configuration and / or time-delivery area information of the UE stored by the CN. In block 908, if the target base station is able to accept the handover, the target base station sends an acknowledgment message (e.g., a handover request acknowledgment message) to the CN. In block 910, the handover from the source base station to the target base station takes place.

[0039] Time distribution configuration and / or time distribution area information are used in block 912 to determine when to send time quality information. For example, the decision may be that, after a handover, when the base station's current time synchronization status changes, when the base station determines the UE's clock quality metric, whether the clock quality is acceptable to the UE or not, and / or when the UE is within the coverage area indicated by the time distribution area, the base station decides to send time quality information to the UE. The time quality information may include at least one of the air interface time synchronization error budget or the clock quality level. In block 914, the target base station sends a message (e.g., an RRC message) to the UE that contains time quality information within the message. Based on the received time quality information, the UE can determine whether it needs to switch to a different clock source or whether the current time quality meets the requirements of an ongoing time-constrained service.

[0040] Figure 10 shows an embodiment for continuity of time-quality delivery during handover. Figure 11 illustrates an alternative embodiment in which the CN stores information as described later. Both embodiments support continuity of time-quality delivery to the UE during handover. In block 1002, the UE connects to the source base station. In block 1004, the source base station determines the target base station for the handover. This determination occurs during UE mobility. If there is an interface connection (Xn interface) between the source base station and the target base station, the source base station sends a handover request message (e.g., a handover request message) to the base station to request the handover of the UE to the target base station. This handover request message includes the time-delivery configuration and / or time-delivery area information described with respect to Figures 4-5. In block 1006, if the target base station can accept the handover, the target base station sends a handover acknowledgment message (e.g., a handover request acknowledgment message) to the source base station. In block 1008, the handover from the source base station to the target base station takes place.

[0041] After the handover, in block 1010, the target base station notifies the new serving base station by sending a path switching message (e.g., a path switching request message) to the CN. In block 1012, the CN sends a path switching acknowledgment message (e.g., a path switching request acknowledgment message) to the target base station. The time distribution configuration and / or time distribution area information is used in block 1014 to determine when to send time quality information. For example, the decision may be that after the handover, when the current time synchronization status of the base station changes, when the base station determines the clock quality metric of the UE, whether the clock quality is acceptable to the UE or not, and / or when the UE is within the coverage area indicated by the time distribution area, the base station decides to send time quality information to the UE. The time quality information may include at least one of the air interface time synchronization error budget or the clock quality level. In block 1016, the target base station sends a message (e.g., an RRC message) to the UE that includes time quality information in the message. Based on the received time quality information, the UE can determine whether it needs to switch to a different clock source or whether the current time quality meets the requirements of the ongoing time-constrained service.

[0042] Figure 11 shows another embodiment for continuity of time-quality delivery during handover with network-based information storage. In Figure 11, the core network (CN) stores the time-delivery configuration and / or time-delivery area information described in relation to Figures 4-5, rather than having that information transmitted with the handover request message as in the embodiment of Figure 10. In this embodiment, the CN can transfer this stored information to the target base station in a path switching acknowledgment message.

[0043] In block 1102, the UE connects with the source base station. In block 1104, the source base station determines the target base station for the handover. This determination occurs during UE mobility. If there is an interface connection (Xn interface) between the source base station and the target base station, the source base station sends a handover request message (e.g., a handover request message) to the base station to request the handover of the UE to the target base station. In this embodiment, this message does not include time distribution configuration and / or time distribution area information stored by the CN. In block 1106, if the target base station is able to accept the handover, the target base station sends a handover acknowledgment message (e.g., a handover request acknowledgment message) to the source base station. In block 1108, the handover from the source base station to the target base station takes place.

[0044] After the handover, in block 1110, the target base station sends a path switching message (e.g., a path switching request message) to the CN to notify the new serving base station. In block 1112, the CN sends a path switching acknowledgment message (e.g., a path switching request acknowledgment message) to the target base station. In this embodiment, the core network (CN) stores the time distribution configuration and / or time distribution area information described with respect to Figures 4-5, which is then included in block 1112 along with the path switching acknowledgment message (e.g., a path switching request acknowledgment message) to the target base station.

[0045] Time distribution configuration and / or time distribution area information are used in block 1114 to determine when to send time quality information. For example, the decision may be that after a handover, when the base station's current time synchronization status changes, when the base station determines the UE's clock quality metric, whether the clock quality is acceptable to the UE or not, and / or when the UE is within the coverage area indicated by the time distribution area, the base station decides to send time quality information to the UE. The time quality information may include at least one of the air interface time synchronization error budget or the clock quality level. In block 1116, the target base station sends a message (e.g., an RRC message) to the UE that contains time quality information in the message. Based on the received time quality information, the UE can determine whether it needs to switch to a different clock source or whether the current time quality meets the requirements of an ongoing time-constrained service.

[0046] Figure 12 shows one embodiment for starting / stopping time distribution to a user device (UE). In block 1202, the UE connects to a base station in a session between core networks (CNs). In block 1204, the CN sends an NGAP message to the base station. The NGAP message may include time distribution configuration and / or time distribution area information as described with respect to Figures 4-5. Furthermore, the NGAP message in block 1204 includes a time distribution start / stop instruction for the UE. This may be provided separately from or together with the time distribution configuration and / or time distribution area information. In block 1206, upon receiving a time distribution stop instruction, the base station can deactivate the time quality distribution function of this UE and stop sending time quality information to the UE. In block 1206, upon receiving a time distribution start instruction, the base station can activate the time quality distribution function of this UE and start sending time quality information to the UE.

[0047] The aforementioned systems and processes may be encoded in computer-readable media such as signal-holding media or memory, programmed in devices such as one or more integrated circuits or one or more processors, or processed by a controller or computer. The data may be analyzed in a computer system and used to generate a spectrum. If the method is performed by software, the software may reside in non-volatile or volatile memory communicating with a storage device, synchronous device, communication interface, or transmitter, or in memory interfaced to such devices. Circuits or electronic devices are designed to send data to another location. Memory may contain an ordered list of executable instructions for implementing a logical function. The described logical function or any system element may be implemented via optical circuits, digital circuits, source code, analog circuits, analog sources such as analog electrical signals, audio signals, video signals, or a combination thereof. The software may be embodied in any computer-readable or signal-holding media for use by or in connection with an instruction-executable system, apparatus, or device. Such a system may include a computer-based system, a system including a processor, or another system capable of selectively fetching instructions from an instruction-executable system, apparatus, or device that can also execute instructions.

[0048] "Computer-readable medium," "machine-readable medium," "propagating signal" medium, and / or "signal-holding medium" may include any device that stores, communicates, propagates, or transports software for use by or in connection with an instruction-executable system, apparatus, or device. Machine-readable medium may be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. A non-exclusive list of examples of machine-readable mediums includes electrical connections "electronic" having one or more wires, portable magnetic or optical disks, volatile memory such as random access memory "RAM", read-only memory "ROM", erasable programmable read-only memory (EPROM or flash memory), or optical fibers. Machine-readable medium may also include tangible medium on which software is printed, so that the software may be electronically stored as an image or in another format (e.g., via optical scanning), then compiled, and / or interpreted, or otherwise processed. The processed medium may then be stored in computer and / or machine memory.

[0049] The examples of embodiments described herein are intended to provide a general understanding of the structures of various embodiments. These example drawings are not intended to serve as a complete description of all elements and features of devices and systems utilizing the structures or methods described herein. Many other embodiments will be apparent to those skilled in the art upon consideration of this disclosure. Other embodiments may be used and derived from this disclosure, thereby making structural and logical substitutions and modifications without departing from the scope of this disclosure. Furthermore, the example drawings are merely illustrative and may not be drawn to scale. Certain parts in the example drawings may be exaggerated, while others may be minimized. Therefore, this disclosure and drawings should be considered illustrative, not restrictive.

[0050] One or more embodiments of this disclosure may be referred to herein, individually and / or collectively, by the term “invention,” merely for convenience and without the intention of voluntarily limiting the scope of this application to any particular invention or inventive concept. Furthermore, while certain embodiments are illustrated and described herein, it should be understood that any subsequent arrangement designed to achieve the same or similar objectives may be used instead of the particular embodiments shown. This disclosure is intended to cover all possible subsequent adaptations or modifications of various embodiments. Combinations of the embodiments described herein, and other embodiments not specifically described herein, will be apparent to those skilled in the art upon consideration of the description.

[0051] The phrase "combined with ~" is defined as meaning directly connected or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware-based and software-based components. Modifications to the arrangement and types of components may be made without departing from the spirit or scope of the claims described herein. Additional, different, or fewer components may be provided.

[0052] The subject matter disclosed above should be considered illustrative rather than restrictive, and the appended claims are intended to cover all such modifications, extensions, and other embodiments that fall within the true spirit and scope of the invention. Therefore, to the maximum extent permitted by law, the scope of the invention should be determined by the broadest permissible interpretation of the following claims and their equivalents, and not limited or restricted by the foregoing detailed description. While various embodiments of the invention have been described, it will be apparent to those skilled in the art that many more embodiments and implementations are possible within the scope of the invention. Therefore, the invention should not be limited in light of the appended claims and their equivalents.

Claims

1. A wireless communication method, At the target base station, receive the time distribution configuration, The target base station determines the distribution of time quality information based on the time distribution configuration. Methods that include...

2. The method according to claim 1, wherein the distribution of the time quality information is directed to a user device (UE).

3. The method according to claim 2, wherein the receiving occurs during a UE handover procedure or during a base station path switching procedure for a UE handover.

4. The method according to claims 1 to 2, wherein the time distribution configuration is transmitted from a source base station or core network (CN).

5. The aforementioned time-based distribution configuration is: Clock quality acceptance criteria, and / or Clock quality level The method according to claim 1, including the method described in claim 1.

6. The method according to claim 5, wherein the user equipment (UE) can determine whether it needs to switch to another clock source or whether the current value of the clock quality level meets the requirements of an ongoing time-constrained service.

7. The method according to claim 5, wherein the clock quality acceptance criteria include traceability to a parent time source, Coordinated Universal Time (UTC), or a Global Navigation Satellite System (GNSS), synchronization status, clock accuracy, or frequency stability.

8. The method according to claim 5, wherein the clock quality level includes a clock quality metric or an instruction for acceptance, and the clock quality level indicates what should be provided to the user equipment (UE).

9. The method according to claim 8, wherein the instruction for acceptance indicates the current timing synchronization status based on the clock quality acceptance criteria.

10. The method according to claim 8, wherein a bit sequence indicates one or more clock quality metrics to be reported to the UE, and each position in the bitmap indicates which of the clock quality metrics is required.

11. The source base station sends the handover required message, including the aforementioned time distribution configuration, to the core network (CN). The target base station receives the time distribution configuration provided by the source base station in the handover request message sent by the CN. The method according to claim 1, further comprising:

12. After receiving a handover required message or a path switching request message, the core network (CN) determines the aforementioned time distribution configuration. The target base station receives the time distribution configuration included in the handover request message or path switching acknowledgment message from the CN. The method according to claim 1, further comprising:

13. The source base station sends a handover request message including the aforementioned time distribution configuration, The target base station receives the time distribution configuration from the source base station. The method according to claim 1, further comprising:

14. The method according to claim 1, wherein the core network (CN) provides the time distribution configuration to the source base station before the reception at the target base station.

15. The method according to claim 1, further comprising receiving an NG Application Protocol (NGAP) message from a core network (CN) that includes a start or stop instruction for time delivery for a user device (UE), wherein the start or stop instruction activates or deactivates a time-quality delivery function for the UE.

16. A wireless communication method, At the target base station, receiving the time distribution area, The target base station determines the distribution of time quality information based on the time distribution area. Methods that include...

17. The method according to claim 16, wherein the distribution of the time quality information is directed to a user device (UE).

18. The method according to claim 17, wherein the receiving occurs during the UE handover procedure or during the base station path switching procedure for the UE handover procedure.

19. The method according to claims 16 to 17, wherein the time distribution area is transmitted from a source base station or core network (CN).

20. The aforementioned time distribution area is: List of tracking areas, List of cells, A list of standalone non-public networks (SNPNs), or List of Closed Access Groups (CAGs) for Integrated Non-Public Networks The method according to claim 16, including the method described in claim 16.

21. The method according to claim 20, further comprising sending time quality information to a user device (UE) when the UE is within a coverage area indicated by the time distribution area.

22. The source base station sends the handover required message, including the aforementioned time distribution area, to the core network (CN), The target base station receives the time distribution area provided by the source base station in the handover request message sent by the CN. The method according to claim 16, further comprising:

23. After receiving a handover required message or a path switching request message, the core network (CN) determines the time distribution area, The target base station receives the time distribution area included in the handover request message or path switching acknowledgment message from the CN. The method according to claim 16, further comprising:

24. The source base station sends a handover request message including the aforementioned time distribution area, The target base station receives the time distribution area from the source base station. The method according to claim 16, further comprising:

25. The method according to claim 16, wherein the core network (CN) provides the time distribution area to the source base station before the reception at the target base station.

26. The method according to claim 16, further comprising receiving an NG Application Protocol (NGAP) message from a core network (CN) that includes a start or stop instruction for time delivery for a user device (UE), wherein the start or stop instruction activates or deactivates the time-quality delivery function for the UE.

27. A wireless communication device comprising a processor and memory, wherein the processor is configured to read a code from the memory and to carry out the method according to any one of claims 1 to 26.

28. A computer program product comprising computer-readable program medium code stored thereon, wherein the code, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 26.

Images