Access control method, terminal device, and network device

Abstract

Provided are an access control method, a terminal device, and a network device. The access control method comprises: a terminal device triggers access control, and executes the access control on the basis of a first configuration, the first configuration comprising an access control parameter of the terminal device, and the first configuration satisfying one or more of the following: the first configuration is used for the terminal device to determine whether to adjust the access control parameter; the first configuration is used for the terminal device to determine whether an access attempt is allowed; the first configuration belongs to one of multiple sets of configurations associated with a first access category, and the first access category is an access category corresponding to a service triggering access control.

Description

Access control methods, terminal equipment and network equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to an access control method, terminal equipment, and network equipment. Background Technology

[0002] Before initiating a call, a terminal device must perform access control. For example, the terminal device can trigger and execute access control, which can be called unified access control (UAC). Currently, when a terminal device executes UAC, the access efficiency is relatively low, affecting user experience and network performance.

[0003] Summary of the Invention

[0004] This application provides an access control method, a terminal device, and a network device. The various aspects covered by this application are described below.

[0005] In a first aspect, an access control method is provided, comprising: a terminal device triggering access control and executing the access control according to a first configuration; wherein the first configuration includes access control parameters of the terminal device, and the first configuration satisfies one or more of the following: the first configuration is used by the terminal device to determine whether to adjust the access control parameters; the first configuration is used by the terminal device to determine whether to allow access attempts; the first configuration belongs to one of multiple configurations associated with a first access category, and the first access category is the access category corresponding to the service that triggers the access control.

[0006] Secondly, an access control method is provided, comprising: a network device sending a first configuration to a terminal device, the first configuration being used by the terminal device to perform access control, the first configuration including access control parameters of the terminal device; wherein the first configuration satisfies one or more of the following: the first configuration is used by the terminal device to determine whether to adjust the access control parameters; the first configuration is used by the terminal device to determine whether to allow an access attempt; the first configuration belongs to one of multiple configurations associated with a first access category, the first access category being the access category corresponding to the service that triggers the access control.

[0007] Thirdly, a terminal device is provided, comprising: a processing module, configured to trigger access control and execute the access control according to a first configuration; wherein the first configuration includes access control parameters of the terminal device, and the first configuration satisfies one or more of the following: the first configuration is used by the terminal device to determine whether to adjust the access control parameters; the first configuration is used by the terminal device to determine whether to allow access attempts; the first configuration belongs to one of multiple configurations associated with a first access category, and the first access category is the access category corresponding to the service that triggers the access control.

[0008] Fourthly, a network device is provided, comprising: a sending module, configured to send a first configuration to a terminal device, the first configuration being used by the terminal device to perform access control, the first configuration including access control parameters of the terminal device; wherein the first configuration satisfies one or more of the following: the first configuration is used by the terminal device to determine whether to adjust the access control parameters; the first configuration is used by the terminal device to determine whether to allow an access attempt; the first configuration belongs to one of multiple configurations associated with a first access category, the first access category being the access category corresponding to the service that triggers the access control.

[0009] Fifthly, a terminal device is provided, including a processor and a memory, the memory being used to store one or more computer programs, and the processor being used to invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the first aspect.

[0010] In a sixth aspect, a network device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of the second aspect.

[0011] Seventhly, embodiments of this application provide a communication system including the aforementioned terminal device and / or network device. In another possible design, the system may further include other devices that interact with the terminal device or network device as described in the embodiments of this application.

[0012] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a computer to perform some or all of the steps in the methods described above.

[0013] Ninthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0014] In a tenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0015] In this embodiment, the terminal device can perform access control according to a first configuration, wherein the first configuration satisfies one or more of the following: the first configuration is used by the terminal device to determine whether to adjust access control parameters; the first configuration is used by the terminal device to determine whether to allow access attempts; the first configuration belongs to one of multiple configurations associated with a first access category. The first configuration satisfying the above requirements helps to improve the flexibility of the access control parameters used by the terminal device when performing access control, thereby improving the access efficiency of the terminal device and optimizing user experience and network performance. Attached Figure Description

[0016] Figure 1 is a system architecture example diagram of a wireless communication system applicable to embodiments of this application.

[0017] Figure 2 is a flowchart illustrating the access control method provided in an embodiment of this application.

[0018] Figure 3 is a schematic diagram of the structure of the terminal device provided in the embodiment of this application.

[0019] Figure 4 is a schematic diagram of the network device provided in an embodiment of this application.

[0020] Figure 5 is a schematic structural diagram of the communication device provided in an embodiment of this application. Detailed Implementation

[0021] Communication system architecture

[0022] Figure 1 is a system architecture example diagram of a wireless communication system 100 to which embodiments of this application can be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographical area and may communicate with the terminal device 120 located within that coverage area.

[0023] Figure 1 illustrates an exemplary network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0024] Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.

[0025] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems, satellite communication systems, and so on.

[0026] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes, etc. Optionally, the UE can act as a base station. For example, the UE can act as a scheduling entity, providing sidelink signals between UEs in V2X or D2D, etc. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through a base station.

[0027] The network device in this application embodiment can be a device for communicating with a terminal device. This network device can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, auxiliary SeNB, multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0028] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0029] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0030] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0031] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0032] UAC

[0033] Before initiating a call, a terminal device must first perform access control. The parameters involved in access control include access identity and access category.

[0034] Access identifiers are used to characterize the identity of terminal devices. Currently, the access identifiers introduced in the NR system include 0-15, where access identifiers 3-10 are undefined (i.e., reserved values). Access identifier 0 is applicable to terminal devices that are not configured with any specific access identifier. Access identifier 1 is applicable to terminal devices configured with Multimedia Priority Service (MPS). Access identifier 2 is applicable to terminal devices configured with Mission Critical Services (MCS). Access identifiers 11-15 are typically used for specific services or user groups.

[0035] Access categories characterize the service attributes of a call initiated by a terminal device; different access categories identify different service attributes. For example, access category 0 represents a mobile-terminated access (MT-access) request initiated by a mobile terminal, generally used in the process of responding to a paging call initiated by the terminal device; access category 2 represents an emergency call access category, and so on. Currently, the NR system has introduced 64 access categories, of which access categories 0-7 are standardized access types, while access categories 32-63 are operator-defined access categories, and the others are undefined access categories.

[0036] Network devices can broadcast access control parameters associated with access identifiers and access categories so that terminal devices can perform access control based on these parameters. For example, network devices can broadcast these access control parameters in system information block 1 (SIB1).

[0037] In some embodiments, key access control parameters broadcast by the network device may include: uac-BarringFactor, uac-BarringTimer, and uac-BarringForAccessIdentity. The parameter uac-BarringFactor can be used to indicate the probability that an access attempt is allowed. The parameter BarringTimer can be used to determine the minimum time interval between a failed access attempt initiated by an access class and a subsequent access attempt initiated by the same access class. The parameter uac-BarringForAccessIdentity can be used to determine whether each access identifier is allowed to attempt an access attempt. The implementation of the parameter uac-BarringForAccessIdentity can be a bitmap, where each bit represents a different access identifier. A bit set to "1" indicates that the access attempt corresponding to that access identifier is allowed (i.e., enters the "green channel" mentioned later), and a bit set to "0" indicates that the access attempt corresponding to that access identifier is rejected (i.e., enters the "red channel" mentioned later).

[0038] Among the parameters mentioned above, those that have a mapping relationship with the access category include uac-BarringFactor and uac-BarringTimer.

[0039] From the perspective of the executor, access control can include two types. One type is access control executed by the terminal device itself, such as when the terminal device triggers and executes access control; this type of access control can be called or understood as User-Agent Control (UAC). As an example, in an NR system, access control triggered and executed by the terminal device is called UAC. The other type is access control executed by the network device. For example, the network device can execute access control based on the "RRC Establishment cause" in the radio resource control (RRC) establishment request message (such as the RRCSetupRequest message) sent by the terminal device.

[0040] For the access control mechanism executed by network devices, when a terminal device's non-access stratum (NAS) initiates a call, it obtains an "RRC establishment reason" based on the access identifier and access class mapping. The terminal device then encodes this "RRC establishment reason" into an RRC establishment request message at the RRC layer and sends this message to the network device. How the network device executes access control based on this "RRC establishment reason" is determined by its internal algorithm. In some embodiments, if the network device accepts the RRC establishment request message initiated by the terminal device, it responds by sending an RRC establishment message; otherwise, it rejects the call by sending an RRC rejection message.

