Methods and apparatus related to timing synchronization status reports

Abstract

A method comprising: receiving a message identifying at least one user equipment for which action should be taken to increase the reliability of the user equipment reading the timing synchronization status report; and determining, based at least in part on information about the user equipment, an action to increase the reliability of the user equipment reading the timing synchronization status report.

Description

[[Technical Field]]

[0001] This application claims the benefit of priority from British Patent Application No. 2211611.5, filed on August 9, 2022, the contents of which are incorporated herein by reference in their entirety as if fully reproduced herein.

[0002] Exemplary embodiments relate to apparatuses, methods, and computer programs, and in particular, but not exclusively, relate to apparatuses, methods, and computer programs related to timing synchronization status reports. [[Background Art]]

[0003] When a radio access network node detects that there is a reportable event relating to a time source that the radio access network node uses as a time reference, the radio access network node may broadcast a timing synchronization status report. [[Summary of Invention]] [[Means for Solving the Problem]]

[0004] According to one aspect, there is provided a method comprising: receiving a message identifying at least one user equipment for which an action is to be taken to increase the reliability of reading of a timing synchronization status report by the user equipment; and determining an action to increase the reliability of reading of the timing synchronization status report by the user equipment based at least in part on information about the user equipment.

[0005] The message may include an indication of an urgency level for increasing the reliability of reading of the timing synchronization status report by the user equipment, and determining the action may be based in part on the indication of the urgency level.

[0006] A timing synchronization status report may be broadcast as part of the system information, and information about user equipment may include information about the interval at which the user equipment reads the broadcasted system information, and this method may include determining at least one parameter based on information about the interval at which the user equipment reads the broadcasted system information for the broadcast of the timing synchronization status report which is part of the system information.

[0007] At least one parameter may include the period during which the timing synchronization status report is included in the system information.

[0008] This method may include paging user devices to determine whether to report reading a timing synchronization status report, and the decision may be based at least in part on one or more of the information obtained from user device messages or information about when to anticipate user device messages.

[0009] Paging a user device to determine whether to report reading a timing synchronization status report may be based at least partially on one or more pieces of information from one or more messages from the user device that contain a field indicating reading a timing synchronization status report, or on information about when the user device is expected to next send a message containing a field indicating reading a timing synchronization status report.

[0010] Information about the user device may include the user device's wireless resource control status, and this method may include paging the user device for broadcasting a timing synchronization status report in response to determining that the user device is in wireless resource control idle mode.

[0011] In another embodiment, a method is provided which includes receiving a message identifying at least one user device for which action should be taken to improve the certainty of reading a timing synchronization status report by the user device, paging the user devices for broadcasting a timing synchronization status report, and then broadcasting the timing synchronization report.

[0012] In yet another embodiment, a method is provided which includes transmitting information from the user device about the reading cycle of a system information block on the user device.

[0013] In yet another embodiment, a method is provided which includes sending an indication from the user device that action should be taken to improve the reliability of reading the timing synchronization status report by the user device.

[0014] In yet another embodiment, a method is provided which includes the steps of receiving a paging message indicating a broadcast of system information including a timing synchronization status report, and reading the system information indicated by the paging message.

[0015] In yet another embodiment, a method is provided which includes sending a request to identify at least one user device for which action should be taken to improve the reliability of reading a timing synchronization status report by the user device.

[0016] The request may include an emergency level indicator to enhance the reliability of reading the timing synchronization status report by the user's equipment.

[0017] In yet another embodiment, an apparatus is provided comprising: means for receiving a message identifying at least one user device for which action should be taken to improve the reliability of reading a timing synchronization status report by the user device; and means for determining an action to improve the reliability of reading a timing synchronization status report by the user device, at least in part, based on information about the user device.

[0018] The message may include an emergency level indicator to enhance the reliability of reading the timing synchronization status report by the user's equipment, and the decision to take action may be based in part on the emergency level indicator.

[0019] A timing synchronization status report may be broadcast as part of system information, and information about user equipment may include information about the period during which the user equipment reads the broadcasted system information, and the device may have means for determining at least one parameter for broadcasting the timing synchronization status report, which is part of the system information, based on information about the period during which the user equipment reads the broadcasted system information.

[0020] At least one parameter may include the period during which the timing synchronization status report is included in the system information.

[0021] The device may include means for paging user devices and determining whether to report reading a timing synchronization status report, based at least partially on one or more of the following: information obtained from user device messages or information about when to predict user device messages.

[0022] Paging a user device to determine whether to report reading a timing synchronization status report may be based at least partially on one or more pieces of information from one or more messages from the user device that contain a field indicating reading a timing synchronization status report, or on information about when the user device is expected to next send a message containing a field indicating reading a timing synchronization status report.

[0023] Information about user equipment may include the wireless resource control status of the user equipment, and the device may include means for paging the user equipment for broadcasting a timing synchronization status report in response to determining that the user equipment is in wireless resource control idle mode.

[0024] In yet another embodiment, an apparatus is provided comprising: means for receiving a message identifying at least one user device for which action should be taken to improve the reliability of reading a timing synchronization status report by the user device; means for paging user devices for broadcasting a timing synchronization status report; and means for subsequently broadcasting the timing synchronization report.

[0025] In yet another embodiment, a user device is provided that includes means for transmitting information about the reading cycle of a system information block in the user device.

[0026] In yet another embodiment, a user device is provided that includes means for transmitting an indication that action should be taken to improve the reliability of reading the timing synchronization status report by the user device.

[0027] According to yet another aspect, a user equipment is provided, comprising: means for receiving a paging message indicating broadcast of system information including a timing synchronization status report; and means for reading the system information indicated by the paging message.

