Semi-persistent scheduling resource activation for mobile station called small data transmission

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a semi-persistent scheduling (SPS) configuration from a network node for downlink data reception in an inactive state. The UE may receive, from the network node and when operating in the inactive state, a physical downlink control channel (PDCCH) communication that activates an SPS resource according to the SPS configuration for downlink data reception in the inactive state, wherein the PDCCH communication is associated with a configured scheduled radio network temporary identifier (CS-RNTI). The UE may receive one or more transmissions of downlink data via the SPS resource from the network node and when operating in the inactive state. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for semi-persistent scheduling (SPS) resource activation for mobile station called small data transmission (MT-SDT). Background Art

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

[0003] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a semi-persistent scheduling (SPS) configuration for receiving downlink data in an inactive state from a network node. The one or more processors may be configured to receive a physical downlink control channel (PDCCH) communication of an SPS resource activated according to an SPS configuration for receiving downlink data in an inactive state from a network node and when operating in an inactive state, wherein the PDCCH communication is associated with a scheduling radio network temporary identifier (CS-RNTI) configured. The one or more processors may be configured to receive one or more transmissions of downlink data from a network node and when operating in an inactive state via an SPS resource.

[0006] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send an SPS configuration for receiving downlink data in an inactive state to a UE. The one or more processors may be configured to send a PDCCH communication of an SPS resource activated according to the SPS configuration for receiving downlink data in an inactive state to the UE when the UE is in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI. The one or more processors may be configured to send one or more transmissions of downlink data to the UE via the SPS resource when the UE is in an inactive state.

[0007] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving an SPS configuration for receiving downlink data in an inactive state from a network node. The method may include receiving a PDCCH communication of activating SPS resources according to the SPS configuration for receiving downlink data in an inactive state from the network node and when operating in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI. The method may include receiving one or more transmissions of downlink data via SPS resources from the network node and when operating in an inactive state.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending an SPS configuration for downlink data reception in an inactive state to a UE. The method may include sending a PDCCH communication to the UE when the UE is in an inactive state that activates SPS resources according to the SPS configuration for downlink data reception in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI. The method may include sending one or more transmissions of downlink data to the UE via the SPS resource when the UE is in an inactive state.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, can enable the UE to receive an SPS configuration for receiving downlink data in an inactive state from a network node. The instruction set, when executed by one or more processors of the UE, can enable the UE to receive a PDCCH communication of an SPS resource activated according to the SPS configuration for receiving downlink data in an inactive state from a network node and when operating in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI. The instruction set, when executed by one or more processors of the UE, can enable the UE to receive one or more transmissions of downlink data via SPS resources from a network node and when operating in an inactive state.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to send an SPS configuration for downlink data reception in an inactive state to a UE. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a PDCCH communication activating an SPS resource to the UE according to the SPS configuration for downlink data reception in an inactive state when the UE is in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI. The instruction set, when executed by one or more processors of the network node, may cause the network node to send one or more transmissions of downlink data to the UE via the SPS resource when the UE is in an inactive state.

[0011] Some aspects described herein relate to a device for wireless communication. The device may include a component for receiving an SPS configuration for receiving downlink data in an inactive state from a network node. The device may include a component for receiving a PDCCH communication of an SPS resource activated according to an SPS configuration for receiving downlink data in an inactive state from a network node and when operating in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI. The device may include a component for receiving one or more transmissions of downlink data via an SPS resource from a network node and when operating in an inactive state.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending an SPS configuration for downlink data reception in an inactive state to a UE. The apparatus may include a component for sending a PDCCH communication of activating SPS resources according to the SPS configuration for downlink data reception in an inactive state to the UE when the UE is in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI. The apparatus may include a component for sending one or more transmissions of downlink data to the UE via the SPS resource when the UE is in an inactive state.

[0013] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0014] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0015] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of mobile originated (MO) random access (RA) small data transmission (SDT) according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of an MO configuration grant (CG) SDT according to the present disclosure.

[0022] Figure 6 is a diagram illustrating an example of a Mobile Station Called (MT) SDT according to the present disclosure.

[0023] Figure 7 is a diagram illustrating an example of downlink semi-persistent scheduling (SPS) communication according to the present disclosure.

[0024] Figure 8 is a diagram illustrating an example associated with SPS resource activation for MT-SDT according to the present disclosure.

[0025] Fig. 9 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0026] Fig.10 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0027] Figure 11 to Figure 12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

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

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

[0030] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0031] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0032] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 may include an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0033] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0034] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0035] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0036] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0037] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0038] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.

[0039] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

[0041] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0042] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0043] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0044] In view of the above examples, unless otherwise specifically stated, it should be understood that where the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that where the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0045] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a semi-persistent scheduling (SPS) configuration for downlink data reception in an inactive state from a network node; receive a physical downlink control channel (PDCCH) communication activating SPS resources according to the SPS configuration for downlink data reception in an inactive state from the network node and when operating in an inactive state, wherein the PDCCH communication is associated with a configured scheduling radio network temporary identifier (CS-RNTI); and receive one or more transmissions of downlink data from the network node and via the SPS resources when operating in an inactive state. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send to the UE an SPS configuration for downlink data reception in an inactive state; send to the UE a PDCCH communication activating SPS resources according to the SPS configuration for downlink data reception in an inactive state when the UE is in an inactive state, wherein the PDCCH communication is associated with the CS-RNTI; and send to the UE one or more transmissions of downlink data via the SPS resources when the UE is in an inactive state. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0047] As noted above, Figure 1 are provided as examples. Other examples may vary from Figure 1 An example of description.

[0048] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0049] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0050] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

[0052] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0053] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 8 to 12 )Aspects of any of the methods described herein.

[0054] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 8 to 12 )Aspects of any of the methods described herein.

[0055] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in the network node 110 may perform one or more techniques associated with SPS resource activation for mobile station called small data transmission, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig. 9 The process of 900 Fig.10 1000 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Fig. 9 The process of 900 Fig.10 The operations of process 1000 and / or other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0056] In some aspects, a UE (e.g., UE 120) includes a component for receiving an SPS configuration for downlink data reception in an inactive state from a network node; a component for receiving a PDCCH communication activating an SPS resource according to the SPS configuration for downlink data reception in an inactive state from the network node and when operating in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI; and / or a component for receiving one or more transmissions of downlink data via the SPS resource from the network node and when operating in an inactive state. The components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0057] In some aspects, a network node (e.g., network node 110) includes means for sending an SPS configuration for downlink data reception in an inactive state to a UE; means for sending a PDCCH communication to the UE activating SPS resources according to the SPS configuration for downlink data reception in an inactive state when the UE is in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI; and / or means for sending one or more transmissions of downlink data to the UE via the SPS resources when the UE is in an inactive state. In some aspects, means for the network node to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0058] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0059] As noted above, Figure 2 are provided as examples. Other examples may vary from Figure 2 An example of description.

[0060] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5GNR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

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

[0062] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0063] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0064] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0065] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU310 may be implemented to communicate with DU 330 for network control and signaling.

[0066] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partitioning (such as that defined by 3GPP). In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0067] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0068] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) 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, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0069] The non-RT RIC 315 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 updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0070] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0071] As noted above, Figure 3 are provided as examples. Other examples may vary from Figure 3 An example of description.

[0072] Small data transmission (SDT) refers to the transmission of data from or to a UE when the UE is in an inactive state (e.g., a radio resource control (RRC) inactive state). In a mobile originated (MO) SDT (MO-SDT) framework, a network node may allow a UE to send uplink small data (e.g., an amount of uplink data less than a configured threshold) in an RRC inactive / idle mode without the UE having to move to an RRC connected mode. A random access channel (RACH) based MO-SDT procedure may involve uplink SDT for a RACH-based scheme (e.g., two-step RACH or four-step RACH) from an RRC inactive state. A configured grant (CG) based MO-SDT procedure may involve the transmission of uplink data on a pre-configured physical uplink shared channel (PUSCH) resource (e.g., reusing CG type 1). In some aspects, subsequent transmission of small data in both the uplink direction and the downlink direction may be supported.

[0073] Figure 4 4 is a diagram illustrating an example 400 of a MO random access (RA)-SDT according to the present disclosure. Figure 4 As shown, communications may occur between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0074] As shown in reference numeral 402, as part of a MO-RA-SDT based at least in part on a two-step RACH, the UE may receive an RRC release message from a network node indicating a suspended configuration, and the UE may enter an RRC inactive / idle mode. As shown in reference numeral 404, the UE may send a random access preamble and a PUSCH payload including an RRC recovery request and uplink data to the network node, which may be part of MsgA. As shown in reference numeral 406, the UE may receive a network response indicating contention resolution from the network node, which may be part of MsgB, wherein the network response may not include an RRC message. At this point, subsequent data transmission may be performed between the UE and the network node. As shown in reference numeral 408, the UE may send uplink data to the network node. As shown in reference numeral 410, the UE may receive downlink data from the network node in response to the uplink data. As shown in reference numeral 412, the UE may send additional uplink data to the network node. As shown in reference numeral 414, the UE may receive an RRC release message from the network node indicating a suspended configuration.

