Small data transmission configuration for non-terrestrial networks

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a UE-specific configured grant (CG) small data transmission (SDT) configuration with parameters specific to a configured grant (CG) small data transmission (SDT) in a non-terrestrial network (NTN). The UE may receive system information associated with validation of parameters for a CG-SDT on the NTN. The UE may transmit an SDT to a network entity of the NTN using one or more of the parameters. Numerous other aspects are described.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to PCT Patent Application No. PCT / CN2022 / 075756, entitled "SMALL DATA TRANSMISSION CONFIGURATION FOR NON-TERRESTRIAL NETWORK," filed on February 10, 2022, which is hereby assigned to the assignee of this application. The disclosure of the prior application is considered part of this patent application and is incorporated by reference into this patent application.

[0002] Aspects of the present disclosure generally relate to techniques and apparatus for using small data transmission configurations for wireless communications and non-terrestrial networks. [Background technology]

[0003]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may utilize multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0004]

[0004] A wireless network may include one or more base stations that support communication for a single user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink and uplink communications. "Downlink" (or "DL") refers to the communication link from a base station to a UE, and "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0005]

[0005] The above multiple access techniques have been adopted in various telecommunication standards to provide a common protocol that allows different UEs to communicate on a city, national, regional, and / or global scale. 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 through improved spectral efficiency, reduced costs, improved services, and new spectrum utilization, as well as better integration with other open standards through the use of orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, 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 support for beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0006]

[0006] Certain aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a UE-specific CG-SDT configuration with parameters specific to a configured grant (CG) small data transmission (SDT) in a non-terrestrial network (NTN). The method may include receiving system information associated with validation of the parameters for the CG-SDT on the NTN. The method may include transmitting the SDT to a network entity of the NTN using one or more of the parameters.

[0007]

[0007] Some aspects described herein relate to a method of wireless communication performed by a network entity of a NTN. The method may include transmitting a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The method may include transmitting system information associated with validation of the parameters for the CG-SDT on the NTN. The method may include receiving an SDT based at least in part on one or more of the parameters.

[0008]

[0008] Some aspects described herein relate to a 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 UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The one or more processors may be configured to receive system information associated with validating parameters for the CG-SDT on the NTN. The one or more processors may be configured to transmit an SDT to a network entity of the NTN using one or more of the parameters.

[0009]

[0009] Some aspects described herein relate to a network entity for wireless communications. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The one or more processors may be configured to transmit system information associated with validation of parameters for the CG-SDT on the NTN. The one or more processors may be configured to receive an SDT based at least in part on one or more of the parameters.

[0010]

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive system information associated with validation of parameters for the CG-SDT on the NTN. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit an SDT to a network entity of the NTN using one or more of the parameters.

[0011]

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit system information associated with validation of parameters for the CG-SDT on the NTN. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to receive an SDT based at least in part on one or more of the parameters.

[0012]

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The apparatus may include means for receiving system information associated with validating the parameters for the CG-SDT on the NTN. The apparatus may include means for transmitting the SDT to a network entity of the NTN using one or more of the parameters.

[0013]

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The apparatus may include means for transmitting system information associated with validation of parameters for the CG-SDT on the NTN. The apparatus may include means for receiving an SDT based at least in part on one or more of the parameters.

[0014]

[0014] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, wireless communication devices, and / or processing systems substantially as described herein with reference to and as illustrated by the drawings and specification.

[0015]

[0015] The above outlines rather broadly the features and technical advantages of the disclosed examples in order to better understand the following "Description of the Preferred Embodiments". Additional features and advantages are set forth below. The concepts and examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures are within the scope of the appended claims. The nature of the concepts disclosed herein, both their organization and the manner of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for the purpose of illustration and description, and is not intended as a definition of the limits of the claims.

[0016]

[0016] Although aspects are described in this disclosure by illustrating some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects may be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital applications (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is contemplated that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed deployments, and / or end user devices of various sizes, shapes, and configurations. [Brief description of the drawings]

[0017]

[0017] In order to be able to understand in detail the above-listed features of the present disclosure, a more detailed description, briefly summarized above, may be obtained by referring to the embodiments, some of which are shown in the attached drawings. However, it should be noted that the attached drawings show only certain exemplary embodiments of the disclosure, and therefore should not be considered as limiting the scope of the disclosure, since the description may be found in other equally effective embodiments. The same reference signs in different drawings may identify the same or similar elements. [Figure 1]

[0018] FIG. 1 illustrates an example of a wireless network in accordance with the present disclosure. [Diagram 2]

[0019] FIG. 1 illustrates an example of network entities in communication with a user equipment (UE) in a wireless network in accordance with the present disclosure. [Diagram 3]

[0020] FIG. 2 illustrates an example of a non-aggregated base station in accordance with the present disclosure. [Figure 4]

[0021] 1 illustrates an example of a regenerative satellite deployment and an example of a transparent satellite deployment in a non-terrestrial network (NTN) according to the present disclosure. [Diagram 5]

[0022] FIG. 1 illustrates an example of transmitting a configured grant small data transmission (CG-SDT) associated with a four-step random access channel procedure according to the present disclosure. [Figure 6]

[0023] FIG. 1 illustrates an example of parameters that may be included in a CG-SDT configuration, according to the present disclosure. [Figure 7]

[0024] 1 illustrates an example of commands and activation timing in accordance with some aspects of the present disclosure. [Figure 8]

[0025] FIG. 2 illustrates an example of a timeline for providing configuration and system information in accordance with the present disclosure. [Figure 9]

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

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

[0028] FIG. 1 is an illustration of an exemplary apparatus for wireless communication in accordance with the present disclosure. [Figure 12]FIG. 1 is an illustration of an exemplary apparatus for wireless communication in accordance with the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018]

[0029] Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. However, the disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the disclosure is intended to encompass any aspect of the disclosure disclosed herein, whether implemented independently or in combination with any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects described herein. In addition, the scope of the disclosure is intended to encompass such an apparatus or method that is implemented using other structure, functionality, or structure and functionality in addition to or excluding various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein can be embodied by one or more elements of a claim.

[0019]

[0030] Several aspects of a telecommunications system are now presented with reference to various apparatus and techniques that are described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0020]

[0031] Although aspects may be described herein using terminology commonly associated with 5G or New Radio (NR) radio access technology (RAT), aspects of the disclosure may be applicable to other RATs, such as 3G RATs, 4G RATs, and / or RATs following 5G (e.g., 6G).

[0021]

[0032] FIG. 1 illustrates an example of a wireless network 100 in accordance with the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may include one or more network entities, such as base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and / or other network entities. The base stations 110 are network entities that communicate with the UEs 120. The base stations 110 (which may be referred to as BSs) may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, and / or transmission reception points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving this coverage area, depending on the context in which the term is used.

[0022]

[0033] A base station 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 few kilometers in radius) and may allow unrestricted access by UEs 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 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 UEs 120 with an association with a femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. 1, BS 110a may be a macro base station for a macro cell 102a, BS 110b may be a pico base station for a pico cell 102b, and BS 110c may be a femto base station for a femto cell 102c. A base station may support one or multiple (e.g., three) cells.

[0023]

[0034] In some examples, the cells may not necessarily be fixed, and the geographic area of ​​the cells may move according to the location of the base station 110 that is mobile (e.g., a mobile base station). In some examples, the base stations 110 may interconnect with each other and / or with one or more other base stations 110 or network entities in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0024]

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

[0025]

[0036] The wireless network 100 may include one or more relay stations. A relay station is a network entity that may receive a transmission of data from an upstream station (e.g., a network entity or a UE 120) and send a transmission of data to a downstream station (e.g., a UE 120 or a network entity). A relay station may be a UE 120 that may relay a transmission for another UE 120. In the example shown in FIG. 1, a BS 110d (e.g., a relay base station) may communicate with a BS 110a (e.g., a macro base station) and a UE 120d to facilitate communication between the BS 110a (e.g., a macro base station) and the UE 120d. A base station 110 that relays communication may be referred to as a relay station, a relay base station, a repeater, etc.

[0026]

[0037] Wireless network 100 may be a heterogeneous network with network entities including different types of BSs, such as, for example, macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different susceptibility to interference within wireless network 100. For example, macro base stations may have high transmit power levels (e.g., 5-40 Watts), while pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1-2 Watts).

[0027]

[0038] Network controller 130 may couple to or communicate with a set of network entities and may provide coordination and control for these network entities. Network controller 130 may communicate with base stations 110 via backhaul communication links. The network entities may communicate with each other directly or indirectly via wireless or wireline backhaul communication links.

[0028]

[0039] In some aspects, as shown, the cells may be provided by network entities (e.g., base stations 110) of a non-terrestrial network (NTN). As used herein, a "non-terrestrial network" may refer to a network to which access is provided by a non-terrestrial base station, such as a base station on board a satellite, a balloon, an airship, an airplane, an unmanned aerial vehicle, and / or a high altitude platform station. A network entity in an NTN (NTN network entity) may use polarization. For example, a network entity in a satellite 135 (NTN network entity) may transmit communications to a UE 120 using circular polarization 136 or linear polarization 138. Circular polarization occurs when the leading edge of the electric field of an electromagnetic wave at a fixed point in space makes a circle, and the electromagnetic wave may be formed by superimposing two orthogonal linear polarizations that are equal in amplitude and have a phase difference of 90 degrees. The circular polarization may be right-hand circular polarization (RHCP) or left-hand circular polarization (LHCP). Linear polarization occurs when the electric field tip of an electromagnetic wave at a fixed point in space oscillates along a straight line with time.

