GB2641745A

GB2641745A - Enhanced random access protocols

Info

Publication number: GB2641745A
Application number: GB2408300.8A
Authority: GB
Inventors: Michalopoulos Diomidis; Keshavamurthy Prajwal; Sahin Taylan; Karimidehkordi Ali; Mangalvedhe Nitin
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2024-06-11
Filing date: 2024-06-11
Publication date: 2025-12-17
Also published as: WO2025257703A1; GB202408300D0

Abstract

A method includes receiving by a user device from a network node, information for selecting a random access class for the device, wherein each random access class is associated with one or more random access parameters, selecting the random access class based on the information, and transmitting uplink data to the network node, based on the one or more random access parameters associated with the selected random access class. Selection may comprise comparing one or more conditions or status of the user device with selection criteria and selecting according to the criteria being met. The selection criteria include measurement information type, a number of random access contention failures, a level of reference signal receive power RSRP or quality RSRQ, a QoS requirement associated with uplink data, battery power level or priority information of uplink data.

Description

[0001] ENHANCED RANDOM ACCESS PROTOCOLS

[0002] TECHNICAL FIELD

[0003] This description relates to wireless communications.

[0004] BACKGROUND

[0005] A communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.

[0006] An example of a cellular communication system is an architecture that is being standardized by the 3rd Generation Partnership Project (3GPP). EUTRA (evolved Universal Mobile Telecommunications System Terrestrial Radio Access) is the air interface of 3GPP's Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, base stations or access points (APs), which are referred to as enhanced Node B (eNBs), provide wireless access within a coverage area or cell. In LTE, mobile devices, or mobile stations are referred to as user equipments (UE). LIE has included a number of improvements or developments.

[0007] [00041 5G New Radio (NR) development is part of a continued mobile broadband evolution process to meet the requirements of 5G, similar to earlier evolution of 3G and 4G wireless networks. In addition, 5G is also targeted at the new emerging use cases in addition to mobile broadband. A goal of 5G is to provide significant improvement in wireless performance, which may include new levels of data rate, latency, reliability, and security. 5G NR may also scale to efficiently connect the massive Internet of Things (IoT) and may offer new types of mission-critical services. For example, ultra-reliable and low-latency communications (URLLC) devices may require high reliability and very low latency. 6G and other networks are also being developed.

[0008] SUMMARY

[0009] [00051 In some aspects, the techniques described herein relate to an apparatus including: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a network node, information for selecting a random access class for the apparatus, wherein each random access class is associated with one or more random access parameters; select the random access class based on the information; and transmit uplink data to the network node, based on the one or more random access parameters associated with the selected random access class.

[0010] In some aspects, the techniques described herein relate to a method including: receiving, by a device from a network node, information for selecting a random access class for the device, wherein each random access class is associated with one or more random access parameters; selecting the random access class based on the information; and transmitting uplink data to the network node, based on the one or more random access parameters associated with the selected random access class.

[0011] Other example embodiments are provided or described for each of the example methods, including: means for performing any of the example methods; a non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform any of the example methods; and an apparatus including at least one processor, and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform any of the example methods.

[0012] The details of one or more examples of embodiments are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.

[0013] BRIEF DESCRIPTION OF THE DRAWINGS

[0014] FIG. 1 is a block diagram of a wireless network.

[0015] FIG. 2 is a diagram illustrating an example random access procedure.

[0016] FIG. 3 is a diagram illustrating an aspect of an example embodiment.

[0017] FIG. 4 is a diagram illustrating an aspect of another example embodiment.

[0018] FIG. 5 is a flow chart illustrating operation of an apparatus (e.g., which may be a UE or user device, or other apparatus) according to an example embodiment.

[0019] FIG. 6 is a block diagram of a wireless station or node (e.g., network node (such as gNB), user node or UE, relay node, or other node).

[0020] DETAILED DESCRIPTION

[0021] It shall be understood that although the terms "first," "second,"..., etc. in front of noun(s) and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun(s). For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the listed terms.

[0022] As used herein, unless stated explicitly, performing a step "in response to A" does not indicate that the step is performed immediately after "A" occurs and one or more intervening steps may be included.

[0023] FIG. 1 is a block diagram of a wireless network 130. In the wireless network of FIG. 1, user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs), user equipment (UEs) or IoT devices, may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB), a gNB or a network node. The terms user device and user equipment (UE) may be used interchangeably. A BS may also include or may be referred to as a RAN (radio access network) node, and may include a portion of a BS or a portion of a RAN node, such as e.g., such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS or split gNB. At least part of the functionalities of a BS (e.g., access point (AP), base station (BS) or (e)Node B (eNB), gNB, RAN node) may also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head. BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices (or UEs) 131, 132, 133 and 135. Although only four user devices (or UEs) are shown as being connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to a core network 150 via a S1 interface 151. This is merely one simple example of a wireless network, and others may be used.

[0024] A base station (e.g., such as BS 134) is an example of a radio access network (RAN) node within a wireless network. A BS (or a RAN node) may be or may include (or may alternatively be referred to as), e.g., an access point (AP), a gNB, an eNB, or portion thereof (such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS or split gNB), or other network node.

[0025] Some functionalities of the communication network may be carried out, at least partly, in a central/centralized unit, CU, (e.g., server, host or node) operationally coupled to distributed unit, DU, (e.g., a radio head/node). Thus, 5G networks architecture may be based on a so-called CU-DU split. The gNB-CU (central node) may control a plurality of spatially separated gNB-DUs, acting at least as transmit/receive (Tx/Rx) nodes. In some embodiments, however, the gNB-DUs (also called DU) may comprise e.g., a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the gNB-CU (also called a CU) may comprise the layers above RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) and an internet protocol (IP) layers. Other functional splits are possible too.

[0026] According to an illustrative example, a BS node (e.g., BS, eNB, gNB, CU/DU, ...) or a radio access network (RAN) may be part of a mobile telecommunication system. A RAN (radio access network) may include one or more BSs or RAN nodes that implement a radio access technology, e.g., to allow one or more UEs to have access to a network or core network (CN). Thus, for example, the RAN (RAN nodes, such as BSs or gNBs) may reside between one or more user devices or UEs and a core network.

[0027] According to an example embodiment, each RAN node (e.g., BS, eNB, gNB, CU/DU, ...) or BS may provide one or more wireless communication services for one or more UEs or user devices, e.g., to allow the UEs to have wireless access to a network, via the RAN node. Each RAN node or BS may perform or provide wireless communication services, e.g., such as allowing UEs or user devices to establish a wireless connection to the RAN node, and sending data to and/or receiving data from one or more of the UEs. For example, after establishing a connection to a UE, a RAN node or network node (e.g., BS, eNB, gNB, CU/DU, ...) may forward data to the UE that is received from a network or the core network, and/or forward data received from the UE to the network or core network. RAN nodes or network nodes (e.g., BS, eNB, gNB, CU/DU, ...) may perform a wide variety of other wireless functions or services, e.g., such as broadcasting control information (e.g., such as system information or on-demand system information) to UEs, paging UEs when there is data to be delivered to the UE, assisting in handover of a UE between cells, scheduling of resources for uplink data transmission from the UE(s) and downlink data transmission to UE(s), sending control information to configure one or more UEs, and the like. These are a few examples of one or more functions that a RAN node or BS may perform.