[0028] According to yet another aspect, an apparatus is provided, comprising means for transmitting a request for identifying at least one user equipment on which an action should be taken in order to increase the reliability of reading of a timing synchronization status report by the user equipment.

[0029] The request may include an indication of an emergency level for increasing the reliability of reading of the timing synchronization status report by the user equipment.

[0030] According to yet another aspect, an apparatus is provided, comprising at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code, together with the at least one processor, are configured to cause the apparatus to perform: receiving a message identifying at least one user equipment on which an action should be taken in order to increase the reliability of reading of a timing synchronization status report by the user equipment; and determining an action for increasing the reliability of reading of the timing synchronization status report by the user equipment based at least in part on information about the user equipment.

[0031] The message may include an indication of an emergency level for increasing the reliability of reading of the timing synchronization status report by the user equipment, and determining the action may be based in part on the indication of the emergency level.

[0032] A timing-synchronized status report may be broadcast as part of system information, and information about user equipment may include information about the period during which the user equipment reads the broadcasted system information, and at least one memory and computer program code may be configured, together with at least one processor, to cause the device to determine at least one parameter for broadcasting a timing-synchronized status report, which is part of system information, based on information about the period during which the user equipment reads the broadcasted system information.

[0033] At least one parameter may include the period during which the timing synchronization status report is included in the system information.

[0034] At least one memory and computer program code, together with at least one processor, may be configured to cause the device to page user devices and report the reading of a timing synchronization status report, at least partially based on one or more of the following: information obtained from user device messages or information about when to predict user device messages.

[0035] At least one memory and computer program code, together with at least one processor, may be configured to cause the device to page user equipment and report the reading of a timing synchronization status report, at least partially based on one or more of the following: information obtained from one or more messages from user equipment that include a field indicating the reading of a timing synchronization status report, or information about when the user equipment is expected to next send a message that includes a field indicating the reading of a timing synchronization status report.

[0036] Information about the user device may include the user device's radio resource control status, and at least one memory and computer program code, together with at least one processor, may be configured to cause the device to page the user device for broadcasting a timing-synchronized status report in response to determining that the user device is in radio resource control idle mode.

[0037] In yet another embodiment, a device is provided comprising at least one processor and at least one memory containing computer program code, wherein the at least one memory and computer program code are configured together with the at least one processor to cause the device to receive a message identifying at least one user device for which action should be taken to improve the certainty of reading a timing synchronization status report by the user device, to page the user devices for broadcasting a timing synchronization status report, and then to broadcast the timing synchronization report.

[0038] In yet another embodiment, a user device is provided comprising at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code are configured together with the at least one processor to cause the user device to transmit information about the period of reading system information blocks in the user device.

[0039] In yet another embodiment, a user device is provided comprising at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code are configured together with the at least one processor to cause the user device to send an indication that action should be taken to improve the reliability of the user device's reading of a timing synchronization status report.

[0040] In yet another embodiment, a user device is provided comprising at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code, together with the at least one processor, are configured to cause the user device to receive paging messages indicating the broadcast of system information including a timing synchronization status report, and to read the system information indicated by the paging messages.

[0041] In yet another embodiment, a device is provided comprising at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code are configured together with the at least one processor to cause the device to send a request to identify at least one user device for which action should be taken to improve the certainty of reading a timing synchronization status report by the user device.

[0042] The request may include an emergency level indicator to enhance the reliability of reading the timing synchronization status report by the user's equipment.

[0043] In yet another embodiment, an apparatus is provided comprising: a receiving circuit configuration for receiving a message that identifies at least one user device for which action should be taken to improve the reliability of reading a timing synchronization status report by the user device; and a deciding circuit configuration for determining an action to improve the reliability of reading a timing synchronization status report by the user device, at least partially based on information about the user device.

[0044] In yet another embodiment, an apparatus is provided comprising: a receiving circuit configuration for receiving a message that identifies at least one user device for which action should be taken to improve the reliability of reading a timing synchronization status report by the user device; a paging circuit configuration for paging user devices for broadcasting a timing synchronization status report; and a broadcast circuit configuration for broadcasting the timing synchronization report.

[0045] In yet another embodiment, a user device is provided that includes a transmission circuit configuration for transmitting information about the reading cycle of a system information block in the user device.

[0046] In yet another embodiment, a user device is provided that includes a transmission circuit configuration that transmits an indication that action should be taken to improve the reliability of reading the timing synchronization status report by the user device.

[0047] In yet another embodiment, user equipment is provided, comprising a receiving circuit configuration for receiving a paging message indicating a broadcast of system information including a timing synchronization status report, and a reading circuit configuration for reading the system information indicated by the paging message.

[0048] In yet another embodiment, the device is provided, which includes a transmission circuit configuration that transmits a request to identify at least one user device for which action should be taken to improve the reliability of reading a timing synchronization status report by the user device.

[0049] In yet another embodiment, a computer-readable medium is provided that includes stored program instructions for receiving a message identifying at least one user device for which action should be taken to improve the reliability of reading a timing synchronization status report by the user device, and determining, at least in part, an action to improve the reliability of reading a timing synchronization status report by the user device.

[0050] In yet another embodiment, a computer-readable medium is provided that includes stored program instructions for receiving a message identifying at least one user device for which action should be taken to improve the reliability of reading a timing synchronization status report by the user device, paging the user devices for broadcasting a timing synchronization status report, and then broadcasting the timing synchronization report.

[0051] In yet another embodiment, a computer-readable medium is provided that includes stored program instructions for transmitting information from the user device about the reading cycle of a system information block at the user device.