[0041] For the access control (UAC) mechanism executed by the terminal device, the terminal device needs to obtain access control parameters before executing access control. As one implementation, before executing the UAC procedure in a certain cell, the terminal device needs to obtain the SIB1 of that cell in order to retrieve the access control parameters from SIB1. Afterwards, the terminal device can execute access control based on the obtained access control parameters.

[0042] The process of UAC execution at the access layer of a terminal device can be divided into three steps. These three steps are described below.

[0043] In step 1, the terminal device determines whether the access attempt can directly enter the "green channel" or the "red channel" based on the access category provided by the NAS layer. Entering the "green channel" means that the access attempt is directly allowed, while entering the "red channel" means that the access attempt is directly rejected (or barred).

[0044] As an example, Access Category 0 indicates a paging response initiated by the terminal device. This access category does not require the UAC process and will be reflected in the "RRC establishment reason". In other words, the call process corresponding to Access Category 0 is unconditionally accepted and directly enters the "green channel".

[0045] As another example, Access Category 2 represents emergency calls. The terminal device only needs to perform the UAC procedure for Access Category 2 when it is currently in a state where the network device is refusing to establish an RRC connection (i.e., when timer T302 is running); otherwise, it does not need to perform the UAC procedure (it directly enters the "green channel"). In other words, emergency calls require the UAC control process when the network is very busy.

[0046] As another example, if the terminal device determines that it corresponds to the current access category and the network device does not broadcast any access control parameters, the terminal device will assume that the access category does not require the execution of the UAC process (and directly enter the "green channel").

[0047] It should be noted that when timer T302 is running, access categories other than access category 0 and access category 2 will be rejected.

[0048] It should also be noted that if an access class fails during UAC execution, the terminal device will start a timer T390 for that access class. The duration of this timer is determined by the parameter uac-BarringTimer. In this case, if the same access class is attempted again while timer T390 is running, the terminal device will directly reject the access attempt.

[0049] Apart from the access categories that directly enter the "green channel" or "red channel" as mentioned above, other access categories require step 2.

[0050] In step 2, the terminal device verifies the access identifier. For example, the terminal device can determine whether to allow the access attempt based on the access identifier. Specifically, whether the access attempts corresponding to access identifiers 1, 2, and 11-15 are allowed can be determined using the parameter `uac-BarringForAccessIdentity`. However, whether the access attempt corresponding to access identifier 0 is allowed cannot be determined using the parameter `uac-BarringForAccessIdentity`. Therefore, in this case, the terminal device needs to proceed to step 3.

[0051] In step 3, the terminal device first determines the unique access control parameters "uac-BarringFactor" and "uac-BarringTimer" based on the access category. Then, the terminal device's access layer generates a random number between 0 and 1. If this generated random number is less than the corresponding uac-BarringFactor, it is considered that UAC control has been successful; otherwise, timer T390 is started, with a length of (0.7 + 0.6 * uac-BarringTimer).

[0052] Currently, when terminal devices perform User-Agent Control (UAC), the access efficiency is relatively low, impacting user experience and network performance. For example, access for certain high-priority services may be delayed compared to low-priority services, resulting in lower access efficiency for high-priority terminal devices and affecting user experience and network performance. Similarly, if a terminal device fails to successfully connect to the network device after multiple access attempts, its access efficiency will also be low, impacting user experience and network performance.

[0053] To address the aforementioned issues, the inventors discovered that the low access efficiency of terminal devices stems from two main reasons. Firstly, the current UAC configuration is based on access category granularity, which may not meet the access requirements of different services. For instance, when a terminal device enters the RRC inactive state, it suspends the PDU session's data plane resources at the access layer (e.g., data radio bearer (DRB)). In this scenario, if uplink data packets arrive from these PDU sessions, the terminal device executes UAC and assumes the service initiating the call is of the MO_data attribute (corresponding to access category 7). However, the arriving uplink data may belong to different radio bearers (different radio bearers reflect different QoS requirements, such as latency requirements). When executing UAC, the terminal device uniformly uses access category 7 as the access category for uplink data arrival scenarios, without considering the different attributes of uplink services and their corresponding QoS requirements. This coarse-grained / single-granularity UAC configuration cannot flexibly handle service differences or guarantee access immediacy, potentially leading to high-priority services being blocked by low-priority services, impacting user experience and network performance. One reason for the low access efficiency of terminal devices is that the current UAC configuration is mainly based on static parameter configuration (i.e., access control parameters statically configured in SIB1), lacking the ability to dynamically adjust. This prevents the system from optimizing in real time according to changes in current network conditions and service requirements. For example, if a terminal device fails to access the network after multiple attempts, it still needs to make another attempt based on the UAC configuration provided in SIB1, affecting the access efficiency of individual terminal devices.

[0054] Based on this, embodiments of this application provide a UAC enhancement scheme to optimize the current UAC configuration and improve the access efficiency of terminal devices. The method embodiments of this application will be described below.

[0055] Figure 2 is a flowchart illustrating the access control method provided in an embodiment of this application. The method shown in Figure 2 can be executed by a terminal device, such as the terminal device 120 shown in Figure 1. The method shown in Figure 2 may include step S210, which will be described below.

[0056] In step S210, the terminal device initiates access control and executes access control according to the first configuration.

[0057] In some embodiments, the process of a terminal device triggering access control and executing access control according to a first configuration can be referred to as or understood as the terminal device executing a UAC process. In this case, the first configuration can also be referred to as or understood as a UAC configuration. However, the embodiments of this application are not limited to this. For example, the process of a terminal device triggering access control and executing access control according to a first configuration may also include a process that is the same as or similar to UAC in future communication systems.

[0058] In some embodiments, the access control may be triggered by the access layer of the terminal device. That is, the terminal device triggering access control means that the access layer of the terminal device triggers access control. For example, the access layer of the terminal device may trigger access control upon request from a higher layer (such as the RRC layer).

[0059] In some embodiments, the terminal device may trigger access control for a first access category, or in other words, the terminal device may initiate a UAC procedure for a first access category. The first access category is the access category corresponding to the service that triggered the access control (or this access control procedure).

[0060] This application does not limit the method for determining the first access category. As one possible implementation, the first access category may be indicated by the NAS layer of the terminal device. As another possible implementation, the first access category may be determined by an upper layer (such as the RRC layer) of the terminal device.

[0061] This application does not limit the first access category in its embodiments. In some embodiments, the first access category may be access category 7, that is, the access category corresponding to MO_data. In some embodiments, the first access category may be another access category besides access category 7, such as access category 4, or an access category introduced by a future communication system.

[0062] In some embodiments, the first configuration described above may include access control parameters for the terminal device. In this way, the terminal device can perform access control according to the access control parameters in the first configuration. This application does not limit the access control parameters included in the first configuration; the access control parameters included in the first configuration will be described later in conjunction with Embodiment 1, and will not be detailed here.

[0063] This application does not limit the configuration granularity of the first configuration in its embodiments. In some embodiments, the first configuration is configured at the access category level, that is, each access category can be associated with one set of configurations. In some embodiments, the first configuration can be configured at a finer granularity than the access category, that is, one access category can be associated with multiple sets of finer-grained configurations, and the first configuration can be one of these multiple sets of configurations. The configuration granularity of the first configuration will be described in detail below with reference to Embodiment 1, and will not be elaborated here.

[0064] In some embodiments, the first configuration described above may be configured by the network device to the terminal device. For example, the network device may send the first configuration to the terminal device through one or more of the following: dedicated signaling; system broadcast message.

[0065] As one possible implementation, when the first configuration is configured at the access class level, the network device can send the first configuration to the terminal device through a system broadcast message (such as SIB).

[0066] As another possible implementation, when the first configuration is configured at a finer granularity than the access class, the network device can send the first configuration to the terminal device via proprietary signaling. For example, the network device can send the first configuration to the terminal device via one or more of the following proprietary signaling: RRC proprietary signaling, medium access control control element (MAC CE), and downlink control information (DCI). Taking the network device sending the first configuration via RRC proprietary signaling as an example, the RRC proprietary signaling can include one or more of the following: RRC release (e.g., RRC Release) message, RRC reconfiguration (e.g., RRC Reconfiguration) message, RRC recovery (e.g., RRC Resume) message, RRC establishment (e.g., RRC Establishment) message, etc.