[0029]

[0040] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be fixed or mobile. The UEs 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. The UEs 120 may be a cellular telephone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, a smart clothing, a smart glasses, a smart wristband, a 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, industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate over a wireless medium.

[0030]

[0041] Some UEs 120 may be considered as machine-type communication (MTC) UEs or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and / or a location tag that may communicate with a network entity, 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 narrowband IoT (NB-IoT) devices. Some UEs 120 may be considered as customer premises equipment. The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled to each other. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0031]

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

[0032]

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

[0033]

[0044] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, etc. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands are defined as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that FR1 is often referred to (interchangeably) as a "sub-6 GHz" band in various documents and papers, although a portion of FR1 is higher than 6 GHz. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as a "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) defined as a "millimeter wave" band by the International Telecommunications Union (ITU).

[0034]

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

[0035]

[0046] With the above examples in mind, it should be understood that, unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specified, it should be understood that terms such as "millimeter wave" as used herein may broadly refer to frequencies that may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, may include mid-band frequencies, or may be within the EHF band. It is contemplated that the frequencies included within 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.

[0036]

[0047] In some aspects, the UE 120 may include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 may receive a UE-specific CG-SDT configuration with parameters specific to a configured grant (CG) small data transmission (SDT) in the NTN. The communications manager 140 may receive system information associated with validation of parameters for the CG-SDT on the NTN and transmit the SDT to a network entity of the NTN using one or more of the parameters. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0037]

[0048] In some aspects, a network entity (e.g., base station 110, satellite 135) may include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 may transmit a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The communications manager 150 may transmit system information associated with validation of parameters for the CG-SDT on the NTN and receive an SDT based at least in part on one or more of the parameters. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0038]

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

[0039]

[0050] 2 illustrates an example network entity 200 (e.g., base station 110) in wireless network 100 communicating with UE 120 in accordance with the present disclosure. Base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas, where T≧1. UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas, where R≧1.

[0040]

[0051] At the base station 110, a transmit processor 220 may receive data intended for a UE 120 (or set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(es) selected for the UE 120 and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., related to semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or higher layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for a reference signal (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and a synchronization signal (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). The PSS / SSS may include a per-cell PSS / SSS for MTC devices and a NB PSS (NPSS) / NB SSS (NSSS) for NB-IoT devices.A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), denoted as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (denoted as MOD) of modem 232. Each modem 232 may use a separate modulator component to process its respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a separate modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a downlink signal. Modems 232a-t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a-t. Base station 110 may be an NTN network entity located at a terrestrial location or a non-terrestrial location (e.g., satellite 135).

[0041]

[0052] At the UE 120, a set of antennas 252 (depicted as antennas 252a through 252r) may receive downlink signals from the base station 110 and / or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), depicted as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (depicted as DEMOD) of the modems 254. Each modem 254 may use a separate demodulator component to condition (e.g., filter, amplify, down-up convert, 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 modems 254, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control 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 examples. In some examples, one or more components of the UE 120 may be included within a housing 284.

[0042]

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

[0043]

[0054] One or more antennas (e.g., antennas 234a-t and / or antennas 252a-r) may include or be contained 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, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components of FIG.

[0044]

[0055] 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 precoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to a network entity. 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 the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (eg, with reference to FIGS. 4-12).

[0045]

[0056] At a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232, denoted as DEMOD), detected by MIMO detector 236, if applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide decoded data to a data sink 239 and decoded control information to controller / processor 240. The network entity may include a communication unit 244 and may communicate with network controller 130 via the communication unit 244. The network entity may include a scheduler 246 for scheduling one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity may include a modulator and a demodulator. In some examples, the network entity includes a transceiver. The transceiver may include any combination of antenna(s) 234, modem(s) 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 aspects of any of the methods described herein (e.g., with reference to FIGS. 4-12).

[0046]

[0057] A controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or any other component(s) of FIG. 2 may perform one or more techniques associated with using the configuration of CG-SDT in the NTN, as described in more detail elsewhere herein. In some aspects, the network entity is a network entity on the Earth's surface or a satellite (e.g., 135). For example, controller / processor 240 of base station 110, controller / processor 280 of UE 120, and / or any other component(s) of FIG. 2 may perform or direct the operation of, for example, process 900 of FIG. 9, process 1000 of FIG. 10, and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for the network entity 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 by one or more processors of the network entity and / or UE 120 (e.g., directly or after compiling, translating, and / or interpreting), may cause the one or more processors, UE 120, and / or network entity to perform or direct the operation of, for example, process 900 of FIG. 9, process 1000 of FIG. 10, and / or other processes as described herein. In some examples, executing the instructions may include running the instructions, translating the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0047]

[0058] In some aspects, the UE 120 includes means for receiving a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN, means for receiving system information associated with validating the parameters for the CG-SDT on the NTN, and / or means for transmitting the SDT to a network entity of the NTN using one or more of the parameters. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0048]

[0059] In some aspects, the network entity 110 includes means for transmitting a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN, means for transmitting system information associated with validating the parameters for the CG-SDT on the NTN, and / or means for receiving an SDT based at least in part on one or more of the parameters. In some aspects, the means for causing the network entity 110 to perform the operations described herein may include, for example, one or more of the communications manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antennas 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0049]

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

[0050]

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

[0051]

[0062] FIG. 3 is a diagram illustrating an example of a non-aggregated base station 300 in accordance with the present disclosure.

[0052]

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

[0053]

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

[0054]

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

[0055]

[0066] The unaggregated base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link or indirectly with the core network 320 via one or more unaggregated base station units (such as a quasi-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 CUs 310 may communicate with one or more DUs 330 via separate midhaul links, such as an F1 interface. The DUs 330 may communicate with one or more RUs 340 via separate fronthaul links. The fronthaul, midhaul, and backhaul links may be generally referred to as "communication links." The RUs 340 may communicate with respective UEs 120 via one or more RF access links. In some aspects, a UE 120 may be served by multiple RUs 340 simultaneously. The DU 330 and the RU 340 are also referred to as "O-RAN DU (O-DUs)" and "O-RAN RU (O-RUs)", respectively. The network entity may include a CU, a DU, a RU, or any combination of a CU, a DU, and a RU. The network entity may include one or more components of a non-aggregated base station, such as a non-aggregated base station, or any combination of a CU, a DU, a RU, or a CU, a DU, and a RU. The network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface for or provide services to a UE, a mobile station, a sensor / actuator, or other wireless device.

[0056]

[0067] Each of the units, i.e., CU 310, DU 330, RU 340, quasi-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 transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to or from one or more of the other units over a wired transmission medium. In addition, a unit may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive and / or transmit signals to or from one or more of the other units over a wireless transmission medium.

[0057]

[0068] In some aspects, the CU 310 may host one or more upper layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP unit, when implemented in an O-RAN configuration, may communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface. The CU 310 may be implemented to communicate with the DU 330, as necessary, for network control and signaling.

[0058]

[0069] The DU 330 may correspond to a logical unit including 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 medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.), at least in part according to a functional division such as that defined by 3GPP. In some aspects, the DU 330 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with a control function hosted by the CU 310.

[0059]

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

[0060]

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

[0061]

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

[0062]

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

[0063]

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

[0064]

[0075] FIG. 4 illustrates an example NTN regenerative satellite deployment 400 and an example transparent satellite deployment 410 in accordance with the present disclosure.

[0065]

[0076] Example 400 illustrates a regenerative satellite deployment. In example 400, UE 120 is served by satellite 420 (e.g., satellite 135) via service link 430. For example, satellite 420 may include BS 110 (e.g., BS 110a) or gNB. In some aspects, satellite 420 may be referred to as a non-terrestrial base station, a regenerative repeater, an on-board processing repeater, and / or an NTN entity, etc. In some aspects, satellite 420 may demodulate an uplink radio frequency signal and modulate a baseband signal derived from the uplink radio frequency signal to generate a downlink radio frequency transmission. Satellite 420 may transmit a downlink radio frequency signal on service link 430. Satellite 420 may provide a cell covering UE 120.

[0066]

[0077] Example 410 illustrates a see-through satellite deployment, also referred to as a bent-pipe satellite deployment. In example 410, UE 120 is served by satellite 440 via service link 430. Satellite 440 may also be considered an NTN entity. Satellite 440 may be a see-through satellite. Satellite 440 may relay signals received from gateway 450 via feeder link 460. For example, the satellite may receive an uplink radio frequency transmission and transmit a downlink radio frequency transmission without demodulating the uplink radio frequency transmission. In some aspects, the satellite may frequency convert the uplink radio frequency transmission received on service link 430 to the frequency of the uplink radio frequency transmission on feeder link 460 and amplify and / or filter the uplink radio frequency transmission. In some aspects, the UE 120 shown in examples 400 and 410 may be associated with Global Navigation Satellite System (GNSS) capabilities, Global Positioning System (GPS) capabilities, etc., although not all UEs have such capabilities. A satellite 440 may provide a cell covering the UE 120.

[0067]

[0078] The service link 430 may include a link between the satellite 440 and the UE 120 and may include one or more of an uplink or a downlink. The feeder link 460 may include a link between the satellite 440 and the gateway 450 and may include one or more of an uplink (e.g., from the UE 120 to the gateway 450) or a downlink (e.g., from the gateway 450 to the UE 120).

[0068]