[0052] In yet another embodiment, a computer-readable medium is provided that includes stored program instructions for sending an indication from the user's device that action should be taken to improve the reliability of the user's device reading the timing synchronization status report.

[0053] In yet another embodiment, a computer-readable medium is provided which includes stored program instructions for receiving a paging message indicating a broadcast of system information including a timing synchronization status report, and for reading the system information indicated by the paging message.

[0054] In yet another embodiment, a computer-readable medium is provided that includes stored program instructions for performing a task of sending a request to identify at least one user device from which action should be taken to improve the reliability of reading a timing synchronization status report by the user device.

[0055] In yet another embodiment, a non-temporary computer-readable medium is provided, which includes stored program instructions for receiving a message identifying at least one user device for which action should be taken to improve the reliability of reading a timing synchronization status report by the user device, and determining, at least in part, measures to improve the reliability of reading the timing synchronization status report by the user device.

[0056] In yet another embodiment, a non-temporary computer-readable medium is provided which includes stored program instructions for receiving a message identifying at least one user device for which action should be taken to improve the reliability of reading a timing synchronization status report by the user device, paging the user devices for broadcasting a timing synchronization status report, and then broadcasting the timing synchronization report.

[0057] In yet another embodiment, a non-temporary computer-readable medium is provided which includes stored program instructions for transmitting from the user device information about the reading cycle of a system information block at the user device.

[0058] In yet another embodiment, a non-temporary computer-readable medium is provided, which includes stored program instructions for sending an indication from the user's device that action should be taken to improve the reliability of reading the timing synchronization status report by the user's device.

[0059] In yet another embodiment, a non-temporary computer-readable medium is provided which includes stored program instructions for receiving a paging message indicating a broadcast of system information including a timing synchronization status report, and for reading the system information indicated by the paging message.

[0060] The non-temporary computer-readable medium includes stored program instructions for performing a task of sending a request to identify at least one user device to which action should be taken in order to improve the reliability of reading the timing synchronization status report by the user device.

[0061] In yet another embodiment, a computer program is provided which includes computer executable code, and when executed on at least one processor, the computer executable code is configured to cause the device to receive a message that identifies at least one user device for which action should be taken to improve the certainty of the user device reading the timing synchronization status report, and to determine, at least in part, an action to improve the certainty of the user device reading the timing synchronization status report.

[0062] In yet another embodiment, a computer program is provided which includes computer executable code, and when executed on at least one processor, the computer executable code is configured to cause the device to receive a message that identifies at least one user device for which action should be taken to increase the certainty of reading a timing synchronization status report by the user device, to cause the user device to page for broadcasting a timing synchronization status report, and then to broadcast the timing synchronization report.

[0063] In yet another embodiment, a computer program is provided which includes computer executable code, and when executed on at least one processor, the computer executable code is configured to cause a user device to transmit at least information about the period of reading system information blocks on the user device.

[0064] In yet another embodiment, a computer program is provided which includes computer executable code, and when executed on at least one processor, the computer executable code is configured to cause a user device to send an indication that at least one action should be taken to increase the certainty of the user device reading a timing synchronization status report.

[0065] In yet another embodiment, a computer program is provided which includes computer executable code, and when the computer executable code is executed on at least one processor, it is configured to cause a user device to receive a paging message indicating a broadcast of system information including a timing synchronization status report, and to read the system information indicated by the paging message.

[0066] In yet another embodiment, a computer program is provided which includes computer executable code, and when executed on at least one processor, the computer executable code is configured to cause the device to send a request to identify at least one user device for which action should be taken to improve the certainty of reading a timing synchronization status report by the user device.

[0067] Many different embodiments have been described above. It should be understood that further embodiments can be provided by combining any two or more of the embodiments described above.

[0068] The following detailed description and the attached claims also describe various other embodiments.

[0069] Herein, several exemplary embodiments are described in further detail, merely as examples, with reference to the following examples and accompanying drawings. [Brief explanation of the drawing]

[0070] [Figure 1] This is a diagram of an exemplary mobile communication system to which several exemplary embodiments may be applied. [Figure 2] This figure shows an example of the operation of some elements of Figure 1 in several exemplary embodiments. [Figure 3] This figure shows an example of the operation of some elements of Figure 1 in several exemplary embodiments. [Figure 4] This figure shows an example of the operation of some elements of Figure 1 in several exemplary embodiments. [Figure 5] This figure shows an example of the operation of some elements of Figure 1 in several exemplary embodiments. [Figure 6] This figure shows an example of the operation of some elements of Figure 1 in several exemplary embodiments. [Figure 7] This figure shows an example of a device that realizes the functionality of user equipment or access nodes, according to several exemplary embodiments. [Figure 8] This figure shows an example of a device that implements network functionality according to several exemplary embodiments. [Figure 9] This figure shows an example of a non-volatile memory medium. [Modes for carrying out the invention]

[0071] The following explanation focuses on an example of a mobile communication system operating according to 3GPP 5G technology, but the underlying techniques may be applicable to systems operating according to other technologies, such as more advanced 3GPP technologies.

[0072] Figure 1 shows a simplified diagram of an example architecture of a 3GPP 5G system. All units shown in Figure 1 are logical units. The connections shown in Figure 1 are logical connections and may differ from actual physical connections. 5G systems may have functions and structures other than those shown in Figure 1.

[0073] The core network can provide connectivity between devices that implement user equipment functionality and one or more data networks (DNs) via a New Generation Radio Access Network (NG-RAN) which has a network of devices that implement instances of gNB (gNodeB) functionality.

