Paging for mobile terminated small data reception in idle and / or inactive mode

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a paging communication from a base station (BS) when the UE is in an inactive mode or an idle mode. The UE may send a first communication to the BS as part of a random access channel (RACH) process based at least in part on receiving the paging communication. The UE may receive a second communication from the BS based at least in part on sending the first communication, the second communication including downlink data terminated by a mobile station, an indication of uplink resources, and a radio resource control (RRC) release message. The RRC release message may keep the UE in an inactive mode or an idle mode when receiving downlink data terminated by a mobile station. The UE may use uplink resources to send uplink data initiated by a mobile station. Many other aspects are provided.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications and techniques and apparatus for paging for mobile-terminated small data reception in idle and / or inactive modes. Background Art

[0002] 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 (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a collection of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless communication network may include multiple base stations (BS) that can support communication of multiple user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. Downlinks (or forward links) refer to the communication link from a BS to a UE, and uplinks (or reverse links) refer to the communication link from a UE to a BS. 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) BS, 5G Node B, etc.

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

[0005] In some aspects, a method of wireless communication performed by a user equipment (UE) may include: receiving a paging communication from a base station (BS) while the UE is in an inactive mode or an idle mode; sending a first communication to the BS as part of a random access channel (RACH) process based at least in part on receiving the paging communication; receiving a second communication from the BS based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, an indication of uplink resources, and a radio resource control (RRC) release message, the radio resource control (RRC) release message causing the UE to remain in an inactive mode or an idle mode while receiving the mobile-terminated downlink data; and, while in the inactive mode or the idle mode, sending mobile-initiated uplink data to the BS using the uplink resources.

[0006] In some aspects, a method of wireless communication performed by a BS may include: sending a paging communication to a UE when the UE is in an inactive mode or an idle mode; receiving a first communication from the UE as part of a RACH process based at least in part on sending the paging communication; sending a second communication to the UE based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, uplink resources that the UE is to use to send mobile-initiated uplink data when it is in the inactive mode or the idle mode, and an RRC release message that enables the UE to receive the mobile-terminated downlink data when it is in the inactive mode or the idle mode; and receiving mobile-initiated uplink data from the UE and in the uplink resources, wherein the UE is to send mobile-initiated uplink data when it is in the inactive mode or the idle mode.

[0007] In some aspects, a UE for wireless communication may include: a memory and one or more processors coupled to the memory. The memory and the one or more processors are configured to: receive a paging communication from a BS when the UE is in an inactive mode or an idle mode; send a first communication to the BS as part of a RACH process based at least in part on receiving the paging communication; receive a second communication from the BS based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, an indication of uplink resources, and an RRC release message, the RRC release message causing the UE to remain in the inactive mode or the idle mode when receiving the mobile-terminated downlink data; and send mobile-originated uplink data to the BS using the uplink resources when in the inactive mode or the idle mode.

[0008] In some aspects, a BS for wireless communication may include: a memory and one or more processors coupled to the memory. The memory and the one or more processors are configured to: send a paging communication to a UE when the UE is in an inactive mode or an idle mode; receive a first communication from the UE as part of a RACH process based at least in part on sending the paging communication; send a second communication to the UE based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, uplink resources that the UE is to use to send mobile-initiated uplink data when it is in the inactive mode or the idle mode, and an RRC release message that causes the UE to receive the mobile-terminated downlink data when it is in the inactive mode or the idle mode; and receive mobile-initiated uplink data from the UE and in the uplink resources, wherein the UE is to send the mobile-initiated uplink data when it is in the inactive mode or the idle mode.

[0009] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, cause the one or more processors to: receive a paging communication from a BS when the UE is in an inactive mode or an idle mode; send a first communication to the BS as part of a RACH process based at least in part on receiving the paging communication; receive a second communication from the BS based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, an indication of uplink resources, and an RRC release message, the RRC release message causing the UE to remain in the inactive mode or the idle mode while receiving the mobile-terminated downlink data; and send mobile-originated uplink data to the BS using the uplink resources when in the inactive mode or the idle mode.

[0010] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a BS, cause the one or more processors to: send a paging communication to a UE when the UE is in an inactive mode or an idle mode; receive a first communication from the UE as part of a RACH process based at least in part on sending the paging communication; send a second communication to the UE based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, uplink resources to be used by the UE to send mobile-initiated uplink data when the UE is in an inactive mode or an idle mode, and an RRC release message that causes the UE to receive the mobile-terminated downlink data when the UE is in an inactive mode or an idle mode; and receive mobile-initiated uplink data from the UE and in the uplink resources, wherein the UE is to send mobile-initiated uplink data when the UE is in an inactive mode or an idle mode.

[0011] In some aspects, an apparatus for wireless communication may include: a component for receiving a paging communication from a BS when the apparatus is in an inactive mode or an idle mode; a component for sending a first communication to the BS as part of a RACH process based at least in part on receiving the paging communication; a component for receiving a second communication from the BS based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, an indication of uplink resources, and an RRC release message, the RRC release message causing the apparatus to remain in an inactive mode or an idle mode while receiving the mobile-terminated downlink data; and a component for sending mobile-initiated uplink data to the BS using uplink resources while in the inactive mode or the idle mode.

[0012] In some aspects, an apparatus for wireless communication may include: a component for sending a paging communication to a UE when the UE is in an inactive mode or an idle mode; a component for receiving a first communication from the UE as part of a RACH process based at least in part on sending the paging communication; a component for sending a second communication to the UE based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, uplink resources that the UE is to use to send mobile-initiated uplink data when it is in the inactive mode or the idle mode, and an RRC release message that enables the UE to receive the mobile-terminated downlink data when it is in the inactive mode or the idle mode; and a component for receiving mobile-initiated uplink data from the UE and in the uplink resources, wherein the UE is to send mobile-initiated uplink data when it is in the inactive mode or the idle mode.

[0013] 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 generally described with reference to and illustrated by the accompanying drawings and description.

[0014] The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure in order that the following detailed description may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may easily serve as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, their organization and methods of operation, both together with the associated advantages, will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0018] Figure 3-Figure 5 is a diagram illustrating an example of small data reception terminated by a mobile station in idle and / or inactive mode in accordance with various aspects of the present disclosure.

[0019] Figure 6 is a diagram illustrating example processes performed, for example, by a UE according to various aspects of the present disclosure.

[0020] Figure 7 is a diagram illustrating example processes performed, for example, by a BS according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0021] 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 throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be comprehensive and complete, and the scope of the present disclosure will be fully conveyed 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, which is practiced using other structures, functions, or structures and functions other than or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0022] 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, etc. (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 the design constraints imposed on the overall system.

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

[0024] Figure 1is 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 some other wireless network, such as a 5G or NR network. The wireless network 100 may include a plurality of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE), and a BS may also be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0025] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. The BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5GNB", and "cell" may be used interchangeably herein.

[0026] In some aspects, the cell may not necessarily be fixed, and the geographic area of ​​the cell may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any suitable transport network.

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

