New small data transmission instructions

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may detect that SDT type data for a non-small data transmission (SDT) data radio bearer (DRB) has entered a buffer of the UE while the UE is in a radio resource control (RRC) inactive state or an RRC idle state. The UE may transmit a message indicating data in the buffer for the non-SDT DRB. The message may be associated with a UE ID. Numerous other aspects are described.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to PCT Patent Application No. PCT / CN2021 / 081733, filed March 19, 2021, entitled "NEW SMALL DATA TRANSMISSION INDICATION," which is expressly incorporated herein by reference.

[0002] Aspects of the present disclosure relate generally to wireless communications, and more particularly to techniques and apparatus for indicating novel small data transmissions. [Background technology]

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting 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 set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP).

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

[0005]

[0005] The above multiple access technologies have been adopted in various telecommunications standards to provide common protocols that enable different user equipment to communicate on a city, national, regional, or even global scale. NR, sometimes referred to as 5G, is a set of extensions to the LTE mobile standard promulgated by 3GPP. NR is designed to improve spectral efficiency, lower costs, improve service, utilize new spectrum, and better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), better integrating with other open standards, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As demand for mobile broadband access continues to grow, further developments in LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0006] In some aspects, a method of wireless communication implemented by a user equipment (UE) includes detecting, while in a radio resource control (RRC) inactive state or an RRC idle state, that data of an SDT type for a non-SDT data radio bearer (DRB) has entered a buffer of the UE. The method may include transmitting a message indicating the data in the buffer for the non-SDT DRB. The message may be associated with a UE identifier (ID) such that the message is a dedicated message.

[0007] In some aspects, a method of wireless communication implemented by a UE includes detecting, while in an RRC inactive state or an RRC idle state, that new data of an SDT type has entered a buffer of the UE during an SDT subsequent data transmission period. The method may include transmitting, during the SDT subsequent data transmission period, a message indicating the new data in the buffer. The message may be associated with a UE ID.

[0008] In some aspects, a method of wireless communication performed by a network entity includes receiving, from a UE during an SDT subsequent data transmission period, a message indicating that new data of an SDT type has entered a buffer of the UE, and receiving the new data, wherein the message can be associated with a UE ID.

[0009] In some aspects, a UE for wireless communication includes a memory and one or more processors coupled to the memory, the memory including instructions executable by the one or more processors to cause the UE, while in an RRC inactive state or an RRC idle state, to detect that SDT type data for a non-SDT DRB has entered a buffer of the UE and to transmit a message indicating the data in the buffer for the non-SDT DRB.

[0010]

[0010] In some aspects, a UE for wireless communication includes a memory and one or more processors coupled to the memory, wherein the memory includes instructions executable by the one or more processors to cause the UE, while in an RRC inactive state or an RRC idle state, to detect that new data of an SDT type has entered a buffer of the UE during an SDT subsequent data transmission period, and to transmit a message indicating the new data in the buffer during the SDT subsequent data transmission period.

[0011]

[0011] In some aspects, a network entity for wireless communication includes a memory and one or more processors coupled to the memory, the memory including instructions executable by the one or more processors to cause the network entity to receive a message from a UE during an SDT subsequent data transmission period indicating that new data of an SDT type has entered the UE's buffer, and to receive the new data.

[0012] In some aspects, a non-transitory computer-readable medium stores a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a UE, cause the UE to detect that SDT type data for a non-SDT DRB has entered a buffer of the UE while in an RRC inactive state or an RRC idle state, and to transmit a message indicating the data in the buffer for the non-SDT DRB.

[0013]

[0013] In some aspects, a non-transitory computer-readable medium stores a set of instructions for wireless communications, the set of instructions including one or more instructions that, when executed by one or more processors of a UE, cause the UE to detect that new data of an SDT type has entered a buffer of the UE during an SDT subsequent data transmission period while in an RRC inactive state or an RRC idle state, and to transmit a message indicating the new data in the buffer during the SDT subsequent data transmission period.

[0014]

[0014] In some aspects, a non-transitory computer-readable medium stores a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a network entity, cause the network entity to receive a message from a UE during an SDT subsequent data transmission period indicating that new data of an SDT type has entered the UE's buffer, and to receive the new data.

[0015]

[0015] In some aspects, an apparatus for wireless communication includes means for detecting that SDT type data for a non-SDT DRB has entered a buffer of a UE while in an RRC inactive state or an RRC idle state, and means for transmitting a message indicating the data in the buffer for the non-SDT DRB.

[0016]

[0016] In some aspects, an apparatus for wireless communication includes means for detecting that new data of an SDT type has entered a buffer of a UE during an SDT subsequent data transmission period while in an RRC inactive state or an RRC idle state, and means for transmitting a message indicating the new data in the buffer during the SDT subsequent data transmission period.

[0017]

[0017] In some aspects, an apparatus for wireless communication includes means for receiving a message from a UE during an SDT subsequent data transmission period indicating that new data of an SDT type has entered a buffer of the UE, and means for receiving the new data.

[0018]

[0018] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, wireless communication devices, and / or processing systems substantially as described in this specification with reference to and as indicated by the drawings and specification.

[0019]

[0019] The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure so that the following detailed description may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out 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, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for the purpose of illustration and description, and not as a definition of the limits of the claims.

[0020] Although aspects are described in this disclosure by way of illustration in some examples, those skilled in the art will understand that such aspects can be implemented in many different configurations and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects may be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communications devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, or artificial intelligence-enabled devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, transmitting and receiving wireless signals may include several components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders, or summers). It is contemplated that the aspects described herein may be practiced in a wide variety of devices, components, systems, distributed configurations, or end-user devices of varying sizes, shapes, and configurations.

[0021]

[0021] In order that the above-described features of the present disclosure may be understood in detail, a more specific description briefly summarized above may be obtained by referring to embodiments, some of which are shown in the accompanying drawings. However, since the description may lead to other equally effective embodiments, it should be noted that the accompanying drawings show only some typical embodiments of the present disclosure and therefore should not be considered as limiting the scope of the present disclosure. The same reference numbers in different drawings may identify the same or similar elements. [Brief explanation of the drawings]

[0022] [Figure 1]

[0022] FIG. 1 illustrates an example of a wireless network according to the present disclosure. [Figure 2]

[0023] 1 illustrates an example of a base station in communication with a UE in a wireless network according to the present disclosure. [Figure 3]

[0024] FIG. 1 illustrates an example of a wireless network in which a UE may support additional communication modes, according to the present disclosure. [Figure 4]

[0025] FIG. 10 illustrates an example of indicating new data in a non-empty buffer according to the present disclosure. [Figure 5]

[0026] FIG. 10 illustrates an example of indicating new data for an uplink configured grant (UL-CG) according to the present disclosure. [Figure 6]

[0027] FIG. 10 illustrates an example of indicating new data for a non-small data transmission (SDT) data radio bearer (DRB) according to the present disclosure. [Figure 7]

[0028] FIG. 10 illustrates an example of transmitting new data of SDT type in a first uplink message according to the present disclosure. [Figure 8]

[0029] 1 illustrates an example process performed, for example, by a UE, in accordance with the present disclosure. [Figure 9]

[0030] 1 illustrates an example process performed, for example, by a UE, in accordance with the present disclosure. [Figure 10]

[0031] 1 illustrates an example process performed, for example, by a network entity, in accordance with the present disclosure. [Figure 11]

[0032] 1 is a block diagram of an exemplary apparatus for wireless communication according to the present disclosure. [Figure 12] 1 is a block diagram of an exemplary apparatus for wireless communication according to the present disclosure. [Figure 13]1 is a block diagram of an exemplary apparatus for wireless communication according to the present disclosure. [Figure 14]

[0033] 1 illustrates an example of a disaggregated base station according to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0023]

[0034] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of the present disclosure covers any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with other aspects of the present disclosure. For example, a device may be implemented or a method may be practiced using any number of aspects described herein. Furthermore, the scope of the present disclosure is intended to cover such devices or methods practiced using other structure, functions, or structure and functions in addition to or other than the various aspects of the present disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0024]

[0035] Several aspects of telecommunications systems are presented next with reference to various apparatus and techniques. These apparatus and techniques are described in the detailed description that follows 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 such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0025]

[0036] It should be noted that although aspects may be described herein using terminology commonly associated with 5G or NR radio access technologies (RATs), aspects of the present disclosure may apply to other RATs, such as 3G RATs, 4G RATs, and / or RATs subsequent to 5G (e.g., 6G).

[0026]

[0037] FIG. 1 illustrates an example wireless network 100 according to the present disclosure. Wireless network 100 may be or include a component of a 5G (NR) network, an LTE network, etc. Wireless network 100 may include several base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, transmit reception point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to the coverage area of ​​a BS and / or the BS subsystem serving this coverage area, depending on the context in which the term is used.

[0027]

