Multiplexing for MBS or SDT

Abstract

A method, an apparatus, and a computer-readable storage medium are provided for supporting Mobile Originated Small Data Transmission (MO-SDT) and Mobile Terminated Small Data Transmission (MT-SDT) or Point-to-Multipoint (P2M) Multicast and Broadcast Services (MBS). An exemplary method may include transmitting a capability indication indicating support of MO-SDT and MT-SDT to a base station. The exemplary method may further include receiving one or more configurations for MO-SDT and MT-SDT in a Radio Resource Control (RRC) message from the base station, the RRC message including at least an RRC release message. The exemplary method may further include transitioning to an RRC inactive state. The exemplary method may further include transmitting a Common Control Channel (CCCH) message in the MO-SDT transmission to the base station while in the RRC inactive state.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of and priority to International Application No. PCT / CN2022 / 075473, filed February 8, 2022, entitled "Multiplexing for MBS or SDT," which is expressly incorporated by reference in its entirety herein.

[0002] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems using small data transfer (SDT), such as mobile-originated small data transmission (MO-SDT) or mobile-terminated small data transmission (MT-SDT), or point-to-multi-point (P2M) or peer to peer (P2P) multicast and broadcast services (MBS).

[0003] introduction Wireless communication systems have been widely deployed to provide various telecommunication services such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that allows different wireless devices to communicate at a city, country, region, or even global level. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuing mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., for the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements are needed in 5G NR technology that may also be applicable to other multiple access technologies and the telecommunications standards that employ those technologies. Summary of the Invention

[0005] SUMMARY OF THE DISCLOSURE The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, nor is it intended to identify key or critical elements of all aspects or to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus in a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory, where the at least one processor is configured to transmit a capability indication representing support of MO-SDT and MT-SDT to a network entity. The at least one processor coupled to the memory may be further configured to receive one or more configurations for MO-SDT and MT-SDT in an RRC message including at least a radio resource control (RRC) release message from the network entity. The at least one processor coupled to the memory may be further configured to transition to an RRC inactive state. The at least one processor coupled to the memory may be further configured to transmit a common control channel (CCCH) message in the MO-SDT transmission to the network entity while in the RRC inactive state.

[0007] In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus in a UE are provided. The apparatus may include a memory and at least one processor coupled to the memory, where the at least one processor is configured to send a capability indication representing support of SDT and P2M MBS to a network entity. The at least one processor coupled to the memory may be further configured to receive one or more configurations for SDT and P2M MBS from the network entity. The at least one processor coupled to the memory may be further configured to transition to an RRC inactive state. The at least one processor coupled to the memory may be further configured to send a CCCH message over the MO-SDT to the network entity while in the RRC inactive state.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus in a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory, where the at least one processor is configured to receive a capability indication representing support of MO-SDT and MT-SDT from a UE. The at least one processor coupled to the memory may be further configured to transmit one or more configurations for MO-SDT and MT-SDT in an RRC message including at least an RRC release message to the UE. The at least one processor coupled to the memory may be further configured to receive a CCCH message in the MO-SDT transmission from the UE while in an RRC inactive state.

[0009] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus in a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory, where the at least one processor is configured to receive a capability indication representing support of SDT and P2M CBS from the UE. The at least one processor coupled to the memory may be further configured to send one or more configurations for SDT and P2M MBS to the UE. The at least one processor coupled to the memory may be further configured to receive a CCCH message over MO-SDT from the UE while in an RRC inactive state.

[0010] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of the various aspects may be employed and the description is intended to include all such aspects and their equivalents. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 illustrates an example of a wireless communication system and an access network in accordance with various aspects of the present disclosure. [Figure 2A] FIG. 2 illustrates an example of a first frame in accordance with various aspects of the present disclosure. [Figure 2B] FIG. 1 illustrates an example of a DL channel in a subframe in accordance with various aspects of the present disclosure. [Figure 2C] FIG. 2 illustrates an example of a second frame, according to various aspects of the present disclosure. [Figure 2D] FIG. 1 illustrates an example of a UL channel in a subframe in accordance with various aspects of the present disclosure. [Diagram 3] FIG. 2 illustrates an example of a base station and user equipment (UE) in an access network, in accordance with various aspects of the present disclosure. [Figure 4] FIG. 1 illustrates an example configured grant (CG) SDT that may be mobile originated (MO). [Diagram 5] FIG. 1 illustrates an example RA-SDT that may be an MO and may be used with a two-step RACH procedure. [Figure 6] FIG. 1 illustrates an example RA-SDT that may be an MO and may be used with a four-step RACH procedure. [Figure 7] FIG. 1 illustrates an exemplary MT-SDT that may be Msg4-based. [Figure 8] FIG. 1 illustrates an exemplary common frequency resource (CFR). [Figure 9A] FIG. 1 illustrates joint support of MO-SDT and MT-SDT in accordance with various aspects of the present disclosure. [Figure 9B] FIG. 1 illustrates joint support of MO-SDT and MT-SDT in a radio resource control (RRC) inactive state in accordance with various aspects of the present disclosure. [Figure 10] FIG. 1 illustrates joint support of SDT and MBS in accordance with various aspects of the present disclosure. [Figure 11A] A diagram illustrating an example resource configuration of SDT and MBS in accordance with various aspects of the present disclosure. [Figure 11B] A diagram illustrating an example resource configuration of SDT and MBS in accordance with various aspects of the present disclosure. [Figure 11C] A diagram illustrating an example resource configuration of SDT and MBS in accordance with various aspects of the present disclosure. [Figure 12] 1 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 13] 1 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 14] 1 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 15] 1 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 16] 1 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 17] 1 is a flowchart of a method of wireless communication in accordance with various aspects of the present disclosure. [Figure 18] FIG. 2 illustrates an example of a hardware implementation for an exemplary apparatus in accordance with various aspects of the present disclosure. [Figure 19] FIG. 2 illustrates an example of a hardware implementation for an exemplary apparatus in accordance with various aspects of the present disclosure. [Figure 20] FIG. 1 shows a diagram illustrating an exemplary split base station architecture. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] The detailed description set forth below in conjunction with the accompanying drawings describes various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The Detailed Description includes specific details intended to provide a thorough understanding of the various concepts. However, it will be apparent to one skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0013] Certain aspects of a telecommunications system are now presented with respect to various apparatus and methods that are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be realized using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0014] As an example, the elements, or any portion of the elements, or any combination of the elements, may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0015] Thus, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of types of computer-readable media, or any other medium that can be accessed by a computer and that can be used to store computer-executable code in the form of instructions or data structures.

[0016] Although aspects and implementations are described in this application by way of example for several embodiments, those skilled in the art will appreciate that additional implementations and use cases may occur in many different configurations and scenarios. The aspects described herein may be realized across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, implementations and / or applications may arise with integrated chip implementations and other non-modular component-based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Some examples may or may not be specifically targeted to a use case or application, but a wide variety of applicability of the described aspects may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and even aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described aspects. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementation and practice of the claimed and described aspects. For example, transmitting and receiving wireless signals necessarily involves a number of components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processor(s), interleavers, summers / analog summers, etc.). It is contemplated that the aspects described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, separate or discrete components, end-user devices, etc., of various sizes, shapes, and configurations.

[0017] FIG. 1 illustrates an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., 5G Core (5GC)). The base stations 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). The macro cells include base stations. The small cells include femto cells, pico cells, and micro cells.

[0018] A base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 over a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with the core network 190 over a second backhaul link 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: forwarding user data, encryption and decryption of radio channels, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, non-access stratum (NAS) message delivery, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and alert message delivery. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the core network 190) via a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184 (e.g., an Xn interface), and the third backhaul link 134 may be wired or wireless.

[0019] In some aspects, the base station 102 or 180 may be referred to as a RAN and may include aggregated or separated components. As an example of a separated RAN, the base station may include a central unit (CU) 106, one or more distributed units (DUs) 105, and / or one or more remote units (RUs) 109, as shown in FIG. 1. The RAN may be separated by a split between the RU 109 and the aggregated CU / DU. The RAN may be separated by a split between the CU 106, the DU 105, and the RU 109. The RAN may be separated by a split between the CU 106 and the aggregated DU / RU. The CU 106 and one or more DUs 105 may be connected via an F1 interface. The DUs 105 and the RUs 109 may be connected via a fronthaul interface. The connection between the CU 106 and the DU 105 may be referred to as a midhaul, and the connection between the DU 105 and the RU 109 may be referred to as a fronthaul. The connection between the CU 106 and the core network may be referred to as a backhaul. The RAN may be based on a functional division between various components of the RAN, for example, between the CU 106, the DU 105, or the RU 109. The CU may be configured to perform processing of one or more aspects of a wireless communication protocol, for example, one or more layers of a protocol stack, and the DU(s) may be configured to process other aspects of the wireless communication protocol, for example, other layers of the protocol stack. In various implementations, the division between layers processed by the CU and layers processed by the DU may occur at different layers of the protocol stack. As one non-limiting example, the DU 105 may provide logical nodes for hosting at least a portion of a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer based on a functional division.The RU may provide a logical node configured to host at least a portion of the PHY layer and radio frequency (RF) processing. The CU 106 may host higher layer functions above the RLC layer, such as, for example, a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, etc. In other implementations, the division between layer functions provided by the CU, DU, or RU may be different.

[0020] An access network may include one or more integrated access and backhaul (IAB) nodes 111 that exchange wireless communications with UEs 104 or other IAB nodes 111 to provide access and backhaul to a core network. In an IAB network of multiple IAB nodes, an anchor node may be referred to as an IAB donor. An IAB donor may be a base station 102 or 180 that provides access to a core network 190 or an EPC 160 and / or control to one or more IAB nodes 111. An IAB donor may include a CU 106 and a DU 105. An IAB node 111 may include a DU 105 and a mobile termination (MT). The DU 105 of an IAB node 111 may act as a parent node, and the MT may act as a child node.

[0021] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) that may provide service to restricted groups known as closed subscriber groups (CSGs). The communication link 120 between the base station 102 and the UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the base station 102, and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use multiple-input and multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 may use spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, allocated in a carrier aggregation of up to Yx MHz (x component carriers) in total, used for transmission in each direction. The carriers may be adjacent or non-adjacent to each other. The carrier allocation may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers.The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0022] Particular UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL WWAN spectrum. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0023] The wireless communication system may further include a Wi-Fi access point (AP) 150 that communicates with Wi-Fi stations (STAs) 152 via communication links 154, such as in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the STAs 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine if a channel is available.

[0024] The small cell 102' may operate in an unlicensed spectrum and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, etc.) used by the Wi-Fi AP 150. By employing NR in the unlicensed frequency spectrum, the small cell 102' may increase coverage to and / or capacity of the access network.

[0025] The electromagnetic spectrum is often divided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU).

[0026] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and / or FR2 characteristics, and thus, in effect, extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0027] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, it should be understood that unless otherwise specified, terms such as "millimeter wave" as used herein may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0028] The base station 102, whether a small cell 102′ or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, g Node B (gNB), or another type of base station. Some base stations, such as the gNB 180, may operate at millimeter wave and / or quasi-millimeter wave frequencies in the conventional sub-6 GHz spectrum in communication with the UE 104. When the gNB 180 operates at millimeter wave or quasi-millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 for the UE 104 to compensate for path loss and short distances. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0029] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182″. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180 / UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

[0030] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are forwarded through the Serving Gateway 166, which is itself connected to the PDN Gateway 172. The PDN Gateway 172 provides IP address allocation for the UE as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP services 176, which may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide functionality for provisioning and delivery of MBMS user services. The BM-SC 170 may act as an entry point for content providers' MBMS transmissions and may be used to authorize and initiate MBMS bearer services in the public land mobile network (PLMN) and may be used to schedule MBMS transmissions.The MBMS Gateway 168 can be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and can be responsible for session management (start / stop) and collection of eMBMS related charging information.

[0031] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. In general, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through the UPF 195. The UPF 195 provides IP address allocation for the UE as well as other functions. The UPF 195 is connected to IP Services 197. The IP services 197 may include the Internet, an intranet, IP Multimedia Subsystem (IMS), Packet Switch (PS) Streaming (PSS) services, and / or other IP services.

[0032] A base station may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for the UE 104. Examples of the UE 104 include a cellular phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small cooking appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UEs 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation configuration. One or more of these devices may collectively access the network and / or individually access the network.

[0033] Referring again to FIG. 1 , in some aspects, the UE 104 may include an SDT component 198. In some aspects, the SDT component 198 may send a capability indication indicating support for MO-SDT and MT-SDT to a network entity. In some aspects, the SDT component 198 may receive one or more configurations for MO-SDT and MT-SDT from a network entity in an RRC message including at least an RRC release message. In some aspects, the SDT component 198 may transition to an RRC inactive state. In some aspects, the SDT component 198 may send a CCCH message in an MO-SDT transmission to a network entity while in the RRC inactive state.

[0034] In some aspects, the network entity may be implemented in a split base station architecture as a base station (i.e., an aggregated base station) or as a central unit (CU), distributed unit (DU), radio unit (RU), near-real time (Near-RT) RAN Intelligent Controller (RIC), or non-real time (Non-RT) RIC.

[0035] In some aspects, the SDT component 198 may send a capability indication to a network entity indicating support of SDT and P2M CBS. In some aspects, the SDT component 198 may receive one or more configurations for SDT and P2M MBS from a network entity. In some aspects, the SDT component 198 may transition to an RRC inactive state. In some aspects, the SDT component 198 may send a CCCH message over the MO-SDT to a network entity while in the RRC inactive state.

[0036] In some aspects, the base station 102 / 180 or another network entity such as the DU 105 or RU 109 may include an SDT component 199. In some aspects, the SDT component 199 may receive a capability indication from the UE indicating support of MO-SDT and MT-SDT. In some aspects, the SDT component 199 may transmit one or more configurations for MO-SDT and MT-SDT in an RRC message including at least an RRC release message to the UE. In some aspects, the SDT component 199 may receive a CCCH message in an MO-SDT transmission from the UE while in an RRC inactive state.