[0028] The wireless network 100 may be a heterogeneous network including different types of BSs, for example, a macro BS, a pico BS, a femto BS, a relay BS, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0029] The network controller 130 may be coupled to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul. In some aspects, the wireless network 100 may include one or more network controllers 130. For example, the wireless network 100 may include a network controller 130 that implements an access and mobility management function (AMF) device, a network controller 130 that implements a user plane function (UPF) device, and the like. In some aspects, the AMF device and / or the UPF device may be included in the core network (e.g., a 5G / NR core network, which may be referred to as a next generation (NG) core) of the wireless network 100. The AMF device may manage authentication, activation, deactivation, and / or mobility functions associated with the UE 120. The AMF device may facilitate selection of a gateway (e.g., a serving gateway, a packet data network gateway, a UPF device, etc.) to serve traffic to and / or from the UE 120, may forward traffic to and from the UE 120 (e.g., control plane traffic), etc. The UPF device may serve as a session anchor and / or gateway for the UE 120, may forward traffic (e.g., user plane traffic, application traffic, etc.) between the UE 120 and an application server, a packet data network, a public network, another type of network, another UE 120, etc.

[0030] UE 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be fixed or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE can 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, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, 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), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

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

[0032] 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.

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

[0034] As noted above, providing Figure 1 As an example. Other examples can be related to Figure 1 Different than described.

[0035] Figure 2 A block diagram of a design 200 of a base station 110 and a UE 120 is shown, which may be Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0036] At the base station 110, the transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) 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)). If applicable, the transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 can process a corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM) or the like) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding can be used to generate synchronization signals to convey additional information.

[0037] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 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 UE 120 may be included in a housing.

[0038] On the uplink, at the UE 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 pre-coded and decoded 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 UE 120 and other UEs 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 UE 120. The receive processor 238 may provide decoded data to a data sink 239 and provide decoded control information to a 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.

[0039] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the base station 110 may perform one or more techniques associated with small data reception terminated by a mobile station in idle and / or 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 UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Figure 6 The process of 600 Figure 7 The operations of process 700 and / or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 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 one or more instructions are executed by one or more processors of base station 110 and / or UE 120, they may perform or direct, for example, Figure 6 The process of 600 Figure 7 The process 700 and / or operations of other processes as described herein. The scheduler 246 can schedule UEs to transmit data on the downlink and / or uplink.

[0040] In some aspects, UE 120 may include: a component for receiving a paging communication from BS 110 while UE 120 is in an inactive mode or an idle mode; a component for sending a first communication to BS 110 as part of a random access channel (RACH) procedure based at least in part on receiving the paging communication; a component for receiving a second communication from BS 110 based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, an indication of uplink resources, and a radio resource control (RRC) release message, the radio resource control (RRC) release message causing UE 120 to remain in an inactive mode or an idle mode while receiving the mobile-terminated downlink data; and a component for sending mobile-originated uplink data to BS 110 using uplink resources while in an inactive mode or an idle mode; etc. In some aspects, these components may include a combination of Figure 2 One or more components of UE 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, etc.

[0041] In some aspects, BS 110 may include: components for sending a paging communication to UE 120 when UE 120 is in an inactive mode or an idle mode; components for receiving a first communication from UE 120 as part of a RACH process based at least in part on sending the paging communication; components for sending a second communication to UE 120 based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, uplink resources that UE 120 is to use to send mobile-originated uplink data when in the inactive mode or the idle mode, and an RRC release message that enables UE 120 to receive mobile-terminated downlink data when in the inactive mode or the idle mode; components for receiving mobile-originated uplink data from UE 120 and in uplink resources, wherein UE 120 is to send mobile-originated uplink data when in the inactive mode or the idle mode; and the like. In some aspects, these components may include in conjunction with Figure 2 One or more components of BS 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 the like.

[0042] As noted above, providing Figure 2 As an example. Other examples can be related to Figure 2 Different than described.

[0043] A UE (e.g., UE 120) may support various communication modes, such as a connected mode, an inactive mode, an idle mode, and / or other communication modes. A UE operating in a connected mode (e.g., an RRC connected mode) may be active and communicatively connected (e.g., an RRC connection) to a BS (e.g., BS 110). The UE may be switched from a connected mode to an inactive mode and / or an idle mode based at least in part on various commands and / or communications received from the BS. For example, the UE may be switched from a connected mode to an idle mode based at least in part on receiving an RRC release message (e.g., an RRC release communication). In this case, the UE may release the connection with the BS and switch to an idle mode, wherein the UE may disable and / or deactivate one or more components of the UE, one or more component carriers and / or subcarriers, and / or other components and / or functions for the purpose of power saving and battery life extension of the UE.

[0044] As another example, the UE may transition from a connected mode to an inactive mode based at least in part on receiving an RRC release message (e.g., an RRC release with suspendConfig communication). In this case, the UE, the BS, and / or the network controller (e.g., the network controller 130) may store a UE context (e.g., an access stratum (AS) context, a higher layer configuration, etc.). This allows the UE and / or the BS to apply the stored UE context when the UE transitions from the inactive mode to a connected mode with the BS in order to resume communication with the BS, which reduces the delay time of transitioning to the inactive mode relative to transitioning from the idle mode to the connected mode.

[0045] The UE may transition from an inactive mode and / or an idle mode to a connected mode based at least in part on sending one or more communications to the BS. For example, the UE may transition from an inactive mode and / or an idle mode to a connected mode by sending an RRCSetupRequest communication, an RRCResumeRequst communication, etc. to the BS. The UE may send an RRCSetupRequest communication or an RRCResumeRequst communication as part of a RACH procedure with the BS, such as a contention-based or contention-free two-step RACH procedure, a contention-based or contention-free two-step RACH procedure, etc.

[0046] In some cases, a UE may receive a small amount of downlink data (e.g., a few hundred kilobytes, a maximum of a kilobyte, etc.) in a burst from another UE, an application server, a network controller (e.g., a UPF device, an AMF device, etc.), and / or other entities. These small amounts of mobile terminated (MT) downlink data (e.g., data destined for the UE) may include messaging applications, location data, small multimedia files, push notifications, keep-alive packets, sensor data, etc.

[0047] In some cases, an entity may send MT downlink data to a UE when the UE is in an idle mode or an inactive mode. In this case, the UE may transition to a connected mode by performing a RACH process with the BS to establish a connection with the BS, and receive MT downlink data from the BS when the UE is in connected mode. However, because of the consumption of network, processing and / or memory resources of the UE and the BS due to the signaling overhead of establishing a connection with the BS, transitioning to a connected mode to receive a small amount of MT downlink data may be inefficient. In addition, delaying the reception of MT downlink data until the UE is in a connected mode may increase the delay time for receiving MT downlink data and / or sending mobile-initiated (MO) uplink data in response to MT downlink data. In addition, if MT downlink data is sent to the UE in a burst, repeated transitions from an idle mode or an inactive mode to a connected mode to receive a small amount of MT downlink data may reduce or negate the power saving benefits of operating in an idle mode or an inactive mode.