[0038] 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., a few kilometers in radius) and may allow unrestricted access by UEs with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs that have an association with the femto cell (e.g., a UE 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 the example shown in FIG. 1, 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. A BS may support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” may be used interchangeably herein.

[0028]

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

[0029]

[0040] In some aspects, the term “base station” (e.g., base station 110) or “network entity” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a “base station” or a “network entity” may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC, or a combination thereof. In some aspects, the term “base station” or “network entity” may refer to one device configured to perform one or more functions, such as those described herein with respect to base station 110. In some aspects, the term “base station” or “network entity” may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, several different devices (which may be located at the same geographic location or different geographic locations) may each be configured to perform at least a portion of the functions or duplicate the performance of at least a portion of the functions, and the term "base station" or "network entity" may refer to any one or more of those different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions and not another. In this manner, a single device may include two or more base stations.

[0030]

[0041] Wireless network 100 may also include relay stations. A relay station is an entity that can receive a data transmission from an upstream station (e.g., a BS or a UE) and send the data transmission 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. In the example shown in FIG. 1, relay BS 110d may communicate with macro BS 110a and UE 120d to enable communication between BS 110a and UE 120d. A relay BS may also be referred to as a relay station, a relay base station, a relay, etc.

[0031]

[0042] Wireless network 100 may be a heterogeneous network including different types of BSs, e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5-40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1-2 watts).

[0032]

[0043] A network controller 130 may couple to a set of BSs and 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 via wireless or wireline backhaul.

[0033]

[0044] The UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), 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 biometric sensor / 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 satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate over a wireless or wired medium.

[0034]

[0045] Some UEs may be considered machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and eMTC UEs include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, a location tag, etc. that may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices and / or implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). The UE 120 may be included in a housing that stores components of the UE 120, such as a processor component, a memory component, etc. In some aspects, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0035]

[0046] Generally, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. A frequency may also be referred to as a carrier, frequency channel, etc. Each frequency may 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 may be deployed.

[0036]

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

[0037]

[0048] The devices of wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various classes, bands, channels, etc. based on frequency or wavelength. For example, the devices of wireless network 100 may communicate using an operating band having a first frequency range (FR1), which may range from 410 MHz to 7.125 GHz, and / or may communicate using an operating band having a second frequency range (FR2), which may range from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the “sub-6 GHz” band. Similarly, FR2 is often referred to as “millimeter wave” even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz), which is identified as the “millimeter wave” band by the International Telecommunications Union (ITU). Thus, unless otherwise specified, it should be understood that terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies below 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specified, it should be understood that terms such as "millimeter wave," as used herein, may broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). The frequencies included within FR1 and FR2 may be modified, and it is contemplated that the techniques described herein are applicable to those modified frequency ranges.

[0038]

[0049] As noted above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0039]

[0050] 2 is a diagram illustrating an example base station 110 200 communicating with a UE 120 in a wireless network 100 in accordance with the present disclosure. The base station 110 may be equipped with T antennas 234a through 234t, and the UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0040]

[0051] At base station 110, transmit processor 220 may receive data from data source 212 for one or more UEs, select one or more modulation and coding schemes (MCSs) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(es) selected for that UE, and provide data symbols for all UEs. 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. Transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), etc.) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0041]

[0052] At the UE 120, antennas 252a through 252r may receive downlink signals from the base station 110 and / or other base stations and may provide received signals to demodulators (DEMODs) 254a through 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. A MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols and provide decoded data for the UE 120 to a data sink 260 and may provide decoded control and system information to a controller / processor 280. The term “controller / processor” may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP), a received signal strength indicator (RSSI), a reference signal received quality (RSRQ), a CQI, etc. In some aspects, one or more components of the UE 120 may be included in a housing 284.

[0042]

[0053] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0043]

[0054] 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 precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a-254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna(s) 252, the modulator and / or demodulator 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to implement aspects of any of the methods described herein (e.g., as described with reference to Figures 3-13).

[0044]

[0055] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by a demodulator 232, detected by a MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the 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 base station 110 may include a scheduler 246 to schedule the UE 120 for downlink and / or uplink communication. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, a modulator and / or demodulator 232, a MIMO detector 236, a receive processor 238, a transmit processor 220, and / or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., a controller / processor 240) and a memory 242 to implement aspects of any of the methods described herein (e.g., as described with reference to FIGS. 3-13).

[0045]

[0056] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component(s) of FIG. 2 may implement one or more techniques associated with indicating new small data transmission (SDT), 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 any other component(s) of FIG. 2 may perform or direct the operation of, for example, process 800 of FIG. 8, process 900 of FIG. 9, process 1000 of FIG. 10, and / or other processes described herein. The memories 242 and 282 may store data and program codes for the base station 110 and the UE 120, respectively. In some aspects, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code, program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of the base station 110 and / or the UE 120 (e.g., directly or after compilation, translation, interpretation), may cause the one or more processors, the UE 120, and / or the base station 110 to perform or direct operations of, for example, process 800 of FIG. 8, process 900 of FIG. 9, process 1000 of FIG. 10, and / or other processes described herein. In some aspects, executing the instructions may include running the instructions, translating the instructions, compiling the instructions, and / or interpreting the instructions.

[0046]

[0057] In some aspects, the UE 120 includes means for detecting that SDT type data for a non-SDT data radio bearer (DRB) has entered a buffer of the UE while in a radio resource control (RRC) inactive state or an RRC idle state, and / or means for transmitting a message indicating the data in the buffer for the non-SDT DRB. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the modulator 254, the controller / processor 280, or the memory 282.

[0047]

[0058] In some aspects, the UE 120 includes, while in an RRC inactive state or an RRC idle state, means for detecting that new data of an SDT type has entered the UE's buffer during an SDT subsequent data transmission period and / or means for transmitting a message indicating the new data in the buffer during an SDT subsequent data transmission period. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the modulator 254, the controller / processor 280, or the memory 282.

[0048]

[0059] In some aspects, a network entity (e.g., base station 110) includes means for receiving a message indicating that new data of the SDT type has entered the UE's buffer and / or means for receiving the new data from the UE during the SDT subsequent data transmission period. The means for base station 110 to perform the operations described herein may include, for example, one or more of transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0049]

[0060] 2 are shown as separate components, the functionality described above with respect to those blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, functionality described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0050]

[0061] As noted above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0051]

[0062] 3 is a diagram illustrating an example 300 of indicating new data after a four-step random access channel (RACH) procedure in accordance with the present disclosure. As shown in FIG. 3, a network entity (e.g., a base station 110) and a UE 120 may communicate with each other to perform the four-step RACH procedure.

[0052]

[0063] The UE 120 may perform a RACH procedure to establish an RRC connection with the base station 110. The RACH procedure may involve signaling in two steps (a two-step RACH procedure) or four steps (a four-step RACH procedure). As the first step of the four-step RACH procedure and as indicated by reference numeral 305, the UE 120 may transmit a RAM (sometimes referred to as a random access preamble, a physical RACH (PRACH) preamble, or a random access message (RAM) preamble), which may include a preamble. A message including a preamble may be referred to as message 1, msg1, MSG1, a first message, or an initial message in the four-step RACH procedure. The random access message may include a random access preamble identifier.

[0053]

[0064] The base station 110 may receive a RAM preamble transmitted by the UE 120. If the base station 110 successfully receives and decodes the RAM preamble, the base station 110 may then receive and decode a RAM payload. As indicated by reference numeral 310, the base station 110 may transmit a random access response (RAR) in response to the preamble. A message including the RAR may be referred to as message 2, msg2, MSG2, or the second message in a four-step random access procedure. In some aspects, the RAR may indicate a detected random access preamble identifier (e.g., received from the UE 120 in msg1). Additionally or alternatively, the RAR may indicate a resource allocation to be used by the UE 120 to transmit message 3 (msg3).

[0054]

[0065] In some aspects, as part of the second step of the four-step RACH procedure, base station 110 may transmit a physical downlink control channel (PDCCH) communication for the RAR. The PDCCH communication may schedule a physical downlink shared channel (PDSCH) communication that includes the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication. Also, as part of the second step of the four-step RACH procedure, base station 110 may transmit a PDSCH communication for the RAR as scheduled by the PDCCH communication.

[0055]

[0066] As indicated by reference numeral 315, the UE 120 may transmit an RRC connection request message. The RRC connection request message may be referred to as message 3, msg3, MSG3, or the third message of the four-step RACH procedure. In some aspects, the RRC connection request may include a UE identifier, uplink control information (UCI), and / or a physical uplink shared channel (PUSCH) communication (e.g., an RRC connection request). The UE 120 may transition between different modes based at least in part on various commands and / or communications received from the base station 110, and the UE 120 may transmit an RRC resume request (RRCResumeRequest) in msg3 to transition from an RRC inactive state to an RRC active state. The RRC resume request may also establish some security for messages from the UE 120 to the base station 110 by verifying the identity of the UE 120. The UE 120 may include data such as an SDT in msg3 with the RRC resume request.

[0056]

[0067] As indicated by reference numeral 320, base station 110 may transmit an RRC connection setup message. The RRC connection setup message may be referred to as message 4, msg4, MSG4, or the fourth message of a four-step RACH procedure. In some aspects, the RRC connection setup message may include a detected UE identifier, a timing advance value, and / or contention resolution information. In some aspects, if UE 120 performs a two-step RACH procedure, msg1 and msg3 may be combined into a single message called “msgA,” and msg2 and msg4 may be combined into a single message called “msgB.”