[0037] In some aspects, the SDT component 199 may receive a capability indication from the UE indicating support of SDT and P2M CBS. In some aspects, the SDT component 199 may send one or more configurations for SDT and P2M MBS to the UE. In some aspects, the SDT component 199 may receive a CCCH message over the MO-SDT from the UE while in an RRC inactive state.

[0038] The following description may focus on 5G NR, however, the concepts described herein may be applicable to other similar domains, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0039] FIG. 2A is a diagram 200 illustrating an example of a first subframe in a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of a DL channel in a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe in a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of a UL channel in a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either DL or UL, or time division duplexed (TDD) where for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL. In the example provided by FIG. 2A, FIG. 2C, the 5G NR frame structure is assumed to be TDD, subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible for DL / UL use, and subframe 3 is configured with slot format 1 (all UL). Subframes 3 and 4 are shown with slot formats 1 and 28, respectively, but any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) or semi-statically / statically through Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure, which is TDD.

[0040] 2A-2D show a frame structure, and aspects of the present disclosure may be applicable to other wireless communication technologies, which may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 subframes (1 ms) of equal size. Each subframe may include one or more time slots. A subframe may also include a minislot, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also called single carrier frequency division multiple access (SC-FDMA) symbols) (for power limited scenarios, i.e., limited to single stream transmission). The number of slots in a subframe is based on the CP and a number logic, which defines the subcarrier spacing (SCS), which effectively defines the symbol length / period equal to 1 / SCS.

[0041] [Table 1]

[0042] For normal CP (14 symbols / slot), the different number logics μ0-4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, number logic 2 allows 4 slots per subframe. Thus, for normal CP and number logic μ, 14 symbols / slot and 2 μ There are slots / subframes. The subcarrier spacing is 2 μ *15kHz, where μ is a number logic 0-4. Therefore, number logic μ=0 has a subcarrier spacing of 15kHz and number logic μ=4 has a subcarrier spacing of 240kHz. The symbol length / period is inversely proportional to the subcarrier spacing. Figures 2A-2D provide an example of a normal CP with 14 symbols per slot and number logic μ=2 with 4 slots per subframe. The slot duration is 0.25ms, the subcarrier spacing is 60kHz, and the symbol duration is about 16.67μs. Within a set of frames, there may be one or more different Bandwidth Parts (BWPs) (see Figure 2B), which are frequency division multiplexed. Each BWP may have a specific number logic and CP (normal or extended).

[0043] A resource grid may be used to represent the frame structure. Each time slot contains resource blocks (RBs) (also called physical RBs (PRBs)), spanning 12 consecutive subcarriers. The resource grid is divided into resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0044] As shown in Figure 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (shown as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0045] FIG. 2B shows an example of various DL channels in a subframe of a frame. A physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), where each CCE includes 6 RE groups (REGs), and each REG includes 12 consecutive REs in an OFDM symbol of an RB. The PDCCHs in one BWP may be referred to as a control resource set (CORESET). During a PDCCH monitoring occasion on the CORESET, the UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space), where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be deployed at higher and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be present in symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine the subframe / symbol timing and the physical layer identity. A secondary synchronization signal (SSS) may be present in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the timing of the radio frame. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS.The physical broadcast channel (PBCH), which carries the master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and paging messages.

[0046] As shown in FIG. 2C , some of the REs carry DM-RS (depicted as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE may transmit sounding reference signals (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and the UE may transmit the SRS in one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0047] 2D shows an example of various UL channels within a subframe of a frame. The PUCCH may be arranged as shown in one configuration. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCIs.

[0048] 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 performs Layer 3 and Layer 2 functions. Layer 3 includes a Radio Resource Control (RRC) layer, and Layer 2 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The controller / processor 375 is responsible for RRC layer functions associated with broadcasting system information (e.g., MIBs, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), mobility between radio access technologies (RATs), and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with forwarding higher layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and mapping of logical channels to transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), MAC SDUs from TBs, and MAC SDUs from TBs. It provides the MAC layer functions associated with demultiplexing of SDUs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0049] The transmit (TX) processor 316 and receive (RX) processor 370 perform Layer 1 functions associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. This OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter, e.g., 318TX. Each transmitter, e.g., 318TX, may modulate a radio frequency (RF) carrier with the respective spatial stream for transmission.

[0050] At the UE 350, each receiver 354 RX receives a signal through its respective antenna 352. Each receiver 354 RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 perform layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by a channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel, which are then provided to a controller / processor 359, which performs layer 3 and layer 2 functions.

[0051] The controller / processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides transport and logical channel demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0052] Similar to the functionality described in connection with DL transmission by base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with forwarding of higher layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping of logical channels to transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0053] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme as well as to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters, e.g., 354TX. Each transmitter, e.g., 354TX, may modulate an RF carrier with a respective spatial stream for transmission.

[0054] The UL transmission is processed at the base station 310 in a manner similar to that described with respect to the receiver functions at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides this information to the RX processor 370.

[0055] The controller / processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides transport and logical channel demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0056] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects associated with the SDT component 198 of FIG.

[0057] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects associated with the SDT component 199 of FIG.

[0058] In some wireless communication systems, the RRC protocol may be used on the air interface. The functions of the RRC protocol may include, among others, connection establishment and release functions, broadcast of system information, establishment, reconfiguration and release of radio bearers, RRC connection mobility procedures, paging notification and release, and outer loop power control. The RRC protocol may configure the user plane and control plane according to the network conditions and may enable radio resource management strategies to be implemented. Some example services and functions of the RRC layer / sublayer may include broadcast of system information related to the access stratum (AS) or non-access stratum (NAS), paging, establishment and release of an RRC connection between the UE and the radio access network (RAN), establishment and release of signaling radio bearers (SRBs) or data radio bearers (DRBs), mobility functions, etc. The operation of the RRC may be based on the particular state that the UE may be in. In some wireless communication systems, the UE may be in an RRC idle state, an RRC inactive state, or an RRC active state.

[0059] The UE may enter the RRC idle state after power-on and before establishing an RRC connection. The UE may also enter the RRC idle state after a connection failure or RRC release in the RRC connected or RRC inactive state. In the RRC idle state, the UE may be able to perform or process public land mobile network (PLMN) selection, broadcast of system information (SI), cell reselection mobility, paging for mobile terminated (MT) data, or discontinuous reception (DRX) for core network (CN) paging configured by the NAS. In the RRC inactive state, the UE may be able to perform or process broadcast of SI, cell reselection mobility, RAN paging, RAN based notification area (RNA), DRX for RAN paging, RAN connection in the control plane or user plane, etc. In the RRC inactive state, the AS context of the UE may be stored in the RAN, and the UE and the RAN may know the RNA to which the UE belongs. In the RRC connected mode, in addition to being able to perform or handle RAN connection, the UE may also transmit or receive unicast data from the RAN, and network controlled mobility including measurements may also be processed or performed.

[0060] In the RRC inactive state, the UE may identify a small amount of UL data for transmission (e.g., data related to an instant messaging service, push notification, or a wearable device) that may be infrequent or unexpected. To transmit the UL data, the UE may perform a random access channel (RACH) procedure, establish an RRC connection with the network, and enter an RRC connected state. However, performing a RACH procedure and establishing an RRC connection for a small amount of data may be inefficient considering the larger signaling overhead compared to the smaller amount of data to be transmitted. Thus, in some wireless communication systems, a UE in an RRC inactive state may be able to use an SDT procedure to transmit an amount of data below a threshold, for example, while remaining in the RRC inactive state, without transitioning or entering an RRC connected state.

[0061] FIG. 4 is a diagram 400 illustrating an example configured grant (CG) SDT that may be mobile originated (MO). As shown in FIG. 4, the base station 404 may send a CG resource configuration 406 in an RRC release message. The CG resource configuration 406 in the RRC release message may be associated with a suspension configuration, such as a SuspendConfig information element (IE). The suspension configuration may provide information to the UE 402, such as RNA updates, paging cycles, etc. The CG resource configuration 406 may be a configuration of CG resources for the UE 402's UL SDT. In some aspects, the RRC release message may also be used to configure CG-SDT resources for the UE to use while the UE 402 is in an RRC inactive state. In some aspects, the CG resource configuration 406 may include one Type 1 CG configuration. In some aspects, the Type 1 CG may be when an uplink grant is provided by the RRC and stored as a configured uplink grant. The UE may use resources provided by the Type 1 CG without additional DCI. In some aspects, the type-2 CG may include an RRC configuration and an uplink grant, where the uplink grant is provided by a PDCCH, such as a DCI, and is stored or cleared as a configured uplink grant based on layer 1 (L1) signaling indicating configured uplink grant activation or deactivation. In a type-1 CG configuration, the network may RRC configure one or more of a configured scheduling radio network temporary identifier (CS-RNT) for retransmissions, a periodicity of the type-1 CG, a time domain offset representing an offset of resources in the time domain, a time domain allocation representing an allocation of the configured uplink grant in the time domain that may include a starting symbol and a length, a number of HARQ processes for the CG, etc. In some aspects, the CG resource configuration 406 may include multiple CG-SDT configurations per carrier in an RRC inactive state that may be supported by a network associated with the base station 404.

[0062] In some aspects, after receiving the CG resource configuration 406, the UE 402 may be in an RRC inactive state at 408. At some point during the RRC inactive state, the UE 402 may transmit a first UL message 410 to the base station 404. For example, the first UL message may be associated with an SDT. In some aspects, the first UL message 410 may be transmitted via a CG transmission and may include an RRC resume request and uplink data. Upon receiving the first UL message 410, the base station 404 may transmit a network response 412 to the UE 402. In some aspects, the network response 412 may include an acknowledgement (ACK) or a retransmission. In some aspects, the network response 412 may not include an RRC message (e.g., because the UE 402 is still in the RRC inactive state).

[0063] In some aspects, after receiving the network response 412, the UE 402 may transmit additional uplink data 414 to the base station 404 in a subsequent data transmission. In some aspects, in the case of CG-SDT, the subsequent data transmission may use CG resources for the new data transmission or may be based on a dynamic grant (DG) of resources for uplink retransmission. In some aspects, upon receiving the uplink data 414, the base station 404 may transmit downlink data 416 in response to the uplink data 414. In some aspects, upon receiving the downlink data 416 in response to the uplink data 414, the UE 402 may transmit additional uplink data 418 to the base station 404. At some point, the base station may transmit an RRC release 420 (which may also include a suspend configuration, e.g., such as a SuspendConfig IE) to the UE 402. In some aspects, the RRC release 420 may terminate the SDT procedure from an RRC perspective.

[0064] In addition to the CG SDT, the SDT may be random access (RA) based. For example, FIG. 5 is a diagram 500 illustrating an example RA-SDT that may be MO and used with a two-step RACH procedure. As shown in FIG. 5, the base station 504 may send an RRC release message 506 to the UE 502. The RRC release message 506 may be associated with a suspension configuration, such as a SuspendConfig IE. The suspension configuration may provide information such as RNA updates, paging cycles, etc. to the UE 502.

[0065] In some aspects, after receiving the RRC release message 506, the UE 502 may be in an RRC inactive state at 508. At some point during the RRC inactive state, the UE 502 may transmit a random access preamble 510 to the base station 504. The random access preamble 510 may be a contention based random access (CBRA). In CBRA, the UE 502 may randomly select a random access preamble sequence, for example, from a set of preamble sequences, to transmit the random access preamble 510. Because the UE 502 randomly selects a preamble sequence, the base station 504 may simultaneously receive another preamble from a different UE. Thus, the CBRA provides for the base station 504 to resolve such contention between multiple UEs. Before transmitting the random access preamble 510, the UE 502 may obtain random access parameters, including, for example, preamble format parameters, time and frequency resources, parameters for determining a root sequence and / or a cyclic shift for the random access preamble, for example, in the SI. The preamble may be transmitted with an identifier such as the RA-RNTI.

[0066] After transmitting the random access preamble 510 to the base station 504, the UE 502 may also transmit a PUSCH payload 511 to the base station 504. In some aspects, the PUSCH payload 511 may include an RRC resume request, UL data, or a buffer status report (BSR) medium access control (MAC) control element (MAC-CE). Upon receiving the PUSCH payload 511, the base station 504 may transmit a network response 512 to the UE 502. In some aspects, the network response 512 may include a contention resolution. In some aspects, the network response 512 may not include an RRC message (e.g., because the UE 402 is still in an RRC inactive state).

[0067] In some aspects, after receiving the network response 512, the UE 502 may transmit additional uplink data 514 to the base station 504 in a subsequent data transmission. In some aspects, in the case of RA-SDT, the UE 502 may re-establish the SDT PDCP and resume the SDT RBs that may be configured for small data. In some aspects, in the subsequent data transmission (after successful contention resolution), the UE 502 may monitor dynamic grants (DGs) with the cell RNTI C-RNTI (if configured) in a separate common search space (CSS) in RA-SDT.

[0068] In some aspects, upon receiving the uplink data 514, the base station 504 may transmit downlink data 516 in response to the uplink data 514. In some aspects, upon receiving the downlink data 516 in response to the uplink data 514, the UE 502 may transmit additional uplink data 518 to the base station 504. At some point, the base station may transmit an RRC release 520 (which may also include a suspension configuration, e.g., a SuspendConfig IE) to the UE 502. In some aspects, the RRC release 520 may terminate the SDT procedure from an RRC perspective.

[0069] In another example, Figure 6 is a diagram 600 illustrating an example RA-SDT that may be MO and may be used with a four-step RACH procedure. As shown in Figure 6, a base station 604 may send an RRC release message 606 to a UE 602. The CG RRC release message 606 may be associated with a suspension configuration, such as a SuspendConfig IE. The suspension configuration may provide information to the UE 602, such as RNA updates, paging cycles, etc.

[0070] In some aspects, after receiving the RRC release message 606, the UE 602 may be in an RRC inactive state at 608. At some point during the RRC inactive state, the UE 602 may transmit a random access preamble 610A to the base station 604. The random access preamble 610A may be CBRA. In CBRA, the UE 602 may randomly select a random access preamble sequence, for example, from a set of preamble sequences, to transmit the random access preamble 610A. Because the UE 602 randomly selects a preamble sequence, the base station 604 may simultaneously receive another preamble from a different UE. Thus, the CBRA provides for the base station 604 to resolve such contention between multiple UEs. Before transmitting the random access preamble 610A, the UE 602 may obtain random access parameters, including, for example, preamble format parameters, time and frequency resources, parameters for determining a root sequence and / or a cyclic shift for the random access preamble, for example, in the SI. The preamble may be transmitted with an identifier such as the RA-RNTI.