[0048] Some aspects described herein provide techniques and apparatus for small data reception terminated by a mobile station in idle mode and / or inactive mode. In some aspects, a UE, a BS and / or other devices included in a wireless network may coordinate to allow a UE to receive a small amount of MT downlink data when in idle mode and / or inactive mode. In some aspects, when the UE is in idle mode or inactive mode, the BS may send a paging communication to the UE. The paging communication may indicate to the UE that MT downlink data is to be sent to the UE. The UE may send a first communication to the BS as part of a RACH process with the BS. The BS may send a second communication to the UE based at least in part on receiving the first communication. The second communication may include MT downlink data in an RRC release message. The UE may receive MT downlink data when in idle mode or inactive mode, and the RRC release message may cause the UE to terminate the RACH process and remain in idle mode or inactive mode. In some aspects, the second communication may also include an indication of an uplink resource, which the UE may use to send MO uplink data when in idle mode or inactive mode.

[0049] In this way, the UE can receive MT downlink data when it is in idle mode or inactive mode, and there is no need to switch from idle mode or inactive mode to connected mode. This reduces the signaling overhead required for sending a small amount of MT downlink data to the UE and for the UE to send MO uplink data, thereby saving network, processing and / or memory resources of the UE, BS and / or other devices included in the wireless network. In addition, this allows the UE to receive MT downlink data and send MO uplink data without establishing a connection (e.g., RRC connection) with the BS, which reduces the delay time for receiving MT downlink data and sending MO uplink data. In addition, this reduces the number of repeated transitions from idle mode or inactive mode to connected mode to receive a small amount of MT downlink data sent in a burst, which can increase the power saving of the UE.

[0050] Figure 3 is a diagram illustrating one or more examples 300 of small data reception terminated by a mobile station in an inactive mode according to various aspects of the present disclosure. Figure 3 As shown, example 300 may include communications between various components of a wireless network (e.g., wireless network 100), such as a UE (e.g., UE 120), multiple BSs (e.g., BS 110) (such as BS1 and BS2), a UPF device (e.g., network controller 130), etc. In some aspects, the UE may operate in an inactive mode.

[0051] like Figure 3 As shown, and by reference numeral 302, the UPF device may receive MT downlink data destined for the UE and may send the MT downlink data to BS 2. The MT downlink data may include a small amount of data, such as data associated with a messaging application, location data, small multimedia files, push notifications, keep-alive packets, sensor data, etc., originating from an application server, another UE, a BS, a network controller, and / or another device included in the wireless network or connected to another network.

[0052] In some aspects, the UPF device may send the MT downlink data to BS2 based at least in part on a determination that BS2 is an anchor BS for the UE (eg, the BS to which the UE was last communicatively connected before transitioning to the inactive mode).

[0053] like Figure 3As further shown, and by reference numeral 304, BS2 may send a radio access network (RAN) paging communication to BS1 based at least in part on receiving the MT downlink data. In some aspects, BS2 may send the RAN paging communication to BS1 based at least in part on determining that the UE is located in a cell of BS1, which may occur, for example, due to mobility of the UE after transitioning to an inactive mode. In some aspects, BS2 may send the RAN paging communication over a backhaul interface such as an Xn interface and / or another type of backhaul interface.

[0054] In some aspects, the RAN paging communication may include an MT Early Data Transfer (MT-EDT) indication and a resume identifier (resumeID) or another type of UE identifier associated with the UE. The MT-EDT indication may be an indication that MT downlink data is being stored or buffered at BS2 and is to be sent to a UE (e.g., a UE associated with the resumeID identified in the paging communication). The resumeID associated with the UE may be a UE identifier assigned to the UE by BS2 for the purpose of storing and reactivating a UE context associated with the UE. The UE may provide the resumeID to the BS (e.g., BS1), and the BS may retrieve the UE context associated with the UE so that the UE may use the UE context to transition from an inactive mode to a connected mode.

[0055] like Figure 3 As further shown and indicated by reference numeral 306, BS1 may send a UE paging communication to the UE based at least in part on receiving a RAN paging communication identifying the MT-EDT indication and a resumeID associated with the UE. In some aspects, the UE paging communication may include the MT-EDT indication and the resumeID associated with the UE.

[0056] The UE may receive a UE paging communication (e.g., while in an inactive mode) and may descramble and / or decode the UE paging communication to determine whether the UE paging communication is directed to the UE. For example, the UE may determine that the UE paging communication is directed to the UE based at least in part on the UE paging communication identifying a resumeID associated with the UE.

[0057] like Figure 3 As further shown and indicated by reference numeral 308, the UE may initiate a RACH procedure with the BS and may send a first communication as part of the RACH procedure. In some aspects, the UE may send the first communication based at least in part on identifying an MT-EDT indication in a UE paging communication. The first communication may include an RRCResumeRequest communication or another type of RACH communication to initiate a connection with the BS.

[0058] In some aspects, the first communication may identify a resumeID of the UE. In some aspects, the first communication may further identify an authentication token associated with the UE, such as an integrity recovery message authentication code (resumeMAC-I), a short resumeMAC-I, etc., which may be used to verify the authenticity of the first communication. In some aspects, the first communication may include an MT-EDT preamble, which may indicate that the first communication is a response to an MT-EDT indication.

[0059] like Figure 3 As further shown, and by reference numeral 310, BS1 may receive the first communication and may send a UE context request to BS2 based at least in part on receiving the first communication. The UE context request may be a request to retrieve a UE context associated with the UE stored at BS2. In some aspects, the UE context request may identify a resumeID associated with the UE, which BS2 may use to identify the UE context associated with the UE. In some aspects, the UE context request may also identify an authentication token associated with the UE, which BS2 may use to verify the authenticity of the first communication.

[0060] like Figure 3 As further shown, and by reference numeral 312, BS2 may send a UE context response to BS2 based at least in part on receiving the UE context request from BS1. In some aspects, BS2 may send the UE context request based at least in part on identifying a UE context associated with the UE (e.g., based at least in part on a resumeID identified in the UE context request), based at least in part on verifying an authenticity authentication of the first communication (e.g., based at least in part on an authentication token identified in the UE context request), and the like.

[0061] In some aspects, BS2 may determine that BS2 is storing or buffering MT downlink data to the UE. In this case, the UE context response may include the MT downlink data. In addition, in some aspects, the UE context response may include a fast release indication. The fast release indication may be an indication to BS1 that the UE is to remain in an inactive mode while and after receiving the MT downlink data.

[0062] In some aspects, BS2 may determine to include a fast release indication in the UE context response message based at least in part on determining that the UE is expected not to send MO uplink data in response to the MT downlink data, or that the UE is expected to send a small amount of MO uplink data in response to the MT downlink data. In some aspects, BS2 may determine to include a fast release indication in the UE context response message based at least in part on subscription information associated with the UE (e.g., subscription information of the wireless network, subscription information of one or more services provided by the wireless network or an application server, etc.), at least in part on the data type of the MT downlink data, at least in part on a historical traffic pattern associated with the UE, at least in part on an indication from a UPF device and / or another network controller, etc.

[0063] like Figure 3 As further shown, and by reference numeral 314, BS1 may receive a UE context response, and may send a second communication as part of a RACH procedure based at least in part on receiving the UE context response. The second communication may be a Msg2 communication or a Msg4 communication in a four-step RACH procedure, a MsgB communication in a two-step RACH procedure, or the like.

