Method and apparatus for access control for small scale and infrequent data transmissions

Abstract

Embodiments of the present disclosure relate to methods and apparatuses for access control for small-scale and infrequent data transmission. According to embodiments of the present disclosure, a method includes receiving access control configuration information; and performing access control of a user equipment (UE) based on the access control configuration information, wherein the UE is configured with preconfigured uplink (UL) resources, and the UE supports small-scale and infrequent data transmission in a radio resource control (RRC) inactive state or an RRC idle state.

Description

TECHNICAL FIELD

[0001] This application relates generally to wireless communication technology, and more specifically to methods and apparatus for access control for small and infrequent data transmissions. BACKGROUND

[0002] In 3GPP (Third Generation Partnership Project) 5G systems, small and infrequent data transmissions are introduced for several use cases. For example, according to the agreement of 3GPP TSG RAN meeting #86, small and infrequent data transmissions can be used for smartphone applications including traffic from instant messaging services or for non-smartphone applications including traffic from wearable devices. Small and infrequent data transmissions can also be referred to as small data packets or small data transmissions.

[0003] Generally, any device with intermittent small data transmissions in a radio resource control (RRC) inactive state or an RRC idle state would benefit from enabling small data transmissions in an RRC inactive state (i.e., RRC inactive state) or an RRC idle state (i.e., RRC idle state). However, for small data transmissions, the signaling overhead from user equipment (UE) in an RRC inactive state or an RRC idle state is a common problem and will be a key issue for more UEs, not only for network performance and efficiency, but also for UE battery performance.

[0004] 3GPP 5G networks are expected to improve network throughput, coverage, and robustness and reduce latency and power consumption. As 3GPP 5G networks evolve, various aspects need to be researched and developed to perfect 5G technology. SUMMARY

[0005] One object of embodiments of the present disclosure is to provide a new type of mechanism for access control for small and infrequent data transmissions of a user equipment (UE).

[0006] Some embodiments of the present application provide a method that can be performed by a UE. The method includes receiving access control configuration information; and performing access control for a user equipment (UE) based on the access control configuration information, wherein the UE is configured with preconfigured uplink (UL) resources, and the UE supports small and infrequent data transmissions in one of an RRC inactive state and an RRC idle state.

[0007] Some embodiments of the application provide a device. The device includes a non-transitory computer-readable medium having computer-executable instructions stored thereon, receiving circuitry, transmitting circuitry, and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry, wherein the computer-executable instructions cause the processor to implement the above method performed by a UE.

[0008] Some embodiments of the application provide a method, which can be performed by a network or a base station (BS). The method includes transmitting an indicator indicating support for receiving a first small-scale and infrequent data transmission from a UE and transmitting another small-scale and infrequent data transmission to the UE, wherein the UE is in one of an RRC inactive state and an RRC idle state, and the UE is configured with preconfigured uplink (UL) resources, and transmitting access control configuration information.

[0009] Some embodiments of the application provide a device. The device includes a non-transitory computer-readable medium having computer-executable instructions stored thereon, receiving circuitry, transmitting circuitry, and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry, wherein the computer-executable instructions cause the processor to implement the above method performed by a network or a BS.

[0010] The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will become apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF DRAWINGS

[0011] In order to describe the manner in which the advantages and features of the application can be obtained, a description of the application will be rendered by reference to specific embodiments thereof which are illustrated in the drawings. These drawings depict only example embodiments of the application and are therefore not to be considered limiting of its scope.

[0012] Figure 1 FIG. 1 illustrates a wireless communication system according to some embodiments of the application;

[0013] Figure 2 FIG. 2 illustrates a flowchart of a method for performing access control according to some embodiments of the application;

[0014] Figure 3 FIG. 3 illustrates a flowchart of a method for transmitting access control configuration information according to some embodiments of the application; and

[0015] Figure 4 FIG. 4 illustrates a device according to some embodiments of the application. DETAILED DESCRIPTION

[0016] The detailed description of the drawings is intended to illustrate preferred embodiments of the application and not to limit the application to the precise form disclosed. It should be understood that the same or equivalent functions could be accomplished by different embodiments, which are intended to fall within the spirit and scope of the application.

[0017] Reference will now be made in detail to some embodiments of the application, examples of which are illustrated in the accompanying drawings. For ease of understanding, the embodiments are provided in specific network architecture and new service scenarios, such as 3GPP 5G, 3GPP LTE Release 8, B5G, 6G, etc. It can be considered that all embodiments in the present application are also applicable to similar technical problems as the network architecture and new service scenarios develop; in addition, the terms cited in the present application can change, which does not affect the principles of the present application.

[0018] Figure 1 A wireless communication system 100 according to some embodiments of the present application is illustrated.

[0019] Reference Figure 1 The wireless communication system 100 can include UEs 101 and BSs 102. Although a specific number of UEs 101 and BSs 102 are depicted in Figure 1 it can be considered that additional UEs 101 and BSs 102 can be used in the wireless communication system 100.

[0020] BSs 102 can be distributed over a geographic region, and each BS 102 can communicate with a core network (CN) node. In some embodiments of the application, the BSs 102 can also be referred to as access points, access terminals, base stations, base station units, macrocells, nodeBs, evolved nodeBs (eNBs), gNBs, home nodeBs, relay nodes, or devices, or described using other terminology used in the art. The BSs 102 are generally part of a radio access network that can include one or more controllers communicably coupled to one or more corresponding BSs 102.

[0021] The UEs 101 can communicate directly with the BSs 102 via uplink communication signals. The UEs 101 can be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, wireless terminals, fixed terminals, subscriber stations, user terminals, or devices, or described using other terminology used in the art.

[0022] In some embodiments of the present application, the UE 101 can include, for example and without limitation, a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart television (e.g., a television connected to the Internet), a set-top box, a game console, a security system (including security cameras), a vehicle-mounted computer, a network device (e.g., a router, switch, and modem), an Internet of Things (IoT) device, an Industrial Internet of Things (IIoT) device, or the like.

[0023] According to some embodiments of the present application, the UE 101 can include, for example and without limitation, a portable wireless communication device, a cell phone, a cellular telephone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals over a wireless network.

[0024] Additionally, in some embodiments of the present application, the UE 101 can include, for example and without limitation, a wearable device such as a smart watch, a fitness band, an optical head-mounted display, or the like.

[0025] The wireless communication system 100 can be compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) based network, a code division multiple access (CDMA) based network, an orthogonal frequency division multiple access (OFDMA) based network, an LTE network, a 3GPP based network, a 3GPP 5G network, a satellite communication network, a high altitude platform network, and / or other communication network.