[0074] The gNB is connected to the User Plane Function (UPF) of the Core Network (CN) to (i) route and forward user data packets and provide connectivity for the device to one or more external packet data networks (DNs), and (ii) connect to the Access Mobility Management Function (AMF) of the Core Network (CN) to control changes in UE access and serving cells.

[0075] The term "User Equipment" (UE) can refer to any device, apparatus, or component that provides at least the functionality of a 3GPP User Equipment (UE).

[0076] A UE may be a mobile or stationary device (e.g., portable or non-portable computing device) including, but not limited to, the following types of devices: mobile phones, smartphones, personal digital assistants (PDAs), handsets, devices using wireless modems (such as alarm or measuring devices), laptops and / or touchscreen computers, tablets, game consoles, notebooks, and multimedia devices. It should be understood that a UE device may be almost exclusively an uplink device, an example of which is a camera or camcorder that loads images or video clips onto the network. A UE device may also be a device capable of operating in an Internet of Things (IoT) network, a scenario where objects are provided that have the ability to transmit data over a network without requiring person-to-person or person-to-computer interaction, for example, to be used in smart power grids and connected vehicles. Devices can also utilize the cloud. In some applications, a UE device may include a user-portable device with wireless components (such as a watch, earphones, or glasses), with the computation performed in the cloud.

[0077] 5G enables the use of multiple input-multiple output (MIMO) antennas and can involve numerous base stations (gNBs), including macrosites that use various radio technologies and work in conjunction with smaller stations, depending on service needs, usage scenarios, and / or available spectrum. 5G mobile communications support a wide range of usage scenarios and related applications, including video streaming, augmented reality, various data sharing methods, and various forms of machine-based applications (such as (large-scale) machine-based communications (mMTC), including vehicle safety, various sensors, and real-time control). 5G can use multiple frequency bands, e.g., below 6 GHz or above 24 GHz, cmWave and mmWave, and may be able to integrate with existing conventional radio access technologies such as LTE. Integration with LTE may be implemented as a system where macro coverage is provided by LTE, and 5G radio interface access is provided from smaller cells by aggregation into LTE. In other words, 5G can support both RAT-to-RAT operability (such as LTE-5G) and RI-to-RI operability (radio interface-to-radio interface operability, such as below 6GHz - cmWave, above 6 or 24GHz - cmWave, and mmWave). 5G networks can use network slicing to run services with differing requirements in terms of latency, reliability, throughput, and mobility, where network slicing can create multiple independent, dedicated virtual subnets (network instances) within the same infrastructure.

[0078] Bringing content closer to 5G systems facilitates low-latency applications and services, leading to local breakout and multi-access edge computing (MEC). 5G enables analysis and knowledge generation to take place at the data source. This approach may involve leveraging resources that may not be continuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for hosting applications and services. MEC also has the ability to store and process content in the vicinity of mobile subscribers for faster response times. Edge computing covers a wide range of technologies, including collaborative distributed peer-to-peer ad-hoc networking and processing, due computing, mobile edge computing, cloudlets, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (where large-scale connectivity and / or latency is critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-constrained control, and healthcare applications), which can also be classified as wireless sensor networks, mobile data acquisition, mobile signature analysis, collaborative distributed peer-to-peer ad-hoc networking and processing, due computing, mobile edge computing, cloudlets, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (where large-scale connectivity and / or latency is critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-constrained control, and healthcare applications).

[0079] 5G can also extend or complement its service coverage by utilizing satellite communications, for example, by providing backhaul. Possible use cases include providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices, or for passengers on board vehicles, Mobile Broadband (MBB), or ensuring service availability for critical communications and future rail / maritime / air communications. Satellite communications can utilize not only geostationary (GEO) satellite systems but also low Earth orbit (LEO) satellite systems, especially megaconstellations (systems with hundreds of (nano) satellites). Each satellite in a megaconstellation can cover multiple satellite-enabled network entities that make up ground cells. Ground cells can be made via ground relay nodes or by gNBs located on the ground or satellite.

[0080] 5GC employs a service-based architecture (SBA), and in accordance with the SBA, communication between network functions uses a Service-Based Interface (SBI). The Application Programming Interface (API) is used for the SBI.

[0081] An exemplary embodiment of a 3GPP ASTI (Access Stratum Time Information) service, in which an Application Function (AF) can request time synchronization as a service to a UE or group of UEs, is described below. The Time Sensitive Communication and Time Synchronization Function (TSCTSF) is a network function that receives the AF's time synchronization request and configures the service within 5GS.

[0082] The delivery of 5G clock (e.g., UTC) information to the UE may include, for example, the gNB providing 5G timing information to the UE via the Uu interface, for example, using the System Information Block (SIB9). The 5G timing information may be included in the Reference Time Information (RTI) information element within the System Information Block (SIB9).

[0083] Figure 2 shows an example of operation according to several exemplary embodiments.

[0084] Application functions (AFs) outside the 5G core network (5GC) send an Nnef_ASTI SubscribeRequest message to the 5GC's Network Exposure Function (NEF). The message includes the identifiers of one or more target UEs and the Guarantee TSS RX flag set to "ON," indicating that the network should take action to ensure that the target UEs receive TSS reports. The message may also indicate the urgency level.

[0085] In response to receiving the Nnef_ASTISubscribeRequest message, the NEF sends an Ntsctsf_ASTISubscribeRequest message to the TSCTSF on the 5GC. The Ntsctsf_ASTISubscribeRequest message also identifies one or more target UEs and includes a Guarantee Timing Synchronization Status (TSS) Received (RX) flag set to "ON," indicating that the network should take action to ensure that the target UEs receive the TSS report. If the Nnef_ASTI SubscribeRequest message from the AF includes an urgency level indicator, the Ntsctsf_ASTISubscribeRequest to the TSCTSF also includes an urgency level indicator.