[0064] In some aspects, the second communication may include MT downlink data to the UE. In addition, the second communication may include an RRC release message that may cause the UE and the BS to terminate the RACH procedure so that the UE remains in an inactive mode while the UE receives the MT downlink data and after receiving the MT downlink data. In this case, the UE may identify the RRC release message included in the second communication and may terminate the RACH procedure to remain in an inactive mode while receiving the MT downlink data and after receiving the MT downlink data based at least in part on identifying the RRC release message. The RRC release message may be an RRCRelease with a suspendConfig communication, which may cause the UE and / or BS1 to store the UE context of the UE.

[0065] In some aspects, the second communication may further include an indication of uplink resources, which may include time domain resources (e.g., one or more OFDM symbols, one or more time slots, etc.) and / or frequency domain resources (e.g., one or more subcarriers, one or more component carriers, etc.), wherein when in inactive mode, the UE may send MO uplink data (e.g., which may be associated with MO downlink data, or may not be associated with MO downlink data). In some aspects, the MO downlink data, the RRC release message, and the indication of the uplink resources may be multiplexed (e.g., time division multiplexing and / or frequency division multiplexing) in the second communication.

[0066] like Figure 3 As further shown, and by reference numeral 316, the UE may send MO uplink data using the uplink resources identified in the second communication. In this case, the UE may send MO uplink data to BS1, and when in inactive mode, BS1 may send or forward the MO uplink data to the UPF device.

[0067] In this way, the UE can receive MT downlink data while in inactive mode without switching from inactive mode to connected mode. This reduces the signaling overhead required for sending a small amount of MT downlink data to the UE and the UE to send MO uplink data, thereby saving network, processing and / or memory resources of the UE, the BS and / or other devices included in the wireless network. In addition, this allows the UE to receive MT downlink data and send MO uplink data without establishing a connection (e.g., an RRC connection) with the BS, which reduces the delay time for receiving MT downlink data and sending MO uplink data. In addition, this reduces the number of repeated transitions from inactive mode to connected mode to receive a small amount of MT downlink data sent in a burst, which can increase the power saving of the UE.

[0068] As noted above, providing Figure 3 As one or more examples. Other examples can be related to Figure 3 Different than described.

[0069] Figure 4 4 is a diagram illustrating one or more examples 400 of small data reception terminated by a mobile station in idle mode according to various aspects of the present disclosure. Figure 4As shown, example 400 may include communications between various components of a wireless network (e.g., wireless network 100), such as a UE (e.g., UE 120), multiple BSs (e.g., BS 110) (such as BS1 and BS2), a UPF device (e.g., network controller 130), an AMF device (e.g., network controller 130), etc. In some aspects, the UE may operate in an idle mode.

[0070] like Figure 4 As shown, and by reference numeral 402, the UPF device may receive MT downlink data destined for the UE and may send an MT downlink indication to the AMF device. The MT downlink data may include a small amount of data, such as data associated with a messaging application, location data, small multimedia files, push notifications, keep-alive packets, sensor data, etc., originating from an application server, another UE, a BS, a network controller, and / or another device included in the wireless network or connected to another network.

[0071] In some aspects, the MT downlink data indication may be an indication that the UPF is storing and / or buffering MT downlink data to the UE. In some aspects, the UPF device may send the MT downlink data indication to the AMF device based at least in part on determining that the AMF device is associated with a RAN including BS1 and manages access and mobility of the RAN, based at least in part on determining that the UE is located in a cell of BS1, etc.

[0072] like Figure 4 As further shown, and by reference numeral 404, the AMF device may send an N2 paging communication to BS1 based at least in part on receiving the MT downlink data indication from the UPF device. In some aspects, the AMF device may send the N2 paging communication to BS1 based at least in part on determining that the UE is located in a cell of BS1, which may occur, for example, due to the mobility of the UE after transitioning to idle mode. In some aspects, the N2 paging communication may be a paging communication sent over a backhaul interface, such as an N2 interface and / or another type of backhaul interface.

[0073] In some aspects, the N2 paging communication may include an MT-EDT indication, a temporary mobile subscription identifier (TMSI) (e.g., a next generation shortened TMSI (NG-S-TMSI) and / or another type of TMSI) or another type of UE identifier associated with the UE (e.g., resumeID), and a fast release indication. The MT-EDT indication may be an indication that MT downlink data is being stored and / or buffered at the UPF device and is to be sent to a UE (e.g., a UE associated with the TMSI identified in the N2 paging communication).

[0074] The TMSI associated with the UE may be a UE identifier assigned to the UE for the purpose of paging the UE when the UE is in idle mode. In some aspects, the AMF device may generate the TMSI and assign the TMSI to the UE. In some aspects, the AMF device may generate the TMSI based at least in part on one or more parameters associated with the AMF device and / or the UE (such as an AMF pointer, an AMF set identifier, another identifier associated with the UE, etc.). The UE may provide the TMSI to the BS (e.g., BS1) based at least in part on being paged by the BS (e.g., based at least in part on receiving a UE paging communication from the BS) to establish the identity of the UE to the BS. The resumeID associated with the UE may be a UE identifier assigned to the UE for the purpose of storing and reactivating a UE context associated with the UE.

[0075] The fast release indication may be an indication to BS1 indicating that the UE is to remain in idle mode while and after receiving the MT downlink data. In some aspects, the AMF device may determine to include the fast release indication in the N2 paging communication based at least in part on determining that the UE is expected not to send MO uplink data in response to the MT downlink data, or that the UE is expected to send a small amount of MO uplink data in response to the MT downlink data. In some aspects, the AMF device may determine that the UE is expected not to send MO uplink data in response to the MT downlink data, or that the UE is expected to send a small amount of MO uplink data in response to the MT downlink data, based at least in part on subscription information associated with the UE (e.g., subscription information of the wireless network, subscription information of one or more services provided by the wireless network or an application server, etc.), based at least in part on the data type of the MT downlink data, based at least in part on a historical traffic pattern associated with the UE, based at least in part on an indication from a UPF device and / or another network controller, and the like.

[0076] like Figure 4 As further shown and indicated by reference numeral 406, BS1 may send a UE paging communication to the UE based at least in part on receiving an N2 paging communication identifying the MT-EDT indication and the TMSI and / or resumeID associated with the UE. In some aspects, the UE paging communication may include the MT-EDT indication and the TMSI and / or resumeID associated with the UE.

[0077] The UE may receive a UE paging communication (e.g., while in idle mode) and may descramble and / or decode the UE paging communication to determine whether the UE paging communication is directed to the UE. For example, the UE may determine that the UE paging communication is directed to the UE based at least in part on the UE paging communication identifying a TMSI and / or a resume ID associated with the UE.

[0078] like Figure 4 As further shown and indicated by reference numeral 408, the UE may initiate a RACH procedure with the BS and may send a first communication as part of the RACH procedure. In some aspects, the UE may send the first communication based at least in part on identifying an MT-EDT indication in a UE paging communication. The first communication may include an RRCResumeRequest communication, an RRCSetupRequest communication, or another type of RACH communication to initiate connection establishment with the BS.

