Transmitting data from mobile source over dedicated preconfigured uplink resources

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive information related to a dedicated preconfigured uplink resource (DPUR) in a message that releases the user equipment to an idle mode or an inactive mode. For example, in some aspects, information related to the DPUR may identify one or more uplink resources allocated to the user equipment to enable the user equipment to initiate uplink data transmissions in the idle mode or inactive mode. While in the idle mode or inactive mode, the user equipment may transmit uplink data based at least in part on information related to the DPUR. Numerous other aspects are provided herein.

Description

[0001] This application is a divisional application of a Chinese patent application with an application date of August 20, 2019, application number 201980099357.0, and name “Sending mobile-originated data via dedicated pre-configured uplink resources in idle mode or inactive mode”. Technical Field

[0002] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for transmitting mobile originated data over dedicated pre-configured uplink resources while in an idle mode or inactive mode. Background Art

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access systems (CDMA), time division multiple access systems (TDMA), frequency division multiple access systems (FDMA), orthogonal frequency division multiple access systems (OFDMA), single carrier frequency division multiple access systems (SC-FDMA), time division synchronous code division multiple access systems (TD-SCDMA), and long term evolution systems (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0004] A wireless communication network may include multiple base stations (BS) that can support communication of multiple user equipments (UEs). A user equipment (UE) may communicate with a base station (BS) via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a base station to a user equipment, and an uplink (or reverse link) refers to a communication link from a user equipment to a base station. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) base station, 5G Node B, etc.

[0005] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user devices to communicate at municipal, national, regional and even global levels. New Radio (NR), also known as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR aims to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL) to better integrate with other open standards, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. However, as the demand for mobile broadband access continues to increase, further improvements in LTE and NR technologies are needed. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0006] In some aspects, a wireless communication method performed by a user equipment (UE) may include: receiving a message that releases the user equipment to an idle mode or an inactive mode, the message including information related to dedicated preconfigured uplink resources (DPUR) and a small data radio network temporary identifier (RNTI) for scrambling uplink data, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment to initiate uplink data transmission when in the idle mode or inactive mode; and monitoring a search space associated with a small data service identified in the message that releases the user equipment to an idle mode or an inactive mode to find downlink data addressed to the small data RNTI; and, while in the idle mode or inactive mode, sending uplink data based at least in part on the information related to the DPUR.

[0007] In some aspects, a method of wireless communication performed by a network entity may include: sending a message to release a user equipment (UE) to an idle mode or an inactive mode, wherein the message includes: information related to dedicated preconfigured uplink resources (DPUR), a small data radio network temporary identifier (RNTI) for scrambling uplink data, and an identifier of a search space associated with a small data service that the user equipment is to monitor to find downlink data addressed to the small data RNTI, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment; and receiving uplink data while the user equipment is in the idle mode or inactive mode.

[0008] In some aspects, a wireless communication method performed by a user equipment (UE) may include: receiving information related to dedicated preconfigured uplink resources (DPUR) in a message to release the user equipment to an idle mode or an inactive mode, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment to initiate uplink data transmission when in the idle mode or the inactive mode; and sending uplink data while in the idle mode or the inactive mode based at least in part on the information related to the DPUR.

[0009] In some aspects, a method of wireless communication performed by a base station may include: sending DPUR-related information to a user equipment in a message to release the user equipment to an idle mode or an inactive mode, wherein the DPUR-related information identifies one or more uplink resources allocated to the user equipment; and receiving uplink data from the user equipment when the user equipment is in the idle mode or the inactive mode.

[0010] In some aspects, a user device for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive a message to release the user device to an idle mode or an inactive mode, the message including information related to a dedicated preconfigured uplink resource (DPUR) and a small data radio network temporary identifier (RNTI) for scrambling uplink data, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user device to initiate uplink data transmission when in the idle mode or inactive mode; and monitor a search space associated with a small data service identified in the message to release the user device to an idle mode or inactive mode to find downlink data addressed to the small data RNTI; and in the case of being in the idle mode or inactive mode, send uplink data at least in part based on the information related to the DPUR.

[0011] In some aspects, a network entity for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: send a message to release a user equipment (UE) to an idle mode or an inactive mode, wherein the message includes: information related to dedicated preconfigured uplink resources (DPUR), a small data radio network temporary identifier (RNTI) for scrambling uplink data, and an identifier of a search space associated with a small data service that the user equipment is to monitor to find downlink data addressed to the small data RNTI, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment; and receive uplink data when the user equipment is in the idle mode or the inactive mode.

[0012] In some aspects, a user equipment for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: receive information related to a DPUR in a message to release the user equipment to an idle mode or an inactive mode, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment to initiate uplink data transmission when in the idle mode or the inactive mode; and send uplink data when in the idle mode or the inactive mode, at least in part based on the information related to the DPUR.

[0013] In some aspects, a base station for wireless communication may include a memory and one or more processors coupled to the memory. The memory and the one or more processors may be configured to: send information related to a DPUR in a message to release the user equipment to an idle mode or an inactive mode to a user equipment, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment; and receive uplink data from the user equipment when the user equipment is in the idle mode or the inactive mode.

[0014] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When one or more instructions are executed by one or more processors of a user device, the one or more processors may be caused to: receive a message to release the user device to an idle mode or an inactive mode, the message including information related to a dedicated preconfigured uplink resource (DPUR) and a small data radio network temporary identifier (RNTI) for scrambling uplink data, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user device to initiate uplink data transmission when in the idle mode or inactive mode; and monitor a search space associated with a small data service identified in the message to release the user device to an idle mode or inactive mode to find downlink data addressed to the small data RNTI; and in the case of being in the idle mode or inactive mode, send uplink data based at least in part on the information related to the DPUR.

[0015] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When the one or more instructions are executed by one or more processors of a user device, the one or more processors may be caused to: receive information related to a DPUR in a message for releasing the user device to an idle mode or an inactive mode, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user device to initiate uplink data transmission when in the idle mode or the inactive mode; and send uplink data when in the idle mode or the inactive mode, at least in part based on the information related to the DPUR.

[0016] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When the one or more instructions are executed by one or more processors of a network entity, the one or more processors may be caused to: send a message to release a user equipment (UE) to an idle mode or an inactive mode, wherein the message includes: information related to a dedicated preconfigured uplink resource (DPUR), a small data radio network temporary identifier (RNTI) for scrambling uplink data, and an identifier of a search space associated with a small data service that the user equipment is to monitor to find downlink data addressed to the small data RNTI, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment; and receive uplink data when the user equipment is in the idle mode or the inactive mode.

[0017] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When the one or more instructions are executed by one or more processors of a base station, the one or more processors may be caused to: send information related to a DPUR in a message that releases the user equipment to an idle mode or an inactive mode to a user equipment, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment; and receive uplink data from the user equipment when the user equipment is in the idle mode or the inactive mode.

[0018] In some aspects, an apparatus for wireless communication may include: a component for receiving a message releasing the user equipment to an idle mode or an inactive mode, the message including information related to dedicated preconfigured uplink resources (DPUR) and a small data radio network temporary identifier (RNTI) for scrambling uplink data, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment to initiate uplink data transmission when in the idle mode or inactive mode; and a component for monitoring a search space associated with a small data service identified in the message releasing the user equipment to an idle mode or an inactive mode to find downlink data addressed to the small data RNTI; and a component for sending uplink data while in the idle mode or inactive mode based at least in part on the information related to the DPUR.