[0079] The feeder link 460 and the service link 430 may each be subject to Doppler effects due to the movement of the satellites 420 and 440 and possibly the movement of the UE 120. These Doppler effects may be significantly greater than those in terrestrial networks. The Doppler effects on the feeder link 460 may be compensated to some extent, but may still be associated with some amount of uncompensated frequency error. Furthermore, the gateway 450 may have residual frequency errors and / or the satellites 420 / 440 may have on-board frequency errors. These sources of frequency error may cause the downlink frequency received at the UE 120 to deviate from the target downlink frequency.

[0069]

[0080] The satellites 420 and 440 may be satellites in geostationary orbit (GSO) or geosynchronous equatorial orbit (GEO), which may be, for example, 36,000 km above the Earth. Although the velocity of the satellite relative to the Earth may be negligible, it has a propagation delay of more than 500 milliseconds (ms), compared to 25 ms for a low earth orbit (LEO) satellite, which is 600 km above the Earth. In NTNs, where the distance between the UE 120 and the satellite may be greater than 600 km, path loss changes may not be properly reflected in the propagation delay changes. It is expected that the UE 120 can autonomously pre-compensate for the propagation delay to a reference point, and thus timing advance (TA) verification may be performed more directly, rather than relying on an indirect parameter such as RSRP. The UE 120 may use the TA for timing alignment of communications due to propagation delay. The TA may inform the UE 120 to transmit communications earlier than the TA amount. If the propagation distance between the UE 120 and the network entity changes, the TA may need to be verified. In addition, if the satellite is in a non-geostationary orbit (NGSO), the satellite may not always be available to the UE 120.

[0070]

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

[0071]

[0082] 5 is a diagram illustrating an example of transmitting a CG-SDT associated with a four-step random access channel (RACH) procedure according to the present disclosure. As shown in FIG. 5, a network entity 510 (e.g., base station 110, satellite 420, satellite 440) and a UE 520 (e.g., UE 120) may communicate with each other to transmit an SDT as part of a four-step RACH procedure over the NTN.

[0072]

[0083] CG-SDT resources may be made available across cells in a satellite depending on the deployment. According to various aspects described herein, the UE 520 may be configured for CG-SDT for the NTN. For example, as indicated by reference numeral 525, the network entity 510 may transmit a CG-SDT configuration for the NTN. The CG-SDT may include parameters such as a MAC apply TA Kmac for delaying application of a downlink configuration indicated by a MAC control element (MAC CE). The duration of Kmac may include a duration between the reception of an activation command (e.g., downlink control information (DCI)) by the UE 520 and application of the activation command by the UE 520. The parameters may include a time offset Koffset for delaying a RACH procedure initiated by a physical downlink control channel (PDCCH) communication (e.g., DCI) and delaying an uplink transmission scheduled by a CG. This Koffset may be specific to the CG-SDT on the NTN. Koffset may be cell-common or UE-specific. The CG-SDT may be referred to as "pre-configured uplink resources (PUR)" in some access networks.

[0073]

[0084] As indicated by reference numeral 530, the network entity 510 may transmit system information for verifying parameters for the NTN. The system information may include, for example, timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset.

[0074]

[0085] As indicated by reference numeral 535, the network entity 510 may verify parameters using system information. This may include, for example, verifying MAC TA Kmac and time offset Koffset using timing relationship verification information. Verifying may include performing measurements and determining whether the measurements satisfy one or more RSRP thresholds (e.g., minimum RSRP, maximum RSRP). Verifying may also include determining whether the measurements are made during a time interval or a timer.

[0075]

[0086] The UE 520 may perform a RACH procedure to establish an RRC connection with the network entity 510. The UE 520 may be in an inactive state, such as an RRC inactive state, to conserve battery power and network resources during times of infrequent data traffic. An "inactive state" may refer to a UE operating in an inactive communication mode. To re-enter an active state, the UE 520 may perform a RACH procedure. The RACH procedure may involve signaling in two steps (a two-step RACH procedure) or four steps (a four-step RACH procedure). As indicated by reference numeral 540, in a first step of the four-step RACH procedure, the UE 520 may transmit a random access message (RAM), which may include a preamble (sometimes referred to as a random access preamble, a PRACH preamble, or a RAM preamble). The message including the preamble may be referred to as a message 1, msg1, MSG1, a first message, or an initial message in the four-step RACH procedure. The random access message may include a random access preamble identifier.

[0076]

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

[0077]

[0088] In some aspects, as part of a second step of the four-step RACH procedure, the network entity 510 may transmit a PDCCH communication for the RAR. The PDCCH communication (e.g., DCI) may schedule a physical downlink shared channel (PDSCH) communication that includes the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication. Also as part of the second step of the four-step RACH procedure, the network entity 510 may transmit a PDSCH communication for the RAR as scheduled by the PDCCH communication. The PDCCH may include an MTC PDCCH (MPDCCH) for MTC devices or an NB PDCCH (NPDCCH) for NB-IoT devices. The PDSCH may include an NB PDSCH (NPDSCH) for NB-IoT devices.

[0078]

[0089] As indicated by reference numeral 550, the UE 520 may transmit an RRC connection request message. The RRC connection request message may be referred to as message 3, msg3, MSG3, or the third message of the four-step RACH procedure. In some aspects, the RRC connection request may include a UE identifier, uplink control information (UCI), and / or a physical uplink shared channel (PUSCH) communication (e.g., RRC connection request). The PUSCH may include NB PUSCH (NPUSCH) format 1 for NB-IoT devices. The physical uplink control channel (PUCCH) may include NPUSCH format 2 for NB-IoT devices. The UE 520 may transition between different modes based at least in part on various commands and / or communications received from the network entity 510, and the UE 520 may transmit an RRC resume request (RRCResumeRequest) in msg3 to transition from an RRC inactive state to an RRC active state. The RRC Resume Request may also establish some security for messages from the UE 520 to the network entity 510 by verifying the identity of the UE 520. The UE 520 may include data such as the SDT in msg3 with the RRC Resume Request. The SDT may be a smaller amount of data that the UE 520 can transmit even if it is not fully connected. In many applications, the UE 520 may generate only a small amount of data during a burst of a data session. Examples of such applications include enhanced mobile broadband (eMBB) communications, Internet of Things (IoT) communications, instant messaging applications, social media applications, and / or wearable device applications. The SDT may be configured or scheduled by the CG.The UE 520 may establish an SDT PDCP and transmit SDT resource blocks (RBs) configured for small data.

[0079]

[0090] When data arrives for data radio bearers (DRBs) or signal radio bearers (SRBs) (i.e., SDT RBs) for which SDT is enabled, the criteria for selecting between SDT and non-SDT procedures includes at least the UE 520 checking whether the amount of available data is less than a data amount threshold, and the UE 520 will perform carrier selection for SDT if both normal uplink carrier (NUL) and supplemental uplink carrier (SUL) are configured and SDT resources are configured. The UE 520 will determine whether the RSRP is greater than or equal to a configured RSRP threshold for SDT. The RSRP threshold is used to select between SDT and non-SDT procedures, if configured. The RSRP threshold is also used to select between SDT and non-SDT procedures, and is used for both CG-SDT and RA-SDT. The data amount threshold (for selecting between SDT and non-SDT procedures) is the same for CG-SDT and RA-SDT. The RSRP threshold for carrier selection is SDT-specific (i.e., configured separately for the SDT). The RSRP threshold for random access (RA) type selection is SDT-specific (i.e., configured separately for the SDT).

[0080]

[0091] If the above criteria are deemed to be met, if the CG-SDT resource is configured and valid on the selected uplink carrier, and if the UE 520 can find the RSRP of the synchronization signal block (SSB) above the configured RSRP threshold of the CG-SDT criteria, the UE 520 selects the CG-SDT and initiates RRC resumption for SDT using the selected CG-SDT resource. If not, the UE 520 checks whether the RA-SDT resource is configured and valid on the selected UL carrier. This check is similar to the normal RACH resource selection and check. If the RA-SDT criteria are deemed to be met, the UE 520 selects the RA-SDT and performs the RA-SDT. The UE 520 is to perform the RA type selection using the SDT-specific RSRP threshold (e.g., either 4-step RA-SDT or 2-step RA-SDT). If not, the UE 520 may perform normal RRC resumption (i.e., not perform the SDT). The physical broadcast channel (PBCH) of the SSB may include a per-cell PBCH for MTC devices or a per-cell NB PBCH (NPBCH) for NB IoT devices.

[0081]

[0092] For an initial CG-SDT transmission, the UE 520 may not select any SSB if none of the SSBs' RSRPs are above the RSRP threshold. The UE 520 may select the RA-SDT if the RA-SDT criteria are met.

[0082]

[0093] As indicated by reference numeral 555, the network entity 510 may transmit an RRC connection setup message. The RRC connection setup message may be referred to as message 4, msg4, MSG4, or the fourth message of the four-step RACH procedure. In some aspects, the RRC connection setup message may include a detected UE identifier, a timing advance value, and / or contention resolution information. In some aspects, if the UE 520 performs a two-step RACH procedure, msg1 and msg3 may be combined into a single message referred to as "msgA" and msg2 and msg4 may be combined into a single message referred to as "msgB". After completion of the four-step (or two-step) RACH procedure, the UE 520 may transmit and receive data.

[0083]

