Method, device and system for uplink resource management in wireless networks

Abstract

The present disclosure relates generally to methods, devices, and systems for resource management in wireless networks. A method performed by a wireless device can include receiving, from a network node, a first message carrying a list of UL resource configurations for transmitting a UL message associated with an access procedure, the access procedure comprising one of a contention-based access procedure or a contention-free access procedure; and transmitting, to the network node, the UL message using a UL resource configured by a UL resource configuration in the list of UL resource configurations or from a PUR.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, and more particularly to methods, apparatus, and systems for uplink (UL) resource management in wireless networks such as 3G, 4G, 5G, or 6G wireless networks. Background Technology

[0002] To meet the demands of unprecedented mobile user growth and a plethora of new services, wireless communication networks need to expand continuously, leading to constant competition for various resources. Efficient resource management is crucial for developing and deploying robust wireless communication networks. Summary of the Invention

[0003] This disclosure relates to methods, apparatus, and systems for UL resource management in wireless networks such as 3G, 4G, 5G, or 6G wireless networks. More specifically, UL resource management includes UL resource configuration and selection, which can be specifically applied to the access process used to establish UE access to the network.

[0004] In some embodiments, a method performed by a wireless device is disclosed. This method performed by the wireless device may include: receiving from a network node a first message carrying a list of UL resource configurations for transmitting UL messages associated with an access procedure, including either a contention-based access procedure or a contention-free access procedure; and transmitting UL messages to the network node using UL resources configured by UL resource configurations in the UL resource configuration list or from a PUR. The UL resource configuration list may include only one UL resource configuration.

[0005] In some embodiments, a method performed by a network element / network node / wireless reception / transmission unit (WRTU) is disclosed. The method may include: transmitting to a wireless device a first message carrying a UL resource configuration list for transmitting UL messages associated with an access procedure, the access procedure including either a contention-based access procedure or a contention-free access procedure; and receiving from the wireless device UL messages transmitted in UL resources, the UL resources being configured by UL resource configurations in the UL resource configuration list or from a PUR.

[0006] In some embodiments, there is a wireless device, network element, WRTU, or network node that includes a processor and memory, wherein the processor is configured to read code from memory and implement any of the methods described in any embodiment.

[0007] In some embodiments, the computer program product includes computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to perform the method described in any embodiment.

[0008] Other aspects and alternatives to the above embodiments and their implementation are described in more detail in the accompanying drawings, specification and the following claims. Attached Figure Description

[0009] Figure 1 An example wireless communication network is shown.

[0010] Figure 2 An example wireless network node is shown.

[0011] Figure 3 An example user device is shown.

[0012] Figure 4 An example non-terrestrial network deployment of a wireless network is shown.

[0013] Figure 5A An example of a contention-based 4-step random access procedure is shown.

[0014] Figure 5B An example of a contention-based two-step access procedure is shown, starting with Msg3.

[0015] Figure 5C Various candidate uplink resources are shown for the two-step access process.

[0016] Figure 6 An example UL resource configuration list according to one embodiment of this disclosure is shown.

[0017] Figure 7 Example candidate resources and pending UL data are shown.

[0018] Figure 8 An example UL resource configuration list with associated conditions is shown according to one embodiment of this disclosure.

[0019] Figure 9 A list of example UL resource configurations using TA timers is shown.

[0020] Figure 10 An example UL resource selection for retransmitting Msg3 is shown. Detailed Implementation

[0021] Wireless communication network

[0022] Figure 1An exemplary wireless communication network 100 is shown, comprising a core network 110 and a radio access network (RAN) 120. The core network 110 further includes at least one Mobility Management Entity (MME) 112 and / or at least one Access and Mobility Management Function (AMF). Figure 1 Other functions that may be included in the core network 110 are not shown. RAN 120 further includes multiple base stations, such as base stations 122 and 124. The base stations may include at least one evolved Node B (eNB) for 4G LTE, an enhanced LTE eNB (ng-eNB), or a next-generation Node B (gNB) for 5G New Radio (NR), or any other type of signal transmission / reception equipment such as a UMTS Node B. eNB 122 communicates with MME 112 via an S1 interface. Both eNB 122 and gNB 124 may be connected to AMF 114 via an Ng interface. Each base station manages and supports at least one cell. For example, base station gNB 124 may be configured to manage and support cell 1, cell 2, and cell 3.

[0023] The gNB 124 may include a central unit (CU) and at least one distributed unit (DU). The CU and DU may be located in the same location, or they may be located in different locations. The CU and DU may be connected via an F1 interface. Alternatively, for an eNB capable of connecting to a 5G network, it may similarly be divided into a CU and at least one DU, referred to as ng-eNB-CU and ng-eNB-DU, respectively. The ng-eNB-CU and ng-eNB-DU may be connected via a W1 interface.

[0024] The wireless communication network 100 may include one or more tracking areas. A tracking area may include a set of cells managed by at least one base station. For example, tracking area 1, labeled 140, includes cells 1, 2, and 3, and may further include cells that can be managed by other base stations and... Figure 1Further cells are not shown. The wireless communication network 100 may also include at least one UE 160. The UE may select a cell from a plurality of cells supported by the base station to communicate with the base station via an over-the-air (OTA) radio communication interface and resources, and may reselect the cell for communication as the UE 160 travels within the wireless communication network 100. For example, the UE 160 may initially select cell 1 to communicate with the base station 124, and may then reselect cell 2 at a later point in time. The cell selection or reselection performed by the UE 160 may be based on the radio signal strength / quality in each cell and other factors.

[0025] The wireless communication network 100 can be implemented as, for example, a 2G, 3G, 4G / LTE, or 5G cellular communication network. Correspondingly, base stations 122 and 124 can be implemented as 2G base stations, 3G NodeBs, LTE eNBs, or 5G NR gNBs. The UE 160 can be implemented as a mobile or fixed communication device capable of accessing the wireless communication network 100. The UE 160 can include, but is not limited to, mobile phones, laptops, tablets, personal digital assistants, wearable devices, Internet of Things (IoT) devices, MTC / eMTC devices, distributed remote sensor devices, roadside assistance devices, XR devices, and desktop computers. The UE 160 can also be commonly referred to as a wireless communication device or a wireless terminal. The UE 160 can support sidelink communication to another UE via a PC5 interface.

[0026] Although the following description focuses on, for example Figure 1 The cellular wireless communication system shown is based on the same principles, but the same principles apply to other types of wireless communication systems used for paging wireless devices. These other wireless systems may include, but are not limited to, Wi-Fi, Bluetooth, ZigBee, and WiMax networks.

[0027] Figure 2 An example of an electronic device 200 for implementing a network base station (e.g., a radio access network node), core network (CN), and / or operation and maintenance (OAM) is shown. Optionally, in one embodiment, the example electronic device 200 may include radio transmit / receive (Tx / Rx) circuitry 208 to transmit / receive communications with a UE and / or other base stations. Optionally, in one embodiment, the electronic device 200 may also include network interface circuitry 209 to enable communication between the base station and other base stations and / or the core network, e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communication with operators, etc.

[0028] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include processor 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more processors 221 to perform the functions of a network node. Parameters 228 may include parameters that support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0029] Figure 3 An example of an electronic device for implementing terminal device 300 (e.g., user equipment (UE)) is shown. UE 300 may be a mobile device, such as a smartphone or a mobile communication module installed in a vehicle. UE 300 may include some or all of the following: communication interface 302, system circuitry 304, input / output interface (I / O) 306, display circuitry 308, and storage device 309. The display circuitry may include a user interface 310. System circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuit. System circuitry 304 may be implemented, for example, using one or more systems-on-a-chip (SoC), application-specific integrated circuits (ASIC), discrete analog and digital circuitry, and other circuitry. System circuitry 304 may be part of an implementation of any desired functionality of UE 300. In this regard, system circuitry 304 may include logic, for example, facilitating the decoding and playback of music and video, such as MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections, such as internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 may include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, a universal serial bus (USB) connector, a memory card slot, a radiation sensor (e.g., an IR sensor), and other types of inputs.

[0030] Reference Figure 3The communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 that processes the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver, including modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaper, an analog-to-digital converter (ADC), filters, waveform shapers, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals may conform to any of various formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), 5G (also known as New Radio, or 5G NR) and 6G standards. However, the techniques described below are applicable to other wireless communication technologies, whether they originate from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0031] Reference Figure 3 System circuitry 304 may include one or more processors 321 and memory 322. Memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. Processor 321 is configured to execute instructions 326 to perform desired functions for UE 300. Parameters 328 can provide and specify configuration and operational options for instructions 326. Memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data that UE 300 will transmit or has received via communication interface 302. In various embodiments, system power for UE 300 may be supplied by power storage devices, such as batteries or transformers.

[0032] Non-terrestrial networks

[0033] In certain regions, such as mountains, deserts, and oceans, deploying wireless communication networks can be expensive and difficult. However, with advancements in science and technology, the demand for data collection and communication in these remote areas is significant. For example, it may be necessary to collect meteorological data on mountain peaks or in deserts.

[0034] In non-terrestrial network (NTN) deployments, satellites can provide signal coverage over large areas, even in remote regions. In addition to terrestrial networks, NTNs can be deployed to further extend the coverage of terrestrial cellular networks. NTNs can be deployed to enhance network resilience in scenarios such as disaster recovery or emergency communications. Furthermore, NTNs can play a significant role in IoT deployments and mission-critical services, thus expanding the business of network operators.

[0035] In NTN, a satellite can be associated with a base station, or be part of a base station (or an extension of a base station). Figure 4 An example of a non-terrestrial network (NTN) 400 providing wireless network access to a UE is shown. In the NTN 400, satellite 402 provides communication links between ground areas. Similar to traditional cellular networks, the covered ground areas can be divided into cells, or more specifically, into satellite cells, such as... Figure 4 Cells 1 through 4 are shown. These cells can provide signal coverage for the UE. The radio link between the satellite and the UE can be referred to as the service link. Satellite 402 can generate multiple beams over a given service area bounded by its field of view. The coverage area of ​​the beams can be elliptical.

[0036] Satellite 402 can be placed in either Low-Earth Orbit (LEO) or Geostationary Earth Orbit (GEO). A Geostationary Orbit is a circular orbit located 35,786 km above the Earth's equator and following the direction of the Earth's rotation. The orbital period of a GEO satellite in this type of orbit can be equal to the Earth's rotation period, and therefore, to a ground observer, it appears stationary in a fixed position in the sky. The typical beam coverage area of ​​a GEO is approximately 200–3500 km. A Low-Earth Orbit is an orbit around the Earth at an altitude between 300 km and 1500 km. LEO satellites in this type of orbit orbit the Earth at, for example, a speed of 7.56 km / s. The LEO beam coverage area can be 50 km to 1000 km.

[0037] The NTN 400 may include an NTN gateway 404, which may be an earth station located on the Earth's surface and provide sufficient RF power and RF sensitivity for accessing the satellite 402. The NTN gateway 404 may be a transport network layer (TNL) node and may provide access to, for example, a core network, a radio access network, or a data network. The wireless link between the NTN gateway 404 and the satellite 402 may be referred to as a feeder link.

[0038] Currently, IoT connectivity typically requires extensive coverage, especially in remote or underserved areas where traditional terrestrial networks may be insufficient. NTN deployment addresses this need by providing wide-area coverage and extending connectivity to areas where terrestrial infrastructure is impractical or unavailable. Narrowband IoT (NB-IoT), or enhanced Machine Type Communication (eMTC), is a low-power, wide-area (LPWA) cellular technology designed specifically for IoT applications, offering remote connectivity, efficient power usage, and support for a large number of devices. Using NTN to support NB-IoT and eMTC is becoming a significant trend in wireless communication development.

[0039] NTN deployments for NB-IoT are underway, marking a significant step in extending IoT connectivity to remote or underserved areas. In early deployments, IoT-NTN, particularly NB-IoT, will need to support a large capacity in terms of the number and types of UEs, which may have different characteristics (e.g., low-cost devices, wearables, etc.). For cost-saving purposes, many IoT UEs are low-cost, low-end, or low-performance UEs. Therefore, special consideration is needed to cover a wide range of UEs.