[0026] In some embodiments of the present application, the wireless communication system 100 is compatible with 5G New Radio of the 3GPP protocol, in which the BS 102 transmits data using an OFDM modulation scheme on the DL and the UE 101 transmits data using a single-carrier frequency division multiple access (SC-FDMA) or OFDM scheme on the UL. However, more generally, the wireless communication system 100 can implement some other open or proprietary communication protocol, such as WiMAX, WiFi, and other protocols.

[0027] In some embodiments of the present application, the BS 102 can communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Moreover, in some embodiments of the present application, the BS 102 can communicate over a licensed spectrum, while in other embodiments the BS 102 can communicate over an unlicensed spectrum. The present application is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In still other embodiments of the present application, the BS 102 can communicate with the UE 101 using the 3GPP 5G protocol.

[0028] In 3GPP 5G New Radio (NR), Unified Access Control (UAC) is introduced. In particular, UAC supports all services and maps different application procedures, services, voice calls, users with different priorities, etc. to categories and the network side controls the access of the UE based on the categories.

[0029] In 3GPP TS 38.331, UAC is specified as follows:

[0030] 5.3.14.2 Start

[0031] Upon starting the procedure, the UE shall:

[0032] 1> if timer T390 is running for the access category:

[0033] 2> consider the access attempt barred;

[0034] 1> else if timer T302 is running and the access category is neither '2' nor '0':

[0035] 2> consider the access attempt barred;

[0036] 1> else:

[0037] 2> if the access category is '0':

[0038] 3> consider the access attempt allowed;

[0039] 2> else:

[0040] 3> if SIB1 contains uac-BarringPerPLMN-List and uac-BarringPerPLMN-List contains a UAC-BarringPerPLMN entry with plmn-IdentityIndex corresponding to the PLMN selected by upper layers (see TS 24.501

[23] ):

[0041] 4> select the UAC-BarringPerPLMN entry with plmn-IdentityIndex corresponding to the PLMN selected by upper layers;

[0042] 4> for the remainder of this procedure, use the selected UAC-BarringPerPLMN entry (i.e. the presence or absence of the access barring parameter in this entry), without considering uac-BarringForCommon included in SIB1;

[0043] 3> else if SIB1 contains uac-BarringForCommon:

[0044] 4> use uac-BarringForCommon contained in SIB1 (i.e. presence or absence of these parameters) for the remainder of this procedure;

[0045] 3> else:

[0046] 4> consider the access attempt to be allowed;

[0047] 3> if uac-BarringForCommon applies or uac-ACBarringListType indicates that uac-ExplicitACBarringList is used:

[0048] 4> if the corresponding UAC-BarringPerCatList contains a UAC-BarringPerCat entry corresponding to the access category:

[0049] 5> select the UAC-BarringPerCat entry;

[0050] 5> if uac-BarringInfoSetList contains a UAC-BarringInfoSet entry corresponding to the selected uac-barringInfoSetIndex in UAC-BarringPerCat:

[0051] 6> select the UAC-BarringInfoSet entry;

[0052] 6> perform the access barring check for the access category as specified in 5.3.14.5 using the selected UAC-BarringInfoSet as "UAC barring parameters";

[0053] 5> else:

[0054] 6> consider the access attempt to be allowed;

[0055] 4> else:

[0056] 5> consider the access attempt to be allowed;

[0057] 3> else if uac-ACBarringListType indicates that uac-ImplicitACBarringList is used:

[0058] 4> select the uac-BarringInfoSetIndex in uac-ImplicitACBarringList corresponding to the access category;

[0059] 4> if the uac-BarringInfoSetList contains a UAC-BarringInfoSet entry corresponding to the selected uac-BarringInfoSetIndex:

[0060] 5> select the UAC-BarringInfoSet entry;

[0061] 5> perform an access barring check for the access category as specified in 5.3.14.5, using the selected UAC-BarringInfoSet as "UAC barring parameters";

[0062] 4> else:

[0063] 5> consider the access attempt as allowed;

[0064] 3> else:

[0065] 4> consider the access attempt as allowed;

[0066] 1> if the access barring check is requested by upper layers:

[0067] 2> if the access attempt is considered as barred:

[0068] 3> if the timer T302 is running:

[0069] 4> if the timer T390 is running for access category '2':

[0070] 5> inform upper layers that access barring applies to all access categories except category '0', after which the procedure ends;

[0071] 4> else

[0072] 5> inform upper layers that access barring applies to all access categories except categories '0' and '2', after which the procedure ends;

[0073] 3> else:

[0074] 4> inform upper layers that the access attempt for the access category is barred, after which the procedure ends;

[0075] 2> else:

[0076] 3> inform upper layers that the access attempt for the access category is allowed, after which the procedure ends;

[0077] 1> else:

[0078] 2> the procedure ends.

[0079] 5.3.14.5 Access barring check

[0080] The UE shall:

[0081] 1> if one or more of the access identities are indicated according to TS 24.501

[23] , and

[0082] 1> if for at least one of these access identities, the corresponding bit in uac-BarringForAccessIdentity included in the "UAC barring parameters" is set to zero:

[0083] 2> consider the access attempt to be allowed;

[0084] 1> else:

[0085] 2> draw a random number 'rand' uniformly distributed in the range: 0 < rand < 1;

[0086] 2> if 'rand' is lower than the value indicated by uac-BarringFactor included in the "UAC barring parameters":

[0087] 3> consider the access attempt to be allowed;

[0088] 2> else:

[0089] 3> consider the access attempt to be barred;

[0090] 1> if the access attempt is considered to be barred:

[0091] 2> draw a random number 'rand' uniformly distributed in the range: 0 < rand < 1;

[0092] 2> start a timer T390 for the access category using uac-BarringTime included in the "AC barring parameters", the timer value is calculated as follows:

[0093] T390 = (0.7 + 0.6*rand) * uac-BarringTime

[0094] AIs and ACs are defined in 3GPP TS 24.501.

[0095] The following table 4.5.2.1 lists the AIs.

[0096] Table 4.5.2.1

[0097]

[0098]

[0099] The following table 4.5.2.2 is a mapping table for ACs.

[0100] Table 4.5.2.2

[0101]

[0102]

[0103] In addition, 3GPP TS 24.501 also describes the mapping between AC / AI and RRC establishment cause in section 4.5.6.

[0104] Generally, a UE in RRC inactive state shall perform Unified Access Control (UAC) when sending uplink user data packets for a packet data unit (PDU) session with suspended user plane resources. UAC is used to determine whether or not which access attempt should be allowed or not to avoid congestion in 3GPP 5G system. In other words, when congestion occurs, there is not enough resource allocated and access attempt is prohibited. When the higher layer (e.g. non-access stratum (NAS) layer) of the UE detects sending uplink user data packets for a PDU session with suspended user plane resources, the UE will perform access barring check based on the determined AI and AC.