[0067] As another possible implementation, if the first configuration is configured at a finer granularity than the access class, the network device can send the access class granularity configuration to the terminal device through system broadcast messages, and send multiple sets of finer granular configurations associated with the access class to the terminal device through dedicated signaling.

[0068] In some embodiments, the first configuration described above may be predefined or preconfigured. For example, the first configuration described above may be predefined by the protocol.

[0069] As one possible implementation, if the first configuration is configured at a finer granularity than the access category, the first configuration can be predefined or pre-configured.

[0070] As another possible implementation, if the first configuration is configured at a finer granularity than the access class, the access class granularity configuration can be configured by the network device to the terminal device through a system broadcast message, while the finer granularity configuration can be predefined or pre-configured.

[0071] In some embodiments, the terminal device needs to determine the first configuration before performing access control according to the first configuration. For example, if a first access category is associated with one set of configurations, the terminal device needs to determine the first configuration corresponding to the first access category. Or, if a first access category is associated with multiple sets of configurations, the terminal device needs to determine the first configuration from among the multiple sets of configurations.

[0072] This application does not limit the implementation method of the terminal device determining the first configuration. For example, the terminal device determining the first configuration may be associated with one or more of the following: whether the service that triggered access control has an established radio bearer (RB), and the access category corresponding to the service that triggered access control.

[0073] As one possible implementation, the terminal device (such as the access layer of the terminal device) can determine the first configuration based on whether an established Resource Block (RB) exists for the service that triggered access control. For example, if no established RB exists for the service that triggered access control, the terminal device can determine an access category-level configuration as the first configuration. Alternatively, if an established RB exists for the service that triggered access control, the terminal device can determine a finer-grained configuration as the first configuration based on that established RB.

[0074] As another possible implementation, the terminal device (such as the access layer of the terminal device) can determine the first configuration based on the first access category. For example, if the first access category is a specific access category, the terminal device can determine a finer-grained configuration as the first configuration; otherwise, the terminal device can determine an access category-level configuration as the first configuration.

[0075] In some embodiments, the specific access category mentioned above refers to the existence of an established Resource Block (RB) for the service corresponding to that access category. That is, the terminal device determining the first configuration based on the first access category can mean that if an established RB exists for the service corresponding to the first access category, the terminal device can determine a more granular configuration as the first configuration; otherwise, the terminal device can determine a configuration at the access category granularity level as the first configuration.

[0076] This application does not limit the specific access category. In some embodiments, the specific access category may refer to access category 7 (e.g., MO_data). In some embodiments, the specific access category may refer to an access category in a future communication system, and the service corresponding to that access category has an established RB.

[0077] In some embodiments, the first configuration described above can be used to enhance access control (such as UAC). The enhancement schemes for access control in this application are described below with reference to Embodiment 1 and Embodiment 2, respectively. Embodiment 1 aims to refine the granularity of the first configuration, while Embodiment 2 aims to improve the terminal device's ability to dynamically adjust access control based on the first configuration.

[0078] It should be noted that Examples 1 and 2 described below can be used individually or in combination.

[0079] For example, the terminal device can determine the first configuration from the multiple configurations provided in Embodiment 1 (such as the multiple configurations associated with the first access category) and perform access control based on the first configuration.

[0080] For example, the terminal device can use the first configuration provided by the current communication system (such as the NR system) and dynamically adjust the access control based on Embodiment 2.

[0081] For example, the terminal device can determine the first configuration from the multiple configurations provided in Embodiment 1 (such as the multiple configurations associated with the first access category), and then the terminal device can further dynamically adjust the access control based on Embodiment 2.

[0082] Example 1:

[0083] In Embodiment 1, an access category (such as a first access category) can be associated with multiple configurations. For example, an access category can be associated with multiple UAC configurations. In some embodiments, an access category can be associated with multiple more granular configurations. In this way, the terminal device can perform access control through more granular configurations.

[0084] In Example 1, the first configuration is one of multiple configurations associated with the first access category.

[0085] In some embodiments, the configuration granularity of the first configuration is associated with the service type of the service that triggers access control.

[0086] In some embodiments, the first configuration may be based on one or more of the following configuration granularities: QoS flow, RB, logical channel (LCH), logical channel group (LCG), first identifier, and access class.

[0087] In some embodiments, the first identifier described above can be used to identify the service type that triggers access control. For example, the first identifier can be used to identify the service type that triggers access control as an emergency call type. As another example, the first identifier can be used to identify the service type that triggers access control as an MCS type. As yet another example, the first identifier can be used to identify the service type that triggers access control as an MPS type, etc.

[0088] In some embodiments, the first identifier may be sent by the NAS layer or an upper layer (such as the RRC layer) of the terminal device to the access layer of the terminal device.

[0089] As an example, the first configuration can be configured at the granularity of QoS flow / RB / LCH / LCG / first identifier.

[0090] As another example, the first configuration can be configured at the access category granularity. That is, the first configuration can be configured according to the configuration granularity in the current NR system.

[0091] As another example, the first configuration can be configured for both access category and QoS granularity. That is, an access category can be associated with multiple configurations, which are configured at the QoS flow level.

[0092] As another example, the first configuration can be configured at the access category and RB granularity. That is, an access category can be associated with multiple sets of configurations, which are configured at the RB granularity.

[0093] As another example, the first configuration can be configured at the access category and LCH granularity. That is, an access category can be associated with multiple sets of configurations, which are configured at the LCH granularity.

[0094] As another example, the first configuration can be configured at the access category and LCG granularity. That is, an access category can be associated with multiple sets of configurations, which are configured at the LCG granularity.

[0095] As another example, the first configuration can be configured at the granularity of the access category and the first identifier. That is, an access category can be associated with multiple sets of configurations, which are configured at the granularity of the first identifier.

[0096] In some embodiments, when multiple configurations are associated with an access category (such as a first access category), the terminal device can determine the first configuration from among the multiple configurations based on the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs. As one possible implementation, there is a mapping relationship (or association, correspondence, etc.) between the multiple configurations and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs. The first configuration is determined based on this mapping relationship and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs. For example, an access category can be associated with multiple configurations, each configuration can be associated with an identifier (ID), and correspondingly, the QoS flow / RB / LCH / LCG / first identifier can also be associated with an ID, and there is a mapping relationship between these two IDs. In this way, the terminal device can select the configuration with a matching ID from the multiple configurations associated with the first access category as the first configuration based on the ID associated with the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs.

[0097] This application does not limit the mapping relationship between the ID associated with each configuration set and the ID associated with the QoS flow (or RB / LCH / LCG / first identifier). As one possible implementation, the ID associated with each configuration set and the ID associated with the QoS flow (or RB / LCH / LCG / first identifier) ​​can be the same. As another possible implementation, the ID associated with each configuration set can be calculated from the ID associated with the QoS flow (or RB / LCH / LCG / first identifier), etc.

[0098] In some embodiments, the first configuration may include access control parameters for the terminal device. Alternatively, the first configuration may include one or more access control parameters that can be used by the terminal device to perform access control. The access control parameters included in the first configuration are described below for different configuration granularities.

[0099] In some embodiments, the access control parameters included in the first configuration at the access category configuration granularity may include one or more of the following: first information, fourth parameter, fifth parameter, sixth parameter, and seventh parameter.

[0100] As an example, at the configuration granularity for access categories, the first configuration may include first information.

[0101] As another example, the first configuration may include a fourth parameter at the configuration granularity for access categories.

[0102] As yet another example, at the configuration granularity for access categories, the first configuration may include first information and a fourth parameter.

[0103] As yet another example, the configuration granularity for access categories can include first information, fifth parameter, and sixth parameter.

[0104] As yet another example, the configuration granularity for access categories can include the fourth, fifth, and sixth parameters.

[0105] As yet another example, the configuration granularity for access categories can include first information, fourth parameter, fifth parameter, and sixth parameter.

[0106] As yet another example, the configuration granularity for access categories can include first information, fourth parameter, fifth parameter, sixth parameter, and seventh parameter.

[0107] It should be noted that the above examples are for illustrative purposes only, and other combinations will not be listed for the sake of brevity.