[0040] This disclosure presents various embodiments designed to address the challenges of supporting diverse UE types and maximizing UL capacity. For example, methods for configuring and allocating uplink resources tailored for NTN / IoT environments are described. These methods provide mechanisms for efficient resource configuration and allocation and enhance the overall capacity of the uplink channel. In particular, these methods can be applied to a Random Access Procedure (RAP) to configure the required UL resources therein. As another example, embodiments are described to unlock additional UL capacity potential by decoupling the uplink (UL) from the downlink (DL) as much as possible.

[0041] Random Access

[0042] In mobile communication systems (e.g., 5G, 4G LTE, 3G UMTS), the UE and the network need to establish a connection to transmit, for example, service data or application data. Typically, an access procedure is required for the UE to access the network.

[0043] In this disclosure, the network may include a radio access network (RAN), which may also include one or more base stations. The network may also include a core network. The connection between the UE and the network may include, for example, a connection between the UE and a base station in the network, a connection between the UE and a cell in the network, etc.

[0044] To establish uplink synchronization and / or Radio Resource Control (RRC) connections, the UE may need to perform a random access procedure, also known as a RACH (Random Access Channel) procedure or a PRACH (Physical RACH) procedure. The RACH procedure can have different implementations (e.g., a 4-step contention-based random access (CBRA) procedure and a 2-step CBRA procedure). A contention-free RACH procedure can also exist.

[0045] Figure 5A Example 4-step CBRA process is shown, which includes the following steps:

[0046] Step 1:

[0047] The UE selects a preamble (or preamble resource) from the available PRACH resource pool and sends the selected preamble (e.g., in Msg1) to the network (e.g., a base station such as a gNB). Note that simultaneously, one or more other UEs may also select the same preamble resource for the RACH procedure, which can lead to contention.

[0048] Step 2:

[0049] Upon receiving the preamble, the base station sends a Random Access Response (RAR) back to the UE (e.g., in Msg2). The RAR may include a Temporary Cell Radio Network Temporary Identifier (C-RNTI) and / or Uplink (UL) authorization assigned by the base station.

[0050] Step 3:

[0051] The UE stores the temporary C-RNTI and sends a third message (e.g., Msg3) to the base station using the UL authorization indicated in the RAR. Exemplarily, this Msg3 can be sent from the RRC layer, in which case it can also be referred to as RRC Msg3. For contention resolution purposes, Msg3 may carry an identifier such as a UE contention resolution identifier.

[0052] After sending Msg3, the UE can start a contention resolution timer (e.g., ra-ContentionResolutionTimer) and monitor the PDCCH.

[0053] Step 4:

[0054] The base station can send a PDCCH addressed to the temporary C-RNTI (as described in steps 2 and 3, which can be denoted as TEMPORARY_C-RNTI) for Msg4 scheduling. The base station can assist the UE in contention resolution by using the C-RNTI on the PDCCH or by using the UE contention resolution identifier (obtained by the base station based on the UL CCCH SDU (e.g., Msg3) received in the previous steps) on the PDSCH. The base station can send Msg4 for contention resolution.

[0055] The UE obtains a PDCCH addressing its temporary C-RNTI. If the MAC PDU associated with Msg4 contains a UE contention resolution identifier MAC CE, and the UE contention resolution identifier in that MAC CE matches the UL CCCH SDU (e.g., Msg3), the UE considers the contention resolution successful; otherwise, if the UE contention resolution identifiers do not match, the UE considers the contention resolution unsuccessful, discards the TEMPORARY_C-RNTI, and triggers the RACH procedure again.

[0056] If the ra-ContentionResolutionTimer times out before the UE can determine that the contention resolution was successful, the UE considers the contention resolution unsuccessful, discards the TEMPORARY_C-RNTI, and triggers the PRACH procedure again.

[0057] Two-step access process

[0058] The RACH process described above involves four steps, which represents a significant overhead for both the UE and the network. In this disclosure, to reduce overhead and accelerate the access procedure for UE access to the network, a simplified two-step access procedure is introduced, as shown in... Figure 5B In the middle. For example Figure 5B As shown, the UE can begin by sending Msg3 to the network as an indication of a network access request or network connection request. The UE can then receive Msg4 to indicate, for example, contention resolution and successful access establishment.

[0059] In this disclosure, an uplink (UL) resource pool is introduced. A UE can be configured with a UL resource pool via one or more UL resource configurations, where each configuration corresponds to a UL resource. When transmitting Msg3, the UE can select a UL resource from the UL resource pool for uplink transmission.

[0060] UL resources can be shared with other UEs. Using shared UL resources, Msg3 transmission is contention-based because multiple UEs can simultaneously use the same UL resources for Msg3 transmission. Similar to Msg3 in the four-step random access procedure described above, Msg3 in this two-step access procedure can also carry an RNTI. This RNTI can be configured by the base station and sent to the UE via, for example, broadcast or RRC message. The RNTI can also be an RNTI stored by the UE when it is in a pre-connected state. The RNTI can also be generated by the UE itself based on certain rules. Various embodiments in this disclosure will cover details regarding the various types of RNTIs used in Msg3. In this disclosure, if Msg3 transmission is contention-based, the access procedure can be referred to as a contention-based access procedure (or a contention-based random access procedure).

[0061] Msg4 can be used similarly for contention resolution. In this disclosure, Msg4 can be addressed by RNTI (so the UE can inform it whether it is the recipient of MSg4), and / or Msg4 can be used to carry RNTI, and the UE can store RNTI for future use.

[0062] Alternatively, the UL resource pool may include one or more UL resources allocated to or dedicated to the UE, and the UE may use these dedicated UL resources to transmit contention-free Msg3.

[0063] Alternatively, in addition to or replacing the UL resource pool, the UE can be configured with a dedicated preconfigured uplink resource (PUR), in which the UE can use contention-free Msg3 transmission.

[0064] Figure 5C The various UL resources from which the UE can select UL resources are shown.

[0065] In this disclosure, the two-step access procedure can be considered an improved or simplified random access procedure. All embodiments in this disclosure are applicable to both two-step and four-step access procedures.

[0066] Example 1: UL Resource Configuration

[0067] In this embodiment, the UL resource pool is configured for, for example, contention-based Msg3, or other types of contention-based or contention-free uplink transmissions. The UL resource pool may include multiple UL resources. Once configured, the UE can use one or more resources selected from the UL resource pool for UL transmissions, such as Msg3 transmissions.

[0068] Figure 6Example UL resource configuration list 600 is shown, which can be used to configure a UL resource pool. For example... Figure 6 As shown, the UL resource configuration list 600 can include n UL resource configurations (with indices from 1 to n). Each UL resource configuration can be assigned an index for identification purposes and can include corresponding UL resource configuration parameters (see below for details on these parameters). Each UL resource configuration can be used to configure the corresponding UL resource. Generally, each UL resource can have its time-domain resource allocation and frequency-domain resource allocation. Furthermore, UL resources can be further configured with code domain allocations (e.g., allocated code sequences, modulation schemes, etc.). Note that, as a special case, the UL resource configuration list can have only one entry (i.e., only one UL resource configuration exists in the list), and in this case, a UL resource configuration index is not required. The number of entries in the list can also be referred to as the size of the list.

[0069] There are several ways to configure the UL resource configuration list. For example, the UL resource configuration list can be configured via broadcast messages, such as broadcast messages or System Information Block (SIB) messages. When using broadcast, multiple UEs can have their UL resource configuration lists configured simultaneously. The UL resource configuration list can also be configured via unicast messages, such as Radio Resource Control (RRC) messages. The configuration of the UL resource configuration list can be sent in a single message or split into multiple messages.

[0070] The following description uses a base station for illustrative purposes. In the example below, the base station can transmit a UL resource configuration list to the UE. The same underlying concepts also apply to other entities that can communicate with the UE, such as a cell, in which case the cell can transmit the UL resource configuration list to the UE.

[0071] Each UL resource configuration in the UL resource configuration list can be used to configure the corresponding UL resource and can include at least one of the following parameters:

[0072] • Identifies the index of each UL resource configuration in the UL resource configuration list;

[0073] • The start time corresponding to the UL resource;

[0074] • The length of the corresponding UL resource in the time domain;

[0075] • The resource block (RB) number corresponding to the UL resource;

[0076] • The Resource Unit (RU) number corresponding to the UL resource;

[0077] • Subcarrier number corresponding to UL resource;

[0078] • Corresponding to the periodicity of UL resources;

[0079] • The transport block size (TBS) corresponding to the UL resource;

[0080] • Anchor carrier or non-anchor carrier corresponding to UL resources;

[0081] • Physical downlink control channel (PDCCH) search space configuration corresponding to UL resources;

[0082] • The number of times the corresponding UL resource is repeated;

[0083] • Subcarrier configuration corresponding to UL resources; or

[0084] • Modulation and coding schemes corresponding to UL resources.

[0085] In some example implementations, the base station may broadcast a UL resource configuration list via SIB.

[0086] In some example implementations, the base station may broadcast a list of public UL resource configurations that can be shared by the UE. Each UL resource configuration in the list may include one or more configuration parameters for the corresponding UL resource, such as: start time, RB number, periodicity, transport block size (TBS), anchor carrier or non-anchor carrier, etc.

[0087] In some example implementations, the base station can send a UL resource configuration list via RRC messages. Each UL resource configuration in the list may include one or more configuration parameters for the corresponding UL resource, such as: start time, RB number, periodicity, TBS, anchor carrier, or non-anchor carrier. Specifically, when an RRC message is sent to a specific UE, the UL resource configuration list may be customized by the base station for the UE based on, for example, auxiliary information sent by the UE. The UE may send auxiliary information to the base station via RRC messages (such as PURConfigurationRequest messages). The auxiliary information may include information about the requested UL resource, such as: periodicity, time offset, transport block size (TBS), RRC acknowledgment (RRC Ack), etc. This auxiliary information may further include UE characteristic data. Based on the UE auxiliary information, the base station can customize a corresponding UL resource configuration list for the UE and send the customized UL resource configuration list via RRC messages (such as RRC release messages).

[0088] Note that from the base station side, the base station can send the same UL resource configuration list to multiple UEs.

[0089] In some example implementations, the base station can send a UL resource configuration indicator to the UE via, for example, an RRC message, so that the UE can select a UL resource configuration from a UL resource configuration list based on the indicator. The UL resource configuration indicator can be an index to a UL resource configuration, such as... Figure 6 As shown. When the UE is configured with a UL resource configuration list that may include multiple UL resource configurations, the base station can determine the index based on the UE assistance information as described above, so that the selected UL resource configuration is adapted to the UE assistance information provided by the UE.

[0090] Note that a base station can indicate the same UL resource configuration to multiple UEs.

[0091] In some example implementations, a UL resource configuration enablement mechanism can be implemented. This mechanism can be considered as access control, ensuring that the UE can only use the UL resource configuration list when it is enabled. For example, after the UL resource configuration list is configured, it can be in an inactive or disabled mode, and the UE cannot use it. The base station can manipulate the mode of the UL resource configuration list by sending an enable indicator to the UE via, for example, an RRC message.

[0092] Specifically, the base station can determine or predict the UL resources that the UE needs for contention-based Msg3 transmissions. The base station can send an enable instruction to enable or disable the UE's use of the UL resource configuration list via, for example, an RRC release message.

[0093] In one example, the UL resource configuration list may include only one UL resource configuration. In this case, the enable instruction also acts as a selection instruction, so that once the list is enabled, no further separate instruction for the UL resource configuration is required.

[0094] With the enabled mechanism, the UE can prevent the transmission of Msg3 when the UL resource configuration list is in disabled mode.

[0095] In some example implementations, the UL resource configuration list can be further divided into one or more groups (or sublists). In this case, each UL resource configuration can be assigned a group ID. Exemplarily, the base station can first configure the UL resource configuration list (which includes multiple groups) via a broadcast message, and then send an RRC message carrying the group ID to the UE. That is, the UE is assigned a group ID and can select only UL resource configurations with the same group ID.