[0105] Based on current principles, there is no difference in access probability between the following two types of UEs camped on the same cell:

[0106] (1) UE A in RRC inactive state is configured with preconfigured UL resources for small data transmission. Meanwhile, traffic#a arrives and traffic#a is suitable as small data transmission.

[0107] (2) UE B in RRC inactive state is not configured with preconfigured UL resources. Meanwhile, traffic#a suitable as small data transmission arrives.

[0108] Since UAC result is determined from the perspective of available resources, in the above example, UE A shall have higher access probability than UE B. Otherwise, in some cases, preconfigured UL resources can be wasted, especially in medium to heavy load cases. In view of the above, there is a need to address how to control the access of UEs configured with preconfigured UL resources which implement small data transmission.

[0109] Embodiments of the present application implement an optimized access control procedure for UEs configured with preconfigured UL resources and implementing small data transmission. Embodiments of the present application avoid the waste of preconfigured UL resources.

[0110] Some embodiments of the present application provide a solution that considers an access attempt to be allowed if the UE is configured with preconfigured UL resources and if the access attempt is for a configured traffic and the traffic is allowed to be transmitted on the preconfigured UL resources as a small data transmission. For example, the traffic is represented by at least one of a configured PDU session, a configured data flow, a configured QoS flow, a configured data radio carrier (DRB), and a configured logical channel (LCH). For example, if the small data transmission is triggered by a traffic that is allowed to be transmitted in the preconfigured UL resources, the UE can select a specific value 'n' as the AC. In Figure 2 A specific example is described in the embodiments of

[0111] Some embodiments of the present application provide a set of specific access control parameters for small data transmission. The set of access control parameters can be broadcasted or RRC dedicated configured. When the UE is configured with preconfigured UL resources, different set of access control parameters will be applied to the same traffic depending on whether the traffic is associated with the preconfigured UL resources for small data transmission.

[0112] Figure 2 is a flowchart illustrating a method for performing access control according to some embodiments of the present application.

[0113] Figure 2 The method illustrated in Figure 1 may be implemented by a UE, such as the UE 101 illustrated and shown in Figure 2 Although described with respect to a UE, it should be understood that other devices can be configured to perform methods similar to the method of

[0114] As shown in Figure 2 , at operation 201, the UE receives access control configuration information. The UE can be configured with preconfigured uplink (UL) resources. The UE can support small-scale and infrequent data transmission in one of an RRC inactive state and an RRC idle state. For example, the UE is configured by the network or the BS to support small-scale and infrequent data transmission in the RRC inactive state or the RRC idle state. At operation 202, the UE performs access control of the UE based on the access control configuration information received in operation 201.

[0115] The following text describes detailed embodiments of the present application. The details described in the embodiments illustrated and shown in Figure 1 , 3 and 4, particularly those related to specific operations for access control for small-scale and infrequent data transmission, are applicable to the embodiments illustrated and shown in Figure 2 . Furthermore, the details described in the embodiments of Figure 2 are applicable to all embodiments of Figure 1 , 3 and 4.

[0116] In some embodiments, the UE receives the access control configuration information through a broadcast message or through RRC signaling. In one embodiment, the UE receives the access control configuration information from the network side (e.g., the BS 102 as illustrated and demonstrated in Figure 1 ). And then the UE can perform access control based on the access control configuration information.

[0117] The access control configuration information can include a set of access control parameters, which can include one or more barring information group entries. For example, the access control configuration information includes a set of unified access control (UAC) parameters, and the set of UAC parameters includes one or more of the following:

[0118] (1) one or more access categories (ACs).

[0119] (2) one or more access identities (AIs).

[0120] (3) a UAC barring parameter. The UAC barring parameter can include an AC of the UE (e.g., the UE 101 as illustrated and demonstrated in Figure 1 ).

[0121] (4) information about whether an access attempt of the UE is allowed for each AI of the UE. The UE can be for one or more AIs. The information about whether an access attempt of the UE is allowed for each AI of the UE includes an AI of the UE.

[0122] (5) a probability of allowing an access attempt of the UE during an access barring check. The probability of allowing an access attempt of the UE can include 100%.

[0123] (6) a minimum time before a subsequent access attempt of the UE is to be performed after an access attempt of the UE is barred during an access barring check. The subsequent access attempt and the access attempt of the UE are for the same AC.

[0124] In some embodiments, the set of UAC parameters includes a plurality of barring information group entries, and each barring information group entry includes one or more of the above.

[0125] In an embodiment, a new entry ‘p’ can be defined for the UE (e.g., the UE 101 as illustrated and demonstrated in Figure 1 ) that is configured with preconfigured UL resources for small data transmission. In particular, the entry ‘p’ can include an AC and a corresponding UAC barring parameter.

[0126] For example, the UAC barring parameter can include: uac-BarringForAccessIdentity, uac-BarringFactor, and uac-BarringTime, as shown in Table 1 below.

[0127] Table 1

[0128]

[0129] In an embodiment, if the UE is configured with preconfigured UL resources for small data transmission and if an entry 'p' corresponding to an AC is included in the system broadcast message, the UE can select the entry 'p' corresponding to the AC to perform access barring check for the AC. In a further embodiment, a newly defined AC (e.g., 'n' or'm' in the following examples 1 to 7) or a newly defined AI (e.g., 'x' in the following case A) can be included in the UAC barring parameters.

[0130] For example, if the UE is configured with preconfigured UL resources for small data transmission and if traffic arrives, but is not allowed to be transmitted as small data transmission on the preconfigured UL resources or is not allowed to be configured to be transmitted as small data transmission on the preconfigured UL resources, the UE can select an entry different from 'p' to perform access barring check for the AC according to the system broadcast message.

[0131] In some embodiments, performing access control for the UE comprises obtaining information related to the UE and determining whether to allow an access attempt of the UE based on the information related to the UE.

[0132] In an embodiment, the information related to the UE is included in the access control configuration information received in operation 201. In a further embodiment, the information related to the UE is indicated by a higher layer (e.g., NAS layer) of the UE. In another embodiment, the information related to the UE is selected or set by a lower layer (e.g., access stratum (AS) layer) of the UE.

[0133] The information related to the UE includes one or more of the following:

[0134] a) one or more ACs of the UE. The one or more ACs of the UE can be indicated by a higher layer of the UE or selected by a lower layer of the UE.