[0057]

[0068] After completing the four-step (or two-step) RACH procedure, the UE 120 may transmit and receive data. However, the UE 120 may enter an inactive state, such as an RRC inactive state, to conserve battery power and network resources during infrequent data traffic. An "inactive state" may refer to a UE operating in an inactive communication mode. To re-enter an active state, the UE 120 may perform another RACH procedure or another connection establishment procedure. In many applications, the UE 120 may generate only small amounts of data in bursts of data sessions. Examples of such applications include enhanced mobile broadband (eMBB) communications, IoT communications, instant messaging applications, social media applications, and / or wearable device applications. Re-establishing an RRC connection using the RACH procedure may consume significant resources of the UE 120 and the base station 110. Therefore, in some scenarios, re-establishing an RRC connection for small uplink data transfers may be inefficient. For example, the UE 120 and base station 110 may waste processing and signaling resources re-establishing an RRC connection simply to transmit a small data burst.

[0058]

[0069] Some RATs may provide a service for transmitting SDT in an inactive mode via an uplink RACH message or configured uplink resources (e.g., dedicated pre-configured uplink resources, pre-configured uplink resources, dedicated uplink resources), etc. However, not all small data sizes fit within an uplink RACH message or configured uplink resources. Therefore, as indicated by reference numeral 325, UE 120 may transmit SDT-type data (small data transmitted during an RRC inactive state or an RRC idle state) as part of an SDT subsequent data transmission period 330. SDT subsequent data transmission period 330 may follow a RACH procedure or a configuration for an uplink grant. During the SDT subsequent data transmission period, base station 110 may allow UE 120 to transmit SDT-type data during an RRC inactive state or an RRC idle state without requiring UE 120 to enter an RRC connected state or an RRC active state. UE 120 may transmit SDT type data from a buffer holding SDT type data during an SDT subsequent data transmission period. UE 120 may transmit data until the buffer is empty.

[0059]

[0070] If new data enters its buffer during the SDT subsequent data transmission period 330, the base station 110 may be unaware of the new data if the new data arrives in the buffer after the UE 120 transmits a buffer status report (BSR) and before the UE 120 receives an RRC response message from the base station 110. To transmit the new data, the UE 120 may require the base station 110 to provide an uplink grant or scheduled resources. In either case, the behavior for the UE 120 is not defined as to when new data arrives in the buffer during the SDT subsequent data transmission period. Without such a definition, the UE 120 and the base station 110 may waste processing and signaling resources determining how to handle new data in the buffer during the SDT subsequent data transmission period. In some scenarios, new data may arrive in the buffer for non-SDT DRBs that are not configured to resume data transmission during the SDT subsequent data transmission period. There is no defined signaling as to when new data arrives in the buffer for non-SDT DRBs. As a result, there may be latency that causes the UE 120 and base station 110 to consume time and other processing and signaling resources.

[0060]

[0071] According to various aspects described herein, UE 120 may detect that new data of SDT type has arrived in the buffer, as indicated by reference numeral 335. UE 120 may then send an indication of the new data in the buffer to base station 110. The indication may include a buffer status in a medium access control element (MAC-CE) or an RRC message.

[0061]

[0072] If the buffer is empty when new data arrives, the UE 120 may initiate a second RACH procedure if there are no available uplink grants or other scheduled resources for transmitting new data of the SDT type. The UE 120 may be in an RRC inactive state or an RRC idle state. In some aspects, the second RACH procedure may involve less signaling or smaller messages than a full RACH procedure to obtain more uplink grants. As indicated by reference numeral 340, the UE 120 may transmit a random access preamble in the second RACH procedure. As indicated by reference numeral 345, the UE 120 may transmit a PUSCH payload or some other data, including new data of the SDT type, to the base station 110. The UE 120 may also transmit an indication of the new data in a BSR MAC-CE. The base station 110 may transmit an RAR as indicated by reference numeral 350, and the UE 120 may transmit new data of the SDT type as indicated by reference numeral 355. In some aspects, UE 120 may wait for a triggering condition (e.g., a minimum data in buffer threshold) to send the indication. The triggering condition may depend on the logical channel priority. If UE 120 meets the triggering condition for triggering the BSR MAC-CE, the second RACH procedure from reference numeral 340 to reference numeral 350 may not be performed. UE 120 may transmit new data of the SDT type after the BSR MAC-CE is triggered.

[0062]

[0073] The base station 110 may transmit an RRC release message, which may end the SDT subsequent data transmission period, as indicated by reference numeral 360. The base station 110 may include a suspend configuration that configured the UE 120 to suspend data transmission and / or suspend the RRC connection.

[0063]

[0074] If UE 120 has already sent an RRC resume request message in the first RACH procedure, UE 120 may not be able to send a second RRC resume request message. To maintain some type of security for the transmission of new data, UE 120 may send a UE identifier (ID) with the RACH message or with an indication of new data in the buffer in a message indicated by reference numeral 345. The UE ID may include a Cell Radio Network Temporary Identifier (C-RNTI) (e.g., the UE ID scrambled with the C-RNTI). Base station 110 may use the UE ID to identify UE 120 and its buffer status to verify new data of the SDT type from UE 120. Base station 110 may keep UE 120 in an RRC inactive state or an RRC idle state to transmit new data of the SDT type, or may configure UE 120 to transition to an RRC connected state or an RRC active state before transmitting new data. In some aspects, the message with the UE ID may be a dedicated control message. The UE 120 may transmit a dedicated control message in resources associated with the UE 120, which may be dedicated to the UE 120.

[0064]

[0075] As noted above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.

[0065]

[0076] 4 is a diagram illustrating an example 400 of indicating new data in a non-empty buffer according to the present disclosure. As shown in FIG. 4, a base station 110 and a UE 120 may communicate with each other.

[0066]

[0077] The base station 110 and the UE 120 may communicate with each other to perform a four-step RACH procedure. As indicated by reference numeral 405, the UE 120 may transmit msg1. As indicated by reference numeral 410, the base station 110 may transmit msg2. As indicated by reference numeral 415, the UE 120 may transmit msg3. As indicated by reference numeral 420, the base station 110 may transmit msg4. As indicated by reference numeral 425, the UE 120 may transmit an SDT as part of an SDT-following data transmission period 430.

[0067]

[0078] If the buffer is not empty when the new data enters the buffer, base station 110 may continue to schedule resources for the UE. If UE 120 detects that new data has arrived in the buffer when the buffer was not empty (if scheduled resources are available), as indicated by reference numeral 435, UE 120 may use the scheduled resources to transmit new data of SDT type. As indicated by reference numeral 440, UE 120 may send an indication of the new data without performing a second RACH procedure. The indication may be a BSR MAC-CE, a new MAC-CE, or a new RRC message. The new MAC-CE or RRC message may be able to indicate new data for either SDT DRBs or non-SDT DRBs, or for both SDT and non-SDT DRBs. Because the new MAC-CE or RRC message is not defined by an existing standard or format, the new MAC-CE or RRC message may be considered "new," and because the new MAC-CE or RRC message may apply to both SDT and non-SDT DRBs, the new MAC-CE or RRC message may be considered a "unified" message.

[0068]

[0079] UE 120 may use the scheduled resources to transmit new data as one or more SDTs, as indicated by reference numeral 445. The subsequent data transmission period 430 may end when UE 120 receives an RRC release message, as indicated by reference numeral 450.

[0069]

[0080] As noted above, Figure 4 is provided as an example. Other examples may differ from those described with respect to Figure 4.

[0070]

[0081] 5 is a diagram illustrating an example 500 of indicating new data for an uplink configured grant (UL-CG) according to the present disclosure. As shown in FIG. 5, a base station 110 and a UE 120 may communicate with each other.

[0071]

[0082] In some aspects, the UE 120 may be transmitting uplink data on pre-configured PUSCH resources. For example, the UE 120 may be reusing UL-CG type 1. As indicated by reference numeral 505, the UE 120 may transmit a first uplink message with scheduled resources as part of the UL-CG. The uplink message may include an RRC resumption request. As indicated by reference numeral 510, the base station 110 may transmit a response, such as an acknowledgement (ACK) or a negative acknowledgement (NACK). No RRC message may be included. As indicated by reference numeral 515, the UE 120 may transmit an SDT as part of an SDT subsequent data transmission period 520.

[0072]

[0083] As indicated by reference numeral 525, UE 120 may detect that there is new data of the SDT type in the buffer. As indicated by reference numeral 530, UE 120 may send an indication of the new data in a BSR MAC-CE, a new MAC-CE, or a new RRC message. As indicated by reference numeral 535, UE 120 may transmit the new data in the buffer with scheduled resources. As indicated by reference numeral 540, UE 120 may receive an RRC release message to end the SDT subsequent data transmission period 520.

[0073]

[0084] As noted above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.

[0074]

[0085] 6 is a diagram illustrating an example 600 of indicating new data for a non-SDT DRB according to the present disclosure. As shown in FIG. 6, a base station 110 and a UE 120 may communicate with each other.

[0075]