[0096] In some implementations, further restrictions may be added to the UL resource configuration list. For example, one or more UL resource configurations in the UL resource configuration list may be configured with a validity region, and the specific UL resource configuration is only valid when the UE is within the corresponding validity region. Optionally, when the UE moves out of the validity region, the UE may choose to release the corresponding UL resource configuration. The validity region may include at least one of: a cell identifier list, a satellite identifier list, a tracking area identifier list, and the like.

[0097] In some implementations, further restrictions may be added to the UL resource configuration list. For example, one or more UL resource configurations in the UL resource configuration list may be configured with a validity period, or a validity time period. A UL resource configuration is valid only for UL resources falling within this time period, or can only be applied to UL resources falling within this time period. If the current time is outside the validity time period, or if the UL resource configured by the UL resource configuration is outside the validity time period, then the UL resource configuration cannot be used. Optionally, if the current time exceeds the validity time period, the UE may choose to release the UL resource configuration. The validity period may be in the form of one or more durations, one or more transmission opportunities, and the like. The validity period may begin counting after the UL resource configuration list becomes effective or is configured, or after the first valid transmission opportunity. Details regarding the first valid transmission opportunity are described in the following sections.

[0098] Example 2: UL resource start time

[0099] In this embodiment, the UE already has a UL resource configuration list configured using the above embodiments. Optionally, the UL resource configuration list may have only one entry.

[0100] In some example implementations, the UL resource configuration list can be configured by RRC messages. From a time-domain perspective, the first (i.e., most recent) UL resource timing configured by the UL resource configuration list is located by the supersystem frame number (HSFN), the system frame number (SFN) (which is the SF within the HSF identified by the HSFN), and the subframe (within the SF identified by the SFN).

[0101] The frame number HSFN of HSF can be determined as follows:

[0102] HSFN = (HSFN) Ref +offset)mod 1024 (that is, it occurs after (FLOOR(offset / 1024)H-SFN loop), where mod is the modulo operation.

[0103] •HSFN RefThis corresponds to the supersystem frame number of the HSF, where the first or last subframe of the first transmission, or the first or last subframe of the last transmission of the RRC message (used to configure the UL resource configuration list). Note that the RRC message may need to be transmitted multiple times.

[0104] • Offset is the offset from the start of an HSF-level time period. Each HSF-level time period can include n HSFs, where n is an integer. The offset can be counted in units of HSFs. For example, if each HSF-level time period has 10 HSFs, an offset of 2 means an offset of 2 HSFs from the start of the HSF-level time period. The offset can be pre-configured.

[0105] • HSF hierarchical periodicity can be pre-configured in units of the number of HSFs.

[0106] The system frame number and / or subframes for the first UL resource timing can be pre-configured.

[0107] In some example implementations, the UL resource configuration list can be configured by broadcast messages (such as SIB messages). From a time-domain perspective, the first UL resource timing configured by the UL resource configuration list is located by the supersystem frame number (HSFN), the system frame number (SFN) (which is the SF within the HSF identified by the HSFN), and the subframe (within the SF identified by the SFN).

[0108] The frame number HSFN of HSF can be determined as follows:

[0109] HSFN = (HSFN) Ref +offset) mod 1024 occurs after the FLOOR(offset / 1024) H-SFN cycle.

[0110] •HSFN Ref The supersystem frame number corresponding to the HSF, where the first or last subframe of the System Information (SI) window of the SIB message (used to configure the UL resource configuration list).

[0111] • Offset is the offset from the start of an HSF-level time period. Each HSF-level time period can include n HSFs, where n is an integer. The offset can be counted in units of the number of HSFs. For example, if each HSF-level time period has 10 HSFs, an offset of 2 means an offset of 2 HSFs from the start of the HSF-level time period. The offset can be pre-configured.

[0112] • HSF hierarchical periodicity can be pre-configured in units of the number of HSFs.

[0113] The system frame number and / or subframes for the first UL resource timing can be pre-configured.

[0114] Example 3: Contention-free operation of Msg3

[0115] In this embodiment, the UE can perform a contention-free Msg3 operation (i.e., transmit a contention-free Msg3).

[0116] The base station can indicate the Orthogonal Cover Code (OCC) index to the UE via, for example, an RRC message. The OCC index can be used to determine the code sequence used to encode / generate the Physical Uplink Shared Channel (PUSCH) for Msg3. Specifically, the base station can indicate different OCC indices to different UEs, so that the PUSCHs (for Msg3) of those UEs are orthogonal in the UL resources.

[0117] In some example implementations, the OCC index may be included as part of the UL resource configuration parameters. When the UL resource configuration list is configured, one or more UL resource configurations may have an OCC index parameter.

[0118] In some example implementations, an OCC index may be indicated separately for a particular UL resource configuration.

[0119] In this embodiment, the code sequence can be determined by using the OCC index to ensure that the PUSCH used for Msg3 is orthogonal, so that Msg3 can be transmitted without contention.

[0120] Example 4: Resource Selection

[0121] With the introduction of UL resources into the UL resource pool via a UL resource configuration list, each UL resource configuration in the list can correspond to a UL resource configured by it. These UL resources can have different time-domain locations and / or different frequency-domain locations. Additionally, from a code domain perspective, these UL resources can already be associated with different code sequences.

[0122] Figure 7 This shows example UL resources configured from the UL resource configuration list. For example... Figure 7 As shown, there are four candidate UL resources: 702, 704, 706, and 708. Each resource corresponds to a UL resource configuration in the UL resource configuration list and can be considered as the timing of transmission. The block size of these UL resources represents the resource size (e.g., in bytes, megabytes, etc.).

[0123] In some example implementations, for UL transmissions, the UE can select the nearest transmission opportunity configured by the UL resource configuration. For example, when Msg3 is triggered (or in other words, when Msg3 is pending), the UE can select the nearest opportunity to transmit Msg3. Figure 7 As shown, at time t0, the UE needs to transmit UL data (e.g., Msg3). The most recent transmission opportunity has the least waiting time. In this case, UL resource 702 is closest to t0, therefore it has the least waiting time. The UE can choose 702 for UL transmission.

[0124] In some example implementations, a resource block size matching scheme can be used. Among all candidate UL resource blocks, the UE can select the one that most closely matches the size of the pending UL data / message. That is, the selected UL resource has the closest matching size (capacity) greater than or equal to the size of the UL data / message (such as Msg3). This size can be represented by, for example, the transport block size (TBS), the number of resource blocks (RBs), the number of resource elements (RUs), or the number of subcarriers. Figure 7 As shown, at time t0, the UE needs to transmit UL data (e.g., Msg3). There are four candidate UL resources (702, 704, 706, and 708), each configured by a UL resource configuration in the UL resource configuration list. In this case, UL resource 708 has the closest match in terms of block size. The UE will select UL resource 708 to transmit the pending UL data 710, which may include Msg3.

[0125] In some example implementations, from a frequency domain perspective, the UE can randomly select the frequency domain timing for transmitting UL resources. When Msg3 is triggered, the UE can randomly select the frequency domain timing for transmitting Msg3.

[0126] Example 5: Conditions for using UL resources

[0127] In this embodiment, after the UE is configured with a UL resource pool via a UL resource configuration list, the UE must meet certain conditions in order to use the UL resources configured by the list to transmit UL data / messages, and this is specifically used for the UE to initiate contention based on Msg3.

[0128] In this embodiment, multiple thresholds are used. Unless otherwise specified, these thresholds may be predefined or configured by the base station via, for example, RRC messages or broadcast messages (e.g., SIBs).

[0129] In some example implementations, the UE's Reference Signal Received Power (RSRP) must be higher than the RSRP threshold. In this case, the channel quality is good enough to utilize UL resources.

[0130] In some example implementations, the RSRP change must be less than a threshold. The RSRP change can include the change between the current RSRP and the last RSRP. The last RSRP can be measured when the UE receives the UL resource configuration list, or when the UL resource configuration list is active. Alternatively, the RSRP change can be measured over a specific duration. For example, the RSRP change can be based on measurements at the start and end of the duration. In this way, the TBS and / or MCS configured in the UL resource configuration can be applicable (i.e., the configured TBS and / or MCS can be applied only if this condition is met). The RSRP change threshold or specific duration can be predefined or configured by the base station via, for example, an RRC message or a broadcast message (e.g., an SIB). When the UL resource configuration list is active, it means that any one of the UL resource configurations in the list is active. Alternatively, if there is only one UL resource configuration in the list, it means that only that single UL resource configuration is active.

[0131] In this disclosure, several types of change measurements exist. For example, there are RSRP changes, timing advance (TA) changes, distance changes, and propagation delay changes. The measurement of these changes can follow the same principles described above for RSRP changes. Taking TA change measurement as an example, the change can be between the current TA and the last TA, and the last TA can be measured when the UE receives the UL resource configuration list, or when the UL resource configuration list takes effect. That is, the last TA measurement is performed at the same time as the last RSRP measurement. Similarly, these changes can be measured for a specific duration, and the duration is as described above for RSRP changes. Similarly, the corresponding change thresholds (e.g., TA change threshold, distance change threshold, propagation delay change) and the measurement duration can be predefined or configured by the base station via, for example, RRC messages or broadcast messages (e.g., SIBs).

[0132] In some example implementations, the amount of UL data (e.g., payload size) of the UE to be transmitted is less than or equal to a data size threshold, or the TBS of the selected UL resource configuration. In this way, large data is restricted / prohibited from using UL resources configured by the UL resource configuration list, prioritizing UL transmissions with small data sizes.

[0133] In some example implementations, UE UL synchronization must be maintained (the UE must be UL synchronized). The UE must remain UL synchronized with the base station. For example, the UL synchronization timer must be running, or the UE must be able to obtain UL synchronization before it can transmit in the UL resources configured by the UL resource configuration in the UL resource configuration list.

[0134] In some example implementations, the UE's timing advance (TA) must be less than a TA threshold. The UE can estimate the TA in the serving link or in a combination of the serving link and the feeder link. In this way, the channel quality is sufficient to utilize UL resources.

[0135] In some example implementations, the TA change must be less than a TA change threshold. In this way, the TBS or MCS configured in the UL resource configuration can be applicable.

[0136] In some example implementations, the distance between the UE and the reference point must be less than a distance threshold. The UE can estimate the distance between the UE and the reference point. Exemplarily, the reference point can be indicated by a base station and can include at least one of the following: the center of a cell associated with the base station, a satellite, or a base station. In this way, the UE is within the maximum permissible distance from the other end of the communication link and the channel quality can be sufficient to utilize UL resources.

[0137] In some example implementations, the distance change must be less than a distance change threshold. In this way, the TBS or MCS configured in the UL resource configuration can be applicable.

[0138] In some example implementations, the propagation delay must be less than a threshold. The UE can estimate the propagation delay between the UE and the satellite, or the propagation delay in the serving link, or the propagation delay as the sum of the serving link delay and the feeder link delay (serving link delay + feeder link delay). In this way, the channel quality can be sufficient to utilize UL resources.

[0139] In some example implementations, the propagation delay variation must be less than a propagation delay threshold. In this way, the TBS or MCS configured in the UL resource configuration can be applicable.

[0140] In some example implementations, UL resource configurations in the UL resource configuration list can only be applied within a time range (i.e., the UL resource configuration has a valid period). For example, at time point x, the UL resource configuration becomes effective or is received by the UE. From time point x, the UL resource configuration is valid for the duration of its validity. Or, at time point z, the UL resource configuration loses its effectiveness. Then, the UL resource configuration is valid during the period from time x to z. Time point x can also be predefined, or configured by the base station via, for example, an RRC message, or a broadcast message (e.g., SIB), instead of using the time when the UL resource configuration becomes effective or is received by the UE. The duration can be predefined, or configured by the base station via, for example, an RRC message, or a broadcast message (e.g., SIB).

[0141] Example 6: Correspondence of Coverage Conditions

[0142] In this embodiment, one or more UL resource configurations from the UL resource configuration list can be used at one or more coverage levels or coverage conditions. The UE can select UL resources based on its coverage level and / or coverage conditions and / or its location. For example, for UE1, if it is in cell coverage level 1, it can select the corresponding UL resource configuration 1 (which is applicable to or corresponds to coverage level 1); for UE2, if it is in cell coverage level 2, it can select the corresponding UL resource configuration 2 (which is applicable to or corresponds to coverage level 2).