[0094] As indicated by reference numeral 560, the UE 520 may transmit an SDT using the CG-SDT parameters for the NTN. This may be done during an SDT subsequent data transmission period 562 following a RACH procedure or configuration of an uplink grant. In subsequent data transmissions (after successful contention resolution), the UE 520 may use the CG to transmit data or to monitor dynamic grants (DGs) with the cell RNTI (C-RNTI) in a separate common search space (CSS) (if configured) in the RA-SDT. During the SDT subsequent data transmission period, the network entity 510 may enable the UE 520 to transmit SDT type data during an RRC inactive or RRC idle state without requiring the UE 520 to enter an RRC connected or RRC active state. The UE 520 may transmit SDT type data during the SDT subsequent data transmission period from a buffer that holds SDT type data. The UE 520 may transmit data until the buffer is empty. The network entity 510 may transmit downlink data in response to the uplink data, as indicated by reference numeral 565. The UE 520 may transmit more uplink data, which may or may not include SDT, as indicated by reference numeral 570. The RRCRelease message may be sent last to terminate the SDT procedure from the RRC perspective, as indicated by reference numeral 575.

[0084]

[0095] The configuration of CG resources for UE uplink small data transfer may be included in the RRCRelease message. The RRCRelease message is also used to reconfigure or release CG-SDT resources while the UE is RRC inactive. The configuration of CG resources may include Type 1 CG configuration. Multiple CG-SDT configurations per carrier in RRC inactive state may be supported by network configuration. In the case of CG-SDT, subsequent data transmissions may use CG resources or DG. The UE 520 may support retransmissions with DG for CG-SDT.

[0085]

[0096] During the subsequent new CG transmission phase, for the purpose of CG resource selection, the UE 520 re-evaluates the SSB for the subsequent CG transmission. Since there may be no new UE-specific RNTI for the SDT, the UE 520 may monitor the PDCCH communication addressed by the C-RNTI in the CG-SDT. The C-RNTI may be pre-configured in the RRC connection. A cell specific RNTI (CS-RNTI) based dynamic retransmission mechanism may be reused for the CG-SDT. The UE 520 may start a window after the CG / DG transmission for the CG-SDT. The UE 520 may support multiple hybrid automatic repeat request (HARQ) processes for the uplink CG-SDT. The CG-SDT resources may be configured on both the NUL and the SUL. The UL carrier selection is performed before the CG-SDT selection. The UE 520 may release the CG-SDT resources upon expiration of the SDT TA timer (TAT-SDT) in RRC inactivity. When the UE 520 initiates an RRC resumption procedure from another cell different from the cell where the RRCRelease was received, the UE 520 shall release the CG-SDT resources.

[0086]

[0097] By providing and verifying parameters in the NTN-specific CG-SDT configuration, the UE 520 may transmit the SDT in the NTN. The parameters may improve timing alignment and improve communication between the UE 520 and the network entity 510. The improved communication saves processing and signaling resources.

[0087]

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

[0088]

[0099] FIG. 6 is a diagram illustrating an example of parameters 600 that may be included in a CG-SDT configuration in accordance with this disclosure.

[0089]

[0100] Example 600 illustrates a UE 520 and an example location of the network entity 510 relative to a satellite 610 (which may also be a network entity 510) and a relay station 620. The satellite 610 may be a distance h above the Earth and a distance g away from the relay station 620. The network entity 510 and the relay station may be separated by a distance β. The satellite 610 may be at an angle α and a distance d from the UE 520.

[0090]

[0101] As mentioned above, the CG-SDT configuration may include parameters such as Koffset. Koffset may be configured in the system information and used in initial access, at least in the cell-specific Koffset configuration used in all beams of the cell. The UE-specific Koffset may be provided and updated by the network entity 510 with the MAC CE. The MAC CE may provide a differential UE-specific Koffset value. The complete UE-specific Koffset value may be equal to the cell-specific Koffset value minus the differential UE-specific Koffset value. When the UE 520 is not provided with a Koffset value other than the one signaled in the system information, the Koffset value signaled in the system information may be used for all timing relationships that require Koffset extension.

[0091]

[0102] The Koffset value signaled in the system information may be used for the transmission timing of PUSCH scheduled by RAR or fallback RAR grant. The Koffset value may be used for the transmission timing of Msg3 retransmission scheduled by DCI format 0_0 with CRC scrambled by temporary cell RNTI (TC-RNTI). The Koffset value may be used for the transmission timing of HARQ acknowledgement (HARQ-ACK) on PUCCH for contention resolution PDSCH scheduled by DCI format 1_0 with CRC scrambled by TC-RNTI. The Koffset value may be used for the transmission timing of HARQ-ACK on PUCCH for MsgB scheduled by DCI format 1_0 with cyclic redundancy check (CRC) scrambled by MsgB-RNTI.

[0092]

[0103] Koffset may be applied to indicate the first transmission opportunity of PUSCH in configured grant type 2, similarly as Koffset is applied to the transmission timing of PUSCH scheduled by DCI. The Koffset value signaled in the system information may be used for PRACH timing relationship with PDCCH order. The unit of Koffset may be the amount of slots for a given subcarrier spacing. In case of a random access procedure initiated by a PDCCH order received in a downlink slot, the UE 520 may determine the next available PRACH occasion after the uplink slot after Koffset of the downlink slot to transmit the ordered PRACH.

[0093]

[0104] Regarding the NTN CG-SDT configuration, in some aspects, the CG-SDT parameters may be specific to the NTN and / or may be added to the parameters for the terrestrial network. For example, the parameters for TA verification may include NTN-specific RSRP thresholds. These RSRP thresholds may be different from and / or added to the RSRP thresholds for the terrestrial network. The NTN-specific parameters may be obtained in a UE-specific, cell-specific, or satellite-specific manner. The Koffset for the CG-SDT in the NTN may be used for SDT transmissions and for subsequent transmissions after the initial transmission of the CG-SDT (e.g., new or retransmissions of PUCCH and PUSCH scheduled by PDCCH in the CG-SDT search space).

[0094]

[0105] There may be several options for Koffset for CG-SDT in NTN. As a first option, the cell-common Koffset (provided by the system information) may be used for subsequent transmissions after the first transmission of CG-SDT. As a second option, Koffset may be UE-specific configured and stored while UE 520 is in RRC connected mode and used for subsequent transmissions after the initial transmission. As a third option, UE 520 may be configured with a separate UE-specific Koffset for CG-SDT in the RRC release message. In either case, the network entity 510 may explicitly reconfigure Koffset in RRC inactive mode.

[0095]

[0106] Another CG-SDT configuration parameter for NTN may be Kmac, as described above. Information of Kmac may be carried in system information. The unit of Kmac may be number of slots for a given subcarrier spacing. The value of Kmac may range from 1 to 512 ms. When UE 520 is not provided with a Kmac value, UE 520 may assume Kmac=0. If UE 520 is provided with a Kmac value, when UE 520 transmits a PUCCH with HARQ-ACK information in uplink slot n corresponding to a PDSCH carrying a MAC CE command in slot x on the downlink configuration, UE 520 action based on the downlink configuration may be to set the PUCCH with HARQ-ACK information in uplink slot n corresponding to a PDSCH carrying a MAC CE command in slot x on the downlink configuration.

[0096]

number

[0097] may be applied starting from the first slot after, where μ is the subcarrier spacing (SCS) configuration for the PUCCH.

[0098]

[0107] 7 illustrates an example 700 of command and activation timing according to the present disclosure. The example 700 illustrates a MAC command received in slot x, HARQ-ACK information in slot n, and activation of the MAC command in slot m. The example 700 illustrates an example of applying Kmac for MAC application timeline alignment between the UE 520 and the network entity 510 in the NTN, which results in activation in slot M. For CG-SDT transmission and subsequent transmissions, the cell-wide Kmac (provided in the system information) may be used.

[0099]

[0108] Kmac may indicate a scheduling offset other than Koffset. For UE actions based on downlink configuration indicated by MAC CE commands in PDSCH, Kmac may not be required if downlink and uplink frame timing are aligned at the gNB. For UE actions based on uplink configuration indicated by MAC CE commands in PDSCH, Kmac may be required if downlink and uplink frame timing are not aligned at the gNB. For UE actions based on downlink configuration indicated by MAC CE commands in PDSCH, Kmac may not be required. Note that this does not preclude identifying exceptional MAC CE timing relationship(s) that may or may not require Kmac.

[0100]

[0109] The parameters may include or be related to TA, where TA=(N TA +N {TA,UE-specific} +N {TA,common} +N {TA,offset} )xT c It can be calculated as follows: N {TA,offset}may depend on the band and LTE / NR coexistence, and is specified in 3GPP Technical Specification (TS) 38.213 Section 4.2. c is specified in TS 38.211, section 4.1. {TA,UE-specific} is the UE self-estimated TA for pre-compensating for the service link delay, which is calculated using the UE position and serving satellite ephemeris. {TA,offset} If so, the UE 520 may use the indicated higher layer common TA parameters. If configured, the UE 520 may {TA,common} The one-way propagation time (Delay_common) used for the calculation can be calculated as follows:

[0101]

number

[0102] is satellite 610 The distance between the uplink and downlink time synchronization reference points is divided by the speed of light. (TA,offset) To pre-compensate for the two-way transmission delay between the uplink time reference point and the satellite 610, the UE may use the Delay common Based on (t), N TA,common is derived.

[0103]