[0019] In some aspects, an apparatus for wireless communication may include: a component for receiving information related to DPUR in a message to release the apparatus to an idle mode or an inactive mode, wherein the information related to DPUR identifies one or more uplink resources allocated to the apparatus to initiate uplink data transmission when in the idle mode or the inactive mode; and a component for sending uplink data in the idle mode or the inactive mode based at least in part on the information related to DPUR.

[0020] In some aspects, an apparatus for wireless communication may include: a component for sending a message to release a user equipment (UE) to an idle mode or an inactive mode, wherein the message includes: information related to dedicated preconfigured uplink resources (DPUR), a small data radio network temporary identifier (RNTI) for scrambling uplink data, and an identifier of a search space associated with a small data service that the user equipment is to monitor to find downlink data addressed to the small data RNTI, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment; and a component for receiving uplink data when the user equipment is in the idle mode or inactive mode.

[0021] In some aspects, an apparatus for wireless communication may include: a component for sending DPUR-related information to a user equipment in a message to release the user equipment to an idle mode or an inactive mode, wherein the DPUR-related information identifies one or more uplink resources allocated to the user equipment; and a component for receiving uplink data from the user equipment when the user equipment is in the idle mode or the inactive mode.

[0022] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication devices, and / or processing systems, as fully described herein with reference to the accompanying drawings and description.

[0023] The features and technical advantages of the examples according to the present disclosure have been summarized quite broadly above so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The features of the concepts disclosed herein, their organization and methods of operation, and related advantages will be better understood through the following description when considered in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to be able to understand the above features of the present disclosure in detail, a more specific description briefly summarized above can be obtained by reference to multiple aspects, some of which are shown in the accompanying drawings. However, it should be noted that the drawings only show certain typical aspects of the present disclosure and should not be considered as limiting the scope thereof, as the description may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0025] Figure 1is a block diagram conceptually illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0026] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a user equipment in a wireless communication network according to various aspects of the present disclosure.

[0027] Figures 3 to 6 is a diagram illustrating an example call flow for enabling mobile originated data over dedicated pre-configured uplink resources while in idle mode or inactive mode in accordance with various aspects of the present disclosure.

[0028] Figure 7 is a diagram illustrating an example process performed, for example, by a user device, according to various aspects of the present disclosure.

[0029] Figure 8 is a diagram illustrating example processes performed, for example, by a base station according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0030] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as being limited to any specific structure or function presented by the entire disclosure. On the contrary, these aspects are provided to make the present disclosure thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings herein, it should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method, using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein to practice. It should be understood that any aspect of the present disclosure disclosed herein can be implemented by one or more elements of the claims.

[0031] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms and / or the like (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and design constraints of the overall system.

[0032] It should be noted that although various aspects may be described herein using terminology typically associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may be applied to other generation-based communication systems, such as 5G and higher, including NR technologies.

[0033] Figure 1 is a diagram showing a wireless network 100 in which various aspects of the present disclosure may be practiced. The wireless network 100 may be an LTE network or other wireless network, such as a 5G or NR network. The wireless network 100 may include a plurality of base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A base station is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR base station, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each base station may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a base station and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0034] Base stations may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to user devices that have subscribed to the service. A pico cell may cover a relatively small geographic area and may allow unrestricted access to user devices that have subscribed to the service. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow limited access to user devices associated with the femto cell (e.g., user devices in a closed subscription group (CSG)). The base station of a macro cell may be referred to as a macro base station. The base station of a pico cell may be referred to as a pico base station. The base station of a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown, base station 110a may be a macro base station for macro cell 102a, base station 110b may be a pico base station for pico cell 102b, and base station 110c may be a femto base station for femto cell 102c. A base station may support one or more (e.g., three) cells. The terms "eNB", "base station", "NRBS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably herein.

[0035] In some aspects, the cells are not necessarily stationary, and the geographic area of ​​the cells may move depending on the location of the mobile base station. In some aspects, the base stations may be interconnected to each other and / or to one or more other base stations or network nodes (not shown) in the wireless network 100 using any suitable transmission network via various types of backhaul interfaces, such as direct physical connections, virtual networks, etc.

[0036] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station or a user device) and send transmissions of data to a downstream station (e.g., a user device or a base station). A relay station may also be a user device that can relay transmissions for other user devices. Figure 1 In the example shown, a relay station 110d may communicate with the macro base station 110a and the user equipment 120d to facilitate communication between the base station 110a and the user equipment 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0037] The wireless network 100 may be a heterogeneous network, which includes different types of base stations, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5-40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1-2 watts).

[0038] A network controller 130 may be coupled to a set of base stations and may provide coordination and control for these base stations. The network controller 130 may communicate with the base stations via a backhaul. The base stations may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul.

[0039] The user devices 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each user device may be stationary or mobile. User devices may also be referred to as access terminals, terminals, mobile stations, subscriber units, stations, etc. The user device may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or facility, a biosensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device or a satellite radio device), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0040] Some user devices may be considered to be machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) user devices. MTC and eMTC user devices include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, a connection to a network (e.g., a wide area network such as the Internet or a cellular network) or provide a connection to a network via a wired or wireless communication link. Some user devices may be considered to be Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some user devices may be considered to be customer premises equipment (CPE). User device 120 may be included in a housing that houses components of user device 120, such as processor components, memory components, etc.

[0041] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific RAT and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0042] In some aspects, two or more user devices 120 (e.g., shown as user device 120a and user device 120e) can communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, the user devices 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, the user devices 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0043] As mentioned above, providing Figure 1 As an example. Other examples may differ from Figure 1 The content described.

[0044] Figure 2 A base station 110 and a user equipment 120 (which may be Figure 1 1. Block diagram of a design 200 of one of the base stations and one of the user equipment in FIG. 110 may be equipped with T antennas 234a through 234t and user equipment 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0045] At the base station 110, the transmit processor 220 may receive data for one or more user equipment from the data source 212, select one or more modulation and coding schemes (MCS) for each user equipment based at least in part on a channel quality indicator (CQI) received from the user equipment, process (e.g., encode and modulate) the data for each user equipment based at least in part on the MCS selected for the user equipment, and provide data symbols for all user equipment. The transmit processor 220 may also process system information (e.g., semi-static resource partitioning information (SRPI) and control information (e.g., CQI requests, grants, upper layer signaling, etc.) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding may be used to generate synchronization signals to transmit additional information.

[0046] At the user equipment 120, antennas 252a to 252r can receive downlink signals from the base station 110 and / or other base stations, and can provide received signals to demodulators (DEMOD) 254a to 254r, respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert and digitize) the received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The multiple-input multiple-output detector 256 can obtain received symbols from all R demodulators 254a to 254r, perform multiple-input multiple-output detection on the received symbols if applicable, and provide detected symbols. The receiving processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for the user equipment 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of user equipment 120 may be included in a housing.