[0143] Figure 8 A sample list of UL resource configurations is shown. UL resource configuration 1 is associated with or corresponds to at least one of the following coverage condition thresholds: RSRP threshold; coverage level; TA threshold; propagation delay threshold; or distance threshold. Based on one or more of these thresholds, the UE can be able to find UL resource configurations from the UL resource configuration list that meet the threshold requirements. Other UL resource configurations in the list may also correspond to a set of threshold parameters.

[0144] In some example implementations, for UL resource configuration, such as Figure 8 In the UL resource configuration, after the UL resource configuration is sent to the UE, the corresponding coverage condition threshold can be sent to the UE via broadcast message or RRC message.

[0145] In some example implementations, UL resource configuration can be configured along with its corresponding coverage condition threshold via, for example, broadcast messages or RRC messages.

[0146] In some example implementations, one or more UL resource configurations correspond to a corresponding RSRP threshold (e.g., UL resource configuration n-1 in the UL resource configuration list). If the UE's RSRP is higher than or equal to this RSRP threshold, the corresponding UL resource configuration can be selected.

[0147] In some example implementations, one or more UL resource configurations may correspond to a specific coverage level. The UE can determine the coverage level based on the RSRP. If the UE is in a coverage level, it can select the UL resource configuration corresponding to that coverage level.

[0148] In some example implementations, one or more UL resource configurations may correspond to a coverage level and an RSRP offset. The UE may determine the coverage level based on an RSRP threshold. If the UE is in a coverage level and the UE's RSRP is higher than or equal to the sum of the RSRP threshold corresponding to the coverage level and the RSRP offset, then the corresponding UL resource configuration can be selected (i.e., the UL resource configuration corresponds to that coverage level and RSRP offset).

[0149] In some example implementations, one or more UL resource configurations r may correspond to a TA threshold. The UE can estimate the TA in the serving link or in a combination of the serving link and the feeder link. If the UE's TA is less than or equal to the TA threshold, the corresponding UL resource configuration can be selected. Otherwise, if the UE's TA is higher than the TA threshold, the corresponding UL resource configuration cannot be selected.

[0150] In some example implementations, one or more UL resource configurations r may correspond to a propagation delay threshold. The UE may estimate the propagation delay between the UE and the satellite either in the server link or in a combination of the server link and the feeder link. If the UE's propagation delay is less than or equal to the propagation delay threshold, the corresponding UL resource configuration can be selected. Otherwise, if the UE's propagation delay is higher than the propagation delay threshold, the corresponding UL resource configuration cannot be selected.

[0151] In some example implementations, one or more UL resource configurations r may correspond to a distance threshold. The UE can estimate the distance between the UE and a reference point. The reference point may be indicated by, for example, a base station. The reference point may include at least one of the following: the center of a cell associated with the base station, a satellite, or a base station. If the UE's distance is less than or equal to the distance threshold, the corresponding UL resource configuration can be selected. Otherwise, if the UE's distance is greater than the distance threshold, the corresponding UL resource configuration cannot be selected.

[0152] Example 7: Coexistence of UL resource pool and pre-configured uplink resources (PUR)

[0153] In some embodiments, in addition to the UL resource pool configured by the UL resource configuration list as described above, the UE may be configured with pre-configured UL resources (PURs) separately. Therefore, the coexistence of UL resource pools and PURs is possible.

[0154] In some example implementations, for contention-based Msg3, if the base station configures a UL resource configuration list via, for example, a broadcast message, and the base station also configures a PUR for the UE, the UE can use the PUR to transmit the contention-based Msg3.

[0155] In some example implementations, for contention-based Msg3, if the base station configures a UL resource configuration list via, for example, a broadcast message, and the base station also configures a PUR for the UE. However, if the PUR times out, becomes invalid, or becomes invalid, the UE can select a UL resource configured by a UL resource configuration in the UL resource configuration list.

[0156] In some example implementations, for contention-based Msg3, if the base station configures a UL resource configuration list via, for example, a broadcast message, and the base station also configures a PUR for the UE, the UE can select the resource with the least waiting time. For example, the UE may have pending UL data (e.g., Msg3) to transmit, and the UE will select the nearest UL resource (i.e., with the least waiting time) from either the PUR or the UL resource pool. Therefore, the delay for Msg3 transmission is minimized.

[0157] In some example implementations, the UE is configured with both a PUR (Programming Receiver) and a UL (Universal Utility) resource pool (via a UL resource configuration list). Within a specific time window (or duration), the UE can assign a higher selection priority to the PUR. That is, within the time window, if a transmission opportunity exists in the PUR, the UE can select a UL resource from the PUR. For example, within the time window, the UE might need to transmit Msg3 or trigger a Mobile Origination (MO) procedure. If an available PUR resource exists within the time window, the UE can select a UL resource from the PUR for Msg3 / MO. Otherwise, if no PUR resource is available within the time window, but an available UL resource exists as configured by the UL resource configuration, the UE can select the UL resource configured by the UL resource configuration.

[0158] The time window can be configured by the base station via RRC messages or broadcast messages.

[0159] This embodiment can be used in conjunction with other embodiments. For example, for a UL resource configuration to be selected, the UL resource configuration must meet certain preconditions, such as those specified in previous embodiments, including resource selection conditions, conditions for using UL resources, coverage conditions, etc. As another example, a list of UL resource configurations, or UL resource configurations in a list that have been enabled before they can be selected.

[0160] In this embodiment, Msg3 is used for exemplary purposes. Other types of UL data, such as contention-based UL data, can also be applied.

[0161] Example 8: UE Capabilities

[0162] As described in previous embodiments, the UE can report auxiliary information to the base station, allowing the base station to customize a UL resource configuration list for the UE. This auxiliary information may include UE capability information. In an NTN deployment, various types of devices can exist (e.g., IoT devices, Machine-Type Communication (MTC) devices, etc.). These devices may have specific characteristics. For example, they may be designed with low-cost hardware and have low performance in transmission and / or reception capabilities. These devices may also have limited functionality and may support only a limited set of operations.

[0163] In this embodiment, the UE can report at least one of the following capabilities:

[0164] • Does the UE support contention-based Msg3?

[0165] • Does the UE support contention-based Msg3 for optimization of control plane cellular IoT evolution packet system and 5G system (CioT EPS / 5GS)?

[0166] • Does the UE support contention-based Msg3 for user plane Ciot EPS / 5GS optimization?

[0167] • Does the UE support Layer 1 (L1) acknowledgment in response to contention-based Msg3?

[0168] • Does the UE support initiating a contention-based Msg3 based on at least one of the following conditions:

[0169] ◦ The reference signal received power (RSRP) of the wireless device is higher than the threshold;

[0170] ◦The RSRP change of the UE is below the threshold;

[0171] ◦ The size of the pending UL transmission is less than or equal to the threshold;

[0172] ◦ The size of the pending UL transfer is less than or equal to the TBS of the UL resource configuration in the UL resource configuration list;

[0173] ◦ The wireless device is UL synchronized;

[0174] ◦The timing advance (TA) of UR is less than the threshold;

[0175] ◦UE's TA change is below the threshold;

[0176] ◦The distance between the UE and the reference point is less than a threshold;

[0177] ◦The distance between the UE and the reference point changes less than a threshold;

[0178] ◦ The propagation delay is less than the threshold;

[0179] ◦ The change in propagation delay is less than the threshold; or

[0180] ◦ The current time is within the duration from when the UL resource configuration list takes effect or is received.

[0181] Example 8: Pre-time

[0182] To maintain UL synchronization or keep UL synchronized, the UE can maintain a TA timer for one or more UL resource configurations in the UL resource configuration list.

[0183] Figure 9 A list of example UL resource configurations configured using TA timers is shown. Figure 9 As shown, UL resource configurations 1 and n-1 are each associated with their respective TA timers. TA timers can be configured together with the UL resource configuration list, or configured separately after the UL resource configuration list has been configured.

[0184] In some example implementations, if the UE at the Radio Resource Control (RRC) layer receives a configuration for a TA timer used for UL resource configuration, the MAC or RRC starts this TA timer.

[0185] In some example implementations, if the UE's RRC layer receives a command to release the TA timer, the TA timer can be stopped by the UE's Media Access Control (MAC) layer or RRC layer.

[0186] In some example implementations, if the MAC layer receives a Timing Advance Command (TAC) or an updated TA for the TA timer, the MAC layer can apply a new timer value to the TA timer based on the TAC command or the updated TA, start the TA timer, and notify the RRC layer about the TA value update.

[0187] In some example implementations, if the Random Access Channel (RACH) procedure (or random access procedure) is successfully completed, the MAC layer may start the TA timer and notify the RRC layer about the TA value update.

[0188] In some example implementations, if the TA timer is configured and not running, the corresponding UL resource (configured by the UL resource configuration in the UL resource configuration list) is invalid.

[0189] In some example implementations, UL resources can be considered valid if the UE can pre-compensate the TA before transmitting it in the UL resource.

[0190] In some example implementations, if the TA timer is started and then times out, the corresponding UL resource (configured by the UL resource configuration in the UL resource configuration list) becomes invalid.

[0191] Example 9: Response window for Msg4

[0192] In this embodiment, after transmitting Msg3, a response window is introduced to ensure the reception of Msg4.

[0193] After the UE transmits a contention-based Msg3, the UE can start a timer for the Msg4 response window. The Msg4 response window can also be called the Msg4 receive window. The UE will only attempt to receive Msg4 within this window. That is, while the timer is running, the response window is open and the UE can receive Msg4 within the Msg4 response window. Once the timer expires, the response window is considered closed, and the UE will not attempt to receive Msg4 (corresponding to the previously transmitted Msg3) but will consider Msg4 reception to have failed.

[0194] In some example implementations, the Msg4 response window configuration can be configured by an RRC message or a broadcast message from the base station. The Msg4 response window configuration may include the length of the window and the number of PDCCH events within the window.

[0195] Example 10: RNTI for Msg4

[0196] As mentioned earlier, Msg4 is a response to Msg3. Msg4 can include, for example, RRC messages, downlink control information (DCI), media access control-control element (MAC CE), etc.

[0197] In some example implementations, Msg4 can be transmitted in physical downlink channels, such as the Physical Downlink Control Channel (PDCCH) and / or the Physical Downlink Shared Channel (PDSCH). The base station can use the RNTI to address the physical channel, for example, by scrambling the PDCCH / PDSCH or performing Cyclic Redundancy Check (CRC) on the PDCCH / PDSCH. The scrambling action can also be considered an "addressing" action, where the RNTI can be considered an address (or identifier) ​​because only a receiver with the same RNTI can correctly decode the channel.

[0198] In this disclosure, Msg4 may typically include a control data portion (e.g., DCI) and / or a payload data portion (e.g., data in a contention-resolved PDSCH) scheduled by the control data portion.

[0199] In some example implementations, the C-RNTI (Cell-RNTI) can be used to address Msg4. In connected mode, the UE can be assigned a C-RNTI. The UE can store it and use it later to address Msg4.

[0200] In some example implementations, a PUR-RNTI (Pre-configured Uplink Resource RNTI) can be used to address Msg4. The UE can allocate the PUR-RNTI via, for example, an RRC message from the base station. The UE can store it and use it later to address Msg4.

[0201] In some example implementations, this disclosure introduces a new UE-specific RNTI that is not currently implemented in wireless technologies. The UE can assign this new RNTI via, for example, an RRC message (such as an RRC release message from a base station). The UE can store it and use it later to address Msg4.

[0202] In some example implementations, a common RNTI can be used to address Msg4. One or more, or all, UEs can use this common RNTI to address Msg4.

[0203] In some example implementations, a group RNTI (or group common) can be used to address Msg4. The UE can assign such a group RNTI via, for example, an RRC message (such as an RRC release message from the base station). Multiple UEs can share this same group RNTI. The UE can store it and use it later to address Msg4.