[0110] The example 600 illustrates such parameters as timing components in the NTN. For example, there may be a common TA for communication between the relay station 620 and the satellite 610. The timing between the UE 520 and the satellite 610 may include TA(t) plus Kmac. TA(t) plus Kmac is at least the common TA(K TA ), UE-specific TA(K TA,UE-specific ), Common TA(K TA,common ), Koffset(K TA,offset ) and Kmac(K mac At least some of these timing elements are unique to NTNs.

[0104]

[0111] Other parameters may include cell outage time, disabled HARQ feedback, ephemeris information, and / or polarization. The cell outage time may be the time that the cell is valid for use before the satellite mobile disables the cell. Currently, the broadcast of the cell outage time in the system information block (SIB) may only be applicable to quasi-earth fixed cells (not mobile cells), and there is currently no information on mobile cell specific details associated with using the cell outage time to assist in measurements or cell reselection. For quasi-earth fixed cells, the broadcast timing information regarding the time that the cell will stop serving the area refers to the time that the cell stops covering the current area. In some aspects, if the cell outage time is broadcast via system information, the CG-SDT resources may be disabled after the broadcast cell outage time. Furthermore, additional time offset information may be provided to the UE 520 in a cell-specific or UE-specific manner. If provided, the UE 520 may not be allowed to attempt to transmit on the PUSCH with CG-SDT after the cell outage time minus the additional time offset received by the UE 520. The SIB may include a reduced bandwidth SIB (SIB-BR) for MTC devices or a NB SIB (NSIB) for NB IoT devices.

[0105]

[0112] For a downlink HARQ process with disabled HARQ feedback, the UE 520 will not receive another set of PDSCHs or slot-aggregated PDSCHs scheduled for a given HARQ process starting a certain time after the end of reception of the last PDSCH or slot-aggregated PDSCH for that HARQ process. In some aspects, one or more of the CG-SDT HARQ process identifiers (IDs) may have HARQ feedback disabled, and the configuration may be UE specific.

[0106]

[0113] The network entity 510 may indicate polarization information for the downlink and uplink. The polarization information for the uplink may be indicated in the SIB. The UE 520 may assume the same polarization for the uplink and downlink when the uplink polarization information is not present. When polarization signaling is present in the SIB, the SIB may indicate the downlink and / or uplink polarization information using a respective polarization type parameter (e.g., RHCP, LHCP, or linear). Polarization signaling may be supported for the target serving cell in a handover command message or for non-serving cells in a radio resource management (RRM) measurement configuration. In some aspects, the network entity 510 may signal the characteristics of the uplink and / or downlink polarization to the UE 520, and the configuration may be satellite-specific and / or cell-specific (e.g., the UE 520 may obtain the information from system information).

[0107]

[0114] The parameters may include ephemeris information, which is information related to the orbits of satellites and / or celestial bodies. Other parameters include a common TA(N TA,common) and epoch time (time based on the reference time). The parameters may include a validity duration of the satellite ephemeris data configured by the network, indicating the maximum time the UE 520 can apply the satellite ephemeris without acquiring new satellite ephemeris. The UE 520 may assume that the UE 520 has lost uplink synchronization if new or additional aiding information (i.e., serving satellite ephemeris data or common TA parameters) is not available within the associated validity duration. The NTN ephemeris validity timer should be started / restarted with the configured timer validity duration at the epoch time of the aiding information (i.e., serving satellite ephemeris data). A single validity duration for both the serving satellite ephemeris and the parameters related to the common TA may be defined, if at least the parameters related to the serving satellite ephemeris and the common TA are signaled in the same SIB message. A single validity duration for both the serving satellite ephemeris and the parameters related to the common TA may be broadcast on the SIB. The UE 520 may read system information from the (satellite-specific) cells. If the validity duration expires, the UE 520 may read the system information at the beginning of the CG-SDT and before any subsequent transmissions.

[0108]

[0115] The parameters may also include cell and / or satellite information. Availability of the UE-specific configured CG-SDT may not be limited to a single cell (i.e., it may be made available in different cell(s) within the same satellite to which the UE 520 was connected when the CG-SDT was configured, or across satellites depending on the configuration). In this scenario, the UE 520 may be configured with a list of cells and / or satellites along with a set of CG-SDT parameters if adjustments are to be made when the UE 520 moves to one of the cells in the list.

[0109]

[0116] As noted above, Figures 6 and 7 are provided as examples. Other examples may differ from those described with respect to Figures 6 and 7.

[0110]

[0117] FIG. 8 illustrates an example timeline 800 for providing configuration and system information in accordance with the present disclosure.

[0111]

[0118] Example 800 shows that a network entity 510 (e.g., a gNB) may transmit a UE-specific CG-SDT configuration and periodically transmit system information for validating parameters of the CG-SDT configuration. The UE-specific CG-SDT configuration may be for a PUSCH and / or PUCCH configuration, may include a search space configuration for CG-SDT, and may include all or a portion of the validation criteria and parameters. The system information may include information related to CG-SDT validation associated with the validation criteria (e.g., ephemeris information, N TA,common ).

[0112]

[0119] In some aspects, the UE 520, if configured, may satisfy the following four verification criteria for uplink transmission of the CG-SDT: verify TA, verify timing relationship, verify link quality, and verify cell and / or satellite availability. For subsequent transmissions after the first transmission of the CG-SDT, all or some of the criteria should still be satisfied.

[0113]

[0120] Regarding TA verification, in addition to the legacy (terrestrial network) RSRP-based TA verification, ephemeris information, N TA,commonSome of the parameters may be involved, including the validity duration, , and epoch time. The UE 520 may receive system information from the (e.g., satellite-specific) cell. If the validity duration expires, the UE 520 may read the system information at the CG-SDT initial and before subsequent transmissions. Another parameter for verifying the TA may include UE location update. If the UE 520 is equipped with a Global Navigation Satellite System (GNSS), the UE 520 may update its location based on GNSS readings before transmitting in RRC inactive state. If the UE 520 is not equipped with a GNSS (e.g., NTN-IoT) and must rely on the TA obtained from the network entity 510, and if the UE 520 is configured with a timer that allows the UE 520 to apply the same TA to uplink transmissions until the configured timer expires, the UE 520 may not use the CG-SDT if the remaining time until the timer expires is less than or equal to A ms or B slots for the SCS of the bandwidth part (BWP) configured for the CG-SDT. In some embodiments, A and / or B may be configured by the network entity 510 or hard-coded in stored configuration information (per a standard). The UE 520 may reset and restart the timer when a timing advance command (TAC) is received or when the CG-SDT is reconfigured to an RRC inactive state (e.g., the timer is extended).

[0114]

[0121] The UE 520 may verify the timing relationship using the system information. The verification of the timing relationship may involve Kmac and / or Koffset, if configured and included as part of the CG-SDT verification conditions, which may be retained before the uplink transmission for the CG-SDT. If Kmac is not included as part of the verification conditions, Kmac may be signaled separately after the first transmission of the CG-SDT. For example, the UE 520 may receive a PDSCH communication that includes Kmac information, which is scheduled by a PDCCH communication in the CG-SDT search space.

[0115]

[0122] The UE 520 may verify the link quality using system information. The initial transmission on the CG-SDT may be followed by PDCCH and PDSCH communications. A link quality verification for a downlink receive RSRP threshold (e.g., + / -RSRP-threshold, the RSRP threshold used for TA verification in the terrestrial network) may be used for link quality verification. If the RSRP change relative to the reference RSRP is greater than a specified RSRP threshold, the UE 520 may not use the CG-SDT. The reference time instant at which the reference RSRP should be measured may be defined separately and may be different from the reference time instant used for the terrestrial network (e.g., the reference RSRP is updated only when the CG-SDT is configured or reconfigured).

[0116]

[0123] The UE 520 may verify link quality verification for the initial uplink transmission and subsequent transmissions (e.g., PUCCH and PUSCH communications) for CG-SDT. If the actual UE transmit power (e.g., a combination of the measured RSRP and power class (maximum transmit power)) is X decibels (dB) less than the specified or requested transmit power (configured by the network entity 510), the UE 520 may not attempt to transmit for CG-SDT. X may be separately configured and / or hard-coded in the stored configuration information for CG-SDT. Link quality verification may apply to both RA-SDT and CG-SDT, but the thresholds used may be different. Link quality verification may also include downlink and uplink polarization information.

[0117]

[0124] The UE 520 may use system information to verify cell and / or satellite availability. This may include verifying cell outage time. If the cell outage time is broadcast via system information, the UE 520 may not use CG-SDT if the remaining time until the cell service outage time is less than or equal to Y ms or Z slots for the SCS of the BWP configured for CG-SDT. Y and / or Z may be configured by the network entity 510 and / or hard-coded in the stored configuration information. In some aspects, the cell outage time is restarted when the UE 520 receives a TA command or the timer is reconfigured by RRC dedicated signaling.

[0118]

[0125] If a UE-specific configured CG-SDT is available after cell (re)selection, the UE 520 may verify the above criteria for the newly (re)selected cell and / or satellite. If the newly (re)selected cell belongs to the same satellite as the cell that configured the CG-SDT, the UE 520 may skip some of the above criteria if the criteria are common between cells.

[0119]

[0126] Depending on the satellite type (e.g., GSO, NGSO) to which the cell belongs, some of the above criteria may be defined differently. For example, if the target cell belongs to a GSO satellite, the UE 520 may be exempt from updating ephemeris information, and TA,common may be exempt from the validation requirement. Different validation criteria may be performed in different time windows, including with respect to the frequency of validation and where validation begins / ends before using CG-SDT resources.

[0120]

[0127] By using and verifying parameters of the CG-SDT configuration for the NTN, the UE 520 and the network entity 510 may improve communication and conserve resources.

[0121]

[0128] The example 800 also illustrates an initial transmission of a PUSCH CG-SDT by the UE 520 and a PDCCH communication (in the CG-SDT search space) from the network entity 510. The PDCCH communication may be for a new PUSCH transmission or a PUSCH retransmission. The PDCCH communication may be for a PDSCH communication or a PUCCH communication.

[0122]

[0129] Example 800 also illustrates subsequent transmissions and receptions after the CG-SDT. In some aspects, during subsequent transmissions after the initial transmission of the CG-SDT, uplink transmission timing requirements may be applied as if discontinuous reception (DRX) was in use. For example, UE 520 may apply incremental TA adjustments (e.g., as needed) to subsequent transmissions. This is in contrast to the initial uplink transmission timing accuracy requirements currently applied to the initial transmission of the CG-SDT.

[0123]

[0130] If the UE 520 receives a TAC during a subsequent transmission, the UE 520 may apply the TA adjustment accuracy requirement to the subsequent transmission after the TA adjustment delay after receiving the TAC. In some aspects, the UE 520 may maintain the TAC-based closed-loop TA during the subsequent transmission after receiving the TAC. The closed-loop TA may be reset at the next occasion of the CG-SDT.

[0124]

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

[0125]

[0132] 9 illustrates an example process 900 performed, for example, by a UE, in accordance with the present disclosure. The example process 900 is an example of a UE (e.g., UE 520) performing operations associated with using a CG-SDT configuration for an NTN.

[0126]

[0133] 9, in some aspects, process 900 may include receiving a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN (block 910). For example, as described above, the UE may receive (e.g., using the communications manager 1108 and / or the receiving component 1102 shown in FIG. 11) a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN.

[0127]

[0134] 9, in some aspects, the process 900 may include receiving system information associated with validating parameters for the CG-SDT on the NTN (block 920). For example, as described above, the UE may receive (e.g., using the communications manager 1108 and / or the receiving component 1102 shown in FIG. 11) system information associated with validating parameters for the CG-SDT on the NTN.

[0128]

[0135] 9, in some aspects, the process 900 may include transmitting the SDT to a network entity of the NTN using one or more of the parameters (block 930). For example, as described above, the UE (e.g., using the communications manager 1108 and / or the processing component 1104 shown in FIG. 11) may transmit the SDT to a network entity of the NTN using one or more of the parameters.

[0129]

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

[0130]

[0137] In a first aspect, receiving system information associated with CG-SDT validation includes periodically receiving system information associated with CG-SDT validation.

[0131]

[0138] In a second aspect, alone or in combination with the first aspect, the parameters include a MAC application TA Kmac for delaying application of the downlink configuration indicated by the MAC CE.

[0132]

[0139] In a third aspect, alone or in combination with one or more of the first and second aspects, the parameters include a time offset Koffset for delaying a RACH procedure initiated by a PDCCH communication and for delaying an uplink transmission scheduled by a CG, the time offset Koffset being specific to a CG-SDT on the NTN.

[0133]

[0140] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the time offset Koffset is cell-wide.

[0134]

[0141] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the time offset Koffset is UE specific.

[0135]

[0142] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset, and the process 900 includes verifying the MAC TA Kmac and the time offset Koffset using the timing relationship verification information.

[0136]

[0143] In the seventh aspect alone or in combination with one or more of the first to sixth aspects, the parameters include ephemeris information and a common TA.

[0137]

[0144] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the system information includes TA verification information for verifying the ephemeris information or the common TA, and the process 900 includes verifying the ephemeris information or the common TA using the TA verification information.

[0138]

[0145] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, verifying the ephemeris information or the common TA includes using the TA verification information to verify an epoch time or validity duration of the ephemeris information or the common TA for the CG-SDT based at least in part on one or more of the location of the UE or a timer.

[0139]

[0146] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the parameters include parameters for disabling a HARQ CG-SDT process on the NTN.

[0140]

[0147] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the parameters include polarization parameters for CG-SDT on the NTN.

[0141]

[0148] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the process 900 includes receiving an indication of a time offset that is cell-specific or UE-specific, the parameter including a cell outage time during which the serving cell is valid for CG-SDT on the NTN, and the UE is restricted from transmitting CG-SDT on the NTN after the end of a time that is the cell outage time minus the time offset.

[0142]

[0149] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the parameters include cell parameters configured for CG-SDT on the NTN or satellite parameters configured for CG-SDT on the NTN.

[0143]

[0150] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the system information includes TA verification information specific to the CG-SDT, and the process 900 includes using the TA verification information to verify a TA for the CG-SDT on the NTN.

[0144]

[0151] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the system information includes link quality verification information for verifying link quality for the CG-SDT on the NTN, and the process 900 includes verifying link quality for the CG-SDT on the NTN using the link quality verification information.

[0145]

[0152] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, verifying link quality for the CG-SDT on the NTN includes verifying link quality for the CG-SDT on the NTN using a measurement threshold for the CG-SDT having a measurement duration different from a measurement duration of the measurement threshold for the CG-SDT on the terrestrial network, or a power class threshold for the CG-SDT on the NTN different from a power class threshold for the CG-SDT on the terrestrial network.

[0146]

[0153] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the system information includes cell or satellite verification information for verifying a cell or satellite for CG-SDT, and the process 900 includes verifying the cell or satellite for CG-SDT using the cell or satellite verification information.

[0147]

[0154] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, validating a cell or satellite for CG-SDT includes using the cell or satellite validation information to verify a cell outage time during which the serving cell is valid for CG-SDT on the NTN.

[0148]

[0155] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the process 900 includes skipping validation of parameters for the CG-SDT on the NTN based at least in part on the CG-SDT configuration.

[0149]

[0156] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the method further includes applying a timing advance adjustment to a subsequent uplink transmission after transmission of the SDT.

[0150]

[0157] In a twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, the process 900 includes receiving a TAC, maintaining a TAC-based closed-loop timing advance during a subsequent uplink transmission, and resetting the closed-loop timing advance during a next transmission occasion of the CG-SDT on the NTN.

[0151]

[0158] 9 illustrates example blocks of process 900, in some aspects process 900 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0152]