[0079] In some aspects, the first communication may include a resumeID so that the BS can retrieve the UE context associated with the UE so that the UE can use the UE context to transition from idle mode to connected mode. In some aspects, the first communication may identify the TMSI of the UE so that the BS can identify the UE. In some aspects, the first communication may further identify an authentication token associated with the UE, such as a resumeMAC-I, a short resumeMAC-I, etc., which can be used to verify the authenticity of the first communication. In some aspects, the first communication may include an MT-EDT preamble, which may indicate that the first communication is a response to an MT-EDT indication.

[0080] like Figure 4 As further shown, and by reference numeral 410, BS1 may receive a first communication and may send a UE context request to BS2 based at least in part on receiving the first communication. In some aspects, BS1 may send the UE context request to BS2 based at least in part on BS2 being an anchor BS for the UE (e.g., the BS to which the UE was last communicatively connected before transitioning to idle mode) and storing a UE context associated with the UE. The UE context request may be a request to retrieve a UE context stored at BS2. In some aspects, the UE context request may identify a resumeID associated with the UE, which BS2 may use to identify the UE context associated with the UE. In some aspects, the UE context request may also identify an authentication token associated with the UE, which BS2 may use to verify the authenticity of the first communication.

[0081] like Figure 4As further shown, and by reference numeral 412, BS2 may send a UE context response to BS2 based at least in part on receiving the UE context request from BS1. In some aspects, BS2 may send the UE context request based at least in part on identifying a UE context associated with the UE (e.g., based at least in part on a resumeID identified in the UE context request), based at least in part on verifying authenticity authentication of the first communication (e.g., based at least in part on an authentication token identified in the UE context request), etc.

[0082] like Figure 4 As further shown, and by reference numeral 414, BS1 may receive a UE context response, and may jointly coordinate a path switch for the UE based at least in part on receiving the UE context response. The path switch may include converting a communication path between the UE and the UPF device from being served by BS2 to being served by BS1. In this case, BS1 may forward communications between the UE and the UPF device based at least in part on the path switch.

[0083] like Figure 4 As further shown and indicated by reference numeral 416, BS1 may send a second communication as part of a RACH procedure based at least in part on the communication path associated with the UE being switched to BS1. The second communication may be a Msg2 communication or a Msg4 communication in a four-step RACH procedure, a MsgB communication in a two-step RACH procedure, or the like.

[0084] In some aspects, the second communication may include MT downlink data to the UE. In addition, the second communication may include an RRC release message, which may cause the UE and the BS to terminate the RACH process so that the UE remains in idle mode while receiving the MT downlink data and after receiving the MT downlink data. In this case, the UE may identify the RRC release message included in the second communication, and may terminate the RACH process based at least in part on identifying the RRC release message to remain in idle mode while receiving the MT downlink data and after receiving the MT downlink data. The RRC release message may be an RRCRelease communication, an RRCRelease with a suspendConfig communication (e.g., which may cause the UE and / or BS1 to store the UE context of the UE), etc.

[0085] In some aspects, the second communication may further include an indication of uplink resources, which may include time domain resources (e.g., one or more OFDM symbols, one or more time slots, etc.) and / or frequency domain resources (e.g., one or more subcarriers, one or more component carriers, etc.), wherein the UE may send MO uplink data (e.g., which may or may not be associated with MT downlink data) when in idle mode. In some aspects, the MT downlink data, the RRC release message, and the indication of the uplink resources may be multiplexed (e.g., time division multiplexing and / or frequency division multiplexing) in the second communication.

[0086] like Figure 4 As further shown, and by reference numeral 418, the UE may send MO uplink data using the uplink resources identified in the second communication. In this case, the UE may send MO uplink data to BS1, and when in idle mode, BS1 may send or forward the MO uplink data to the UPF device.

[0087] In this way, the UE can receive MT downlink data while in idle mode, and there is no need to switch from idle mode to connected mode. This reduces the signaling overhead required for sending a small amount of MT downlink data to the UE and the UE to send MO uplink data, thereby saving network, processing and / or memory resources of the UE, the BS and / or other devices included in the wireless network. In addition, this allows the UE to receive MT downlink data and send MO uplink data without establishing a connection (e.g., RRC connection) with the BS, which reduces the delay time for receiving MT downlink data and sending MO uplink data. In addition, this reduces the number of repeated transitions from idle mode to connected mode to receive a small amount of MT downlink data sent in a burst, which can increase the power saving of the UE.

[0088] As noted above, providing Figure 4 As one or more examples. Other examples can be related to Figure 4 Different than described.

[0089] Figure 5 1 is a diagram illustrating one or more examples 500 of small data reception terminated by a mobile station in idle mode according to various aspects of the present disclosure. Figure 5 As shown, example 500 may include communications between various components of a wireless network (e.g., wireless network 100), such as a UE (e.g., UE 120), a BS (e.g., BS 110), a UPF device (e.g., network controller 130), an AMF device (e.g., network controller 130), etc. In some aspects, the UE may operate in an idle mode.

[0090] like Figure 5 As shown, and by reference numeral 502, the UPF device may receive MT downlink data destined for the UE and may send an MT downlink request to the AMF device. The MT downlink data may include a small amount of data, such as data associated with a messaging application, location data, small multimedia files, push notifications, keep-alive packets, sensor data, etc., originating from an application server, another UE, a BS, a network controller, and / or another device included in the wireless network or connected to another network.

[0091] In some aspects, the MT downlink data request may be a request to send MT downlink data to the UE. In some aspects, the UPF device may send the MT downlink data request to the AMF device based at least in part on determining that the AMF device is associated with a RAN including the BS and manages access and mobility of the RAN, based at least in part on determining that the UE is located in a cell of the BS, etc.

[0092] like Figure 5 As further shown, and by reference numeral 504, the AMF device may send an N2 paging communication to the BS based at least in part on receiving a MT downlink data request from the UPF device. In some aspects, the AMF device may send the N2 paging communication to the BS based at least in part on determining that the UE is located in a cell of the BS, which may occur, for example, due to the mobility of the UE after transitioning to idle mode. In some aspects, the N2 paging communication may be a paging communication sent over a backhaul interface, such as an N2 interface and / or another type of backhaul interface.

[0093] In some aspects, the N2 paging communication may include an MT-EDT indication, a TMSI (e.g., an NG-S-TMSI and / or another type of TMSI) or another type of UE identifier associated with the UE, and a fast release indication. The MT-EDT indication may be an indication that MT downlink data is being stored or buffered at the AMF device and is to be sent to a UE (e.g., a UE associated with a TMSI identified in the N2 paging communication).

[0094] The TMSI associated with the UE may be a UE identifier assigned to the UE for the purpose of paging the UE when the UE is in idle mode. In some aspects, the AMF device may generate the TMSI and assign the TMSI to the UE. In some aspects, the AMF device may generate the TMSI based at least in part on one or more parameters associated with the AMF device and / or the UE (such as an AMF pointer, an AMF set identifier, another identifier associated with the UE, etc.). The UE may provide the TMSI to the BS (e.g., BS1) based at least in part on being paged by the BS (e.g., based at least in part on receiving a UE paging communication from the BS) so as to establish the identity of the UE to the BS.