[0075] As noted above, Figure 4 are provided as examples. Other examples may vary from Figure 4 An example of description.

[0076] Figure 5 is a diagram illustrating an example 500 of MO-CG-SDT according to the present disclosure. Figure 5 As shown, communications may occur between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0077] As shown in reference numeral 502, as part of MO-CG-SDT, the UE may receive a CG resource configuration from a network node in an RRC release message indicating a suspended configuration, and the UE may enter an RRC inactive / idle mode. The CG resource configuration may indicate a configured PUSCH resource for MO-SDT. As shown in reference numeral 504, the UE may send a first uplink message to the network node, which may be a CG transmission (e.g., a transmission on a configured PUSCH resource) indicating an RRC recovery request and uplink data. As shown in reference numeral 506, the UE may receive a network response from the network node, which may indicate a dynamic grant (DG) for a new uplink transmission or a retransmission of uplink data included in the first uplink message. At this point, subsequent data transmission may be performed between the UE and the network node. As shown in reference numeral 508, the UE may send uplink data to the network node. As shown in reference numeral 510, the UE may receive downlink data from the network node in response to the uplink data. As indicated by reference numeral 512, the UE may send additional uplink data to the network node. As indicated by reference numeral 514, the UE may receive an RRC release message from the network node indicating the suspension configuration.

[0078] As noted above, Figure 5 are provided as examples. Other examples may vary from Figure 5 An example of description.

[0079] MT-SDT can be an SDT initiated by downlink data. For example, when a small amount of downlink data (e.g., less than a configured threshold) is ready to be sent from a network node to the UE, an MT-SDT for the UE can be initiated. In some aspects, the MT-SDT can be triggered by paging the UE. The MT-SDT procedure for the UE may involve initial downlink data reception and subsequent uplink / downlink data transmission in an RRC inactive / idle state. In some examples, the MO-RA-SDT procedure and / or the MO-CG-SDT procedure may be reused for the UE to send an uplink response to downlink data received in the MT-SDT procedure.

[0080] Figure 6 6 is a diagram illustrating an example 600 of MT-RA-SDT according to the present disclosure. Figure 6 As shown, communications may occur between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0081] As shown in reference numeral 602, as part of MT-RA-SDT based at least in part on a four-step RACH, the UE may receive an RRC release message from a network node indicating a suspended configuration, and the UE may enter an RRC inactive / idle mode. As shown in reference numeral 604, the UE may receive a paging message from the network node, which may indicate a UE identity, an MT-SDT indication, and a dedicated preamble. As shown in reference numeral 606, the UE may send a random access preamble (Msg1) to the network node. For example, the UE may send a dedicated preamble indicated in the paging message to the network node. As shown in reference numeral 608, the UE may receive a random access response (Msg2) from the network node. As shown in reference numeral 610, the UE may send a first uplink message (Msg3) indicating an RRC recovery request and uplink data to the network node. As shown in reference numeral 612, the UE may receive a network response (Msg4) indicating contention resolution from the network node, wherein the network response may not include an RRC message. As shown in reference numeral 614, the UE may receive downlink data scheduled by a PDCCH communication associated with a cell radio network temporary identifier (C-RNTI) from a network node. At this point, subsequent data transmission may be performed between the UE and the network node. As shown in reference numeral 616, the UE may send uplink data to the network node in response to the downlink data scheduled by the C-RNTI. As shown in reference numerals 618 and 620, the UE may receive additional downlink data from the network node. In this case, each additional transmission of the downlink data may be scheduled by a corresponding PDCCH communication (e.g., a PDCCH communication associated with the C-RNTI). As shown in reference numeral 622, the UE may receive an RRC release message from the network node indicating a suspension configuration.

[0082] As noted above, Figure 6 are provided as examples. Other examples may vary from Figure 6 An example of description.

[0083] Figure 7 700 is a diagram illustrating an example of downlink SPS communication according to the present disclosure. SPS communication may include periodic downlink communications configured for a UE so that a network node does not need to send (e.g., directly or via one or more network nodes) separate downlink control information (DCI) to schedule each downlink communication, thereby saving signaling overhead.

[0084] like Figure 7As shown, the UE may be configured with an SPS configuration for SPS communication. For example, the UE may receive the SPS configuration via an RRC message sent by a network node (e.g., directly or via one or more network nodes). The SPS configuration may indicate the periodicity of downlink resources repeatedly allocated for downlink SPS. The SPS configuration may also indicate the number of configured hybrid automatic repeat request (HARQ) processes for downlink SPS and the physical uplink control channel (PUCCH) resources for the UE to send HARQ feedback for downlink SPS.

[0085] When operating in an RRC connected state, the UE may monitor a PDCCH addressed to the CS-RNTI (e.g., a PDCCH with a cyclic redundancy check (CRC) scrambled by the CS-RNTI). In some examples, a downlink resource assignment for downlink SPS may be indicated via a PDCCH communication (e.g., a PDCCH communication addressed to the CS-RNTI), and the UE may store the downlink resource assignment based at least in part on layer 1 (L1) signaling indicating SPS activation. Figure 7 As shown, the network node may send an SPS activation DCI to the UE in a PDCCH communication addressed to the CS-RNTI to activate the SPS configuration for the UE. In some examples, the SPS activation DCI may indicate the assignment of allocated downlink resources (e.g., physical downlink shared channel (PDSCH) resources). In this case, the allocated downlink resources may be repeated with the periodicity indicated in the SPS configuration, resulting in the periodic reappearance of scheduled SPS opportunities 705 for the UE. For example, the network node may assign allocated downlink resources for initial SPS downlink communications (e.g., initial HARQ transmissions) to the UE. The UE may begin monitoring the SPS opportunity 705 based at least in part on receiving the SPS activation DCI. The UE may monitor the allocated downlink resources (e.g., PDSCH resources) at each SPS opportunity 705.

[0086] In some examples, the UE may clear downlink resource assignments for downlink SPS based at least in part on L1 signaling indicating SPS deactivation. Figure 7 As shown, the network node may send an SPS release DCI to the UE in a PDCCH communication addressed to the CS-RNTI to deactivate the SPS configuration for the UE. The UE may stop monitoring scheduled SPS opportunities 705 based at least in part on receiving the SPS release DCI. When SPS is released by upper layers, the UE may release all corresponding SPS configurations.

[0087] As noted above, Figure 7 are provided as examples. Other examples can be found in the Figure 7Different than described.

[0088] As above combined Figure 6 As described, the MT-SDT to the UE (e.g., the transmission of a small amount of downlink data) can be scheduled by the corresponding PDCCH dynamic grant. However, in the case where MT-SDT is scheduled for a large number of UEs (e.g., a large number of IoT devices), due to the large amount of downlink signaling overhead associated with the PDCCH dynamic grant, the use of PDCCH dynamic grant to schedule the transmission of a small amount of downlink data may be inefficient. In some aspects, the use of SPS to schedule periodic downlink resources for sending MT-SDT to the UE can reduce downlink signaling overhead compared to scheduling MT-SDT by PDCCH dynamic grant. However, there is currently no mechanism for downlink SPS activation and resource assignment for UEs operating in an RRC inactive state.

[0089] Some techniques and devices described herein enable SPS resource activation for downlink data reception by UEs in an inactive state. The UE can receive an SPS resource configuration for receiving downlink data in an inactive state from a network node. The UE can receive a PDCCH communication that activates SPS resources according to the SPS resource configuration for receiving downlink data in an inactive state from a network node and when the UE operates in an inactive state. The UE can receive one or more transmissions of downlink data via SPS resources from a network node and when the UE operates in an inactive state. Therefore, periodically occurring SPS resources can be used to send downlink data (e.g., for MT-SDT) to the UE when the UE is in an inactive state, which reduces downlink signaling overhead compared to scheduling MT-DTS using PDCCH dynamic grants. Due to the reduced PDCCH decoding, this reduced downlink signaling overhead can improve network efficiency and reduce UE power consumption.