[0108] In some embodiments, the first configuration for the configuration granularity of QoS flow / RB / LCH / LCG / first identifier may include first information and / or a fourth parameter. However, the embodiments of this application are not limited to this. For example, for the configuration granularity of QoS flow / RB / LCH / LCG / first identifier, the first configuration may include other parameters such as a fifth parameter and a sixth parameter in addition to the first information and / or the fourth parameter.

[0109] The first information, the fourth parameter, the fifth parameter, the sixth parameter, and the seventh parameter are described below.

[0110] In some embodiments, the first information can be used by the terminal device to determine whether to perform access control enhancement. For example, the first information can be used by the terminal device to determine whether to adjust access control parameters and / or to determine whether to allow an access attempt.

[0111] The embodiments of this application do not limit the first information. Exemplarily, the first information may include one or more of the following: a first parameter, a second parameter, and a third parameter.

[0112] As an example, the first information may include the first parameter.

[0113] As another example, the first information may include the second parameter.

[0114] As yet another example, the first piece of information may include a third parameter.

[0115] As yet another example, the first information may include a first parameter and a second parameter.

[0116] As yet another example, the first information may include a first parameter and a third parameter.

[0117] As yet another example, the first piece of information may include the second and third parameters.

[0118] As yet another example, the first information may include a first parameter, a second parameter, and a third parameter.

[0119] In some embodiments, the first parameter can be used by the terminal device to determine whether access control enhancement is supported. For example, the first parameter can be used to determine whether adjusting access control parameters is supported and / or whether allowing access attempts is supported.

[0120] As an example, the first parameter can be used to determine whether adjusting access control parameters is supported. One possible implementation is that the first parameter can have a first value and a second value. When the first parameter is the first value, the terminal device determines that adjusting access control parameters is supported; when the first parameter is the second value, the terminal device determines that adjusting access control parameters is not supported.

[0121] As another example, the first parameter can be used to determine whether to allow the access attempt. As one possible implementation, the first parameter can have a first value and a second value. When the first parameter has the first value, the terminal device determines that it supports allowing the access attempt; when the first parameter has the second value, the terminal device determines that it does not support allowing the access attempt.

[0122] As another example, the first parameter can be used to determine whether adjusting access control parameters is supported and whether allowing access attempts is supported. As one possible implementation, when the first parameter takes a first value, the terminal device determines that adjusting access control parameters is supported and allowing access attempts is supported; when the first parameter takes a second value, the terminal device determines that adjusting access control parameters is supported but allowing access attempts is not supported; when the first parameter takes a third value, the terminal device determines that adjusting access control parameters is not supported but allowing access attempts is supported; and when the first parameter takes a fourth value, the terminal device determines that adjusting access control parameters is not supported and allowing access attempts is not supported.

[0123] In some embodiments, the first parameter may include one or more indications that indicate whether access control enhancements are supported (e.g., whether adjusting access control parameters is supported and / or whether allowing access attempts is supported). For example, the first parameter may include first indications, which may use 1 bit or 2 bits to indicate whether access control enhancements are supported. As another example, the first parameter may include second and third indications, where the second indications may use 1 bit to indicate whether access control enhancements are supported, and the third indications may use one or more bits to indicate the type of support; that is, the third indications may indicate support for adjusting access control parameters, support for allowing access attempts, or support for both adjusting access control parameters and allowing access attempts.

[0124] In some embodiments, the third indication information indicating that the terminal device supports allowing the access attempt may include: the third indication information indicating that the terminal device supports directly allowing the access attempt.

[0125] In some embodiments, the third indication information indicating that the terminal device allows access attempts may include: the third indication information indicating that the terminal device supports allowing access attempts based on the number of access attempts.

[0126] In some embodiments, the second parameter can be used to determine the adjusted access control parameters. For example, the second parameter can be used to scale the access control parameters included in the first configuration.

[0127] In some embodiments, the second parameter may include one or more parameters. As an example, the second parameter may include a parameter that can be used to determine the scaling factor. As one possible implementation, this parameter may be used to indicate the scaling factor. As another possible implementation, this parameter may be used to indicate a scaling order, which can be used to determine the scaling factor. As yet another example, the second parameter may include multiple parameters, which may each be used to indicate the scaling factor and the scaling order corresponding to that scaling factor.

[0128] In some embodiments, the third parameter may be used to indicate a threshold number of attempts by the terminal device to perform an access attempt.

[0129] In some embodiments, the terminal device may determine whether to allow the current access attempt based on a third parameter. For example, when the number of access attempts performed by the terminal device is greater than or equal to the attempt count threshold, the terminal device may determine that the current access attempt is allowed. Conversely, when the number of access attempts performed by the terminal device is less than the attempt count threshold, the terminal device may determine that the current access attempt is not allowed.

[0130] In some embodiments, the fourth parameter can be used to indicate the identifier of the first configuration. For example, the fourth parameter can be used to indicate the identifier associated with each of the multiple configurations associated with the first access category. In this way, the terminal device can determine the first configuration based on the ID associated with the QoS flow / RB / LCH / LCG / first identifier of the service that triggered access control and the identifier associated with each configuration.

[0131] In some embodiments, the fifth parameter may be used to indicate the probability that an access attempt is allowed to pass. For example, the fifth parameter may include the parameter uac-BarringFactor or a parameter in a future communication system that functions the same or similarly to the parameter uac-BarringFactor.

[0132] In some embodiments, the sixth parameter can be used to determine the minimum time interval between a failed access attempt initiated by an access class and a subsequent access attempt initiated by the same access class. For example, the sixth parameter may include the parameter BarringTimer or a parameter in a future communication system that has the same or similar function as the parameter BarringTimer.

[0133] In some embodiments, the seventh parameter can be used to determine whether each access identifier is allowed to attempt access. For example, the seventh parameter may include the parameter uac-BarringForAccessIdentity or a parameter in a future communication system that functions the same or similarly to the parameter uac-BarringForAccessIdentity.

[0134] Example 2:

[0135] In Embodiment 2, the terminal device can dynamically adjust access control based on the first configuration. Taking the first configuration as an access category granularity configuration as an example, the terminal device can dynamically adjust access control based on the access category granularity configuration. Taking the first configuration as a QoS flow / RB / LCH / LCG / first identifier granularity configuration as an example, the terminal device can dynamically adjust access control based on the QoS flow / RB / LCH / LCG / first identifier granularity configuration.

[0136] In Embodiment 2, the first configuration may satisfy one or more of the following: the first configuration is used by the terminal device to determine whether to adjust the access control parameters; the first configuration is used by the terminal device to determine whether to allow the access attempt; and the first configuration belongs to one of multiple configurations associated with the first access category.

[0137] As an example, the first configuration can be used by the terminal device to determine whether to adjust the access control parameters.

[0138] As another example, the first configuration can be used by the terminal device to determine whether to allow the access attempt.

[0139] As yet another example, the first configuration is one of multiple configurations associated with the first access category.

[0140] As yet another example, the first configuration can be used by the terminal device to determine whether to adjust the access control parameters, and by the terminal device to determine whether to allow the access attempt.

[0141] As yet another example, the first configuration can be used by the terminal device to determine whether to adjust the access control parameters, and the first configuration belongs to one of multiple configurations associated with the first access category.

[0142] As yet another example, the first configuration can be used by the terminal device to determine whether to allow the access attempt, and the first configuration belongs to one of multiple configurations associated with the first access category.

[0143] As yet another example, the first configuration can be used by the terminal device to determine whether to adjust access control parameters and whether to allow access attempts, and the first configuration belongs to one of multiple configurations associated with the first access category.

[0144] In some embodiments, the first configuration used by the terminal device to determine whether to adjust the access control parameters can be understood as the first configuration used by the terminal device to determine whether to adjust the access control parameters configured in the first configuration. For example, the first configuration can be used by the terminal device to determine whether to scale the access control parameters configured in the first configuration.

[0145] In some embodiments, the first configuration for the terminal device to determine whether to allow the access attempt can also be replaced by: the first configuration for the terminal device to determine whether to reject the access attempt or whether the access attempt is blocked.

[0146] In some embodiments, the terminal device determining that the access attempt is allowed can be understood as the terminal device determining that the access attempt is successful, i.e., entering the "green channel" mentioned above.

[0147] In some embodiments, the terminal device determining that the access attempt is allowed can be understood as the terminal device determining that the access attempt is successful, that is, the terminal device can bypass the access control.