[0071] After transmitting the random access preamble 610A to the base station 604, the UE 602 may receive a random access response 610B from the base station 604. Upon receiving the random access response 610B from the base station 604, the UE 602 also transmits a PUSCH payload 611 to the base station 604. In some aspects, the PUSCH payload 611 may include an RRC resumption request, UL data, or BSR MAC-CE, and upon receiving the PUSCH payload 611, the base station 604 may transmit a network response 612 to the UE 602. In some aspects, the network response 612 may include a contention resolution. In some aspects, the network response 612 may not include an RRC message (e.g., because the UE 402 is still in an RRC inactive state).

[0072] In some aspects, after receiving the network response 612, the UE 602 may transmit additional uplink data 614 to the base station 604 in a subsequent data transmission. In some aspects, in the case of RA-SDT, the UE 602 may re-establish the SDT PDCP and resume the SDT RBs that may be configured for small data. In some aspects, in a subsequent data transmission (after successful contention resolution), the UE 602 may monitor the DG with the cell RNTI C-RNTI (if configured) in a separate common search space (CSS) in RA-SDT.

[0073] In some aspects, upon receiving the uplink data 614, the base station 604 may transmit downlink data 616 in response to the uplink data 614. In some aspects, upon receiving the downlink data 616 in response to the uplink data 614, the UE 602 may transmit additional uplink data 618 to the base station 604. At some point, the base station may transmit an RRC release 620 (which may also include a suspension configuration, e.g., a SuspendConfig IE) to the UE 602. In some aspects, the RRC release 620 may terminate the SDT procedure from an RRC perspective.

[0074] In MO-SDT, non-SDT DL data may be supported (e.g., in DL data 416, 516, or 616). For example, in CG-SDT, CG-SDT resources may be configured in a previous RRC release signaling. DL data may be scheduled by dynamic grant. The UE may monitor a UE-specific search space addressed in the C-RNTI even when there is no UL transmission.

[0075] In addition to MO-SDT, MT-SDT may also be supported by the UE. For example, FIG. 7 is a diagram 700 illustrating an example MT-SDT that may be Msg4-based. In some aspects, Msg2 (random access response)-based SDT may include DL data for UEs with identities that may not be verified. Msg4-based MT-SDT may address such issues. As shown in FIG. 7, a UE 702 may be in an RRC inactive state at 706. The UE 702 may receive a paging 708 from a base station 704. In some aspects, the paging 708 may be associated with a UE identity associated with the UE 702. For example, the paging 708 may include an ID that may be used to derive an identifier (ID) associated with the UE 702. In some aspects, the paging 708 may also include an MT-SDT indication associated with the UE 702. Upon receiving the paging 708, the UE 702 may transmit an RA preamble 710 to the base station 704 via a dedicated preamble. In some aspects, the UE 702 may be allowed to use the MO-SDT preamble for the RACH for DL ​​data reception instead of using a dedicated RACH resource, as long as an MT-SDT indication is paged in paging 708.

[0076] In some aspects, upon receiving the RA preamble 710, the base station 704 may transmit an RA response 712 to the UE 702. In some aspects, upon receiving the RA response 712, the UE 702 may transmit an RRC resume request 714 in Msg3 to the base station 704. In some aspects, the UE 702 may indicate in Msg3 whether the UE intends to send data in the UL, for example, by BSR or UE assistance information (similar to MO-SDT). In some aspects, the RRC resume request 714 may include an authentication token with a UE identity associated with the UE 702. Based on the authentication token with a UE identity associated with the UE 702, the base station 704 may verify the identity of the UE 702 and, in response, transmit Msg4 716, which may be encrypted with the authentication token. In some aspects, Msg4 716 may include DL data. In some aspects, Msg4 716 may include RRC signaling. Upon receiving the DL data 716, the UE 702 may transmit subsequent UL data 718 to the base station 704. In some aspects, the base station 704 may send an RRC resume message to the UE 702 if the UE 702 is allowed to send UL in the RRC connected state but not in the RRC inactive state, or may send an RRC release to keep the UE inactive for a UL response.

[0077] A common frequency resource (CFR) for a group-common PDCCH or PDSCH may be confined within frequency resources of an initial or dedicated bandwidth portion (BWP) of different UEs (belonging to the same or different UE type or UE capability) and may use the same numerology (SCS and cyclic prefix (CP)). For example, FIG. 8 is a diagram 800 illustrating an example CFR. As shown in FIG. 8, a BWP 802 of a first UE and a BWP 804 of a second UE may include a CFR 806. In some aspects, the CFR may include one or more configurations, i.e., a starting PRB and number of PRBs, a starting PRB and a common reference, or an RS, PDCCH, or PDSCH configuration within the CFR.

[0078] In some wireless communication systems, SDTs including MO-SDT and MT-SDT in RRC inactive state may be supported. MBS in all RRC states including RRC inactive state may also be supported. In some aspects, RAN nodes in cells may form an MBS SFN area. Cells in the MBS SFN area may be designated as reserved cells. Reserved cells may not provide multicast / broadcast content, but may be time synchronized to the cell and may have limited power on MBS SFN resources to limit interference to the MBS SFN area. Each RAN node in the MBS SFN area synchronously transmits the same MBS control information and data. For example, cells (e.g., RAN nodes) may transmit transmissions using the same frequency resources at the same time (e.g., synchronously), and the transmissions may include the same control and / or data. A UE may receive the transmissions as if they were from a single cell, for example, based on the synchronous transmission of the same information using the same frequency resources. Each area may support broadcast, multicast, and unicast services. A unicast service is a service provided to a particular user, e.g., a voice call. A multicast service is a service that may be received by a group of users, e.g., a subscription video service. A broadcast service is a service that may be received by all users, e.g., a news broadcast. In some aspects, a first MBS SFN area may support a first MBS broadcast service, such as by providing a particular news broadcast to the UE. A second MBS SFN area may support a second MBS broadcast service, such as by providing a different news broadcast to the UE. Each MBS SFN area may support one or more physical multicast channels (PMCHs) or PDCCH-scheduled PDSCHs. Each PMCH or PDCCH-scheduled PDSCH corresponds to an MCH or DL-SCH.Each MCH or DL-SCH can multiplex multiple multicast logical channels. Each MBS SFN area may have one multicast control channel (MCCH). Thus, one MCH or DL-SCH can multiplex one or more MCCHs and multiple multicast traffic channels (MTCHs), and the remaining MCH or DL-SCH can multiplex multiple MTCHs.

[0079] A UE may camp on a cell to discover the availability of MBS service access and corresponding configuration. First, the UE may acquire system information and may acquire an MBS SFN area configuration message on the MCCH based on the system information. The system information may include information for acquiring the MCCH, such as an MBS SFN area identifier for each MBS SFN area supported by the cell, an MCCH repetition period, an MCCH offset, an MCCH modification period, a signaling MCS, subframe allocation information indicating which subframes of a radio frame as indicated by the repetition period and offset may transmit the MCCH, and / or an MCCH change notification configuration. The MBS SFN area configuration message may indicate group identity information, one or more session identifiers, resources allocated per PMCH, an MCH scheduling period, or dynamic PDCCH-based PDSCH scheduling, etc. The UE may receive control information indicating, for example, a field indicating the start of each scheduling period of the PMCH, a channel identifier, and / or an end of the MTCH.

[0080] In some aspects, ACK / NACK-based HARQ feedback and NACK-only-based HARQ feedback may be supported to improve multicast reliability for RRC connected UEs. Aspects provided herein provide joint support for SDTs, including MO-SDT and MT-SDT and MBS (with or without retransmissions triggered by UE HARQ feedback) for UEs in an RRC inactive state. For example, sensor networks for environmental monitoring, factory automation, periodic software and firmware updates, or smart homes receiving mission-critical signaling may all be exemplary UEs that may support SDTs (including MO-SDT and MT-SDT) and MBS. With aspects provided herein, UEs may benefit from power savings, latency or signaling overhead reduction, and reliability improvements for multicast in the RRC inactive state, enabled, for example, by P2P retransmissions and priority indication. Some aspects provided herein include support for multicast reception by UEs in an RRC inactive state. The UE may use shared processing for MBS broadcast and unicast reception. Based on aspects provided herein, a UE in an RRC inactive state may receive multicast data configured by semi-persistent scheduling (SPS) or scheduled by DCI. If the UE does not have a valid timing advance (TA) and valid UL resources (PUCCH or PUSCH) in the RRC inactive state, the UE may not send a HARQ NACK to trigger retransmission of an MBS that is not correctly received by the UE, nor may it send a MAC-CE to activate or deactivate an SPS configuration for the MBS.Aspects provided herein improve service continuity, reliability, and resource utilization efficiency of MBS by addressing the inability to trigger retransmission of MBS or deactivate SPS configuration for MBS while still allowing the UE to remain in RRC inactive state. As described herein, a UE may support both SDT and MBS sessions in RRC inactive state. Joint support for SDT allows the UE to transmit HARQ feedback for MT-SDT or MBS using the same set of PUCCH resources. For example, the UE may have PUCCH resources for SDT while remaining RRC inactive, and the UE may use PUCCH resources to transmit HARQ NACK for MBS while remaining RRC inactive. The use of SDT PUCCH resources can help reduce system overhead for uplink communications and improve reliability of downlink MBS reception by providing the UE with an indication to the network when it is not receiving MBS.

[0081] In some aspects, joint support for MBS and MT-SDT allows a UE to transmit data or control information on the uplink using configured CG-SDT resources, which reduces PDCCH monitoring at the UE, thereby allowing signaling overhead reduction and UE power saving. Since the CG-SDT resources are pre-configured, the UE can skip monitoring the PDCCH with a grant of resources before transmitting data or control. The data or control can be for MBS, for example, and since the UE already has configured CG-SDT resources, the UE can transmit uplink data or control without monitoring a separate grant of resources. The network also saves signaling overhead by not transmitting DCI allocating resources for data or control.

[0082] In some aspects, joint support for MBS and MT-SDT allows the network to perform link adaptation for MBS (for initial transmission or retransmission) based on CSI reporting from a UE (or group of UEs) over MO-SDT. Using MO-SDT resources to provide CSI feedback for MBS may result in improved reliability. Using MO-SDT resources already configured for the UE may provide resource utilization efficiency and save overhead signaling, since the network does not transmit a separate set of resources for CSI transmission.

[0083] In some aspects, joint support for MBS and MT-SDT allows the network to multiplex MBS and MT-SDT in a downlink transmission to the UE, which may result in UE power savings, reduced system overhead on the DL, and / or reduced PDCCH monitoring for reduced latency. The network can send MT-SDT and MBS together without additional signaling to inform the UE of MT-SDT, which may save overhead signaling from the network and may save power at the UE since the UE may skip monitoring such signaling.

[0084] In some aspects, joint support for MBS and MT-SDT allows a UE to provide periodic, semi-static, or on-demand updates (e.g., based on a UE request in MO-SDT) for software or firmware for UEs in a low power state (e.g., in downlink MBS-based transmissions). The combined use of CG-SDT and MBS resources may result in reduced system overhead and UE power savings, for example, by using configured resources without added PDCCH signaling and the UE skipping monitoring for added PDCCH signaling.

[0085] In some aspects, joint support for MBS and MT-SDT allows joint configuration for MBS and SDT with dedicated RRC signaling. As an example, a single RRC release message for MBS and SDT may be RRC configured, which may result in reduced signaling overhead in both downlink and uplink directions since a single HARQ-ACK may be used for joint configuration or messages.

[0086] In some aspects, joint support for MBS and MT-SDT allows the network to send UE reconfiguration signaling for MBS in MT-SDT downlink resources for the UE. The UE may send UE assistance information (UAI) in CG-SDT resources for MO-SDT. Using SDT resources to reconfigure MBS allows additional flexibility for network scheduling.

[0087] In some aspects, joint support for MBS and MT-SDT allows the network to provide paging trigger MT-SDT to assist in retransmission of MBS, e.g., for an augmented reality user. For example, SDT and MBS sessions may be multiplexed for a UE in an RRC inactive state.

[0088] 9A is a diagram 900 illustrating joint support of MO-SDT and MT-SDT. In some aspects, MO-SDT and MT-SDT may be jointly supported by a UE 902, which may enter an RRC inactive state at 910. In some aspects, prior to initiation of SDT, the UE 902 may signal a capability indication 906 to the network (e.g., by transmitting to a base station 904) indicating the UE's 902 capability for joint support of MO-SDT and MT-SDT. Upon receiving the capability indication 906 indicating the UE's 902 capability for joint support of MO-SDT and MT-SDT, the base station 904 may transmit a configuration 908 to the UE 902, which may include a configuration for MO-SDT and MT-SDT. Although the aspects performed by 904 in FIG. 9A are described for a base station, the aspects may be performed by an aggregated base station or alternatively as a CU, DU, RU, quasi-real-time (quasi-RT) RAN intelligent controller (RIC), or non-real-time (non-RT) RIC in a separated base station architecture. In some aspects, the configuration 908 may be multiplexed with (or may include) an RRC release message with a suspend configuration (e.g., SuspendConfig IE). In some aspects, the configuration 908 may include one or more MT / MO SDT configurations, such as radio resource allocation for DL / UL control and data channels, DL RS resource(s) for timing advance (TA) validation / power control / positioning / QCL / spatial relationship, data volume threshold for MT-SDT / MO-SDT or non-SDT selection, reference signal received power (RSRP) threshold for SDT type selection, SDT / non-SDT selection, beam management, TA validation, etc.