[0090] In some examples, an SDT common search space (CSS) set (also referred to as a "type 1A-PDCCH CSS set") may be configured for a UE. For example, a type 1A-PDCCH CSS set may be configured by sdt-SearchSpace in PDCCH-ConfigCommon. Type 1A-PDCCH CSS may be used for a DCI format with a CRC scrambled by a C-RNTI or CS-RNTI. In some examples, if a type 1A-PDCCH CSS set is configured, the UE may monitor a type 1A-PDCCH CSS set (e.g., an SDT CSS set) after contention resolution for a PDCCH addressed to a C-RNTI. If a type 1A-PDCCH CSS set is not configured, the UE may monitor a random access CSS (also referred to as a "type 1-PDCCH CSS") for a PDCCH addressed to a C-RNTI. However, currently, the random access CSS may not be used for a DCI format with a CRC scrambled by a CS-RNTI, which may be used for SPS activation. Furthermore, since SPS resources are UE-specific configuration, simply sending activation of SPS resources for MT-SDT to the UE via the CSS may not be efficient.

[0091] In some aspects, a UE-specific search space (USS) set for MT-SDT may be configured for the UE. In some aspects, after contention resolution, if the UE receives a trigger to monitor a PDCCH associated with a CS-RNTI, and if the USS set for MT-SDT is configured for the UE, the UE may monitor the USS set for MT-SDT for the PDCCH associated with the CS-RNTI. In some aspects, if the USS set for MT-SDT is not configured for the UE and the type 1A-PDCCH CSS set is configured for the UE, the UE may monitor the type 1A-PDCCH CSS set for the PDCCH associated with the CS-RNTI. In some aspects, the random access CSS may be extended to monitor PDCCH candidates with a CRC scrambled by the CS-RNTI. In some aspects, if the USS set for MT-SDT is not configured for the UE and the type 1A-PDCCH CSS set is not configured for the UE, the UE may monitor the random access CSS for the PDCCH associated with the CS-RNTI. Thus, when in the inactive state, the UE may receive an indication of activation of SPS resources for MT-SDT via the PDCCH associated with the CS-RNTI.

[0092] Figure 8 8 is a diagram illustrating an example 800 associated with SPS resource activation for MT-SDT according to the present disclosure. Figure 8As shown, example 800 includes communications between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as the wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0093] like Figure 8 As shown in reference numeral 802, the network node 110 may send an RRC release message (e.g., RRCRelease) including a suspension configuration (e.g., SuspendConfig) to the UE 120. The UE 120 may receive the RRC release message including the suspension configuration from the network node 110. When operating in the RRC connected state, the UE 120 may receive the RRC release message. In conjunction with receiving the RRC release message including the suspension configuration, the UE 120 may switch from the RRC connected state to the RRC inactive state. The suspension configuration may indicate parameters associated with the operation of the UE 120 when in the RRC inactive state. For example, the suspension configuration may indicate a paging cycle for the UE 120 in the RRC inactive state.

[0094] In some aspects, the network node 110 may send an SPS configuration for MT-SDT of the UE 120, and the UE 120 may receive the SPS configuration. For example, the SPS configuration for MT-SDT may be an SPS configuration for downlink data reception in an inactive state (e.g., in an RRC inactive state). When the UE 120 is in an RRC connected state, the UE 120 may receive the SPS configuration for MT-SDT from the network node 110. In some aspects, the network node 110 may receive the SPS configuration for MT-SDT from the network node 110 via dedicated RRC signaling. In some aspects, the SPS configuration for MT-SDT (e.g., an SPS configuration for downlink reception in an RRC inactive state) may be included in an RRC release message. For example, the RRC release message may include dedicated RRC signaling indicating the SPS configuration for MT-SDT of the UE 120. The SPS configuration for MT-SDT may indicate the periodicity of repeating the SPS resource for downlink data reception in an RRC inactive state. The SPS configuration may also indicate the number of HARQ processes for a downlink SPS in an RRC inactive state and PUCCH resources for sending HARQ feedback for downlink communications received via a downlink SPS in an RRC inactive state. In some aspects, during MT-SDT, the network node 110 may send a PDCCH communication (e.g., a PDCCH communication associated with a CS-RNTI) to the UE 120 that activates the SPS configuration for MT-SDT and assigns SPS resources (e.g., PDSCH resources) that are repeated according to the SPS configuration for MT-SDT.

[0095] In some aspects, whether the network node 110 configures an SPS configuration for MT-SDT of the UE 120 may be based at least in part on the UE capabilities of the UE 120. For example, the UE 120 may send a UE capability report to the network node 110 (e.g., when in an RRC connected state), the UE capability report including an indication of whether the UE 120 supports SPS PDSCH reception for SDT. In this case, the network node 110 may send an SPS configuration for MT-SDT to the UE 120 (e.g., in an RRC release message) based at least in part on the UE capability report indicating that the UE 120 supports SPS PDSCH reception for SDT. In some aspects, one or more SPS configurations for MT-SDT may be configured for the UE 120. For example, the network node 110 RRC release message may indicate one or more SPS configurations for MT-SDT. In some aspects, UE 120 may send a UE capability report to network node 110 (e.g., while in an RRC connected state) indicating whether UE 120 supports multiple SPS configurations for MT-SDT in a bandwidth part (BWP). In this case, the number of SPS configurations for MT-SDT for UE 120 may be based at least in part on the indication of whether UE 120 supports multiple SPS configurations for MT-SDT in the BWP.

[0096] In some aspects, the CG type 1 for SDT configuration and the SPS configuration for MT-SDT may be independently configured for the UE 120 based at least in part on respective reported UE capabilities. For example, the network node 110 may configure the SPS configuration for MT-SDT for the UE 120, but may not configure the CG resources for SDT for the UE 120. In some aspects, the RRC release message may indicate the SPS configuration for MT-SDT, the configured CG resources for SDT, or both the SPS configuration for MT-SDT and the configured CG resources for SDT.

[0097] like Figure 8As further shown by reference numeral 804, when the UE 120 is in the RRC inactive state, the network node 110 may send a paging message associated with the MT-SDT to the UE 120. When in the RRC inactive state, the UE 120 may receive a paging message sent by the network node 110. In some aspects, the UE 120 may monitor a paging DCI (e.g., a DCI having a CRC scrambled by a paging radio network temporary identifier (P-RNTI)) in a paging occasion of a paging cycle. For example, the paging cycle for the UE 120 in the RRC inactive state may be configured in a suspension configuration included in the RRC release message. The paging DCI may indicate that a paging message is sent in a PDSCH communication. In conjunction with detecting the paging DCI in the paging occasion, the UE 120 may receive and decode a PDSCH communication including a paging message.

[0098] In some aspects, the paging message may indicate a UE identity, an MT-SDT indication, and / or a dedicated random access preamble. The UE identity may indicate a UE identifier (ID) of a UE to which the paging message applies (e.g., a UE paged by the paging message). The MT-SDT indication may be an indication that the paging message is for triggering an MT-SDT (e.g., RA-based MT-SDT or CG-based MT-SDT) for the UE identified by the UE identity. For example, the paging message may trigger an MT-SDT for the UE 120 based at least in part on a paging message including an MT-SDT indication and a paging message indicating the UE ID of the UE 120. The dedicated random access preamble may be a random access preamble to be used by the UE 120 to initiate a RACH procedure for the MT-SDT.

[0099] like Figure 8 As further shown by reference numeral 806, the UE 120 may send a random access preamble (Msg1) to the network node. The network node 110 may receive the random access preamble (Msg1) sent by the UE 120. In some aspects, based at least in part on receiving a paging message (e.g., a paging message indicating a UE ID of the UE 120), the UE 120 may send a dedicated preamble indicated in the paging message to the network node. The UE 120 may initiate a RACH procedure for MT-SDT by sending the dedicated random access preamble to the network node 110. For example, the dedicated random access preamble may indicate to the network node 110 that the RACH procedure is for MT-SDT.

[0100] As indicated by reference numeral 808, the network node 110 may send a random access response (Msg2) to the UE 120. The UE 120 may receive the random access response (Msg2) sent by the network node 110. The random access response may include an initial uplink grant indicating uplink resources (e.g., PUSCH resources) to be used by the UE 120 to send a first uplink message to the network node 110.

[0101] As shown by reference numeral 810, UE 120 may send a first uplink message (Msg3) to network node 110. Network node 110 may receive the first uplink message (Msg3) sent by UE 120. For example, UE 120 may send the first uplink message using the uplink resources indicated by the initial uplink grant in the random access response. The first uplink message may include an RRC resume request (e.g., RRCResumeReq). The first uplink message may also include uplink data.

[0102] As indicated by reference numeral 812, the network node 110 may send a network response (Msg4) to the UE 120. The UE 120 may receive the network response (Msg4) sent by the network node 110. The network response may indicate contention resolution. For example, the network response may indicate that the contention resolution is successful for the UE 120.