[0086] TSCTSF makes one or more discovery requests to the 5GC's network repository function (NRF) and discovers the addresses of one or more AMF instances currently associated with the identified target UE in the Ntsctsf_ASTISubscribeRequest message.

[0087] TSCTSF sends one or more Namf_NonUeN2MsgTransfer messages to one or more AMF instances detected via NRF. Each Namf_NonUeN2MsgTransfer message to an AMF instance includes the target UE and the Guarantee TSS RX flag set to "ON," indicating that the network should take action to ensure the target UE receives the TSS report. If the Ntsctsf_ASTISubscribeRequest message includes an urgency level indicator, the Namf_NonUeN2MsgTransfer message also includes an urgency level indicator.

[0088] The AMF sends a Next Generation Application Protocol (NGAP):TSS Reporting Control message to one or more NG-RAN gNBs. The NGAP:TSS Reporting Control message to each AMF instance includes the target UE and the Guarantee TSS RX flag, set to "ON," indicating that the network should take action to ensure the target UE receives the TSS report. If the Namf_NonUeN2MsgTransfer message from TSCTSF includes an urgency level indicator, the NGAP:TSS Reporting Control message to the gNB also includes an urgency level indicator.

[0089] In the example described above, the request for RAN TSS reports from the AMF by TSCTSF, and the forwarding of such requests to the gNB, are performed by node-level signaling, which may also be achieved by, for example, UE-related signaling.

[0090] One alternative to the AF requesting guaranteed reception of RAN TSS (via the exposure framework) from one or more UEs is for one or more UEs to make a direct request to the gNB. The gNB then forwards the indication of this request (via the AMF) to the TSCTSF so that the TSCTSF becomes aware of the request. Such direct requests by UEs can also be made directly through RRC signaling. For example, in addition to the UEAssistanceInformation IE, which is an information element that allows a UE to indicate a preference for RTI provisioning, new information elements (IEs) may be included as part of the RRC signaling.

[0091] Figure 3 illustrates further operation in several exemplary embodiments of a gNB that receives an NGAP:TSS Reporting Control message identifying one or more UEs with an RRC INACTIVE status.

[0092] A primary source event (e.g., detection of network timing synchronization degradation / failure / improvement / recovery in the gNB) triggers the gNB to generate a TSS report, include the TSS report in the system information broadcast by the gNB (e.g., a System Information Block (SIB9)), and send the TSS report to the AMF instance associated with the gNB. The SIB9 broadcast by the gNB includes a field containing reference time information (RTI) and a field containing the TSS report.

[0093] For each identified RRC INACTIVE UE in the NGAP:TSS Reporting Control message received from the AMF instance, the gNB has information about the frequency at which the UE reads the SIB. The gNB may have received this information directly from the UE when the UE had an RRC CONNECTED status (as shown in Figure 3), or it may have received this information from the AF via TCSTSF and AMF. Based on the information about the frequency at which the UE reads the SIB9, the gNB continues to include the TSS report in the SIB9 broadcast for a certain period to increase the certainty that the UE reads the TSS report. Including the TSS report more often than the SIB9 broadcast helps to ensure that the UE reads the TSS report. For example, the gNB continues to include the RAN TSS report in the SIB9 broadcast for a longer period than the UE's SIB9 reading cycle.

[0094] Figure 4 shows diagrams illustrating the operation of gNB in ​​several other embodiments.

[0095] A primary source event (e.g., detection of network timing synchronization degradation / failure / improvement / recovery in the gNB) triggers the gNB to generate a TSS report, include the TSS report in the system information broadcast by the gNB (e.g., a System Information Block (SIB9)), and send the TSS report to the AMF instance associated with the gNB. The SIB9 broadcast by the gNB includes a field containing reference time information (RTI) and a field containing the TSS report.

[0096] A UE with RRC INACTIVE status may have one or more internal triggers that cause it to re-establish a connection to the gNB (and switch to RRC_CONNECTED status) for primary reasons other than reporting the reading of a TSS report. The RRC signaling message subsequently sent by the UE may be adapted to include additional (secondary-purpose) fields indicating that the UE has read a TSS report. The information the gNB has about the UE may include information obtained from such RRC signaling messages from the UE, and / or (if the RRC signaling has a time-based trigger) information about when the UE is expected to send the next such RRC signaling. If the information provided by these RRC signaling messages meets the urgency level specified in the NGAP:TSS Reporting Control message from AMF, or (if no urgency level is specified in the NGAP:TSS Reporting Control message from AMF) the default urgency level stored in the gNB, the gNB will refrain from paging the UE and switching to RRC CONNECTED status, primarily for the purpose of reporting the reading of a TSS report. On the other hand, if the information provided by these RRC signaling messages does not meet or cannot meet the urgency level specified in the NGAP:TSS Reporting Control message from AMF, or (if no urgency level is specified in the NGAP:TSS Reporting Control message from AMF) does not meet or cannot meet the default urgency level stored in the gNB, the gNB then triggers the UE to page and switch to the RRC CONNECTED status, primarily for the purpose of indicating that the TSS report has been read. In either case, the gNB receives an explicit acknowledgment that the UE has read the TSS report, thereby increasing the gNB's certainty that the UE has read the TSS report.