[0089] In some aspects, radio resources for MO-SDT and MT-SDT may be configured in the initial DL BWP or dedicated DL BWP of the UE 902, and may also be configured in the initial UL BWP or dedicated UL BWP, respectively. Since the resources are for MO-SDT and MT-SDT, the UE will have resources configured for both downlink SDT and uplink SDT, e.g., in a pair of BWPs including a downlink BWP and an uplink BWP. For example, for different UE types or capabilities (such as normal or reduced capability) that jointly support MO-SDT and MT-SDT, the initial or dedicated UL BWP configurations may be the same or different. For example, different types of UEs may have a common initial UL BWP or a common dedicated UL BWP. Alternatively, a first type of UE, such as a reduced capability UE, may have a different initial UL BWP than a second type of UE, such as a non-reduced capability UE. Similarly, a first type of UE may have a different dedicated UL BWP than a second type of UE. The initial or dedicated DL BWP configurations may be the same or different for different UE types. In addition, for different UE types or capabilities (such as normal or reduced capability) that jointly support MO-SDT and MT-SDT and share the same initial or dedicated DL / UL BWP, the MO-SDT and MT-SDT configurations may be the same or different. For example, a first type of UE may share the same initial / dedicated DL BWP and the same initial / dedicated UL BWP with a second type of UE, but the two types of UE may have different configurations for MO-SDT and / or MT-SDT.

[0090] To initiate the SDT procedure, the UE 902 may transmit a CCCH message 912 to the base station 904 in an initial MO-SDT transmission while remaining in an RRC inactive state, without transitioning to an RRC connected state. Upon receiving the CCCH message 912, the base station 904 may respond and transmit a response 914 to the UE 902. The response 914 may be an implicit or explicit ACK to the CCCH message 912. In some aspects, the UE-specific SDT on the UL or DL ​​cannot proceed to the RRC inactive state until the UE 902 receives a response 914 (e.g., an ACK (implicit or explicit)) for its initial MO-SDT transmission with the CCCH message 912. In some aspects, the response 914 may be a DCI that schedules a subsequent UL transmission 918 of the UE 902. In some aspects, the response 914 may be a DCI or MAC-CE that triggers the MT-SDT of the UE 902. For example, the network may send the UE MT-SDT while the UE is in an RRC inactive state without the UE transitioning to an RRC connected state. The MT-SDT may be based on an MT-SDT configuration for the UE. In some aspects, at some point, the UE 902 may receive an RRC Release 920 with a suspension configuration (e.g., SuspendConfig IE) that may terminate the SDT. In some aspects, the suspension configuration may provide the UE 902 with information such as RNA updates, paging cycles, etc.

[0091] FIG. 9B is a diagram 950 illustrating communication between a network and a UE with joint support of SDT and MBS while the UE is in an RRC inactive state, according to various aspects of the disclosure. As shown in FIG. 9B, a UE 952 may receive a CG-SDT configuration from a network entity 954 and an MBS configuration 956 from the network entity 954 (e.g., a semi-persistent scheduling (SPS) MBS configuration). In some aspects, the configuration 956 may configure a joint SDT and MBS session. In some aspects, the configuration 956 may be a single RRC message, for example, with one or more aspects configured together for SDT and MBS. In other aspects, the UE may receive a first configuration for CG-SDT (e.g., as described with respect to FIG. 9A) and a second configuration for MBS (e.g., as described with respect to FIG. 10).

[0092] The UE 952 may enter an RRC inactive state, for example, based on a release message, as shown at 958. While in the RRC inactive state, the UE 952 may receive paging 960 from the network entity 954. In some aspects, the paging 960 may be for an SDT or an MBS, such as a paging-based indication for an MT-SDT, a paging for an initial transmission of an MBS, or a paging for a retransmission of an MBS.

[0093] Upon receiving the paging 960, the UE 952 may transmit a first SDT message 962 to the network entity 954. In some aspects, the first SDT message 962 may include an RRC resume request (e.g., represented by an RRCResumeRequest information element). In some aspects, the first SDT message 962 may include an identifier (ID) associated with the UE 952. In some aspects, the first SDT message 962 may include a MAC-CE for the MBS.

[0094] Upon receiving the first SDT message 962, the network entity 954 may respond with a response 964, which may be initial DL data for the UE 952 (e.g., initial DL data associated with paging 960). In some aspects, the response 964 may include DL data or control information scheduled by the C-RNTI or group RNTI of the MBS. The response may include any of the aspects described herein for communications based on joint support of SDT and MBS.

[0095] The subsequent data transmission may occur after the network entity 954 sends a response 964 to the UE 952. For example, the network entity 954 may transmit additional DL data or control information 968 to the UE 952. In some aspects, the DL data or control information 968 may include DL data or control information for the MT-SDT or MBS scheduled by the C-RNTI, P-RNTI, or group RNTI of the MBS. The downlink transmission may include any of the aspects described herein for communications based on joint support of SDT and MBS. The UE 952 may also transmit UL data or control information 970 in response to the DL, which may be HARQ feedback, UE assistance information (UAI), CSI report, MO-SDT, UCI (e.g., SR), MAC CE (e.g., Buffer Status Report (BSR), Power Headroom Report (PHR), etc. for the MT-SDT or MBS. The uplink transmission may include any of the aspects described herein for communication based on joint support of SDT and MBS. The network entity may transmit additional DL data or control information 972 to the UE 952, which may also include DL data or control information for the MT-SDT or MBS scheduled by the C-RNTI, P-RNTI, or group RNTI of the MBS. In some aspects, a suspension configuration (e.g., SuspendConfig An RRC release message 974 with the associated UE 952 release request (IE) may be sent from the network entity 954 to the UE 952. For example, a single RRC release message 974 may terminate the SDT and the MBS.In some aspects, in addition to data or control information associated with the SDT and MBS, DL RS including a paging early indication (PEI), wake up signal (WUS), tracking reference signal (TRS), SSB, or positioning reference signal (PRS), UL RS including a PRACH or SRS may also be transmitted on the DL / UL during a joint SDT and MBS session (e.g., as part of a subsequent transmission). As shown at 976, the UE may continue in an RRC inactive state, and communication between 958 and 976 may occur without the UE transitioning from an RRC inactive state to an RRC connected state. The communication in FIG. 9B may include additional aspects for the SDT as described in connection with FIG. 9A and may include additional aspects for the MBS as described in connection with FIG. 10.

[0096] FIG. 10 is a diagram 1000 illustrating joint support of SDT and MBS. In some aspects, SDT (e.g., MO-SDT or MT-SDT) and MBS (e.g., P2M MBS) may be jointly supported by a UE 1002, which may enter an RRC inactive state at 1010. In some aspects, prior to initiation of SDT and MBS, the UE 1002 may signal a capability indication 1006 to the network (e.g., by transmitting to a base station 1004) indicating the UE's 1002 capability for joint support of SDT and MBS. Although the aspects performed by 1004 in FIG. 10 are described with respect to a base station, the aspects may be performed by an aggregated base station or, alternatively, as a CU, DU, RU, quasi-RT RIC, or non-non-RT RIC in a separated base station architecture. Upon receiving the capability indication 1006 indicating the UE's 1002 capability for joint support of SDT and MBS, the base station 1004 may transmit a configuration 1008 to the UE 1002, which may include a configuration for SDT and MBS. In some aspects, the configuration 1008 may be multiplexed with (or may include) an RRC release message with a suspension configuration (e.g., SuspendConfig IE). In some aspects, the configuration 1008 may be transmitted via an RRC message. In some aspects, the configuration 1008 may include a P2M MBS configuration, which may be provided via an SI or MAC-CE. In some aspects, the configuration 1008 may include one or more MT / MO SDT configurations, such as radio resource allocation for DL / UL control and data channels, DL RS resource(s) for Timing Advance (TA) validation / power control / positioning / QCL / spatial relationship, data volume thresholds for MT-SDT / MO-SDT or non-SDT selection, Reference Signal Received Power (RSRP) thresholds for SDT type selection, SDT / non-SDT selection, beam management, TA validation, etc. In some aspects, for a UE 1002 in an RRC inactive state, the data volume thresholds for MBS or SDT may be the same or different.

[0097] In some aspects, radio resources for SDT and MBS may be configured in the initial or dedicated DL BWP and the initial or dedicated UL BWP of the UE 1002, respectively. For example, for different UE types or capabilities (such as normal or reduced capability) that jointly support SDT and P2M MBS, the radio resource configurations for SDT and P2M MBS may be the same or different. In some aspects, for different UE types or capabilities (such as normal or reduced capability) that share the same initial or dedicated DL / UL BWP, the configurations for the physical control / data channel or physical control / data channel plane and RS on the DL or UL may be the same or different. In some aspects, for a UE 1002 that jointly supports SDT and P2M MBS in an RRC inactive state, the configurations for the physical control / data channel or physical control / data channel plane and RS on the DL / UL may be the same or different. For example, the time domain resource allocation (TDRA), frequency domain resource allocation (FDRA), control resource set (CORESET), CSS, UE specific search space (USS), PUCCH, QCL, or spatial relationship may be the same or different.

[0098] 11A-11C, FIG. 11A, FIG. 11B, and FIG. 11C are diagrams 1100, 1150, and 1170 illustrating example resource configurations of SDT and MBS. As shown in FIG. 11A, the DL / UL BWP of a UE type 1 (or a first capability) associated with both SDT and MBS configuration 1102 may be different from the DL / UL BWP of a UE type 2 (or a second capability) associated with both SDT and MBS configuration 1104. As shown in FIG. 11B, the DL / UL BWP 1152 may be shared by multiple UE types / capabilities. Within the DL / UL BWP 1152, the BWP associated with the SDT and MBS configuration 1154 for the UE type 1 (or a first capability) may be different from the BWP associated with the SDT and MBS configuration 1156 for the UE type 2 (or a second capability). 11C, the DL / UL BWP 1172 may be shared by multiple UE types / capabilities. Within the DL / UL BWP 1172, the BWP associated with the SDT 1174 may be different from the BWP associated with the MBS configuration 1176.

[0099] 10, for a UE 1002 that jointly supports SDT and MBS in an RRC inactive state, the SDT procedure may be initiated by the UE 1002's initial MO-SDT transmission, which includes a CCCH message 1012. In other words, to initiate the SDT procedure, the UE 1002 may transmit a CCCH message 1012 in an initial MO-SDT transmission to the base station 1004. Upon receiving the CCCH message 1012, the base station 1004 may respond and transmit a response 1014 to the UE 1002. The response 1014 may be an implicit or explicit ACK to the CCCH message 1012. In some aspects, UE-specific SDT on the UL or DL ​​cannot proceed to the RRC inactive state until the UE 1002 receives a response 1014 (e.g., an ACK (implicit or explicit)) for its initial MO-SDT transmission with the CCCH message 1012. In some aspects, the response 1014 may be a DCI that schedules a subsequent UL transmission 1018 of the UE 1002. In some aspects, the response 1014 may be a DCI or MAC-CE that triggers an MT-SDT of the UE 1002. In some aspects, the response 1014 may be a PDCCH that schedules a P2M MBS initial transmission or retransmission 1020, or a multicast P2P retransmission may not be used as an implicit ACK for the UE's initial MO-SDT transmission with the CCCH message 1012.

[0100] In some aspects, the UE 1002's reception of the MBS data 1016 may begin before or after the UE 1002 receives the response 1014. In some aspects, the UE 1002's HARQ feedback 1017 for the MBS data 1016 may not be sent if 1) the UE 1002 does not receive the response 1014, 2) the UE 1002 does not have a valid TA, or 3) the UE's TA timer for the SDT has expired.

[0101] In some aspects, at some point, the UE 1002 may receive an RRC Release 1050 with a suspension configuration (e.g., a SuspendConfig IE) that may terminate the SDT. In some aspects, the suspension configuration may provide information to the UE 1002, such as RNA updates, paging cycles, etc.

[0102] In some aspects, for a UE 1002 supporting both SDT and MBS in an RRC inactive state, the UE 1002 may support P2P retransmissions 1020 for multicast within its initial DL BWP configured via a MIB or SIB (e.g., SIB1). In some aspects, in a capability indication 1006 or separate capability indication 1007 representing joint support of SDT and MBS (e.g., P2M initial transmission or retransmission scheduled by a group common DCI (GC-DCI) on a CFR defined in an initial or dedicated DL BWP), the UE 1002 may indicate support for P2P retransmissions of multicast scheduled by a unicast DCI transmitted on a CFR.

[0103] In some aspects, the unicast DCI used by the SDT (MO or MT) and the unicast DCI used by the multicast P2P retransmission may be configured with the same or different CORESET / USS sets. In some aspects, different RNTIs may be used to scramble the CRCs of the unicast DCIs associated with the SDT and the MBS. In some aspects, by default, the GC-DCI associated with the SDT and the GC-DCI that schedules the P2M initial transmission or retransmission of the MBS may be configured with the same or different CORESET or CSS sets. In some aspects, the sizes of the GC-DCIs for the SDT and the MBS may be aligned. In some aspects, different RNTIs may be used to scramble the CRCs of the GC-DCIs associated with the SDT and the MBS. In some aspects, the UCI carrying HARQ feedback in the SDT and the UCI carrying HARQ feedback for multicast P2P retransmissions may be configured with shared or separate PUCCH resources or multiplexed with PUSCH transmissions of the MO-SDT (e.g., including msg3, msg A in a two-step RACH procedure, CG-PUSCH, or subsequent UL data). In some aspects, the HARQ feedback in the SDT and the HARQ feedback for multicast P2P retransmissions may be configured with the same or different priorities by the RRC, DCI, or MAC-CE. In some aspects, DL data associated with multicast and MT-SDT may be assigned different HARQ process IDs.

[0104] 12 is a flowchart 1200 of a method of wireless communication. The method may be performed by a UE (e.g., a UE 104, a UE 902, an apparatus 1802).

[0105] At 1202, the UE may transmit a capability indication to a network entity indicating support of MO-SDT and MT-SDT. For example, the UE 902 may transmit a capability indication 906 indicating support of MO-SDT and MT-SDT to the base station 904. In some aspects, 1202 may be performed by the SDT component 1842 of FIG. 18.

[0106] At 1204, the UE may receive from a network entity one or more configurations for the MO-SDT and the MT-SDT in an RRC message including at least an RRC release message. For example, the UE 902 may receive from the base station 904 one or more configurations 908 for the MO-SDT and the MT-SDT in an RRC message including at least an RRC release message. In some aspects, 1204 may be performed by the SDT component 1842 of FIG. 18.