[0135] b) one or more AIs of the UE. The one or more AIs of the UE can be indicated by a higher layer of the UE or selected by a lower layer of the UE.

[0136] c) a bitmap of AIs of the UE. The bitmap of AIs of the UE can be received from a system broadcast message. For example, as explained and shown in Figure 1 the UE 101 receives the bitmap of AIs of the UE 101 from the BS 102 as explained and shown in Figure 1

[0137] d) a barring information group entry, e.g., a barring information group entry in a group of UAC parameters. ​

[0138] In particular, in some embodiments, if the UE determines that the access attempt is allowed, the UE further determines whether the access attempt is associated with a small data transmission. If the UE determines that the access attempt is associated with a small data transmission, the UE transmits the small data transmission on the preconfigured UL resource. Otherwise, if the UE determines that the access attempt is not associated with a small data transmission, the UE will not transmit any transmission on the preconfigured UL resource.

[0139] In some embodiments, the UE in RRC inactive or idle state allows the access attempt directly based on the AC of the UE. There can be the following cases:

[0140] Case 1: If the UE is configured with preconfigured UL resource for small data transmission and if uplink user data packet is to be sent for a PDU session with suspended user plane resources, the UE considers the access attempt to be allowed.

[0141] Case 2: If the UE is configured with preconfigured UL resource for small data transmission, if the UE is configured with a PDU session, data flow, QoS flow, DRB or LCH which is allowed to be transmitted on the preconfigured UL resource for small data transmission, and if the access attempt is for the configured PDU session, data flow, QoS flow, DRB or LCH, the UE considers the access attempt to be allowed.

[0142] Case 3: If the UE is configured with preconfigured UL resource for small data transmission, if the UE is configured with a PDU session, data flow, QoS flow, DRB or LCH which is allowed to be transmitted on the preconfigured UL resource for small data transmission, if uplink user data packet is to be sent for a PDU session with suspended user plane resources, and if the access attempt is for the configured PDU session, data flow, QoS flow, DRB or LCH, the UE considers the access attempt to be allowed.

[0143] Case 4:

[0144] Scenario 1: If the UE is configured with preconfigured UL resource for small data transmission and if uplink user data packet is to be sent for a PDU session with suspended user plane resources, the UE further determines whether the data can be fully transmitted by the current preconfigured UL resource.

[0145] Scenario 2: If the UE is configured with preconfigured UL resource for small data transmission, if the UE is configured with a PDU session, data flow, QoS flow, DRB or LCH which is allowed to be transmitted on the preconfigured UL resource for small data transmission, and if the access attempt is for the configured PDU session, data flow, QoS flow, DRB or LCH, the UE further determines whether the data can be fully transmitted by the current preconfigured UL resource.

[0146] Scenario 3: If the UE is configured with preconfigured UL resources for small data transmission, if the UE is configured with a PDU session, a data flow, a QoS flow, a DRB, or a LCH, which is allowed to be transmitted on the preconfigured UL resources as small data transmission, if an uplink user data packet is to be transmitted for a PDU session with suspended user plane resources, and if the access attempt is for the configured PDU session, data flow, QoS flow, DRB, or LCH, then the UE further determines whether the data can be fully transmitted by the current preconfigured UL resources.

[0147] Regarding scenarios 1 to 3 of case 4 above, after the determination, there can be the following sub-cases:

[0148] 4.1. If the data can be fully transmitted by the current preconfigured UL resources, the UE considers that the access attempt is allowed.

[0149] 4.2. If the data cannot be fully transmitted by the current preconfigured UL resources, the UE considers that the access attempt is not allowed.

[0150] 4.3. If the data cannot be fully transmitted by the current preconfigured UL resources, the UE further determines whether the size of the data to be transmitted needs to be segmented and assembled into the current preconfigured resources and whether the remaining size of the data can be assembled into the subsequent preconfigured resources and whether the data / packets will be discarded due to the expiration of service data units (SDUs), data, or packets. If the UE determines that the size of the data to be transmitted needs to be segmented and assembled into the current preconfigured resources, the remaining size of the data can be assembled into the following preconfigured resources, and the data or packets will not be discarded due to the expiration of SDUs, data, or packets, then the UE considers that the access attempt is allowed.

[0151] In particular, in embodiments, during the determination of whether to allow the access attempt, the UE can perform the following operations:

[0152] (1) If one AC of the UE is obtained, and the one AC represents an access configuration associated with small data transmission, then the UE can allow the access attempt. The access configuration can also be named as one piece of access configuration information. Specific examples of such operations are described in the following examples 1 to 5.

[0153] In further embodiments, during the determination of whether to allow the access attempt, the UE can perform the following operations:

[0154] (1) If one AC and / or one or more AIs are obtained, the UE can set a predefined value as the value of the one AC. The predefined value is related to the access configuration.

[0155] (2) Then, the UE further determines whether the value of the one AC is equal to the predefined value.

[0156] (3) Option 1: If the UE determines that the value of one AC is equal to a pre-defined value, then the UE allows the access attempt. Specific examples of such operation are described in Examples 6 and 7 below.

[0157] (4) Option 2: If one AC and / or one or more AIs of the UE are obtained, the UE can set a pre-defined value as the value of the AC. If the UE is configured with pre-configured UL resources for small data transmission, and if an entry ‘p’ corresponding to the AC is included in the system broadcast message, the UE can select the entry ‘p’ to perform the access barring check for the AC.

[0158] In another embodiment, during determining whether to allow the access attempt, the UE can perform the following operations:

[0159] (1) If one AC of the UE is obtained, and the AC indicates an access configuration associated with small data transmission, the UE determines whether the data to be transmitted by the UE can be completely transmitted on the pre-configured UL resources.

[0160] (2) If the UE determines that the data to be transmitted by the UE can be completely transmitted on the pre-configured UL resources, the UE allows the access attempt of the UE.

[0161] (3) If the UE determines that the data to be transmitted by the UE cannot be completely transmitted on the pre-configured UL resources, the UE further determines whether the data to be transmitted by the UE will be discarded.

[0162] (4) If the UE determines that the data to be transmitted by the UE will not be discarded, the UE allows the access attempt.

[0163] For example, the access configuration associated with small data transmission can include one or more of the following configuration information, and specific examples of such operation are described in Examples 1 to 7:

[0164] (1) The UE is configured to transmit small data transmission on pre-configured UL resources.

[0165] (2) The UE is configured with traffic allowed to be transmitted as small data transmission on the pre-configured UL resources. The traffic is represented by at least one of PDU session, data flow, DRB, LCH, and QoS flow.

[0166] For Example 1, the above procedure can be implemented by 3GPP specification documents as:

[0167] (1) Define an access category “n” for small data transmission on pre-configured UL resources when the UE is in RRC inactive or idle state; and / or

[0168] (2) A new access category'm' is defined for traffic that is allowed to be transmitted on pre-configured UL resources as small data transmission when the UE is in RRC Inactive or Idle state. The traffic can be a configured PDU session, data flow, QoS flow, DRB or LCH.

[0169] For example, the relevant 3GPP specification document can define the operation of the UE in Example 1 as follows:

[0170] Upon initiation of the (unified access control) procedure (at AS layer), the UE shall:

[0171] 1> if timer T390 is running for the access category:

[0172] 2> consider the access attempt to be barred;

[0173] 1> else if timer T302 is running and the access category is neither '2' nor '0':

[0174] 2> consider the access attempt to be barred;

[0175] 1> else:

[0176] 2> if the access category is '0' or 'n' or'm':

[0177] 3> consider the access attempt to be allowed;

[0178] ...

[0179] For Example 2, the above procedure can be implemented by the 3GPP specification document as:

[0180] • A new access category'm' is defined for traffic that is allowed to be transmitted on pre-configured UL resources as small data transmission when the UE is in RRC Inactive or Idle state. The traffic can be a configured PDU session, data flow, QoS flow, DRB or LCH.

[0181] For example, the relevant 3GPP specification document can define the operation of the UE in Example 2 as follows:

[0182] Upon initiation of the (unified access control) procedure (at AS layer), the UE shall:

[0183] 1> if timer T390 is running for the access category:

[0184] 2> consider the access attempt to be barred;

[0185] 1> else if timer T302 is running and the access category is neither '2' nor '0':

[0186] 2> consider the access attempt to be barred;

[0187] 1> else:

[0188] 2> if the access category is '0':

[0189] 3> consider the access attempt to be allowed;

[0190] 2> else if the access category is'm' or the UE is configured with preconfigured UL resources for small data transmission and if the UE is in RRC inactive or idle state:

[0191] 3> consider the access attempt to be allowed;

[0192] ...

[0193] For example 3, the above procedure can be implemented by a 3GPP specification document as:

[0194] • define an access category 'n' for small data transmission on preconfigured UL resources when the UE is in RRC inactive or idle state.

[0195] For example, the relevant 3GPP specification document can define the operation of the UE in example 3 as follows:

[0196] Upon initiation of the (unified access control) procedure (at AS layer), the UE shall:

[0197] 1> if timer T390 is running for the access category:

[0198] 2> consider the access attempt to be barred;

[0199] 1> else if timer T302 is running and the access category is neither '2' nor '0':

[0200] 2> consider the access attempt to be barred;

[0201] 1> else:

[0202] 2> if the access category is '0':

[0203] 3> consider the access attempt to be allowed;

[0204] 2> else if the access category is 'n' and the UE is in RRC inactive or idle state:

[0205] 3> consider the access attempt to be allowed;

[0206] ...

[0207] For example 4, the 3GPP specification document can define the operation of the UE as follows:

[0208] Upon initiation of the (unified access control) procedure (at AS layer), the UE shall:

[0209] 1> if timer T390 is running for the access category:

[0210] 2> consider the access attempt barred;

[0211] 1> else if timer T302 is running and the access category is neither '2' nor '0':

[0212] 2> consider the access attempt barred;

[0213] 1> else:

[0214] 2> if the access category is '0':

[0215] 3> consider the access attempt allowed;

[0216] 2> else if the UE is configured with preconfigured UL resources for small data transmission and the UE is in RRC inactive or idle state:

[0217] 3> consider the access attempt allowed;

[0218] …

[0219] For instance 5, the above procedure can be implemented by a 3GPP specification document as:

[0220] • Configuring the service DRB 'k' to be allowed to be transmitted as small data transmission on the preconfigured UL resources. Similarly, in other cases, 'k' can be configured to represent a data flow, a QoS flow or a LCH.

[0221] For example, a relevant 3GPP specification document can define the operation of the UE in instance 5 as follows:

[0222] Upon (AS layer) initiation of the (unified access control) procedure, the UE shall:

[0223] 1> if timer T390 is running for the access category:

[0224] 2> consider the access attempt barred;

[0225] 1> else if timer T302 is running and the access category is neither '2' nor '0':

[0226] 2> consider the access attempt barred;

[0227] 1> else:

[0228] 2> if the access category is '0':

[0229] 3> consider the access attempt allowed;

[0230] 2> else if the UE is configured with preconfigured UL resources for small data transmission and the newly arrived data is for a configured DRB 'k' and the UE is in RRC Inactive or Idle state:

[0231] 3> consider the access attempt as allowed;

[0232] ...

[0233] For example 6, the above procedure can be implemented by a 3GPP specification document as:

[0234] • (optional) define an access category 'n' for small data transmission on preconfigured UL resources when the UE is in RRC Inactive or Idle state.

[0235] For example, the relevant 3GPP specification document can define the operation of the UE in example 6 as follows:

[0236] 1> else if the resumption of RRC connection is triggered by upper layers:

[0237] 2> if the access category '7' and one or more access identities are provided by upper layers and preconfigured UL resources for small data transmission are configured:

[0238] 3> set / select 'n' as the access category;

[0239] 3> perform the unified access control procedure as specified in 5.3.14 using the access category and access identities provided by upper layers;

[0240] 4> if the access attempt is barred, the procedure ends;

[0241] ...

[0242] When starting the (unified access control) procedure, the UE shall:

[0243] 1> if timer T390 is running for the access category:

[0244] 2> consider the access attempt as barred;

[0245] 1> else if timer T302 is running and the access category is neither '2' nor '0':

[0246] 2> consider the access attempt as barred;

[0247] 1> else:

[0248] 2> if the access category is 'n':

[0249] 3> consider the access attempt as allowed;

[0250] ...

[0251] For example 7, the above procedure can be implemented by 3GPP specification documents as follows:

[0252] • (Optional) A new access category'm' is defined for traffic that is allowed to be transmitted on preconfigured UL resources as small data transmission when the UE is in RRC inactive or idle state. The traffic can be configured at PDU session, data flow, QoS flow, DRB or LCH level.

[0253] For example, the relevant 3GPP specification documents can define the operation of the UE in example 7 as follows:

[0254] 1> else if the RRC connection resume is triggered by upper layers:

[0255] 2> if the upper layers provide an access category '7' and one or more access identities and the arrival data is allowed to be transmitted on UL preconfigured resources as small data transmission:

[0256] 3> set / select'm' as the access category;