[0095] The fast release indication may be an indication to the BS indicating that the UE is to remain in idle mode while and after receiving the MT downlink data. In some aspects, the AMF device may determine to include the fast release indication in the N2 paging communication based at least in part on determining that the UE is expected to not send MO uplink data in response to the MT downlink data, or determining that the UE is expected to send a small amount of MO uplink data in response to the MT downlink data. In some aspects, the AMF device may determine that the UE is expected to not send MO uplink data in response to the MT downlink data based at least in part on subscription information associated with the UE (e.g., subscription information of the wireless network, subscription information of one or more services provided by the wireless network or application server, etc.), at least in part on the data type of the MT downlink data, at least in part on the historical traffic pattern associated with the UE, at least in part on an indication from a UPF device and / or another network controller, and the like.

[0096] like Figure 5 As further shown and indicated by reference numeral 506, the BS may send a UE paging communication to the UE based at least in part on receiving the N2 paging communication identifying the MT-EDT indication and the TMSI associated with the UE. In some aspects, the UE paging communication may include the MT-EDT indication and the TMSI associated with the UE.

[0097] The UE may receive a UE paging communication (e.g., while in idle mode) and may descramble and / or decode the UE paging communication to determine whether the UE paging communication is directed to the UE. For example, the UE may determine that the UE paging communication is directed to the UE based at least in part on the UE paging communication identifying a TMSI associated with the UE.

[0098] like Figure 5As further shown, and by reference numeral 508, the UE may initiate a RACH procedure with the BS and may send a first communication as part of the RACH procedure. In some aspects, the UE may send the first communication based at least in part on identifying an MT-EDT indication in a UE paging communication. The first communication may include an RRC EsumeRequest communication, an RRC Setup Request communication, or another type of RACH communication to initiate a connection establishment with the BS. In some aspects, the first communication may include an RRC Early Data Request. The RRC Early Data Request may be a request by the AMF device to send data to the UE.

[0099] like Figure 5 As further shown, and by reference numeral 510, the BS may receive a first communication and may send a MT downlink data request to the AMF device based at least in part on receiving the first communication. In some aspects, the MT downlink data request may be a request by the AMF device to the BS for MT downlink data stored and / or buffered at the AMF device and destined for the UE. In some aspects, the BS may send the MT downlink data request to the AMF device based at least in part on identifying an RRC early data request from the UE. In some aspects, the MT downlink data request may be included in a non-access stratum (NAS) packet data unit (PDU) request communication.

[0100] like Figure 5 As further shown, and by reference numeral 512, the AMF device may send MT downlink data to the BS based at least in part on receiving a MT downlink data request from the BS. In some aspects, the MT downlink data may be included in one or more NAS PDUs.

[0101] like Figure 5 As further shown, and by reference numeral 514, the BS may send a second communication as part of a RACH procedure based at least in part on receiving MT downlink data from the AMF device. The second communication may be a Msg2 communication or a Msg4 communication in a four-step RACH procedure, a MsgB communication in a two-step RACH procedure, etc.

[0102] In some aspects, the second communication may include MT downlink data to the UE. In addition, the second communication may include an RRC release message, which may cause the UE and the BS to terminate the RACH process so that the UE remains in idle mode while receiving the MT downlink data and after receiving the MT downlink data. In this case, the UE may identify the RRC release message included in the second communication, and may terminate the RACH process based at least in part on identifying the RRC release message to remain in idle mode while receiving the MT downlink data and after receiving the MT downlink data. The RRC release message may be an RRCRelease communication, an RRCRelease with a suspendConfig communication (e.g., which may cause the UE and / or the BS to store the UE context of the UE), etc.

[0103] In some aspects, the second communication may further include an indication of uplink resources, which may include time domain resources (e.g., one or more OFDM symbols, one or more time slots, etc.) and / or frequency domain resources (e.g., one or more subcarriers, one or more component carriers, etc.), wherein the UE may send MO uplink data (e.g., which may or may not be associated with MT downlink data) when in idle mode. In some aspects, the MT downlink data, the RRC release message, and the indication of the uplink resources may be multiplexed (e.g., time division multiplexing and / or frequency division multiplexing) in the second communication.

[0104] like Figure 5 As further shown, and by reference numeral 516, the UE may send MO uplink data using the uplink resources identified in the second communication. In this case, the UE may send MO uplink data to the BS, and when in idle mode, the BS may send or forward the MO uplink data to the AMF device.

[0105] In this way, the UE can receive MT downlink data while in idle mode, and there is no need to switch from idle mode to connected mode. This reduces the signaling overhead required for sending a small amount of MT downlink data to the UE and the UE to send MO uplink data, thereby saving network, processing and / or memory resources of the UE, the BS and / or other devices included in the wireless network. In addition, this allows the UE to receive MT downlink data and send MO uplink data without establishing a connection (e.g., RRC connection) with the BS, which reduces the delay time for receiving MT downlink data and sending MO uplink data. In addition, this reduces the number of repeated transitions from idle mode to connected mode to receive a small amount of MT downlink data sent in a burst, which can increase the power saving of the UE.

[0106] As noted above, providing Figure 5 As one or more examples. Other examples can be related to Figure 5 Different than described.

[0107] Figure 6 is a diagram illustrating an example process 600, performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 600 is an example of operations in which a UE (eg, UE 120) performs paging for mobile terminated small data reception in an idle and / or inactive mode.

[0108] like Figure 6 As shown, in some aspects, process 600 may include receiving a paging communication from a BS when the UE is in an inactive mode or an idle mode (block 610). For example, when the UE is in an inactive mode or an idle mode, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may receive a paging communication from a BS, as described above.

[0109] like Figure 6 As further shown, in some aspects, process 600 may include sending a first communication to the BS as part of a RACH procedure based at least in part on receiving the paging communication (block 620). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may send a first communication to the BS as part of a RACH procedure based at least in part on receiving the paging communication, as described above.

[0110] like Figure 6 As further shown, in some aspects, process 600 may include receiving, based at least in part on sending the first communication, a second communication from the BS, the second communication including mobile-terminated downlink data, an indication of uplink resources, and an RRC release message, the RRC release message causing the UE to remain in an inactive mode or idle mode while receiving the mobile-terminated downlink data (block 630). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may receive, based at least in part on sending the first communication, a second communication from the BS, the second communication including mobile-terminated downlink data, an indication of uplink resources, and an RRC release message, the RRC release message causing the UE to remain in an inactive mode or idle mode while receiving the mobile-terminated downlink data, as described above.

[0111] like Figure 6As further shown, in some aspects, process 600 may include using uplink resources to send mobile-originated uplink data to the BS while in an inactive mode or idle mode (block 640). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may use uplink resources to send mobile-originated uplink data to the BS while in an inactive mode or idle mode, as described above.

[0112] Process 600 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.

[0113] In a first aspect, the first communication is an RRC recovery request or an RRC early data request, and the second communication comprises an Msg2 communication, an Msg4 communication or an MsgB communication. In a second aspect, alone or in combination with the first aspect, the RACH procedure is a two-step RACH procedure or a four-step RACH procedure. In a third aspect, alone or in combination with one or more of the first or second aspects, mobile station terminated downlink data and an RRC release message are multiplexed in the second communication.

[0114] although Figure 6 Example blocks of process 600 are shown, but in some aspects process 600 may include Figure 6 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 600 may be included. Additionally or alternatively, two or more blocks of process 600 may be performed in parallel.