[0107] The UE may transition to an RRC inactive state at 1206. For example, the UE 902 may transition to an RRC inactive state at 910. In some aspects, 1206 may be performed by the SDT component 1842 of FIG.

[0108] At 1208, the UE may transmit a CCCH message in an MO-SDT transmission to a network entity while in the RRC inactive state. For example, the UE 902 may transmit a CCCH message 912 in an MO-SDT transmission to the base station 904 while remaining in the RRC inactive state. In some aspects, 1208 may be performed by the SDT component 1842 of FIG. 18.

[0109] 13 is a flowchart 1300 of a method of wireless communication. The method may be performed by a UE (e.g., a UE 104, a UE 902, an apparatus 1802).

[0110] At 1302, the UE may transmit a capability indication to a network entity indicating support of MO-SDT and MT-SDT. For example, the UE 902 may transmit a capability indication 906 indicating support of MO-SDT and MT-SDT to the base station 904. In some aspects, 1302 may be performed by the SDT component 1842 of FIG. 18.

[0111] At 1304, the UE may receive from a network entity one or more configurations for the MO-SDT and MT-SDT in an RRC message including at least an RRC release message. For example, the UE 902 may receive from the base station 904 one or more configurations 908 for the MO-SDT and MT-SDT in an RRC message including at least an RRC release message. In some aspects, 1304 may be performed by the SDT component 1842 of FIG. 18. In some aspects, the one or more configurations for the MO-SDT and MT-SDT may include one or more DL RS resources for at least one of one or more RSRP measurements, TA verification, link quality assessment, beam management, power control, positioning, one or more tracking loops, quasi-co-location, or spatial relationships. In some aspects, the one or more configurations for the MO-SDT and MT-SDT may include one or more data volume thresholds for initiation of the MO-SDT and MT-SDT. In some aspects, the one or more configurations for MO-SDT and MT-SDT may include an RSRP threshold associated with selecting MO-SDT, MT-SDT, or non-SDT, beam management, link quality assessment, or TA verification, where the value of the RSRP threshold depends on the type of procedure and one or more UE capabilities associated with the UE. In some aspects, the one or more configurations for MO-SDT and MT-SDT include downlink resources in an initial or dedicated DL BWP for MT-SDT and MO-SDT, and the one or more configurations for MO-SDT and MT-SDT further include uplink resources in an initial or dedicated UL BWP for MO-SDT and MT-SDT. In some aspects, the initial or dedicated DL BWP and the initial or dedicated UL BWP are configured based on a UE type or one or more UE capabilities associated with the UE. In some aspects, the initial or dedicated DL BWP and the initial or dedicated UL BWP are independent of the UE type or UE capabilities.

[0112] The UE may transition to an RRC inactive state at 1306. For example, the UE 902 may transition to an RRC inactive state at 910. In some aspects, 1306 may be performed by the SDT component 1842 of FIG.

[0113] At 1308, the UE may transmit a CCCH message in an MO-SDT transmission to a network entity while in the RRC inactive state. For example, the UE 902 may transmit a CCCH message 912 in an MO-SDT transmission to the base station 904 while in the RRC inactive state. In some aspects, 1308 may be performed by the SDT component 1842 of FIG. 18.

[0114] At 1310, the UE may receive a response to the CCCH message from a network entity. For example, the UE 902 may receive a response 914 to the CCCH message 912 from the base station 904. In some aspects, 1310 may be performed by the SDT component 1842 of FIG. 18. In some aspects, the response is multiplexed with a DCI, an RRC message, or a MAC-CE that triggers an MT-SDT for the UE. In some aspects, the response may include a DCI that schedules a subsequent UL transmission or a CCCH message retransmission of the UE. In some aspects, an RRC release message is associated with a suspension configuration IE. In some aspects, the one or more configurations for the MO-SDT and MT-SDT may include radio resource allocation for DL ​​or UL messages that belong to the control or data plane.

[0115] At 1312, the UE may transmit a subsequent UE-specific SDT transmission based on receiving the response. For example, the UE 902 may transmit a subsequent UE-specific SDT transmission (e.g., a subsequent UL transmission 918) based on receiving the response 914. In some aspects, 1312 may be performed by the SDT component 1842 of FIG. 18.

[0116] 14 is a flowchart 1400 of a method of wireless communication. The method may be performed by a UE (e.g., a UE 104, a UE 1002, an apparatus 1802).

[0117] At 1402, the UE may transmit a capability indication to a network entity indicating support of SDT and P2M MBS. For example, the UE 1002 may transmit a capability indication 1006 to the base station 1004 indicating support of SDT and P2M MBS. In some aspects, 1402 may be performed by the SDT component 1842 of FIG. 18.

[0118] At 1404, the UE may receive from a network entity one or more configurations for the SDT and P2M MBS in an RRC message including at least an RRC release message. For example, the UE 1002 may receive from the base station 1004 one or more configurations 1008 for the SDT and P2M MBS in an RRC message including at least an RRC release message. In some aspects, 1404 may be performed by the SDT component 1842 of FIG. 18.

[0119] The UE may transition to an RRC inactive state at 1406. For example, the UE 1002 may transition to the RRC inactive state at 1010. In some aspects, 1406 may be performed by the SDT component 1842 of FIG.

[0120] At 1408, the UE may transmit a CCCH message over the MO-SDT to a network entity while in the RRC inactive state. For example, the UE 1002 may transmit a CCCH message 1012 in an MO-SDT transmission to the base station 1004 while in the RRC inactive state. In some aspects, 1408 may be performed by the SDT component 1842 of FIG. 18.

[0121] 15 is a flowchart 1500 of a method of wireless communication. The method may be performed by a UE (e.g., a UE 104, a UE 1002, an apparatus 1802).

[0122] At 1502, the UE may transmit a capability indication to a network entity indicating support of SDT and P2M MBS. For example, the UE 1002 may transmit a capability indication 1006 to the base station 1004 indicating support of SDT and P2M MBS. In some aspects, 1502 may be performed by the SDT component 1842 of FIG. 18.

[0123] At 1504, the UE may receive from a network entity one or more configurations for the SDT and P2M MBS in an RRC message including at least an RRC release message. For example, the UE 1002 may receive from the base station 1004 one or more configurations 1008 for the SDT and P2M MBS in an RRC message including at least an RRC release message. In some aspects, 1504 may be performed by the SDT component 1842 of FIG. 18. In some aspects, the one or more configurations for the SDT and P2M MBS are received / sent via an RRC message. In some aspects, the RRC message may include at least an RRC release message associated with a suspension configuration, and the one or more configurations for the SDT and P2M MBS are received / sent via an SI or MAC-CE. In some aspects, the one or more configurations for SDT and P2M include joint resources in an initial or dedicated DL BWP and an initial or dedicated UL BWP for the SDT or P2M MBS, or separate resources for the SDT or P2M MBS in an initial or dedicated DL BWP and an initial or dedicated UL BWP. In some aspects, the joint resources or the initial or dedicated DL BWP or the initial or dedicated UL BWP are partitioned based on a UE type or one or more UE capabilities associated with the UE.

[0124] The UE may transition to an RRC inactive state at 1506. For example, the UE 1002 may transition to the RRC inactive state at 1010. In some aspects, 1506 may be performed by the SDT component 1842 of FIG.

[0125] At 1508, the UE may transmit a CCCH message over the MO-SDT to a network entity while in the RRC inactive state. For example, the UE 1002 may transmit a CCCH message 1012 in an MO-SDT transmission to the base station 1004 while in the RRC inactive state. In some aspects, 1508 may be performed by the SDT component 1842 of FIG. 18.

[0126] At 1510, the UE may receive a response to the CCCH message from a network entity. For example, the UE 1002 may receive a response 1014 to the CCCH message 1012 from the base station 1004. In some aspects, 1510 may be performed by the SDT component 1842 of FIG. 18. In some aspects, the response is multiplexed with a DCI, RRC message, or MAC-CE that triggers an MT-SDT for the UE. In some aspects, the response may include a PDCCH that schedules a P2M MBS transmission, a P2M retransmission, or a P2P retransmission. In some aspects, the response may include a DCI that schedules a subsequent UL transmission or a CCCH message retransmission of the UE. In some aspects, the RRC release message is associated with a suspension configuration IE.I.

[0127] At 1512, the UE may transmit a subsequent UE-specific SDT transmission based on receiving the response. For example, the UE 1002 may transmit a subsequent UE-specific SDT transmission (e.g., a subsequent UL transmission 1018) based on receiving the response 1014. In some aspects, 1512 may be performed by the SDT component 1842 of FIG. 18.

[0128] At 1514, the UE may receive an MBS transmission from a network entity before or after transmitting the CCCH message. For example, the UE 1002 may receive an MBS transmission (e.g., MBS data 1016) from the base station 1004 before or after transmitting the CCCH message 1012. In some aspects, 1514 may be performed by the SDT component 1842 of FIG. 18.

[0129] In some aspects, the UE may transmit HARQ feedback for the MBS transmission to a network entity based on a valid TA, an unexpired TA timer for the SDT, and a response to the CCCH message. For example, the UE 1002 may transmit HARQ feedback (e.g., 1017) for the MBS transmission to the base station 1004 based on a valid TA, an unexpired TA timer for the SDT, and a response to the CCCH message.

[0130] In some aspects, the initial or dedicated DL BWP is configured via a MIB, an RRC message, or a SIB, and the capability indication further indicates support of P2P retransmission for the multicast associated with the P2M MBS. In some aspects, the UL BWP is configured via an RRC message or SIB. In some aspects, the capability indication further indicates support HARQ feedback for P2P or P2M retransmission for the multicast associated with the P2M MBS, and the HARQ feedback is transmitted on common UL resources for a group of UEs including the UE or on dedicated UL resources for the UE. In some aspects, the HARQ feedback for the MBS transmission or retransmission is multiplexed with the HARQ feedback for the MT-SDT transmission or retransmission and other control information on common UL resources or dedicated UL resources. In some aspects, the HARQ feedback for the P2M MBS or MT-SDT is multiplexed with the MO-SDT transmission or retransmission on the same set common UL resources for a group of UEs including the UE or on dedicated UL resources for the UE.

[0131] In some aspects, the UE may skip or prioritize at 1516. For example, the UE may skip transmitting a UL control channel, a UL data channel or UL RS associated with HARQ feedback to an MBS, HARQ feedback to an MT-SDT, an MO-SDT transmission or retransmission, positioning, channel condition feedback based on one or more configured rules, dynamic or semi-persistent priority indications, or UE capabilities associated with the UE. In some aspects, the UE may skip receiving a DL control channel, a DL data channel or DL ​​RS associated with a P2M MBS transmission or retransmission, an MT-SDT transmission or retransmission, HARQ feedback to an MO-SDT transmission, measurements (or other procedures), or positioning based on one or more configured rules, dynamic or semi-persistent priority indications, a UE power saving specification associated with the UE, or UE capabilities associated with the UE. In some aspects, the UE prioritizes reception of DL control channels, DL data channels, or DL ​​RSs associated with P2M MBS, MT-SDT, MO-SDT, positioning, or measurements (or other procedures) or transmission of UL control channels, UL data channels, or UL RSs based on the UE not supporting transmission and reception simultaneously and overlapping or insufficient switching gaps between DL and UL, where the prioritization may be further based on one or more configured rules, dynamic or semi-persistent priority indications, UE power saving specifications associated with the UE, UE capabilities associated with the UE, etc. For example, if the UE supports half-duplex FDD without supporting full-duplex, the UE cannot transmit and receive simultaneously. Thus, the UE can prioritize DL reception and skip UL transmission, or vice versa. In some aspects, if there is overlap between UL resources associated with HARQ feedback to MBS, HARQ feedback to MT-SDT, and MO-SDT transmission / retransmission, the UE can drop some of them based on priority or UE capabilities.

[0132] 16 is a flowchart 1600 of a method of wireless communication. The method may be performed by a network device (e.g., base station 102 / 180, base station 904, apparatus 1902). In some aspects, the method may be performed by a base station (e.g., an aggregated base station) or, alternatively, by a CU, DU, RU, quasi-real-time (quasi-RT) RAN Intelligent Controller (RIC), or non-real-time (non-RT) RIC in a separated base station architecture.

[0133] At 1602, the network device may receive a capability indication from the UE indicating support of MO-SDT and MT-SDT. For example, the base station 904 may receive a capability indication 906 from the UE 902 indicating support of MO-SDT and MT-SDT. In some aspects, 1602 may be performed by the SDT component 1942 of FIG. 19.

[0134] At 1604, the network device may transmit to the UE one or more configurations for the MO-SDT and MT-SDT in an RRC message including at least an RRC release message. For example, the base station 904 may transmit to the UE 902 one or more configurations 908 for the MO-SDT and MT-SDT in an RRC message including at least an RRC release message. In some aspects, 1604 may be performed by the SDT component 1942 of FIG. 19. In some aspects, the one or more configurations for the MO-SDT and MT-SDT may include one or more DL RS resources for at least one of one or more RSRP measurements, TA verification, link quality assessment, beam management, power control, positioning, one or more tracking loops, quasi-co-location, or spatial relationships. In some aspects, the one or more configurations for the MO-SDT and MT-SDT may include one or more data volume thresholds for initiation of the MO-SDT and MT-SDT. In some aspects, the one or more configurations for MO-SDT and MT-SDT may include an RSRP threshold associated with selecting MO-SDT, MT-SDT, or non-SDT, beam management, link quality assessment, or TA verification, where the value of the RSRP threshold depends on the type of procedure and one or more UE capabilities associated with the UE. In some aspects, the one or more configurations for MO-SDT and MT-SDT include downlink resources in an initial or dedicated DL BWP for MT-SDT and MO-SDT, and the one or more configurations for MO-SDT and MT-SDT further include uplink resources in an initial or dedicated UL BWP for MO-SDT and MT-SDT. In some aspects, the initial or dedicated DL BWP and the initial or dedicated UL BWP are configured based on a UE type or one or more UE capabilities associated with the UE. In some aspects, the initial or dedicated DL BWP and the initial or dedicated UL BWP are independent of the UE type or UE capabilities.