[0103] In some aspects, a four-step RACH procedure may be used to initiate MT-SDT for UE 120, such as Figure 8 As shown. In some aspects, a two-step RACH procedure may be used to initiate MT-SDT for UE 120. In this case, based at least in part on receiving a paging message, UE 120 may send a MsgA including a random access preamble (e.g., a dedicated random access preamble indicated in the paging message) and a PUSCH payload including an RRC recovery request and uplink data to network node 110, and network node 110 may send a network response (MsgB) indicating contention resolution to UE 120. In some aspects, a CG-based procedure may be used to initiate MT-SDT for UE 120. In the CG-based procedure, the RRC release message may include a CG resource configuration indicating configured PUSCH resources for sending uplink data in an RRC inactive state. In this case, based at least in part on receiving the paging message, UE 120 may send a first uplink message including an RRC recovery request and uplink data to network node 110 using configured PUSCH resources, and network node 110 may send a network response indicating contention resolution to UE 120.

[0104] In some aspects, after contention resolution, while in RRC inactive mode, UE 120 may monitor a PDCCH associated with a CS-RNTI based at least in part on UE 120 receiving a trigger for UE 120 to monitor a PDCCH associated with a CS-RNTI (e.g., a PDCCH addressed to the CS-RNTI). A PDCCH associated with a CS-RNTI refers to a PDCCH with a CRC scrambled by the CS-RNTI. The trigger may be an indication (e.g., a message or an indication within a message) sent from network node 110 to UE 120 that triggers UE 120 to monitor a search space for PDCCH communications associated with the CS-RNTI. In some aspects, receiving Msg4 in a four-step RACH procedure, receiving MsgB in a two-step RACH procedure, or receiving a network response in a CG-based procedure may trigger UE 120 to monitor PDCCH communications associated with the CS-RNTI. For example, if UE 120 receives an SPS configuration for MT-SDT (e.g., in an RRC release message), in addition to monitoring temporary PDCCH communications associated with C-RNTI (TC-RNTI) and C-RNTI, UE 120 may also automatically monitor PDCCH communications associated with CS-RNTI starting from receiving Msg4, MsgB, or a network response (e.g., contention resolution) message in a CG-based procedure. In some aspects, receiving a contention resolution message from network node 110 may trigger UE 120 to monitor PDCCH communications associated with CS-RNTI. For example, UE 120 may monitor PDCCH communications associated with CS-RNTI after receiving Msg4 with contention resolution in a four-step RACH procedure, MsgB with contention resolution in a two-step RACH procedure, or a contention resolution message (e.g., network response with contention resolution) in a CG-based procedure.

[0105] In some aspects, such as Figure 8As shown, the network response (e.g., Msg4 in a four-step RACH procedure, MsgB in a two-step RACH procedure, or a contention resolution message in a CG-based procedure) may include an indication to trigger the UE 120 to monitor PDCCH communications associated with the CS-RNTI. For example, the network response may include a binary indication (e.g., a "flag") indicating whether the UE 120 should monitor PDCCH communications associated with the CS-RNTI after contention resolution. In some aspects, the indication to trigger the UE 120 to monitor PDCCH communications associated with the CS-RNTI may be included in a medium access control (MAC) control element (MAC-CE) (e.g., a dedicated MAC-CE for triggering the UE 120 to monitor PDCCH communications associated with the CS-RNTI). In some aspects, the indication to trigger the UE 120 to monitor PDCCH communications associated with the CS-RNTI may be included in a field in a DCI associated with the network response (e.g., a dedicated field in the DCI for triggering the UE 120 to monitor PDCCH communications associated with the CS-RNTI). In some aspects, based at least in part on receiving a network response including an indication triggering UE 120 to monitor PDCCH communications associated with the CS-RNTI, UE 120 may begin monitoring PDCCH communications associated with the CS-RNTI after a time slot offset by K time slots from a time slot in which UE 120 sent an acknowledgment (ACK) of the network response. For example, the offset of K time slots may be defined in a wireless communication standard or may be configured by network node 110 for UE 120.

[0106] In some aspects, a paging DCI or a paging message associated with an MT-SDT (e.g., a paging message for triggering an MT-SDT for a UE 120) may include an indication to trigger the UE 120 to monitor PDCCH communications associated with a CS-RNTI. For example, the paging DCI or the paging message may include an indication of when to monitor a search space set (e.g., a type 1A-PDCCH CSS set) for PDCCH communications associated with a CS-RNTI. In some aspects, a dedicated field in the paging DCI or the paging message may indicate a selection from a set of options for when the UE 120 monitors PDCCH communications associated with a CS-RNTI.

[0107] In some aspects, UE 120 may monitor a search space set for PDCCH communications associated with the CS-RNTI based at least in part on receiving an indication that triggers monitoring of PDCCH communications associated with the CS-RNTI. In some aspects, a USS set for MT-SDT may be configured for UE 120. For example, when UE 120 is in an RRC connected state, the configuration of the USS set for MT-SDT of UE 120 may be indicated in an RRC release message sent from network node 110 to UE 120 (e.g., in an SPS configuration for MT-SDT included in the RRC release message). The USS set for MT-SDT may be a search space set configured for UE 120 for monitoring PDCCH associated with the CS-RNTI. In some aspects, where a USS set for MT-SDT is configured for UE 120 (e.g., in an RRC release message), UE 120 may monitor the USS set for MT-SDT for PDCCH communications associated with the CS-RNTI. In some aspects, where a USS set for MT-SDT is not configured for UE 120 and an SDT CSS set (e.g., a type 1A-PDCCH CSS set) is configured, UE 120 may monitor the SDT CSS set (e.g., a type 1A-PDCCH CSS set) for PDCCH communications associated with the CS-RNTI. In some aspects, where a USS set for MT-SDT is not configured for UE 120 and an SDT CSS set (e.g., a type 1A-PDCCH CSS set) is not configured, UE 120 may monitor a random access CSS set (e.g., a type 1-PDCCH CSS set) for PDCCH communications associated with the CS-RNTI. In this case, a random access CSS set (eg, type 1 -PDCCH CSS set) may be extended for monitoring PDCCH candidates having a CRC scrambled by a CS-RNTI.

[0108] like Figure 8And as further shown by reference numeral 814, when UE 120 is in the RRC inactive state, network node 110 may send to UE 120 a PDCCH communication associated with the CS-RNTI, the PDCCH communication activating SPS resources according to the SPS configuration for MT-SDT. When in the RRC inactive state, UE 120 may receive a PDCCH communication associated with the CS-RNTI, the PDCCH communication activating SPS resources according to the SPS configuration for MT-SDT. For example, UE 120 may receive a PDCCH communication associated with the CS-RNTI activating SPS resources based at least in part on monitoring a search space set (e.g., a USS set, an SDTCSS set, or a random access CSS set for MT-SDT) for the PDCCH communication associated with the CS-RNTI. In some aspects, network node 110 (or another network device) may determine whether to activate SPS resources and / or when to activate SPS resources for MT-SDT based at least in part on radio channel conditions and / or downlink traffic patterns between network node 110 and UE 120.

[0109] In some aspects, the PDCCH communication associated with the CS-RNTI may include an SPS activation DCI indicating activation of an SPS configuration for MT-SDT and indicating assignment of SPS resources (e.g., PDSCH resources) repeated in periodically occurring SPS opportunities according to the activated SPS configuration for MT-SDT. In the event that the RRC release message indicates multiple SPS configurations for MT-SDT, the SPS activation DCI may indicate one or more SPS configurations for MT-SDT to be activated among the multiple SPS configurations for MT-SDT indicated in the RRC release message.

[0110] Once UE 120 receives SPS activation via PDCCH communication associated with the CS-RNTI, subsequent data transmissions may occur between network node 110 and UE 120. For example, UE 120 may use periodically recurring SPS resources (e.g., PDSCH resources) to receive transmissions of downlink small data (e.g., downlink user data or signaling) from network node 110 in one or more SPS opportunities.

[0111] As shown by reference numeral 816, when in the RRC inactive state, the UE 120 may monitor SPS resources (e.g., PDSCH resources) in an SPS opportunity. The network node 110 may send a transmission of downlink data to the UE 120 via the SPS resources in the SPS opportunity. When operating in the RRC inactive state, the UE 120 may receive a transmission of downlink data from the network node 110 via the SPS resources in the SPS opportunity. In some aspects, the transmission of downlink data from the network node 110 to the UE 120 via the SPS resources may be MT-SDT. For example, the downlink data sent to the UE 120 via the SPS resources may include downlink user data or signaling.

[0112] As indicated by reference numeral 818, in some aspects, UE 120 may send uplink data to network node 110 in response to downlink data received via SPS. Network node 110 may receive the uplink data sent by UE 120.

