Timing-related state updates

Abstract

Embodiments of the present disclosure disclose an apparatus, method, and device for timing-related state updates, where an end device identifies access attempts for network timing-related state updates and performs access control on the access attempts for network timing-related state updates.

Description

[Technical Field]

[0001] FIELD Embodiments of the present disclosure relate generally to the field of communications, and more particularly to devices, methods, apparatus, and computer-readable storage media for timing-related state updates. [Background technology]

[0002] Clock quality information updates are one of the key aspects required to provide communication services for time-sensitive applications. Rel-18 considers enhancements to 5G timing resiliency and time-sensitive communication (TSC) and ultra-reliable low latency communication (URLLC). The network side may provide timing-related state changes in the system information block (SIB). The UE may decide to reconnect to the network to obtain more detailed information about timing synchronization.

[0003] There are a huge number of terminal devices in communication systems. Efficient and effective network timing synchronization state updates for these terminal devices remain a challenge. Therefore, there is a need for enhanced timing-related state updates. Summary of the Invention

[0004] Generally, embodiments of the present disclosure provide devices, methods, apparatus, and computer-readable storage media for timing-related state updates.

[0005] In a first aspect, a terminal device is provided, the terminal device comprising at least one processor and at least one memory containing computer program code configured, by the at least one processor, to cause the terminal device to identify access attempts for network timing-related state updates and to perform access control on the access attempts for network timing-related state updates.

[0006] In a second aspect, a network device is provided, the network device comprising: at least one processor and at least one memory containing computer program code configured, by the at least one processor, to cause the network device to: send, to a terminal device, one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts; and receive, from the terminal device, an access attempt that is access-controlled based on the one or more parameters.

[0007] In a third aspect, there is provided a method performed in a terminal device, the method including: the terminal device identifying an access attempt for a network timing-related state update; and the terminal device performing access control on the access attempt for the network timing-related state update.

[0008] In a fourth aspect, there is provided a method performed in a network device, the method including transmitting, to a terminal device, one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts, and receiving, from the terminal device, an access attempt that is access-controlled based on the one or more parameters.

[0009] In a fifth aspect, an apparatus is provided for a terminal device, the apparatus comprising: means, by the terminal device, for identifying access attempts for network timing-related state updates; and means, by the terminal device, for performing access control on the access attempts for network timing-related state updates.

[0010] In a sixth aspect, an apparatus of a network device is provided, the apparatus comprising: means for transmitting, to a terminal device, one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts; and means for receiving, from the terminal device, an access attempt that is access-controlled based on the one or more parameters.

[0011] In a seventh aspect, a terminal device is provided, the terminal device comprising: one or more transceivers; and one or more processors coupled to the one or more transceivers, the one or more transceivers causing the one or more processors to identify access attempts for network timing-related state updates and perform access control on the access attempts for the network timing-related state updates.

[0012] In an eighth aspect, a network device is provided, the network device comprising: one or more transceivers; and one or more processors coupled to the one or more transceivers, the one or more transceivers causing the network device, by the one or more processors, to send to the terminal device one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts, and receive from the terminal device an access attempt that is access-controlled based on the one or more parameters.

[0013] In a ninth aspect, there is provided a non-transitory computer readable medium comprising program instructions to cause an apparatus to perform at least a method according to the third or fourth aspect.

[0014] In a tenth aspect, a computer program is provided that includes instructions that, when executed by an apparatus in a terminal device, cause the apparatus to at least identify access attempts for network timing-related state updates and perform access control on access attempts for network timing-related state updates.

[0015] In an eleventh aspect, a computer program is provided that includes instructions that, when executed by a network device, cause the device to at least: send one or more parameters to a terminal device for configuring the terminal device to perform access control on timing-related state update access attempts; and receive, from the terminal device, access-controlled access attempts based on the one or more parameters.

[0016] In a twelfth aspect, a terminal device is provided, the terminal device comprising: an identification circuit configured to identify an access attempt for a network timing-related state update; and an execution circuit configured to execute access control on the access attempt for the network timing-related state update.

[0017] In a thirteenth aspect, a network device is provided, the network device comprising: a transmitting circuit configured to transmit, to a terminal device, one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts; and a receiving circuit configured to receive, from the terminal device, an access attempt that is access-controlled based on the one or more parameters.

[0018] It should be understood that the Summary is not intended to identify key features or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure can be readily understood through the following description. [Brief explanation of the drawings]

[0019] Some embodiments will now be described with reference to the accompanying drawings. [Figure 1] FIG. 1 illustrates an example of a network environment in which embodiments of the present disclosure may be implemented. [Figure 2] FIG. 2 illustrates an example of a signaling flow between a terminal device and a network device according to some embodiments of the present disclosure. [Figure 3] FIG. 3 is a flowchart illustrating an example of a method performed in a terminal device according to an embodiment of the present disclosure. [Figure 4] FIG. 4 is a flowchart illustrating an example of a method performed in a network device acting as a candidate cell according to another embodiment of the present disclosure. [Figure 5] FIG. 5 illustrates a simplified block diagram of an example of an apparatus suitable for implementing embodiments of the present disclosure. [Figure 6] 6 is a block diagram illustrating an example of a computer-readable medium according to an embodiment of the present disclosure. Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0020] The principles of the present specification will be explained with reference to some examples. It should be understood that these examples are not intended to limit the scope of the present specification, but are merely for illustrative purposes and are provided to assist those skilled in the art in understanding and practicing the present specification. The disclosure described herein can be implemented in various ways other than those described below.

[0021] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0022] References herein to "one embodiment," "embodiment," "exemplary embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments necessarily include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one skilled in the art to affect that feature, structure, or characteristic in connection with other embodiments, whether or not explicitly stated.

[0023] Although terms such as "first" and "second" may be used herein to describe various elements, it should be understood that these elements should not be limited by these terms. These terms are merely used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" encompasses any and all combinations including one or more of the listed terms.