[0204] In some example implementations, the UE can generate the RNTI based on the time-domain and / or frequency-domain resources used by the UE to transmit Msg3. The UE may be pre-configured with a UL resource pool by the base station via, for example, broadcast messages (e.g., System Information Block (SIB) messages), RRC messages, etc. The UL resource pool can be configured using a list of UL resource configurations provided by the base station via these messages. When transmitting Msg3, the UE may be instructed by the base station to use a specific UL resource configuration, or the UE may determine a specific UL resource configuration based on, for example, predefined rules. The UE can then use the UL resources configured by that specific UL resource configuration.

[0205] Based on the time and frequency resources of the selected UL resources for Msg3, the UE can generate a UE-specific or UE-dedicated RNTI. Specifically, one or more of the following parameters related to time and frequency resources can be used to generate the RNTI:

[0206] • The Hypersystem Frame Number (HSFN) of the selected UL resource;

[0207] • The system frame number (SFN) of the selected UL resource;

[0208] • The first subframe of the selected UL resource is named Subsfn;

[0209] • The first resource block (RB), first resource element (RU), or first subcarrier index of the selected UL resource is named ResourceIndex; or

[0210] • The carrier index of the selected UL resource is named carrier.

[0211] For example, RNTI can be generated by a linear function using the parameters described above as variables. For instance, RNTI can be generated using the following equation:

[0212] RNTI=1+A*Subsfn / E+B*SFN / F+C*HSFN / G+D*ResourceIndex / H+P*carrier / Q+I (Equation 1)

[0213] Note that the order of the parameters above is for illustrative purposes only and can be flexibly organized. For example, the above equation can be rewritten as:

[0214] RNTI=1+D*ResourceIndex / H+A*Subsfn / E+B*SFN / F+C*HSFN / G+P*carrier / Q+I (Equation 2)