[0115] Figure 7 is a diagram illustrating an example process 700, performed, for example, by a BS, in accordance with various aspects of the present disclosure. Example process 700 is an example of operations in which a BS (eg, BS 110) performs paging for mobile-terminated small data reception in an idle and / or inactive mode.

[0116] like Figure 7 As shown, in some aspects, process 700 may include sending a paging communication to the UE when the UE is in an inactive mode or an idle mode (block 710). For example, the BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may send a paging communication to the UE when the UE is in an inactive mode or an idle mode, as described above.

[0117] like Figure 7As further shown, in some aspects, process 700 may include receiving a first communication from the UE as part of a RACH procedure based at least in part on sending the paging communication (block 720). For example, the BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may receive the first communication from the UE as part of a RACH procedure based at least in part on sending the paging communication, as described above.

[0118] like Figure 7 As further shown, in some aspects, process 700 may include sending a second communication to the UE based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, uplink resources that the UE is to use to send mobile-initiated uplink data when in the inactive mode or the idle mode, and an RRC release message that enables the UE to receive mobile-terminated downlink data when in the inactive mode or the idle mode (block 730). For example, the BS (e.g., using the transmit processor 220, the receive processor 238, the controller / processor 240, the memory 242, etc.) may send the second communication to the UE based at least in part on sending the first communication, the second communication including mobile-terminated downlink data, uplink resources that the UE is to use to send mobile-initiated uplink data when in the inactive mode or the idle mode, and an RRC release message that enables the UE to receive mobile-terminated downlink data when in the inactive mode or the idle mode, as described above.

[0119] like Figure 7 As further shown, in some aspects, process 700 may include receiving mobile-originated uplink data from a UE and in an uplink resource, wherein the UE is to transmit the mobile-originated uplink data when in an inactive mode or an idle mode (block 740). For example, the BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may receive mobile-originated uplink data from the UE and in an uplink resource, as described above. In some aspects, the UE is to transmit the mobile-originated uplink data when in an inactive mode or an idle mode.

[0120] 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.

[0121] In the first aspect, sending a second communication including an RRC release message includes sending a second communication including an RRC release message based at least in part on receiving a fast release indication for the UE. In the second aspect, alone or in combination with the first aspect, the process 700 further includes receiving a fast release indication in an N2 paging communication from a network controller, or receiving a fast release indication in a RAN paging communication from another BS.

[0122] In a third aspect, alone or in combination with one or more of the first and second aspects, sending a second communication including mobile-terminated downlink data includes sending a second communication including mobile-terminated downlink data based at least in part on receiving the mobile-terminated downlink data. In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 700 further includes receiving the mobile-terminated downlink data from a network controller, or receiving the mobile-terminated downlink data from another BS.

[0123] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the process 700 further comprises sending the mobile station originated uplink data to at least one of another BS or a network controller.

[0124] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the first communication is an RRC recovery request or an RRC early data request, and the second communication includes an Msg2 communication, an Msg4 communication, or an MsgB communication. In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the RACH procedure is a two-step RACH procedure or a four-step RACH procedure. In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the mobile station terminated downlink data and the RRC release message are multiplexed in the second communication.

[0125] 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 differently arranged blocks than those depicted in the process 700 may be included. Additionally or alternatively, two or more blocks of process 700 may be performed in parallel.

[0126] The above 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 are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0127] 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.

[0128] As used herein, satisfying a threshold may refer to a value being 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.

[0129] 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 does not limit these aspects. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code - it is understood that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0130] Although specific combinations of features are recorded in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically recorded in the claims and / or not specifically disclosed in the specification. Although each dependent claim listed below can be directly subordinate to only one claim, the disclosure of various aspects includes that each dependent claim is combined with each other claim in the claim set. The phrase "at least one" mentioned in the list of items refers to any combination of these items, including single members. 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, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b and c).

[0131] Elements, actions or instructions used herein should not be interpreted as critical or essential unless explicitly described as such. In addition, as used herein, the articles "a" and "an" are 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". In the case of only meaning one item, the phrase "only one" or similar language is used. In addition, as used herein, the terms "has", "have", "having" etc. are intended to 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 method of wireless communication performed by a user equipment UE, comprising: receiving, while the UE is in an inactive mode or an idle mode, a paging communication from a first network entity, the paging communication comprising a mobile terminated early data transfer (MT-EDT) indication and a resumption identifier of the UE, wherein the MT-EDT indication is an indication that MT downlink data is stored at a second network entity, and wherein the resumption identifier is a UE identifier assigned to the UE by the second network entity for the purpose of storing and reactivating a UE context associated with the UE; sending a first communication to the first network entity as part of a random access channel (RACH) procedure based at least in part on receiving the paging communication, the first communication including the recovery identifier; Based at least in part on sending the first communication, receiving a second communication from the first network entity, the second communication comprising: Mobile terminated downlink data, an indication of uplink resources, and a radio resource control (RRC) release message that causes the UE to remain in the inactive mode or the idle mode while receiving downlink data terminated by the mobile station; as well as When in the inactive mode or the idle mode, the uplink resources are used to send uplink data originated by a mobile station to the first network entity.

2. The method of claim 1, wherein the first communication is an RRC resume request or an RRC early data request; and The second communication includes: Msg2 communication, Msg4 communication, or MsgB communication.

3. The method according to claim 1, wherein the RACH procedure is a two-step RACH procedure or a four-step RACH procedure.

4. The method of claim 1, wherein the mobile station terminated downlink data and the RRC release message are multiplexed in the second communication.

5. A method of wireless communication performed by a first network entity, comprising: sending a paging communication to a user equipment (UE) when the UE is in an inactive mode or an idle mode, the paging communication comprising a mobile terminated early data transmission (MT-EDT) indication and a resumption identifier of the UE, wherein the MT-EDT indication is an indication that MT downlink data is stored at a second network entity, and wherein the resumption identifier is a UE identifier assigned to the UE by the second network entity for the purpose of storing and reactivating a UE context associated with the UE; receiving a first communication from the UE as part of a random access channel (RACH) procedure based at least in part on sending the paging communication, the first communication including the recovery identifier; Based at least in part on sending the first communication, sending a second communication to the UE, the second communication comprising: Mobile terminated downlink data, uplink resources, which the UE is to use to send mobile station initiated uplink data when in the inactive mode or the idle mode, and a radio resource control (RRC) release message, which enables the UE to receive downlink data terminated by the mobile station when in the inactive mode or the idle mode; as well as receiving mobile station originated uplink data from said UE and in said uplink resources, The UE, when in the inactive mode or the idle mode, is to send uplink data initiated by the mobile station.

6. The method of claim 5, wherein sending the second communication including the RRC release message comprises: The second communication including the RRC release message is sent based at least in part on receiving a fast release indication for the UE.

7. The method according to claim 6, further comprising: receiving said fast release indication in an N2 paging communication from a network controller, or The fast release indication is received in a Radio Access Network, RAN, paging communication from the second network entity.

8. The method of claim 5, wherein sending the second communication including the mobile station terminated downlink data comprises: The second communication including the mobile-terminated downlink data is sent based at least in part on receiving the mobile-terminated downlink data.