[0159] 10 illustrates an example process 1000 performed, for example, by a network entity, in accordance with the present disclosure. The example process 1000 is an example of a network entity (e.g., network entity 510) performing operations associated with transmitting a CG-SDT configuration for an NTN.

[0153]

[0160] 10, in some aspects, the process 1000 may include transmitting a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN (block 1010). For example, as described above, the network entity may transmit (e.g., using the communications manager 1208 and / or the transmitting component 1204 shown in FIG. 12) a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN.

[0154]

[0161] 10, in some aspects, the process 1000 may include transmitting system information associated with validating parameters for the CG-SDT on the NTN (block 1020). For example, as described above, the network entity may transmit (e.g., using the communications manager 1208 and / or the transmitting component 1204 shown in FIG. 12) system information associated with validating parameters for the CG-SDT on the NTN.

[0155]

[0162] 10, in some aspects, the process 1000 may include receiving an SDT based at least in part on one or more of the parameters (block 1030). For example, as discussed above, the network entity (e.g., using the communications manager 1208 and / or the receiving component 1202 shown in FIG. 12) may receive an SDT based at least in part on one or more of the parameters.

[0156]

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

[0157]

[0164] In a first aspect, the parameters include a MAC application timing advance (TA) Kmac for delaying application of a downlink configuration indicated by the MAC CE.

[0158]

[0165] In a second aspect, alone or in combination with the first aspect, the parameters include a time offset Koffset for delaying a random access procedure initiated by a physical downlink control channel communication and for delaying an uplink transmission scheduled by a CG, the time offset Koffset being specific to CG-SDT on the NTN.

[0159]

[0166] In a third aspect, alone or in combination with one or more of the first and second aspects, the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset.

[0160]

[0167] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the parameters include ephemeris information and a common TA, and the system information includes TA verification information for verifying the validity duration of the ephemeris information or the common TA.

[0161]

[0168] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the system information includes one or more of TA verification information specific to the CG-SDT, link quality verification information for verifying link quality for the CG-SDT on the NTN, or cell or satellite verification information for verifying a cell or satellite for the CG-SDT.

[0162]

[0169] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, further includes receiving a subsequent uplink transmission using the TA adjustment after receiving the SDT.

[0163]

[0170] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the process 1000 includes transmitting a TAC, maintaining a TAC-based closed-loop timing advance during a subsequent uplink transmission, and resetting the closed-loop timing advance during a next transmission occasion of the CG-SDT on the NTN.

[0164]

[0171] 10 illustrates example blocks of process 1000, in some aspects process 1000 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0165]

[0172] FIG. 11 is a diagram of an example apparatus 1100 for wireless communication. The apparatus 1100 may be a UE (e.g., UE 520), or a UE may include the apparatus 1100. In some aspects, the apparatus 1100 includes a receiving component 1102 and a transmitting component 1104 that may communicate with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using the receiving component 1102 and the transmitting component 1104. As further shown, the apparatus 1100 may include a communications manager 1108. The communications manager 1108 may control and / or otherwise manage one or more operations of the receiving component 1102 and / or the transmitting component 1104. In some aspects, the communications manager 1108 may include one or more antennas, a modem, a controller / processor, a memory, or a combination thereof, of the UE 120 described in connection with FIG. 2. The communications manager 1108 may be or may be similar to the communications manager 150 shown in FIG. 1 and FIG. 2. For example, in some aspects, the communications manager 1108 may be configured to perform one or more of the functions described as being performed by the communications manager 150. In some aspects, the communications manager 1108 may include a receiving component 1102 and / or a transmitting component 1104. The communications manager 1108 may include a verifying component 1110, among other examples.

[0166]

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