[0257] 3> use the access category and access identities provided by upper layers to perform the unified access control procedure as specified in 5.3.14;

[0258] 4> if the access attempt is barred, the procedure ends;

[0259] ...

[0260] When initiating the (unified access control) procedure (at AS layer), the UE shall:

[0261] 1> if timer T390 is running for the access category:

[0262] 2> consider the access attempt as barred;

[0263] 1> else if timer T302 is running and the access category is neither '2' nor '0':

[0264] 2> consider the access attempt as barred;

[0265] 1> else:

[0266] 2> if the access category is'm':

[0267] 3> consider the access attempt as allowed;

[0268] ...

[0269] In some further embodiments, the UE directly allows the access attempt based on the UE's AI. There can be the following cases.

[0270] Case A

[0271] 1. A new access identity 'x' is defined for UEs in RRC inactive or idle state capable of transmitting or receiving small data transmission.

[0272] 2. The UE is configured with preconfigured UL resources for small data transmission.

[0273] 3. The AI 'x' is indicated by higher layers (e.g. NAS layer). Alternatively, the AI 'x' is set or selected by lower layers (e.g. AS layer).

[0274] 4. If all the above conditions 1 to 3 are met, the access attempt is considered allowed.

[0275] Case B

[0276] 1. A new access identity 'x' is defined for UEs in RRC inactive or idle state capable of transmitting or receiving small data transmission.

[0277] 2. The UE is configured with preconfigured UL resources for small data transmission.

[0278] 3. The AI 'x' is indicated by higher layers (e.g. NAS layer). Alternatively, the AI 'x' is set or selected by lower layers (e.g. AS layer).

[0279] 4. If all the above conditions 1 to 3 are met: If the data can be fully transmitted by the current preconfigured resources, the access attempt is considered allowed. Otherwise, if the data cannot be fully transmitted by the current preconfigured resources, the access attempt is considered not allowed.

[0280] Case C

[0281] 1. A new access identity 'x' is defined for UEs in RRC inactive or idle state capable of small data transmission, where pre-defined UL resources are used for small data transmission.

[0282] 2. The AI 'x' is indicated by higher layers (e.g. NAS layer). Alternatively, the AI 'x' is set or selected by lower layers (e.g. AS layer).

[0283] 3. A bitmap of the AI 'x' is included in the network broadcast message.

[0284] 4. If all the above conditions 1 to 3 are met: If the corresponding bit of the AI 'x' (which can be included in uac-BarringForAccessIdentity included in "UAC barring parameters") is set to zero, the access attempt is considered allowed. Otherwise, if the corresponding bit of the AI 'x' is not set to zero, the access attempt is considered not allowed.

[0285] In some further embodiments, the UE allows the access attempt directly based on the UI's AI and traffic. There can be the following cases.

[0286] Case X

[0287] 1. A new access identity 'x' is defined for a small data transmission capable UE in RRC Inactive or Idle state.

[0288] 2. The UE is configured with preconfigured UL resources for small data transmission.

[0289] 3. The UE is configured with traffic of PDU session, data flow, QoS flow, DRB or LCH which is allowed to be transmitted on preconfigured UL resources as small data transmission.

[0290] 4. If the access attempt is for configured traffic represented by PDU session, data flow, QoS flow, DRB or LCH: AI 'x' can be indicated by higher layer; or AI 'x' can be set or selected by lower layer.

[0291] 5. If all the above conditions 1 to 4 are met, the access attempt is considered to be allowed.

[0292] Case Y

[0293] 1. A new access identity 'x' is defined for a small data transmission capable UE in RRC Inactive or Idle state.

[0294] 2. The UE is configured with preconfigured UL resources for small data transmission.

[0295] 3. The UE is configured with traffic of PDU session, data flow, QoS flow, DRB or LCH which is allowed to be transmitted on preconfigured UL resources as small data transmission.

[0296] 4. If the access attempt is for configured traffic of PDU session, data flow, QoS flow, DRB or LCH: AI 'x' can be indicated by higher layer; or AI 'x' can be set or selected by lower layer.

[0297] 5. There can be the following sub-cases:

[0298] 5.1. If all the above conditions 1 to 4 are met: if the corresponding bit of AI 'x' in uac-BarringForAccessIdentity contained in "UAC barring parameters" is set to zero, the access attempt is considered to be allowed.

[0299] 5.2. If all the above conditions 1 to 4 are met: if the data can be fully transmitted by the current preconfigured UL resources, the access attempt is considered to be allowed; otherwise, if the data cannot be fully transmitted by the current preconfigured UL resources, the access attempt is considered to be not allowed.

[0300] 5.3. If all of the above conditions 1 to 3 are met: if the corresponding bit of AI 'x' in uac-BarringForAccessIdentity included in the "UAC barring parameters" is set to zero, and it is determined whether the data can be fully transmitted by the current preconfigured UL resource; if the data can be fully transmitted by the current preconfigured UL resource, then the access attempt is considered to be allowed; otherwise, if the data cannot be fully transmitted by the current preconfigured UL resource, then the access attempt is considered to be not allowed.

[0301] Referring back to Figure 2 In an embodiment, during determining whether to allow the access attempt, if the AI of the UE is obtained and the AI of the UE indicates an access identity 'x', the UE allows the access attempt of the UE. The access identity 'x' indicates that the UE is configured to transmit small-scale and infrequent data transmission in one of the RRC inactive state and the RRC idle state. The access identity is indicated by a higher layer of the UE or selected by a lower layer of the UE. A bitmap of the access identity can be included in a broadcast message.

[0302] In a further embodiment, during determining whether to allow the access attempt, if the AI of the UE is obtained and the AI of the UE indicates an access identity 'x', the UE determines whether the UE is configured with traffic that allows transmission as small data transmission on the preconfigured UL resource; and if the UE determines that the UE is configured with the traffic, the UE allows the access attempt of the UE. If the UE determines that the UE is not configured with the traffic, the UE performs an access barring check according to a broadcast message received from the network or the BS. For example, the traffic can be represented by one or more of a PDU session, a data flow, a QoS flow, a DRB, and a LCH.

[0303] In another embodiment, during determining whether to allow the access attempt, if the AI of the UE is obtained and the AI of the UE indicates an access identity 'x', it is determined whether a bit in the access control configuration information is set to zero, where the bit corresponds to the AI of the UE. If the UE determines that the bit is set to zero, the UE further determines whether the data to be transmitted by the UE can be fully transmitted on the preconfigured UL resource; if the UE determines that the data to be transmitted by the UE can be fully transmitted on the preconfigured UL resource, the UE allows the access attempt; if the UE determines that the data to be transmitted by the UE cannot be fully transmitted on the preconfigured UL resource, the UE further determines whether the data to be transmitted by the UE will be dropped; if the UE determines that the data to be transmitted by the UE will not be dropped, the UE allows the access attempt.