[0113] As shown by reference numerals 820, 822, and 824, while in the RRC inactive state, the UE 120 may monitor SPS resources (e.g., PDSCH resources) in multiple SPS opportunities. The SPS opportunities may occur with a periodicity indicated in the SPS configuration for MT-SDT. The network node 110 may send downlink data to the UE 120 via the SPS resources in one or more of the multiple SPS opportunities. When in the RRC inactive mode, the UE 120 may receive transmissions of downlink data via the SPS resources in one or more SPS opportunities.

[0114] In some aspects, the UE 120 may continue to monitor the PDCCH communication associated with the CS-RNTI after receiving the SPS activation. In some aspects, the network node 110 may send another PDCCH communication that deactivates the SPS resources associated with the CS-RNTI, and the UE 120 may receive the PDCCH communication. For example, the UE 120 may receive a PDCCH communication including an SPS release DCI that indicates the deactivation of the SPS configuration for the MT-SDT. In this case, in conjunction with receiving the PDCCH communication that deactivates the SPS resources, the UE 120 may stop using the periodically reappearing SPS resources to receive the transmission of downlink data from the network node 110. In some aspects, based at least in part on the UE capabilities of the UE 120, the release DCI in the PDCCH communication may jointly release two or more activated SPS configurations for the MT-SDT of the BWP of the serving cell.

[0115] like Figure 8As further shown by reference numeral 826, the network node 110 may send an RRC release message (e.g., RRCRelease) or an RRC resume message (e.g., RRCResume) to the UE 120. The UE 120 may receive the RRC release message or the RRC resume message sent by the network node 110. In some aspects, the RRC release message or the RRC resume message may terminate the MT-SDT for the UE 120. For example, receiving the RRC release message or the RRC resume message may terminate downlink data reception for the UE 120 in the RRC inactive mode. In this case, in conjunction with the UE 120 receiving the RRC release message or the RRC resume message, the UE 120 may stop using the periodically reoccurring SPS resources to receive transmission of downlink data from the network node 110.

[0116] As noted above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 Different than described.

[0117] Fig. 9 is a diagram illustrating an example process 900, performed, for example, by a UE, according to the present disclosure. Example process 900 is an example of operations in which a UE (eg, UE 120) performs operations associated with SPS resource activation for MT-SDT.

[0118] like Fig. 9 As shown, in some aspects, process 900 may include receiving an SPS configuration for downlink data reception in an inactive state from a network node (block 910). For example, a UE (e.g., using Fig.11 The communication manager 140 and / or receiving component 1102 depicted in FIG. 1 may receive an SPS configuration for downlink data reception in an inactive state from a network node, as described above.

[0119] like Fig. 9 As further shown, in some aspects, process 900 may include receiving, from a network node and while operating in an inactive state, a PDCCH communication activating SPS resources according to an SPS configuration for downlink data reception in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI (block 920). Fig.11 The communication manager 140 and / or receiving component 1102 depicted in the figure can receive a PDCCH communication activating SPS resources according to an SPS configuration for downlink data reception in an inactive state from a network node and when operating in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI as described above.

[0120] like Fig. 9As further shown, in some aspects, process 900 may include receiving one or more transmissions of downlink data from a network node and via SPS resources when operating in an inactive state (block 930). Fig.11 The communication manager 140 and / or receiving component 1102 depicted in FIG. 1 may receive one or more transmissions of downlink data from a network node and via SPS resources when operating in an inactive state, as described above.

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

[0122] In a first aspect, the one or more transmissions of downlink data include one or more transmissions of downlink user data or signaling.

[0123] In a second aspect, receiving an SPS configuration for downlink data reception in an inactive state includes, while operating in an RRC connected state, receiving an RRC release message indicating the SPS configuration for downlink data reception in an inactive state.

[0124] In a third aspect, process 900 includes receiving an indication from a network node and while operating in an inactive state to trigger monitoring of PDCCH communications associated with a CS-RNTI, and monitoring a search space set for PDCCH communications associated with the CS-RNTI based at least in part on receiving the indication to trigger monitoring of PDCCH communications associated with the CS-RNTI, wherein receiving the PDCCH communication includes receiving the PDCCH communication associated with the CS-RNTI based at least in part on monitoring the search space set for PDCCH communications associated with the CS-RNTI.

[0125] In a fourth aspect, process 900 includes receiving configuration of a UE-specific search space set for MT-SDT from a network node, and monitoring the search space set for PDCCH communications associated with a CS-RNTI includes monitoring the UE-specific search space set for MT-SDT for PDCCH communications associated with the CS-RNTI.

[0126] In a fifth aspect, monitoring a search space set for PDCCH communications associated with a CS-RNTI includes monitoring the SDT common search space set for PDCCH communications associated with the CS-RNTI in conjunction with a SDT common search space set being configured for the UE.

[0127] In a sixth aspect, monitoring an SDT common search space set for PDCCH communications associated with a CS-RNTI includes monitoring an SDT common search space set for PDCCH communications associated with a CS-RNTI in combination with an SDT common search space set configured for the UE and in combination with a UE-specific search space set not used for MT-SDT configured for the UE.

[0128] In a seventh aspect, monitoring a search space set for PDCCH communications associated with a CS-RNTI comprises monitoring a random access common search space set for PDCCH communications associated with the CS-RNTI in conjunction with no SDT common search space set being configured for the UE.

[0129] In an eighth aspect, receiving an indication triggering monitoring of PDCCH communications associated with the CS-RNTI includes receiving Msg4 or MsgB in a random access channel procedure, and monitoring a search space set for PDCCH communications associated with the CS-RNTI includes monitoring a search space set for PDCCH communications associated with the CS-RNTI in combination with receiving Msg4 or MsgB.

[0130] In a ninth aspect, receiving an indication triggering monitoring of PDCCH communications associated with a CS-RNTI includes receiving a contention resolution message from a network node, and monitoring a search space set for PDCCH communications associated with the CS-RNTI includes monitoring a search space set for PDCCH communications associated with the CS-RNTI in conjunction with receiving the contention resolution message.

[0131] In a tenth aspect, receiving an indication triggering monitoring of PDCCH communications associated with the CS-RNTI comprises receiving an indication triggering monitoring of PDCCH communications associated with the CS-RNTI via Msg4 or MsgB in a random access channel procedure.

[0132] In an eleventh aspect, a search space set for monitoring PDCCH communications associated with a CS-RNTI includes, in combination with a Msg4 or MsgB including an indication for monitoring PDCCH communications associated with the CS-RNTI, starting after an offset relative to the sending of an acknowledgment of the Msg4 or MsgB, the search space set for monitoring PDCCH communications associated with the CS-RNTI.

[0133] In a twelfth aspect, an indication triggering monitoring of PDCCH communications associated with a CS-RNTI is included in a paging DCI or a paging message associated with an MT-SDT.

[0134] In a thirteenth aspect, process 900 includes receiving another PDCCH communication from a network node to deactivate SPS resources associated with a CS-RNTI.

[0135] In a fourteenth aspect, process 900 comprises receiving an RRC release message or an RRC resume message from a network node after receiving a PDCCH communication activating SPS resources, wherein receiving the RRC release message or the RRC resume message terminates downlink data reception via the SPS resources in an inactive mode.

[0136] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted in the process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more blocks in the blocks of the process 900 may be executed in parallel.

[0137] Fig.10 is a diagram illustrating an example process 1000, performed, for example, by a network node, in accordance with the present disclosure. Example process 1000 is an example of a network node (eg, network node 110) performing operations associated with SPS resource activation for MT-SDT.

[0138] like Fig.10 As shown, in some aspects, process 1000 may include sending an SPS configuration for downlink data reception in an inactive state to a UE (block 1010). For example, a network node (e.g., using Fig.12 The communication manager 150 and / or the sending component 1204 depicted in FIG. 1 may send an SPS configuration for downlink data reception in an inactive state to the UE, as described above.

[0139] like Fig.10 As further shown, in some aspects, process 1000 may include sending, to the UE when the UE is in an inactive state, a PDCCH communication activating SPS resources according to an SPS configuration for downlink data reception in an inactive state, wherein the PDCCH communication is associated with the CS-RNTI (block 1020). Fig.12 The communication manager 150 and / or sending component 1204 depicted in the figure may send a PDCCH communication to the UE when the UE is in an inactive state to activate SPS resources according to the SPS configuration for downlink data reception in an inactive state, wherein the PDCCH communication is associated with the CS-RNTI, as described above.

[0140] like Fig.10As further shown, in some aspects, process 1000 may include one or more transmissions of downlink data to the UE via the SPS resources when the UE is in an inactive state (block 1030). Fig.12 The communication manager 150 and / or transmission component 1204 depicted in FIG. 1 may send one or more transmissions of downlink data to the UE via the SPS resources when the UE is in an inactive state, as described above.

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

[0142] In a first aspect, the one or more transmissions of downlink data include one or more transmissions of downlink user data or signaling.

[0143] In a second aspect, sending the SPS configuration for downlink data reception in an inactive state includes sending an RRC release message indicating the SPS configuration for downlink data reception in an inactive state to the UE.

[0144] In a third aspect, process 1000 includes sending an indication to a UE that triggers the UE to monitor a PDCCH communication associated with a CS-RNTI when the UE is in an inactive state.

[0145] In a fourth aspect, process 1000 includes sending a configuration of a UE-specific search space set for MT-SDT to a UE, and sending a PDCCH communication activating SPS resources includes sending a PDCCH communication associated with a CS-RNTI to the UE in the UE-specific search space set for MT-SDT.

[0146] In a fifth aspect, sending a PDCCH communication activating SPS resources includes sending a PDCCH communication associated with a CS-RNTI in the SDT common search space set to the UE in conjunction with an SDT common search space set being configured for the UE.

[0147] In a sixth aspect, sending a PDCCH communication associated with a CS-RNTI to a UE in an SDT common search space set includes sending a PDCCH communication associated with a CS-RNTI to a UE in an SDT common search space set in combination with an SDT common search space set configured for the UE and in combination with a UE-specific search space set not configured for MT-SDT for the UE.

[0148] In a seventh aspect, sending a PDCCH communication activating SPS resources for MT-SDT includes sending a PDCCH communication associated with a CS-RNTI in a random access common search space set to the UE in conjunction with no SDT common search space set being configured for the UE.

[0149] In an eighth aspect, sending an indication to trigger the UE to monitor PDCCH communications associated with the CS-RNTI includes sending Msg4 or MsgB to the UE in a random access channel procedure.

[0150] In a ninth aspect, sending an indication to trigger a UE to monitor a PDCCH for communications associated with a CS-RNTI includes sending a contention resolution message to the UE.

[0151] In a tenth aspect, an indication triggering the UE to monitor PDCCH communications associated with the CS-RNTI is included in Msg4 or MsgB in the random access channel procedure.

[0152] In an eleventh aspect, an indication triggering the UE to monitor PDCCH communications associated with the CS-RNTI is included in a paging DCI or a paging message associated with the MT-SDT.

[0153] In a twelfth aspect, process 1000 includes sending another PDCCH communication to the UE that deactivates SPS resources associated with the CS-RNTI.

[0154] In a thirteenth aspect, process 1000 includes sending an RRC release message or an RRC resume message to the UE after sending a PDCCH communication activating the SPS resources, wherein the RRC release message or the RRC resume message indicates termination of downlink data reception via the SPS resources in an inactive mode.

[0155] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 The blocks in the process 1000 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more blocks in the blocks of the process 1000 may be executed in parallel.

[0156] Fig.111 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a UE, or a UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a sending component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and sending component 1104. As further shown, apparatus 1100 may include a communication manager 140. Communication manager 140 may include monitoring component 1108, etc.

[0157] In some aspects, the apparatus 1100 may be configured to perform Figure 8 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more of the processes described herein (such as Fig. 9 In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0158] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0159] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0160] The receiving component 1102 may receive an SPS configuration for downlink data reception in an inactive state from a network node. The receiving component 1102 may receive a PDCCH communication activating SPS resources according to the SPS configuration for downlink data reception in an inactive state from the network node while operating in an inactive state, wherein the PDCCH communication is associated with a CS-RNTI. The receiving component 1102 may receive one or more transmissions of downlink data via the SPS resources from the network node while operating in an inactive state.