[0148] In some embodiments, allowing access attempts can include different types. For example, if the terminal device supports allowing access attempts, the terminal device can directly allow the current access attempt (i.e., directly bypass access control). As another example, if the terminal device supports allowing access attempts, the terminal device can determine whether to allow the access attempt based on the number of attempts.

[0149] In other words, in some embodiments, the first configuration for the terminal device to determine whether to allow the access attempt may include: if the first configuration indicates that the access attempt is allowed, the terminal device may directly allow the access attempt; otherwise, the current access attempt is not allowed. In some embodiments, the first configuration for the terminal device to determine whether to allow the access attempt may include: the first configuration may be used by the terminal device to determine whether to allow the access attempt based on the number of access attempts. For example, if the first configuration indicates that allowing the access attempt is supported, and the terminal device determines that the number of access attempts is greater than or equal to a threshold number of attempts, then the terminal device determines that the current access attempt is allowed; otherwise, if the first configuration indicates that allowing the access attempt is supported, and the terminal device determines that the number of access attempts is less than the threshold number of attempts, then the terminal device determines that the current access attempt is not allowed.

[0150] In some embodiments, the terminal device dynamically adjusting access control based on the first configuration can be understood as the terminal device dynamically adjusting the access control parameters in the first configuration to perform access control based on the adjusted access control parameters, and / or the terminal device dynamically adjusting whether to allow the current access attempt based on the first configuration. This will be described in detail below.

[0151] In some embodiments, the terminal device performing access control according to the first configuration may include one or more of the following: the terminal device adjusts access control parameters according to the first configuration and performs access control based on the adjusted access control parameters; the terminal device determines whether to allow access attempts according to the first configuration.

[0152] As an example, the terminal device can adjust the access control parameters according to the first configuration and perform access control based on the adjusted access control parameters.

[0153] As another example, the terminal device can determine whether to allow the access attempt based on the first configuration.

[0154] As another example, the terminal device can adjust the access control parameters according to the first configuration, perform access control based on the adjusted access control parameters, and determine whether to allow the access attempt according to the first configuration.

[0155] In some embodiments, the first configuration may explicitly indicate whether adjusting access control parameters is supported. For example, a first parameter in the first configuration may be used to explicitly indicate whether adjusting access control parameters is supported.

[0156] In some embodiments, the first configuration may implicitly indicate whether adjusting access control parameters is supported. For example, a second parameter in the first configuration may be used to implicitly indicate whether adjusting access control parameters is supported.

[0157] In some embodiments, the terminal device adjusting access control parameters according to a first configuration and performing access control based on the adjusted access control parameters may include: if the first configuration includes a first parameter, the terminal device determines that it can (or supports) adjusting the access control parameters; otherwise, if the first configuration does not include the first parameter, the terminal device determines that it cannot (or does not support) adjusting the access control parameters.

[0158] In some embodiments, the terminal device adjusting access control parameters according to a first configuration and performing access control based on the adjusted access control parameters may include: if the first configuration includes a first parameter and the value of the first parameter is a first value, the terminal device determines that it can (or supports) adjusting the access control parameters; otherwise, if the first configuration does not include the first parameter, or if the first configuration includes the first parameter but the value of the first parameter is not the first value, the terminal device determines that it cannot (or does not support) adjusting the access control parameters.

[0159] In some embodiments, the terminal device adjusting access control parameters according to a first configuration and performing access control based on the adjusted access control parameters may include: if the first configuration includes a second parameter, the terminal device determines that it can (or supports) adjusting the access control parameters; otherwise, if the first configuration does not include a second parameter, the terminal device determines that it cannot (or does not support) adjusting the access control parameters.

[0160] In some embodiments, the terminal device adjusting access control parameters according to a first configuration and performing access control based on the adjusted access control parameters may include: if the first access category supports adjusting access control parameters, the terminal device determines that the access control parameters can be adjusted; otherwise, if the first access category does not support adjusting access control parameters, the terminal device determines that the access control parameters cannot be adjusted.

[0161] In some embodiments, the terminal device adjusting access control parameters according to the first configuration and performing access control based on the adjusted access control parameters may include: if the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports adjusting access control parameters, then the terminal device determines that the access control parameters can be adjusted; otherwise, if the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs does not support adjusting access control parameters, then the terminal device determines that the access control parameters cannot be adjusted.

[0162] In some embodiments, whether the first access category supports adjusting access control parameters is determined by a first configuration.

[0163] In some embodiments, the first configuration may explicitly indicate whether the first access category supports adjusting access control parameters. As one possible implementation, if the first configuration includes a first parameter, the first access category supports adjusting access control parameters; otherwise, if the first configuration does not include the first parameter, the first access category does not support adjusting access control parameters. As another possible implementation, if the first configuration includes a first parameter and the first parameter takes the value of a first value, the first access category supports adjusting access control parameters; otherwise, if the first configuration does not include the first parameter, or if the first configuration includes the first parameter but the value of the first parameter is not the first value, the first access category does not support adjusting access control parameters.

[0164] In some embodiments, the first configuration may implicitly indicate whether the first access class supports adjusting access control parameters. As one possible implementation, if the first configuration includes a second parameter, the first access class supports adjusting access control parameters; otherwise, if the first configuration does not include a second parameter, the first access class does not support adjusting access control parameters.

[0165] In some embodiments, whether the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports adjusting access control parameters is determined by a first configuration.

[0166] In some embodiments, the first configuration may explicitly indicate whether the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports adjusting access control parameters. As one possible implementation, if the first configuration includes a first parameter, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports adjusting access control parameters; otherwise, if the first configuration does not include the first parameter, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs does not support adjusting access control parameters. As another possible implementation, if the first configuration includes a first parameter and the value of the first parameter is a first value, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports adjusting access control parameters; otherwise, if the first configuration does not include the first parameter, or if the first parameter includes the first parameter but the value of the first parameter is not the first value, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs does not support adjusting access control parameters.

[0167] In some embodiments, the first configuration may implicitly indicate whether the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports adjusting access control parameters. As a possible implementation, if the first configuration includes a second parameter, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports adjusting access control parameters; otherwise, if the first configuration does not include a second parameter, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs does not support adjusting access control parameters.

[0168] This application does not limit the implementation method of how the terminal device adjusts the access control parameters. In some embodiments, the terminal device may determine the adjusted access control parameters based on one or more of the following: a second parameter indicated by a first configuration, and the number of access attempts performed by the terminal device.

[0169] As one possible implementation, the terminal device can determine a first scaling factor for adjusting the access control parameters based on a second parameter indicated by a first configuration, and determine the adjusted access control parameters based on the first scaling factor. For example, the terminal device can determine the first scaling factor based on the scaling factor indicated by the first configuration, and determine the adjusted access control parameters based on the first scaling factor. As another example, the terminal device can determine the first scaling factor based on the ramp order indicated by the first configuration, and determine the adjusted access control parameters based on the first scaling factor. As an example, the first scaling factor can be equal to the scaling factor indicated in the first configuration * a first ratio. For example, the value of the first ratio may differ for terminal devices with different capabilities.

[0170] As another possible implementation, the terminal device can determine a first scaling factor based on the number of access attempts it makes, and then determine the adjusted access control parameters based on the first scaling factor. In other words, the first scaling factor can be determined based on the number of access attempts the terminal device makes.

[0171] In some embodiments, the more access attempts the terminal device makes, the smaller the first scaling factor becomes. For example, the first scaling factor = 1 / number of attempts. As an example, the terminal device needs to adjust a sixth parameter, the first scaling factor corresponding to which can decrease as the number of access attempts made by the terminal device increases.

[0172] In some embodiments, the more access attempts the terminal device makes, the larger the first scaling factor becomes. For example, the first scaling factor = number of attempts * second ratio. As an example, the terminal device may need to adjust a fifth parameter, and the first scaling factor corresponding to the fifth parameter can increase as the number of access attempts made by the terminal device increases.

[0173] In some embodiments, the value of the second ratio can be a fixed value. In some embodiments, the value of the second ratio may be related to the capabilities of the terminal device, that is, the value of the second ratio may be different for terminal devices with different capabilities.

[0174] As another possible implementation, the terminal device can determine a first scaling factor based on the second parameter of the first configuration indication and the number of access attempts performed by the terminal device, and determine the adjusted access control parameters based on the first scaling factor. That is, the first scaling factor can be determined based on the second parameter and the number of access attempts performed by the terminal device. As an example, the terminal device can determine the first scaling factor based on the ramp order of the first configuration indication and the number of access attempts performed by the terminal device.