[0086] In some scenarios, new data may arrive in the buffer for an SDT DRB, which is a DRB configured to resume data transmission (with an RRC resume message) during the SDT subsequent data transmission period. However, if new data arrives for a non-SDT DRB that is not configured for SDT-type data and is not configured to resume data transmission during the SDT subsequent data transmission period, there is no current procedure for notifying base station 110 of the new data for that non-SDT DRB. Base station 110 may not have information about whether UE 120 is capable of transmitting SDT-type data for the non-SDT DRB.

[0076]

[0087] In some aspects, UE 120 may send an indication of new data of SDT type even for non-SDT DRBs. UE 120 may send the indication as a buffer status in the MAC-CE for SDT DRBs, and UE 120 may send the indication in a new MAC-CE message or a new RRC message that can indicate new data for either SDT or non-SDT DRBs. For example, the new MAC-CE may include a one-bit indication of whether there is new data for non-SDT DRBs. The new MAC-CE may also include the buffer status for SDT DRBs. The new MAC-CE may indicate a DRB ID or a logical channel group (LCG) ID.

[0077]

[0088] By indicating new SDT-type data in the buffer with a new MAC-CE (or a new RRC message) rather than using the existing BSR MAC-CE for SDT DRBs and a new MAC-CE for non-SDT DRBs, UE 120 may efficiently notify base station 110 of the new data in the buffer without using additional signaling resources for a separate MAC-CE. Because UE 120 may send an indication of new SDT-type data, including for non-SDT DRBs, to base station 110, UE 120 and base station 110 may conserve time, processing resources, and signaling resources that would otherwise be consumed by waiting for uplink resources, delaying transmission of new data, or performing a full RACH procedure that would not be necessary.

[0078]

[0089] Example 600 shows a portion of a RACH procedure involving a non-SDT DRB. As indicated by reference numeral 605, the UE 120 may transmit msg1. As indicated by reference numeral 610, the base station 110 may transmit msg2. As indicated by reference numeral 615, the UE 120 may transmit msg3. As indicated by reference numeral 620, the base station 110 may transmit msg4. As indicated by reference numeral 625, the UE 120 may transmit SDT type data during an SDT subsequent data transmission period 630.

[0079]

[0090] As indicated by reference numeral 635, the UE 120 may detect that new data has arrived in the buffer for the non-SDT DRB. As indicated by reference numeral 640, the UE 120 may transmit a new MAC-CE or a new RRC message, which may indicate the new data for the non-SDT DRB (and the new data for the SDT DRB). The new MAC-CE or new RRC message may indicate the buffer status. The RRC message may include a resume cause. If the non-SDT DRB has new data, it may be inefficient to keep the UE 120 in an RRC inactive state. The base station 110 may determine to transition the UE 120 to an RRC connected state. As indicated by reference numeral 645, the base station 110 may transmit an RRC resume message. In some aspects, the UE 120 may wait for a trigger condition (e.g., a minimum buffered data threshold) to send the indication. The trigger condition may depend on the logical channel priority. If UE 120 meets the triggering conditions for triggering a BSR MAC-CE, the BSR MAC-CE may include both buffer status information for SDT DRBs as well as buffer status information for non-SDT DRBs. After UE 120 transmits the BSR MAC-CE to base station 110, base station 110 may decide to transition UE 120 to the RRC connected state.

[0080]

[0091] As noted above, Figure 6 is provided as an example. Other examples may differ from those described with respect to Figure 6.

[0081]

[0092] 7 is a diagram illustrating an example 700 of transmitting new data of an SDT type in a first uplink message in accordance with the present disclosure. As shown in FIG. 7, a base station 110 and a UE 120 may communicate with each other.

[0082]

[0093] In the first RACH procedure, the first uplink message in msg3 may include new data of the SDT type that has arrived in the buffer. As indicated by reference numeral 705, UE 120 transmits msg1. As indicated by reference numeral 710, base station 110 transmits msg2. As indicated by reference numeral 715, UE 120 may detect that new data of the SDT type has arrived in the buffer. The new data may be for a non-SDT DRB. As indicated by reference numeral 720, UE 120 may transmit the new data of the SDT type as the first uplink message in msg3. msg3 may include an indication that there is new data of the SDT type in the buffer (BSR MAC-CE, new MAC-CE, or RRC message). UE 120 may also transmit an RRC resume request message to base station 110. As indicated by reference numeral 725, base station 110 may transmit msg4, including the RRC resume message. As indicated by reference numeral 730, UE 120 may transition to the RRC Connected state after the first uplink data transmission of data that is of the SDT type. By transmitting new data of the SDT type in an early RACH message, UE 120 and base station 110 may reduce latency. After UE 120 transitions to the RRC Connected state, UE 120 may transmit new data stored for non-SDT DRBs.

[0083]

[0094] As noted above, Figure 7 is provided as an example. Other examples may differ from those described with respect to Figure 7.

[0084]

[0095] 8 illustrates an example process 800, performed by, for example, a UE, in accordance with the present disclosure. The example process 800 is an example in which a UE (e.g., UE 120) performs operations associated with indicating a new SDT.

[0085]

[0096] 8, in some aspects, process 800 may include detecting that SDT-type data for non-SDT DRBs has entered a buffer of the UE while in an RRC inactive state or an RRC idle state (block 810). For example, the UE may detect (e.g., using detection component 1108 shown in FIG. 11) that SDT-type data for non-SDT DRBs has entered a buffer of the UE while in an RRC inactive state or an RRC idle state, as described above.

[0086]

[0097] 8, in some aspects, process 800 may include transmitting a message indicating data in a buffer for the non-SDT DRB (block 820). For example, the UE may transmit (e.g., using the transmitting component 1104 shown in FIG. 11) a message indicating data in a buffer for the non-SDT DRB, as described above. In some aspects, the message may be associated with a UE ID.

[0087]

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

[0088]

[0099] In a first aspect, the message is configured to indicate one or more of SDT type data for a non-SDT DRB or SDT type data for an SDT DRB.

[0089]

[0100] In a second aspect, alone or in combination with the first aspect, transmitting the message includes transmitting a BSR in a MAC-CE or RRC message. In some aspects, the RRC message includes the resume cause.

[0090]

[0101] In a third aspect, alone or in combination with one or more of the first and second aspects, sending the message includes sending the message if a trigger condition is met.

[0091]

[0102] In a fourth aspect, alone or in combination with one or more of the first through third aspects, transmitting the message includes transmitting the message during an SDT subsequent data transmission period occurring following the first RACH procedure.

[0092]

[0103] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the process 800 includes transmitting a RACH preamble to initiate a second RACH procedure during the SDT subsequent data transmission period before transmitting the message and if there is no available uplink grant.

[0093]

[0104] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the message includes at least a UE ID, and the second RACH procedure is performed without sending an RRC resume request message.

[0094]

[0105] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, transmitting the message includes transmitting the message in a scheduled resource if the scheduled resource is available for use.

[0095]

[0106] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, transmitting the message includes transmitting the message during a configured grant SDT subsequent data transmission period.

[0096]

[0107] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the process 800 includes transmitting data after transitioning to an RRC connected state.

[0097]

[0108] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the process 800 includes transmitting data in an RRC inactive state or an RRC idle state.

[0098]

[0109] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, transmitting the message includes transmitting the message in a first uplink transmission with data of an SDT type in coordination with an RRC resumption request.

[0099]

[0110] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the process 800 includes indicating that the data is of an SDT type for a non-SDT DRB, for an SDT DRB, or for both an SDT DRB and a non-SDT DRB.

[0100]

[0111] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the message includes a radio bearer ID.

[0101]

[0112] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the message indicates a type of radio bearer.

[0102]

[0113] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the message includes an LCG ID.

[0103]

[0114] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, transmitting the message includes transmitting the message in resources associated with the UE ID.

[0104]

[0115] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the UE ID includes a C-RNTI.

[0105]

[0116] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, transmitting the message includes transmitting the message during an SDT subsequent data transmission period occurring following the first RACH procedure.

[0106]

[0117] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, transmitting a RACH preamble to initiate a second RACH procedure during an SDT subsequent data transmission period before transmitting the message and if no uplink grant is available.

[0107]

[0118] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the second RACH procedure is performed without transmitting an RRC resume request message.

[0108]

[0119] 8 illustrates example blocks of process 800, in some aspects process 800 may include additional, fewer, different, or differently configured blocks than those shown in FIG 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0109]

[0120] 9 illustrates an example process 900, performed by, for example, a UE, in accordance with the present disclosure. The example process 900 is an example in which a UE (e.g., UE 120) performs operations associated with indicating a new SDT.

[0110]

[0121] 9, in some aspects, process 900 may include detecting that new data of an SDT type has entered a buffer of the UE during an SDT subsequent data transmission period while in an RRC inactive state or an RRC idle state (block 910). For example, the UE may detect (e.g., using detection component 1208 shown in FIG. 12) that new data of an SDT type has entered a buffer of the UE during an SDT subsequent data transmission period while in an RRC inactive state or an RRC idle state, as described above.

[0111]

[0122] 9, in some aspects, the process 900 may include transmitting a message indicating new data in the buffer during the SDT subsequent data transmission period (block 920). For example, the UE may transmit (e.g., using the transmitting component 1204 shown in FIG. 12) a message indicating new data in the buffer during the SDT subsequent data transmission period, as described above. In some aspects, the message may be associated with a UE ID.