9. The method according to claim 8, further comprising: receiving said mobile station terminated downlink data from a network controller, or The mobile station terminated downlink data is received from the second network entity.

10. The method according to claim 5, further comprising: Sending uplink data initiated by the mobile station to at least one of the following: the second network entity, or Network controller.

11. The method of claim 5, wherein the first communication is an RRC resume request or an RRC early data request; and The second communication includes: Msg2 communication, Msg4 communication, or MsgB communication.

12. The method of claim 5, wherein the RACH procedure is a two-step RACH procedure or a four-step RACH procedure.

13. The method of claim 5, wherein the mobile-terminated downlink data and the RRC release message are multiplexed in the second communication.

14. A user equipment UE for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the memory and the one or more processors being configured to: receiving, while the UE is in an inactive mode or an idle mode, a paging communication from a first network entity, the paging communication comprising a mobile terminated early data transfer (MT-EDT) indication and a resumption identifier of the UE, wherein the MT-EDT indication is an indication that MT downlink data is stored at a second network entity, and wherein the resumption identifier is a UE identifier assigned to the UE by the second network entity for the purpose of storing and reactivating a UE context associated with the UE; sending a first communication to the first network entity as part of a random access channel (RACH) procedure based at least in part on receiving the paging communication, the first communication including the recovery identifier; as well as Based at least in part on sending the first communication, receiving a second communication from the first network entity, the second communication comprising: Mobile terminated downlink data, an indication of uplink resources, and a radio resource control (RRC) release message that causes the UE to remain in the inactive mode or the idle mode while receiving downlink data terminated by the mobile station; as well as When in the inactive mode or the idle mode, the uplink resources are used to send uplink data originated by a mobile station to the first network entity.

15. A first network entity for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the memory and the one or more processors being configured to: sending a paging communication to a user equipment (UE) when the UE is in an inactive mode or an idle mode, the paging communication comprising a mobile terminated early data transmission (MT-EDT) indication and a resumption identifier of the UE, wherein the MT-EDT indication is an indication that MT downlink data is stored at a second network entity, and wherein the resumption identifier is a UE identifier assigned to the UE by the second network entity for the purpose of storing and reactivating a UE context associated with the UE; receiving a first communication from the UE as part of a random access channel (RACH) procedure based at least in part on sending the paging communication, the first communication including the recovery identifier; Based at least in part on sending the first communication, sending a second communication to the UE, the second communication comprising: Mobile terminated downlink data, uplink resources, which the UE is to use to send mobile station initiated uplink data when in the inactive mode or the idle mode, and a radio resource control (RRC) release message, which enables the UE to receive downlink data terminated by the mobile station when in the inactive mode or the idle mode; as well as receiving mobile station originated uplink data from said UE and in said uplink resources, The UE, when in the inactive mode or the idle mode, is to send uplink data initiated by the mobile station.

16. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions, which, when executed by one or more processors of a user equipment UE, cause the one or more processors to: receiving, while the UE is in an inactive mode or an idle mode, a paging communication from a first network entity, the paging communication comprising a mobile terminated early data transfer (MT-EDT) indication and a resumption identifier of the UE, wherein the MT-EDT indication is an indication that MT downlink data is stored at a second network entity, and wherein the resumption identifier is a UE identifier assigned to the UE by the second network entity for the purpose of storing and reactivating a UE context associated with the UE; sending a first communication to the first network entity as part of a random access channel (RACH) procedure based at least in part on receiving the paging communication, the first communication including the recovery identifier; as well as Based at least in part on sending the first communication, receiving a second communication from the first network entity, the second communication comprising: Mobile terminated downlink data, an indication of uplink resources, and a radio resource control (RRC) release message that causes the UE to remain in the inactive mode or the idle mode while receiving downlink data terminated by the mobile station; as well as When in the inactive mode or the idle mode, the uplink resources are used to send uplink data originated by a mobile station to the first network entity.

17. A non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions that, when executed by one or more processors of a first network entity, cause the one or more processors to: sending a paging communication to a user equipment (UE) when the UE is in an inactive mode or an idle mode, the paging communication comprising a mobile terminated early data transmission (MT-EDT) indication and a resumption identifier of the UE, wherein the MT-EDT indication is an indication that MT downlink data is stored at a second network entity, and wherein the resumption identifier is a UE identifier assigned to the UE by the second network entity for the purpose of storing and reactivating a UE context associated with the UE; receiving a first communication from the UE as part of a random access channel (RACH) procedure based at least in part on sending the paging communication, the first communication including the recovery identifier; Based at least in part on sending the first communication, sending a second communication to the UE, the second communication comprising: Mobile terminated downlink data, uplink resources, which the UE is to use to send mobile station initiated uplink data when in the inactive mode or the idle mode, and a radio resource control (RRC) release message, which enables the UE to receive downlink data terminated by the mobile station when in the inactive mode or the idle mode; as well as receiving mobile station originated uplink data from said UE and in said uplink resources, The UE, when in the inactive mode or the idle mode, is to send uplink data initiated by the mobile station.

18. An apparatus for wireless communication, comprising: means for receiving, while the apparatus is in an inactive mode or an idle mode, a paging communication from a first network entity, the paging communication comprising a mobile terminated early data transfer (MT-EDT) indication and a resumption identifier of the UE, wherein the MT-EDT indication is an indication that MT downlink data is stored at a second network entity, and wherein the resumption identifier is a UE identifier assigned to the UE by the second network entity for the purpose of storing and reactivating a UE context associated with the UE; means for sending a first communication to the first network entity as part of a random access channel (RACH) procedure based at least in part on receiving the paging communication, the first communication including the recovery identifier; means for receiving, from the first network entity, a second communication based at least in part on sending the first communication, the second communication comprising: Mobile terminated downlink data, an indication of uplink resources, and a radio resource control (RRC) release message, wherein the radio resource control (RRC) release message causes the apparatus to remain in the inactive mode or the idle mode when receiving downlink data terminated by the mobile station; and When in the inactive mode or the idle mode, the uplink resources are used to send uplink data originated by a mobile station to the first network entity.

19. An apparatus for wireless communication, comprising: means for sending a paging communication to a user equipment (UE) when the UE is in an inactive mode or an idle mode, the paging communication comprising a mobile terminated early data transfer (MT-EDT) indication and a resumption identifier of the UE, wherein the MT-EDT indication is an indication that MT downlink data is stored at a second network entity, and wherein the resumption identifier is a UE identifier assigned to the UE by the second network entity for the purpose of storing and reactivating a UE context associated with the UE; means for receiving a first communication from the UE as part of a random access channel (RACH) procedure based at least in part on sending the paging communication, the first communication including the recovery identifier; means for sending a second communication to the UE based at least in part on sending the first communication, the second communication comprising: Mobile terminated downlink data, uplink resources, which the UE is to use to send mobile station initiated uplink data when in the inactive mode or the idle mode, and a radio resource control (RRC) release message, which enables the UE to receive downlink data terminated by the mobile station when in the inactive mode or the idle mode; as well as means for receiving mobile-originated uplink data from said UE and in said uplink resources, The UE, when in the inactive mode or the idle mode, is to send uplink data initiated by the mobile station.

Images