[0161] Receiving component 1102 can receive, from a network node and while operating in an inactive state, an indication triggering monitoring of PDCCH communications associated with a CS-RNTI.

[0162] The monitoring component 1108 may monitor a search space set for PDCCH communications associated with the CS-RNTI based at least in part on receiving an indication that triggers monitoring of PDCCH communications associated with the CS-RNTI, wherein receiving the PDCCH communication includes receiving the PDCCH communication associated with the CS-RNTI based at least in part on monitoring the search space set for PDCCH communications associated with the CS-RNTI.

[0163] Receiving component 1102 can receive configuration of a UE-specific search space set for MT-SDT from a network node, wherein monitoring the search space set for PDCCH communications associated with a CS-RNTI includes monitoring the UE-specific search space set for MT-SDT for PDCCH communications associated with the CS-RNTI.

[0164] Receiving component 1102 can receive another PDCCH communication from a network node to deactivate SPS resources associated with the CS-RNTI.

[0165] Receiving component 1102 may receive an RRC release message or an RRC resume message from a network node after receiving a PDCCH communication activating the SPS resources, wherein receiving the RRC release message or the RRC resume message terminates downlink data reception via the SPS resources in an inactive mode.

[0166] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged differently than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The illustrated set of component(s) may be described as being executable by Fig.11 Another component shown may be a collection of components that perform one or more functions.

[0167] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a network node, or a network node may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and sending component 1204. As further shown, apparatus 1200 may include a communication manager 150. Communication manager 150 may include a determining component 1208, etc.

[0168] In some aspects, the apparatus 1200 may be configured to perform Figure 8 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein (such as Fig.10 In some aspects, Fig.12 The illustrated apparatus 1200 and / or one or more components may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0169] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0170] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0171] The transmitting component 1204 may transmit to the UE an SPS configuration for downlink data reception in an inactive state. The transmitting component 1204 may transmit to the UE a PDCCH communication activating SPS resources according to the SPS configuration for downlink data reception in an inactive state when the UE is in an inactive state, wherein the PDCCH communication is associated with the CS-RNTI. The transmitting component 1204 may transmit to the UE one or more transmissions of downlink data via the SPS resources when the UE is in an inactive state.

[0172] Determining component 1208 can determine an SPS configuration for inactive downlink data reception of the UE and / or SPS resources to be activated for the UE based on the SPS configuration for inactive downlink data reception.

[0173] The transmitting component 1204 can transmit, to the UE when the UE is in an inactive state, an indication triggering the UE to monitor the PDCCH for communications associated with the CS-RNTI.

[0174] Transmitting component 1204 can transmit a configuration of a UE-specific search space set for MT-SDT to the UE, wherein transmitting a PDCCH communication activating SPS resources comprises transmitting a PDCCH communication associated with the CS-RNTI to the UE in the UE-specific search space set for MT-SDT.

[0175] Transmitting component 1204 can transmit another PDCCH communication to the UE with deactivated SPS resources associated with the CS-RNTI.

[0176] The transmitting component 1204 may transmit a radio resource control (RRC) release message or an RRC resume message to the UE after transmitting the PDCCH communication activating the SPS resources, wherein the RRC release message or the RRC resume message indicates termination of downlink data reception via the SPS resources in the inactive mode.

[0177] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged differently than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The illustrated set of component(s) may be described as being executable by Fig.12 Another component shown may be a collection of components that perform one or more functions.

[0178] The following provides an overview of some aspects of the disclosure:

[0179] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving a semi-persistent scheduling (SPS) configuration for downlink data reception in an inactive state from a network node; receiving a physical downlink control channel (PDCCH) communication activating SPS resources according to the SPS configuration for downlink data reception in the inactive state from the network node and when operating in the inactive state, wherein the PDCCH communication is associated with a configured scheduling radio network temporary identifier (CS-RNTI); and receiving one or more transmissions of downlink data from the network node and via the SPS resources when operating in the inactive state.

[0180] Aspect 2: The method according to aspect 1, wherein the one or more transmissions of downlink data include one or more transmissions of downlink user data or signaling.

[0181] Aspect 3: A method according to any one of Aspects 1 to 2, wherein receiving the SPS configuration for downlink data reception in the inactive state includes: when operating in a radio resource control (RRC) connected state, receiving an RRC release message indicating the SPS configuration for downlink data reception in the inactive state.

[0182] Aspect 4: The method according to any one of Aspects 1 to 3 further includes: receiving an indication from the network node and when operating in the inactive state to trigger monitoring of the PDCCH communication associated with the CS-RNTI; and monitoring a search space set for the PDCCH communication associated with the CS-RNTI based at least in part on receiving the indication to trigger monitoring of the PDCCH communication associated with the CS-RNTI, wherein receiving the PDCCH communication includes receiving the PDCCH communication associated with the CS-RNTI based at least in part on monitoring the search space set for the PDCCH communication associated with the CS-RNTI.

[0183] Aspect 5: The method according to Aspect 4 also includes: receiving a configuration of a UE-specific search space set for mobile station called small data transmission (MT-SDT) from the network node, wherein monitoring the search space set for the PDCCH communication associated with the CS-RNTI includes monitoring the UE-specific search space set for MT-SDT for the PDCCH communication associated with the CS-RNTI.