[0028] A user device or user node (user terminal, user equipment (UE), mobile terminal, handheld wireless device, etc.) may refer to a portable computing device that includes wireless mobile communication devices operating either with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, a vehicle, a sensor, an IoT device, and a multimedia device, as examples, or any other wireless device. It should be appreciated that a user device may also be (or may include) a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. Also, a user node may include a user equipment (UE), a user device, a user terminal, a mobile terminal, a mobile station, a mobile node, a subscriber device, a subscriber node, a subscriber terminal, or other user node. For example, a user node may be used for wireless communications with one or more network nodes (e.g., gNB, eNB, BS, AP, CU, DU, CU/DU) and/or with one or more other user nodes, regardless of the technology or radio access technology (RAT). In LTE (as an illustrative example), core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility/handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks. Other types of wireless networks, such as 5G (which may be referred to as New Radio (NR)) may also include a core network.

[0029] [00221 In addition, the techniques described herein may be applied to various types of user devices or data service types, or may apply to user devices that may have multiple applications running thereon that may be of different data service types. New Radio (SG) development may support a number of different applications or a number of different data service types, such as for example: machine type communications (MTC), enhanced machine type communication (eMTC), Internet of Things (IoT), and/or narrow-band loT user devices, enhanced mobile broadband (eMBB), and ultra-reliable and low-latency communications (URLLC). Many of these new 5G (NR) -related applications may require generally higher performance than previous wireless networks.

[0030] IoT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices. For example, many sensor type applications or devices may monitor a physical condition or a status and may send a report to a server or other network device, e.g., when an event occurs. Machine Type Communications (MTC, or Machine to Machine communications) may, for example, be characterized by fully automatic data generation, exchange, processing and actuation among intelligent machines, with or without intervention of humans. Enhanced mobile broadband (eMBB) may support much higher data rates than currently available in LTE.

[0031] [00241 Ultra-reliable and low-latency communications (URLLC) is a new data service type, or new usage scenario, which may be supported for New Radio (50) systems. This enables emerging new applications and services, such as industrial automations, autonomous driving, vehicular safety, e-health services, and so on. 3GPP targets in providing connectivity with reliability corresponding to block error rate (BLER) of 10-5 and up to 1 ms U-Plane (user/data plane) latency, by way of illustrative example. Thus, for example, URLLC user devices/UEs may require a significantly lower block error rate than other types of user devices/UEs as well as low latency (with or without requirement for simultaneous high reliability). Thus, for example, a URLLC UE (or URLLC application on a UE) may require much shorter latency, as compared to an eMBB UE (or an eMBB application running on a UE).

[0032] [00251 The techniques described herein may be applied to a wide variety of wireless technologies or wireless networks, such as 5G (New Radio (NR)), cmWave, and/or mmWave band networks, IoT, MTC, eMTC, eMBB, URLLC, 6G, etc., or any other wireless network or wireless technology. These example networks, technologies or data service types are provided only as illustrative examples.

[0033] [00261 A user device (or UE) may measure various signals and may transmit one or more measurement reports to the network. For example, a UE may measure reference signals received from one or more network nodes (e.g., gNBs or DUs), including channel state information-reference signals (CSI-RSs) and/or synchronization signal block (SSB) reference signals, demodulation references signals, and/or other reference signals. Based on received reference signals, the UE may measure various signal parameters, e.g., such as reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), received signal strength indicator (RSSI), or other signal parameter.

[0034] The PHY (physical) layer may refer to layer 1 (1_,1) and MAC (media access control) may refer to layer 2 (L2). RSRP, RSRQ, SINR and RSSI are signal quantities measured at layer 1 (L1). The UE may send LI measurement reports (e.g., CSI-RS reports, which include measurements of one or more signal parameters for one or more cells) to a gNB, source DU or serving cell. These LI measurement reports may be sent periodically, for example, or aperiodically. Ll/L2 measurement reports may include no averaging or filtering of measurement values or may include less averaging or filtering than what is performed for L3 measurement reports. Ll (or Ll/L2) measurement reports may be transmitted by a UE to a serving network node or source DU and may cause the network node to trigger or initiate a L1/L2 triggered mobility (LTM) handover of the UE to another cell. LI measurements (e.g., RSRP RSRQ, RSSI) may be provided or reported periodically to the DU (MAC/PHY).

[0035] FIG. 2 is a diagram illustrating an example random access (RA) procedure. In an example, a four-step random access procedure may include the following. At step 1 of FIG. 2, the UE 210 may transmit to a gNB 220 a preamble, e.g., in a physical random-access channel (PRACH) (e.g., message 1 or msg 1). In case of non-successful RA procedure, as this is determined at a later phase (step 4) of the RA procedure, the preamble transmission may be carried out repeatedly with stepwise increased transmit power. At step 2, the gNB 220 may transmit to the UE 210, a random-access response (RAR) (e.g., message 2 or msg 2) indicating resource parameters needed for the device transmitting an UL message to the network. In an example, the gNB 220 (in the RAR message or msg 2) may provide a time-alignment command to the UE 210 to adjust the transmission timing of the UE 210 based on the timing of the received preamble. In an example, the gNB 220 (in the RAR message or msg 2) may provide an UL grant for the UL message. At step 3 and step 4, the UE 210 and the gNB 220 may exchange messages (uplink message 3 or msg 3 and subsequent downlink message 4 or msg 4) with the aim of resolving potential collisions, also referred to as contention resolution. In an example, the contention or collision may occur due to simultaneous transmission from multiple UEs 210.

[0036] In an example, when the need for data (or uplink (UL) data) transfer arises, a radio resource control (RRC) connection may be established between the UE and a gNB. To transfer the data, the established RRC connection between the UE and the gNB may transition or change to a connected state and data transfer subsequently may take place.

[0037] Once the data has been transferred, the UE at some point in time, may return to a RRC idle state or RRC inactive state. Limiting data transfer to the connected state only is a good approach for larger amounts of data as transmission may make use of the UE's unique capabilities, something which may be possible in connected state only. Moving from RRC idle to RRC connected state may require signaling of configuration parameters and establishing a connection with the core network. The amount of signaling for this may be non-negligible and the RRC inactive state is therefore introduced in NR. The RRC inactive state is efficient due to a reduced overhead as the configuration information and the connection to the core network are maintained at the network node when a UE transitions back and forth between RRC inactive and RRC connected states. However, for transmission of small payloads (e.g., data of smaller size, or small data transmission (SDT)), which is common in, but not limited to, IoT scenarios, the signaling overhead related to a UE transitioning to RRC connected state is non-negligible compared to the amount of user data to be transmitted. Therefore, 3GPP technologies introduced support for small data transmission (SDT), which is a procedure allowing (uplink) data and/or signaling transmission while remaining in the RRC inactive state, that is, without the UE transitioning from the RRC inactive to the RRC connected state.

[0038] 100301 In an example embodiment, the SDT may be performed within a random access (RA) procedure, e.g., a SDT transmission performed within a random access based physical uplink shared channel (PUSCH) transmission. For the random-access-based PUSCH transmission, user data may be transmitted as part of message 3 (msg 3 or msg A) for four-step and two-step random access, respectively. In the case of SDT with four-step random access, upon the UE transmitting the selected random access (or RACH) preamble as part of message 1 (or msgl), the network or the gNB may respond with msg 2 (also known as random-access response, RAR) as depicted in FIG. 2. Compared to regular random access (e.g., where SDT is not performed), the size of the uplink resources allocated by msg 2 and the associated transport-block size may be larger for SDT to accommodate (some of) the user data as part of msg 3. Once msg 3, including the user data, has been transmitted by the UE to the gNB, the UE does not know whether there was an uplink collision. Therefore, similar to regular random access, the device needs to receive msg 4 from the gNB for contention resolution. Msg 4 includes an acknowledgment message to the UE, indicating successful decoding of the UL message at msg 3, as a result the UE may determine that the contention resolution was successful. If the contention resolution is successful, the device determines/knows whether the (first part of) the user data is properly received by the network or the gNB.

[0039] 100311 Note, for example, that multiple UEs may attempt random access to a gNB at the same time. If a UE receives a contention resolution message at step 4 indicating its cell-radio network temporary identifier (RNTI), this informs the UE that its random access attempt to the gNB was successful. Also, for example, if the UE does not receive a contention resolution message at step 4 from the gNB that includes its RNTI (e.g., within a specific time period), that is the UE does not receive timely acknowledgment of successful decoding, then this informs the UE that its random access attempt has failed.

[0040] [00321 In an example embodiment, the UE may autonomously trigger UL data transmissions (e.g., in a periodic manner or aperiodic manner). In an example, the UE may be triggered by the network to transmit UL data or UL information. For example, the UE may be an loT sensor that may be triggered by the network to provide collected measurements, measurement information, measurement data, and/or the like, to the gNB. Or, for example, the UE or IoT device may be configured to periodically report some collected data to the network. In an example, the UE may be a low power IoT device, low power wide area (LPWA) device, a tracking device, a factory loT device, and/or the like.

[0041] [00331 In existing technologies, a collision or contention may occur when a large number of UEs or many UEs (or IoT devices, sensors, and/or the like) perform RA procedure (simultaneously) with a gNB to transmit UL data or to perform a SDT procedure. In other words, when a large number of UEs perform RA procedure at the same time, a collision or a contention may occur. For example, the collision, contention, conflict and/or the like may occur due to simultaneous transmission from multiple UEs. Therefore, performing the SDT procedure while in RRC inactive state may be more efficient when a probability of contention or collision is reduced thereby reducing the signalling overhead incurred due to repetition of RA procedure by the UEs. Therefore, when a large number of UEs (or IoT devices) perform RA at the same time, frequent collisions, or contentions may occur that may lead to additional signalling between the UE and the gNB, resulting in an inefficient use of resources.

[0042] [00341 Therefore, a technique to reduce the probability of contention and/or collision during simultaneous random access of the large number of UEs may be advantageous to improve battery performance of the UE, and to enhance signalling efficiency and network resource utilization.

[0043] According to an example embodiment, a plurality of random access classes may be provided or may be available, where each random access class may be associated with a plurality of random access parameters (e.g., values of random access parameter, to be used by a UE for performing random access). For example, each random access class may be associated with a plurality of random access parameters, such as one or more of: a scaling factor indicating an initial transmit power when performing a random access procedure; a power ramping parameter indicating a power increase value; a backoff time parameter indicating a wait time before retransmission of a random access message; a random access configuration index; or a random access preamble index. Each random access class may be identified by or associated with a random access class identifier (or random access class ID). By having different values of one or more of the random access parameters of these random access classes, random accesses may be prioritized. As an example, a random access class having a lower value for backoff time may typically result in quicker or more frequent random access attempts after a collision.

[0044] 100361 In some cases, a UE may be assigned a random access class by the gNB, thereby assigning a set of random access parameters to be used by the UE for random access. However, there may be, for example, various status (e.g., UE status) or conditions (e.g., local network conditions) that may be known to the UE (and which may or may not be known by the network node/gNB). These status (e.g., UE status) or conditions (e.g., network conditions) may change over time. And, according to an example embodiment, based on (e.g., current or updated) values of these UE status or conditions and/or based on other information, it may be desirable to allow the UE to select a random access class (e.g., which may include the UE selecting an updated or new random access class) to be used by the UE for random access.

[0045] [00371 For example, some status or conditions (and which may be used by the UE to select a random access class) may include, e.g., a number of random access contention failures with respect to the gNB or network node, a level or range of reference signal received power (RSRP), or a level or range of reference signal received quality (RSRQ) of reference signals received from the network node, a quality of service (QoS) class or requirement associated with transmission of the uplink data from the UE to the network node; a battery power level of the UE, priority information associated with the transmission of the uplink data; and/or a status of buffer allocated for the transmission of the uplink data (e.g., a level of fullness of a data buffer, or indication of an amount of uplink data for transmission).

[0046] Also, according to an example embodiment, it may be desirable for the network or gNB to configure or control, at least in some respects, the manner in which the UE will select a random access class out of a plurality of random access classes. Therefore, a UE may receive, from a network node or gNB, information (e.g., such as random access class selection criteria) for selecting a random access class for the UE. The UE may then select a random access class (or a random access class ID) based on this received information. Further details and examples will now be described.

[0047] Example embodiments are directed to enhancements of signalling between the UE and the gNB (e.g., a NG-RAN node, an eNB, a network node, a base station, and/or the like) to assist the UE in selecting or reselecting a (or selecting an updated) random access (RA) class. The UE may then determine the associated random access parameters associated with the random access class to transmit uplink data while achieving a lower probability of contention, for example.

[0048] In other words, example embodiments are directed to improved techniques or methods where the UE(s) or the IoT devices may be assigned a set of random access parameters. The random access parameters may be employed by the UE(s) when performing random access (RA) with the network node or the gNB. In an example, the UE(s) may be configured with an RA class association information. The RA class association information may be determined by the network and transmitted to the UE. The RA class association information may include at least one or more of a random access class identifier (class ID) or a set of random access class IDs, an association between a random access class and one or more random access parameters, a mapping information that maps one or more random access classes to an identifier of the UE (or UE ID), a mapping information that maps one or more random access classes to a type of the uplink data, and/or the like. For example, the set of class IDs may include a set of RA class IDs that is associated with the UE (or configured in the UE e.g., by pre-configuration or network configuration). As an example, any mapping or association such as the mapping or association of RA class IDs to the UE ID may be determined by the network such as a gNB, a RAN node or a core network node. In an example, the UE may be associated with one or more (such as a plurality of or multiple) RA classes (or RA class LDs), e.g., when the UE may transmit different types of UL data, different types of measurement information, different types of traffic, and/or the like. For example, the UEs may be multipurpose IoT devices deployed in agricultural applications or fields, where typically multiple types of data are to be collected and transmitted to the network.

[0049] Furthermore, example embodiments are directed to further enhancements of techniques or methods where the UE receives RA class (e.g., RA class ID) selection criteria from the network. In an example embodiment, the UE may determine to perform the random access based on the RA parameters associated with a selected RA class or selected RA class ID wherein the selection (by the UE) of the RA class ID may be based on the one or more selection criteria. In an example, the one or more selection criteria may be provided by the network node or the gNB. In an example, the criteria may be preconfigured at the UE or provided by the network node or the gNB. The selection criteria may include one or more conditions wherein the UE selects a RA class when a corresponding condition(s) is met, then the UE may select the RA parameters associated with the RA class (or the RA class ID). The UE may perform the RA procedure based on the selected RA parameters, and then transmit UL data via the RA procedure.

[0050] 100421 In an example, the RA class may be associated with transmission of a predetermined type of the uplink data or a measurement information type. In an example, the RA class may be associated with at least one of: a priority information of a RA request, a priority information of the uplink data, a priority information of the measurement information type.

[0051] FIG. 3 is a diagram illustrating an aspect of an example embodiment. Step 1 of FIG. 3 refers to a registration procedure to register a new loT device, and includes steps 2- 7b. In an example embodiment, the UE may perform a registration procedure with the network and may transmit capability indication to the network. The registration procedure may include transmitting a non-access stratum (NAS) message to the network. In an example, the UE may transmit the NAS message to a core network node such as a mobility management entity (MME) or an access and mobility management function (AMF) of the network. The authentication procedure as shown in step 2, may include receiving an identity request message by the UE from the core network node. The UE may send an identity response message to the core network node as part of step 2. At step 3, the UE may send a capability indication to the core network node. In an example, the capability indication may indicate a capability of the UE to select a random access class, e.g., a capability of the UE to select a random access class of a plurality of random access classes based on information (such as random access selection criteria or conditions) preconfigured at the UE or received by the UE from the network node. The capability indication may include a capability of the UE to transmit small data, type of measurement data that the UE is capable of transmitting, type of data traffic, size of data packets, frequency of measurements and/or UL data transmissions, and/or the like. In an example, the type of measurement data may include environmental sensor-related measurements such as temperature or humidity, or metering information and data types applicable to smart city, smart factory, or intelligent transport applications. In another example, an application function (AF) or application server (AS) may indicate type of measurement data to the core network node. In an example the AF may interact with the core network node via a network exposure function (NEF). At step 4, the core network node (e.g., the AMY) may perform allocation of random access classes to the UE(s). In an example, the AIVIIF may assign an initial RA Class ID to the UE or the IoT device. In another example, at step 4, the AMF may determine at least one of an association between a random access class and one or more random access parameters, a mapping information that maps one or more random access classes to an identifier of the UE, a mapping information that maps one or more random access classes to a type of the uplink data.

[0052] 100441 In an example, the assignment of RA class IDs may be performed initially and dynamically updated by the network (e.g., the core network node). In an example, assignment or reassignment of RA class IDs may be performed by the network node or the core network node based on objectives such as to reduce the likelihood of contention. In an example, assignment or reassignment of RA class IDs may be performed by the core network node based on factors such as device type, types of measurement information, type of traffic, and/or the like.

[0053] In an example, at step 5, information about the (initial) assignment of the RA classes or the RA class 1Ds may be transmitted from the core network node (such as AMF) to the gNB e.g., via N2 interface. In an example, the information about the (initial) assignment of RA class IDs may include at least one of the association between the random access class and one or more random access parameters, the mapping information that maps the one or more random access classes to the identifier of the UE (UE ID), the mapping information that maps the one or more random access classes to the type of the uplink data. In an example, initial assignment of the RA class IDs may include assigning to a UE, a RA class ID or a set of RA class IDs with the highest priority of (successful) random access (e.g., lowest probability of incurring a contention). In an example, the (initial assignment) may be valid for a (current or specific) serving cell of the RAN node or the gNB. For example, a cell switch may trigger a reassignment of the RA classes or the RA class IDs. In an example implementation, each UE ID may be mapped to a RA class ID based on measurement type or traffic type that the UE can generate and transmit. For example, each UE ID may be assigned a set of class IDs, the cardinality of which equals the number of measurement types or traffic types it can generate and transmit. For instance, an loT device may be assigned one class ID for reporting plant progress/growth and another class ID for reporting humidity. As such, multiple UE IDs may be mapped to the same RA class ID if they are associated with the same traffic type or measurement type. In another implementation, the AMF may assign a (new) flag or field to each UE ID that may include class ID (or class ID set) information. The flag or field may be part of the AMF UE NG application protocol (NGAP) ID information element (IE). For example, the AMF UE NGAP ID IE may be implemented, extended or modified to include the class ID (or class ID set) information. In another example, the AMF may employ a (new) NGAP IE that may include an aggregate or a collection of information (mapping) between the registered UE IDs and their assigned RA classes or RA class IDs.

[0054] At step 6 of FIG. 3, the UE may receive from the gNB, information for selecting a random access class for the UE.In an example, the information may include at least one of: an indication of a random access class, an association between a random access class and one or more random access parameters, a mapping information that maps one or more random access classes to an identifier of the device, a mapping information that maps one or more random access classes to a type of the uplink data, and/or the like.

[0055] In an example embodiment, the gNB may transmit the information to the LIE via at least one of: a system information block (SIB), a radio resource control (RRC) message, a RRC reconfiguration message, a configuration update command (CUC) message, a registration accept message, medium access control (MAC) control element (CE) (e.g., MAC-CE), and/or the like.

[0056] Alternatively or additionally, at step 7 of FIG. 3, the UE may receive configuration information of one or more random access parameters per random access class. In an example embodiment, the one or more random access parameters may include at least one of: a scaling factor indicating an initial transmit power when performing a random access procedure, a power ramping parameter indicating a power increase value, a backoff time parameter indicating a wait time of the UE before retransmission of a random access message, a random access configuration index, a random access preamble index, and/or the like. Alternatively or additionally, at step 7b, the UE may receive information of selection criteria for selecting or reselecting a RA class (or RA class ID),In an example, the selecting may include comparing one or more conditions (e.g., network conditions such as RSRP or RSRQ of reference signals from the network node, a number of random access failures with respect to the network node) or status of the UE (e.g., amount and/or type of data to be transmitted, UE battery status, QoS or priority of the application or of the data to be transmitted by the UE, and the like) with the one or more random access class selection criteria, determining, based on the comparing, that the one or more random access class selection criteria are met, and selecting the random access class based on the determining. In an example embodiment, each of the random access classes may be associated with a set of random access class selection criteria, wherein the selecting includes selecting one of the plurality of random access classes for which the associated set of random access class selection criteria is met. In an example implementation, the one or more random access class selection criteria may include at least one of: a measurement information type, a number of random access contention failures of the UE with respect to the gNB, a level or range of reference signal received power (RSRP), or a level or range of reference signal received quality (RSRQ) of reference signals received by the UE from the gNB, a quality of service (QoS) class or requirement associated with transmission of the uplink data by the UE to the gNB, a battery power level of the UE indicating a range of available battery level that corresponds to a given random access class identifier (RA class ID), priority information associated with the transmission of the uplink data by the UE, a status of UE buffer allocated for the transmission of the uplink data, and/or the like. For example, the UE may increment the class ID or decrement the class ID by a certain value if a selection criteria is met. For example, the UE may (initially) determine a first random access class, then selects a second random access class based on the information. In an example, the selecting of the second random access class may include incrementing or decrementing a first random access class identifier of the first random access class to obtain a second random access class identifier identifying the second random access class. In an example, the selection of the different random access class or different RA class ID may be performed based on a result of a random access contention resolution procedure. For example, when during the RA procedure, the message 3 is transmitted by the UE to the gNB, and the message 4 is not received from the gNB before expiry of a timer at the UE, then the UE may determine that a random access failure or random access contention (resolution) failure has occurred for the UE. In an example, if the message 4 is received from the gNB before expiry of the timer at the UE, then the UE may determine that the random access procedure was successful. In an example, the selection of the different random access class or RA class ID may be performed based on one or more criteria including at least one of a measurement information type, a number of random access contention failures with respect to the gNB, a level or range of reference signal received power (RSRP), or a level or range of reference signal received quality (RSRQ) of reference signals received from the gNB, a quality of service (QoS) class or requirement associated with transmission of the uplink data by the UE to the gNB, a battery power level of the UE indicating a range of available battery level that corresponds to a given random access class identifier, priority information associated with the transmission of the uplink data by the UE, a status of the UE buffer allocated for the transmission of the uplink data, and/or the like. An example action may include applying a negative/positive delta (value) on the class ID (e.g., decrease/increase the class ID by a value equal to delta) by one level or multiple levels (by one or multiple class IDs) when some conditions or additional conditions are met. For example, when the current RA class ID is 1 and delta is 5, then by incrementing the RA class ID with delta value of 5, the new RA class ID would be 6. For example, if X number of RA contention failures is experienced by a TJE, then the UE may increase the RA class ID by one level or by one RA class ID (to the next higher RA class ID). If in addition to the X number of RA contention failures, the buffer status/level is above 80% of the UE's buffer capacity then increase the class ID by N additional levels (larger delta) or by N additional or higher RA class IDs, e.g., larger delta, or larger step up to select another class ID. Upon completion of the registration and configuration procedure, the UE (e.g., the LPWA loT device) may be configured or provided with the RA parameters needed to perform random access, and may transmit the UL data (e.g., sensor-related measurements) to the gNB based on the SDT procedure. In an example, the UE may transition to a RRC inactive state and perform the SDT procedure for transmission of the UL data.

[0057] 100481 At step 8 of FIG. 3, the RAN node (gNB) may provide broadcast information to the UEs (or IoT devices). The broadcast information may be a SIB (system information block) message that may include the mapping between the RA parameters and the RA class IDs. Thus, for example, in this manner, the gNB or network may notify various UEs of the RA parameters (including an update or any changes to the RA parameters associated with each of a plurality of RA class IDs). In an example, the SIB messages may be enhanced to include the RA class IDs and/or the RA parameters. For example, a new element may be added to the SIB. Enhancement of the SIB may be advantageous when the UEs may autonomously trigger UL data transmission or SDT. In another implementation, paging procedures may be enhanced. For example, a paging message may include a new IE or a new element/parameter. The new element of the paging message may include the information described in an example embodiment e.g., the information for selecting the random access class for the UE. Enhancement of the paging message may be advantageous when transmission of the UL data or the SDT is triggered by the network. In an example implementation, the paging message may include a new set of scaling factor and/or backoff time parameter assigned to each class ID. It is noted that the information received by UE at steps 6, 7, 7b and 8 may be carried by one or separate messages.

[0058] Step 9 of FIG. 3 refers to a stateless uplink (small data transmission) procedure, and includes steps 10 -15. In an example embodiment, the UE may transmit UL data (e.g., sensor measurements) to the gNB based on the SDT (small data transmission) procedure, without transitioning to RRC connected, as part of the RA procedure (described in FIG. 2). Specifically, at step 10, the UE may apply the configured RA parameters and transmit the message 1. At step 11, the UE may receive the RA response via message 2 i.e., RAR. In an example, the UE may determine the RA parameters based on the updated information received via the SIB broadcast. In an example, the UE may determine the RA parameters based on the type of the UL data to be transmitted. For example, the UE may compare one or more conditions or status of the device regarding the type of the UL data with the one or more random access class selection criteria, and may determine, based on the comparing, that the one or more random access class selection criteria are met, and select the random access class based on the determining. At step 12, the UE may send to the gNB the message 3 (e.g., RA Msg 3). The message 3 may include the UL data (e.g., sensor measurements), a RAN identifier such as an RNTI, and/or the like. At step 13, the gNB may estimate the contention probability for a coverage area of the gNB. The estimate may be based on a number of contention events or RA contention failures per unit of time or over a period of time, or a number of consecutive number of RA contention failures. At step 14, the gNB may utilize the estimated contention probability from step 13 to update the mapping of the RA class ID to UE ID, or update the information for selecting the random access class for the UE. For example, the gNB may modify the size (cardinality) of the set of the RA class IDs. As an example, if the contention probability is above a threshold, the gNB may remove a (predefined) number of registered devices from a prioritized class (e.g., RA class ID #1) and may assign them to a lower priority RA class (RA class ID) such as RA class ID #2. In an example, the gNB may assign more UEs to the prioritized class (RA class ID #1) for which the contention probability is below a threshold. In another example, the gNB may assign new RA parameters per RA class ID and may broadcast the updated mapping of the new RA parameters to the RA class IDs in a future paging message or a SIB message. At step 15, the gNB may update the UE (or the IoT device) with the (new) RA class ID(s) the device is assigned to. The gNB may update the UE via RA message 4 as part of a downlink SDT procedure. The UE may update and store the RA class ID information, for subsequent RA procedures and SDT.

[0059] FIG. 4 is a diagram illustrating an aspect of another example embodiment.

[0060] Steps 7, 8 and 10-13 are not shown in FIG. 4, as these steps are similar as in FIG. 3. In an example implementation, the network may provide configuration information to the UEs, such that the UEs select or determine the RA class ID based on UE-specific conditions. At steps 1-4, the UE may perform initial procedures for registration with the network as described in steps 1 -4 of FIG. 3, except that in the embodiment of FIG. 4, the core network entity, e.g., AIVIF, determines UE conditions (e.g., include one or more random access class selection criteria) for obtaining a RA class ID instead of allocation of RA class ID as in FIG. 3. At step 5, the AMF may send a N2 message to the gNB. The N2 message may include information for selecting a random access class for the UE. The information for selecting the random access class for the UE may include one or more random access class selection criteria (e.g., for selecting the random access class for the UE). In an example, the one or more random access class selection criteria may include at least one of a measurement information type, a number of random access contention failures of the UE with respect to the gNB or the network node, a level or range of reference signal received power (RSRP), or a level or range of reference signal received quality (RSRQ) of reference signals received from the gNB or the network node, a quality of service (QoS) class or requirement associated with transmission of the uplink data by the UE to the gNB or the network node, a battery power level of the UE indicating a range of available battery level that corresponds to a given random access class identifier, priority information associated with the transmission of the uplink data, or a status of UE's buffer allocated for the transmission of the uplink data. At step 6, the gNB may transmit the information for selecting a random access class to the TIE.

[0061] The procedure of selecting or reselecting a RA class by UE is similar to what is described in FIG. 3. According to some illustrative examples: based on current UE status and network conditions, as compared to RA class selection criteria, the UE may select RA class #5, or may select the next higher priority RA class (e.g., may decrement the RA class ID by Y levels, to select a next higher priority RA class ID) if either selection criteria set A) or B) is met: A) there have been 3 or more consecutive RA contention failures, UE battery level is less than 50%, and RSRP of reference signals from the gNB is less than X dB; or B) QoS of data to be transmitted is QoS level 3 or above (high priority data), there has been at least two RA contention failures in last X minutes, and UE data buffer is more than 50% full (or there is more than Z MB of data to be transmitted). These are just illustrative examples and other examples of RA class selection criteria may be used.

[0062] At step 9 of FIG. 4, the UE may transmit the UL data (e.g., sensor measurements) to the gNB based on the SDT procedure, without transitioning to RRC connected state/mode, as part of the RA procedure (e.g., as described in FIG. 2). At step 14, the gNB may update the information for selecting a random access class. At step 15, the gNB may transmit the updated information for selecting a random access class.

[0063] In an example, the RA class may be associated with transmission of a predetermined type of the uplink data or a measurement information type. In an example, the RA class may be associated with at least one of: the priority information of the RA request, the priority information of the uplink data, the priority information of the measurement information type.

[0064] FIG. 5 is a flow chart illustrating operation of an apparatus (e.g., which may be a UE or user device, or other apparatus) according to an example embodiment. Operation 510 includes receiving, by a device from a network node, information for selecting a random access class for the device, wherein each random access class is associated with one or more random access parameters. Operation 520 includes selecting the random access class based on the information. Operation 530 includes transmitting uplink data to the network node, based on the one or more random access parameters associated with the selected random access class.

[0065] With respect to the method of FIG. 5, the method may further include: wherein the information includes one or more random access class selection criteria for selecting the random access class for the device.

[0066] With respect to the method of FIG. 5, the method may further include: wherein the selecting includes: comparing one or more conditions or status of the device with the one or more random access class selection criteria; determining, based on the comparing, that the one or more random access class selection criteria are met; and selecting the random access class based on the determining.

[0067] With respect to the method of FIG. 5, the method may further include: wherein each of a plurality of random access classes is associated with a set of random access class selection criteria, wherein the selecting includes selecting one of the plurality of random access classes for which the associated set of random access class selection criteria is met.

[0068] With respect to the method of FIG. 5, the method may further include: wherein the one or more random access class selection criteria include at least one of: a measurement information type; a number of random access contention failures with respect to the network node; a level of reference signal received power (RSRP), or a level of reference signal received quality (RSRQ) of reference signals received from the network node; a quality of service (QoS) requirement associated with transmission of the uplink data to the network node; a battery power level of the device indicating a range of available battery level that corresponds to a given random access class identifier; priority information associated with the transmission of the uplink data; or a status of buffer allocated for the transmission of the uplink data.

[0069] With respect to the method of FIG. 5, the method may further include: wherein the information includes at least one of: an indication of a random access class; an association between a random access class and one or more random access parameters; a mapping information that maps one or more random access classes to an identifier of the device; or a mapping information that maps one or more random access classes to a type of the uplink data.

[0070] With respect to the method of FIG. 5, the method may further include: wherein the information is received via at least one of: a system information block (SIB); a radio resource control (RRC) message; a configuration update command (CUC) message; or a registration accept message.

[0071] With respect to the method of FIG. 5, the method may further include: receiving an update of the information for selecting the random access class for the device, wherein the update of the information is received via at least one of a radio resource control (RRC) message; a random access response message; a configuration update command (CUC) message; or a system information block (SIB).

[0072] With respect to the method of FIG. 5, the method may further include: wherein the random access class is identified by a random access class identifier.

[0073] With respect to the method of FIG. 5, the method may further include: wherein the device is associated with one or more random access classes.

[0074] With respect to the method of FIG. 5, the method may further include: wherein the one or more random access parameters includes at least one of: a scaling factor indicating an initial transmit power when performing a random access procedure; a power ramping parameter indicating a power increase value; a backoff time parameter indicating a wait time before retransmission of a random access message; a random access configuration index; or a random access preamble index.

[0075] With respect to the method of FIG. 5, the method may further include: wherein the random access class is associated with transmission of a predetermined type of the uplink data or a measurement information type.

[0076] With respect to the method of FIG. 5, the method may further include: wherein the random access class is associated with at least one of: a priority information of a random access request; a priority information of the uplink data; or a priority information of a measurement information type.

[0077] With respect to the method of FIG. 5, the method may further include: wherein the selecting of the random access class for the device is performed based on a result of a random access contention resolution procedure.

[0078] With respect to the method of FIG. 5, the method may further include: wherein the information is received from at least one of a base station; or a core network node.

[0079] With respect to the method of FIG. 5, the method may further include: sending, by the device to the network node, a registration request message; and receiving, a registration response message indicating a result of a registration of the device.

[0080] With respect to the method of FIG. 5, the method may further include: determining a first random access class; and wherein the selecting includes selecting a second random access class based on the information.

[0081] With respect to the method of FIG. 5, the method may further include: wherein each of a plurality of random access classes are identified by a random access class identifier; and wherein the selecting of the second random access class includes incrementing or decrementing a first random access class identifier of the first random access class to obtain a second random access class identifier identifying the second random access class.

[0082] With respect to the method of FIG. 5, the method may further include: wherein the determining the first random access class includes receiving an indication of the first random access class.

[0083] With respect to the method of FIG. 5, the method may further include: wherein the device is an intemet of things (IoT) device or a user device.

[0084] Some examples will now be described, based on the description and figures provided herein.

[0085] Example Al. An apparatus including: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a network node, information for selecting a random access class for the apparatus, wherein each random access class is associated with one or more random access parameters; select the random access class based on the information; and transmit uplink data to the network node, based on the one or more random access parameters associated with the selected random access class.

[0086] Example A2. The apparatus of example Al, wherein the information includes one or more random access class selection criteria for selecting the random access class for the apparatus.

[0087] Example A3. The apparatus of example A2, wherein the selecting includes: comparing one or more conditions or status of the apparatus with the one or more random access class selection criteria; determining, based on the comparing, that the one or more random access class selection criteria are met; and selecting the random access class based on the determining.

[0088] Example A4. The apparatus of example A2, wherein each of a plurality of random access classes is associated with a set of random access class selection criteria, wherein the selecting includes selecting one of the plurality of random access classes for which the associated set of random access class selection criteria is met.

[0089] Example A5. The apparatus of any of examples A2 to A4, wherein the one or more random access class selection criteria include at least one of: a measurement information type; a number of random access contention failures with respect to the network node; a level or range of reference signal received power (RSRP), or a level or range of reference signal received quality (RSRQ) of reference signals received from the network node; a quality of service (QoS) class or requirement associated with transmission of the uplink data to the network node; a battery power level of the apparatus indicating a range of available battery level that corresponds to a given random access class identifier; priority information associated with the transmission of the uplink data; or a status of buffer allocated for the transmission of the uplink data.

[0090] Example A6. The apparatus of any of examples Al to A5, wherein the information includes at least one of: an indication of a random access class; an association between a random access class and one or more random access parameters; a mapping information that maps one or more random access classes to an identifier of the apparatus; or a mapping information that maps one or more random access classes to a type of the uplink data.

[0091] Example A7. The apparatus of any of examples Al to A6, wherein the information is received via at least one of: a system information block (SIB); a radio resource control (RRC) message; a configuration update command (CUC) message; or a registration accept message.

[0092] Example A8. The apparatus of any of examples Al to A7, wherein the apparatus is further caused to receive an update of the information for selecting the random access class for the apparatus, wherein the update of the information is received via at least one of: a radio resource control (RRC) message; a random access response message; a configuration update command (CUC) message; or a system information block (SIB).

[0093] Example A9. The apparatus of any of examples Al to A8, wherein the random access class is identified by a random access class identifier.

[0094] Example A10. The apparatus of any of examples Al to A9, wherein the apparatus is associated with one or more random access classes.

[0095] Example All. The apparatus of any of examples Al to A10, wherein the one or more random access parameters includes at least one of: a scaling factor indicating an initial transmit power when performing a random access procedure; a power ramping parameter indicating a power increase value; a backoff time parameter indicating a wait time before retransmission of a random access message; a random access configuration index; or a random access preamble index.

[0096] Example Al2. The apparatus of any of examples Al to A11, wherein the random access class is associated with transmission of a predetermined type of the uplink data or a measurement information type.

[0097] Example A13. The apparatus of any of examples Al to Al2, wherein the random access class is associated with at least one of a priority information of a random access request; a priority information of the uplink data; or a priority information of a 30 measurement information type.

[0098] Example A14. The apparatus of any of examples Al to A13, wherein the selecting of the random access class for the apparatus is performed based on a result of a random access contention resolution procedure.

[0099] Example A15. The apparatus of any of examples Al to A14, wherein the information is received from at least one of: a base station; or a core network node.

[0100] Example A16. The apparatus of any of examples Al to A15, wherein the apparatus is further caused to: send to the network node, a registration request message; and receive, a registration response message indicating a result of a registration of the apparatus.

[0101] Example A17. The apparatus of any of examples Al to A16, wherein the apparatus is further caused to determine a first random access class; and wherein the selecting includes selecting a second random access class based on the information.

[0102] [00921 Example A18. The apparatus of example A17, wherein each of a plurality of random access classes are identified by a random access class identifier; and wherein the selecting of the second random access class includes incrementing or decrementing a first random access class identifier of the first random access class to obtain a second random access class identifier identifying the second random access class.

[0103] Example A19. The apparatus of example A18, wherein the determining the first random access class includes receiving an indication of the first random access class.

[0104] [00941 Example A20. The apparatus of any of examples Al to A19, wherein the apparatus is an internet of things (loT) device or a user device.

[0105] Example Bl. A method including: receiving, by a device from a network node, information for selecting a random access class for the device, wherein each random access class is associated with one or more random access parameters; selecting the random access class based on the information; and transmitting uplink data to the network node, based on the one or more random access parameters associated with the selected random access class.

[0106] Example B2. The method of example BE wherein the information includes one or more random access class selection criteria for selecting the random access class for the device.

[0107] Example B3. The method of example B2, wherein the selecting includes: comparing one or more conditions or status of the device with the one or more random access class selection criteria; determining, based on the comparing, that the one or more random access class selection criteria are met; and selecting the random access class based on the determining.

[0108] Example B4. The method of example B2, wherein each of a plurality of random access classes is associated with a set of random access class selection criteria, wherein the selecting includes selecting one of the plurality of random access classes for which the associated set of random access class selection criteria is met.

[0109] Example B5. The method of any of examples B2 to B4, wherein the one or more random access class selection criteria include at least one of: a measurement information type; a number of random access contention failures with respect to the network node; a level or range of reference signal received power (RSRP), or a level or range of reference signal received quality (RSRQ) of reference signals received from the network node; a quality of service (QoS) class or requirement associated with transmission of the uplink data to the network node; a battery power level of the device indicating a range of available battery level that corresponds to a given random access class identifier; priority information associated with the transmission of the uplink data; or a status of buffer allocated for the transmission of the uplink data.

[0110] Example B6. The method of any of examples Bl to B5, wherein the information includes at least one of: an indication of a random access class; an association between a random access class and one or more random access parameters; a mapping information that maps one or more random access classes to an identifier of the device; or a mapping information that maps one or more random access classes to a type of the uplink data.

[0111] Example B7. The method of any of examples B1 to B6, wherein the information is received via at least one of: a system information block (SIB); a radio resource control (RRC) message; a configuration update command (CUC) message; or a registration accept message.

[0112] Example B8. The method of any of examples B1 to B7, further including receiving an update of the information for selecting the random access class for the device, wherein the update of the information is received via at least one of a radio resource control (RRC) message; a random access response message; a configuration update command (CUC) message; or a system information block (SIB).

[0113] Example B9. The method of any of examples B1 to B8, wherein the random access class is identified by a random access class identifier.

[0114] Example B10. The method of any of examples B1 to B9, wherein the device is associated with one or more random access classes.

[0115] Example B11. The method of any of examples B1 to B10, wherein the one or more random access parameters includes at least one of: a scaling factor indicating an initial transmit power when performing a random access procedure; a power ramping parameter indicating a power increase value; a backoff time parameter indicating a wait time before retransmission of a random access message; a random access configuration index; or a random access preamble index.

[0116] Example B12. The method of any of examples B1 to B11, wherein the random access class is associated with transmission of a predetermined type of the uplink data or a measurement information type.

[0117] Example B13. The method of any of examples B1 to B12, wherein the random access class is associated with at least one of: a priority information of a random access request; a priority information of the uplink data; or a priority information of a measurement information type.

[0118] Example B14. The method of any of examples B1 to B13, wherein the selecting of the random access class for the device is performed based on a result of a random access contention resolution procedure.

[0119] Example B15. The method of any of examples B1 to B14, wherein the information is received from at least one of: a base station; or a core network node.

[0120] Example B16. The method of any of examples B1 to B15, further including: sending, by the device to the network node, a registration request message; and receiving, a registration response message indicating a result of a registration of the device.

[0121] Example B17. The method of any of examples B1 to B16, the method further including determining a first random access class; and wherein the selecting includes selecting a second random access class based on the information.

[0122] Example B18. The method of example B17, wherein each of a plurality of random access classes are identified by a random access class identifier; and wherein the selecting of the second random access class includes incrementing or decrementing a first random access class identifier of the first random access class to obtain a second random access class identifier identifying the second random access class.

[0123] Example B19. The method of example B18, wherein the determining the first random access class includes receiving an indication of the first random access class.

[0124] Example B20. The method of any of examples B1 to B19, wherein the device is an internet of things (loT) device or a user device.

[0125] FIG. 6 is a block diagram of a wireless station or node (e.g UE, user device, AP, BS, eNB, gNB, RAN node, network node, TRP, or other node) 1300 according to an example embodiment. The wireless station 1300 may include, for example, one or more (e.g., two as shown in FIG. 6) RF (radio frequency) or wireless transceivers 1302A, 1302B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit/entity (controller) 1304 to execute instructions or software and control transmission and receptions of signals, and a memory 1306 to store data and/or instructions.

[0126] Processor 1304 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 1304, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 1302 (1302A or 1302B). Processor 1304 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 1302, for example). Processor 1304 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 1304 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor 1304 and transceiver 1302 together may be considered as a wireless transmitter/receiver system, for example.

[0127] [01171 In addition, referring to FIG. 6, a controller (or processor) 1308 may execute software and instructions, and may provide overall control for the station 1300, and may provide control for other systems not shown in FIG. 6, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 1300, such as, for example, an email program, audio/video applications, a word processor, a Voice over LP application, or other application or software.

[0128] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 1304, or other controller or processor, performing one or more of the functions or tasks described above.

[0129] [01191 According to another example embodiment, RF or wireless transceiver(s) 1302A/1302B may receive signals or data and/or transmit or send signals or data. Processor 1304 (and possibly transceivers 1302A/1302B) may control the RF or wireless transceiver 1302A or 1302B to receive, send, broadcast or transmit signals or data.

[0130] [01201 Example embodiments are provided or described for each of the example methods, including: An apparatus (e.g., 1300, FIG. 6) including means (e.g., processor 1304, RF transceivers 1302A and/or 1302B, and/or memory 1306, in FIG. 6) for carrying out any of the methods; a non-transitory computer-readable storage medium (e.g., memory 1306, FIG. 6) comprising instructions stored thereon that, when executed by at least one processor (processor 1304, FIG. 6), are configured to cause a computing system (e.g., 1300, FIG. 6) to perform any of the example methods; and an apparatus (e.g., 1300, FIG. 6) including at least one processor (e.g., processor 1304, FIG. 6), and at least one memory (e.g., memory 1306, FIG. 6) including computer program code, the at least one memory (1306) and the computer program code configured to, with the at least one processor (1304), cause the apparatus (e.g., 1300) at least to perform any of the example methods.

[0131] Embodiments of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Embodiments may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Embodiments may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Embodiments of the various techniques may also include embodiments provided via transitory signals or media, and/or programs and/or software embodiments that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks. In addition, embodiments may be provided via machine type communications (MTC), and also via an Internet of Things (JOT).

[0132] [01221 As used in this application, the term 'circuitry' or "circuit" refers to all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of circuits and soft-ware (and/or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s)/software including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present. This definition of 'circuitry' applies to all uses of this term in this application. As a further example, as used in this application, the term 'circuitry' would also cover an implementation of merely a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and/or firmware. The term 'circuitry' would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.

[0133] 10123] The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer, or it may be distributed amongst a number of computers.

[0134] 10124] Furthermore, embodiments of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the embodiment and exploitation of massive amounts of interconnected 1CT devices (sensors, actuators, processors microcontrollers, ) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various embodiments of techniques described herein may be provided via one or more of these technologies.

[0135] [01251 A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

[0136] Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0137] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magnetooptical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0138] To provide for interaction with a user, embodiments may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.

[0139] Embodiments may be implemented in a computing system that includes a backend component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a frontend component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an embodiment, or any combination of such backend, middleware, or frontend components. Components may be interconnected by any form or medium of digital data communication, e g, a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.

[0140] While certain features of the described embodiments have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the various embodiments.

Claims

1. WHAT IS CLAIMED IS: 1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from a network node, information for selecting a random access class for the apparatus, wherein each random access class is associated with one or more random access parameters; select the random access class based on the information; and transmit uplink data to the network node, based on the one or more random access parameters associated with the selected random access class.

2. The apparatus of claim 1, wherein the information comprises one or more random access class selection criteria for selecting the random access class for the apparatus.

3. The apparatus of claim 2, wherein the selecting comprises: comparing one or more conditions or status of the apparatus with the one or more random access class selection criteria; determining, based on the comparing, that the one or more random access class selection criteria are met; and selecting the random access class based on the determining.

4. The apparatus of claim 2, wherein each of a plurality of random access classes is associated with a set of random access class selection criteria, wherein the selecting comprises selecting one of the plurality of random access classes for which the associated set of random access class selection criteria is met.

5. The apparatus of any of claims 2 to 4, wherein the one or more random access class selection criteria comprise at least one of a measurement information type; a number of random access contention failures with respect to the network node; a level or range of reference signal received power (RSRP), or a level or range of reference signal received quality (RSRQ) of reference signals received from the network node; a quality of service (QoS) class or requirement associated with transmission of the uplink data to the network node; a battery power level of the apparatus indicating a range of available battery level that corresponds to a given random access class identifier; priority information associated with the transmission of the uplink data; or a status of buffer allocated for the transmission of the uplink data.

6. The apparatus of any of claims I to 5, wherein the information comprises at least one of: an indication of a random access class; an association between a random access class and one or more random access parameters; a mapping information that maps one or more random access classes to an identifier of the apparatus; or a mapping information that maps one or more random access classes to a type of the uplink data.

7. The apparatus of any of claims 1 to 6, wherein the information is received via at least one of: a system information Nock (SIB); a radio resource control (RRC) message; a configuration update command (CUC) message; or a registration accept message.

8. The apparatus of any of claims 1 to 7, wherein the apparatus is further caused to receive an update of the information for selecting the random access class for the apparatus, wherein the update of the information is received via at least one of: a radio resource control (RRC) message; a random access response message; a configuration update command (CUC) message; or a system information block (SIB).

9. The apparatus of any of claims 1 to 8, wherein the random access class is identified by a random access class identifier.

10. The apparatus of any of claims 1 to 9, wherein the apparatus is associated with one or more random access classes. 10

11. The apparatus of any of claims 1 to 10, wherein the one or more random access parameters comprises at least one of a scaling factor indicating an initial transmit power when performing a random access procedure; a power ramping parameter indicating a power increase value; a backotT time parameter indicating a wait time before retransmission of a random access message; a random access configuration index; or a random access preamble index.

12. The apparatus of any of claims 1 to 11, wherein the random access class is associated with transmission of a predetermined type of the uplink data or a measurement information type.

13. The apparatus of any of claims 1 to 12, wherein the random access class is associated with at least one of a priority information of a random access request; a priority information of the uplink data; or a priority information of a measurement information type.

14. The apparatus of any of claims 1 to 13, wherein the selecting of the random access class for the apparatus is performed based on a result of a random access contention resolution procedure.

15. The apparatus of any of claims 1 to 14, wherein the information is received from at least one of: a base station; or a core network node.

16. The apparatus of any of claims 1 to 15, wherein the apparatus is further caused to: send to the network node, a registration request message; and receive, a registration response message indicating a result of a registration of the apparatus.

17. The apparatus of any of claims 1 to 16, wherein the apparatus is further caused to determine a first random access class; and wherein the selecting comprises selecting a second random access class based on the information.

18. The apparatus of claim 17, wherein each of a plurality of random access classes are identified by a random access class identifier; and wherein the selecting of the second random access class comprises incrementing or decrementing a first random access class identifier of the first random access class to obtain a second random access class identifier identifying the second random access class.

19. The apparatus of claim 18, wherein the determining the first random access class comprises receiving an indication of the first random access class. 25

20. The apparatus of any of claims 1 to 19, wherein the apparatus is an internet of things (IoT) device or a user device.

21. A method comprising: receiving, by a device from a network node, information for selecting a random access class for the device, wherein each random access class is associated with one or more random access parameters; selecting the random access class based on the information; and transmitting uplink data to the network node, based on the one or more random access parameters associated with the selected random access class.