[0175] In some embodiments, the more attempts the terminal device makes, the larger the first scaling factor becomes. For example, the first scaling factor = number of attempts * number of ramps. As an example, the terminal device may need to adjust the fifth parameter, and the first scaling factor corresponding to the fifth parameter can increase as the number of access attempts made by the terminal device increases.

[0176] In some embodiments, if an access attempt corresponding to the first access class is blocked and / or an RRC rejection message is received, the number of attempts for the access attempt corresponding to the first access class is incremented by 1.

[0177] In some embodiments, if an access attempt corresponding to the first access class is allowed, the number of attempts for the access attempt corresponding to the first access class can be reset to an initial value (e.g., 0).

[0178] This application does not limit the implementation method of the terminal device determining the adjusted access control parameters based on the first scaling factor. As one possible implementation, the adjusted access control parameters are equal to the product (or quotient) of the access control parameters indicated by the first configuration and the first scaling factor. As another possible implementation, the adjusted access control parameters are equal to the sum (or difference) of the access control parameters indicated by the first configuration and the first scaling factor.

[0179] This application does not limit the access control parameters that need to be adjusted. For example, the access control parameters that need to be adjusted may include one or more of the following: the fifth parameter, the sixth parameter, and a random number generated by the terminal device when performing an access attempt.

[0180] As an example, the access control parameters that need to be adjusted may include the fifth parameter.

[0181] As another example, the access control parameters that need to be adjusted may include the sixth parameter.

[0182] As yet another example, the access control parameters that need to be adjusted may include random numbers generated when the terminal device performs an access attempt.

[0183] As yet another example, the access control parameters that need to be adjusted may include the fifth and sixth parameters.

[0184] As yet another example, the access control parameters that need to be adjusted may include the sixth parameter and the random number generated when the terminal device performs an access attempt.

[0185] For details regarding the first, second, fifth, and sixth parameters, please refer to Example 1. For the sake of brevity, these details will not be repeated here.

[0186] In some embodiments, the first configuration may explicitly indicate whether access control is supported. For example, a first parameter in the first configuration may be used to explicitly indicate whether access control is supported.

[0187] In some embodiments, the first configuration may implicitly indicate whether access control is supported. For example, a third parameter in the first configuration may be used to implicitly indicate whether access control is supported.

[0188] In some embodiments, the terminal device determining whether to allow an access attempt based on a first configuration may include: if the first configuration includes a first parameter, the terminal device determines that it supports allow access control; otherwise, if the first configuration does not include the first parameter, the terminal device determines that it does not support allow access control.

[0189] In some embodiments, the terminal device determining whether to allow an access attempt based on the first configuration may include: if the first configuration includes a first parameter and the value of the first parameter is a first value, the terminal device determines that it supports allow access control; otherwise, if the first configuration does not include the first parameter, or if the first configuration includes the first parameter but the value of the first parameter is not the first value, the terminal device determines that it does not support allow access control.

[0190] In some embodiments, the terminal device determining whether to allow an access attempt based on a first configuration may include: if the first configuration includes a third parameter, the terminal device determines that it supports allow access control; otherwise, if the first configuration does not include a third parameter, the terminal device determines that it does not support allow access control.

[0191] In some embodiments, the terminal device determining whether to allow an access attempt based on a first configuration may include: if the first access category supports allow access control, the terminal device determines that allow access control is supported; otherwise, if the first access category does not support allow access control, the terminal device determines that allow access control is not supported.

[0192] In some embodiments, the terminal device determining whether to allow an access attempt based on a first configuration may include: if the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports allowing access control, then the terminal device determines that allowing access control is supported; otherwise, if the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs does not support allowing access control, then the terminal device determines that allowing access control is not supported.

[0193] In some embodiments, whether the first access category supports access control is determined by a first configuration.

[0194] In some embodiments, the first configuration may explicitly indicate whether the first access class supports access control. As one possible implementation, if the first configuration includes a first parameter, the first access class supports access control; if the first configuration does not include the first parameter, the first access class does not support access control. As another possible implementation, if the first configuration includes a first parameter and the value of the first parameter is a first value, the first access class supports access control; if the first configuration does not include the first parameter, or if the first configuration includes a first parameter but the value of the first parameter is not the first value, the first access class does not support access control.

[0195] In some embodiments, the first configuration may implicitly indicate whether the first access class supports allowed access control. As one possible implementation, if the first configuration includes a third parameter, the first access class supports allowed access control; if the first configuration does not include a third parameter, the first access class does not support allowed access control.

[0196] In some embodiments, whether the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports allowing access control is determined by a first configuration.

[0197] In some embodiments, the first configuration may explicitly indicate whether the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports allowing access control. As one possible implementation, if the first configuration includes a first parameter, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports allowing access control; if the first configuration does not include the first parameter, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs does not support allowing access control. As another possible implementation, if the first configuration includes a first parameter and the value of the first parameter is a first value, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports allowing access control; if the first configuration does not include the first parameter, or if the first configuration includes the first parameter but the value of the first parameter is not the first value, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs does not support allowing access control.

[0198] In some embodiments, the first configuration may implicitly indicate whether the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports allowing access control. As a possible implementation, if the first configuration includes a third parameter, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs supports allowing access control; if the first configuration does not include a third parameter, then the QoS flow / RB / LCH / LCG / first identifier to which the service triggering access control belongs does not support allowing access control.

[0199] For details regarding the first and third parameters, please refer to Example 1. For the sake of brevity, these details will not be repeated here.

[0200] The method embodiments of this application have been described in detail above with reference to Figures 1 and 2. The apparatus embodiments of this application will be described in detail below with reference to Figures 3 to 5. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0201] Figure 3 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The terminal device 300 shown in Figure 3 may include a processing module 310. The processing module 310 can be used to trigger access control and execute the access control according to a first configuration. The first configuration includes access control parameters of the terminal device, and the first configuration satisfies one or more of the following: the first configuration is used by the terminal device to determine whether to adjust the access control parameters; the first configuration is used by the terminal device to determine whether to allow an access attempt; the first configuration belongs to one of multiple configurations associated with a first access category, where the first access category is the access category corresponding to the service that triggered the access control.

[0202] In some embodiments, the first configuration is based on one or more of the following configuration granularities: QoS flow; RB; LCH; LCG; first identifier, which is used to identify the service type that triggers the access control; access category.

[0203] In some embodiments, the first identifier is sent from the non-access layer of the terminal device to the access layer of the terminal device.

[0204] In some embodiments, the first configuration includes first information, which is used by the terminal device to determine whether to adjust the access control parameters and / or by the terminal device to determine whether to allow the access attempt.

[0205] In some embodiments, the first information includes one or more of the following: a first parameter for determining whether adjusting the access control parameters is supported and / or whether allowing access attempts is supported; a second parameter for determining the adjusted access control parameters; and a third parameter for indicating a threshold number of access attempts that the terminal device can perform.

[0206] In some embodiments, the first configuration further includes a fourth parameter for indicating an identifier of the first configuration.

[0207] In some embodiments, the first configuration is configured via one or more of the following: dedicated signaling; system broadcast messages.

[0208] In some embodiments, the terminal device performing access control according to the first configuration includes one or more of the following: the terminal device adjusts the access control parameters according to the first configuration and performs access control based on the adjusted access control parameters; the terminal device determines whether to allow the access attempt according to the first configuration.

[0209] In some embodiments, the terminal device adjusts the access control parameters according to the first configuration, including: if the first configuration includes a first parameter, or if the first configuration includes a first parameter and the value of the first parameter is a first value, the terminal device determines that it supports adjusting the access control parameters; and / or if the first configuration includes a second parameter, the terminal device determines that it only supports adjusting the access control parameters; wherein the first parameter is used to determine whether it supports adjusting the access control parameters and / or whether it supports allowing access attempts, and the second parameter is used to determine the adjusted access control parameters.

[0210] In some embodiments, the adjusted access control parameters are determined based on one or more of the following: a second parameter indicated by the first configuration; the number of access attempts performed by the terminal device.