[0024] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly dictates otherwise. Furthermore, as used herein, the terms "comprises," "comprising," "has," "having," "includes," and / or "comprising" identify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, "at least one of: " and "at least any of: " and similar expressions, when a list of two or more elements is connected by "and," mean at least any element, at least two or more elements, or at least all elements.

[0025] In this application, the term "circuit" means (a) hardware-only circuit implementation (e.g., implementation using only analog and / or digital circuitry); (b) a combination of hardware circuitry and software, e.g., (where applicable); (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) A configuration in which a portion of a hardware processor and software (including a digital signal processor), software, and memory work together to cause a device such as a mobile phone or server to perform various functions; (c) hardware circuitry and / or processors (e.g., microprocessors or portions of microprocessors) that require software (e.g., firmware) to operate, but the software may be absent if not necessary for operation; It may refer to any one or more, or all of the above.

[0026] This definition of circuit applies to all uses of the term in this application, i.e., in all claims. By way of further example, the term circuit as used herein also encompasses a simple hardware circuit or processor (or processors), or a portion of a hardware circuit or processor and its associated software and / or firmware implementation. The term circuit also encompasses, for example, baseband or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular networks, and other computing systems, where applicable to particular claim elements.

[0027] As used herein, the term "communication network" refers to a network conforming to an appropriate communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), or Narrowband Internet of Things (NB-IoT). Furthermore, communications between terminal devices and network devices in a communication network may be performed according to any appropriate generation of communication protocol, including, but not limited to, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), sixth-generation (6G) communication protocols, and other protocols now known or developed in the future. Embodiments of the present disclosure are applicable to various communication systems. Given the rapid development of communication technologies, future communication technologies and systems may also embody the present disclosure. The scope of the present disclosure is not limited to only the aforementioned systems.

[0028] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services. A network device may refer to, for example, a base station (BS) or access point (AP), a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a new radio (NR) NB (also known as gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a repeater, a low-power node such as a femto or pico node, etc. This varies depending on the term and technology being used.

[0029] The term "terminal equipment" refers to any terminal device capable of wireless communication. By way of example and not limitation, terminal equipment may also be referred to as communications equipment, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal equipment may include mobile phones, mobile phone terminals, smartphones, VoIP phones, wireless local loop phones, tablets, wearable devices, PDAs, portable computers, desktop computers, digital cameras and other imaging devices, gaming devices, music storage and playback devices, automotive wireless terminals, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches and other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automation processing chain environments), consumer electronics devices, and devices operating on commercial and / or industrial wireless networks. In the following description, the terms "terminal equipment", "communications device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0030] In the Study on 5G Timing Resiliency and TSC&URLLC enhancements Rel-18 on Radio Access Network (RAN) clock quality information updates, SIBs are proposed to provide timing synchronization status changes and the UE may decide to reconnect to get more detailed information.

[0031] Network timing synchronization state information from the RAN or user plane function / network side time-sensitive network (TSN) translator (NW-TT) may include node synchronization state, node synchronization capability, primary source description, and primary source event parameters.

[0032] Timing synchronization state updates are a new use case for UEs to connect, and there may be other factors that trigger RRC connection establishment even when the UE is performing backoff (T390 is running for a particular access category). Currently, it is not clear how the various triggers interact with each other.

[0033] Furthermore, the inventors have realized that a large number of UEs may attempt to read the system information and obtain the latest available clock quality information. If these UEs simultaneously access the network to obtain clock quality information, congestion is likely to occur. Therefore, it is not desirable for the UEs to always immediately transition to a Radio Resource Control (RRC) connected state (RRC_CONNECTED state or mode) to obtain the latest available clock quality information. Instead, it is beneficial to avoid this congestion by distributing the UEs' connection attempts in the time domain.

[0034] In this disclosure, an improved solution for timing-related state updates is provided that performs access control on access attempts for timing-related state updates to reduce or avoid network-side congestion.

[0035] In some embodiments, the terminal device identifies access attempts for network timing-related state updates. The terminal device then performs access control on the access attempts for network timing-related state updates.

[0036] The solution proposed herein can substantially reduce or avoid network-side congestion caused by network timing related state updates, resulting in efficient and effective network timing synchronization state updates.

[0037] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The principles and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Referring to Figure 1, Figure 1 shows an example of a network environment 100 in which embodiments of the present disclosure can be implemented.

[0038] The network environment 100 may be part of a communications network and includes terminal devices 110 and network devices 120, which communicate with each other and through each other to other devices.

[0039] Network environment 100 may include any suitable number of devices and cells. In network environment 100, terminal device 110 and network device 120 may communicate data and control information with each other. The link from network device 120 to terminal device 110 is referred to as DL, and the link from terminal device 110 to network device 120 is referred to as UL.

[0040] The number of terminal devices 110 and the number of network devices 120 shown in communication network environment 100 are for illustrative purposes only and are not intended to limit the scope of the present disclosure. In some embodiments, communication network environment 100 may include any number of terminal devices and / or any number of network devices.