[0097] The gNB can start a timer, for example, by broadcasting a TSS report (which is part of SIB9). The timer can have a value determined by the urgency level indicated in the NGAP:TSS Reporting Control message from the AMF, or a default value if no urgency level is indicated in the NGAP:TSS Reporting Control message from the AMF. If the timer expires and the gNB has not received RRC signaling from the UE indicating that the TSS report has been read, the gNB can decide, for example, to page the UE (under the gNB's control) to check whether the UE has read the TSS report through SIB9. If there are multiple such UEs, the gNB can control the paging of multiple UEs to ensure that random access by multiple UEs is randomized. One example of an alternative action when the timer expires is for the gNB to notify the TSCTSF of one or more UEs that have not received RRC signaling indicating that the TSS report has been read. The TSCTSF then controls the paging of such UEs to the TSCTSF, thereby centralizing the management of UEs within the TSCTSF.

[0098] Periodic control procedures that can be adapted to the additional secondary purpose of providing gNBs with information about TSS report readings may include, for example, time-triggered, mobility-triggered, or event-triggered RRC signaling. For example, a Mobility Registration Update message (an RRC signaling with a mobility-based trigger) may include an additional (e.g., 1-bit) field indicating that the UE has read a TSS report, and the TSCTSF may act on the AMF to set the UE's registration area smaller, with the intention of increasing the probability that the gNB will receive an indication of TSS report reading in a timely manner through the Mobility Registration Update message, and avoid paging the UE to switch to RRC connected status, primarily for the purpose of reporting TSS report readings. As another example, a periodic Registration Update message (controlled by periodic registration update timer 3512) or an RNA update message (controlled by timer T380) may include an additional (e.g., 1-bit) field for indicating that the UE has read a TSS report. The gNB can have information about when the UE is expected to next send these time-triggered RRC signaling messages, and can also determine whether such messages from the UE are expected in time and avoid paging the UE to switch to the RRC CONNECTED status, primarily for the purpose of reporting the TSS report reading.

[0099] Figure 5 shows illustrative operation in gNB and TSCTSF according to several exemplary embodiments.

[0100] A primary source event (e.g., detection of network timing synchronization degradation / failure / improvement / recovery in the gNB) triggers the gNB to generate a TSS report, include the TSS report in the system information broadcast by the gNB (e.g., a System Information Block (SIB9)), and send the TSS report to the AMF instance associated with the gNB. The SIB9 broadcast by the gNB includes a field containing reference time information (RTI) and a field containing the TSS report.

[0101] The gNB does not take any action to increase the certainty that a UE has read the TSS report for each target UE (among those identified in the NGAP:TSS Reporting Control message received from the AMF instance) whose information in the gNB indicates that the UE does not have an RRC INACTIVE status (or RRC CONNECTED status). In response to receiving the TSS report from the gNB via the AMF, the TSCTSF determines which target UEs (among those identified in the Ntsctsf_SubscribeRequest message from the AF via the NEF) have an RRC IDLE status and are most recently associated with the gNB from which the TSS report is received. The TSCTSF then begins paging messages indicating the broadcast of the TSS report by the gNB for this subset of target UEs. This action increases the certainty that UEs with an RRC IDLE status camped in cells operated by the gNB will read the TSS report broadcast by the gNB.

[0102] Figure 6 shows an example of operation in gNB according to several exemplary embodiments.

[0103] A primary source event (e.g., detection of network timing synchronization degradation / failure / improvement / recovery in the gNB) triggers the gNB to generate a TSS report, include the TSS report in the system information broadcast by the gNB (e.g., a System Information Block (SIB9)), and send the TSS report to the AMF instance associated with the gNB. The SIB9 broadcast by the gNB includes a field indicating reference time information (RTI) and a field containing the TSS report.

[0104] The gNB pages each target UE (one of the UEs identified in the NGAP:TSS Reporting Control message received from the AMF instance) to notify the UE of upcoming SIB9 broadcasts containing the TSS report, provided the gNB has information indicating that the UE has an RRC INACTIVE status and is camped in a cell operated by the gNB. The UE then recognizes that the next SIB9 broadcast will contain the TSS report and reads the next SIB9 broadcast. This action by the gNB increases the certainty that the target UE will read the TSS.

[0105] The examples described above, including a gNB that uses information about the UE's SIB9 read cycle, and the example described above, including a gNB that sends a paging message indicating that an upcoming SIB9 broadcast will contain a RAN TSS report, are examples of the implicit confirmation technique. The implicit confirmation technique can better avoid RAN congestion that may result from the reconnection of multiple UEs in response to the same event.

[0106] Some features of some exemplary embodiments are as follows:

[0107] The AF can request guaranteed / acknowledged receipt of 5G network timing synchronization status reports for a UE or group of UEs. For example, additional flags can be added to the exposure API between the AF and TSCTSF. The AF can indicate how urgent the acknowledgment needs to be in order to influence how the UE should react if it has not received a 5G RAN timing synchronization status report from the RAN.

[0108] 5GS (either gNB or TSCTSF) ensures that the UE reads the 5G RAN timing synchronization status report. Multiple options include: (a) The RAN timing synchronization status report within the SIB is reported over a long period (or always) within the cell. The decision of how long (or always) the RAN timing synchronization status report should be provided rests with the gNB. To assist in this decision, the UE can indicate to the gNB the frequency at which the UE will read the SIB9 before the UE releases or interrupts the RRC connection. This indication from the UE can have two uses in the gNB: i) it allows the gNB to determine the shortest period at which the RAN timing synchronization status report should be repeated to ensure that the UE reads the timing synchronization status report, and ii) it informs the gNB that the UE requires this guaranteed reception of the report (i.e., instead of the AF requesting guaranteed reception of the 5G network timing synchronization status report). (b) The gNB or TSCTSF can anticipate confirmation of receipt of a RAN timing synchronization status report from the UE by relying on periodic control procedures that the UE performs with the network based on event triggers (e.g., time-based, mobility-based, or other event-based). The UE can add a bit to the signaling message it sends to the network for this confirmation. (c) gNB can page the UE to indicate that the next SIB9 will contain a RAN timing synchronization status report. If the UE is in the RRC_IDLE / INACTIVE state, it does not need to reconnect to the network and will read the subsequent SIB9 after paging. (d) The gNB or TSCTSF may rely on UE paging. The paging message may again include the RAN timing synchronization status report broadcast within the cell, and the UE may add a bit to acknowledge receipt of the report when reconnecting to the network due to paging. This can prevent multiple UEs from attempting to reconnect in a short period of time (i.e., the gNB or TSCTSF can control access to the network to make reconnections uncorrelated with new report events).