[0211] In some embodiments, the terminal device determines whether to allow the access attempt based on the first configuration by including one or more of the following: if the first configuration includes a first parameter, or if the first configuration includes a first parameter and the value of the first parameter is a first value, the terminal device determines that it supports allowing the access attempt; if the first configuration includes a third parameter, the terminal device determines that it supports allowing the access attempt; wherein the first parameter is used to determine whether it supports adjusting the access control parameter and / or whether it supports allowing the access attempt, and the third parameter is used to indicate a threshold number of attempts for the terminal device to perform the access attempt.

[0212] In some embodiments, the first configuration for the terminal device to determine whether to allow an access attempt includes: the first configuration for the terminal device to determine whether to allow the access attempt based on the number of attempts of the access attempt.

[0213] In some embodiments, there is a mapping relationship between the multiple configurations and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs, and the first configuration is determined based on the mapping relationship and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs.

[0214] In some embodiments, the processing module 310 may be a processor 510. The terminal device 300 may also include a transceiver 530 and a memory 520, as shown in FIG5.

[0215] Figure 4 is a schematic diagram of the network device provided in an embodiment of this application. The network device 400 shown in Figure 4 may include a sending module 410. The sending module 410 can be used to send a first configuration to a terminal device. The first configuration is used by the terminal device to perform access control, and the first configuration includes the access control parameters of the terminal device. The first configuration satisfies one or more of the following: the first configuration is used by the terminal device to determine whether to adjust the access control parameters; the first configuration is used by the terminal device to determine whether to allow an access attempt; the first configuration belongs to one of multiple configurations associated with a first access category, where the first access category is the access category corresponding to the service that triggers the access control.

[0216] In some embodiments, the first configuration is based on one or more of the following configuration granularities: QoS flow; RB; LCH; LCG; first identifier, which is used to identify the service type that triggers the access control; access category.

[0217] In some embodiments, the first identifier is sent from the non-access layer of the terminal device to the access layer of the terminal device.

[0218] In some embodiments, the first configuration includes first information, which is used by the terminal device to determine whether to adjust the access control parameters and / or by the terminal device to determine whether to allow the access attempt.

[0219] In some embodiments, the first information includes one or more of the following: a first parameter for determining whether adjusting the access control parameters is supported and / or whether allowing access attempts is supported; a second parameter for determining the adjusted access control parameters; and a third parameter for indicating a threshold number of access attempts that the terminal device can perform.

[0220] In some embodiments, the first configuration further includes a fourth parameter for indicating an identifier of the first configuration.

[0221] In some embodiments, the first configuration is configured via one or more of the following: dedicated signaling; system broadcast messages.

[0222] In some embodiments, the adjusted access control parameters are determined based on one or more of the following: a second parameter indicated by the first configuration; the number of access attempts performed by the terminal device.

[0223] In some embodiments, the first configuration for the terminal device to determine whether to allow an access attempt includes: the first configuration for the terminal device to determine whether to allow the access attempt based on the number of attempts of the access attempt.

[0224] In some embodiments, there is a mapping relationship between the multiple configurations and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs, and the first configuration is determined based on the mapping relationship and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs.

[0225] In some embodiments, the transmitting module 410 may be a transceiver 510. The network device 400 may also include a processor 510 and a memory 520, as shown in FIG5.

[0226] Figure 5 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 5 indicate that the unit or module is optional. This device 500 can be used to implement the methods described in the above method embodiments. Device 500 can be a chip, a terminal device, or a network device.

[0227] The apparatus 500 may include one or more processors 510. The processor 510 may support the apparatus 500 in implementing the methods described in the preceding method embodiments. The processor 510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0228] The apparatus 500 may also include one or more memories 520. The memories 520 store a program that can be executed by the processor 510, causing the processor 510 to perform the methods described in the preceding method embodiments. The memories 520 may be independent of the processor 510 or integrated within the processor 510.

[0229] The device 500 may also include a transceiver 530. The processor 510 can communicate with other devices or chips via the transceiver 530. For example, the processor 510 can send and receive data with other devices or chips via the transceiver 530.

[0230] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal device or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0231] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal device or network device provided in the embodiments of this application, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0232] This application also provides a computer program. This computer program can be applied to the terminal device or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of this application.

[0233] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0234] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0235] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0236] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0237] In the embodiments of this application, the term "comprising" can refer to direct inclusion or indirect inclusion. Optionally, "comprising" in the embodiments of this application can be replaced with "instructing" or "used to determine". For example, "A includes B" can be replaced with "A instructs B" or "A is used to determine B".

[0238] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0239] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0240] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0241] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0242] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0243] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0244] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0245] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0246] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for access control, characterized in that, include: The terminal device triggers access control and executes the access control according to the first configuration; The first configuration includes access control parameters for the terminal device, and the first configuration satisfies one or more of the following: The first configuration is used by the terminal device to determine whether to adjust the access control parameters; The first configuration is used by the terminal device to determine whether to allow the access attempt; The first configuration is one of multiple configurations associated with the first access category, and the first access category is the access category corresponding to the service that triggers the access control.

2. The method according to claim 1, characterized in that, The first configuration is based on one or more of the following configuration granularities: Quality of Service (QoS) flow; Radio bearer (RB); Logical Channel (LCH); Logical Channel Group (LCG); A first identifier, wherein the first identifier is used to identify the service type that triggers the access control; Access category.

3. The method according to claim 2, characterized in that, The first identifier is sent from the non-access layer of the terminal device to the access layer of the terminal device.

4. The method according to any one of claims 1-3, characterized in that, The first configuration includes first information, which is used by the terminal device to determine whether to adjust the access control parameters and / or by the terminal device to determine whether to allow the access attempt.

5. The method according to claim 4, characterized in that, The first information includes one or more of the following: The first parameter is used to determine whether adjusting the access control parameters is supported and / or whether allowing access attempts is supported; The second parameter is used to determine the adjusted access control parameters; The third parameter is used to indicate the threshold number of access attempts that the terminal device should attempt.

6. The method according to any one of claims 1-5, characterized in that, The first configuration also includes: The fourth parameter is used to indicate the identifier of the first configuration.

7. The method according to any one of claims 1-6, characterized in that, The first configuration is configured through one or more of the following: dedicated signaling; system broadcast messages.

8. The method according to any one of claims 1-7, characterized in that, The terminal device performs access control according to the first configuration, including one or more of the following: The terminal device adjusts the access control parameters according to the first configuration, and performs access control based on the adjusted access control parameters; The terminal device determines whether to allow the access attempt based on the first configuration.

9. The method according to claim 8, characterized in that, The terminal device adjusts the access control parameters according to the first configuration, including: If the first configuration includes a first parameter, or if the first configuration includes a first parameter and the value of the first parameter is a first value, the terminal device determines that it supports adjusting the access control parameter; and / or If the first configuration includes the second parameter, the terminal device determines that it supports adjusting the access control parameter; The first parameter is used to determine whether adjusting the access control parameters is supported and / or whether allowing access attempts is supported, and the second parameter is used to determine the adjusted access control parameters.

10. The method according to claim 8 or 9, characterized in that, The adjusted access control parameters are determined based on one or more of the following: The second parameter indicated by the first configuration; The number of times the terminal device attempts to access the device.

11. The method according to any one of claims 8-10, characterized in that, The terminal device determines whether to allow the access attempt based on the first configuration, including one or more of the following: If the first configuration includes a first parameter, or if the first configuration includes a first parameter and the value of the first parameter is a first value, the terminal device determines that it supports allowing the access attempt; If the first configuration includes a third parameter, the terminal device determines that it supports allowing the access attempt; The first parameter is used to determine whether adjusting the access control parameters is supported and / or whether allowing access attempts is supported, and the third parameter is used to indicate the threshold number of access attempts performed by the terminal device.

12. The method according to any one of claims 1-11, characterized in that, The first configuration for the terminal device to determine whether to allow the access attempt includes: The first configuration is used by the terminal device to determine whether to allow the access attempt based on the number of attempts made.

13. The method according to any one of claims 1-12, characterized in that, There is a mapping relationship between the multiple configurations and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs. The first configuration is determined based on the mapping relationship and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs.

14. A method for access control, characterized in that, include: The network device sends a first configuration to the terminal device, the first configuration being used by the terminal device to perform access control, the first configuration including the access control parameters of the terminal device; Wherein, the first configuration satisfies one or more of the following: The first configuration is used by the terminal device to determine whether to adjust the access control parameters; The first configuration is used by the terminal device to determine whether to allow the access attempt; The first configuration is one of multiple configurations associated with the first access category, and the first access category is the access category corresponding to the service that triggers the access control.