[0112]

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

[0113]

[0124] In a first aspect, the SDT subsequent data transmission period occurs after the first RACH procedure, and the process 900 includes transmitting a RACH preamble to initiate a second RACH procedure during the SDT subsequent data transmission period before transmitting the message and if no uplink grant is available.

[0114]

[0125] In a second aspect, alone or in combination with the first aspect, the message includes at least a UE ID, and the second RACH procedure is performed without sending an RRC resume request message.

[0115]

[0126] In a third aspect, alone or in combination with one or more of the first and second aspects, transmitting the message includes transmitting the message in a scheduled resource if the scheduled resource is available for use.

[0116]

[0127] In a fourth aspect, alone or in combination with one or more of the first through third aspects, transmitting the message includes transmitting the message during a configured allowed SDT subsequent data transmission period.

[0117]

[0128] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, transmitting the message includes transmitting a BSR in a MAC-CE or RRC message. In some aspects, the RRC message includes the resume cause.

[0118]

[0129] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the new data is for SDT DRB.

[0119]

[0130] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the new data is for a non-SDT DRB.

[0120]

[0131] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the message is configured to indicate one or more of SDT type data for a non-SDT DRB, or SDT type data for an SDT DRB.

[0121]

[0132] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the UE ID includes a C-RNTI.

[0122]

[0133] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, an SDT subsequent data transmission period occurs after a first RACH procedure, and the process 900 includes transmitting a RACH preamble to initiate a second RACH procedure during the SDT subsequent data transmission period before transmitting the message and if no uplink grant is available.

[0123]

[0134] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the second RACH procedure is performed without transmitting an RRC resume request message.

[0124]

[0135] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, transmitting the message includes transmitting the message during a configured allowed SDT subsequent data transmission period.

[0125]

[0136] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the message includes a radio bearer ID or indicates a type of radio bearer.

[0126]

[0137] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the message includes an LCG ID.

[0127]

[0138] 9 illustrates example blocks of process 900, in some aspects process 900 may include additional, fewer, different, or differently configured blocks than those shown in FIG 9. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0128]

[0139] 10 illustrates an example process 1000, performed by, for example, a network entity, in accordance with the present disclosure. The example process 1000 is an example in which a network entity (e.g., base station 110) performs operations associated with indicating a new SDT.

[0129]

[0140] 10, in some aspects, process 1000 may include receiving a message from the UE during an SDT subsequent data transmission period indicating that new data of the SDT type has entered a buffer of the UE (block 1010). For example, the network entity (e.g., using the receiving component 1302 shown in FIG. 13) may receive a message from the UE during an SDT subsequent data transmission period indicating that new data of the SDT type has entered a buffer of the UE, as described above. In some aspects, the message may be associated with a UE ID.

[0130]

[0141] 10, in some aspects, the process 1000 may include receiving the new data (block 1020). For example, the network entity (e.g., using the receiving component 1302 shown in FIG. 13) may receive the new data as described above.

[0131]

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

[0132]

[0143] In a first aspect, the message is configured to indicate one or more of SDT type data for a non-SDT DRB or SDT type data for an SDT DRB.

[0133]

[0144] In a second aspect, alone or in combination with the first aspect, an SDT subsequent data transmission period occurs following a first RACH procedure, and process 1000 includes receiving a preamble to initiate a second RACH procedure during the SDT subsequent data transmission period, and transmitting an RAR, where the message includes at least a UE identifier corresponding to the UE.

[0134]

[0145] In a third aspect, alone or in combination with one or more of the first and second aspects, the process 1000 includes transmitting a scheduled resource for a message and receiving the message in the scheduled resource.

[0135]

[0146] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the message is received in a MAC-CE or RRC message.

[0136]

[0147] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the message comprises a BSR.

[0137]

[0148] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the message indicates that the new data is for a non-SDT DRB.

[0138]

[0149] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the process 1000 includes configuring the UE to transmit new data after transitioning to an RRC connected state.

[0139]

[0150] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the process 1000 includes configuring the UE to transmit new data in an RRC inactive state or an RRC idle state.

[0140]

[0151] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the UE ID includes a C-RNTI.

[0141]

[0152] 10 illustrates example blocks of process 1000, in some aspects process 1000 may include additional, fewer, different, or differently configured blocks than those shown in FIG 10. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0142]

[0153] 11 is a block diagram of an example apparatus 1100 for wireless communication. The apparatus 1100 may be a UE, or the UE may include the apparatus 1100. In some aspects, the apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, a network entity, or another wireless communication device) using the receiving component 1102 and the transmitting component 1104. As further shown, the apparatus 1100 may include a detecting component 1108, among other examples.

[0143]

[0154] In some aspects, apparatus 1100 may be configured to perform one or more operations described herein with respect to FIGS. 1-7. Additionally or alternatively, apparatus 1100 may be configured to perform one or more processes described herein, such as process 800 of FIG. 8. In some aspects, apparatus 1100 and / or one or more components illustrated in FIG. 11 may include one or more components of a UE described above with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 11 may be implemented within one or more components described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored on a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0144]

[0155] The receiving component 1102 may receive communications such as reference signals, control information, data communications, or a combination thereof from the device 1106. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a UE as described above with respect to FIG.

[0145]

[0156] The transmitting component 1104 may transmit a communication such as a reference signal, control information, a data communication, or a combination thereof to the device 1106. In some aspects, one or more other components of the device 1100 may generate a communication and provide the generated communication to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing on the generated communication (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) and transmit the processed signal to the device 1106. In some aspects, the transmitting component 1104 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of a UE described above with respect to FIG. 2. In some aspects, the transmitting component 1104 may be co-located with the receiving component 1102 in a transceiver.

[0146]

[0157] The detection component 1108 may detect that SDT type data for non-SDT DRBs has entered the UE's buffer while in the RRC inactive state or the RRC idle state. The transmitting component 1104 may transmit a message indicating the data in the buffer for the non-SDT DRB. The transmitting component 1104 may transmit the data after transitioning to the RRC connected state. The transmitting component 1104 may transmit the data in the RRC inactive state or the RRC idle state.

[0147]

[0158] The number and arrangement of components shown in Figure 11 are provided as an example. In practice, there may be additional, fewer, different, or differently arranged components than those shown in Figure 11. Furthermore, two or more components shown in Figure 11 may be implemented within a single component, or a single component shown in Figure 11 may be implemented as multiple distributed components. Additionally or alternatively, a set of components shown in Figure 11 may perform one or more functions that are described as being performed by another set of components shown in Figure 11.

[0148]

[0159] 12 is a block diagram of an example apparatus 1200 for wireless communication. The apparatus 1200 may be a UE, or the UE may include the apparatus 1200. In some aspects, the apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, a network entity, or another wireless communication device) using the receiving component 1202 and the transmitting component 1204. As further shown, the apparatus 1200 may include a detecting component 1208, among other examples.

[0149]

[0160] In some aspects, apparatus 1200 may be configured to perform one or more operations described herein with respect to FIGS. 1-7. Additionally or alternatively, apparatus 1200 may be configured to perform one or more processes described herein, such as process 900 of FIG. 9. In some aspects, apparatus 1200 and / or one or more components illustrated in FIG. 12 may include one or more components of a UE described above with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 12 may be implemented within one or more components described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored on a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0150]

[0161] Receiving component 1202 may receive communications such as reference signals, control information, data communications, or a combination thereof from apparatus 1206. Receiving component 1202 may provide the received communications to one or more other components of apparatus 1200. In some aspects, receiving component 1202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of apparatus 1200. In some aspects, receiving component 1202 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a UE described above with respect to FIG.

[0151]

[0162] The transmitting component 1204 may transmit a communication to the device 1206, such as a reference signal, control information, a data communication, or a combination thereof. In some aspects, one or more other components of the device 1200 may generate a communication and provide the generated communication to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing on the generated communication (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) and transmit the processed signal to the device 1206. In some aspects, the transmitting component 1204 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of a UE, as described above with respect to FIG. 2. In some aspects, the transmitting component 1204 may be co-located with the receiving component 1202 in a transceiver.

[0152]

[0163] The detecting component 1208 may detect that new data of the SDT type has entered the buffer of the UE during an SDT subsequent data transmission period while in an RRC inactive state or an RRC idle state. The transmitting component 1204 may transmit a message indicating the new data in the buffer during the SDT subsequent data transmission period.

[0153]

[0164] The number and arrangement of components shown in Figure 12 are provided as an example. In practice, there may be additional, fewer, different, or differently arranged components than those shown in Figure 12. Furthermore, two or more components shown in Figure 12 may be implemented within a single component, or a single component shown in Figure 12 may be implemented as multiple distributed components. Additionally or alternatively, a set of components shown in Figure 12 may perform one or more functions that are described as being performed by another set of components shown in Figure 12.

[0154]

[0165] 13 is a block diagram of an example apparatus 1300 for wireless communication. The apparatus 1300 may be a network entity, or the network entity may include the apparatus 1300. In some aspects, the apparatus 1300 includes a receiving component 1302 and a transmitting component 1304, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, a network entity, or another wireless communication device) using the receiving component 1302 and the transmitting component 1304. As further shown, the apparatus 1300 may include a configuration component 1308, among other examples.