[0109] AF may include a flag indicating the need for guaranteed / acknowledged reception of the UE's 5G RAN timing synchronization status report, and may also include a value indicating how urgently the acknowledgment is needed.

[0110] If guaranteed / confirmed receipt of the UE's 5G RAN timing synchronization status report is required, and the UE is in the RRC_INACTIVE / IDLE state, and the gNB decides to use SIB9 to broadcast the report within the cell, the gNB may repeat the report within the SIB9 for an extended period within the cell to ensure that the UE reads the report. The gNB may use additional information provided by the AF and transmitted via TSCTSF / AMF (i.e., the target UE that requires this assurance mode), or additional information transmitted by the UE (e.g., how often the UE reads the SIB9 before changing to RRC_INACTIVE / IDLE) to determine how long the gNB should repeat the report. The determination of how guaranteed / confirmed reception of the UE's RAN timing synchronization status report is achieved is at the discretion of the gNB or TSCTSF (for example, depending on future control procedures that the UE can perform with the gNB via time / mobility / event-based triggers, or using paging messages to indicate to the UE that an upcoming SIB9 will contain a RAN timing synchronization status report that the UE should read, or performing paging initiated by the RAN / CN).

[0111] If guaranteed / confirmed receipt of the UE's 5G RAN timing synchronization status report is required, and the gNB decides to send the report to the UE via SIB9, the gNB may use various methods to enable the UE to read the RAN timing synchronization status report.

[0112] The UE can indicate to the gNB how often it reads the SIB9, provided that guaranteed / confirmed receipt of the UE's 5GRAN timing synchronization status report is supported.

[0113] Figure 7 shows an example of a device that implements the functionality of a UE or RAN access node in the architecture of Figure 1. The device may comprise at least one processor 802 coupled to one or more interfaces 808. In the case of a UE, the one or more interfaces 808 may include, for example, one or more interfaces to other devices / components that enable wireless communication for the UE's functionality. In the case of a RAN access node, the one or more interfaces 808 may include, for example, one or more interfaces to core network nodes that implement core network functions such as AMF, UPF, etc. At least one processor 802 may also be coupled to a radio unit 804, which includes, for example, one or more antennas for wireless transmission and reception. At least one processor 802 may also be coupled to at least one memory 806. At least one processor 802 may be configured to execute appropriate software code to perform the operations described above. The software code may be stored in memory 806.

[0114] Figure 8 shows an example of a device that implements one of the core network functions of Figure 1. The device may include at least one processor 902 coupled to one or more interfaces 908 for communicating with other core network functions or NG-RAN (New Generation Radio Access Network) nodes. At least one processor 902 may also be coupled to at least one memory 906. At least one processor 902 may be configured to execute appropriate software code to perform the operations described above. The software code may be stored in memory 906.

[0115] Figure 9 shows schematic diagrams of non-volatile memory media 1100a (e.g., a computer disk (CD) or digital versatile disk (DVD)) and 1100b (e.g., a Universal Serial Bus (USB) memory stick) that store instructions and / or parameters 1102, which, when executed by the processor, enable the processor to perform one or more of the steps of the previously described method.

[0116] It should be noted that exemplary embodiments may be implemented as circuit configurations consisting of software, hardware, application logic, or a combination of software, hardware, and application logic. In exemplary embodiments, the application logic, software, or instruction set is held on any computer-readable medium. In the context of this document, “computer-readable medium” can be any medium or means on which instructions can be stored, preserved, transmitted, propagated, or transferred by, or in use with, an instruction execution system, apparatus, or device such as a base station or user equipment of the exemplary embodiments described above.

[0117] As used in this application, the term “circuit configuration” means all of the following: (a) embodiments of hardware-only circuits (such as embodiments of analog and / or digital circuit configurations only); (b) combinations of circuits and software (and / or firmware) (where applicable), such as: (i) combinations of processors; or (ii) a portion of processors / software (including digital signal processors), software, and memory that work together to cause a user device or base station or other device of the embodiments described above to perform various functions; and (c) circuits such as microprocessors or portions of microprocessors that require software or firmware to operate, even if the software or firmware is not physically present. This definition of circuit configuration also applies to all use of the term “means” in this application, including in all claims. As a further example, the term “circuit configuration” as used in this application also covers embodiments of processors (or more processors) alone, or portions of processors and software and / or firmware associated with processors (or more processors). The term "circuit configuration" also covers, for example, a baseband integrated circuit or application processor integrated circuit for a mobile phone, or a similar integrated circuit in a server, mobile communications network device, or other network device, where it falls under a specific claimed element.