[0167]

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

[0168]

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

[0169]

[0176] The receiving component 1102 may receive a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The receiving component 1102 may receive system information associated with validation of parameters for the CG-SDT on the NTN. The transmitting component 1104 may transmit the SDT to a network entity of the NTN using one or more of the parameters.

[0170]

[0177] The receiving component 1102 may receive an indication of a time offset that is cell-specific or UE-specific, and the parameters may include a cell outage time during which the serving cell is valid for CG-SDT on the NTN, and the UE may be restricted from transmitting CG-SDT on the NTN after the end of the cell outage time minus the time offset.

[0171]

[0178] The validation component 1110 may skip validation of parameters for the CG-SDT on the NTN based at least in part on the CG-SDT configuration.

[0172]

[0179] The receiving component 1102 may receive the TAC. The transmitting component 1104 may maintain the TAC-based closed-loop timing advance during a subsequent uplink transmission. The transmitting component 1104 may reset the closed-loop timing advance during the next transmission occasion of the CG-SDT on the NTN.

[0173]

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

[0174]

[0181] 12 is a diagram of an example apparatus 1200 for wireless communication. The apparatus 1200 may be a network entity (e.g., network entity 510) or the network entity may include the apparatus 1200. In some aspects, the apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using the receiving component 1202 and the transmitting component 1204. As further shown, the apparatus 1200 may include a communications manager 1208. The communications manager 1208 may control and / or otherwise manage one or more operations of the receiving component 1202 and / or the transmitting component 1204. In some aspects, the communications manager 1208 may include one or more antennas, modems, controllers / processors, memories, or combinations thereof, of the network entities described in connection with FIG. 2. The communications manager 1208 may be or be similar to the communications manager 150 shown in FIG. 1 and FIG. 2. For example, in some aspects, the communications manager 1208 may be configured to perform one or more of the functions described as being performed by the communications manager 150. In some aspects, the communications manager 1208 may include a receiving component 1202 and / or a transmitting component 1204. The communications manager 1208 may include a generating component 1210, among other examples.

[0175]

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

[0176]

[0183] 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, among other examples) on the received communications and provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of the network entities described in connection with FIG.

[0177]

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

[0178]

[0185] The generating component 1210 may generate a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The transmitting component 1204 may transmit the CG-SDT configuration for the NTN. The transmitting component 1204 may transmit system information associated with validation of the parameters for the CG-SDT on the NTN. The receiving component 1202 may receive the SDT based at least in part on one or more of the parameters.

[0179]

[0186] The transmitting component 1204 may transmit the TAC. The receiving component 1202 may hold the TAC-based closed-loop timing advance during a subsequent uplink transmission. The receiving component 1202 may reset the closed-loop timing advance during the next transmission occasion of the CG-SDT on the NTN.

[0180]

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

[0181]

[0188] The following provides a summary of several aspects of the disclosure.

[0182]

[0189] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving a UE-specific CG-SDT configuration having parameters specific to a configured grant (CG) small data transmission (SDT) in a non-terrestrial network (NTN); receiving system information associated with validation of the parameters for the CG-SDT on the NTN; and transmitting the SDT to a network entity of the NTN using one or more of the parameters.

[0183]

[0190] Aspect 2: The method of aspect 1, wherein receiving system information associated with CG-SDT validation includes periodically receiving system information associated with CG-SDT validation.

[0184]

[0191] Aspect 3: The method of aspect 1 or 2, wherein the parameters include a Medium Access Control (MAC) Application Timing Advance (TA) Kmac for delaying application of a downlink configuration indicated by a MAC control element (MAC CE).

[0185]

[0192] Aspect 4: The method of aspect 3, wherein the parameters include a time offset Koffset for delaying a random access procedure initiated by a physical downlink control channel communication and for delaying an uplink transmission scheduled by the CG, the time offset Koffset being specific to CG-SDT on the NTN.

[0186]

[0193] Aspect 5: The method of aspect 4, wherein the time offset Koffset is cell common.

[0187]

[0194] Aspect 6: The method of aspect 4, wherein the time offset Koffset is UE specific.

[0188]

[0195] Aspect 7: The method of aspect 6, wherein the time offset Koffset is configured while the UE is in a radio resource control connected mode.

[0189]

[0196] Example 8: The method of example 6, wherein the time offset Koffset is a separate UE-specific Koffset for the CG-SDT configured in the radio resource control release message.

[0190]

[0197] Example 9: The method of example 6, wherein the time offset Koffset is reconfigured in a radio resource control inactive mode.

[0191]

[0198] Aspect 10: The method of any of aspects 4 to 9, wherein the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset, and the method further includes verifying the MAC TA Kmac and the time offset Koffset using the timing relationship verification information.

[0192]

[0199] Example 11: The method of example 3, wherein the MAC TA Kmac is received in a separate message within the CG-SDT search space.

[0193]

[0200] Example 12: The method of any one of examples 1 to 11, wherein the parameters include ephemeris information and a common timing advance (TA).

[0194]

[0201] Aspect 13: The method of aspect 12, wherein the system information includes TA validation information for validating the ephemeris information or the common TA, and the method further includes validating the ephemeris information or the common TA using the TA validation information.

[0195]

[0202] Aspect 14: The method of aspect 13, wherein verifying the ephemeris information or the common TA includes using TA verification information to verify the epoch time or validity duration of the ephemeris information or the common TA for the CG-SDT based at least in part on one or more of the UE's location or a timer.

[0196]

[0203] Aspect 15: The method of any of aspects 1 to 14, wherein the parameters include parameters for disabling a hybrid automatic repeat request (CG-SDT) process on the NTN.

[0197]

[0204] Example 16: The method of any one of examples 1 to 15, wherein the parameters include polarization parameters for CG-SDT on the NTN.

[0198]

[0205] Aspect 17: The method of any of aspects 1 to 16, further comprising receiving an indication of a time offset that is cell-specific or UE-specific, the parameter comprising a cell outage time during which the serving cell is valid for CG-SDT on the NTN, and the UE being restricted from transmitting CG-SDT on the NTN after the end of the cell outage time minus the time offset.

[0199]

[0206] Aspect 18: The method of any of aspects 1 to 17, wherein the parameters include cell parameters configured for CG-SDT on the NTN or satellite parameters configured for CG-SDT on the NTN.

[0200]

[0207] Aspect 19: The method of any of aspects 1 to 18, wherein the parameters include a set of CG-SDT parameters associated with the configured list of cells.

[0201]

[0208] Aspect 20: The method of any of aspects 1 to 19, wherein the parameters include a set of CG-SDT parameters associated with a configured list of satellites.

[0202]

[0209] Aspect 21: Any of the methods of aspects 1 to 20, wherein the system information includes timing advance (TA) verification information specific to the CG-SDT, and the method further includes verifying the TA for the CG-SDT on the NTN using the TA verification information.

[0203]

[0210] Aspect 22: The method of any of aspects 1 to 21, wherein the UE uses the CG-SDT based at least in part on expiration of a timer associated with the timing advance.

[0204]

[0211] Aspect 23: Any of the methods of aspects 1 to 22, wherein the system information includes link quality verification information for verifying link quality for CG-SDT on the NTN, and the method further includes verifying link quality for CG-SDT on the NTN using the link quality verification information.

[0205]

[0212] Aspect 24: The method of aspect 23, wherein verifying link quality for the CG-SDT on the NTN includes verifying link quality for the CG-SDT on the NTN using a measurement threshold for the CG-SDT having a measurement duration different from the measurement duration of the measurement threshold for the CG-SDT on the terrestrial network, or a power class threshold for the CG-SDT on the NTN different from the power class threshold for the CG-SDT on the terrestrial network.

[0206]

[0213] Aspect 25: Any of the methods of aspects 1 to 24, wherein the system information includes cell or satellite verification information for verifying a cell or satellite for CG-SDT, and the method includes using the cell or satellite verification information to verify a cell or satellite for CG-SDT.

[0207]

[0214] Aspect 26: The method of aspect 25, wherein verifying the cell or satellite for CG-SDT includes using the cell or satellite verification information to verify a cell outage time during which the serving cell is valid for CG-SDT on the NTN.

[0208]

[0215] Aspect 27: The method of aspect 26, wherein the cell outage time is restarted when the UE receives a timing advance command or when the timer is reconfigured by radio resource control dedicated signaling.

[0209]

[0216] Aspect 28: The method of any of aspects 1 to 27, further comprising skipping parameter validation for the CG-SDT on the NTN based at least in part on the CG-SDT configuration.

[0210]

[0217] Aspect 29: Any of the methods of aspects 1 to 28, wherein one or more processors are configured to skip validation of parameters for CG-SDT on the NTN based at least in part on a newly reselected cell belonging to the same satellite as the previous cell and having common criteria with the previous cell.

[0211]

[0218] Aspect 30: Any of the methods of aspects 1 to 29, wherein one or more processors are configured to skip validation of parameters for CG-SDT on the NTN based at least in part on a satellite type associated with the cell.

[0212]

[0219] Aspect 31: Any of the methods of aspects 1 to 30, wherein one or more processors are configured to perform parameter validation for CG-SDT on the NTN within one or more time windows.

[0213]

[0220]

[0041] Aspect 32: The method of any of aspects 1 to 31, further comprising, after transmitting the SDT, applying a timing advance adjustment to a subsequent uplink transmission.

[0214]

[0221] Aspect 33: The method of any of aspects 1 to 32, comprising receiving a timing advance command (TAC), maintaining a TAC-based closed-loop timing advance during a subsequent uplink transmission, and resetting the closed-loop timing advance during a next transmission occasion of the CG-SDT on the NTN.