[0155]

[0166] In some aspects, apparatus 1300 may be configured to perform one or more operations described herein with respect to FIGS. 1-7. Additionally or alternatively, apparatus 1300 may be configured to perform one or more processes described herein, such as process 1000 of FIG. 10. In some aspects, apparatus 1300 and / or one or more components illustrated in FIG. 13 may include one or more components of the base station described above with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 13 may be implemented within one or more components described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored on a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0156]

[0167] The receiving component 1302 may receive communications such as reference signals, control information, data communications, or a combination thereof from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of the base station described above with respect to FIG.

[0157]

[0168] The transmitting component 1304 may transmit a communication to the device 1306, such as a reference signal, control information, a data communication, or a combination thereof. In some aspects, one or more other components of the device 1300 may generate a communication and provide the generated communication to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing on the generated communication (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) and transmit the processed signal to the device 1306. In some aspects, the transmitting component 1304 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the base station described above with respect to FIG. 2. In some aspects, the transmitting component 1304 may be co-located with the receiving component 1302 in a transceiver.

[0158]

[0169] The receiving component 1302 may receive a message from the UE during the SDT subsequent data transmission period indicating that new data of the SDT type has entered the buffer of the UE. The receiving component 1302 may receive the new data.

[0159]

[0170] The transmitting component 1304 may transmit the scheduled resource for the message. The receiving component 1302 may receive the message in the scheduled resource.

[0160]

[0171] The configuration component 1308 may configure the UE to transmit new data after transitioning to the radio resource control connected state. The configuration component 1308 may configure the UE to transmit new data in the RRC inactive state or the RRC idle state.

[0161]

[0172] The number and arrangement of components shown in Figure 13 are provided as an example. In practice, there may be additional, fewer, different, or differently arranged components than those shown in Figure 13. Furthermore, two or more components shown in Figure 13 may be implemented within a single component, or a single component shown in Figure 13 may be implemented as multiple distributed components. Additionally or alternatively, a set of components shown in Figure 13 may perform one or more functions that are described as being performed by another set of components shown in Figure 13.

[0162]

[0173] FIG. 14 is a diagram illustrating an example disaggregated base station 1400 in accordance with the present disclosure.

[0163]

[0174] A communication system deployment, such as a 5G NR system, can be configured in multiple ways with various components or components. In a 5G NR system, or network, a network node, network entity, network mobility element, Radio Access Network (RAN) node, core network node, network element, or network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality, can be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B, evolved NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell) can be implemented as an aggregated or disaggregated base station (network entity) (also known as a standalone BS or monolithic BS).

[0164]

[0175] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU or alternatively geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0165]

[0176] Base station type operation or network design may take into account the aggregation characteristics of base station functions. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN, such as the network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as Cloud Radio Access Network (C-RAN)). Disaggregation may include distributing functions across two or more units at various physical locations, as well as virtually distributing functions for at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station, or disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0166]

[0177] The disaggregated base station 1400 architecture may include one or more CUs 1410 that can communicate directly with the core network 1420 via a backhaul link or indirectly with the core network 1420 through one or more disaggregated base station units (such as a Near-RT RIC 1425 via an E2 link, or a Non-RT RIC 1415 associated with a service management and orchestration (SMO) framework 1405). The CUs 1410 may communicate with one or more DUs 1430 via respective midhaul links, such as an F1 interface. The DUs 1430 may communicate with one or more RUs 1440 via respective fronthaul links. The fronthaul, midhaul, and backhaul links may be commonly referred to as “communication links.” The RUs 1440 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some aspects, a UE 120 may be served by multiple RUs 1440 simultaneously. The DU 1430 and the RU 1440 may also be referred to as the "O-RAN DU (O-DU)" and "O-RAN RU (O-RU)," respectively. A network entity may include a CU, a DU, an RU, or any combination of a CU, a DU, and an RU. A network entity may include a disaggregated base station or one or more components of a disaggregated base station, such as a CU, a DU, an RU, or any combination of a CU, a DU, and an RU. A network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that provide a network interface for or may service a UE, a mobile station, a sensor / actuator, or other wireless device.

[0167]

[0178] Each of the units, i.e., CU 1410, DU 1430, RU 1440, and Near-RT RIC 1425, Non-RT RIC 1415, and SMO framework 1405, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, a unit may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive or transmit signals to one or more of the other units, or both, over a wireless transmission medium.

[0168]

[0179] In some aspects, the CU 1410 may host one or more upper layer control functions. Such control functions may include RRC, Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 1410. The CU 1410 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 1410 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface. The CU 1410 may be implemented to communicate with the DU 1430, as needed, for network control and signaling.

[0169]

[0180] The DU 1430 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 1440. In some aspects, the DU 1430 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending, at least in part, on a functional split, such as that defined by 3GPP. In some aspects, the DU 1430 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 1430 or with control functions hosted by the CU 1410.

[0170]

[0181] The lower layer functions may be implemented by one or more RUs 1440. In some deployments, the RUs 1440 controlled by the DU 1430 may correspond to logical nodes hosting RF processing functions, or low PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, PRACH extraction and filtering, etc.), or both, based at least in part on a functional split, such as a lower layer functional split. In such an architecture, the RU(s) 1440 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 1440 may be controlled by the corresponding DU 1430. In some scenarios, this configuration may enable the DU(s) 1430 and CU 1410 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0171]

[0182] The SMO framework 1405 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. In non-virtualized network elements, the SMO framework 1405 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an O1 interface). In virtualized network elements, the SMO framework 1405 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 1490) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, the CU 1410, the DU 1430, the RU 1440, and the Near-RT RIC 1425. In some implementations, the SMO framework 1405 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 1411, via the O1 interface. Additionally, in some implementations, the SMO framework 1405 can communicate directly with one or more RUs 1440 via an O1 interface. The SMO framework 1405 may also include a Non-RT RIC 1415 configured to support the functionality of the SMO framework 1405.

[0172]

[0183] The Non-RT RIC 1415 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources in the Near-RT RIC 1425, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features. The Non-RT RIC 1415 may be coupled to or communicate with the Near-RT RIC 1425 (such as via an A1 interface). The Near-RT RIC 1425 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and action over interfaces (such as via an E2 interface) connecting one or more CUs 1410, one or more DUs 1430, or both, and the O-eNB with the Near-RT RIC 1425.

[0173]

[0184] In some implementations, the Non-RT RIC 1415 may receive parameters or external enrichment information from an external server to generate AI / ML models to be deployed in the Near-RT RIC 1425. Such information may be utilized by the Near-RT RIC 1425 and may be received at the SMO framework 1405 or the Non-RT RIC 1415 from non-network data sources or from network functions. In some examples, the Non-RT RIC 1415 or the Near-RT RIC 1425 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 1415 may employ AI / ML models to monitor long-term trends and patterns in performance and take corrective action through the SMO framework 1405 (such as reconfiguration via O1) or through the creation of RAN management policies (such as A1 policies).

[0174]

[0185] As noted above, Figure 14 is provided as an example. Other examples may differ from those described with respect to Figure 14.

[0175]

[0186] The above disclosure provides illustration and description, and is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or acquired from practice of the embodiments.

[0176]

[0187] The following provides an overview of some aspects of the disclosure.

[0177]

[0188] Aspect 1: A method of wireless communications implemented by a user equipment (UE), comprising: detecting, while in a radio resource control (RRC) inactive state or an RRC idle state, that SDT-type data for a non-small data transmission (SDT) data radio bearer (DRB) has entered a buffer of the UE; and transmitting a message indicating the data in the buffer for the non-SDT DRB.

[0178]

[0189] Aspect 2: The method of aspect 1, wherein the message is configured to indicate one or more of SDT type data for a non-SDT DRB or SDT type data for an SDT DRB.

[0179]

[0190] Example 3: The method of example 1 or 2, wherein transmitting the message includes transmitting a buffer status report in a medium access control control element (MAC-CE) or RRC message.

[0180]

[0191] Aspect 4: The method of any of aspects 1 to 3, wherein sending the message includes sending the message if a trigger condition is met.

[0181]

[0192] Aspect 5: The method of any one of aspects 1 to 4, wherein transmitting the message includes transmitting the message during an SDT subsequent data transmission period that occurs following a first random access channel (RACH) procedure.

[0182]

[0193] Aspect 6: The method of aspect 5, further comprising, before transmitting the message and if no uplink grant is available, transmitting a RACH preamble to initiate a second RACH procedure during an SDT subsequent data transmission period.

[0183]

[0194] Aspect 7: The method of aspect 6, wherein the message includes at least a UE identifier, and the second RACH procedure is performed without sending an RRC resume request message.

[0184]

[0195] Aspect 8: The method of any of aspects 1 to 7, wherein transmitting the message includes transmitting the message in a scheduled resource if the scheduled resource is available for use.

[0185]

[0196] Aspect 9: The method of any of aspects 1 to 4, wherein transmitting the message includes transmitting the message during a configured allowed SDT subsequent data transmission period.