[0047] On the uplink, at the user equipment 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the user equipment 120 and other user equipment may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the user equipment 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0048] The controller / processor 240 of the base station 110, the controller / processor 280 of the user equipment 120 and / or Figure 2Any other components of the base station 110 may perform one or more techniques associated with enabling the user equipment 120 to initiate uplink data transmission via dedicated pre-configured uplink resources (DPUR) when the user equipment 120 is in an idle mode or an inactive mode, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the user equipment 120, and / or Figure 2 Any other component of the Figure 7 The process of 700 Figure 8 The operations of process 800 and / or other processes described herein. Memories 242 and 282 may store data and program codes for base station 110 and user equipment 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, when executed by one or more processors of base station 110 and / or user equipment 120, the one or more instructions may perform or direct, for example, Figure 7 The process of 700 Figure 8 The operations of process 800 and / or other processes described herein. Scheduler 246 can schedule user equipment to transmit data on the downlink and / or uplink.

[0049] In some aspects, user equipment 120 may include means for receiving information associated with a DPUR in a message to release user equipment 120 to an idle mode or an inactive mode, wherein the information associated with the DPUR identifies one or more uplink resources allocated to user equipment 120 to initiate uplink data transmission while in the idle mode or the inactive mode; means for transmitting uplink data in the idle mode or the inactive mode based at least in part on the information associated with the DPUR, and the like. In some aspects, such means may include in conjunction with Figure 2 One or more components of user equipment 120 are depicted, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and / or the like.

[0050] In some aspects, base station 110 may include means for sending information related to user equipment 120 in a message to release user equipment 120 to idle mode or inactive mode, wherein the information related to DPUR identifies one or more uplink resources allocated to user equipment 120; means for receiving uplink data from user equipment 120 when user equipment 120 is in idle mode or inactive mode, and / or the like. In some aspects, such means may include in conjunction with Figure 2 One or more components of base station 110 are depicted, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and / or the like.

[0051] As mentioned above, providing Figure 2 As an example. Other examples can be related to Figure 2 Described differently.

[0052] In some cases, the user device may be communicating in a data session in which only a small amount of data is generated in a given concentrated burst. For example, instant messaging applications typically include data payloads of relatively small size to carry small amounts of text, low-resolution images, etc. In another example, social media applications may generate notifications, updates, etc. with relatively small payload sizes. In yet other examples, wearable devices may be used to exchange location information, small and / or low-resolution images, short voice and / or video clips, etc.; various applications may send keep-alive packets with small sizes to maintain session contexts; and wireless sensors may send packets to transmit information related to changes in temperature, pressure, etc. In some cases, when these small data payloads are generated, the user device may operate in a low-power mode, such as an idle mode or an inactive mode. In addition to reducing battery consumption at the user device, the low-power mode may also be associated with reduced signaling between the user device and the wireless network. However, in some cases, the user device may need to switch from a low-power mode to a connected mode in order to send and / or receive data, even if the payload size is relatively small, which may result in increased power consumption, additional network overhead, etc.

[0053] Some aspects described herein provide techniques and apparatus for allocating or specifying dedicated preconfigured uplink resources (DPUR) to user equipment so that when the user equipment is in idle mode, inactive mode, etc., the user equipment can initiate small uplink data transmission. For example, in some aspects, the small uplink data transmission can generally have a payload size (e.g., a maximum size, such as several kilobytes, one megabyte, several megabytes, etc.) that meets a threshold, which can be configured in system information transmitted to the user equipment in a manner such as unicast, broadcast, multicast and / or other suitable radio resource control (RRC) signaling. In addition, in some aspects, one or more system information blocks (SIBs) may include one or more information elements (IEs) related to small data transmission. For example, an IE related to small data transmission may indicate a list of transmission blocks (TBs) to be used when the user equipment initiates small uplink data transmission, a small data transmission technology originated by mobile, a small data transmission technology terminated by mobile, etc. Typically, a node in a wireless network (e.g., a base station, a core network node, etc.) can configure a DPUR, and in the case where a user equipment transitions from a connected mode to an idle or inactive mode, dedicated radio resource control (RRC) signaling (e.g., an RRC release message that may include a suspend configuration (suspendConfig)) can be used to indicate to the user equipment information related to the DPUR, to remain in the inactive mode and / or be released to the inactive mode after initiating an uplink transmission from a mobile source in the inactive mode, to remain in the idle mode and / or be released to the idle mode after initiating an uplink transmission from a mobile source in the idle mode, and so on.

[0054] In some aspects, the DPUR may include a dedicated random access channel (RACH) preamble, a dedicated physical uplink shared channel (PUSCH), and / or other suitable uplink resources allocated to the user equipment to enable the user equipment to initiate uplink data transmission when in idle mode or inactive mode. For example, as further described in detail elsewhere herein, when the user equipment is configured with a DPUR including a dedicated RACH preamble, the user equipment operating in idle or inactive mode can initiate uplink data transmission in message 3 of a contention-free four-step RACH process. Additionally or alternatively, when the user equipment is configured with a DPUR including a dedicated RACH preamble and a dedicated PUSCH, the user equipment in idle or inactive mode can initiate uplink data transmission in message A of a contention-free two-step RACH process. Additionally or alternatively, when the user equipment is configured with a DPUR including a dedicated PUSCH, the user equipment operating in inactive mode can initiate uplink data transmission independently of any RACH process. In addition, in some aspects, the RRC signaling used to indicate the DPUR to the user equipment may also include a small data radio network temporary identifier (SD-RNTI) for scrambling uplink data transmissions, scheduling hybrid automatic repeat request (HARQ) retransmissions, monitoring subsequent downlink traffic (e.g., downlink signaling or downlink data sent to the user equipment in response to uplink data transmissions), etc.

[0055] In this way, when the user equipment has been released to idle or inactive mode, when small uplink data transmission is triggered in one or more upper layers (e.g., application layer and / or similar layers), the user equipment can use DPUR to send uplink data in idle or inactive mode without entering connected mode, which saves power at the user equipment because the user equipment can remain in low power (e.g., idle or inactive) mode. In addition, enabling the user equipment to initiate uplink data transmission from idle or inactive mode (without entering connected mode) reduces the network and / or signaling overhead associated with the user equipment switching from idle or inactive mode to connected mode (and vice versa). In addition, by transmitting information related to small data transmission in one or more base stations, the user equipment can quickly obtain small data configuration information in an on-demand manner, thereby reducing overhead, reducing delays, improving efficiency, etc.

[0056] Figure 3 3 is a diagram illustrating an example call flow 300 that enables mobile-originated data via DPUR in an idle mode or inactive mode in accordance with various aspects of the present disclosure. For example, as described in further detail herein, Figure 3The example call flow 300 shown in FIG. 3 may enable user equipment 120 to transmit uplink data to base station 110 while operating in an idle or inactive mode during a contention-free four-step RACH procedure.