[0184] Aspect 6: A method according to Aspect 4, wherein monitoring the search space set for the PDCCH communication associated with the CS-RNTI includes: combining a small data transmission (SDT) common search space set configured for the UE, and monitoring the SDT common search space set for the PDCCH communication associated with the CS-RNTI.

[0185] Aspect 7: A method according to Aspect 6, wherein monitoring the SDT common search space set for the PDCCH communication associated with the CS-RNTI includes: combining the SDT common search space set configured for the UE and combining a UE-specific search space set not used for mobile station called SDT (MT-SDT) configured for the UE, monitoring the SDT common search space set for the PDCCH communication associated with the CS-RNTI.

[0186] Aspect 8: A method according to Aspect 4, wherein monitoring the search space set for the PDCCH communication associated with the CS-RNTI includes: in combination with no SDT common search space set being configured for the UE, monitoring the random access common search space set for the PDCCH communication associated with the CS-RNTI.

[0187] Aspect 9: A method according to any one of Aspects 4 to 8, wherein receiving the indication triggering monitoring of the PDCCH communication associated with the CS-RNTI includes receiving Msg4 or MsgB in a random access channel procedure, and wherein monitoring the search space set for the PDCCH communication associated with the CS-RNTI includes monitoring the search space set for the PDCCH communication associated with the CS-RNTI in combination with receiving the Msg4 or the MsgB.

[0188] Aspect 10: A method according to any one of Aspects 4 to 9, wherein receiving the indication triggering monitoring of the PDCCH communication associated with the CS-RNTI includes receiving a contention resolution message from the network node, and wherein monitoring the search space set for the PDCCH communication associated with the CS-RNTI includes monitoring the search space set for the PDCCH communication associated with the CS-RNTI in combination with receiving the contention resolution message.

[0189] Aspect 11: A method according to any one of Aspects 4 to 8, wherein receiving the indication that triggers monitoring of the PDCCH communication associated with the CS-RNTI includes: receiving the indication to monitor the PDCCH communication associated with the CS-RNTI via Msg4 or MsgB in the random access channel procedure.

[0190] Aspect 12: A method according to Aspect 11, wherein monitoring the search space set for the PDCCH communication associated with the CS-RNTI includes: in combination with the Msg4 or the MsgB including the indication for monitoring the PDCCH communication associated with the CS-RNTI, starting after an offset relative to the sending of a confirmation of the Msg4 or the MsgB, monitoring the search space set for the PDCCH communication associated with the CS-RNTI.

[0191] Aspect 13: A method according to any one of Aspects 4 to 8, wherein the indication triggering monitoring of the PDCCH communication associated with the CS-RNTI is included in paging downlink control information (DCI) or a paging message associated with a mobile station called small data transmission (MT-SDT).

[0192] Aspect 14: The method according to any one of aspects 1 to 13, further comprising: receiving another PDCCH communication associated with the CS-RNTI from the network node to deactivate the SPS resources.

[0193] Aspect 15: The method according to any one of Aspects 1 to 14 further includes: receiving a radio resource control (RRC) release message or an RRC recovery message from the network node after receiving the PDCCH communication that activates the SPS resource, wherein receiving the RRC release message or the RRC recovery message terminates downlink data reception via the SPS resource in an inactive mode.

[0194] Aspect 16: A method of wireless communication performed by a network node, comprising: sending a semi-persistent scheduling (SPS) configuration for downlink data reception in an inactive state to a user equipment (UE); sending a physical downlink control channel (PDCCH) communication to the UE that activates SPS resources according to the SPS configuration for downlink data reception in the inactive state when the UE is in the inactive state, wherein the PDCCH communication is associated with a configured scheduling radio network temporary identifier (CS-RNTI); and sending one or more transmissions of downlink data to the UE via the SPS resources when the UE is in the inactive state.

[0195] Aspect 17: The method according to aspect 16, wherein the one or more transmissions of downlink data include one or more transmissions of downlink user data or signaling.

[0196] Aspect 18: A method according to any one of Aspects 16 to 17, wherein sending the SPS configuration for receiving downlink data in the inactive state includes: sending an RRC release message to the UE indicating the SPS configuration for receiving downlink data in the inactive state.

[0197] Aspect 19: The method according to any one of aspects 16 to 18 further includes: sending an indication to the UE to trigger the UE to monitor the PDCCH communication associated with the CS-RNTI when the UE is in the inactive state.

[0198] Aspect 20: The method according to Aspect 19 also includes: sending a configuration of a UE-specific search space set for mobile station called small data transmission (MT-SDT) to the UE, wherein sending the PDCCH communication for activating the SPS resource includes sending the PDCCH communication associated with the CS-RNTI to the UE in the UE-specific search space set for MT-SDT.

[0199] Aspect 21: A method according to Aspect 19, wherein sending the PDCCH communication that activates the SPS resource includes: combining a small data transmission (SDT) common search space set configured for the UE, and sending the PDCCH communication associated with the CS-RNTI to the UE in the SDT common search space set.

[0200] Aspect 22: A method according to Aspect 21, wherein sending the PDCCH communication associated with the CS-RNTI to the UE in the SDT common search space set includes: in combination with the SDT common search space set being configured for the UE and in combination with a UE-specific search space set not used for mobile station called SDT (MT-SDT) being configured for the UE, sending the PDCCH communication associated with the CS-RNTI to the UE in the SDT common search space set.

[0201] Aspect 23: A method according to Aspect 19, wherein sending the PDCCH communication for activating the SPS resources for MT-SDT includes: in combination with no small data transmission (SDT) common search space set being configured for the UE, sending the PDCCH communication associated with the CS-RNTI to the UE in the random access common search space set.

[0202] Aspect 24: The method according to any one of aspects 19 to 23, wherein sending the indication to trigger the UE to monitor the PDCCH communication associated with the CS-RNTI includes: sending Msg4 or MsgB to the UE in a random access channel procedure.

[0203] Aspect 25: The method according to any one of aspects 19 to 24, wherein sending the indication to trigger the UE to monitor the PDCCH communication associated with the CS-RNTI includes: sending a contention resolution message to the UE.

[0204] Aspect 26: The method according to any one of aspects 19 to 23, wherein the indication triggering the UE to monitor the PDCCH communication associated with the CS-RNTI is included in Msg4 or MsgB in a random access channel procedure.

[0205] Aspect 27: A method according to any one of Aspects 19 to 23, wherein the indication for triggering the UE to monitor the PDCCH communication associated with the CS-RNTI is included in paging downlink control information (DCI) or a paging message associated with a mobile station called small data transmission (MT-SDT).

[0206] Aspect 28: The method according to any one of aspects 16 to 27 further comprises: sending another PDCCH communication associated with the CS-RNTI to the UE to deactivate the SPS resources.

[0207] Aspect 29: The method according to any one of Aspects 16 to 28 further includes: sending a radio resource control (RRC) release message or an RRC recovery message to the UE after sending the PDCCH communication that activates the SPS resource, wherein the RRC release message or the RRC recovery message indicates the termination of downlink data reception via the SPS resource in an inactive mode.

[0208] Aspect 30: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 15.

[0209] Aspect 31: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 15.

[0210] Aspect 32: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 1 to 15.

[0211] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 15.

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

[0213] Aspect 35: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 16 to 29.

[0214] Aspect 36: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 16 to 29.

[0215] Aspect 37: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 16 to 29.

[0216] Aspect 38: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 16 to 29.

[0217] Aspect 39: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 16 to 29.

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

[0219] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

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

[0221] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the item list refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other sorting of a, b and c).

[0222] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., when used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving, from a network node, a semi-persistent scheduling (SPS) configuration for downlink data reception in an inactive state; receiving, from the network node and while operating in the inactive state, a physical downlink control channel (PDCCH) communication activating SPS resources according to the SPS configuration for downlink data reception in the inactive state, wherein the PDCCH communication is associated with a configured scheduling radio network temporary identifier (CS-RNTI); as well as One or more transmissions of downlink data are received from the network node and via the SPS resources while operating in the inactive state. 2 . The UE of claim 1 , wherein the one or more transmissions of downlink data comprise one or more transmissions of downlink user data or signaling.

3. The UE of claim 1 , wherein to receive the SPS configuration for downlink data reception in the inactive state, the one or more processors are configured to: When operating in a radio resource control (RRC) connected state, an RRC release message is received indicating the SPS configuration for downlink data reception in the inactive state.

4. The UE of claim 1, wherein the one or more processors are further configured to: receiving, from the network node and while operating in the inactive state, an indication triggering monitoring of the PDCCH communications associated with the CS-RNTI; and monitoring a search space set for the PDCCH communication associated with the CS-RNTI based at least in part on receiving the indication that triggers monitoring of the PDCCH communication associated with the CS-RNTI, wherein in order to receive the PDCCH communication, the one or more processors are configured to receive the PDCCH communication associated with the CS-RNTI based at least in part on monitoring the search space set for the PDCCH communication associated with the CS-RNTI.