[0186]

[0197] Example 10: The method of any one of examples 1 to 9, further comprising transmitting data after transitioning to an RRC connected state.

[0187]

[0198] Example 11: The method of any one of examples 1 to 10, further comprising transmitting data in an RRC inactive state or an RRC idle state.

[0188]

[0199] Aspect 12: The method of any one of aspects 1 to 4, wherein transmitting the message includes transmitting the message in a first uplink transmission with data of an SDT type in coordination with an RRC resume request.

[0189]

[0200] Aspect 13: A method of wireless communication implemented by a user equipment (UE), comprising: detecting, while in a radio resource control (RRC) inactive state or an RRC idle state, that new data of a small data transmission (SDT) type has entered a buffer of the UE during an SDT subsequent data transmission period; and transmitting, during the SDT subsequent data transmission period, a message indicating the new data in the buffer.

[0190]

[0201] Aspect 14: The method of aspect 13, wherein the SDT subsequent data transmission period occurs after a first random access channel (RACH) procedure, and wherein the method further comprises, before transmitting the message and if there is no uplink grant available, transmitting a RACH preamble to initiate a second RACH procedure during the SDT subsequent data transmission period.

[0191]

[0202] Aspect 15: The method of aspect 14, wherein the message includes at least a UE identifier, and the second RACH procedure is performed without transmitting an RRC resume request message.

[0192]

[0203] Aspect 16: The method of any of aspects 13 to 15, wherein transmitting the message includes transmitting the message in a scheduled resource if the scheduled resource is available for use.

[0193]

[0204] Aspect 17: The method of aspect 13, wherein transmitting the message includes transmitting the message during a configured allowed SDT subsequent data transmission period.

[0194]

[0205]

[0033] Aspect 18: The method of any of aspects 13 to 17, wherein transmitting the message includes transmitting a buffer status report in a medium access control control element (MAC-CE) or RRC message.

[0195]

[0206] Aspect 19: The method of any one of aspects 13 to 18, wherein the new data is for an SDT data radio bearer.

[0196]

[0207] Aspect 20: The method of any of aspects 13 to 18, wherein the new data is for a non-SDT data radio bearer (DRB).

[0197]

[0208] Aspect 21: The method of any of aspects 13 to 20, wherein the message is configured to indicate one or more of SDT type data for a non-SDT data radio bearer (DRB), or SDT type data for an SDT DRB.

[0198]

[0209] Aspect 22: A method of wireless communication implemented by a network entity, comprising: receiving a message from a user equipment (UE) during a small data transmission (SDT) subsequent data transmission period indicating that new data of an SDT type has entered a buffer of the UE; and receiving the new data.

[0199]

[0210] Aspect 23: The method of aspect 22, wherein the message is configured to indicate one or more of SDT type data for a non-SDT data radio bearer (DRB) or SDT type data for an SDT DRB.

[0200]

[0211] Aspect 24: The method of aspect 22 or 23, wherein an SDT subsequent data transmission period occurs following a first random access channel (RACH) procedure, wherein the method further comprises receiving a preamble to initiate a second RACH procedure during the SDT subsequent data transmission period, and transmitting a random access response, wherein the message includes at least a UE identifier corresponding to the UE.

[0201]

[0212]

[0041] Aspect 25: The method of any of aspects 22 to 24, further comprising: transmitting a scheduled resource for the message; and receiving the message in the scheduled resource.

[0202]

[0213]

[0062] Aspect 26: The method of any one of aspects 22 to 25, wherein the message is received in a medium access control control element (MAC-CE) or radio resource control message.

[0203]

[0214] Aspect 27: The method of aspect 26, wherein the message includes a buffer status report.

[0204]

[0215] Aspect 28: The method of any one of aspects 22 to 27, wherein the message indicates that the new data is for a non-SDT data radio bearer (DRB).

[0205]

[0216] Aspect 29: The method of any of aspects 22 to 28, further comprising configuring the UE to transmit new data after transitioning to a radio resource control connected state.

[0206]

[0217]

[0071] Aspect 30: The method of any of aspects 22 to 29, further comprising configuring the UE to transmit new data in a radio resource control (RRC) inactive state or an RRC idle state.

[0207]

[0218] Aspect 31: A method of wireless communication implemented by a user equipment (UE), comprising: detecting, while in a radio resource control (RRC) inactive state or an RRC idle state, that SDT-type data for a non-small data transmission (SDT) data radio bearer (DRB) has entered a buffer of the UE; and transmitting a message indicating the data in the buffer for the non-SDT DRB, wherein the message is associated with a UE identifier (ID).

[0208]

[0219] Aspect 32: The method of aspect 31, further comprising indicating that the data is of an SDT type for a non-SDT DRB, an SDT type for an SDT DRB, or an SDT type for both an SDT DRB and a non-SDT DRB.

[0209]

[0220]

[0041] Aspect 33: The method of aspect 31 or 32, wherein the sending of the message includes sending a buffer status report in a medium access control control element (MAC-CE) or RRC message.

[0210]

[0221] Aspect 34: The method of aspect 33, wherein the RRC message includes a resume cause.

[0211]

[0222] Aspect 35: The method of aspect 33, wherein sending the message includes sending the message if a trigger condition is met.

[0212]

[0223]

[0037] Aspect 36: The method of any one of aspects 31 to 35, wherein the message includes a radio bearer identifier.

[0213]

[0224] Aspect 37: The method of any one of aspects 31 to 36, wherein the message indicates a type of radio bearer.

[0214]

[0225]

[0062] Aspect 38: The method of any one of aspects 31 to 37, wherein the message includes a logical channel group identifier.

[0215]

[0226]

[0041] Aspect 39: The method of any of aspects 31 to 38, wherein transmitting the message comprises transmitting the message in resources associated with a UE ID.

[0216]

[0227]

[0071] Aspect 40: The method of any one of aspects 31 to 39, wherein the UE ID comprises a cell radio temporary network identifier.

[0217]

[0228] Aspect 41: The method of aspect 40, wherein transmitting the message includes transmitting the message during an SDT subsequent data transmission period that occurs following a first random access channel (RACH) procedure.

[0218]

[0229] Aspect 42: The method of aspect 40 or 41, further comprising, before transmitting the message and if no uplink grant is available, transmitting a RACH preamble to initiate a second RACH procedure during an SDT subsequent data transmission period.

[0219]

[0230] Aspect 43: The method of aspect 42, wherein the message includes at least a UE ID, and wherein the second RACH procedure is performed without sending an RRC resume request message.

[0220]

[0231] Aspect 44: The method of any of aspects 31 to 43, wherein transmitting the message includes transmitting the message in a scheduled resource if the scheduled resource is available for use.

[0221]

[0232] Aspect 45: The method of any of aspects 31 to 44, wherein transmitting the message includes transmitting the message during a configured allowed SDT subsequent data transmission period.

[0222]

[0233]

[0071] Aspect 46: The method of any one of aspects 31 to 45, further comprising transmitting data after transitioning to an RRC connected state.

[0223]

[0234] Example 47: The method of any of examples 31 to 46, further comprising transmitting data in an RRC inactive state or an RRC idle state.

[0224]

[0235] Aspect 48: The method of any of aspects 31 to 47, wherein transmitting the message includes transmitting the message in a first uplink transmission with data of an SDT type in coordination with an RRC resume request.

[0225]

[0236] Aspect 49: A method of wireless communication implemented by a user equipment (UE), comprising: detecting, while in a radio resource control (RRC) inactive state or an RRC idle state, that new data of a small data transmission (SDT) type has entered a buffer of the UE during an SDT subsequent data transmission period; and transmitting, during the SDT subsequent data transmission period, a message indicating the new data in the buffer, wherein the message is associated with a UE identifier (ID).

[0226]

[0237] Aspect 50: The method of aspect 49, wherein the UE identifier includes a cell radio temporary network identifier.

[0227]

[0238] Aspect 51: The method of aspect 50, wherein the SDT subsequent data transmission period occurs after a first random access channel (RACH) procedure, and wherein the method further comprises, before transmitting the message and if there is no uplink grant available, transmitting a RACH preamble to initiate a second RACH procedure during the SDT subsequent data transmission period.

[0228]

[0239] Aspect 52: The method of aspect 51, wherein the message includes at least a UE ID, and wherein the second RACH procedure is performed without sending an RRC resume request message.

[0229]

[0240] Aspect 53: The method of any of aspects 49 to 52, wherein transmitting the message includes transmitting the message during a configured allowed SDT subsequent data transmission period.

[0230]

[0241] Aspect 54: The method of any of aspects 49 to 53, wherein the message includes a radio bearer identifier or indicates a type of radio bearer.

[0231]

[0242]

[0047] Aspect 55: The method of any of aspects 49 to 54, further comprising sending a buffer status report in a medium access control control element (MAC-CE) or RRC message.

[0232]

[0243] Aspect 56: The method described in aspect 55, wherein the RRC message includes a resume cause.

[0233]

[0244] Aspect 57: The method of any of aspects 49 to 56, wherein the message includes a logical channel group identifier.

[0234]