[0304] Figure 3 FIG. 1 is a flowchart illustrating a method for transmitting access control configuration information according to some embodiments of the present application.

[0305] Figure 3 The method illustrated in FIG. 1 can be performed by a network or a BS (e.g., as illustrated in FIG. 2).Figure 1 The BS 102) is implemented. Although described with respect to a network or a BS, it should be understood that other devices can be configured to perform methods similar to Figure 3 the methods of the methods of

[0306] As shown in Figure 3 , at operation 301, the BS transmits an indicator indicating support for receiving small data transmissions from a UE (e.g., the UE 101 as illustrated and described in Figure 1 ) and transmitting small data transmissions to the UE. The UE can be configured with preconfigured UL resources. The UE is configured to support small data transmissions in one of an RRC inactive state and an RRC idle state. At operation 302, the BS transmits access control configuration information.

[0307] For example, the access control configuration information can be transmitted through a broadcast message or through RRC signaling. The access control configuration information can include a set of access control parameters, which can include one or more barring information set entries.

[0308] As all the details described in the embodiments as illustrated and described in Figure 1 , 2 and 4, especially those related to specific operations of access control for small data transmissions, apply to the embodiments as illustrated and described in Figure 3 . Furthermore, all the details described in the embodiments of Figure 3 apply to all the embodiments of Figure 1 , 2 and 4.

[0309] Figure 4 An apparatus in accordance with some embodiments of the present application is illustrated. In some embodiments of the present disclosure, the apparatus 400 can be the UE 101 as illustrated and described in Figure 1 or other embodiments of the present application. In some other embodiments of the present disclosure, the apparatus 400 can be the BS 102 as illustrated and described in Figure 1 or other embodiments of the present application.

[0310] As all the details described in the embodiments as illustrated and described in Figure 4As shown in FIG. 4, apparatus 400 can include receiver 401, transmitter 403, processor 405, and non-transitory computer-readable medium 407. Non-transitory computer- readable medium 407 has computer-executable instructions stored therein. Processor 405 is configured to couple to non-transitory computer-readable medium 407, receiver 401, and transmitter 403. It is contemplated that, in some other embodiments of the present application, apparatus 400 can include more computer-readable media, receivers, transmitters, and processors, as actual needs can dictate. In some embodiments of the present application, receiver 401 and transmitter 403 are integrated into a single device, such as a transceiver. In certain embodiments, apparatus 400 can further include input devices, memory, and / or other components.

[0311] In some embodiments of the present application, non-transitory computer- readable medium 407 can have stored thereon computer-executable instructions to cause a processor to implement a method in accordance with embodiments of the present application.

[0312] Those skilled in the art will understand that the terms used in the present application are for the purpose of describing the present application and its principles and are not intended to limit the present application to a specific embodiment.

[0313] One of ordinary skill in the art will appreciate that the steps of the methods described in connection with the aspects disclosed herein can be embodied directly in hardware, in software executed by a processor, or in a combination of the two. Software modules can reside in RAM, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Furthermore, in some aspects, the steps of the methods can be embodied as one or any combination or set of codes and / or instructions residing in a non-transitory computer-readable medium which can be incorporated into a computer program product.

[0314] Although the present disclosure has been described with reference to specific embodiments, it is evident that many alternatives, modifications and variations can be apparent to those skilled in the art. For instance, various components of the embodiments can be interchanged, added, or removed in other embodiments. In addition, not all of the elements of each figure are essential for operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments will be able to implement and use the teachings of the present disclosure by simply employing the essential elements of the independent claims. Accordingly, the embodiments of the present disclosure set forth herein are intended to be illustrative, not limiting. Various changes can be made without departing from the spirit and scope of the present disclosure.

[0315] In this document, the terms“comprises”,“comprising”, or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by“comprises a”,“has”,“has a”, or“has one of” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus including the recited element. Additionally, the term“another” is defined as at least a second or more. The terms“including”,“having” and variants thereof, as used in this document, are defined as“comprising”.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the UE to: receive access control configuration information, the access control configuration information including a set of unified access control (UAC) parameters, wherein the UE is configured with preconfigured uplink (UL) resources and supports small data transmission on the preconfigured UL resources when the UE is in one or more of a radio resource control (RRC) inactive state or an RRC idle state; and perform access control of the UE based on the access control configuration information, wherein to perform the access control, the at least one processor is operable to cause the UE to: obtain information related to the UE in an indication of a non-access stratum (NAS) layer, the information related to the UE including one or more access categories (ACs) and one or more access identities (AIs) of the UE; and determine whether an access attempt of the UE is allowed based on the information related to the UE.

2. The UE of claim 1, wherein the set of UAC parameters includes one or more barring information set entries, and wherein the barring information set entry includes one or more of: information about whether a first access attempt of the UE is allowed for each access identity (AI) of the UE; a probability that the first access attempt of the UE is allowed during an access barring check; or a minimum time before a second access attempt of the UE is to be performed after the first access attempt of the UE is barred during an access barring check, wherein the second access attempt and the first access attempt are for a same AC.

3. The UE of claim 2, wherein the probability that the first access attempt of the UE is allowed is 100%.

4. The UE of claim 1, wherein if the small data transmission is triggered by traffic allowed to transmit on the preconfigured UL resources, the at least one processor is further operable to cause the UE to: select a barring information set entry in the set of UAC parameters; and perform the access control of the UE based on the selected barring information set entry.

5. The UE of claim 4, wherein the traffic is represented by one or more of a packet data unit (PDU) session, a data flow, a data radio carrier (DRB), a logical channel (LCH), or a quality of service (QoS) flow.

6. The UE of claim 1, wherein the at least one processor is operable to cause the UE to: determine whether the access attempt is associated with the small data transmission based at least in part on determining that the access attempt of the UE is allowed; transmit the small data transmission on the preconfigured UL resources based at least in part on determining that the access attempt is associated with the small data transmission; and not transmit a transmission on the preconfigured UL resources based at least in part on determining that the access attempt is not associated with the small data transmission. ​ 7. The UE of claim 1, wherein, to determine whether to allow the access attempt by the UE, the at least one processor is operable to cause the UE to: obtain, among the one or more ACs, an AC representing an access configuration associated with the small data transmission; and allow the access attempt by the UE.