[0135] The UE may transition to an RRC inactive state at 1606. For example, the UE 902 may transition to an RRC inactive state at 910. In some aspects, 1606 may be performed by the SDT component 1942 of FIG.

[0136] At 1608, the network device may receive a CCCH message in an MO-SDT transmission from the UE while in the RRC inactive state. For example, the base station 904 may receive a CCCH message 912 in an MO-SDT transmission from the UE 902 while in the RRC inactive state. In some aspects, 1608 may be performed by the SDT component 1942 of FIG. 19.

[0137] At 1610, the network device may transmit a response to the CCCH message to the UE. For example, the base station 904 may transmit a response 914 to the CCCH message 912 to the UE 902. In some aspects, 1610 may be performed by the SDT component 1942 of FIG. 19. In some aspects, the response is multiplexed with a DCI, an RRC message, or a MAC-CE that triggers an MT-SDT for the UE. In some aspects, the response may include a DCI that schedules a subsequent UL transmission or a CCCH message retransmission of the UE. In some aspects, an RRC release message is associated with a suspension configuration IE. In some aspects, the one or more configurations for the MO-SDT and MT-SDT may include radio resource allocation for DL ​​or UL messages that belong to the control or data plane.

[0138] At 1612, the network device may receive a subsequent UE-specific SDT transmission based on receiving the response. For example, the base station 904 may receive a subsequent UE-specific SDT transmission (e.g., a subsequent UL transmission 918) based on the response 914. In some aspects, 1612 may be performed by the SDT component 1942 of FIG. 19.

[0139] 17 is a flowchart 1700 of a method of wireless communication. The method may be performed by a UE (e.g., a UE 104, a UE 1002, an apparatus 1802).

[0140] At 1702, the network device may receive a capability indication from the UE indicating support of SDT and P2M MBS. For example, the base station 1004 may receive a capability indication 1006 from the UE 1002 indicating support of SDT and P2M MBS. In some aspects, 1702 may be performed by the SDT component 1842 of FIG. 18.

[0141] At 1704, the network device may transmit to the UE one or more configurations for the SDT and P2M MBS in an RRC message including at least an RRC release message. For example, the base station 1004 may transmit to the UE 1002 one or more configurations 1008 for the SDT and P2M MBS in an RRC message including at least an RRC release message. In some aspects, 1704 may be performed by the SDT component 1842 of FIG. 18. In some aspects, the one or more configurations for the SDT and P2M MBS are received / transmitted via an RRC message. In some aspects, the RRC message may include at least an RRC release message associated with a suspension configuration, and the one or more configurations for the SDT and P2M MBS are received / transmitted via an SI or MAC-CE. In some aspects, the one or more configurations for SDT and P2M include joint resources in an initial or dedicated DL BWP and an initial or dedicated UL BWP for the SDT or P2M MBS, or separate resources for the SDT or P2M MBS in an initial or dedicated DL BWP and an initial or dedicated UL BWP. In some aspects, the joint resources or the initial or dedicated DL BWP or the initial or dedicated UL BWP are partitioned based on a UE type or one or more UE capabilities associated with the UE.

[0142] At 1708, the network device may receive a CCCH message over the MO-SDT from the UE while in the RRC inactive state. For example, the base station 1004 may receive a CCCH message 1012 in an MO-SDT transmission from the UE 1002 while in the RRC inactive state. In some aspects, 1708 may be performed by the SDT component 1842 of FIG. 18.

[0143] At 1710, the network device may transmit a response to the CCCH message to the UE. For example, the base station 1004 may transmit a response 1014 to the CCCH message 1012 to the UE 1002. In some aspects, 1710 may be performed by the SDT component 1842 of FIG. 18. In some aspects, the response is multiplexed with a DCI, RRC message, or MAC-CE that triggers an MT-SDT for the UE. In some aspects, the response may include a PDCCH that schedules a P2M MBS transmission, a P2M retransmission, or a P2P retransmission. In some aspects, the response may include a DCI that schedules a subsequent UL transmission or a CCCH message retransmission of the UE. In some aspects, the RRC release message is associated with a suspension configuration IE.I.

[0144] At 1712, the base station may receive a subsequent UE-specific SDT transmission based on receiving the response. For example, the base station 1004 may receive a subsequent UE-specific SDT transmission (e.g., a subsequent UL transmission 1018). In some aspects, 1712 may be performed by the SDT component 1842 of FIG. 18.

[0145] At 1714, the network device may send an MBS transmission to the UE before or after sending the CCCH message. For example, the base station 1004 may send an MBS transmission (e.g., MBS data 1016) to the UE 1002 before or after receiving the CCCH message 1012. In some aspects, 1714 may be performed by the SDT component 1842 of FIG. 18.

[0146] In some aspects, a network device may receive HARQ feedback for an MBS transmission from a UE based on a valid TA, an unexpired TA timer for the SDT, and a response to the CCCH message. For example, a base station 1004 may receive HARQ feedback (e.g., 1017) for an MBS transmission from a UE 1002 based on a valid TA, an unexpired TA timer for the SDT, and a response to the CCCH message.

[0147] In some aspects, the initial or dedicated DL BWP is configured via a MIB, an RRC message, or a SIB, and the capability indication further indicates support of P2P retransmission for the multicast associated with the P2M MBS. In some aspects, the UL BWP is configured via an RRC message or SIB. In some aspects, the capability indication further indicates support HARQ feedback for P2P or P2M retransmission for the multicast associated with the P2M MBS, and the HARQ feedback is transmitted on common UL resources for a group of UEs including the UE or on dedicated UL resources for the UE. In some aspects, the HARQ feedback for the MBS transmission or retransmission is multiplexed with the HARQ feedback for the MT-SDT transmission or retransmission and other control information on common UL resources or dedicated UL resources. In some aspects, the HARQ feedback for the P2M MBS or MT-SDT is multiplexed with the MO-SDT transmission or retransmission on the same set common UL resources for a group of UEs including the UE or on dedicated UL resources for the UE.

[0148] 18 is a diagram 1800 illustrating an example of a hardware implementation for a device 1802. The device 1802 may be a UE, a component of a UE, or may perform UE functions. In some aspects, the device 1802 may include a cellular baseband processor 1804 (also referred to as a modem) coupled to a cellular RF transceiver 1822. In some aspects, the device 1802 may further include one or more subscriber identity module (SIM) cards 1820, an application processor 1806 coupled to a secure digital (SD) card 1808 and a screen 1810, a Bluetooth module 1812, a wireless local area network (WLAN) module 1814, a Global Positioning System (GPS) module 1816, or a power source 1818. The cellular baseband processor 1804 communicates with the UE 104 and / or the BS 102 / 180 through the cellular RF transceiver 1822. The cellular baseband processor 1804 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1804 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1804, causes the cellular baseband processor 1804 to perform various functions as described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1804 when executing the software. The cellular baseband processor 1804 further includes a receiving component 1830, a communications manager 1832, and a transmitting component 1834. The communications manager 1832 includes one or more of the illustrated components. The components within the communications manager 1832 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1804.The cellular baseband processor 1804 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1802 may be a modem chip and may include only the baseband processor 1804, while in another configuration, the apparatus 1802 may be an entire UE (e.g., see 350 in FIG. 3) and may include additional modules of the apparatus 1802.

[0149] The communications manager 1832 includes an SDT component 1842 that may be configured to send a capability indication indicating support of the MO-SDT and MT-SDT to a network entity, e.g., as described with respect to 1202 of FIG. 12 and 1302 of FIG. 13. In some aspects, the SDT component 1842 may be configured to receive one or more configurations for the MO-SDT and MT-SDT in an RRC message including at least an RRC release message from a network entity, e.g., as described with respect to 1204 of FIG. 12 and 1304 of FIG. 13. In some aspects, the SDT component 1842 may be configured to transition to an RRC inactive state, e.g., as described with respect to 1206 of FIG. 12 and 1306 of FIG. 13. In some aspects, the SDT component 1842 may be configured to transmit a CCCH message in an MO-SDT transmission to a network entity while in an RRC inactive state, e.g., as described with respect to 1208 of FIG. 12 and 1308 of FIG. 13. In some aspects, the SDT component 1842 may be configured to receive a response to the CCCH message from the network entity, e.g., as described with respect to 1310 of FIG. 13. In some aspects, the SDT component 1842 may be configured to transmit a subsequent UE-specific SDT transmission based on receiving the response, e.g., as described with respect to 1312 of FIG. 13.

[0150] In some aspects, the SDT component 1842 may be configured to send a capability indication indicating support of SDT and P2M MBS to a network entity, e.g., as described with respect to 1502 of FIG. 15 and 1402 of FIG. 14. In some aspects, the SDT component 1842 may be configured to receive one or more configurations for SDT and P2M MBS from a network entity, e.g., as described with respect to 1504 of FIG. 15 and 1404 of FIG. 14. In some aspects, the SDT component 1842 may be configured to transition to an RRC inactive state, e.g., as described with respect to 1506 of FIG. 15 and 1406 of FIG. 14. In some aspects, the SDT component 1842 may be configured to send a CCCH message over the MO-SDT to a network entity while in the RRC inactive state, e.g., as described with respect to 1508 of FIG. 15 and 1408 of FIG. 14. In some aspects, the SDT component 1842 may be configured to receive a response to the CCCH message from a network entity, e.g., as described with respect to 1510 of FIG. 15. In some aspects, the SDT component 1842 may be configured to transmit a subsequent UE-specific SDT transmission or retransmit the CCCH message based on receiving the response, e.g., as described with respect to 1512 of FIG. 15. In some aspects, the SDT component 1842 may be configured to receive an MBS transmission from a network entity and transmit a HARQ before or after transmitting a CCCH message, e.g., as described with respect to 1514 of FIG. 15. In some aspects, the SDT component 1842 may be configured to skip or prioritize, e.g., as described with respect to 1516 in FIG. 15.

[0151] The apparatus may include additional components that perform each of the blocks of the algorithms in the flowcharts of Figures 12-15. Thus, each block in the flowcharts of Figures 12-15 may be performed by a component, and the apparatus may include one or more of those components. Those components may be one or more hardware components specifically configured to perform the described process / algorithm, executed by a processor configured to perform the described process / algorithm, stored in a computer-readable medium for implementation by the processor, or some combination thereof.

[0152] As shown, the apparatus 1802 may include various components configured for various functions. In one configuration, the apparatus 1802, particularly the cellular baseband processor 1804, includes means for transmitting a capability indication indicating support of MO-SDT and MT-SDT to a base station. The cellular baseband processor 1804 may further include means for receiving one or more configurations for MO-SDT and MT-SDT in an RRC message from the base station, the RRC message including at least an RRC release message. The cellular baseband processor 1804 may further include means for transitioning to an RRC inactive state. The cellular baseband processor 1804 may further include means for transmitting a CCCH message in an MO-SDT transmission to the base station while in the RRC inactive state. The cellular baseband processor 1804 may further include means for receiving a response to the CCCH message from the base station. The cellular baseband processor 1804 may further include means for transmitting a subsequent UE-specific SDT transmission based on receiving the response. The cellular baseband processor 1804 may further include means for transmitting a capability indication indicating support of SDT and P2M MBS to the base station. The cellular baseband processor 1804 may further include means for receiving one or more configurations for SDT and P2M MBS from the base station. The cellular baseband processor 1804 may further include means for transitioning to an RRC inactive state. The cellular baseband processor 1804 may further include means for transmitting a CCCH message over the MO-SDT to the base station while in the RRC inactive state. The cellular baseband processor 1804 may further include means for receiving a response to the CCCH message from the base station. The cellular baseband processor 1804 may further include means for transmitting a subsequent UE-specific SDT transmission or retransmitting the CCCH message based on receiving the response. The cellular baseband processor 1804 may further include means for receiving an MBS transmission from the base station before or after transmitting the CCCH message and means for transmitting a HARQ.The cellular baseband processor 1804 may further include a means for skipping or prioritizing. This means may be one or more of the components of the device 1802 configured to perform the recited functions by the means. As described above, the device 1802 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, this means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the recited functions by the means.

[0153] FIG. 19 is a diagram 1900 illustrating an example of a hardware implementation for an apparatus 1902. The apparatus 1902 may be a base station, a component of a base station, or may perform base station functions. In some aspects, the apparatus may be an aggregated base station), or alternatively, a CU, DU, RU, quasi-RT RIC, or non-RT RIC in a separated base station architecture. In some aspects, the apparatus 1802 may include a baseband unit 1904. The baseband unit 1904 may communicate with the UE 104 via a cellular RF transceiver 1922. The baseband unit 1904 may include a computer-readable medium / memory. The baseband unit 1904 is responsible for overall processing, including execution of software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 1904, causes the baseband unit 1904 to perform various functions described above. The computer readable medium / memory may also be used to store data manipulated by the baseband unit 1904 when executing software. The baseband unit 1904 further includes a receiving component 1930, a communications manager 1932, and a transmitting component 1934. The communications manager 1932 includes one or more of the illustrated components. The components in the communications manager 1932 may be stored in the computer readable medium / memory and / or may be configured as hardware in the baseband unit 1904. The baseband unit 1904 may be a component of the base station 310 and may include the memory 376 and / or at least one of the TX processor 316, the RX processor 370, and the controller / processor 375.

[0154] The communications manager 1932 includes an SDT component 1942, which may receive a capability indication indicating support of MO-SDT and MT-SDT from the UE, e.g., as described with respect to 1602 of FIG. 16. The SDT component 1942 may also transmit one or more configurations for MO-SDT and MT-SDT in an RRC message including at least an RRC release message to the UE, e.g., as described with respect to 1604 of FIG. 16. The SDT component 1942 may also receive a CCCH message in an MO-SDT transmission from the UE while in an RRC inactive state, e.g., as described with respect to 1608 of FIG. 16. The SDT component 1942 may also transmit a response to the CCCH message to the UE, e.g., as described with respect to 1610 of FIG. 16. The SDT component 1942 may also receive a subsequent UE-specific SDT transmission based on receiving the response, e.g., as described with respect to 1612 of FIG. 16. The SDT component 1942 may receive a capability indication indicating support of SDT and P2M MBS from the UE, e.g., as described in connection with 1702 of FIG. 17. The SDT component 1942 may send one or more configurations for SDT and P2M MBS to the UE, e.g., as described in connection with 1704 of FIG. 17. The SDT component 1942 may receive a CCCH message from the UE over the MO-SDT while in the RRC inactive state, e.g., as described in connection with 1708 of FIG. 17. The SDT component 1942 may send a response to the CCCH message to the UE, e.g., as described in connection with 1710 of FIG. 17. The SDT component 1942 may receive a subsequent UE-specific SDT transmission or retransmit the CCCH message based on receiving the response, e.g., as described in connection with 1712 of FIG. 17. The SDT component 1942 may send an MBS transmission to the UE, for example, before or after receiving the CCCH message, as described in connection with 1714 of FIG.