[0215] Where A, B, C, D, and P are coefficients and can be integers, including 0, 1, or other values. For example, each of these parameters can be determined by the maximum value of its preceding term in the above equation to avoid potential repetition of RNTI. For instance, B could be the maximum value of (A*Subsfn / E), note that ((A*Subsfn / E) is the preceding term of B in the equation (or a term including B).

[0216] Here, E, F, G, H, and Q are coefficients and can be integers, including 0, 1, or other values. Each of these parameters can be determined by the range, upper limit, or lower limit of the corresponding variable in the same term to avoid redundant values. For example, G can be the maximum value of the variable HSFN (i.e., the upper limit of HSFN as defined in the relevant 3GPP standard, such as 1023, or other values ​​depending on the frame structure). In some example implementations, these parameters can be determined by the maximum possible value of the response window to avoid redundant values. For example, if the maximum possible value of the response window is 100 ms, then E can be set to 100. To clarify, the possible values ​​of a variable are values ​​within the range of the variable.

[0217] Parameter I can be an integer including 0 and other values, and it can also be determined by the range of values ​​for RNTI to avoid overlap between RNTI and other RNTI. The range of values ​​for RNTI can be predefined / preconfigured based on relevant 3GPP standards or actual implementation methods.

[0218] In some example implementations, as a variation of the above implementation, the UE can generate an RNTI with additional parameters and an orthogonal overlay code (OCC) index. That is, the UE can generate the RNTI based on the time resources, frequency resources, and OCC index used by the UE to transmit Msg3.

[0219] For UL resources selected from the UL resource pool used for Msg3 transmission, the UL resource configuration may include an OCC index, which may be provided by the base station when configuring the UL resource pool, or by the base station via a separate message, such as an RRC message. For example, the UE may determine a code sequence based on the OCC index and use that code sequence to encode the physical channel carrying Msg3.

[0220] One or more of the following parameters, which are related to time and frequency resources, can be used to generate RNTI:

[0221] • The Hypersystem Frame Number (HSFN) of the selected UL resource;

[0222] • The system frame number (SFN) of the selected UL resource;

[0223] • The first subframe of the selected UL resource is named Subsfn;

[0224] • The first resource block (RB), first resource element (RU), or first subcarrier index of the selected UL resource is named ResourceIndex; or

[0225] • The carrier index of the selected UL resource is named carrier.

[0226] • The OCC index of the selected UL resource is named OCC.

[0227] For example, RNTI can be generated by a linear function using the parameters described above as variables. For instance, RNTI can be generated using the following equation:

[0228] RNTI = 1 + A*Subsfn / E + B*SFN / F + C*HSFN / G + D*ResourceIndex / H + J*OCC / K + P*carrier / Q + I (Equation 3)

[0229] Note that the order of the parameters above is for illustrative purposes only and can be flexibly organized. For example, the above equation can be rewritten as:

[0230] RNTI= 1 + D* ResourceIndex / H + J*OCC / K + A*Subsfn / E + B*SFN / F + C*HSFN / G + P*carrier / Q + I (Equation 4)

[0231] Where A, B, C, D, J, and P are integers, including 0, 1, or other values. For example, each of these parameters can be determined by the maximum value of its preceding term in the above equation. For instance, B could be the maximum value of (A*Subsfn / E), note that ((A*Subsfn / E) is the preceding term of B in the equation (or a term including B).

[0232] Where E, F, G, H, K, and Q are integers, including 0, 1, or other values. Each of these parameters can be determined by the range, upper or lower limit of the corresponding variable in the same term to avoid redundant values. For example, G can be the maximum value of the variable HSFN (i.e., the upper limit of HSFN as defined in the relevant 3GPP standard, such as 1023, or other values ​​depending on the frame structure). In some example implementations, these parameters can be determined by the maximum possible value of the response window to avoid redundant values. For example, if the maximum possible value of the response window is 100 ms, then E can be set to 100.

[0233] Parameter I can be an integer including 0 and other values, and it can also be determined by the range of values ​​for RNTI to avoid overlap between RNTI and other RNTI. The range of values ​​for RNTI can be predefined / preconfigured based on relevant 3GPP standards or actual implementation methods.

[0234] In some example implementations, as a variation of the above implementation, the UE can further generate an RNTI with an additional cyclic shift parameter. That is, the UE can generate the RNTI based on the time resources, frequency resources, OCC index, and cyclic shift used by the UE to transmit Msg3.

[0235] One or more of the following parameters, which are related to time and frequency resources, can be used to generate RNTI:

[0236] • The Hypersystem Frame Number (HSFN) of the selected UL resource;

[0237] • The system frame number (SFN) of the selected UL resource;

[0238] • The first subframe of the selected UL resource is named Subsfn;

[0239] • The first resource block (RB), first resource unit (RU), or first subcarrier index of the selected UL resource is named ResourceIndex;

[0240] • The carrier index of the selected UL resource is named carrier;

[0241] • The OCC index of the selected UL resource is named OCC; or

[0242] • The cyclic shift of the selected UL resource is named CS.

[0243] For example, RNTI can be generated by a linear function using the parameters described above as variables. For instance, RNTI can be generated using the following equation:

[0244] RNTI = 1 + A*Subsfn / E + B*SFN / F + C*HSFN / G + D*ResourceIndex / H + J*OCC / K + M*CS / N + P*carrier / Q + I (Equation 5)

[0245] Note that the order of the parameters above is for illustrative purposes only and can be flexibly organized. For example, the above equation can be rewritten as:

[0246] RNTI= 1 + D* ResourceIndex / H + J*OCC / K + M*CS / N + A*Subsfn / E + B*SFN / F + C*HSFN / G + P*carrier / Q + I (Equation 6)

[0247] Where A, B, C, D, J, M, and P are integers, including 0, 1, or other values. For example, each of these parameters can be determined by the maximum value of its preceding term in the above equation. For instance, B could be the maximum value of (A*Subsfn / E), note that ((A*Subsfn / E) is the preceding term of B in the equation (or a term including B).

[0248] Where E, F, G, H, K, N, and Q are integers, including 0, 1, or other values. Each of these parameters can be determined by the range, upper limit, or lower limit of the corresponding variable in the same term to avoid redundant values. For example, G can be the maximum value of the variable HSFN (i.e., the upper limit of HSFN as defined in the relevant 3GPP standard, such as 1023, or other values ​​depending on the frame structure). In some example implementations, these parameters can be determined by the maximum possible value of the response window to avoid redundant values. For example, if the maximum possible value of the response window is 100 ms, then E can be set to 100.

[0249] Parameter I can be an integer including 0 and other values, and it can also be determined by the range of values ​​for RNTI to avoid overlap between RNTI and other RNTI. The range of values ​​for RNTI can be predefined / preconfigured based on relevant 3GPP standards or actual implementation methods.

[0250] Example 11: RNTI for Msg3

[0251] When a UE transmits Msg3 during random access, it can use an uplink channel, such as the Physical Uplink Shared Channel (PUSCH). The UE can use RNTI to address the PUSCH, for example, by scrambling the PUSCH using RNTI, or by performing Cyclic Redundancy Check (CRC) on the PUSCH.

[0252] One of the following RNTIs is used to address PUSCH for msg3.

[0253] In some example implementations, the C-RNTI can be used to address msg3. In connected mode, the UE can be assigned a C-RNTI. The UE can store it and use it later to address Msg3.

[0254] In some example implementations, the PUR-RNTI can be used to address msg3. The UE can allocate the PUR-RNTI via, for example, an RRC message from the base station. The UE can store it and use it later to address Msg3.

[0255] In some example implementations, this disclosure introduces a new UE-specific RNTI that is not currently implemented in wireless technologies. The UE can assign this new RNTI via, for example, an RRC message (such as an RRC release message from a base station). The UE can store it and use it later to address Msg3.

[0256] In some example implementations, a common RNTI can be used to address Msg3. One or more, or all, UEs can use this common RNTI to address Msg3.

[0257] In some example implementations, a group RNTI (or group common) can be used to address Msg3. The UE can allocate the PUR-RNTI via, for example, an RRC message (such as an RRC release message from the base station). Multiple UEs can share this same group RNTI. The UE can store it and use it later to address Msg3.

[0258] Example 12: Contention Resolution Identifier

[0259] In a contention-based access procedure, if contention exists and Msg3 conflicts (with other Msg3s transmitted simultaneously by other UEs), Msg4 will carry a contention resolution flag to identify the UE and confirm that the contention has been resolved for the identified UE. If the UE receives the contention resolution flag, the UE can consider the access procedure to be successful.

[0260] In this embodiment, various types of RNTIs that can resolve contention are described. These RNTIs can be UE-specific (e.g., dedicated to the UE) and can be used to identify the UE. Therefore, when used to address Msg4, these RNTIs can be used as an identifier for contention resolution, and no further contention resolution identifier is required. For example, these RNTIs can be used for two purposes: 1) scrambling Msg4 (or the PDCCH of Msg4); and 2) contention resolution. That is, if the UE can correctly decode Msg4 using the RNTI, the UE can consider resolving the contention for it, and the UE does not need to further check the contention resolution identifier. In addition, if some RNTIs are not UE-specific (e.g., group common RNTIs), these RNTIs can be combined with other UE-specific information to form an identifier for contention resolution.

[0261] In some example implementations, the UE's C-RNTI (assigned to the UE) is used to address Msg4. If the UE receives a PDCCH (for Msg4) addressed using its assigned C-RNTI, the UE can consider the access procedure successful. That is, if the UE is able to decode the PDCCH for Msg4 using its assigned C-RNTI, then the access procedure is successful.

[0262] In some example implementations, the PUR-RNTI can be used to address Msg4. The UE can allocate the PUR-RNTI via, for example, an RRC message from the base station. If the UE receives a PDCCH (for Msg4) addressed using its allocated PUR-RNTI, the UE can consider the access procedure successful.

[0263] In some example implementations, this disclosure introduces a new UE-specific RNTI that is not currently implemented in wireless technologies. The UE can assign this new RNTI via, for example, an RRC message (such as an RRC release message from a base station). This new RNTI can distinguish the UE from other UEs. If the UE receives a PDCCH addressed using this new RNTI (for Msg4), the UE can consider the access procedure successful.

[0264] In some example implementations, the UE can generate an RNTI based on an OCC index using, for example, Equations 3-6. If the UE receives a PDCCH addressed using this RNTI (for Msg4), the UE can consider the access procedure successful. Note that the RNTI generated by the UE can be sent to the base station in a previous RA step, such as in Msg3.

[0265] In some example implementations, at least a portion of the Common Control Channel (CCCH) may be used in conjunction with a Common RNTI or a Group RNTI as a contention resolution identifier. For example, a portion of the CCCH may include N leftmost bits and / or M rightmost bits of the CCCH, where M and N are integers.

[0266] Further, in the above implementation, the MAC CE of Msg4 (or the MAC CE carried in Msg4) may carry a portion of the CCCH. When the UE receives this MAC CE, and the portion (or the entire CCCH) carried in the MAC CE matches the corresponding portion (or the entire CCCH) of the UE's CCCH, the UE can consider the access procedure successful. If a common RNTI, group RNTI, or another RNTI not specific to the UE is used to address Msg4, the CCCH or a portion of the CCCH is used as a contention resolution identifier.

[0267] In some example implementations, instead of using the MAC CE of Msg4, the DCI of Msg4 (or the DCI associated with Msg) can be used to carry the aforementioned CCCH or a portion of the CCCH.

[0268] In some example implementations, instead of using CCCH, a Temporary Mobile Subscriber Identity (TMSI) or a portion of the TMSI can be used. For example, the N leftmost bits and / or M rightmost bits of the TMSI can be carried by the MAC CE and / or DCI of Msg4 (M and N are integers). If the TMSI matches the UE's TMSI, or if a portion of the TMSI matches the corresponding portion of the UE's TMSI, the UE can consider the access procedure successful.

[0269] In some example implementations, instead of using TMSI, short-end TMSI (S-TMSI) can be used similarly.

[0270] In some example implementations, the TMSI can be carried jointly by the PDCCH of Msg4 and the MAC CE of Msg4. A portion of the TMSI can be carried in the PDCCH Msg4 (e.g., the N leftmost bits and / or M rightmost bits of the TMSI), and the remainder of the TMSI is carried in the MAC CE of Msg4. If the UE receives this MAC CE and DCI, and the carried TMSI matches the UE's TMSI, the UE can consider the access procedure successful. Therefore, if a common RNTI, a group RNTI, or another RNTI that is not UE-specific is used to address Msg4, the TMSI is used as a contention resolution identifier.

[0271] In some example implementations, S-TMSI can be used instead of TMSI as described above.

[0272] Example 13: RNTI in Msg3

[0273] In this embodiment, the base station can identify the UE that sent Msg3 during the access process via certain identification information carried in Msg3 (e.g., a UE-specific RNTI dedicated to the UE). Furthermore, when the base station responds using Msg4, it can embed the identification information therein to address Msg4.

[0274] In some example implementations, Msg3 may carry a UE-specific RNTI as described in previous embodiments. For example, the UE-specific RNTI may include: a C-RNTI for the UE; a PUR-RNTI for the UE; a newly introduced (in this disclosure) UE-specific RNTI that may be assigned by the base station; an RNTI generated based on: time-domain / frequency-domain resources for transmitting Msg3, and / or an OCC index uniquely assigned for Msg3 transmission, and / or a cyclic shift assigned for Msg3 transmission. The Msg3 may include, for example, an RRCConnectionRequest message; an RRCEarlyDataRequest message; an RRCConnectionResumeRequest message; an RRCSetupRequest message; an uplink (UL) Non-Access Stratum (NAS) Packet Data Unit (PDU); or data (payload) in a Data Radio Bearer (DRB), and the like. In this way, the base station can identify the UE upon receiving Msg3 and address Msg4 using the same RNTI carried in Msg3.

[0275] In some example implementations, the Media Access Control-Control Element (MAC CE) of Msg3 may be used to carry the aforementioned UE-specific RNTI. When the UE transmits Msg3, it may include an RRCConnectionRequest message or an RRCEarlyDataRequest message, along with the MAC CE carrying the UE-specific RNTI.

[0276] In some example implementations, the MAC CE mentioned above can also be considered as part of Msg3.

[0277] Example 14: RNTI allocated by the base station and carried in Msg4

[0278] In connected mode, the UE will require an identifier, such as C-RNTI, to serve as an address or identifier for messages targeting the UE. In this embodiment, such an identifier can be integrated into the access procedure. For example, such an identifier can be sent to the UE via Msg4.

[0279] In some example implementations, the base station may assign the C-RNTI to the UE and use the PDCCH for Msg4 to carry the C-RNTI.

[0280] In some example implementations, the base station may assign the C-RNTI to the UE and use the MACCE for Msg4 to carry the C-RNTI.

[0281] In some example implementations, instead of using the base station to assign a specific RNTI to the UE (e.g., a C-RNTI), the RNTI can be generated by the UE side. As described in previous embodiments, the UE can generate a UE-specific RNTI based on resources used for transmitting Msg3. These resources can include at least one of the following: time-domain resources, frequency-domain resources, code-domain resources (e.g., an OCC index, which is used to determine the OCC sequence used to encode PUCCH / PUSCH), or cyclic shifts. When transmitting Msg3 to the base station, Msg3 can carry the UE-generated RNTI. From the base station side, the base station can take the UE-generated RNTI and further pass the same RNTI down to the UE via, for example, Msg4. When receiving Msg4 (along with the UE's previously generated RNTI), the UE can treat this RNTI as a C-RNTI and save it for later use.

[0282] Example 15: Msg3 retransmission

[0283] When the wireless network is congested and / or when a UE's msg3 conflicts with other msg3s sent simultaneously by other UEs, it may be necessary to perform a Msg3 retransmission.

[0284] Ideally, upon observing a Msg3 collision, the base station can send a command to the affected UE to retransmit the Msg3. However, in contention-based random access procedures, the base station may be unable to distinguish between conflicting Msg3s, and therefore such commands for Msg3 retransmission may not be sent. In this embodiment, various methods are described to enable the UE to autonomously determine whether a Msg3 retransmission is necessary, and the UE can take further actions to reduce the probability of further Msg3 collisions.

[0285] In some example implementations, if the UE does not receive Msg4 as a response to Msg3 within the Msg4 response window, the UE can perform an autonomous Msg3 retransmission. For example, the UE can select the next available transmission opportunity (i.e., the most recent available transmission opportunity) from a pre-configured UL resource pool (e.g., for Msg3) and retransmit Msg3. Furthermore, the UE can add associated Hybrid Automatic Repeat Request (HARQ) information to the HARQ entity of Msg3.

[0286] In some example implementations, if the UE does not receive Msg4 as a response to Msg3 within the Msg4 response window, the UE can perform an autonomous Msg3 retransmission. To reduce the probability of further Msg3 collisions, the UE can randomly select a UL transmission timing that falls within the duration. For example, if the Msg4 response window times out at time point A, the UE can assume that the Msg3 transmission failed at time point A. Then, within the duration starting from time point A, the UE can randomly select a UL transmission timing to retransmit Msg3. (See also...) Figure 10 To illustrate this example. Figure 10 In the process, the initial Msg3 transmission was determined to have failed at time point A (after the Msg4 response window timed out). From time point A, there is a duration of 1010 for selecting the UL resource (or UL transmission timing). For example... Figure 10 As shown, there are four UL transmission opportunities: 1002, 1004, 1006, and 1008. The UE can randomly select a UL transmission opportunity and use it for Msg3 retransmission.

[0287] For another example, starting with the UL transmission opportunity closest to time point A, the UE can randomly select a UL transmission opportunity from the next N UL transmission opportunities and use the selected UL transmission opportunity to retransmit Msg3. The duration and N can be predefined, or configured by the base station via, for example, an RRC message or a broadcast message. (See reference...) Figure 10Assuming N=3, starting from time point A, the next 3 UL transmission opportunities (i.e., 1002, 1004, 1006) are available, and the UE can randomly select the UL transmission opportunity from them.

[0288] Example 16: Msg3 retransmission delay

[0289] During the access process (e.g., using two steps, Msg3 and Msg4), collisions may occur when multiple UEs attempt to transmit Msg3 simultaneously during the access process, leading to interference and signal overlap. The base station may struggle to decode the conflicting messages. Collisions must be properly resolved to prevent congestion, as multiple UEs will continue to compete for uplink resources, potentially causing further UE access delays.

[0290] In this embodiment, various methods are described to mitigate collisions via improved Msg3 retransmission coordination. These methods enable more efficient resource utilization and minimal latency.

[0291] At higher levels, if msg3 collisions and / or uplink congestion are observed, the base station can instruct the UE to delay retrying access, and the base station can control the delayed access.

[0292] In some example implementations, the base station can send a backoff indication via the PDCCH for Msg4. If the UE receives this indication from the PDCCH, the UE can delay random access; that is, instead of retransmitting Msg3, the UE will add a delay to the retransmission.

[0293] In some example implementations, the base station may send a backoff indication via the MAC CE for Msg4. If the UE receives this indication from the MAC CE, the UE may delay random access.

[0294] In some example implementations, the base station may further transmit a delay time (or wait time) via the PDCCH for Msg4. The UE can then transmit the delay time indicated by the random access delay. This delay time may be in the form of a duration, or the number of transmission opportunities presented in the UL resource pool, and the like. For example, the UE may wait for the indicated duration, or skip multiple transmission opportunities as indicated. Note that the UE may be configured with a UL resource pool by the base station (e.g., via a UL resource configuration list, where each UL resource configuration in the list corresponds to a UL resource).

[0295] In some example implementations, the base station may similarly transmit the delay time (or waiting time) via the MAC CE for Msg4.

[0296] In some example implementations, the UE can delay (postpone) access by a randomly selected duration. The maximum duration can be predefined or preconfigured by the base station via, for example, an RRC message or a broadcast message. The maximum duration can also be carried in the PDCCH or MAC CE for Msg4. The UE can select a random value within the maximum duration as the delay value. Alternatively, the UE can skip a random number of transmission contentions to postpone random access. The maximum skipped transmission contention can be predefined or preconfigured by the base station via, for example, an RRC message or a broadcast message. The maximum skipped transmission contention can also be carried in the PDCCH or MAC CE for Msg4.

[0297] Note that the above implementation methods can be combined. For example, when the UE receives a backoff indication, the UE can postpone the next Msg3 attempt for a duration pre-configured or indicated by the base station, or the UE can postpone the next Msg3 attempt for a random delay, or the UE can skip multiple transmission opportunities pre-configured or indicated by the base station.

[0298] Example 17: Msg3 Failure Handling

[0299] In this embodiment, various methods for handling Msg3 failures are described. Msg3 transmission can be contention-based. For example, multiple UEs can simultaneously transmit their respective Msg3s using shared resources configured by the UL resource configuration. In this embodiment, various thresholds are used to determine various types of failures. These thresholds can be configured by the base station via, for example, RRC messages or broadcast messages.

[0300] In some example implementations, when the UE's Media Access Control (MAC) layer detects or considers that the Msg3 transmission has failed, the MAC layer may indicate the failure to the UE's RRC layer.

[0301] In some example implementations, if the number of retransmissions for Msg3 exceeds a threshold, the MAC layer considers Msg3 to have failed based on contention.

[0302] In some example implementations, if a retransmission exceeds a time length threshold, the UE's MAC layer considers the contention-based msg3 to have failed. This time length threshold can be configured by the base station via, for example, an RRC message or a broadcast message.

[0303] In some example implementations, if the UE's MAC layer deems the contention-based msg3 transmission a failure, the MAC layer can indicate the failure to the UE's RRC layer. For example, if the UE performs msg3 transmission more than a threshold number of times or retransmissions exceed a time length threshold, the MAC layer can indicate the failure to the UE's RRC layer.

[0304] In some example implementations, if the RRC layer receives an indication of a transmission failure for contention-based msg3, the RRC layer considers contention-based msg3 to have failed.

[0305] In some example implementations, if the RRC layer receives an indication of a transmission failure based on contention-based msg3, the RRC can trigger a retransmission based on contention-based msg3.

[0306] In some example implementations, if the number of times the RRC triggers a contention-based msg3 transmission exceeds a threshold, the RRC considers the contention-based msg3 transmission to have failed.

[0307] In some example implementations, if the duration of a contention-based msg3 transmission triggered by the RRC layer exceeds a threshold, the RRC considers the contention-based msg3 transmission to have failed. That is, from the start of a msg3 transmission triggered by the RRC layer, there exists a time window (e.g., 10 seconds) for attempting the Msg3 transmission and possible retransmissions. If the Msg3 transmission fails within this time window, the RRC layer can consider the msg3 transmission to have failed.

[0308] In some example implementations, if the RRC layer considers that the contention-based msg3 has failed, the RRC can indicate that the Non-Access Stratum (NAS) RRC has failed.

[0309] In some example implementations, if the RRC layer considers that the contention-based msg3 has failed, the RRC layer may discard the UL resource pool, which is configured to provide UL resources for UL transmissions (e.g., Msg3 transmissions).

[0310] In some example implementations, if the RRC layer determines that the contention-based msg3 has failed and the conditions for pre-configured uplink resources (PUR) are met, the RRC layer can trigger a PUR procedure to use the PUR resources to transmit Msg3.

[0311] In some example implementations, if the RRC layer determines that the contention-based msg3 has failed and the conditions for EDT / CG-SDT are met, the RRC layer may trigger the Early Data Transmission / Configured Grant (EDT / CG-SDT) procedure.

[0312] In this disclosure, embodiments are described individually only for ease of understanding and description. These embodiments are for illustrative purposes and can be combined in any order without conflict. For example, an embodiment for processing Msg3 can be combined with an embodiment for processing Msg4 to form a new embodiment, since Msg4 follows Msg3 during access. Embodiments for processing message error detection and / or retransmission can be combined with corresponding embodiments for processing messages. Embodiments for processing RNTI can be combined with embodiments for processing Msg3 and / or Msg4. In this disclosure, messages can be addressed by RNTI; for example, PDCCH / PDSCH / PUCCH / PUSCH can be scrambled by RNTI for addressing purposes. Messages can also carry RNTI as payload data, so RNTI can be sent to the receiver.

[0313] The above description and accompanying drawings provide specific example embodiments and implementations. However, the described subject matter can be embodied in many different forms, and therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the example embodiments set forth herein. A reasonably broad scope is intended for the claimed or covered subject matter. Among other things, the subject matter can be embodied as a method, apparatus, component, system, or non-transitory computer-readable medium for storing computer code. Thus, embodiments can take the form of, for example, hardware, software, firmware, storage media, or any combination thereof. For example, the method embodiments described above can be implemented by a component, apparatus, or system including a memory and a processor by executing computer code stored in the memory.

[0314] Throughout the specification and claims, terms may have nuanced meanings beyond those explicitly stated, implied or suggested in the context. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to different embodiments. For example, the subject matter intended to be claimed includes combinations of all or some of the exemplary embodiments.

[0315] Generally, terms can be understood, at least in part, from their usage in the context. For example, the terms “and,” “or,” or “and / or,” as used herein, can come in a variety of meanings, which can depend at least in part on the context in which such terms are used. Typically, “or,” when used in an associative list, such as A, B, or C, is intended to mean A, B, and C, used here in an inclusive sense, and A, B, or C, used here in an exclusive sense. Furthermore, depending at least in part on the context, the term “one or more” as used herein can be used to describe any feature, structure, or characteristic in a singular sense or in a plural sense. Similarly, terms such as “a,” “one,” or “this” can also be understood to convey a singular or plural usage, depending at least in part on the context. Moreover, the term “based on” can be understood to not necessarily convey an exclusive set of factors and can instead allow for additional factors that are not necessarily explicitly described, again, depending at least in part on the context.

[0316] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable using this solution should be or should be included in any single implementation thereof. Rather, references to features and advantages are to be understood as meaning that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, the discussion of features and advantages, and similar language throughout this specification, may, but does not necessarily, refer to the same embodiments.

[0317] Furthermore, the features, advantages, and characteristics described in this solution can be combined in one or more embodiments in any suitable manner. Those skilled in the art will recognize that, based on the description herein, this solution can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages that may not be present in all embodiments of this solution may be recognized in certain embodiments.

Claims

1. A method for wireless communication performed by a wireless device, comprising: Receive a first message from a network node carrying an uplink (UL) resource configuration list, the uplink (UL) resource configuration list being used to transmit UL messages associated with an access procedure, the access procedure including one of the following: a contention-based access procedure or a contention-free access procedure; and The UL message is transmitted to the network node using UL resources configured from UL resource configuration list or from pre-configured uplink resources (PUR).

2. The method according to claim 1, wherein, The UL message includes Msg3 of the access procedure.

3. The method according to claim 1, wherein, The first message includes at least one of the following: a Radio Resource Control (RRC) message; or a broadcast message.

4. The method according to claim 1, wherein, Each UL resource configuration in the UL resource configuration list applies to the corresponding UL resource and includes at least one of the following: An index that identifies each UL resource configuration in the UL resource configuration list; The start time of the corresponding UL resource; The corresponding UL resource's resource block (RB) number; The RU number of the corresponding UL resource; The subcarrier number of the corresponding UL resource; The periodicity of the corresponding UL resources; The corresponding UL resource's transport block size (TBS); The anchor carrier or non-anchor carrier of the corresponding UL resource; The physical downlink control channel (PDCCH) search space configuration of the corresponding UL resource; The number of times the corresponding UL resource is repeated; The subcarrier configuration of the corresponding UL resource; or The modulation and encoding scheme of the corresponding UL resources.

5. The method according to any one of claims 1-4, wherein, The UL message is based on contention.

6. The method according to claim 5, wherein, The first message includes broadcast messages.

7. The method according to claim 5, wherein: The first message includes a System Information Block (SIB) message; and The UL resource configuration list is shared by the wireless device and other wireless devices.

8. The method according to claim 5, wherein, Before receiving the first message, the method further includes: A second message carrying auxiliary information is transmitted to the network node, the auxiliary information being used by the network node to determine the UL resource configuration list.

9. The method according to claim 8, wherein: There is one UL resource configuration in the UL resource configuration list; and Each of the first message and the second message includes a Radio Resource Control (RRC) message.

10. The method according to claim 8, wherein, The auxiliary information includes at least one of the following: UE characteristics; or desired UL resource configuration.

11. The method according to claim 8, wherein, The first message includes an RRC release message.

12. The method according to claim 5, wherein: The method further includes: Send a third message carrying auxiliary information to the network node, the auxiliary information being used by the network node to determine the UL resource configuration list; and Receive an indication of a target UL resource configuration from the UL resource configuration list from the network node; and Transmitting the UL message using the UL resources configured by the UL resource configuration in the UL resource configuration list includes: The UL message is transmitted to the network node using the UL resource configured by the target UL resource configuration.

13. The method according to claim 12, wherein, The instruction includes an index that identifies the target UL resource configuration from the UL resource configuration list.

14. The method according to claim 5, wherein: There is one UL resource configuration in the UL resource configuration list, named the target UL resource configuration; The method further includes: Receive an enable indicator from the network node indicating whether to enable or disable the target UL resource configuration; and Transmitting the UL message using the UL resources configured by the UL resource configuration in the UL resource configuration list includes: The UL message is transmitted to the network node using the UL resource configured by the target UL resource configuration.

15. The method according to claim 5, wherein, Each UL resource configuration in the UL resource configuration list is associated with a corresponding group identifier, and wherein transmitting the UL message using the UL resource configured by the UL resource configuration in the UL resource configuration list includes: Receive group identifier allocation from the network node to allocate group identifiers to the wireless device; Select a target UL resource configuration from the UL resource configuration list, such that the wireless device and the target UL resource configuration have the same group identifier; and The UL message is transmitted to the network node using the UL resource configured by the target UL resource configuration.

16. The method according to any one of claims 1-4, wherein, Each UL resource configuration in the UL resource configuration list is associated with a validity region, and each UL resource configuration is valid only when the wireless device is located in the validity region.

17. The method according to claim 16, wherein, The validity region is represented by at least one of the following: List of community signs; Satellite identifier list; or List of tracking area identifiers.

18. The method according to any one of claims 1-4, wherein, Each UL resource configuration in the UL resource configuration list is associated with an validity period, and each UL resource configuration is valid only if the application time meets the constraints imposed by the validity period.

19. The method according to any one of claims 18, wherein, The validity period is represented by at least one of the following: One or more transmission opportunities; Duration, wherein the duration begins from one of the following: a first transmission timing in one or more transmission timings; or when each UL resource configuration in the UL resource configuration list is active or configured.

20. The method according to any one of claims 1-4, wherein: There is one UL resource configuration in the UL resource configuration list, named the target UL resource configuration; The first message includes one of the following: an RRC message or a broadcast message; The start time of the first UL resource timing configured by the target UL resource configuration is determined by at least one of the following: Periodicity in units of HSF (supersystem frames) or SF (system frames); The HSF reference frame number, wherein the last subframe of the first transmission or the last subframe of the last transmission of the first message is named HSFN. Ref ; HSFN for the HSF used in the first UL resource timing; The offset from the start of the HSF within the period determined by the periodicity; The SFN (system frame number) of the SF in the HSF; or The subframes in the SFN.

21. The method according to claim 20, wherein, The HSFN is determined by the following: HSFN = (HSFN Ref +offset) mod 1024.

22. The method of any one of claims 1-4, further comprising, in response to the UL message pending, selecting the UL resource configured by a UL resource configuration from the UL resource configuration list via one of the following: From a time-domain perspective, selecting the UL resource minimizes the latency of the UL resource. Select the UL resource such that the capacity of the UL resource is greater than or equal to the size of the UL message; or From a frequency domain perspective, the frequency domain timing for the UL resource configuration is randomly selected.

23. The method according to any one of claims 1-5, further comprising determining to transmit the UL message in response to at least one of the following conditions: The reference signal received power (RSRP) of the wireless device is higher than the threshold. The RSRP change of the wireless device is below the threshold. The size of the pending UL transmission is less than or equal to the threshold; The size of the pending UL transmission is less than or equal to the TBS of the UL resource configuration in the UL resource configuration list; The wireless device is UL synchronized; The timing advance (TA) of the wireless device is less than the threshold; The TA change of the wireless device is below the threshold; The distance between the wireless device and the reference point is less than a threshold. The change in distance between the wireless device and the reference point is less than a threshold. The propagation delay is less than the threshold; The change in propagation delay is less than the threshold; or The current time is within the duration since the UL resource configuration list became effective or was received.

24. The method according to claim 23, wherein, The reference point includes at least one of the following: The center of the cell associated with the network node; The geographical location of the network node; or satellite.

25. The method according to claim 23, wherein, The duration ends when a UL resource configuration in the UL resource configuration list becomes invalid.

26. The method according to any one of claims 1-5, wherein, Each UL resource configuration in the UL resource configuration list corresponds to or applies to at least one of the following: RSRP threshold; Coverage level; The coverage level and the RSRP threshold; Timing advance (TA) threshold; Propagation delay threshold; or Distance threshold.

27. The method according to claim 26, wherein, Each of the RSRP threshold, the TA threshold, the propagation delay threshold, and the distance threshold is predefined or transmitted to the wireless device via a broadcast message or an RRC message.

28. The method according to any one of claims 26-27, further comprising selecting the UL resource configuration from the UL resource configuration list in one of the following ways: In response to the RSRP of the wireless device being higher than or equal to the RSRP threshold, the UL resource configuration is selected from the UL resource configuration list such that the UL resource configuration corresponds to the RSRP threshold; In response to the wireless device being at the coverage level, the UL resource configuration is selected from the UL resource configuration list such that the UL resource configuration corresponds to the coverage level; In response to the wireless device being in the coverage level and the wireless device's RSRP being higher than or equal to the RSRP threshold, the UL resource configuration is selected from the UL resource configuration list such that the UL resource configuration corresponds to the coverage level and the RSRP threshold; In response to the timing advance (TA) of the wireless device being less than or equal to the TA threshold, the UL resource configuration is selected from the UL resource configuration list such that the UL resource configuration corresponds to the TA threshold; In response to the propagation delay of the wireless device being less than or equal to the propagation delay threshold, a UL resource configuration is selected from the UL resource configuration list such that the UL resource configuration corresponds to the propagation delay threshold; or In response to the distance between the wireless device and the reference point being less than or equal to the distance threshold, the UL resource configuration is selected from the UL resource configuration list such that the UL resource configuration corresponds to the distance threshold.

29. The method according to any one of claims 1-5, wherein, The PUR is configured separately from the UL resource configuration list, and the PUR is dedicated to the wireless device.

30. The method of claim 29, further comprising selecting the UL resource via one of the following methods: Select the UL resource from the PUR; In response to the PUR timeout or invalidity, select the UL resource configured by the UL resource configuration in the UL resource configuration list; Based on the minimum waiting time, the UL resource is selected from the UL resource configuration configured by the UL resource configuration in the UL resource configuration list or from the PUR; In response to the availability of the PUR, the PUR is selected as the UL resource; otherwise, the UL resource configured by the UL resource configuration in the UL resource configuration list is selected; or If the PUR is available within the time window, select the PUR as the UL resource; otherwise, select the UL resource configured by the UL resource configuration in the UL resource configuration list.

31. The method according to any one of claims 1-5, further comprising transmitting to the network node a fourth message carrying the UE capabilities of the wireless device, the UE capabilities including at least one of the following: Does the wireless device support contention-based Msg3? Does the wireless device support contention-based Msg3 for optimizing control planar cellular IoT evolution packet system and 5G system (CioT EPS / 5GS)? Does the wireless device support contention-based Msg3 for user plane Ciot EPS / 5GS optimization? Does the wireless device support Layer 1 (L1) acknowledgment in response to contention-based Msg3? or Does the wireless device support initiating a contention-based Msg3 based on at least one of the following conditions: The reference signal received power (RSRP) of the wireless device is higher than the threshold. The RSRP change of the wireless device is below the threshold. The size of the pending UL transmission is less than or equal to the threshold; The size of the pending UL transmission is less than or equal to the TBS of the UL resource configuration in the UL resource configuration list; The wireless device is UL synchronized; The timing advance (TA) of the wireless device is less than the threshold; The TA change of the wireless device is below the threshold; The distance between the wireless device and the reference point is less than a threshold. The change in distance between the wireless device and the reference point is less than a threshold. The propagation delay is less than the threshold; The propagation delay change is less than the threshold; or The current time is within the duration since the UL resource configuration list came into effect or was being received.

32. The method according to any one of claims 1-5, further comprising at least one of the following: In response to the radio resource control (RRC) layer of the wireless device receiving configuration information for a timing advance (TA) timer associated with a UL resource configuration in the UL resource configuration list, the TA timer is started via the RRC layer or the media access control (MAC) layer of the wireless device. In response to the RRC layer receiving a release command to release the TA timer, the TA timer is stopped via the RRC layer or the MAC layer; In response to the MAC layer receiving a Timing Advance Control (TAC) command or an instruction to update the timer in the TA: The MAC layer applies a new timer value to the TA timer based on the TAC command or the instruction, and the MAC layer starts the TA timer. as well as The MAC layer notifies the RRC layer of the new timer value of the TA timer; In response to the successful completion of the Random Access Channel (RACH) procedure, the MAC layer starts the TA timer and notifies the RRC layer of the new timer value of the TA timer. In response to the TA timer not running, the UL resource configured by the UL resource configuration in the UL resource configuration list is considered invalid; In response to the wireless device being able to pre-compensate TA before transmitting the UL message, the UL resource configured by the UL resource configuration in the UL resource configuration list is considered valid; or In response to the TA timer timeout, the UL resource configured by the UL resource configuration in the UL resource configuration list is considered invalid.

33. The method according to any one of claims 1-5, wherein, The UL message includes Msg3 of the access procedure, and the method further includes: After transmitting the UL message, a timer is started for the Msg4 receive window; and Within the Msg4 receive window, the Physical Downlink Control Channel (PDCCH) is monitored for Msg4, which is a response to Msg3.

34. The method of claim 33, further comprising: In response to the timer timeout, it is considered that the reception of Msg4 has failed.

35. The method according to claim 33, wherein: The Msg4 receive window is configured by an RRC message or a broadcast message from the network node; and The configuration of the Msg4 receive window includes at least one of the following: the length of the Msg4 receive window; or the number of PDCCH timings in the Msg4 receive window.

36. The method according to any one of claims 1-4, wherein: The access process includes the contention-free access process; The UL resource configurations in the UL resource configuration list include Orthogonal Cover Code (OCC) indexes; as well as The transmission of the UL message includes: The UL message is transmitted to the network node using UL resources configured by the UL resource configuration in the UL resource configuration list, wherein the physical channel carrying the UL message is encoded with an OCC sequence indicated by the OCC index.

37. The method of claim 36, wherein, The physical channel includes at least one of the following: a physical uplink control channel or a physical uplink shared channel.

38. A method for wireless communication performed by a network node, comprising: A first message carrying an uplink (UL) resource configuration list is transmitted to the wireless device. This uplink (UL) resource configuration list is used to transmit UL messages associated with an access procedure, which includes one of the following: a contention-based access procedure or a contention-free access procedure; and The wireless device receives the UL message transmitted in a UL resource, which is configured by UL resource configuration in the UL resource configuration list or from a pre-configured uplink resource (PUR).

39. The method according to claim 38, wherein, The UL message includes Msg3 of the access procedure.

40. The method of claim 38, wherein, The first message includes at least one of the following: a Radio Resource Control (RRC) message; or a broadcast message.

41. The method according to claim 38, wherein, Each UL resource configuration in the UL resource configuration list applies to the corresponding UL resource and includes at least one of the following: An index that identifies each UL resource configuration in the UL resource configuration list; The start time of the corresponding UL resource; The corresponding UL resource's resource block (RB) number; The RU number of the corresponding UL resource; The subcarrier number of the corresponding UL resource; The periodicity of the corresponding UL resources; The corresponding UL resource's transport block size (TBS); The anchor carrier or non-anchor carrier of the corresponding UL resource; The physical downlink control channel (PDCCH) search space configuration of the corresponding UL resource; The number of times the corresponding UL resource is repeated; The subcarrier configuration of the corresponding UL resource; or The modulation and encoding scheme of the corresponding UL resources.

42. The method according to any one of claims 38-41, wherein, The UL message is based on contention.

43. The method according to claim 42, wherein, The first message includes broadcast messages.

44. The method according to claim 42, wherein: The first message includes a System Information Block (SIB) message; and The UL resource configuration list is shared by the wireless device and other wireless devices.

45. The method according to claim 42, wherein, Before transmitting the first message, the method further includes: The network node receives a second message carrying auxiliary information, which is used by the wireless device to determine the UL resource configuration list.

46. ​​The method of claim 45, wherein: There is one UL resource configuration in the UL resource configuration list; and Each of the first message and the second message includes a Radio Resource Control (RRC) message.

47. The method according to claim 45, wherein, The auxiliary information includes at least one of the following: UE characteristics; or desired UL resource configuration.

48. The method according to claim 45, wherein, The first message includes an RRC release message.

49. The method according to claim 42, wherein: The method further includes: Receive a third message carrying auxiliary information from the wireless device, the auxiliary information being used by the network node to determine the UL resource configuration list; and Transmit to the wireless device an indication of a target UL resource configuration from the UL resource configuration list; and Receiving the UL message from the wireless device includes: The UL message is received from the wireless device using the UL resources configured by the target UL resource configuration.

50. The method according to claim 49, wherein, The instruction includes an index that identifies the target UL resource configuration from the UL resource configuration list.

51. The method according to claim 42, wherein: The UL resource configuration list contains only one UL resource configuration, named the target UL resource configuration; The method further includes: Transmit an enable indicator to the wireless device indicating whether to enable or disable the target UL resource configuration; and Receiving the UL message from the wireless device includes: The UL message is received from the wireless device using the UL resources configured by the target UL resource configuration.

52. The method according to any one of claims 38-41, wherein, Each UL resource configuration in the UL resource configuration list is associated with a validity region, and each UL resource configuration is valid only when the wireless device is located in the validity region.

53. The method according to claim 52, wherein, The validity region is represented by at least one of the following: List of community signs; Satellite identifier list; or List of tracking area identifiers.

54. The method according to any one of claims 38-41, wherein, Each UL resource configuration in the UL resource configuration list is associated with an validity period, and each UL resource configuration is valid only if the application time meets the constraints imposed by the validity period.

55. The method according to any one of claims 54, wherein, The validity period is represented by at least one of the following: One or more transmission opportunities; Duration, wherein the duration begins from one of the following: a first transmission timing in one or more transmission timings; or when each UL resource configuration in the UL resource configuration list is active or configured.

56. The method according to any one of claims 38-41, wherein: There is one UL resource configuration in the UL resource configuration list, named the target UL resource configuration; The first message includes one of the following: an RRC message or a broadcast message; The start time of the first UL resource timing configured by the target UL resource configuration is determined by at least one of the following: Periodicity in units of HSF (supersystem frames) or SF (system frames); The HSF reference frame number, wherein the last subframe of the first transmission or the last subframe of the last transmission of the first message is named HSFN. Ref ; HSFN for the HSF used in the first UL resource timing; The offset from the start of the HSF within the period determined by the periodicity; The SFN (system frame number) of the SF in the HSF; or The subframes in the SFN.

57. The method according to claim 56, wherein, The HSFN is determined by the following: HSFN = (HSFN Ref +offset) mod 1024.

58. The method according to any one of claims 38-42, wherein, Each UL resource configuration in the UL resource configuration list corresponds to or applies to at least one of the following: RSRP threshold; Coverage level; The coverage level and the RSRP threshold; Timing advance (TA) threshold; Propagation delay threshold; or Distance threshold.

59. The method according to claim 58, wherein, Each of the RSRP threshold, the TA threshold, the propagation delay threshold, and the distance threshold is predefined or transmitted to the wireless device via a broadcast message or an RRC message.

60. The method according to any one of claims 38-42, wherein, The PUR is configured separately from the UL resource configuration list, and the PUR is dedicated to the wireless device.

61. The method according to any one of claims 38-42, further comprising receiving from the wireless device a fourth message carrying UE capabilities of the wireless device, the UE capabilities including at least one of the following: Does the wireless device support contention-based Msg3? Does the wireless device support contention-based Msg3 for optimizing control planar cellular IoT evolution packet system and 5G system (CioT EPS / 5GS)? Does the wireless device support contention-based Msg3 for user plane Ciot EPS / 5GS optimization? Does the wireless device support Layer 1 (L1) acknowledgment in response to contention-based Msg3? or Does the wireless device support initiating a contention-based Msg3 based on at least one of the following conditions: The reference signal received power (RSRP) of the wireless device is higher than the threshold. The RSRP change of the wireless device is below the threshold. The size of the pending UL transmission is less than or equal to the threshold; The size of the pending UL transmission is less than or equal to the TBS of the UL resource configuration in the UL resource configuration list; The wireless device is UL synchronized; The timing advance (TA) of the wireless device is less than the threshold; The TA change of the wireless device is below the threshold; The distance between the wireless device and the reference point is less than a threshold. The change in distance between the wireless device and the reference point is less than a threshold. The propagation delay is less than the threshold; The change in propagation delay is less than the threshold; or The current time is within the duration since the UL resource configuration list became effective or was received.

62. The method according to any one of claims 38-41, wherein: The access process includes the contention-free access process; The UL resource configurations in the UL resource configuration list include Orthogonal Cover Code (OCC) indexes; as well as Receiving the UL message includes: The UL message is received from the wireless device using UL resources configured by the UL resource configuration in the UL resource configuration list, wherein the physical channel carrying the UL message is encoded with an OCC sequence indicated by the OCC index.

63. The method according to claim 62, wherein, The physical channel includes at least one of the following: a physical uplink control channel or a physical uplink shared channel.

64. A device for wireless communication, comprising a memory for storing computer instructions and a processor for communicating with said memory, wherein, When the processor executes the computer instructions, the processor is configured to implement the method of any one of claims 1-63.

65. A computer program product comprising a non-transitory computer-readable program medium having computer code stored thereon, the computer code causing the one or more processors, when executed, to perform the method of any one of claims 1-63.

Images