[0041] Communications in network environment 100 may be in accordance with any suitable existing or future-developed communications standard or protocol, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE Advanced (LTE-A), Fifth Generation (5G) New Radio (NR), Sixth Generation (6G) or later, Wireless Fidelity (Wi-Fi®), or Worldwide Interoperable Microwave Access (WiMAX) standards, or other suitable communications technology. For example, these include Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), Bluetooth®, ZigBee®, Machine Type Communications (MTC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communications (mMTC), Ultra-Reliable Low Latency Communications (URLLC), Carrier Aggregation (CA), Dual Connectivity (DC), New Radio License-Free (NR-U) technologies, etc.

[0042] In some embodiments, the network device 120 transmits network timing-related state information to the terminal device 110. The terminal device 110 determines whether the RAN clock quality information has changed based on the network timing-related state information transmitted from the network device 120. If the terminal device determines that the RAN clock quality information has changed, the terminal device 110 needs to obtain the latest clock quality information. That is, the terminal device 110 needs to perform a network timing-related state update. For example, the terminal device 110 initiates an access attempt to obtain detailed timing-related information (e.g., the latest clock quality information) from the network device 120.

[0043] In some embodiments, terminal device 110 identifies access attempts for network timing-related state updates and performs access control on access attempts for network timing-related state updates.

[0044] 2 illustrates an example of a signaling flow 200 between a terminal device and a network device in accordance with an embodiment of the present disclosure. For illustrative purposes, the signaling flow 200 will be described with reference to FIG.

[0045] 2, the network device 120 transmits network timing related state information (e.g., using SIB9) to the terminal device 110. For example, the network timing related state information from the network device 120 (i.e., RAN or UPF / NW-TT) may include node synchronization state, node synchronization capability, primary source description, and primary source event parameters.

[0046] Upon receiving the network timing related state information, the terminal device 110 determines whether the RAN clock quality information has changed.

[0047] The terminal device determines that the RAN clock quality information has changed using the following method. SIB broadcast information (for UEs in RRC_IDLE and RRC_INACTIVE states) and dedicated RRC signaling for UEs in RRC_CONNECTED state allows the UE to determine: that the timing synchronization state of the cell to which the UE is connected has changed; the timing synchronization state of the new cell on which the UE is camped after cell reselection is different from the timing synchronization state of the cell on which the UE was previously camped; If the UE determines that the RAN clock quality information has changed and the TSCTSF requests a network connection when the RAN clock quality information has changed, the UE shall perform registration (if the UE is in RRC_IDLE state) or perform a UE triggered connection resume (if in RRC inactive state).

[0048] A UE in RRC_INACTIVE or RRC_IDLE state may be notified of changes in the RAN clock quality information. The gNB includes a Reference Report ID in SIB9 to inform UEs reading SIB9 that new clock quality information is available. The UE compares the Reference Report ID with its locally stored Reference Report IDs to determine whether it has already obtained the previous clock quality information. The Reference Report ID consists of a Report ID range and an Event ID (an integer). The range identifies either a set of cells within a single gNB or a set of cells across multiple gNBs. In the latter case, signaling can be further reduced, as a UE moving to another gNB does not need to obtain clock quality details.

[0049] For example, a system information block (e.g., SIB9) may include a reference report ID, which is used as a notification to the terminal device 110. That is, the terminal device reads SIB9 to determine whether new clock quality information is available. For example, the UE compares the reference report ID with a locally stored reference report ID to determine whether it has already obtained the latest available clock quality information. If the RAN clock quality information changes, the terminal device 110 may decide to initiate an access attempt for a network timing-related state update.

[0050] The above-mentioned identification method is merely an example, and other methods may also be used.

[0051] In the terminal device 110, access attempts for network timing-related state updates are identified as shown in Figure 2. There are usually many types or access categories of access attempts, each triggered by different reasons or causes. Therefore, to perform access control, it is first necessary to identify access attempts for network timing-related state updates.

[0052] In some embodiments, a unified access control (UAC) framework may be modified to facilitate identification of access attempts for network timing-related state updates. The UAC framework is a framework in current 5G NR systems that enables unified access control for access attempts before RRC connection establishment (for UEs in RRC_IDLE state) or upon RRC connection resumption (for UEs in INACTIVE state).

[0053] To enable access control for access attempts for timing-related state updates (triggered by SIB indications), new access categories and / or access identities can be defined for such access attempts.

[0054] In some embodiments, the access identity may be predefined as a reserved value of the access identity number in the UAC framework. For illustrative purposes, an example of an access identity as specified in TS 22.261 is provided below: [Table 1]

[0055] In Table 1, Access Identity 1 is used by UEs configured for MPS for the public land mobile network (PLMN) for which the configuration is valid. The PLMNs for which the configuration is valid are the HPLN, PLMNs equivalent to the HPLN, and visited PLMNs in the home country. Additionally, Access Identity 1 is valid for UEs that are explicitly authorized by the network based on a specific configured PLMN within or outside the home country.

[0056] Access Identity 2 is used by MCS-configured UEs in the configured PLMNs. Valid PLMNs are the HPLN or equivalent PLMNs, and visited PLMNs in the home country. Access Identity 2 is also valid when the UE is explicitly authenticated by the network based on a specific configured PLMN in or outside the home country.

[0057] Access Identity 3 is used by UEs where disaster conditions apply and is valid for a PLMN to indicate to potential disaster inbound roamers that the UE has access to the PLMN. Access Identities 4 to 10 are reserved for future use.

[0058] Access identities 11 and 15 are only valid in the home PLMN if no EHPLMN list exists or in any EHPLMN. Access identities 12, 13, and 14 are only valid in the home PLMN and visited PLMNs in the home country. For this purpose, home country is defined as the country indicated by the MCC portion of the IMSI.

[0059] From Table 1, it can be seen that access identities 4 to 11 are not used but are still reserved. Therefore, an access identity may be predefined as any of the "access identity numbers" from 4 to 10. For example, any of access identities 4 to 11 may be defined for the UE that triggers a timing-related state update access attempt.

[0060] In some embodiments, the access identity may be predefined as a used value of the access identity number in the UAC framework. In some embodiments, the access identity may be predefined as one of the "access identity numbers" excluding 4 through 10. For example, any of access identities 1 through 3 and 11 through 15 may be additionally redefined for the UE to trigger a timing-related state update access attempt.

[0061] Additionally or alternatively, new access categories may be defined. For illustrative purposes, an example of an access identity as specified in TS 22.261 is provided below: [Table 2]

[0062] In Table 2, 8 bits are used to indicate the access category number, with 64 possible values. Of these, values ​​11 through 31 are reserved for future use, while values ​​0 through 10 and 32 through 63 are used. Thus, similar to access identities, it is possible to define new access categories and map access identities to timing-related state updates. In this case, one of the reserved bits in the "access category number" can be used. Alternatively, it is possible to integrate timing-related state updates into existing access categories, but in this case the existing access categories must be prohibited.

[0063] In some embodiments, access attempts are identified based on one or more of an access category or an access identity, and the access category and access identity are mapped to timing-related state update access attempts. For example, the mapping from access categories or access identities to timing-related state update access attempts may be predefined, such as by a standard or specification. Additionally or alternatively, the mapping from access categories or access identities to timing-related state update access attempts may be preconfigured by network device 120.

[0064] In some embodiments, the access category or access identity may be encoded into a subscriber identity module (SIM) module or a universal SIM (USIM) module.

[0065] Based on the new access category and / or the new access identity, the network device identifies an access attempt for a network timing-related state update. For example, the terminal device determines whether the access category and / or access identity associated with the access attempt corresponds to a new access category and / or access identity defined for a network timing-related state update. If so, the access attempt for a network timing-related state update is identified.

[0066] In some embodiments, the identification of the access randomness of the network timing related state updates may be performed by means other than the UAC, for example, the access attempt itself may provide a specific identity that can be used to identify the access attempt.

[0067] Returning to FIG. 2, after identifying the access attempts for network timing related state updates, terminal device 110 performs access control on the access attempts, for example, by distributing UE connection attempts in the time domain.

[0068] In some embodiments, access control may be based on a Unified Access Control (UAC) framework.

[0069] The UAC defined in RRC may allow randomization of UEs gaining access when the cell is congested. In some embodiments, the terminal device receives from the network device one or more UAC parameters dedicated to access categories or access identities that are mapped to timing-related state update access attempts.

[0070] The information element (IE) UAC-BarringInfoSetList provides a list of access control parameter sets. An access category consists of access parameters based on one of the sets. IE UAC-BarringInfoSetList includes uac-BarringFactor, uac-BarringTime, and uac-BarringForAccessIdentity. uac-BarringForAccessIdentity indicates whether an access attempt is permitted for each access identity. Bits 0 to 6 of the bit string correspond to access identity 1, access identity 2, access identity 11, access identity 12, access identity 13, access identity 14, and access identity 15, respectively. A value of 0 indicates that an access attempt is permitted for the corresponding access identity, and a value of 1 indicates that an access attempt is not permitted.

[0071] For example, the network sets a prohibition time for each access category and access identity, and the UE randomly generates a time based on the prohibition time.

[0072] In some embodiments, the network side can configure UAC parameters specific to the access attempt. For example, the network side can send or update the UAC parameters to the terminal device via an appropriate message at an appropriate time. In some embodiments, the terminal device 110 receives the UAC parameters from the network device 120 in advance before a timing-related status update is required. In some embodiments, the terminal device 110 receives the UAC parameters from another network device in advance before a timing-related status change occurs.

[0073] In some embodiments, the access attempt includes information about a connection establishment cause or connection resumption cause for the timing-related state update access attempt, where the connection establishment cause or connection resumption cause is predefined. A new establishment / resumption cause can be defined for an access attempt triggered due to a timing-related state update. Alternatively, the connection establishment cause or connection resumption cause is defined as mobile-originated (MO) signaling. That is, a connection establishment or connection resumption due to a timing-related state update may be classified as the same cause as MO signaling.

[0074] In some embodiments, the terminal device performs an access attempt for timing-related state updates to obtain detailed timing-related state information from the network device, for example, by initiating a random access procedure to obtain a connection. In some embodiments, the terminal device performs an access attempt for timing-related state updates through a small data transmission (SDT) procedure instead of obtaining a connection.

[0075] It should be noted that the process of performing an access attempt through the Small Data Transmission (SDT) procedure to obtain detailed timing-related information from a network device may be independent of the UAC framework. That is, if a terminal device decides to obtain detailed timing-related information, it may use the Small Data Transmission (SDT) procedure without performing an access prohibition check. In other words, SDT may also be used for this purpose to provide detailed timing-related information while avoiding connections.

[0076] In some embodiments, if the access attempt for timing-related state updates is performed through a small data transmission (SDT) procedure, the SDT transmission to the network device may include a connection establishment cause or a connection resumption cause, for example, the establishment / resumption cause of MO signaling may be reused.

[0077] In some embodiments, the terminal device 110 receives configuration information from the network device 120 indicating that the terminal device uses the SDT procedure to obtain detailed timing-related state information. That is, the NW can configure the UE to use SDT for timing-related state updates, and if the terminal device is not so configured, the terminal device cannot use SDT for this purpose.

[0078] In some embodiments, for an access attempt for a timing-related state update, the terminal device generates a random value and determines whether it is less than the value indicated by uac-BarringFactor included in the "UAC Barring Parameters." If it is less, the terminal device 110 considers the access attempt to be allowed. Otherwise, the terminal device 110 considers the access attempt to be barred. If the access attempt is considered barred, the terminal device generates a random number "rand" that is uniformly distributed in the range 0≦rand<1. Then, it starts a timer T390 for the access category. The timer value is calculated using uac-BarringTime included in the "UAC Barring Parameters" as follows: T390=(0.7+0.6*rand)*uac-BarringTime

[0079] At the start of the procedure, the UE shall: Consider the access attempt as barred if timer T390 is running for the access category; Or, consider the access attempt as barred if timer T302 is running and the access category is neither "2" nor "0"; The access attempt may be performed after expiry of T390 or may perform other access control in the same way as above.

[0080] 2, after experiencing the above access control, the terminal device 110 transmits a request for detailed timing-related information to the network device 120. Upon receiving this request, the network device 120 transmits the detailed timing-related information (e.g., the latest clock quality information) to the terminal device 110.

[0081] In some embodiments, terminal device 110 transmits a request for detailed timing-related state information to a network device based on determining that another access attempt has been triggered and authorized. That is, even if an access attempt for a timing-related state update is triggered and the UE is performing backoff due to an active T390 timer, if another access attempt (e.g., MO data) is triggered at the same time and is not subject to UAC or access to that attempt is authorized, the UE may still perform the access attempt and send a timing-related state update request to the network.

[0082] Thus, upon receiving the request, the network can provide detailed timing-related status updates (e.g., latest available clock quality information) to the UE.

[0083] In some embodiments, the detailed timing related information provided by the network device may include timing synchronization status information, or RAN clock quality information, or the like.

[0084] For example, the network device may provide the UE in the RRC_Connected state with the latest clock quality information of the RAN. If the UE supports Access Stratum Time Synchronization (ASTI) in Unified Data Management (UDM), the "Access and Mobility Subscription Data" may additionally contain the following clock quality reporting control information: Clock quality detail level: Indicates whether and what type of clock quality information is provided to the UE, and takes the value of either clock quality metrics or an indication of acceptable / unacceptable. UE clock quality acceptance criteria (if clock quality level is "acceptable / not acceptable indication"): UE clock quality acceptance criteria. The acceptance criteria may be defined based on any of the attributes, for example, traceability to time source, UTC or GNSS, synchronization state, clock accuracy, PTP clock class, frequency stability. For example, it may include the acceptable clock accuracy, the acceptable frequency stability, etc.

[0085] From the above, we can see that the UAC framework can adequately support access control for timing-related state updates. This allows us to reuse existing frameworks while effectively reducing or avoiding communication congestion. At the same time, it has minimal impact on existing communication systems.

[0086] In some embodiments, access control may be performed independently of the UAC framework. For example, the terminal device 110 performs access control by generating a random value based on an upper limit value and performing backoff based on the generated random value. In other words, the UE applies a default value to backoff generation. For example, if a UAC is not configured in a cell, the UE may apply a default value to backoff generation. Here, the default value or upper limit value has a similar function to the aforementioned "uac-BarringFactor" and may be used interchangeably herein.

[0087] In some embodiments, the upper limit value is one of a predefined default value, a default value received from a network device via system information (e.g., SIB), or dedicated signaling. For example, the default value may be predefined in a specification, signaled from the network (e.g., when indicating that new clock quality information is available via system information (SIB) with a reference report ID, or dedicated signaling), or determined by the UE.

[0088] In some embodiments, there is a default value that the terminal device determines based on either a default pacing period, a terminal device-specific DRX period, a system information change period, the type of service the terminal device has, or a timer value provided in the non-access stratum (NAS).

[0089] 3 is a flowchart illustrating an example of a method 300 performed in a terminal device in accordance with an embodiment of the present disclosure. For purposes of explanation, the method 300 will be described with reference to FIG. 1 and from the perspective of the terminal device 110. It should be noted that although the method 300 is described from the perspective of the terminal device 110, it may also be performed by other terminal devices.

[0090] In step 310, terminal device 110 identifies an access attempt for a network timing-related state update. In step 320, terminal device 110 performs access control on the access attempt for a network timing-related state update.

[0091] In some embodiments, terminal device 110 can identify an access attempt based on one or more of an access category or an access identity, where the access category and access identity are mapped to a timing-related state update access attempt.

[0092] In some embodiments, the mapping from access categories or access identities to timing-related state update access attempts may be predefined or pre-configured.

[0093] In some embodiments, the access category or access identity is encoded into a Universal Subscriber Identity Module (USIM).

[0094] In some embodiments, access control is performed based on a Unified Access Control (UAC) framework.

[0095] In some embodiments, terminal device 110 further receives from the network device one or more UAC parameters specific to the access category or access identity that is mapped to the timing-related state update access attempt.

[0096] In some embodiments, the access identity may be predefined as a reserved value for the access identity number in the UAC framework.

[0097] In some embodiments, the access identity may be predefined as a used value of the access identity number in the UAC framework.

[0098] In some embodiments, at terminal device 110, the access attempt may include information regarding a connection establishment cause or a connection resumption cause for a timing-related state update access attempt, where the connection establishment cause or the connection resumption cause is predefined.

[0099] In some embodiments, a connection establishment cause or a connection resumption cause may be defined as Mobile Originated (MO) signaling.

[0100] In some embodiments, terminal device 110 performs an access attempt through a small data transmission (SDT) procedure to obtain detailed timing-related information from the network device.

[0101] In some embodiments, the detailed timing related information includes timing synchronization status information or RAN clock quality information.

[0102] In some embodiments, terminal device 110 further receives configuration information from the network device indicating that the terminal device will use SDT procedures to obtain detailed timing-related information.

[0103] In some embodiments, terminal device 110 sends a request to a network device for detailed timing-related information based on determining that another access attempt has been triggered and authorized.

[0104] In some embodiments, the terminal device 110, when performing access control, includes generating a random value for performing access control based on the upper limit value.

[0105] In some embodiments, the upper limit value of the terminal device 110 may be one of a predefined default value, a value received from a network device via system information or dedicated signaling, or a value determined by the terminal device based on a default pacing period, a terminal device-specific DRX period, a system information change period, the type of service the terminal device has, or a timer value provided in the non-access stratum (NAS).

[0106] Based on the set upper limit value, the terminal device randomly generates a backoff period for controlling access attempts. When the backoff period expires, the terminal device directly sends a detailed timing-related information request. Alternatively, the terminal device first generates a random number, and if the random number is smaller than a predetermined value, generates another backoff time based on the random number. In this case, when the period expires, another access attempt is attempted.

[0107] All operations and functions described above with reference to Figure 2 are equally applicable to method 300 and have similar effect, and details are omitted for the sake of brevity.

[0108] 4 illustrates a flowchart of an example method 400 performed in a network device in accordance with some embodiments of the present disclosure. For purposes of explanation, the method 400 will be described with reference to FIG. 1 from the perspective of the network device 120. It should be understood that although the method 400 is described from the perspective of the network device 120, it may be performed by any other network device.

[0109] In step 410, network device 120 transmits to the terminal device one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts. In step 420, network device 120 receives from the terminal device an access attempt that is access-controlled based on the one or more parameters.

[0110] In some embodiments, the access control is based on a unified access control (UAC) framework, and the one or more parameters include UAC parameters specific to access categories or access identities mapped to timing-related state update access attempts.

[0111] In some embodiments, the network device 120 may further receive from the end device an access attempt that includes information regarding a connection establishment cause or a connection resumption cause for the timing-related state update access attempt, where the connection establishment cause or the connection resumption cause is predefined.

[0112] In some embodiments, the connection establishment cause or connection resumption cause may be predefined as Mobile Originated (MO) signaling.

[0113] In some embodiments, the network device 120 may further transmit detailed timing-related information to the end device based on the connection establishment cause or connection resumption cause indicated in the access attempt.

[0114] In some embodiments, detailed timing related information is transmitted to the terminal device through a small data transmission (SDT) procedure.

[0115] In some embodiments, the network device further transmits configuration information to the terminal device indicating that the terminal device uses the SDT procedure to obtain detailed timing-related information.

[0116] In some embodiments, the one or more parameters may include an upper limit value that the terminal device uses when generating random values ​​for performing access control. As mentioned above, this upper limit value may also be referred to as a default value used to generate, for example, a backoff value.

[0117] In some embodiments, the upper limit value is either a predefined default value, a value received from a network device via system information or dedicated signaling, or a value determined by the terminal device based on either a default pacing period, a terminal device-specific DRX period, a system information change period, the type of service the terminal device has, or a timer value provided in the non-access stratum (NAS).

[0118] In some embodiments, the detailed timing related information includes timing synchronization status information or RAN clock quality information.

[0119] For example, using a set upper limit value, the terminal device may randomly generate a backoff period for controlling access attempts. When the backoff time period expires, the terminal device directly sends a request for detailed timing-related information. Alternatively, the terminal device may first generate a random number, and if the random number is smaller than a predetermined value, generate a further backoff time based on the random number. In this case, when the period expires, another access attempt will be attempted.

[0120] All of the operations and features described above with reference to Figure 2 are equally applicable to method 400 and have similar effect, and details are omitted for the sake of brevity.

[0121] In some embodiments, an apparatus (e.g., terminal device 110) capable of performing any of the operations of method 300 may include means for performing each step of method 300. The means may be implemented in any suitable form, for example, as a circuit or a software module.

[0122] In some embodiments, the apparatus may comprise means for a terminal device to identify an access attempt for a network timing related state update, and means for the terminal device to perform access control on the access attempt for the network timing related state update.

[0123] In some embodiments, the apparatus comprises means for identifying an access attempt based on one or more of an access category or an access identity, the access category and access identity being mapped to a timing-related state update access attempt.

[0124] In some embodiments, the manner in which access categories or access identities are mapped to timing-related state update access attempts may be predefined or preconfigured.

[0125] In some embodiments, the access category or access identity may be encoded into a Universal Subscriber Identity Module (USIM).

[0126] In some embodiments, access control is performed based on a Unified Access Control (UAC) framework.

[0127] In some embodiments, the device may further comprise means for receiving, from the network device, one or more UAC parameters specific to an access category or access identity mapped to a timing-related state update access attempt.

[0128] In some embodiments, the access identity may be predefined as a reserved value for the access identity number in the UAC framework.

[0129] In some embodiments, the access identity may be predefined as a pre-used value of the access identity number in the UAC framework.

[0130] In some embodiments, the access attempt may include information regarding a connection establishment or connection resumption cause of the timing-related state update access attempt, where the connection establishment or connection resumption cause is predefined.

[0131] In some embodiments, a connection establishment cause or a connection resumption cause may be defined as Mobile Originated (MO) signaling.

[0132] In some embodiments, the device comprises means for performing an access attempt through a small data transmission (SDT) procedure to obtain detailed timing-related information from the network device.

[0133] In some embodiments, the apparatus further comprises means for receiving, from the network device, configuration information indicating that the terminal device uses an SDT procedure to obtain detailed timing-related information.

[0134] In some embodiments, the device further comprises means for transmitting a request for detailed timing-related information to the network device based on determining that another access attempt was triggered and allowed.

[0135] In some embodiments, the means for performing access control may comprise means for generating a random value for performing access control based on the upper limit value.

[0136] In some embodiments, the upper limit value is either a predefined default value, a value received from the network device via system information or dedicated signaling, or a value determined by the terminal device based on either a default pacing period, a terminal device-specific DRX period, a system information change period, the type of service the terminal device has, or a timer value provided in the non-access stratum (NAS).

[0137] In some embodiments, the detailed timing related information includes timing synchronization status information or RAN clock quality information.

[0138] In some embodiments, the apparatus further comprises means for performing other steps of some embodiments of method 300. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code being configured to cause the at least one processor to perform the operations of the apparatus.

[0139] In some embodiments, the apparatus further comprises means for performing other steps of some embodiments of method 300. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code configured, by the at least one processor, to cause the apparatus to perform operations.

[0140] In some embodiments, an apparatus is provided that is implemented in a terminal device. The apparatus may comprise means for the terminal device to identify access attempts for network timing-related state updates. Furthermore, the apparatus comprises means for the terminal device to perform access control on access attempts for network timing-related state updates. It should be noted that the apparatus can be used separately from or in combination with the solution described with reference to Figure 2.

[0141] In some embodiments, a device capable of performing any of the methods 400 (e.g., network device 120) may comprise means for performing each step of the method 400. The means may be implemented in any suitable form. For example, the means may be implemented as a circuit or a software module.

[0142] In some embodiments, the apparatus may comprise means for transmitting, to a terminal device, one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts, and means for receiving, from the terminal device, access-controlled access attempts based on the one or more parameters.

[0143] In some embodiments, the access control is based on a unified access control (UAC) framework, and the one or more parameters include one or more UAC parameters dedicated to an access category or access identity mapped to a timing-related state update access attempt T.

[0144] In some embodiments, the apparatus may further comprise means for receiving, from the terminal device, an access attempt including information regarding a connection establishment cause or a connection resumption cause for the timing-related state update access attempt, wherein the connection establishment cause or the connection resumption cause is predefined.

[0145] In some embodiments, the connection establishment cause or connection resumption cause may be predefined as Mobile Originated (MO) signaling.

[0146] In some embodiments, the apparatus may further comprise means for transmitting, to the terminal device, detailed timing-related information based on the connection establishment cause or connection resumption cause indicated in the access attempt.

[0147] In some embodiments, detailed timing related information is transmitted to the terminal device via a small data transmission (SDT) procedure.

[0148] In some embodiments, the apparatus may further comprise means for transmitting configuration information to the terminal device instructing the terminal device to obtain detailed timing-related information using an SDT procedure.

[0149] In some embodiments, the one or more parameters include an upper limit value used by the terminal device to generate random values ​​for performing access control.

[0150] In some embodiments, the upper limit value is either a predefined default value, a value received from the network device via system information or dedicated signaling, or a value determined by the terminal device based on any of the following: a default pacing period, a terminal device-specific DRX period, a system information change period, a service type that the terminal device has, or a timer value provided in the non-access stratum (NAS).

[0151] In some embodiments, the detailed timing related information includes timing synchronization status information or RAN clock quality information.

[0152] In some embodiments, the apparatus further comprises means for performing other steps of some embodiments of method 400. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code configured to cause the at least one processor to perform the operations of the apparatus.

[0153] In some embodiments, an apparatus is provided that is implemented in a network device. The apparatus may comprise means for transmitting, to a terminal device, one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts. Furthermore, the apparatus comprises means for receiving, from the terminal device, an access-controlled access attempt based on the one or more parameters. It should be noted that the apparatus can be used separately from or in combination with the solution described with reference to FIG. 2.

[0154] 5 is a simplified block diagram of an apparatus 500 suitable for carrying out embodiments of the present disclosure. The apparatus 500 may be provided to implement, for example, a communications apparatus such as the terminal equipment 110 or the network equipment 120 shown in FIG. 1. As shown, the device 500 includes one or more processors 510, one or more memories 520 connectable to the processors 510, and one or more transmitters and / or receivers (TX / RX) 540 (communications modules) connectable to the processors 510.

[0155] The TX / RX 540 is for bidirectional communication. The TX / RX 540 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communication with other network elements. The communication interface may be a hardware-based or software-based interface. For example, the communication interface may be one or more transceivers. The one or more transceivers are connected to one or more antennas or antenna ports to wirelessly transmit and / or receive communication signals. The antennas or antenna ports may be of the same or different types. The antennas or antenna ports may be located in different locations within the device. The one or more transceivers enable the device to communicate with other devices, wired and / or wirelessly. The transceivers support one or more wireless technologies. For example, the one or more transceivers may include a cellular subsystem, a WLAN subsystem, and / or a Bluetooth subsystem. The one or more transceivers may include a processor, a controller, a radio, a socket, a plug, a buffer, or similar circuitry to form one or more communication channels to one or more radio frequency units.

[0156] Processor 510 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), processors based on multi-core processor architectures, etc. Device 500 may have multiple processors, such as application specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