[0155] The apparatus may include additional components that perform each of the blocks of the algorithms in the flowcharts of Figures 16 and 17. Thus, each block in the flowcharts of Figures 16 and 17 may be performed by a component, and the apparatus may include one or more of those components. Those components may be one or more hardware components specifically configured to perform the described process / algorithm, executed by a processor configured to perform the described process / algorithm, stored in a computer-readable medium for implementation by the processor, or some combination thereof.

[0156] As shown, the apparatus 1902 may include various components configured for various functions. In one configuration, the apparatus 1902, particularly the baseband unit 1904, includes means for receiving a capability indication from the UE indicative of support of MO-SDT and MT-SDT. The baseband unit 1904 may further include means for transmitting one or more configurations for MO-SDT and MT-SDT in an RRC message including at least an RRC release message to the UE. The baseband unit 1904 may further include means for receiving a CCCH message in an MO-SDT transmission from the UE while in an RRC inactive state. The baseband unit 1904 may further include means for transmitting a response to the CCCH message to the base station. The baseband unit 1904 may further include means for receiving a subsequent UE-specific SDT transmission based on receiving the response. The baseband unit 1904 may further include means for receiving a capability indication from the UE indicative of support of SDT and P2M MBS. The baseband unit 1904 may further include means for transmitting one or more configurations for SDT and P2M MBS to the UE. The baseband unit 1904 may further include means for receiving a CCCH message from the UE over the MO-SDT while in the RRC inactive state. The baseband unit 1904 may further include means for transmitting a response to the CCCH message to the UE. The baseband unit 1904 may further include means for receiving a subsequent UE-specific SDT transmission or retransmitting the CCCH message based on receiving the response. The baseband unit 1904 may further include means for transmitting an MBS transmission to the UE before or after receiving the CCCH message. The means may be one or more of the components of the apparatus 1902 configured to perform the recited functions by the means. As described above, the apparatus 1902 may include the TX processor 316, the RX processor 370, and the controller / processor 375.Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and the controller / processor 375, configured to perform the recited functions by the means.

[0157] The deployment of communication systems, such as 5G New Radio (NR) systems, can be configured in multiple ways using various components or parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of the network, a radio access network (RAN) node, a core network node, a network element, or a network equipment such as a base station (BS), or one or more units (or one or more components) performing a base station function, can be implemented in an aggregated or separated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or a separated base station.

[0158] 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 separated 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 centralized units (CUs), one or more distributed units (DUs), or one or more radio units (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).

[0159] The operation of a base station type or network design may take into account the aggregated nature of the base station functions. For example, a separated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration supported by the O-RAN alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network, C-RAN). Disaggregation may include distributing functions across two or more units in different physical locations, as well as distributing functions virtually for at least one unit, which may allow flexibility in network design. Various units of a separated base station, or a separated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0160] FIG. 20 illustrates a diagram illustrating an architecture of an exemplary separated base station 2000. The separated base station 2000 architecture may include one or more central units (CUs) 2010 that may communicate directly with the core network 2020 via a backhaul link or indirectly with the core network 2020 via one or more separated base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 2025 via an E2 link, or a non-real-time (non-RT) RIC 2015 associated with a Service Management and Orchestration (SMO) framework 2005, or both). The CU 2010 may communicate with one or more distributed units (DUs) 2030 via respective midhaul links, such as an F1 interface. The DU 2030 may communicate with one or more radio units (RUs) 2040 via respective fronthaul links. The RUs 2040 may communicate with each UE 2220 via one or more radio frequency (RF) access links. In some implementations, a UE 2220 may be served by multiple RUs 2040 simultaneously.

[0161] Each of the units, i.e., CU2010, DU2030, RU2040, as well as quasi-RT RIC2025, non-RT RIC2015, and SMO framework2005, 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, the units may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Furthermore, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit or transmit signals over a wireless transmission medium to one or more of the other units.

[0162] In some aspects, the CU 2010 may host one or more upper layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), and the like. Each control function may execute with an interface configured to communicate signals with other control functions hosted by the CU 2010. The CU 2010 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 2010 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units, when implemented in an O-RAN configuration, may communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface. The CU 2010 may be implemented to communicate with the DU 2030, as needed, for network control and signaling.

[0163] The DU 2030 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 2040. In some aspects, the DU 2030 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), at least in part according to a functional division such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 2030 may further host one or more lower PHY layers. Each layer (or module) may execute with an interface configured to communicate signals with other layers (and modules) hosted by the DU 2030 or with a control function hosted by the CU 2010.

[0164] The lower layer functions may be performed by one or more RUs 2040. In some deployments, the RUs 2040 controlled by the DU 2030 may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division such as a lower layer functional division. In such an architecture, the RU(s) 2040 may be implemented to handle over the air (OTA) communications with one or more UEs 2220. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 2040 may be controlled by the corresponding DU 2030. In some scenarios, this configuration may enable the DU(s) 2030 and the CU 2010 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0165] The SMO framework 2005 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 2005 may be configured to support deployment of dedicated physical resources for RAN coverage requirements that can be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 2005 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 2090) to perform network element lifecycle management (such as instantiating 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 2010, the DU 2030, the RU 2040, and the quasi-RT RIC 2025. In some implementations, the SMO framework 2005 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 2011, via an O1 interface. Additionally, in some implementations, the SMO framework 2005 can communicate directly with one or more RUs 2040 via an O1 interface. The SMO framework 2005 can also include a non-RT RIC 2015 configured to support the functionality of the SMO framework 2005.

[0166] The non-RT RIC 2015 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 2025. The non-RT RIC 2015 may be coupled to or in communication with the quasi-RT RIC 2025 (e.g., via an A1 interface). The quasi-RT RIC 2025 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources via data collection and action via one or more CUs 2010, one or more DUs 2030, or both, and interfaces connecting the O-eNB to the quasi-RT RIC 2025 (e.g., via an E2 interface).

[0167] In some implementations, the non-RT RIC 2015 may receive parameters or external enrichment information from an external server to generate the AI / ML models deployed to the quasi-RT RIC 2025. Such information may be utilized by the quasi-RT RIC 2025 and may be received from non-network data sources or from network functions in the SMO framework 2005 or the non-RT RIC 2015. In some examples, the non-RT RIC 2015 or the quasi-RT RIC 2025 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 2015 may employ the AI / ML models to monitor long-term trends and patterns in performance and take corrective action through the SMO framework 2005 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0168] It should be understood that the particular order or hierarchy of the blocks in the disclosed processes / flow charts is an example of an example approach. It should be understood that the particular order or hierarchy of the blocks in those processes / flow charts can be rearranged based on design preferences. Further, some blocks can be combined or omitted. The accompanying method claims present elements of the various blocks in an example order, and are not meant to be limited to the particular order or hierarchy presented.

[0169] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects set forth herein, but are to be accorded the widest scope consistent with the language of the claims, and references to elements in the singular shall mean "one or more" and not "one and only", unless otherwise expressly stated. Terms such as "if", "when", and "while" should be construed to mean "under the condition that", rather than implying an immediate temporal relationship or reaction. That is, these phrases, such as "when", do not imply immediate action in response to or during the occurrence of an action, but simply mean that an action will occur if a condition is met, but do not require a specific or immediate temporal constraint for the action to occur. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other aspects. Unless expressly stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple As, multiple Bs, or multiple Cs.Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, and any such combinations can include one or more elements of A, B, or C. A set should be interpreted as a set of elements, the number of elements being one or more. Thus, for a set of X, X will include one or more elements. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later become known to those of skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly recited in the claims. Words such as "module," "mechanism," "element," "device," and the like may not be substitutes for the word "means." Thus, no element of a claim should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for."

[0170] The following aspects are exemplary only and can be combined with other aspects or teachings described herein without limitation.

[0171] Aspect 1 is a method for communication in a user equipment (UE), the method including: transmitting a capability indication indicating support of mobile originated small data transmission (MO-SDT) and mobile terminated small data transmission (MT-SDT) to a base station; receiving one or more configurations for MO-SDT and MT-SDT in a radio resource control (RRC) message from the base station, the RRC message including at least an RRC release message; transitioning to an RRC inactive state; and transmitting a common control channel (CCCH) message in the MO-SDT transmission to the base station while in the RRC inactive state.

[0172] Example 2 is the method of example 1, further comprising receiving a response to the CCCH message from the base station.

[0173] Example 3 is the method of example 1 or 2, further comprising transmitting a subsequent UE-specific SDT transmission based on receiving the response.

[0174] Example 4 is any of the methods of Examples 1-3, wherein the response is multiplexed with a downlink control information (DCI), an RRC message, or a medium access control (MAC) control element (MAC-CE) that triggers MT-SDT for the UE.

[0175] Example 5 is the method of any of Examples 1-4, wherein the response includes downlink control information (DCI) that schedules a subsequent uplink (UL) transmission or CCCH message retransmission of the UE.

[0176] Example 6 is any of the methods of Examples 1-5, wherein the RRC release message is associated with a suspension configuration information element (IE).

[0177] Example 7 is any of the methods of Examples 1 to 6, wherein the one or more configurations for the MO-SDT and MT-SDT include radio resource allocation for downlink (DL) messages or uplink (UL) messages belonging to a control plane or a data plane.

[0178] Example 8 is the method of any of Examples 1-7, wherein the one or more configurations for the MO-SDT and MT-SDT include one or more downlink reference signal (DL RS) resources for at least one of one or more reference signal received power (RSRP) measurements, timing advance (TA) verification, link quality assessment, beam management, power control, positioning, one or more tracking loops, quasi-colocation, or spatial relationships.

[0179] Example 9 is the method of any of Examples 1-8, wherein the one or more configurations for the MO-SDT and the MT-SDT include one or more data volume thresholds for initiation of the MO-SDT and the MT-SDT.

[0180] Example 10 is the method of any of Examples 1-9, wherein the one or more configurations for MO-SDT and MT-SDT include a Reference Signal Received Power (RSRP) threshold associated with selecting MO-SDT, MT-SDT, or non-SDT, beam management, link quality assessment, or timing advance (TA) verification, and the value of the RSRP threshold depends on a type of procedure and one or more UE capabilities associated with the UE.

[0181] Example 11 is the method of any of Examples 1-10, wherein the one or more configurations for the MO-SDT and the MT-SDT include downlink resources in an initial or dedicated downlink (DL) bandwidth portion (BWP) for the MT-SDT and the MO-SDT, and the one or more configurations for the MO-SDT and the MT-SDT further include uplink resources in an initial or dedicated uplink (UL) BWP for the MO-SDT and the MT-SDT.

[0182] Example 12 is the method of any of Examples 1-11, wherein the initial or dedicated DL BWP and the initial or dedicated UL BWP are configured based on a UE type or one or more UE capabilities associated with the UE.

[0183] Example 13 is the method of any of Examples 1 to 12, wherein the initial or dedicated DL BWP and the initial or dedicated UL BWP are independent of UE type or UE capability.

[0184] Aspect 14 is a method for communication in a user equipment (UE), the method including: sending a capability indication to a base station indicating support of small data transmission (SDT) and point-to-multipoint (P2M) multicast and broadcast services (MBS); receiving one or more configurations for SDT and P2M MBS from the base station; transitioning to a radio resource control (RRC) inactive state; and sending a common control channel (CCCH) message over a mobile originated SDT (MO-SDT) to the base station while in the RRC inactive state.

[0185] Example 15 is the method of example 14, wherein the one or more configurations for the SDT and P2M MBS are received via an RRC message including at least an RRC release message associated with the suspension configuration, and the one or more configurations for the SDT and P2M MBS are received via system information (SI) or a medium access control (MAC) control element (MAC-CE).

[0186] Example 16 is the method of example 14 or 15, wherein the one or more configurations for the SDT and P2M include joint resources in an initial or dedicated downlink (DL) bandwidth portion (BWP) and an initial or dedicated uplink (UL) BWP for the SDT or P2M MBS, or separate resources for the SDT or P2M MBS in an initial or dedicated DL BWP and an initial or dedicated UL BWP.

[0187] Example 17 is the method of any of Examples 14-16, wherein the joint resources, or the initial or dedicated DL BWP or the initial or dedicated UL BWP, are partitioned based on a UE type or one or more UE capabilities associated with the UE.

[0188] Example 18 is the method of any of Examples 14 to 17, further comprising receiving, from the base station, a response to the CCCH message.

[0189] Example 19 is the method of any of Examples 14-18, further comprising transmitting a subsequent UE-specific SDT transmission or retransmitting the CCCH message based on receiving the response, wherein the response is multiplexed with a downlink control information (DCI), an RRC message, or a medium access control (MAC) control element (MAC-CE) that triggers a mobile terminated small data transmission (MT-SDT) of the UE.

[0190] Example 20 is the method of any of Examples 14-19, wherein the response includes downlink control information (DCI) that schedules a subsequent uplink (UL) transmission or CCCH message retransmission of the UE, or includes a physical downlink control channel (PDCCH) that schedules a P2M MBS transmission, a P2M retransmission, or a peer-to-peer (P2P retransmission).

[0191] Example 21 is the method of any of Examples 14 to 20, further comprising receiving an MBS transmission from the base station before or after transmitting the CCCH message.

[0192] Example 22 is the method of any of Examples 14 to 21, further including transmitting, to the base station, hybrid automatic repeat request (HARQ) feedback for the MBS transmission based on a valid timing advance (TA), an unexpired TA timer for the SDT, and a response to the CCCH message.