[0057] like Figure 3 As shown, by reference numeral 310, the user equipment 120 may receive a release message including information related to the dedicated RACH preamble from the base station 110. For example, in some aspects, the dedicated RACH preamble may be configured as a one-time resource, a periodic resource with a valid time, etc., and the dedicated RACH preamble may be based on an indication from the user equipment 120 and / or network side information (e.g., information related to the subscription of the user equipment 120, information related to local radio resource management (RRM), etc.). In some aspects, the dedicated RACH preamble may be associated with a single cell or base station. Additionally or alternatively, as further described in detail elsewhere herein, the dedicated RACH preamble may be included in a DPUR list valid for certain areas (e.g., a cell list, a base station list, a radio network area (RNA) list, etc.). In some aspects, the information related to the dedicated RACH preamble may be stored at an application server, and the base station 110 may obtain the information related to the dedicated RACH preamble from the application server before sending the release message to the user equipment 120.

[0058] As further shown by reference numeral 310, the release message may include information related to the search space for downlink traffic. For example, in a physical downlink control channel (PDCCH) region in a downlink radio frame, there may be various places where a particular PDCCH is located, which may be different depending on whether the PDCCH is specific to user equipment 120, common to various user equipments, and / or the like. Thus, in some aspects, the search space indicated in the release message may indicate possible locations of a PDCCH that may carry downlink signaling (e.g., downlink control information (DCI)), downlink data addressed to user equipment 120 (e.g., based on an SD-RNTI assigned to user equipment 120), and the like.

[0059] like Figure 3As further shown in the figure and reference numeral 312, the release message can cause the user equipment 120 to be released to idle mode or inactive mode. For example, in some aspects, the release message can cause the user equipment 120 to switch from connected mode to idle mode, or from connected mode to inactive mode. Additionally or alternatively, the release message can cause the user equipment 120 to remain in inactive mode after sending uplink data from a mobile source in inactive mode. For example, before receiving a release message including a dedicated RACH preamble and / or other information related to DPUR, the user equipment 120 can operate in inactive mode and initiate an RRC recovery request, and the base station 110 can respond with a release message (which may include a pause configuration) to keep the user equipment 120 in inactive mode. Additionally or alternatively, in some aspects, the release message can cause the user equipment 120 to remain in idle mode after sending uplink data from a mobile source in idle mode. For example, prior to receiving the release message, the user equipment 120 may be operating in an idle mode and may send an RRC resume request, an RRC early data request, an RRC setup request, etc. to the base station 110, and the base station 110 may respond with a release message to keep the user equipment 120 in the idle mode. Furthermore, in certain aspects, the dedicated RACH preamble and / or other DPUR information indicated in the release message may be valid while the user equipment 120 is in an idle or inactive mode, or may continue to be valid if and / or when the user equipment 120 changes state (e.g., from an inactive mode to an idle mode).

[0060] like Figure 3 As further shown in FIG. 1 and reference numeral 314, the user equipment 120 may send a dedicated RACH preamble to the base station 110 based on an upper layer (e.g., an application layer) triggering a small data transmission (e.g., an uplink data transmission whose payload size satisfies a threshold, which may be indicated in RRC signaling, one or more SIBs, etc.). In general, the dedicated RACH preamble may be sent as message 1 in a contention-free four-step RACH process. Thus, as Figure 3As further shown in and reference numeral 316, the base station 110 may send and the user equipment may receive a random access response (RAR) message (e.g., message 2 in a contention-free four-step RACH process). In some aspects, the RAR message may include a dedicated PUSCH allocation for the user equipment 120. In some aspects, the dedicated PUSCH allocation may be a DPUR resource that is managed in a substantially similar manner as described above with respect to the dedicated RACH preamble. For example, the dedicated PUSCH may be a periodic, one-time resource configuration with a validity period, based on a subscription of the user equipment 120, based on information related to local RRM, associated with a single cell or base station or a group of multiple cells or base stations, and the like. In addition, in some aspects, the RAR message may include a small data RNTI (SD-RNTI), which the user equipment 120 will use to scramble uplink data transmissions, schedule HARQ retransmissions, receive downlink traffic, and the like.

[0061] like Figure 3 As further shown in the figure and reference numeral 318, in a non-contention four-step RACH process, the user equipment 120 may send uplink small data as message 3 via a dedicated PUSCH, and the user equipment 120 may scramble the uplink small data using the SD-RNTI provided in the RAR message. In some aspects, the uplink small data may be sent using RRC signaling (e.g., RRC recovery request, RRC early data request, RRC establishment request, etc.). Additionally or alternatively, the uplink small data may be sent without RRC signaling. For example, the uplink small data may be sent together with a recovery identifier and an authentication token for the user equipment 120, which may be included in a media access control (MAC) control element (MAC-CE). As Figure 3 As further shown and referenced by numeral 320, the user equipment 120 may monitor the search space indicated in the previous release message for downlink traffic (e.g., downlink signaling, downlink user plane data, etc.). For example, in some aspects, the user equipment 120 may monitor the search space for downlink traffic addressed to the SD-RNTI, where the SD-RNTI is assigned to the user equipment 120 and indicated in the RAR message. Figure 3As further shown in and reference numeral 322, in a contention-free four-step RACH procedure, the user equipment 120 may receive downlink signaling and / or downlink data addressed to the SD-RNTI as message 4. In general, the downlink signaling provided in message 4 may include RRC signaling, such as an RRC resume message, an RRC release message, etc., which causes the user equipment 120 to enter and / or remain in an inactive or idle mode. In this manner, the user equipment 120 may initiate a contention-free four-step RACH procedure using a DPUR including a dedicated RACH preamble provided in an initial release message, and subsequently send uplink data (using a dedicated PUSCH allocation received in message 2) in message 3 of the contention-free four-step RACH procedure without entering a connected mode.

[0062] As mentioned above, Figure 3 are provided as examples. Other examples may be related to Figure 3 Different than described.

[0063] Figure 4 4 is a diagram illustrating an example call flow 400 for initiating a mobile originated data call via DPUR in an idle mode or inactive mode in accordance with aspects of the present disclosure. For example, as described in further detail herein, Figure 4 The example call flow 400 shown in FIG. 4 may enable user equipment 120 to transmit uplink data to base station 110 while operating in an idle or inactive mode during a contention-free two-step RACH procedure.

[0064] like Figure 4As shown in the figure mark 410, the user equipment 120 can receive a release message from the base station 110, and the release message includes the DPUR configuration assigned to the user equipment 120. For example, as shown in the figure, the DPUR configuration may include information related to the dedicated RACH preamble and the dedicated PUSCH assigned to the user equipment 120. For example, in some aspects, the dedicated RACH preamble and the dedicated PUSCH may be configured as a one-time resource, a periodic resource with a valid time, etc., and the DPUR configuration including the dedicated RACH preamble and the dedicated PUSCH may be based on an indication from the user equipment 120 and / or network side information (e.g., information related to the subscription of the user equipment 120, information related to the local RRM, etc.). In some aspects, the DPUR configuration may be associated with a single cell or base station. Additionally or alternatively, as further described in detail elsewhere herein, the DPUR configuration may be included in a DPUR configuration list valid for certain areas. In some aspects, information related to the DPUR configuration may be stored at an application server, and the base station 110 may obtain information related to the DPUR configuration from the application server before sending a release message to the user equipment 120. In addition, in some aspects, the release message provided to the user equipment may further include information related to the search space and SD-RNTI for downlink traffic, where the user equipment 120 uses the information to scramble uplink data transmission, schedule HARQ retransmissions, receive downlink traffic, etc.