[0157] The memory 520 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 524, electrically erasable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), other magnetic and / or optical storage devices, etc. Examples of volatile memories include random access memory (RAM) 522 and other volatile memories that cannot retain data during power-off periods.

[0158] The computer program 530 includes computer-executable instructions that are executed by the associated processor 510. The program 530 may be stored in ROM 524. The processor 510 can load the program 530 into RAM 522 to perform any suitable operations and processes.

[0159] The embodiments of the present disclosure may be implemented by a program, which allows the device 500 to perform any of the processes disclosed above and described with reference to Fig. 2. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0160] In some embodiments, the program 530 may be tangibly stored on a computer-readable medium contained in the device 500 (e.g., in memory 520) or other storage accessible by the device 500. The device 500 may load the program 530 from the computer-readable medium into RAM 522 and execute it. The computer-readable medium may include any type of tangible non-volatile storage device, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0161] 6 shows an example of a computer readable medium 600 in the form of a CD or DVD, on which the program 530 is stored.

[0162] In general, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. While various aspects of embodiments of the present disclosure have been described using block diagrams, flowcharts, or other graphical representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented by, by way of non-limiting example, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or any combination thereof.

[0163] The present disclosure also provides at least one computer program product tangibly recorded on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, that execute on a target real or virtual processor device to perform the method 300 or 400 described above with reference to FIGS. 3 and 4. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. The machine-executable instructions for the program modules may be executed in local or distributed devices. In a distributed device, the program modules may be located in both local and remote storage media.