[0193] Example 23 is any of the methods of Examples 14 to 22, wherein the initial or dedicated downlink (DL) bandwidth portion (BWP) is configured via a master information block (MIB), an RRC message, or a system information block (SIB), and the capability indication further indicates support for peer-to-peer (P2P) retransmission for multicast associated with the P2M MBS.

[0194] Example 24 is the method of any of Examples 14-23, wherein the uplink (UL) bandwidth portion (BWP) is configured via an RRC message or a system information block (SIB), and the capability indication further indicates support of hybrid automatic repeat request (HARQ) feedback to peer-to-peer (P2P) or P2M retransmissions for multicast associated with the P2M MBS, and the HARQ feedback is transmitted on common UL resources for a group of UEs including the UE or on dedicated UL resources for the UE.

[0195] Example 25 is any of the methods of Examples 14 to 24, wherein hybrid automatic repeat request (HARQ) feedback to the MBS transmission or MBS retransmission is multiplexed with HARQ feedback to the MT-SDT transmission or MT-SDT retransmission and other control information on common UL resources or dedicated UL resources.

[0196] Example 26 is the method of any of Examples 14 to 25, wherein hybrid automatic repeat request (HARQ) feedback to the P2M MBS or mobile terminated SDT (MT-SDT) is multiplexed with the MO-SDT transmission or retransmission on the same set common UL resources for a group of UEs including the UE or on dedicated UL resources for the UE.

[0197] Aspect 27 includes skipping transmission of at least one of a UL control channel, a UL data channel, a UL RS associated with a first hybrid automatic repeat request (HARQ) feedback to a P2M MBS, a second HARQ feedback to an MT-SDT transmission, a MT-SDT retransmission, an MO-SDT transmission, an MO-SDT retransmission, or positioning or channel condition feedback based on at least one of one or more configured rules, dynamic or semi-persistent priority indications, or UE capabilities associated with the UE, or skipping transmission of a downlink (DL) control channel, a DL data channel associated with a P2M MBS transmission or a P2M MBS retransmission, or a DL data channel associated with a DL control channel, ... 27. The method of any of aspects 14 to 26, further comprising skipping reception of at least one of the RS, an MT-SDT transmission or an MT-SDT retransmission, a third HARQ feedback to the MO-SDT transmission, or measurement or positioning.

[0198] Example 28 is the method of any of Examples 14-27, further including prioritizing reception of a downlink (DL) control channel, DL data channel, or DL ​​reference signal (RS) associated with a P2M MBS, a mobile terminated SDT (MT-SDT), a MO-SDT, positioning, or measurement, or transmission of an uplink (UL) control channel, UL data channel, or UL RS, based on the UE not supporting simultaneous transmission and reception and an overlapping or insufficient switching gap between the DL and UL, where the prioritization is further based on one or more configured rules, dynamic or semi-persistent priority indications, a UE power save specification associated with the UE, or a UE capability associated with the UE.

[0199] Example 29 is a communication apparatus comprising a memory containing instructions and at least one processor coupled to the memory, the at least one processor configured to execute the instructions and cause the apparatus to perform a method according to any of Examples 1 to 13.

[0200] Aspect 30 is an apparatus for communication, comprising means for performing the method according to any one of aspects 1-13.

[0201] Aspect 31 is a computer-readable medium storing computer-executable code, which when executed by a processor causes the processor to perform a method according to any of aspects 1-13.

[0202] Example 32 is a communication apparatus comprising a memory containing instructions and at least one processor coupled to the memory, the at least one processor configured to execute the instructions and cause the apparatus to perform a method according to any of examples 14 to 28.

[0203] Aspect 33 is an apparatus for communication, comprising means for executing the method according to any one of aspects 14 to 28.

[0204] Aspect 34 is a computer-readable medium storing computer-executable code, which, when executed by a processor, causes the processor to perform a method according to any of aspects 14-28.

Claims

1. An apparatus for communication in a user equipment (UE), comprising: Memory, at least one processor coupled to the memory; wherein the at least one processor: Sending a capability indication to a network entity indicating support of Mobile Originated Small Data Transmission (MO-SDT) and Mobile Terminated Small Data Transmission (MT-SDT); receiving, from the network entity, one or more configurations for the MO-SDT and the MT-SDT in a Radio Resource Control (RRC) message including at least an RRC release message; Transition to RRC inactive state, The apparatus is configured to transmit a Common Control Channel (CCCH) message to the network entity in a MO-SDT transmission while in the RRC inactive state.

2. the at least one processor coupled to the memory; The apparatus of claim 1 , further configured to receive a response to the CCCH message from the network entity.

3. the at least one processor coupled to the memory; The apparatus of claim 2 , further configured to transmit a subsequent UE-specific SDT transmission based on receiving the response.

4. The apparatus of claim 2 , wherein the response is multiplexed with a downlink control information (DCI), an RRC message, or a medium access control (MAC) control element (MAC-CE) that triggers the MT-SDT for the UE.

5. 3. The apparatus of claim 2, wherein the response includes downlink control information (DCI) that schedules a subsequent uplink (UL) transmission or CCCH message retransmission of the UE.

6. The apparatus of claim 1 , wherein the RRC release message is associated with a suspension configuration information element (IE).

7. The apparatus of claim 1 , wherein the one or more configurations for the MO-SDT and the MT-SDT include radio resource allocations for downlink (DL) or uplink (UL) messages belonging to a control plane or a data plane.

8. 2. The apparatus of claim 1, wherein the one or more configurations for the MO-SDT and the MT-SDT include one or more downlink reference signal (DL RS) resources for at least one of one or more reference signal received power (RSRP) measurements, timing advance (TA) verification, link quality assessment, beam management, power control, positioning, one or more tracking loops, quasi-co-location, or spatial relationship.

9. The apparatus of claim 1 , wherein the one or more configurations for the MO-SDT and the MT-SDT include one or more data volume thresholds for initiation of the MO-SDT and the MT-SDT.

10. 2. The apparatus of claim 1, wherein the one or more configurations for the MO-SDT and the MT-SDT include a Reference Signal Received Power (RSRP) threshold associated with selecting the MO-SDT, the MT-SDT, or non-SDT, beam management, link quality assessment, or timing advance (TA) verification, the value of the RSRP threshold depending on a type of procedure and one or more UE capabilities associated with the UE.

11. 2. The apparatus of claim 1, wherein the one or more configurations for the MO-SDT and the MT-SDT include downlink resources in an initial or dedicated downlink (DL) bandwidth portion (BWP) for the MT-SDT and the MO-SDT, and the one or more configurations for the MO-SDT and the MT-SDT further include uplink resources in an initial or dedicated uplink (UL) BWP for the MO-SDT and the MT-SDT.

12. The apparatus of claim 11 , wherein the initial or dedicated DL BWP and the initial or dedicated UL BWP are configured based on a UE type or one or more UE capabilities associated with the UE.

13. 12. The apparatus of claim 11, wherein the initial or dedicated DL BWP and the initial or dedicated UL BWP are independent of UE type or UE capabilities, and further comprising a transceiver coupled to the at least one processor.

14. An apparatus for communication in a user equipment (UE), comprising: Memory, at least one processor coupled to the memory; wherein the at least one processor: Sending a capability indication to a network entity indicating support for small data transmission (SDT) and point-to-multipoint (P2M) multicast and broadcast services (MBS); receiving one or more configurations for the SDT and the P2M MBS from the network entity; Transition to a radio resource control (RRC) inactive state; The apparatus, configured to transmit a Common Control Channel (CCCH) message to the network entity via a Mobile Originated SDT (MO-SDT) while in the RRC inactive state.

15. 15. The apparatus of claim 14, wherein the one or more configurations for the SDT and the P2M MBS are received via an RRC message including at least an RRC release message associated with a suspension configuration, and the one or more configurations for the SDT and the P2M MBS are received via system information (SI) or a medium access control (MAC) control element (MAC-CE).

16. The one or more configurations for the SDT and the P2M an initial or dedicated downlink (DL) bandwidth portion (BWP) and an initial or dedicated uplink (UL) BWP for the SDT or the P2M MBS; or 15. The apparatus of claim 14, further comprising separate resources for the SDT or the P2M MBS in the initial or dedicated DL BWP and the initial or dedicated UL BWP.

17. The apparatus of claim 16 , wherein the joint resources, or the initial or dedicated DL BWP or the initial or dedicated UL BWP, are partitioned based on a UE type or one or more UE capabilities associated with the UE.

18. the at least one processor coupled to the memory; The apparatus of claim 14 , further configured to receive a response to the CCCH message from the network entity.

19. the at least one processor coupled to the memory; 20. The apparatus of claim 18, further configured to transmit a subsequent UE-specific SDT transmission or retransmit the CCCH message based on receiving the response, the response being multiplexed with a Downlink Control Information (DCI), an RRC message, or a Medium Access Control (MAC) Control Element (MAC-CE) that triggers a Mobile Terminated Small Data Transmission (MT-SDT) of the UE.

20. 20. The apparatus of claim 18, wherein the response includes Downlink Control Information (DCI) for scheduling a subsequent Uplink (UL) transmission or CCCH message retransmission of the UE, or includes a Physical Downlink Control Channel (PDCCH) for scheduling a P2M MBS transmission, a P2M retransmission, or a Peer to Peer (P2P retransmission).

21. the at least one processor coupled to the memory; receiving an MBS transmission from the network entity before or after transmitting the CCCH message; 20. The apparatus of claim 18, further configured to send, to the network entity, a hybrid automatic repeat request (HARQ) feedback for the MBS transmission based on a valid Timing Advance (TA), an unexpired TA timer for the SDT, and the response to the CCCH message.

22. the at least one processor coupled to the memory; using a single set of physical uplink control channel (PUCCH) resources to transmit hybrid automatic repeat request (HARQ) feedback for P2M MBS transmissions and MT-SDT transmissions; transmitting data or control for the P2M MBS using resources configured for the MO-SDT; transmitting channel state information (CSI) for the P2M MBS using the resources configured for the MO-SDT; receiving a multiplexed transmission including the P2M MBS and the MT-SDT; sending a request for a software or firmware update for the P2M MBS using the resources configured for the MO-SDT; receiving the software or firmware update for the P2M MBS using MT-SDT resources; receiving a joint configuration for the P2M MBS and the MO-SDT or the MT-SDT; receiving a reconfiguration for the P2M MBS in the MT-SDT resources; or and receiving paging using the MT-SDT resources for retransmission of the P2M MBS.

23. 15. The apparatus of claim 14, wherein an initial or dedicated downlink (DL) bandwidth portion (BWP) is configured via a Master Information Block (MIB), an RRC message, or a System Information Block (SIB), and the capability indication further indicates additional support for peer-to-peer (P2P) retransmission for multicast associated with the P2M MBS.

24. 15. The apparatus of claim 14, wherein an uplink (UL) bandwidth portion (BWP) is configured via an RRC message or a system information block (SIB), and the capability indication further indicates support of Hybrid Automatic Repeat Request (HARQ) feedback for peer-to-peer (P2P) or P2M retransmissions for multicast associated with the P2M MBS, and the HARQ feedback is transmitted on common UL resources for a group of UEs including the UE or on dedicated UL resources for the UE.

25. 25. The apparatus of claim 24, wherein Hybrid Automatic Repeat Request (HARQ) feedback for MBS transmissions or MBS retransmissions is multiplexed with HARQ feedback for MT-SDT transmissions or MT-SDT retransmissions and other control information on the common UL resources or on the dedicated UL resources.

26. 15. The apparatus of claim 14, wherein Hybrid Automatic Repeat Request (HARQ) feedback to the P2M MBS or Mobile Terminated SDT (MT-SDT) is multiplexed with the MO-SDT transmission or retransmission on the same set common UL resources for a group of UEs including the UE or on dedicated UL resources for the UE.

27. the at least one processor coupled to the memory; based on at least one of one or more configured rules, dynamic or semi-persistent priority indications, or UE capabilities associated with the UE; UL control channel, UL Data Channel, a UL RS associated with a first Hybrid Automatic Repeat Request (HARQ) feedback to the P2M MBS; a second HARQ feedback to an MT-SDT transmission, an MT-SDT retransmission, an MO-SDT transmission, an MO-SDT retransmission, or skipping the transmission of at least one of the positioning or channel condition feedback, or based on at least one of the one or more configured rules, the dynamic or semi-persistent priority indication, a UE power saving specification associated with the UE, or the UE capabilities associated with the UE; A downlink (DL) control channel; a DL data channel or DL ​​RS associated with the P2M MBS transmission or P2M MBS retransmission; The MT-SDT transmission or the MT-SDT retransmission, a third HARQ feedback to the MO-SDT transmission; or The apparatus of claim 14 , further configured to skip receiving at least one of the measurements or the positioning.

28. the at least one processor coupled to the memory; 15. The apparatus of claim 14, further configured to prioritize reception of a downlink (DL) control channel, DL data channel, or DL ​​reference signal (RS), or transmission of an uplink (UL) control channel, UL data channel, or UL RS, associated with the P2M MBS, a mobile terminated SDT (MT-SDT), the MO-SDT, positioning, or measurement based on the UE not supporting simultaneous transmission and reception and overlapping or insufficient switching gaps between DL and UL, wherein prioritization is further based on one or more configured rules, dynamic or semi-persistent priority indications, a UE power saving specification associated with the UE, or a UE capability associated with the UE.

29. 1. A method for communication in a user equipment (UE), comprising: transmitting a capability indication to a base station indicating support of Mobile Originated Small Data Transmission (MO-SDT) and Mobile Terminated Small Data Transmission (MT-SDT); receiving, from the base station, one or more configurations for the MO-SDT and the MT-SDT in a Radio Resource Control (RRC) message including at least an RRC release message; Transitioning to an RRC inactive state; transmitting a Common Control Channel (CCCH) message in a MO-SDT transmission to the base station while in the RRC inactive state.

30. 1. A method for communication in a user equipment (UE), comprising: transmitting a capability indication to a base station indicating support of small data transmission (SDT) and point-to-multipoint (P2M) multicast and broadcast services (MBS); receiving one or more configurations for the SDT and the P2M MBS from the base station; transitioning to a radio resource control (RRC) inactive state; and transmitting a Common Control Channel (CCCH) message to the base station via Mobile Originated SDT (MO-SDT) while in the RRC inactive state.

Images