[0065] like Figure 4 As further shown in the figure and reference numeral 412, the release message can cause the user equipment 120 to be released to an idle mode or an inactive mode. For example, as described in more detail elsewhere herein, the release message can cause the user equipment 120 to be released from a connected mode, an inactive mode, an idle mode, etc. to an idle or inactive mode. In addition, in some aspects, the DPUR configuration indicated in the release message can be effective while the user equipment 120 is in the idle or inactive mode, or the DPUR configuration indicated in the release message can continue to be effective if and / or when the user equipment 120 changes state (e.g., from an inactive mode to an idle mode).

[0066] like Figure 4As further shown in the figure and reference numeral 414, in a non-contention two-step RACH process, the user equipment 120 can send uplink small data as message A on a dedicated PUSCH using a dedicated RACH preamble. For example, in some aspects, the uplink small data can be sent based on an upper layer triggering the transmission of small data with a payload size that meets a threshold. In some aspects, the uplink small data can be sent using RRC signaling (e.g., RRC recovery request, RRC early data request, RRC establishment request, etc.). Additionally or alternatively, the uplink small data can be sent without RRC signaling. For example, the uplink small data can be sent together with an identifier and an authentication token associated with the user equipment 120, and the identifier and the authentication token can be included in the MAC-CE. As Figure 4 As further shown in FIG. 4 and reference numeral 416, the user equipment 120 may monitor the search space indicated in the previous release message to find downlink traffic that is addressed to the SD-RNTI assigned to the user equipment 120. Figure 4 As further shown in and by reference numeral 418, in a contention-free two-step RACH procedure, the user equipment 120 may receive downlink signaling and / or downlink data addressed to the SD-RNTI as message B. In general, the downlink signaling provided in message B may include RRC signaling, such as an RRC recovery message, an RRC release message, etc., which causes the user equipment 120 to enter and / or remain in an inactive or idle mode. In this manner, the user equipment 120 may use the DPUR including the dedicated RACH preamble and the dedicated PUSCH provided in the initial release message to initiate uplink data transmission (e.g., subject to a maximum size limit for uplink data transmission) via a contention-free two-step RACH procedure while in an inactive or idle mode and without entering a connected mode.

[0067] As mentioned above, Figure 4 are provided as examples. Other examples may be related to Figure 4 Different than described.

[0068] Figure 5 is a diagram illustrating an example call flow 500 that enables mobile-originated data via DPUR in an idle mode or inactive mode in accordance with various aspects of the present disclosure. For example, as described in further detail herein, Figure 5 The example call flow 500 shown in FIG. 5 may enable the user equipment 120 to transmit uplink data to the base station 110 over a dedicated PUSCH while operating in an idle or inactive mode and independent of any RACH procedure.

[0069] like Figure 5As shown in the figure 510, the user equipment 120 can receive a release message from the base station 110, and the release message includes the DPUR configuration assigned to the user equipment 120. For example, as shown in the figure, the DPUR configuration may include information related to the dedicated PUSCH assigned to the user equipment 120. For example, in some aspects, the dedicated PUSCH can be configured as a one-time resource, a periodic resource with a valid time, etc., as further described in detail elsewhere herein. In addition, in some aspects, the release message provided to the user equipment may further include information related to the search space of the downlink traffic, wherein the user equipment 120 uses the information to scramble uplink data transmission, schedule HARQ retransmissions, receive downlink traffic, etc.

[0070] like Figure 5 As further shown in the figure and reference numeral 512, the release message can cause the user equipment 120 to be released to an idle mode or an inactive mode. For example, as described in more detail elsewhere herein, the release message can cause the user equipment 120 to be released from a connected mode, an inactive mode, an idle mode, etc. to an idle or inactive mode. In addition, in some aspects, the DPUR configuration indicated in the release message can be effective while the user equipment 120 is in the idle or inactive mode, or the DPUR configuration indicated in the release message can continue to be effective if and / or when the user equipment 120 changes state (e.g., from an inactive mode to an idle mode).

[0071] like Figure 5 As further shown in the figure and reference numeral 514, the user equipment 120 can send uplink small data to the base station 110 via a dedicated PUSCH (e.g., independent of the RACH process). For example, in some aspects, the uplink small data can be sent based on an upper layer triggering the transmission of small data with a payload size that meets a threshold. In some aspects, the uplink small data can be sent using RRC signaling (e.g., RRC recovery request, RRC early data request, RRC establishment request, etc.). Additionally or alternatively, the uplink small data can be sent using a MAC-CE, which includes an identifier and an authentication token associated with the user equipment 120. As shown in FIG. Figure 5 As further shown in FIG. 1 and at 516, the user equipment 120 may monitor the search space indicated in the previous release message to find downlink traffic addressed to the SD-RNTI assigned to the user equipment 120. Figure 5As further shown in and by reference numeral 518, the user equipment 120 may receive downlink signaling that causes the user equipment 120 to enter and / or remain in an inactive or idle mode. Additionally or alternatively, in some aspects, downlink traffic addressed to the SD-RNTI of the user equipment 120 may include downlink data sent in response to an uplink small data transmission from the user equipment 120. In this manner, the user equipment 120 may use the DPUR for the dedicated PUSCH provided in the initial release message to initiate an uplink data transmission while in an inactive or idle mode without having to enter a connected mode or transmit signaling messages associated with a two-step or four-step RACH procedure.

[0072] As mentioned above, Figure 5 are provided as examples. Other examples may be related to Figure 5 Different than described.

[0073] Figure 6 600 is a diagram illustrating an example call flow 600 that enables mobile-originated data via DPUR in an idle mode or inactive mode in accordance with various aspects of the present disclosure. For example, as described in further detail herein, Figure 6 The example call flow 600 shown in the example can enable the DPUR configuration to be coordinated across multiple cells, base stations, radio network areas (RNAs), etc., which can enable the user equipment 120 to send uplink data to any one or more of multiple base stations 110-1, 110-2, etc. (for example, to support mobile scenarios in which uplink small data transmission can be triggered after the user equipment 120 moves from the coverage area of ​​one base station (e.g., base station 110-1) to the coverage area of ​​another base station (e.g., base station 110-2)).

[0074] For example, Figure 6 As shown and referenced by 610, a base station group including base station 110-1, base station 110-2 and / or other base stations in the coordination group may coordinate DPUR allocations for small data transmission. For example, the coordination group may include a group of cells, a group of base stations, a group of RNAs, etc., and each cell, base station, RNA, etc. may configure one or more DPUR allocations and SD-RNTIs for user equipment 120 operating in a corresponding coverage area and in an inactive mode. For example, in Figure 6In the illustrated call flow 600, base station 110-1 may send a DPUR reservation request to base station 110-2 to preconfigure certain uplink resources (e.g., dedicated RACH preamble, dedicated PUSCH, etc.) before releasing user equipment 120 to an idle or inactive mode. Thus, in some aspects, base station 110-1 may receive a DPUR reservation response from base station 110-2, the DPUR reservation response including information related to one or more dedicated RACH preambles, dedicated PUSCH allocations, SD-RNTIs, and / or other resources that have been reserved and allocated for small data transmission.