[0164] Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, and executed by the processor or controller to implement the functions / acts specified in the flowcharts and / or block diagrams. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0165] In the context of the present disclosure, computer program code or associated data may be transmitted by any suitable medium to enable a device, apparatus, or processor to perform the various processes and operations as described above, examples of which include signals, computer-readable media, etc.

[0166] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium includes, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More specific examples of computer-readable storage media include an electrical connection having one or more conductors, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. The term "non-transitory" as used herein refers not to a limitation regarding the permanence of data storage (e.g., RAM vs. ROM), but to the medium itself (i.e., a tangible medium, not a signal).

[0167] Furthermore, even if acts are shown in a particular order, this should not be interpreted as requiring that the acts be performed in the particular order or sequential order shown, or that all of the acts shown be performed, to achieve desirable results. In certain situations, multitasking or parallel processing may be advantageous. Similarly, while the above description includes some specific implementation details, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of functionality specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0168] Although the present disclosure has been described in language specifying structural features and / or method acts, it is to be understood that the present disclosure, as defined by the appended claims, is not necessarily limited to the specific features and acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A terminal device, at least one processor; When executed by the at least one processor, the terminal device is configured to: identifying access attempts for network timing related state updates; performing access control on the access attempts for the network timing-related state updates; at least one memory storing instructions for executing the A terminal device comprising:

2. the access attempt is identified based on one or more of an access category or an access identity; the access category and the access identity are mapped to timing-related state update access attempts; The terminal device according to claim 1 .

3. The terminal device of claim 2 , wherein the mapping of the access categories or access identities to timing-related state update access attempts is predefined or preconfigured.

4. The terminal device according to claim 2 , wherein the access category or the access identity is encoded in a Universal Subscriber Identity Module (USIM).

5. The terminal device according to claim 1 , wherein the access control is performed based on a Unified Access Control (UAC) framework.

6. The terminal device of claim 4 , further configured to receive, from a network device, one or more UAC parameters specific to the access category or the access identity mapped to the timing-related state update access attempt.

7. The terminal device according to claim 5 , wherein the access identity is predefined as a reserved value of an access identity number in the UAC framework.

8. The terminal device according to claim 5 , wherein the access identity is predefined as a previously used value of an access identity number in the UAC framework.

9. the access attempt includes information regarding a connection establishment cause or a connection resumption cause for a timing-related state update access attempt; The connection establishment cause or the connection resumption cause is predefined.

9. The terminal device according to claim 1.

10. The terminal device of claim 9 , wherein the connection establishment cause or the connection resumption cause is defined as Mobile Originated (MO) signaling.

11. The terminal device performing said access attempt via a small data transmission (SDT) procedure and obtaining detailed timing-related information from a network device; The terminal device according to claim 1 , wherein