[0215]

[0222] Aspect 34: A method of wireless communication performed by a network entity of a non-terrestrial network (NTN), comprising: transmitting a user equipment (UE)-specific small data transmission (SDT) configuration having parameters specific to a configured grant (CG) small data transmission (SDT) configuration in the NTN; transmitting system information associated with validation of the parameters for the CG-SDT on the NTN; and receiving an SDT based at least in part on one or more of the parameters.

[0216]

[0223] Aspect 35: The method of aspect 34, wherein the parameters include a Medium Access Control (MAC) Apply Timing Advance (TA) Kmac for delaying application of the downlink configuration indicated by a MAC control element (MAC CE).

[0217]

[0224] Aspect 36: The method of aspect 35, wherein the parameters include a time offset Koffset for delaying a random access procedure initiated by physical downlink control channel communication and delaying an uplink transmission scheduled by the CG, the time offset Koffset being specific to CG-SDT on the NTN.

[0218]

[0225] Aspect 37: The method of aspect 36, wherein the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset.

[0219]

[0226] Example 38: The method of any of examples 34 to 37, wherein the parameters include ephemeris information and a common timing advance (TA), and the system information includes TA verification information for verifying the validity duration of the ephemeris information or the common TA.

[0220]

[0227] Aspect 39: The method of any of aspects 34 to 38, wherein the system information includes one or more of timing advance (TA) verification information specific to CG-SDT, link quality verification information for verifying link quality for CG-SDT on the NTN, or cell or satellite verification information for verifying a cell or satellite for CG-SDT.

[0221]

[0228]

[0046] Aspect 40: The method of any of aspects 34 to 39, further comprising, after receiving the SDT, receiving a subsequent uplink transmission using a timing advance adjustment.

[0222]

[0229] Aspect 41: The method of any of aspects 34 to 40, comprising transmitting a timing advance command (TAC), maintaining a TAC-based closed-loop timing advance during a subsequent uplink transmission, and resetting the closed-loop timing advance during a next transmission occasion of the CG-SDT on the NTN.

[0223]

[0230] Aspect 42: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform one or more of the methods of aspects 1 to 41.

[0224]

[0231] Aspect 43: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform one or more of the methods of aspects 1 to 41.

[0225]

[0232] Aspect 44: An apparatus for wireless communication comprising at least one means for performing one or more of the methods of aspects 1 to 41.

[0226]

[0233] Aspect 45: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform one or more of the methods of aspects 1 to 41.

[0227]

[0234] Aspect 46: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more methods of aspects 1 to 41.

[0228]

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

[0229]

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

[0230]

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

[0231]

[0238] Even if particular combinations of features are recited in a claim and / or disclosed herein, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to include a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., 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 permutation of a, b, and c).

[0232]

[0239] No element, act, or instruction used herein should be construed as critical or required unless explicitly described. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Additionally, as used herein, the article "the" is intended to include one or more items referred to in relation to the article "the" and may be used interchangeably with "one or more." Additionally, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more." When only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, terms such as "has," "have," and "having" are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "has" A may also have B). Additionally, the phrase "based on" is intended to mean "based, at least in part, on," unless expressly stated otherwise. Also, as used herein, the term "or" is intended to be inclusive when used in a sequence and may be used interchangeably with "and / or," unless expressly stated otherwise (e.g., when used in combination with "either" or "only one of").

Claims

1. 1. A user equipment (UE) for wireless communications, comprising: Memory and one or more processors coupled to the memory, receiving a UE-specific CG-SDT configuration having parameters specific to a configured grant (CG) small data transmission (SDT) in a non-terrestrial network (NTN); receiving system information associated with verifying the parameters for CG-SDT on the NTN; and a processor configured to send an SDT to a network entity of the NTN using one or more of the parameters.

2. 10. The UE of claim 1, wherein the one or more processors are configured to periodically receive the system information associated with CG-SDT verification to receive the system information associated with CG-SDT verification.

3. The parameters are: a MAC application timing advance (TA) Kmac for delaying application of a downlink configuration indicated by a Medium Access Control (MAC) control element (MAC CE); and optionally, a time offset Koffset for delaying random access procedures initiated by physical downlink control channel communications and delaying uplink transmissions scheduled by a CG, wherein the time offset Koffset is specific to CG-SDT on the NTN; and / or Ephemeris information and a common timing advance (TA), and / or a parameter for disabling the Hybrid Automatic Repeat Request (CG-SDT) process on the NTN; and / or Polarization parameters for CG-SDT on the NTN, and / or Cell parameters configured for CG-SDT on the NTN or satellite parameters configured for CG-SDT on the NTN, and / or a set of CG-SDT parameters associated with the configured list of cells; and / or A set of CG-SDT parameters associated with a configured list of satellites The UE of claim 1 , comprising:

4. The time offset Koffset is Cell-common; and / or UE specific; and / or configured while the UE is in a radio resource control connected mode; and / or a separate UE-specific Koffset for CG-SDT configured in the radio resource control release message; and / or Reconfigured in radio resource control inactive mode; The UE of claim 3.

5. 4. The UE of claim 3, wherein the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset, and the one or more processors are configured to verify the MAC TA Kmac and the time offset Koffset using the timing relationship verification information.

6. The UE of claim 3 , wherein the MAC TA Kmac is received in a separate message within a CG-SDT search space.

7. the system information includes TA verification information for verifying the ephemeris information or the common TA, and the one or more processors are configured to verify the ephemeris information or the common TA using the TA verification information; and optionally, 4. The UE of claim 3, wherein the one or more processors are configured to use the TA validation information to validate the ephemeris information or the common TA, including using the TA validation information to validate an epoch time or validity duration of the ephemeris information or the common TA for CG-SDT based at least in part on one or more of a location of the UE or a timer.

8. 2. The UE of claim 1, wherein the one or more processors are configured to receive an indication of a time offset that is cell-specific or UE-specific, the parameters including a cell outage time during which a serving cell is valid for CG-SDT on the NTN, and the UE is restricted from transmitting CG-SDT on the NTN after the end of a time that is the cell outage time minus the time offset.

9. The system information comprises: Timing Advance (TA) verification information specific to CG-SDT, wherein the one or more processors are configured to verify TA for CG-SDT on the NTN using the TA verification information; and / or Link quality verification information for verifying link quality for CG-SDT over the NTN, wherein the one or more processors are configured to use the link quality verification information to verify the link quality for CG-SDT over the NTN; and / or cell or satellite verification information for verifying a cell or satellite for CG-SDT, wherein the one or more processors are configured to use the cell or satellite verification information to verify the cell or satellite for CG-SDT; The UE of claim 1 , comprising:

10. 10. The UE of claim 1, wherein the UE uses CG-SDT based at least in part on the expiration of a timer associated with a timing advance.

11. the one or more processors are configured to verify the link quality for CG-SDT over the NTN using a measurement threshold for CG-SDT having a measurement duration different from a measurement duration of the measurement threshold for CG-SDT over a terrestrial network, or a power class threshold for CG-SDT over the NTN different from a power class threshold for CG-SDT over the terrestrial network, to verify the link quality for CG-SDT over the NTN; and / or the one or more processors are configured to use the cell or satellite verification information to verify the cell or satellite for CG-SDT, and to verify a cell outage time during which a serving cell is valid for CG-SDT on the NTN; and optionally: the cell outage time is restarted when the UE receives a timing advance command or when the timer is reconfigured by radio resource control dedicated signaling; 10. The UE of claim 9.

12. the one or more processors: Skipping validation of the parameters for CG-SDT on the NTN based at least in part on the CG-SDT configuration; and / or Skipping the validation of the parameters for CG-SDT on the NTN based at least in part on a newly reselected cell belonging to the same satellite as the previous cell and having common criteria with the previous cell; and / or Skipping validation of the parameters for CG-SDT on the NTN based at least in part on a satellite type associated with a cell; and / or performing a verification of said parameters for CG-SDT on said NTN within one or more time windows; and / or applying a timing advance adjustment to subsequent uplink transmissions after transmitting the SDT; and / or receiving a timing advance command (TAC); maintaining the TAC-based closed-loop timing advance during subsequent uplink transmissions; resetting the closed loop timing advance during the next transmission occasion of a CG-SDT on the NTN; The UE of claim 1 , configured to:

13. 1. A network entity in a non-terrestrial network (NTN) for wireless communications, comprising: Memory and one or more processors coupled to the memory, Transmitting a user equipment (UE) specific CG-SDT configuration having parameters specific to a configured grant (CG) small data transmission (SDT) in the NTN; transmitting system information associated with the verification of the parameters for CG-SDT on the NTN; and a processor configured to receive an SDT based at least in part on one or more of the parameters.

14. 1. A method of wireless communication performed by a user equipment (UE), comprising: receiving a UE-specific CG-SDT configuration having parameters specific to a configured grant (CG) small data transmission (SDT) in a non-terrestrial network (NTN); receiving system information associated with verifying the parameters for CG-SDT on the NTN; and transmitting an SDT to a network entity of the NTN using one or more of the parameters.

15. 1. A method of wireless communication performed by a network entity in a non-terrestrial network (NTN), comprising: transmitting a user equipment (UE) specific CG-SDT configuration with parameters specific to a configured grant (CG) small data transmission (SDT) in the NTN; transmitting system information associated with the verification of the parameters for CG-SDT on the NTN; and receiving an SDT based at least in part on one or more of the parameters.

Images