8. The UE of claim 1, wherein, to determine whether to allow the access attempt by the UE, the at least one processor is operable to cause the UE to: determine whether data to be transmitted by the UE can be completely transmitted on the preconfigured UL resources based, at least in part, on obtaining, among the one or more ACs, an AC representing an access configuration associated with the small data transmission; allow the access attempt by the UE based, at least in part, on determining that the data to be transmitted by the UE can be completely transmitted on the preconfigured UL resources; determine whether the data to be transmitted by the UE is to be dropped based, at least in part, on determining that the data to be transmitted by the UE cannot be completely transmitted on the preconfigured UL resources; and allow the access attempt by the UE based, at least in part, on determining that the data to be transmitted by the UE is not to be dropped.

9. The UE of claim 1, wherein the at least one processor is operable to cause the UE to: determine whether a bit corresponding to an AI in the access control configuration information is set to zero based, at least in part, on obtaining the AI among the one or more AIs; and allow the access attempt by the UE based, at least in part, on determining that the bit is set to zero.

10. A method performed by a user equipment (UE), the method comprising: receiving access control configuration information, the access control configuration information including a set of unified access control (UAC) parameters, wherein the UE is configured with preconfigured uplink (UL) resources and supports small data transmission on the preconfigured UL resources when the UE is in one or more of a radio resource control (RRC) inactive state or an RRC idle state; and performing access control for the UE based on the access control configuration information, wherein performing the access control comprises: obtaining information related to the UE in an indication of a non-access stratum (NAS) layer, the information related to the UE including one or more access categories (ACs) and one or more access identities (AIs) of the UE; and determining whether to allow an access attempt by the UE based on the information related to the UE.

11. The method of claim 10, wherein the set of UAC parameters includes one or more barring information set entries, and wherein the barring information set entries comprise one or more of: information regarding whether a first access attempt by the UE is allowed for each access identity (AI) of the UE; a probability of allowing the first access attempt by the UE during an access barring check; or ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ a minimum time after the first access attempt by the UE is barred during an access barring check before a second access attempt by the UE is to be performed, wherein the second access attempt and the first access attempt are for a same access category (AC).

12. The method of claim 11, wherein the probability of allowing the first access attempt by the UE is 100%.

13. The method of claim 10, wherein if the small data transmission is triggered by traffic allowed to transmit on the preconfigured UL resource, the method further comprises: selecting a barring information set entry in the set of UAC parameters; and performing the access control for the UE based on the selected barring information set entry.

14. The method of claim 13, wherein the traffic is represented by at least one of: a packet data unit (PDU) session, a data flow, a data radio carrier (DRB), a logical channel (LCH), or a quality of service (QoS) flow.

15. The method of claim 10, further comprising: determining whether the access attempt is associated with the small data transmission based at least in part on determining that the access attempt by the UE is allowed; transmitting the small data transmission on the preconfigured UL resource based at least in part on determining that the access attempt is associated with the small data transmission; and not transmitting a transmission on the preconfigured UL resource based at least in part on determining that the access attempt is not associated with the small data transmission.

16. The method of claim 10, wherein determining whether to allow the access attempt by the UE comprises: obtaining an AC in the one or more ACs that represents an access configuration associated with the small data transmission; and allowing the access attempt by the UE.

17. The method of claim 10, wherein determining whether to allow the access attempt by the UE comprises: determining whether data to be transmitted by the UE can be fully transmitted on the preconfigured UL resource based at least in part on obtaining an AC in the one or more ACs that represents an access configuration associated with the small data transmission; allowing the access attempt by the UE based at least in part on determining that the data to be transmitted by the UE can be fully transmitted on the preconfigured UL resource; determining whether the data to be transmitted by the UE will be discarded based at least in part on determining that the data to be transmitted by the UE cannot be fully transmitted on the preconfigured UL resource; and allowing the access attempt by the UE based at least in part on determining that the data to be transmitted by the UE will not be discarded.

18. The method of claim 10, further comprising: determining whether a bit corresponding to an AI in the access control configuration information is set to zero based at least in part on obtaining the AI in the one or more AIs; and allowing the access attempt by the UE based at least in part on determining that the bit is set to zero.

19. A processor for a user equipment (UE) for wireless communication, comprising: ​ ​ ​ at least one controller coupled with the at least one memory and operable to cause the processor to: receive access control configuration information, the access control configuration information including a set of unified access control (UAC) parameters, wherein the UE is configured with preconfigured uplink (UL) resources and supports small data transmission on the preconfigured UL resources when the UE is in one or more of a radio resource control (RRC) inactive state or an RRC idle state; and perform access control for the UE based on the access control configuration information, wherein to perform the access control, the at least one is operable to cause the processor to: obtain information related to the UE in an indication of a non-access stratum (NAS) layer, the information related to the UE including one or more access categories (ACs) and one or more access identities (AIs) of the UE; and determine whether to allow an access attempt by the UE based on the information related to the UE.

20. A base station for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and operable to cause the base station to: transmit an indicator including an indication to support receiving a first small data transmission from a user equipment (UE) and transmitting a second small data transmission to the UE, wherein the UE is in one of a radio resource control (RRC) inactive state or an RRC idle state; and transmit access control configuration information to the UE, the access control configuration information including a set of unified access control (UAC) parameters, the set of UAC parameters including one or more access categories (ACs) and one or more access identities (AIs) of the UE, and the access control configuration information including information indicating whether an access attempt by the UE is allowed for each AI of the UE.

21. The base station of claim 20, wherein the set of UAC parameters includes one or more barring information set entries, and the barring information set entries include one or more of: information regarding whether the access attempt by the UE is allowed for each AI of the UE; a probability of allowing the access attempt by the UE during an access barring check; or a minimum time before a second access attempt by the UE is to be performed before the access attempt by the UE is barred during an access barring check, wherein the second access attempt and the access attempt are for a same AC.

22. The base station of claim 21, wherein the probability of allowing the access attempt by the UE is 100%.

23. A method performed by a base station, the method comprising: transmitting an indicator including an indication to support receiving a first small data transmission from a user equipment (UE) and transmitting a second small data transmission to the UE, wherein the UE is in one of a radio resource control (RRC) inactive state or an RRC idle state; and transmitting access control configuration information to the UE, the access control configuration information including a set of unified access control (UAC) parameters, the set of UAC parameters including one or more access categories (ACs) and one or more access identities (AIs) of the UE, and the access control configuration information including information indicating whether an access attempt by the UE is allowed for each AI of the UE. Transmitting access control configuration information to the UE, the access control configuration information including a set of unified access control (UAC) parameters, the set of UAC parameters including one or more access categories (ACs) and one or more access identities (AIs) for the UE, and the access control configuration information including information indicating whether access attempts by the UE are allowed for each AI of the UE.

Images