12. The terminal device further receiving configuration information from the network device indicating that the terminal device uses an SDT procedure to obtain detailed timing-related information; The terminal device according to claim 10, wherein

13. The terminal device further sending a request for detailed timing-related information to the network device based on determining that another access attempt was triggered and permitted; 13. The terminal device according to claim 1, wherein the terminal device is configured to:

14. The terminal device according to claim 1 , wherein the detailed timing-related information includes timing synchronization status information or RAN clock quality information.

15. The terminal device according to claim 1 , wherein performing the access control includes generating a random number value for executing the access control based on an upper limit value.

16. The upper limit is Predefined default values, a value received from said network device via system information or dedicated signaling; or The terminal device, Default paging cycle, A DRX cycle specific to the terminal device, System information change period, The type of service provided by the terminal device, or timer values ​​provided by the Non-Access Stratum (NAS); a value determined based on either The terminal device according to claim 15, wherein the terminal device is one of the following:

17. A network device, at least one processor; When executed by the at least one processor, the network device is configured to: transmitting to a terminal device one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts; receiving, from the terminal device, an access-controlled access attempt based on the one or more parameters; at least one memory storing instructions for executing the A network device comprising:

18. The access control is based on a Unified Access Control (UAC) framework, and the one or more parameters are: one or more UAC parameters specific to an access category or access identity mapped to said timing-related state update access attempt; 20. The network device of claim 17, comprising:

19. The network device further comprises: receiving an access attempt from the terminal device, the access attempt including information regarding a connection establishment cause or a connection resumption cause for a timing-related state update access attempt; It was like this, The connection establishment cause or the connection resumption cause is predefined.

18. The network device of claim 17.

20. The connection establishment cause or the connection resumption cause is predefined as a mobile originated (MO) signaling.

20. The network device of claim 19.

21. The network device further comprises: sending detailed timing-related information to the terminal device based on the connection establishment cause or the connection resumption cause indicated in the access attempt; 20. The network device according to claim 19, wherein

22. 22. The network device of claim 21, wherein the detailed timing related information includes timing synchronization status information or RAN clock quality information.

23. 18. The network device of claim 17, wherein the detailed timing-related information is transmitted to the terminal device by a Small Data Transmission (SDT) procedure.

24. The network device further comprises: transmitting, to the terminal device, configuration information instructing the terminal device to acquire the detailed timing-related information using an SDT procedure; 23. The network device according to claim 22, wherein

25. 25. The network device according to claim 16, wherein the one or more parameters include an upper limit value used by the terminal device to generate random values ​​for performing the access control.

26. The upper limit is Predefined default values, a value received from said network device via system information or dedicated signaling; The terminal device Default paging cycle, A DRX cycle specific to the terminal device, System information change period, The type of service provided by the terminal device, or timer values ​​provided by the Non-Access Stratum (NAS); a value determined based on any of the following:

25. The network device of claim 24, wherein:

27. A method performed by a terminal device, comprising: identifying, by the terminal device, an access attempt for a network timing related state update; the terminal device performing access control on the access attempts for the network timing-related state updates; A method comprising:

28. 1. A method performed by a network device, comprising: transmitting to a terminal device one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts; receiving, from the terminal device, an access attempt that is access controlled based on the one or more parameters; A method comprising:

29. A device of a terminal device, means for identifying access attempts for network timing related state updates, in the terminal device; means, in the terminal device, for performing access control on the access attempts for the network timing-related state updates; An apparatus comprising:

30. A device of a network device, means for transmitting to a terminal device one or more parameters for configuring the terminal device to perform access control on timing-related state update access attempts; means for receiving, from the terminal device, an access attempt that is access controlled based on the one or more parameters; An apparatus comprising:

31. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method of claim 27 or 28.

Images