[0075] like Figure 6 As further shown in FIG. 1 and at 612, the base station 110-1 may send and the user equipment 120 may receive a release message including information related to the DPUR allocation list. For example, the DPUR allocation list may include a list of dedicated RACH preambles, dedicated PUSCH allocations, SD-RNTIs, etc., which may be associated with a cell list, a base station list, an RNA list, etc. Figure 6 As further shown in FIG. 1 and at reference numeral 614, the release message may cause the user equipment 120 to be released into an inactive or idle mode, as described in greater detail elsewhere herein.

[0076] like Figure 6 As further shown in the figure and reference numeral 616, user equipment 120 can move from the coverage area of ​​base station 110-1 to the coverage area of ​​another base station, such as base station 110-2. In some aspects, based at least in part on one or more upper layer triggers for uplink small data transmission, user equipment 120 can check the DPUR allocation list to determine whether the current serving base station appears in the DPUR allocation list or is associated with one or more cells, RNAs, etc. indicated in the DPUR allocation list. Therefore, as Figure 6 As shown in the figure 618, the user equipment 120 can send the uplink small data transmission via the DPUR associated with the base station 110-2 (e.g., the DPUR associated with the cell provided by the base station 110-2) based at least in part on the appearance of the base station 110-2 in the DPUR allocation list. For example, in the case where the DPUR associated with the base station 110-2 only includes the dedicated RACH preamble code, the user equipment 120 can send the uplink small data transmission via the DPUR associated with the base station 110-2 (e.g., the DPUR associated with the cell provided by the base station 110-2). Figure 3 In addition or alternatively, in the case where the DPUR associated with base station 110-2 includes a dedicated RACH preamble and a dedicated PUSCH, user equipment 120 may initiate uplink small data transmission via the non-contention four-step RACH process described in further detail above. Figure 4Additionally or alternatively, in the case where the DPUR associated with base station 110-2 includes only a dedicated PUSCH, user equipment 120 may initiate uplink small data transmission independently of any RACH procedure, as described above with reference to Figure 5 described in further detail.

[0077] As mentioned above, Figure 6 are provided as examples. Other examples may be related to Figure 6 Different than described.

[0078] Figure 7 is a diagram illustrating an example process 700, for example, performed by a user equipment, in accordance with various aspects of the present disclosure. Example process 700 is an example of operations performed by a user equipment (eg, user equipment 120, etc.) to initiate uplink data transmission via DPUR while in idle mode or inactive mode.

[0079] like Figure 7 As shown, in some aspects, the process 700 may include receiving information associated with the DPUR in a message that releases the user equipment to an idle mode or an inactive mode, wherein the information associated with the DPUR identifies one or more uplink resources allocated to the user equipment to initiate uplink data transmission when in the idle mode or the inactive mode (block 710). For example, as described above, the user equipment may (e.g., using antenna 252, DEMOD 254, MIMO detector 256, receiving processor 258, controller / processor 280, etc.) receive information associated with the DPUR in a message that releases the user equipment to an idle mode or an inactive mode. In some aspects, the information associated with the DPUR identifies one or more uplink resources allocated to the user equipment to initiate uplink data transmission when in the idle mode or the inactive mode.

[0080] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include sending uplink data while in idle mode or inactive mode based at least in part on information associated with the DPUR (block 720). For example, as described above, the user equipment may send uplink data while in idle mode or inactive mode (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) based at least in part on information associated with the DPUR, as described above.

[0081] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0082] In a first aspect, one or more uplink resources allocated to a user equipment include a dedicated preamble.

[0083] In a second aspect, either alone or in combination with the first aspect, a user equipment sends a dedicated preamble in a first message of a four-step RACH procedure and receives a PUSCH allocation in a second message of the four-step RACH procedure, and the user equipment sends uplink data via the PUSCH in a third message of the four-step RACH procedure.

[0084] In a third aspect, alone or in combination with one or more of the first and second aspects, the second message of the four-step RACH procedure further includes a RNTI for scrambling uplink data sent over the PUSCH.

[0085] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a user equipment monitors a search space identified in a message that releases the user equipment to an idle mode or an inactive mode to find downlink data addressed to the RNTI; in a fourth message of a four-step RACH process, downlink data within the search space is received; and the downlink data includes one or more downlink user plane data in response to uplink data or downlink signaling that releases the user equipment to an idle mode or an inactive mode.

[0086] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the four-step RACH procedure is a contention-free four-step RACH procedure.

[0087] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the one or more uplink resources allocated to the user equipment further include a dedicated PUSCH.

[0088] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, uplink data is sent on a dedicated PUSCH using a dedicated preamble in a first message of a two-step RACH procedure.

[0089] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the message for releasing the user equipment to idle mode or inactive mode further comprises a RNTI for scrambling uplink data sent over the PUSCH.

[0090] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the user equipment monitors a search space identified in a message that releases the user equipment to idle mode or inactive mode to find downlink data addressed to the RNTI; in a second message of a two-step RACH process, receives downlink data within the search space; and the downlink data includes one or more downlink user plane data in response to uplink data or downlink signaling that releases the user equipment to idle mode or inactive mode.

[0091] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the two-step RACH procedure is a contention-free two-step RACH procedure.

[0092] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the one or more uplink resources allocated to the user equipment include a dedicated PUSCH.

[0093] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, uplink data is transmitted via a dedicated PUSCH when the user equipment is in an inactive mode.

[0094] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, a user equipment receives downlink data addressed to an RNTI for scrambling uplink data within a search space, the search space being identified in a message releasing the user equipment to an idle mode or an inactive mode, and the downlink data includes one or more downlink user plane data in response to the uplink data or downlink signaling releasing the user equipment to an idle mode or an inactive mode.

[0095] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the information related to the DPUR comprises a list of cells associated with one or more uplink resources allocated to the user equipment.

[0096] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, uplink data is further sent at least in part based on the user equipment detecting a base station associated with at least one cell in a list of cells associated with one or more uplink resources allocated to the user equipment.

[0097] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, a message including information related to the DPUR causes the user equipment to one or more of transition from a connected mode to an inactive mode, remain in an inactive mode, transition from a connected mode to an idle mode, or remain in an idle mode.

[0098] Although Figure 7 Example blocks of process 700 are shown, but in some aspects, process 700 may include Figure 7 Additional blocks, fewer blocks, different blocks, or blocks in a different arrangement than those shown in . Additionally or alternatively, two or more blocks of process 700 may be performed in parallel.

[0099] Figure 8 8 is a diagram illustrating an example process 800 performed by, for example, a base station in accordance with various aspects of the present disclosure. Example process 800 is an example of operations performed by a base station (e.g., base station 110, etc.) in connection with initiating uplink data transmission via DPUR when a user equipment is in an idle mode or an inactive mode.

[0100] like Figure 8 As shown, in some aspects, process 800 may include sending information related to the DPUR in a message to release the user equipment to an idle mode or an inactive mode to the user equipment, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment (block 810). For example, as described above, the base station may (e.g., using the controller / processor 240, the transmit processor 220, the TX MIMO processor 230, the MOD 232, the antenna 234, etc.) send information related to the DPUR in a message to release the user equipment to an idle mode or an inactive mode to the user equipment. In some aspects, the information related to the DPUR identifies one or more uplink resources allocated to the user equipment.