15. The method according to claim 14, characterized in that, The first configuration is based on one or more of the following configuration granularities: Quality of Service (QoS) flow; Radio bearer (RB); Logical Channel (LCH); Logical Channel Group (LCG); A first identifier, wherein the first identifier is used to identify the service type that triggers the access control; Access category.

16. The method according to claim 15, characterized in that, The first identifier is sent from the non-access layer of the terminal device to the access layer of the terminal device.

17. The method according to any one of claims 14-16, characterized in that, The first configuration includes first information, which is used by the terminal device to determine whether to adjust the access control parameters and / or by the terminal device to determine whether to allow the access attempt.

18. The method according to claim 17, characterized in that, The first information includes one or more of the following: The first parameter is used to determine whether adjusting the access control parameters is supported and / or whether allowing access attempts is supported; The second parameter is used to determine the adjusted access control parameters; The third parameter is used to indicate the threshold number of access attempts that the terminal device should attempt.

19. The method according to any one of claims 14-18, characterized in that, The first configuration also includes: The fourth parameter is used to indicate the identifier of the first configuration.

20. The method according to any one of claims 14-19, characterized in that, The first configuration is configured through one or more of the following: dedicated signaling; system broadcast messages.

21. The method according to any one of claims 14-20, characterized in that, The adjusted access control parameters are determined based on one or more of the following: The second parameter indicated by the first configuration; The number of times the terminal device attempts to access the device.

22. The method according to any one of claims 14-21, characterized in that, The first configuration for the terminal device to determine whether to allow the access attempt includes: The first configuration is used by the terminal device to determine whether to allow the access attempt based on the number of attempts made.

23. The method according to any one of claims 14-22, characterized in that, There is a mapping relationship between the multiple configurations and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs. The first configuration is determined based on the mapping relationship and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs.

24. A terminal device, characterized in that, include: A processing module is used to trigger access control and execute the access control according to the first configuration; The first configuration includes access control parameters for the terminal device, and the first configuration satisfies one or more of the following: The first configuration is used by the terminal device to determine whether to adjust the access control parameters; The first configuration is used by the terminal device to determine whether to allow the access attempt; The first configuration is one of multiple configurations associated with the first access category, and the first access category is the access category corresponding to the service that triggers the access control.

25. The terminal device according to claim 24, characterized in that, The first configuration is based on one or more of the following configuration granularities: Quality of Service (QoS) flow; Radio bearer (RB); Logical Channel (LCH); Logical Channel Group (LCG); A first identifier, wherein the first identifier is used to identify the service type that triggers the access control; Access category.

26. The terminal device according to claim 25, characterized in that, The first identifier is sent from the non-access layer of the terminal device to the access layer of the terminal device.

27. The terminal device according to any one of claims 24-26, characterized in that, The first configuration includes first information, which is used by the terminal device to determine whether to adjust the access control parameters and / or by the terminal device to determine whether to allow the access attempt.

28. The terminal device according to claim 27, characterized in that, The first information includes one or more of the following: The first parameter is used to determine whether adjusting the access control parameters is supported and / or whether allowing access attempts is supported; The second parameter is used to determine the adjusted access control parameters; The third parameter is used to indicate the threshold number of access attempts that the terminal device should attempt.

29. The terminal device according to any one of claims 24-28, characterized in that, The first configuration also includes: The fourth parameter is used to indicate the identifier of the first configuration.

30. The terminal device according to any one of claims 24-29, characterized in that, The first configuration is configured through one or more of the following: dedicated signaling; system broadcast messages.

31. The terminal device according to any one of claims 24-30, characterized in that, The terminal device performs access control according to the first configuration, including one or more of the following: The terminal device adjusts the access control parameters according to the first configuration, and performs access control based on the adjusted access control parameters; The terminal device determines whether to allow the access attempt based on the first configuration.

32. The terminal device according to claim 31, characterized in that, The terminal device adjusts the access control parameters according to the first configuration, including: If the first configuration includes a first parameter, or if the first configuration includes a first parameter and the value of the first parameter is a first value, the terminal device determines that it supports adjusting the access control parameter; and / or If the first configuration includes the second parameter, the terminal device determines that it supports adjusting the access control parameter; The first parameter is used to determine whether adjusting the access control parameters is supported and / or whether allowing access attempts is supported, and the second parameter is used to determine the adjusted access control parameters.

33. The terminal device according to claim 31 or 32, characterized in that, The adjusted access control parameters are determined based on one or more of the following: The second parameter indicated by the first configuration; The number of times the terminal device attempts to access the device.

34. The terminal device according to any one of claims 31-33, characterized in that, The terminal device determines whether to allow the access attempt based on the first configuration, including one or more of the following: If the first configuration includes a first parameter, or if the first configuration includes a first parameter and the value of the first parameter is a first value, the terminal device determines that it supports allowing the access attempt; If the first configuration includes a third parameter, the terminal device determines that it supports allowing the access attempt; The first parameter is used to determine whether adjusting the access control parameters is supported and / or whether allowing access attempts is supported, and the third parameter is used to indicate the threshold number of access attempts performed by the terminal device.

35. The terminal device according to any one of claims 24-34, characterized in that, The first configuration for the terminal device to determine whether to allow the access attempt includes: The first configuration is used by the terminal device to determine whether to allow the access attempt based on the number of attempts made.

36. The terminal device according to any one of claims 24-35, characterized in that, There is a mapping relationship between the multiple configurations and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs. The first configuration is determined based on the mapping relationship and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs.

37. A network device, characterized in that, include: The sending module is configured to send a first configuration to the terminal device, the first configuration being used by the terminal device to perform access control. One configuration includes the access control parameters of the terminal device; Wherein, the first configuration satisfies one or more of the following: The first configuration is used by the terminal device to determine whether to adjust the access control parameters; The first configuration is used by the terminal device to determine whether to allow the access attempt; The first configuration is one of multiple configurations associated with the first access category, and the first access category is the access category corresponding to the service that triggers the access control.

38. The network device according to claim 37, characterized in that, The first configuration is based on one or more of the following configuration granularities: Quality of Service (QoS) flow; Radio bearer (RB); Logical Channel (LCH); Logical Channel Group (LCG); A first identifier, wherein the first identifier is used to identify the service type that triggers the access control; Access category.

39. The network device according to claim 38, characterized in that, The first identifier is sent from the non-access layer of the terminal device to the access layer of the terminal device.

40. The network device according to any one of claims 37-39, characterized in that, The first configuration includes first information, which is used by the terminal device to determine whether to adjust the access control parameters and / or by the terminal device to determine whether to allow the access attempt.

41. The network device according to claim 40, characterized in that, The first information includes one or more of the following: The first parameter is used to determine whether adjusting the access control parameters is supported and / or whether allowing access attempts is supported; The second parameter is used to determine the adjusted access control parameters; The third parameter is used to indicate the threshold number of access attempts that the terminal device should attempt.

42. The network device according to any one of claims 37-41, characterized in that, The first configuration also includes: The fourth parameter is used to indicate the identifier of the first configuration.

43. The network device according to any one of claims 37-42, characterized in that, The first configuration is configured through one or more of the following: dedicated signaling; system broadcast messages.

44. The network device according to any one of claims 37-43, characterized in that, The adjusted access control parameters are determined based on one or more of the following: The second parameter indicated by the first configuration; The number of times the terminal device attempts to access the device.

45. The network device according to any one of claims 37-44, characterized in that, The first configuration for the terminal device to determine whether to allow the access attempt includes: The first configuration is used by the terminal device to determine whether to allow the access attempt based on the number of attempts made.

46. ​​The network device according to any one of claims 37-45, characterized in that, There is a mapping relationship between the multiple configurations and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs. The first configuration is determined based on the mapping relationship and the QoS flow / RB / LCH / LCG / first identifier to which the service triggering the access control belongs.

47. A terminal device, characterized in that, It includes a memory and a processor, the memory being used to store a program, and the processor being used to invoke the program in the memory to cause the terminal device to perform the method as described in any one of claims 1-13.

48. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method as described in any one of claims 14-23.

49. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-13 or 14-23.

50. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-13 or 14-23.

51. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-13 or 14-23.

52. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-13 or 14-23.

53. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-13 or 14-23.

Images