[0118] The features, advantages, and characteristics described herein can be combined in any preferred manner in one or more exemplary embodiments. Those skilled in the art will recognize that such exemplary embodiments may be practiced without one or more of the specific features or advantages of a particular embodiment. In other examples, additional features and advantages in a particular embodiment may be recognized that are not present in all exemplary embodiments. Those skilled in the art will readily understand that the exemplary embodiments discussed above may be practiced with steps in a different order and / or with hardware elements in configurations different from those disclosed. Therefore, while several embodiments have been described based on such exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, changes, and alternative structures are apparent while remaining within the spirit and scope of the exemplary embodiments.

Claims

1. A method performed by a radio access network node of a fifth-generation mobile communication system, The fifth-generation mobile communication system's access mobility management function receives a message containing the user device identifier and a flag set to indicate that an action will be taken by the radio access network node to enhance the reliability of the user device's reading of the timing synchronization status report. To generate a timing synchronization status report, The determination of an action to enhance the reliability of reading the timing-synchronized status report by the user device, based at least on information about the cycle in which the user device reads system information, is as follows: The timing synchronization status report will be included in the system information that will be broadcast to user devices by the wireless access network node, Broadcasting system information repeatedly over a period longer than the cycle in which user devices can read the broadcasted system information. including and Methods that include...

2. The method according to claim 1, wherein the message includes an urgency level indicator to enhance the reliability of reading the timing-synchronized status report by the user device, and the decision on action is further based on the urgency level indicator.

3. The process involves paging user devices to determine whether to have them report reading timing synchronization status reports, and this determination is based on at least one of the following: information obtained from messages received from user devices, or information about when to anticipate messages from user devices. Based on the decision to page user devices, the paging of user devices and The method according to claim 1, including the method described in claim 1.

4. The method according to claim 1, wherein the decision of whether to paging user devices to cause them to report the reading of a timing synchronization status report is based on at least one of the following: information obtained from a message from a user device that includes a field indicating the reading of a timing synchronization status report, or information about when the user device is expected to next send a message that includes a field indicating the reading of a timing synchronization status report.

5. Receiving information from the user device regarding the wireless resource control status of the user device, Based on information about the user device's wireless resource control status, in response to determining that the user device is in wireless resource control idle mode, paging the user device to report the reading of the timing synchronization status report. The method according to claim 1, further comprising:

6. A method performed by a user device having a wireless resource control inactive status, Receiving a paging message from a radio access network node of a fifth-generation mobile communication system indicating upcoming broadcasts of system information, including a timing synchronization status report, Receiving system information broadcast by wireless access network nodes, Establish a connection with the wireless access network node and send a wireless resource control signaling message to the wireless access network node, which includes a field containing an indication that the user device has read the timing synchronization status report. Methods that include...

7. A wireless access network node for a fifth-generation mobile communication system, A means for receiving a message from the access mobility management function of a fifth-generation mobile communication system, which includes a user device identifier and a flag set to indicate that an action will be taken by a radio access network node to enhance the reliability of the user device reading the timing synchronization status report. A means for generating a timing synchronization status report, A means for determining an action to improve the reliability of reading the timing synchronization status report by the user device, based at least on information about the user device, wherein determining the action is The timing synchronization status report will be included in the system information that will be broadcast to user devices by the wireless access network node, Broadcasting system information repeatedly over a period longer than the cycle in which user devices can read the broadcasted system information. means and A wireless access network node equipped with the following features.

8. The wireless access network node according to claim 7, wherein the message includes an emergency level indication to enhance the reliability of reading the timing-synchronized status report by the user device, and the decision of action is further based on the emergency level indication.

9. A means for paging a user device to determine whether to have the user device report reading a timing synchronization status report, wherein the determination is based on at least one of the following: information obtained from a message received from the user device, or information about when to predict a message from the user device. Based on the decision to page user devices, the means for paging user devices and A wireless access network node according to claim 7, comprising:

10. The wireless access network node according to claim 7, further comprising means for paging user devices to determine whether to cause a user device to report the reading of a timing synchronization status report, based at least one of the following: information obtained from a message from a user device that includes a field indicating the reading of a timing synchronization status report, or information about when the user device is expected to next send a message that includes a field indicating the reading of a timing synchronization status report.

11. The wireless access network node according to claim 7, further comprising means for receiving information about the wireless resource control status of a user device, and means for paging the user device to report reading a wireless access network timing synchronization status report in response to determining that the user device is in wireless resource control idle mode based on the information about the wireless resource control status.

12. A means for receiving a paging message from a radio access network node of a fifth-generation mobile communication network indicating an upcoming broadcast of system information including a radio timing synchronization status report, Means for receiving system information broadcast by a wireless access network node, Means for establishing a connection with a wireless access network node and transmitting a wireless resource control signaling message to the wireless access network node, including a field that includes an indication that the user device has read the wireless access network timing synchronization status report. User equipment equipped with these features.

13. A computer-readable medium containing stored program instructions, wherein when the program instructions are executed by at least one processor of a wireless access network node, the computer-readable medium causes the wireless access network node to perform the method according to any one of claims 1 to 6.

14. A computer-readable medium containing stored program instructions, wherein when the program instructions are executed by at least one processor of the user device, the computer-readable medium causes the user device to perform the method according to claim 6.

15. A computer program comprising computer executable code, wherein when the computer executable code is executed on at least one processor, the computer program is configured to cause a radio access network node of a fifth-generation mobile communication system to perform the method according to any one of claims 1 to 5.

16. A computer program comprising computer executable code, wherein the computer executable code is configured to cause a user device to perform the method described in claim 6 when executed on at least one processor.

Images