[0101] like Figure 8 As further shown, in some aspects, process 800 may include receiving uplink data from the user equipment while the user equipment is in an idle mode or an inactive mode (block 820). For example, as described above, the base station may receive uplink data from the user equipment (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, etc.) while the user equipment is in an idle mode or an inactive mode.

[0102] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0103] In a first aspect, one or more uplink resources allocated to a user equipment include a dedicated preamble.

[0104] In a second aspect, alone or in combination with the first aspect, a base station receives a dedicated preamble from a user equipment in a first message of a four-step RACH procedure, sends a PUSCH allocation to the user equipment in a second message of the four-step RACH procedure, and receives uplink data via the PUSCH in a third message of the four-step RACH procedure.

[0105] In a third aspect, alone or in combination with one or more of the first and second aspects, the second message of the four-step RACH procedure further includes a RNTI for scrambling uplink data sent over the PUSCH.

[0106] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the base station sends, in a fourth message of a four-step RACH procedure, downlink data addressed to the RNTI within a search space identified in a message for releasing a user equipment to an idle mode or an inactive mode, and the downlink data includes one or more downlink user plane data in response to uplink data or downlink signaling for releasing the user equipment to an idle mode or an inactive mode.

[0107] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the four-step RACH procedure is a contention-free four-step RACH procedure.

[0108] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the one or more uplink resources allocated to the user equipment further include a dedicated PUSCH.

[0109] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, uplink data is received over a dedicated PUSCH in a first message using a dedicated preamble in a two-step RACH procedure.

[0110] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the message to release the user equipment to idle mode or inactive mode further comprises a RNTI to be used for scrambling uplink data sent over the PUSCH.

[0111] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the base station sends, in the second message of the two-step RACH process, downlink data addressed to the RNTI within the search space identified in the message for releasing the user equipment to idle mode or inactive mode, and the downlink data includes one or more downlink user plane data in response to the uplink data or downlink signaling for releasing the user equipment to idle mode or inactive mode.

[0112] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the two-step RACH procedure is a contention-free two-step RACH procedure.

[0113] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the one or more uplink resources allocated to the user equipment include a dedicated PUSCH.

[0114] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, uplink data is received through a dedicated PUSCH when the user equipment is in an inactive mode.

[0115] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the base station sends downlink data addressed to the RNTI for scrambling uplink data within a search space identified in a message for releasing the user equipment to idle mode or inactive mode, and the downlink data includes one or more downlink user plane data in response to the uplink data or downlink signaling for releasing the user equipment to idle mode or inactive mode.

[0116] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the information related to the DPUR comprises a list of cells associated with one or more uplink resources allocated to the user equipment.

[0117] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, uplink data is received from a user equipment based at least in part on the base station being associated with at least one cell in a cell list, wherein the cell list is associated with one or more uplink resources allocated to the user equipment.

[0118] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, a message including information related to the DPUR causes the user equipment to one or more of transition from a connected mode to an inactive mode, remain in an inactive mode, transition from a connected mode to an idle mode, or remain in an idle mode.

[0119] Although Figure 8 Example blocks of process 800 are shown, but in some aspects, process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or blocks arranged differently than those shown in . Additionally or alternatively, two or more blocks of process 800 can be performed in parallel.

[0120] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0121] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software.

[0122] As used herein, satisfying a threshold may refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0123] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited in these respects. Thus, the operation and behavior of the systems and / or methods described herein are not referenced to specific software code—it should be understood that software and hardware may be designed to implement systems and / or methods based at least in part on the description herein.

[0124] Even if specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features can be combined in ways that are not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below can directly depend on only one claim, the disclosure of the various aspects includes each dependent claim and each other claim in the claim set. "At least one" in the list of items refers to any combination of those items, including single items. For example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc, as well as any combination with multiples of the same elements (e.g., aa, aaa, aab, aac, abb, ac, bb, bbc, Bbc, cc and ccc or any other ordering of a, b, c).

[0125] Unless expressly stated, any element, action or instruction used herein should not be interpreted as critical or essential. In addition, as used herein, the article "a" is intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.), and can be used interchangeably with "one or more". When only one item is intended, the phrase "only one" or similar language is used. In addition, as used herein, the terms "having", "containing", "having" and / or similar terms can be open terms. In addition, unless otherwise expressly stated, the phrase "based on" is intended to mean "based at least in part on".

Claims

1. A wireless communication method performed by a user equipment (UE), comprising: receiving a message to release the user equipment to an idle mode or an inactive mode, the message comprising: information related to a dedicated preconfigured uplink resource (DPUR) and a small data radio network temporary identifier (RNTI) for scrambling uplink data, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment to initiate uplink data transmission when in the idle mode or inactive mode; and monitoring a search space associated with small data traffic identified in the message releasing the user equipment to idle mode or inactive mode to find downlink data addressed to the small data RNTI; and While in the idle mode or inactive mode, uplink data is sent based at least in part on the DPUR-related information.

2. The method of claim 1, wherein the one or more uplink resources allocated to the user equipment comprise a dedicated preamble.

3. The method according to claim 2, further comprising: sending the dedicated preamble in a first message of a four-step random access channel (RACH) procedure; and In a second message of the four-step RACH procedure, a physical uplink shared channel (PUSCH) allocation is received, wherein the uplink data is sent over the PUSCH in a third message of the four-step RACH procedure.

4. The method according to claim 3, further comprising: The downlink data is received in a fourth message of the four-step RACH procedure within the search space, wherein the downlink data comprises one or more of downlink user plane data in response to the uplink data or downlink signaling to release the user equipment to the idle mode or inactive mode.

5. The method of claim 2, wherein the one or more uplink resources allocated to the user equipment further comprises a dedicated physical uplink shared channel (PUSCH).

6. The method of claim 5, wherein the uplink data is sent over the dedicated PUSCH using the dedicated preamble in a first message of a two-step random access channel (RACH) procedure.

7. The method according to claim 6, further comprising: The downlink data is received in a second message of the two-step RACH procedure within the search space, wherein the downlink data comprises one or more of downlink user plane data in response to the uplink data or downlink signaling to release the user equipment to the idle mode or the inactive mode.

8. The method of claim 1, wherein the one or more uplink resources allocated to the user equipment comprises a dedicated physical uplink shared channel (PUSCH).

9. The method according to claim 8, wherein in a case where the user equipment is in the inactive mode, the uplink data is transmitted through the dedicated PUSCH.

10. The method according to claim 8, further comprising: The downlink data addressed to the small data RNTI is received, wherein the downlink data comprises one or more of downlink user plane data in response to the uplink data or downlink signaling to release the user equipment to the idle mode or inactive mode.

11. The method of claim 1, wherein the information related to the DPUR comprises a list of cells associated with the one or more uplink resources allocated to the user equipment.

12. The method of claim 11, wherein the uplink data is further sent based at least in part on the user equipment detecting a network entity associated with at least one cell in the cell list associated with the one or more uplink resources allocated to the user equipment.

13. A method according to claim 1, wherein the message including information related to the DPUR causes the user equipment to perform one or more of a transition from a connected mode to the inactive mode, remain in the inactive mode, transition from the connected mode to the idle mode, or remain in the idle mode.