5. The UE of claim 4, wherein the one or more processors are further configured to: A configuration of a UE-specific search space set for mobile station called small data transmission (MT-SDT) is received from the network node, wherein in order to monitor the search space set for the PDCCH communication associated with the CS-RNTI, the one or more processors are configured to monitor the UE-specific search space set for MT-SDT for the PDCCH communication associated with the CS-RNTI.

6. The UE of claim 4, wherein to monitor the search space set for the PDCCH communication associated with the CS-RNTI, the one or more processors are configured to: In conjunction with a small data transmission (SDT) common search space set being configured for the UE, the SDT common search space set is monitored for the PDCCH communication associated with the CS-RNTI.

7. The UE of claim 6, wherein to monitor the SDT common search space set for the PDCCH communication associated with the CS-RNTI, the one or more processors are configured to: The SDT common search space set is configured for the UE in conjunction with the SDT common search space set being configured for the UE and in conjunction with no UE-specific search space set for mobile called SDT (MT-SDT) being configured for the UE, monitoring the SDT common search space set for the PDCCH communication associated with the CS-RNTI.

8. The UE of claim 4, wherein to monitor the search space set for the PDCCH communication associated with the CS-RNTI, the one or more processors are configured to: In conjunction with no SDT common search space set being configured for the UE, a random access common search space set is monitored for the PDCCH communication associated with the CS-RNTI.

9. The UE according to claim 4, wherein in order to receive the indication triggering monitoring of the PDCCH communication associated with the CS-RNTI, the one or more processors are configured to receive Msg4 or MsgB in a random access channel procedure, and wherein in order to monitor the search space set for the PDCCH communication associated with the CS-RNTI, the one or more processors are configured to monitor the search space set for the PDCCH communication associated with the CS-RNTI in combination with receiving the Msg4 or the MsgB.

10. The UE of claim 4, wherein in order to receive the indication triggering monitoring of the PDCCH communication associated with the CS-RNTI, the one or more processors are configured to receive a contention resolution message from the network node, and wherein in order to monitor the search space set for the PDCCH communication associated with the CS-RNTI, the one or more processors are configured to monitor the search space set for the PDCCH communication associated with the CS-RNTI in combination with receiving the contention resolution message.

11. The UE of claim 4, wherein to receive the indication triggering monitoring of the PDCCH communication associated with the CS-RNTI, the one or more processors are configured to: An indication to monitor the PDCCH communication associated with the CS-RNTI is received via Msg4 or MsgB in a random access channel procedure.

12. The UE of claim 11, wherein to monitor the search space set for the PDCCH communication associated with the CS-RNTI, the one or more processors are configured to: In conjunction with the Msg4 or the MsgB including the indication to monitor the PDCCH communication associated with the CS-RNTI, starting after an offset relative to the sending of an acknowledgement of the Msg4 or the MsgB, monitoring the search space set for the PDCCH communication associated with the CS-RNTI.

13. The UE of claim 4, wherein the indication triggering monitoring of the PDCCH communication associated with the CS-RNTI is included in paging downlink control information (DCI) or a paging message associated with a mobile station called small data transmission (MT-SDT).

14. The UE of claim 1, wherein the one or more processors are further configured to: Another PDCCH communication associated with the CS-RNTI is received from the network node deactivating the SPS resources.

15. The UE of claim 1, wherein the one or more processors are further configured to: A radio resource control (RRC) release message or an RRC resume message is received from the network node after receiving the PDCCH communication activating the SPS resources, wherein receiving the RRC release message or the RRC resume message terminates downlink data reception via the SPS resources in an inactive mode.

16. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: sending a semi-persistent scheduling (SPS) configuration for downlink data reception in an inactive state to a user equipment (UE); sending, to the UE when the UE is in the inactive state, a physical downlink control channel (PDCCH) communication activating SPS resources according to the SPS configuration for downlink data reception in the inactive state, wherein the PDCCH communication is associated with a configured scheduling radio network temporary identifier (CS-RNTI); as well as One or more transmissions of downlink data are sent to the UE via the SPS resources when the UE is in the inactive state.

17. The network node of claim 16, wherein to send the SPS configuration for downlink data reception in the inactive state, the one or more processors are configured to: An RRC release message is sent to the UE indicating the SPS configuration for downlink data reception in the inactive state.

18. The network node of claim 16, wherein the one or more processors are further configured to: When the UE is in the inactive state, an indication is sent to the UE to trigger the UE to monitor the PDCCH communication associated with the CS-RNTI.

19. The network node of claim 18, wherein the one or more processors are further configured to: A configuration of a UE-specific search space set for mobile station called small data transmission (MT-SDT) is sent to the UE, wherein sending the PDCCH communication for activating the SPS resource includes sending the PDCCH communication associated with the CS-RNTI to the UE in the UE-specific search space set for MT-SDT.

20. The network node of claim 18, wherein to send the PDCCH communication activating the SPS resources, the one or more processors are configured to: The PDCCH communication associated with the CS-RNTI is transmitted to the UE in conjunction with a small data transmission (SDT) common search space set configured for the UE and in conjunction with a UE-specific search space set not configured for mobile station called SDT (MT-SDT) for the UE.

21. The network node of claim 18, wherein to send the PDCCH communication activating the SPS resources for MT-SDT, the one or more processors are configured to: In conjunction with no small data transmission (SDT) common search space set being configured for the UE, the PDCCH communication associated with the CS-RNTI is transmitted to the UE in a random access common search space set.

22. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving, from a network node, a semi-persistent scheduling (SPS) configuration for downlink data reception in an inactive state; receiving, from the network node and while operating in the inactive state, a physical downlink control channel (PDCCH) communication activating SPS resources according to the SPS configuration for downlink data reception in the inactive state, wherein the PDCCH communication is associated with a configured scheduling radio network temporary identifier (CS-RNTI); as well as One or more transmissions of downlink data are received from the network node and via the SPS resources while operating in the inactive state.

23. The method of claim 22, wherein receiving the SPS configuration for downlink data reception in the inactive state comprises: When operating in a radio resource control (RRC) connected state, an RRC release message is received indicating the SPS configuration for downlink data reception in the inactive state.

24. The method according to claim 22, further comprising: receiving, from the network node and while operating in the inactive state, an indication triggering monitoring of the PDCCH communications associated with the CS-RNTI; as well as A search space set is monitored for the PDCCH communication associated with the CS-RNTI based at least in part on receiving the indication that triggers monitoring of the PDCCH communication associated with the CS-RNTI, wherein receiving the PDCCH communication includes receiving the PDCCH communication associated with the CS-RNTI based at least in part on monitoring the search space set for the PDCCH communication associated with the CS-RNTI.

25. The method according to claim 24, further comprising: A configuration of a UE-specific search space set for mobile station called small data transmission (MT-SDT) is received from the network node, wherein monitoring the search space set for the PDCCH communication associated with the CS-RNTI includes monitoring the UE-specific search space set for MT-SDT for the PDCCH communication associated with the CS-RNTI.

26. The method of claim 24, wherein monitoring the search space set for the PDCCH communication associated with the CS-RNTI comprises: In conjunction with a small data transmission (SDT) common search space set configured for the UE and in conjunction with a UE-specific search space set not configured for mobile station called SDT (MT-SDT) for the UE, the SDT common search space set is monitored for the PDCCH communication associated with the CS-RNTI.

27. The method of claim 24, wherein monitoring the search space set for the PDCCH communication associated with the CS-RNTI comprises: In conjunction with no SDT common search space set being configured for the UE, a random access common search space set is monitored for the PDCCH communication associated with the CS-RNTI.

28. A method of wireless communication performed by a network node, the method comprising: sending a semi-persistent scheduling (SPS) configuration for downlink data reception in an inactive state to a user equipment (UE); sending, to the UE when the UE is in the inactive state, a physical downlink control channel (PDCCH) communication activating SPS resources according to the SPS configuration for downlink data reception in the inactive state, wherein the PDCCH communication is associated with a configured scheduling radio network temporary identifier (CS-RNTI); as well as One or more transmissions of downlink data are sent to the UE via the SPS resources when the UE is in the inactive state.

29. The method of claim 28, wherein sending the SPS configuration for downlink data reception in the inactive state comprises: An RRC release message is sent to the UE indicating the SPS configuration for downlink data reception in the inactive state.

30. The method of claim 28, further comprising: When the UE is in the inactive state, an indication is sent to the UE to trigger the UE to monitor the PDCCH communication associated with the CS-RNTI.

Images