[0245] Aspect 58: A method of wireless communication implemented by a network entity, comprising receiving a message from a user equipment (UE) during a small data transmission (SDT) subsequent data transmission period indicating that new data of an SDT type has entered a buffer of the UE, wherein the message is associated with a UE ID and receives the new data.

[0235]

[0246] Aspect 59: The method of aspect 58, wherein the UE ID includes a cell radio temporary network identifier.

[0236]

[0247]

[0062] Aspect 60: The method of aspect 58 or 59, wherein the message is received in a medium access control control element (MAC-CE) or radio resource control message.

[0237]

[0248] Aspect 61: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform a method described in one or more of aspects 1 to 60.

[0238]

[0249] Aspect 62: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the memory comprises instructions executable by the one or more processors to cause the device to perform a method described in one or more of aspects 1 to 60.

[0239]

[0250] Aspect 63: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform a method described in one or more of aspects 1 to 60.

[0240]

[0251] Aspect 64: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method recited in one or more of aspects 1 to 60.

[0241]

[0252] Aspect 65: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method described in one or more of aspects 1 to 60.

[0242]

[0253] Aspect 66: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the methods described in one or more of aspects 1 to 60.

[0243]

[0254] The term "component" as used herein shall be broadly construed as hardware and / or a combination of hardware and software. Software shall be broadly construed to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or the like. A processor, as used herein, is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not intended to limit the scope of the invention. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it will be understood that software and hardware may be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0244]

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

[0245]

[0256] It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware, software, and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it will be understood that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0246]

[0257] Although particular combinations of features are recited in the claims and / or disclosed herein, these combinations do not limit the disclosure of various aspects. Indeed, many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. While each dependent claim set forth below may depend directly on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the range. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to include a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).

[0247]

[0258] No element, act, or instruction used herein should be construed as critical or required unless explicitly described as such. Also, as used herein, the articles "a" and "an" include one or more items and may be used interchangeably with "one or more." Furthermore, as used herein, the article "the" includes one or more items referenced in connection with the article "the" and may be used interchangeably with "one or more." Furthermore, as used herein, the terms "set" and "group" include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with "one or more." Where only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, the terms "has," "have," "having," and the like are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on," unless expressly specified otherwise. Also, as used herein, the term "or" is inclusive when used consecutively and can be used interchangeably with "and / or" unless otherwise specified (e.g., when used in combination with "either" or "only one of"). The inventions described in the claims of the present application as originally filed are set forth below. [C1] A user equipment (UE) for wireless communications, comprising: Memory and one or more processors coupled to the memory; The memory is provided to the UE. Detecting that small data transmission (SDT) type data for a non-SDT data radio bearer (DRB) has entered a buffer of the UE while in a radio resource control (RRC) inactive state or an RRC idle state; a user equipment (UE), comprising instructions executable by the one or more processors to cause the UE to transmit a message indicating the data in the buffer for the non-SDT DRB, wherein the message is associated with a UE identifier (ID). [C2] UE according to C1, wherein the message is configured to indicate that the data is of the SDT type for the non-SDT DRB, for an SDT DRB, or for both the SDT DRB and the non-SDT DRB. [C3] The UE of C1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to send a buffer status report in a medium access control control element (MAC-CE) or RRC message. [C4] The UE of C3, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the message if a trigger condition is met. [C5] The UE according to C4, wherein the RRC message includes a resume cause. [C6] The UE of C1, wherein the message includes a radio bearer identifier. [C7] The UE of C1, wherein the message indicates a type of radio bearer. [C8] The UE of C1, wherein the message includes a logical channel group identifier. [C9] The UE of C8, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the message in resources associated with the UE ID. [C10] The UE of C1, wherein the UE ID includes a Cell Radio Temporary Network Identifier. [C11] The UE of C10, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the message during an SDT subsequent data transmission period that occurs following a first random access channel (RACH) procedure. [C12] The UE of C11, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit a RACH preamble to initiate a second RACH procedure before transmitting the message and during the SDT subsequent data transmission period if no uplink grant is available. [C13] The UE of C12, wherein the message includes at least the UE ID, and the second RACH procedure is performed without sending an RRC resume request message. [C14] The UE of C1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the message in the scheduled resources if the scheduled resources are available for use. [C15] 10. The UE of claim 1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the message during a configured granted SDT subsequent data transmission period. [C16] The UE of C1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the data after transitioning to an RRC connected state. [C17] The UE of C1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the data in the RRC inactive state or the RRC idle state. [C18] The UE of C1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the message in a first uplink transmission involving data of the SDT type in coordination with an RRC resumption request. [C19] A user equipment (UE) for wireless communications, comprising: Memory and one or more processors coupled to the memory; The memory is provided to the UE. Detecting, while in a Radio Resource Control (RRC) inactive state or an RRC idle state, that new data of a small data transmission (SDT) type has entered a buffer of the UE during a data transmission period subsequent to an SDT; transmitting a message indicating the new data in the buffer during the SDT subsequent data transmission period, wherein the message is associated with a UE identifier (ID); and a user equipment (UE) comprising instructions executable by the one or more processors to cause the one or more processors to perform the above. [C20] The UE of C19, wherein the UE ID includes a Cell Radio Temporary Network Identifier. [C21] The UE of C19, wherein the SDT subsequent data transmission period occurs after a first random access channel (RACH) procedure, and wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit a RACH preamble to initiate a second RACH procedure during the SDT subsequent data transmission period before transmitting the message and if no uplink grant is available. [C22] The UE of C21, wherein the message includes at least the UE ID, and the second RACH procedure is performed without sending an RRC resume request message. [C23] The UE of C19, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the message during a configured granted SDT subsequent data transmission period. [C24] The UE of C19, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to send a buffer status report in a medium access control control element (MAC-CE) or RRC message. [C25] The UE of C24, wherein the RRC message includes a resume cause. [C26] The UE of C19, wherein the message includes a radio bearer identifier or indicates a type of radio bearer. [C27] The UE of C19, wherein the message includes a logical channel group identifier. [C28] A network entity for wireless communications, comprising: Memory and one or more processors coupled to the memory; and the memory is configured to include: receiving a message from a user equipment (UE) during a small data transmission (SDT) subsequent data transmission period indicating that new data of type SDT has entered a buffer of the UE, wherein the message is associated with a UE identifier (ID); receiving the new data; and a network entity comprising instructions executable by said one or more processors to cause said one or more processors to perform [C29] The network entity of C28, wherein the UE ID includes a Cell Radio Temporary Network Identifier. [C30] The network entity of C28, wherein the message is received in a Medium Access Control Control Element (MAC-CE) or Radio Resource Control message.

Claims

1. 1. A user equipment (UE) for wireless communications, comprising: Memory and one or more processors coupled to the memory; The memory includes: Detecting that small data transmission (SDT) type data for a non-SDT data radio bearer (DRB) has entered a buffer of the UE while in a radio resource control (RRC) inactive state or an RRC idle state; 11. A user equipment (UE) comprising instructions executable by the one or more processors to cause the one or more processors to: transmit a message indicating the data in the buffer for the non-SDT DRB; and wherein the message is associated with a UE identifier (ID).

2. 2. The UE of claim 1, wherein the message is configured to indicate that the data is of the SDT type for the non-SDT DRB, for an SDT DRB, or for both the SDT DRB and the non-SDT DRB.

3. 10. The UE of claim 1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to send a buffer status report in a Medium Access Control Control Element (MAC-CE) or RRC message.

4. The UE of claim 3 , wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the message when a trigger condition is met.

5. The UE of claim 4 , wherein the RRC message includes a resume cause.

6. The UE of claim 1 , wherein the message includes a radio bearer identifier.

7. The UE of claim 1 , wherein the message indicates a type of radio bearer.

8. The UE of claim 1 , wherein the message includes a logical channel group identifier.

9. The UE of claim 1 , wherein the UE ID comprises a Cell Radio Temporary Network Identifier.

10. 10. The UE of claim 1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the message in scheduled resources if the scheduled resources are available for use.

11. 2. The UE of claim 1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the message during a configured allowed SDT subsequent data transmission period.

12. 10. The UE of claim 1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the data after transitioning to an RRC connected state.

13. 2. The UE of claim 1, wherein the memory further comprises instructions executable by the one or more processors to cause the UE to transmit the data in the RRC inactive state or the RRC idle state.

14. 1. A user equipment (UE) for wireless communications, comprising: Memory and one or more processors coupled to the memory; The memory includes: Detecting that new data of a small data transmission (SDT) type has entered a buffer of the UE during an SDT subsequent data transmission period while in a radio resource control (RRC) inactive state or an RRC idle state; transmitting a message indicating the new data in the buffer during the SDT subsequent data transmission period, wherein the message is associated with a UE identifier (ID); and a user equipment (UE) comprising instructions executable by the one or more processors to cause the one or more processors to perform the steps of:

15. A network entity for wireless communications, comprising: Memory and one or more processors coupled to the memory; and the memory is configured to include: receiving a message from a user equipment (UE) during a small data transmission (SDT) subsequent data transmission period indicating that new data of SDT type has entered a buffer of the UE, wherein the message is associated with a UE identifier (ID); receiving the new data; and a network entity, comprising instructions executable by said one or more processors to cause said one or more processors to perform

Images