14. A wireless communication method performed by a network entity, comprising: Sending a message to release a user equipment (UE) to an idle mode or an inactive mode, wherein the message includes: Information related to Dedicated Preconfigured Uplink Resources (DPUR), A small data Radio Network Temporary Identifier (RNTI) used to scramble uplink data, and The user equipment is to monitor to find the downlink data addressed to the small data RNTI, an identification of a search space associated with a small data service, wherein the information associated with the DPUR identifies one or more uplink resources allocated to the user equipment; and In case the user equipment is in the idle mode or the inactive mode, uplink data is received.

15. The method of claim 14, wherein the one or more uplink resources allocated to the user equipment comprises a dedicated preamble.

16. The method according to claim 15, further comprising: receiving the dedicated preamble from the user equipment in a first message of a four-step random access channel (RACH) procedure; and A physical uplink shared channel (PUSCH) allocation is sent to the user equipment in a second message of the four-step RACH procedure, wherein the uplink data is received over the PUSCH in a third message of the four-step RACH procedure.

17. The method according to claim 16, further comprising: The downlink data addressed to the small data RNTI is sent in a fourth message of the four-step RACH procedure within a search space identified in a message releasing the user equipment to the idle mode or the inactive mode, wherein the downlink data comprises one or more of downlink user plane data in response to the uplink data or downlink signaling releasing the user equipment to the idle mode or the inactive mode.

18. The method of claim 15, wherein the one or more uplink resources allocated to the user equipment further comprises a dedicated physical uplink shared channel (PUSCH).

19. The method of claim 18, wherein the uplink data is received over the dedicated PUSCH in a first message using the dedicated preamble in a two-step random access channel (RACH) procedure.

20. The method according to claim 19, further comprising: The downlink data addressed to the small data RNTI is sent in a second message of the two-step RACH procedure within a search space identified in a message releasing the user equipment to the idle mode or the inactive mode, wherein the downlink data comprises one or more of downlink user plane data in response to the uplink data or downlink signaling releasing the user equipment to the idle mode or the inactive mode.

21. The method of claim 14, wherein the one or more uplink resources allocated to the user equipment comprises a dedicated physical uplink shared channel (PUSCH).

22. The method of claim 21, wherein the uplink data is received through the dedicated PUSCH in a case where the user equipment is in the inactive mode.

23. The method according to claim 21, further comprising: The downlink data addressed to the small data RNTI is sent within a search space identified in a message releasing the user equipment to the idle mode or the inactive mode, wherein the downlink data comprises one or more of downlink user plane data in response to the uplink data or downlink signaling releasing the user equipment to the idle mode or the inactive mode.

24. The method of claim 14, wherein the information related to the DPUR comprises a list of cells associated with the one or more uplink resources allocated to the user equipment.

25. The method of claim 24, wherein the uplink data is received from the user equipment based at least in part on the network entity being associated with at least one cell in the cell list, wherein the cell list is associated with the one or more uplink resources allocated to the user equipment.

26. A method according to claim 14, wherein the message including the information related to the DPUR causes the user equipment to perform one or more of transitioning from the connected mode to the inactive mode, remaining in the inactive mode, transitioning from the connected mode to the idle mode, or remaining in the idle mode.

27. A user equipment (UE) for wireless communication, comprising: Memory; and One or more processors coupled to the memory, configured to: receiving a message for releasing the user equipment to an idle mode or an inactive mode, the message comprising: Information related to Dedicated Preconfigured Uplink Resources (DPUR), and a small data radio network temporary identifier (RNTI) for scrambling uplink data, wherein the information related to the DPUR identifies one or more uplink resources allocated to the user equipment to initiate uplink data transmission while in the idle mode or inactive mode; and monitoring a search space associated with small data traffic identified in the message releasing the user equipment to idle mode or inactive mode to find downlink data addressed to the small data RNTI; and While in the idle mode or the inactive mode, uplink data is sent based at least in part on the information related to the DPUR.

28. The user equipment of claim 27, wherein the one or more uplink resources allocated to the user equipment include a dedicated preamble, and wherein the memory and the one or more processors are further configured to: sending the dedicated preamble in a first message of a four-step random access channel (RACH) procedure; and In a second message of the four-step RACH procedure, a physical uplink shared channel (PUSCH) allocation is received, wherein the uplink data is sent over the PUSCH in a third message of the four-step RACH procedure.

29. A user equipment according to claim 27, wherein the one or more uplink resources allocated to the user equipment include a dedicated preamble and a dedicated physical uplink shared channel (PUSCH), and wherein the uplink data is sent through the dedicated PUSCH using the dedicated preamble in a first message of a two-step random access channel (RACH) procedure.

30. The user equipment of claim 27, wherein the one or more uplink resources allocated to the user equipment comprise a dedicated physical uplink shared channel (PUSCH), and wherein when the user equipment is in the inactive mode, the uplink data is sent via the dedicated PUSCH.

31. The user equipment of claim 27, wherein the message is a Radio Resource Control (RRC) release message.

32. The user equipment of claim 27, wherein the one or more uplink resources allocated to the user equipment comprises a dedicated preamble.

33. A network entity for wireless communication, comprising: Memory; and One or more processors coupled to the memory, configured to: Sending a message to release a user equipment (UE) to an idle mode or an inactive mode, wherein the message includes: Information related to Dedicated Preconfigured Uplink Resources (DPUR), A small data Radio Network Temporary Identifier (RNTI) used to scramble uplink data, and The user equipment is to monitor to find an identification of a search space associated with a small data service for downlink data addressed to the small data RNTI, wherein the information associated with the DPUR identifies one or more uplink resources allocated to the user equipment; and In case the user equipment is in the idle mode or the inactive mode, uplink data is received.

34. The network entity of claim 33, wherein the one or more uplink resources allocated to the user equipment comprise a dedicated preamble, and wherein the memory and the one or more processors are further configured to: receiving the dedicated preamble from the user equipment in a first message of a four-step random access channel (RACH) procedure; and A physical uplink shared channel (PUSCH) allocation is sent to the user equipment in a second message of the four-step RACH procedure, wherein the uplink data is received over the PUSCH in a third message of the four-step RACH procedure.

35. A network entity according to claim 33, wherein the one or more uplink resources allocated to the user equipment include a dedicated preamble and a dedicated physical uplink shared channel (PUSCH), and wherein the uplink data is received through the dedicated PUSCH in a first message using the dedicated preamble in a two-step random access channel (RACH) process.

36. A network entity according to claim 33, wherein the one or more uplink resources allocated to the user equipment include a dedicated physical uplink shared channel (PUSCH), and wherein when the user equipment is in the inactive mode, the uplink data is received via the dedicated PUSCH.

37. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions, when executed by one or more processors of a user equipment (UE), cause the one or more processors to perform the method of any one of claims 1-13.

38. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions, when executed by one or more processors of a network entity, causing the one or more processors to perform the method of any one of claims 14-26.

39. An apparatus for wireless communication, comprising means for performing the method of any one of claims 1-13.

40. An apparatus for wireless communication, comprising means for performing the method of any one of claims 14-26.

Images