Small data transmission configuration for non-terrestrial network

Abstract

The various formats described herein generally relate to wireless communication. In some formats, the user equipment (UE) can receive a UE-specific CG-SDT configuration with parameters specific to Configurable Granted (CG) Small Data Transmission (SDT) (CG-SDT) in a non-terrestrial network (NTN). The UE can receive system information associated with the verification of these parameters for the CG-SDT used on the NTN. The UE can use one or more of these parameters to send SDTs to network entities of the NTN. Many other formats are described.

Description

Technical Field

[0001] The contents of this case generally pertain to wireless communication and the technologies and devices used for small data transmission configurations for non-terrestrial networks. Prior Technology

[0002] Wireless communication systems are widely deployed to provide various telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiplexing access technologies that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiplexing access technologies include Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile service standard released by the 3rd Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more base stations that support communication of user equipment (UE) or multiple UEs. UEs may communicate with base stations via downlinks and uplinks. A "downlink" (or "DL") refers to the communication link from the base station to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the base station.

[0004] The above multiplexing access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile service standard released by 3GPP. NR aims to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL) and / or supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements to LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0005] Some of the methods described herein relate to a method of wireless communication performed by a user equipment (UE). This method may include receiving a UE-specific CG-SDT configuration having parameters for Configurable Granted (CG) Small Data Transmission (SDT) (CG-SDT) specific to a non-terrestrial network (NTN). This method may include receiving system information associated with authentication of these parameters for the CG-SDT on the NTN. This method may include using one or more of these parameters to send the SDT to a network entity of the NTN.

[0006] Some of the methods described herein relate to a method of radio communication performed by a network entity of an NTN. This method may include transmitting a UE-specific CG-SDT configuration having parameters specific to the CG-SDT in the NTN. This method may include transmitting system information associated with authentication of these parameters for the CG-SDT on the NTN. This method may include receiving the SDT based at least in part on one or more of these parameters.

[0007] Some of the states described herein relate to a UE for wireless communication. The UE may include 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 having parameters specific to the CG-SDT used on the NTN. The one or more processors may be configured to receive system information associated with the verification of these parameters for the CG-SDT on the NTN. The one or more processors may be configured to send the SDT to a network entity of the NTN using one or more of these parameters.

[0008] Some of the states described herein relate to a network entity for wireless communication. This network entity may include 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 having parameters specific to the CG-SDT in the NTN. The one or more processors may be configured to transmit system information associated with the verification of these parameters for the CG-SDT on the NTN. The one or more processors may be configured to receive the SDT based at least in part on one or more of these parameters.

[0009] Some of the states described herein relate to a non-transitory computer-readable medium storing instruction sets for wireless communication by a UE. When executed by one or more processors of the UE, these instruction sets can cause the UE to receive a UE-specific CG-SDT configuration with parameters specific to the CG-SDT on the NTN. When executed by one or more processors of the UE, these instruction sets can cause the UE to receive system information associated with the verification of these parameters for the CG-SDT on the NTN. When executed by one or more processors of the UE, these instruction sets can cause the UE to send an SDT to a network entity of the NTN using one or more of these parameters.

[0010] Some of the states described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. When executed by one or more processors of the network entity, such a set of instructions can cause the network entity to send a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. When executed by one or more processors of the network entity, such a set of instructions can cause the network entity to send system information associated with the verification of these parameters for the CG-SDT on the NTN. When executed by one or more processors of the network entity, such a set of instructions can cause the network entity to receive the SDT at least in part based on one or more of these parameters.

[0011] Some of the features described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a UE-specific CG-SDT configuration having parameters specific to the CG-SDT on the NTN. The apparatus may include components for receiving system information associated with the verification of these parameters for the CG-SDT on the NTN. The apparatus may include components for transmitting the SDT to a network entity of the NTN using one or more of these parameters.

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

[0013] Various types typically include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, wireless communication devices and / or processing systems as described herein with reference to the accompanying drawings and specifications and illustrated by examples as illustrated in the accompanying drawings and specifications.

[0014] The features and technical advantages of examples based on the content of this application have been outlined quite extensively above to facilitate a better understanding of the subsequent detailed description. Other features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures to achieve the same purpose as the content of this application. Such equivalent structures do not depart from the scope of the appended claims. The features, organization, and operation of the concepts disclosed herein, as well as their associated advantages, will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not as a limiting definition of the claims.

[0015] Although various embodiments have been described in this document by way of example, those skilled in the art will understand that such embodiments can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some embodiments can be implemented via integrated wafer embodiments or other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Embodiments can be implemented in wafer-level components, modular components, non-modular components, non-wafer-level components, device-level components, or system-level components. Devices incorporating the described embodiments and features may include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers) for analog and digital purposes. The patterns described herein are intended to be implemented in a variety of devices, components, systems, distributed layouts, and / or end-user devices of different sizes, shapes, and constructions. Simple Explanation of the Diagram

[0016] To gain a more detailed understanding of the aforementioned features of this case, a more specific description of the brief overview above can be obtained by referring to the various embodiments (some of which are shown in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only some typical embodiments of this case and should therefore not be considered as limiting its scope, as the description may allow for other equivalent embodiments. Identical element symbols in different drawings may identify the same or similar elements.

[0017] Figure 1 is a schematic diagram illustrating an example of a wireless network according to the contents of this case.

[0018] Figure 2 is a schematic diagram illustrating an example of communication between a network entity and a user equipment (UE) in a wireless network according to the contents of this case.

[0019] Figure 3 is a schematic diagram illustrating an example of a non-aggregate base station according to the content of this case.

[0020] Figure 4 is a schematic diagram illustrating examples of regenerative satellite deployment and transparent satellite deployment in a non-terrestrial network (NTN) according to the content of this case.

[0021] Figure 5 is a schematic diagram illustrating an example of a Configurable Authorized Small Data Transfer (CG-SDT) associated with the transmission and four-step random access channel procedure according to the content of this case.

[0022] Figure 6 is a schematic diagram illustrating an example of parameters included in the CG-SDT configuration according to the content of this case.

[0023] Figure 7 illustrates an example of commands and startup sequence based on the content of this case.

[0024] Figure 8 is a schematic diagram illustrating an example of an isochronous line used to provide configuration and system information according to the contents of this case.

[0025] Figure 9 is a schematic diagram illustrating an exemplary process performed by a UE, for example, according to the contents of this case.

[0026] Figure 10 is a schematic diagram illustrating an exemplary process, for example, performed by a network entity according to the contents of this case.

[0027] Figures 11-12 are schematic diagrams of exemplary devices for wireless communication according to the contents of this case. Implementation

[0028] Various forms of the present invention are described more fully below with reference to the accompanying drawings. However, the present invention can be embodied in many different forms and should not be construed as limited to any particular structure or function provided throughout the present invention. Rather, these forms are provided to make the present invention thorough and complete, and to fully convey the scope of the present invention to those skilled in the art. Those skilled in the art should understand that the scope of the present invention is intended to cover any form of the present invention disclosed herein, whether implemented independently of or in combination with any other form of the present invention. For example, any number of forms described herein can be used to implement an apparatus or method of practice. Furthermore, the scope of the present invention is intended to cover such apparatus or methods practiced using other structures, functions, or structures and functions attached to or different from the various forms of the present invention described herein. It should be understood that any form of the present invention disclosed herein can be embodied by one or more elements of the claim.

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

[0030] Although the terms commonly associated with 5G or New Radio (NR) Radio Access Technology (RAT) are used in this document to describe the various forms, the various forms of the content herein may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0031] Figure 1 is a schematic diagram illustrating an example of a wireless network 100 according to the present invention. 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, etc. The wireless network 100 may include 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 also 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. Base station 110 is a network entity that communicates with UE 120. Base station 110 (sometimes referred to as BS) 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 Transmit / Receive Points (TRPs). Each base station 110 can provide communication coverage for a specific geographic area. In the 3GPP, the term "cell service area" can represent the coverage area of ​​base station 110 and / or the base station subsystems serving that coverage area, depending on the context in which the term is used.

[0032] Base station 110 can provide communication coverage for macrocell service areas, picocell service areas, femtocell service areas, and / or another type of cell service area. Macrocell service areas can cover relatively large geographic areas (e.g., radius of several kilometers) and allow unrestricted access for UEs 120 with service subscriptions. Picocell service areas can cover relatively small geographic areas and allow unrestricted access for UEs 120 with service subscriptions. Femtocell service areas can cover relatively small geographic areas (e.g., homes) and allow restricted access for UEs 120 associated with a femtocell service area (e.g., UEs 120 in a Closed Subscriber Group (CSG)). Base station 110 used for macrocell service areas can be referred to as a macro base station. Base station 110 used for picocell service areas can be referred to as a pico base station. Base station 110 used for femtocell service areas can be referred to as a femto base station or a home base station. In the example shown in Figure 1, BS 110a can be a macro base station for macro cell service area 102a, BS 110b can be a pico base station for pico cell service area 102b, and BS 110c can be a femto base station for femto cell service area 102c. The base station can support one or more (e.g., three) cell service areas.

[0033] In some instances, the cell service area may not necessarily be static, and the geographical area of ​​the cell service area may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some instances, base stations 110 may interconnect with each other and / or interconnect to one or more other base stations 110 or network entities in the wireless network 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0034] In some embodiments, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a non-converged base station, an integrated access and return (IAB) node, a relay node, and / or one or more of its components. For example, in some embodiments, "base station" or "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 embodiments, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (e.g., the functions described herein in conjunction with base station 110). In some embodiments, the term "base station" or "network entity" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of several different devices (which may be located in the same geographical location or in different geographical locations) can be configured to perform at least a portion of a function, or to replicate the execution of at least a portion of a function, and the terms "base station" or "network entity" can refer to any one or more of these different devices. In some configurations, the terms "base station" or "network entity" can refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some configurations, two or more base station functions can be created on a single device. In some configurations, the terms "base station" or "network entity" can refer to one of these base station functions rather than the other. In this way, a single device can include more than one base station.

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

[0036] Wireless network 100 can be a heterogeneous network having network entities including different types of base stations (such as macro base stations, pico base stations, femto base stations, repeater base stations, etc.). These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different effects on interference in wireless network 100. For example, macro base stations may have high transmit power levels (e.g., 5 to 40 watts), while pico base stations, femto base stations, and repeater base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0037] Network controller 130 can be coupled to or communicate with a group of network entities, and can provide coordination and control for such network entities. Network controller 130 can communicate with base station 110 via a backhaul communication link. Network entities can communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0038] In some configurations, as shown in the figure, the cell service area can be provided by a non-terrestrial network (NTN) network entity (e.g., base station 110). As used herein, "non-terrestrial network" can refer to a network accessed by a non-terrestrial base station (such as a base station carried by a satellite, balloon, airship, aircraft, unmanned aerial vehicle, and / or high-altitude platform station). Network entities in the NTN (NTN network entities) can use polarization. For example, a network entity in satellite 135 (NTN network entity) can use circular polarization 136 or linear polarization 138 to send communications to UE 120. Circular polarization occurs when the tip trajectory of the electric field of an electromagnetic wave at a fixed point in space is circular, and this electromagnetic wave can be formed by superimposing two orthogonal linearly polarized waves with equal amplitude and a 90-degree phase difference. Circular polarization can be right-hand circular polarization (RHCP) or left-hand circular polarization (LHCP). Linear polarization occurs when the tip of the electric field of an electromagnetic wave at a fixed point in space oscillates linearly with time.

[0039] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or user units. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a wireless phone, a wireless loop (WLL) station, a tablet device, a camera, a gaming device, a laptop, a smart computer, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio device), a vehicle component or sensor, a smart instrument / sensor, industrial manufacturing equipment, a GPS device, and / or any other suitable device configured to communicate via wireless media.

[0040] Some UEs 120 may be considered Machine-Type Communications (MTC) or Evolved or Enhanced Machine-Type Communications (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which can communicate with network entities, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UE 120 may be included within a housing that houses the components of UE 120, such as processor elements and / or memory elements. In some instances, processor elements and memory elements may be coupled together. For example, processor elements (e.g., one or more processors) and memory elements (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

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

[0043] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., by frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been identified as the frequency range names FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. Similar naming issues sometimes arise regarding FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30 GHz - 300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0044] The frequencies between FR1 and FR2 are often referred to as intermediate frequency (IF) bands. Recent 5G NR research has identified the operating frequency bands of these IF bands as the frequency range name FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 into the IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range names FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0045] Considering the above examples, unless otherwise specifically stated, it should be understood that the term "sub-6 GHz" and the like (if used herein) can broadly refer to frequencies that can be less than 6 GHz, frequencies that can be within FR1, or frequencies that can include intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that the term "millimeter wave" and the like (if used herein) can broadly refer to frequencies that can include intermediate frequency bands, frequencies that can be within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or frequencies that can be within the EHF band. It is contemplated that frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to such modified frequency ranges.

[0046] In some configurations, UE 120 may include a communication manager 140. As described in more detail elsewhere in this document, the communication manager 140 may receive a UE-specific CG-SDT configuration with parameters specific to the Configurable Authorized (CG) Small Data Transfer (SDT) (CG-SDT) in the NTN. The communication manager 140 may receive system information associated with the verification of these parameters for the CG-SDT on the NTN, and may use one or more of these parameters to send the SDT to the network entity of the NTN. Alternatively or concurrently, the communication manager 140 may perform one or more other operations described herein.

[0047] In some configurations, network entities (e.g., base station 110, satellite 135) may include a communication manager 150. As described in more detail elsewhere in this document, the communication manager 150 may send a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The communication manager 150 may send system information associated with the verification of these parameters for the CG-SDT on the NTN, and may receive the SDT based at least in part on one or more of these parameters. Alternatively or additionally, the communication manager 150 may perform one or more other operations described herein.

[0048] As mentioned above, Figure 1 is provided as an example. Other examples may differ from the example described with respect to Figure 1.

[0049] Figure 2 is a schematic diagram illustrating an example 200 of communication between a network entity (e.g., base station 110) and a UE 120 in a wireless network 100 according to the present invention. The base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R ≥ 1).

[0050] At base station 110, transmit processor 220 can receive data intended for transmission to UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 can select one or more modulation and coding schemes (MCS) for UE 120, at least in part, based on one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 can process (e.g., encode and modulate) the data for UE 120, at least in part, based on the selected (one or more) MCS for UE 120, and can provide data symbols for UE 120. Transmit processor 220 can process system information (e.g., information for Semi-Static Resource Partitioning (SRPI)) and control information (e.g., CQI requests, authorizations, and / or upper-layer signaling), and provide management burden symbols and control symbols. Transmit processor 220 can generate reference symbols for reference signals (e.g., cell service area specific reference signal (CRS) or demodulated reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). PSS / SSS may include per-cell service area PSS / SSS for MTC devices and NB PSS (NPSS) / NB SSS (NSSS) for NB-IoT devices. Transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, management burden symbols, and / or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of corresponding modems 232 (e.g., T modems), shown as modems 232a to 232t. For example, each output symbol stream can be provided to a modulator element (shown as MOD) of modem 232. Each data transmitter 232 may use a corresponding modulator element to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each data transmitter 232 may further use a corresponding modulator element to process (e.g., analog-to-digital conversion, amplification, filtering, and / or upconversion) the output sample stream to obtain a downlink signal. Data transmitters 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a set of corresponding antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t). Base station 110 may be an NTN network entity located at a terrestrial or non-terrestrial location (e.g., satellite 135).

[0051] At UE 120, an array of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from base station 110 and / or other base stations 110, and can provide the received signal set (e.g., R received signals) to an array of data terminals 254 (e.g., R data terminals) (shown as data terminals 254a to 254r). For example, each received signal can be provided to a demodulator element (shown as DEMOD) of data terminal 254. Each data terminal 254 can use a corresponding demodulator element to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each data terminal 254 can use a demodulator element to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbol from data terminal 254, can perform MIMO detection on the received symbol where applicable, and can provide the detected symbol. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data slot 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some instances, one or more components of UE 120 may be included in housing 284.

[0052] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with network entities via communication unit 294.

[0053] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more antenna element sets and / or one or more antenna arrays, etc., or may be included therein. Antenna panels, antenna groups, antenna element sets and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element sets, non-coplanar antenna element sets and / or one or more antenna elements coupled to one or more transmitting and / or receiving elements (such as one or more elements of FIG. 2).

[0054] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting RSRP, RSSI, RSRQ, and / or CQI). Transmit processor 264 can generate reference symbols for one or more reference signals. Symbols from transmit processor 264 may be pre-encoded by TX MIMO processor 266 where applicable, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network entities. In some instances, modem 254 of UE 120 may include modulators and demodulators. In some instances, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform various forms of any of the methods described herein (e.g., refer to Figures 4-12).

[0055] At the 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., demodulator element of modem 232, shown as DEMOD), detected by MIMO detector 236 (if applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 may provide the decoded data to data slot 239 and the decoded control information to controller / processor 240. The network entity may include communication unit 244 and may communicate with network controller 130 via communication unit 244. The network entity may include scheduler 246 to schedule downlink and / or uplink communication for one or more UEs 120. In some instances, the modem 232 of the network entity may include modulator and demodulator. In some instances, the network entity includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receiver processor 238, transmitter processor 220, and / or TX MIMO processor 230. The transceiver may be configured by a processor (e.g., controller / processor 240) and memory 242 to perform various forms of any of the methods described herein (e.g., refer to Figures 4-12).

[0056] The controller / processor of the network entity (e.g., controller / processor 240 of base station 110), the controller / processor 280 of UE 120, and / or any other element of FIG. 2 may perform one or more technologies associated with the configuration using CG-SDT in NTN, as described in more detail elsewhere herein. In some cases, the network entity is a network entity located on the ground or on a satellite (e.g., 135). For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other element of FIG. 2 may perform or direct operations such as 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 code for the network entity and UE 120, respectively. In some instances, memory 242 and / or memory 282 may include non-transitory computer-readable media storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when one or more instructions are executed by one or more processors of the network entity and / or UE 120 (e.g., directly, or after compilation, translation, and / or interpretation), they may cause one or more processors, UE 120, and / or network entity to perform or direct operations such as process 900 of FIG. 9, process 1000 of FIG. 10, and / or other processes as described herein. In some instances, execution instructions may include execution instructions, translation instructions, compilation instructions, and / or interpretation instructions, etc.

[0057] In some configurations, UE 120 includes: a component for receiving a UE-specific CG-SDT configuration having parameters specific to the CG-SDT in the NTN; a component for receiving system information associated with the verification of the parameters for the CG-SDT on the NTN; and / or a component for transmitting the SDT to a network entity of the NTN using one or more of the parameters. Components enabling UE 120 to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0058] In some embodiments, network entity 110 includes: a component for transmitting a UE-specific CG-SDT configuration having parameters specific to the CG-SDT in the NTN; a component for transmitting system information associated with the verification of the parameters for the CG-SDT on the NTN; and / or a component for receiving the SDT based at least in part on one or more of the parameters. In some embodiments, the components for network entity 110 to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0059] Although the blocks in Figure 2 are shown as different components, the functions described above for these blocks can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 can be executed by or under the control of the controller / processor 280.

[0060] As mentioned above, Figure 2 is provided as an example. Other examples may differ from the example described with respect to Figure 2.

[0061] Figure 3 is a schematic diagram illustrating an example of a non-aggregate base station 300 according to the contents of this case.

[0062] The deployment of communication systems such as 5G NR systems can involve various elements or components arranged in multiple ways. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as base stations or one or more units (or elements) performing base station functions) can be implemented in aggregated or non-aggregated architectures. For example, BSs (such as node B, evolved NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell service area, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or non-aggregated base stations.

[0063] Aggregated base stations can be configured to utilize radio protocol stacks that are physically or logically integrated within a single RAN node. Non-aggregated base stations can be configured to utilize protocol stacks that are physically or logically distributed among two or more units (e.g., one or more CUs, one or more DUs, or one or more RUs). In some configurations, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other RAN nodes. DUs can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can 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).

[0064] Base station type operation or network design can consider the aggregation characteristics of base station functions. For example, non-aggregated base stations can be used in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations sponsored by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Non-aggregated configurations can include distributing functions across two or more units at various physical locations, as well as virtually distributing functions to at least one unit, thus enabling flexibility in network design. Various units in a non-aggregated base station or non-aggregated RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication.

[0065] The non-converged base station 300 architecture may include one or more CUs 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more non-converged base station units (such as near-RT RICs 325 via E2 links, or non-real-time (non-RT) RICs 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). CUs 310 may communicate with one or more DUs 330 via appropriate midhaul links (e.g., F1 interfaces). DUs 330 may communicate with one or more RUs 340 via appropriate fronthaul links. Fronthaul links, midhaul links, and backhaul links may be collectively referred to as "communication links". RUs 340 may communicate with corresponding UEs 120 via one or more RF access links. In some configurations, a UE 120 may be served by multiple RUs 340 simultaneously. DU 330 and RU 340 may also be referred to as "O-RAN DU (O-DU)" and "O-RAN RU (O-RU)" respectively. Network entities may include CU, DU, RU, or any combination of CU, DU, and RU. Network entities may include one or more elements of a non-converged base station, such as CU, DU, RU, or any combination of CU, DU, and RU. Network entities may also include one or more of the following: TRP, relay station, passive device, intelligent reflective surface (IRS), or other elements that provide a network interface for or serve a UE, mobile station, sensor / actuator, or other wireless device.

[0066] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO frame 305) may include one or more interfaces, or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit, or an associated processor or controller that provides instructions to the communication interface of that unit, may be configured to communicate with one or more other units via transmission media. For example, the unit may include a wired interface configured to receive signals or transmit signals to one or more other units via a wired transmission media. Additionally, the unit may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals or transmit signals to one or more other units, or both, via a wireless transmission media.

[0067] In some configurations, CU 310 may house one or more higher-level control functions. These control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptability Protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signals with other control functions housed in CU 310. CU 310 may be configured to handle user plane functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units may communicate bidirectionally with CU-CP units via an interface (e.g., an E1 interface). CU 310 may be implemented to communicate with DU 330 as needed for network control and signal transmission.

[0068] DU 330 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 340s. In some configurations, DU 330 may, at least in part, accommodate one or more of the following layers, depending on the functional partitioning (e.g., the functional partitioning defined by 3GPP): a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and one or more High Physical (PHY) layers (e.g., modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some configurations, DU 330 may further accommodate one or more Low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) accommodated by DU 330 or with the control functions accommodated by CU 310.

[0069] Lower-level functions can be implemented by one or more RU 340s. In some deployments, the RU 340 controlled by the DU 330 can correspond at least partially to accommodating 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 logical nodes of both, based on functional partitioning (such as lower-level functional partitioning). In this architecture, the RU 340 can be implemented to handle over-the-air (OTA) communications with one or more UE 120s. In some implementations, the real-time and non-real-time modes of communication between the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows the DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (e.g., vRAN architecture).

[0070] SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 305 can be configured to support the deployment of dedicated entity resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network elements, SMO framework 305 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as generating entities for virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some implementations, SMO framework 305 can communicate with 4G RAN hardware models (such as Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0071] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) connecting one or more CUs 310s, one or more DUs 330s, or both, and the O-eNB to the near-RT RIC 325.

[0072] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 can receive parameters or external rich information from an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some instances, the non-RT RIC 315 or near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns in performance and use AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via O1) or via the establishment of RAN management policies (such as A1 policies).

[0073] As mentioned above, Figure 3 is provided as an example. Other examples may differ from the example described with respect to Figure 3.

[0074] Figure 4 is a schematic diagram illustrating example 400 of regenerable satellite deployment and example 410 of transparent satellite deployment in NTN according to the contents of this case.

[0075] Example 400 illustrates a regenerative satellite deployment. In Example 400, UE 120 is served by satellite 420 (e.g., satellite 135) via serving link 430. For example, satellite 420 may include BS 110 (e.g., BS 110a) and / or gNB. In some configurations, satellite 420 may be referred to as a non-terrestrial base station, a regenerative transponder, an airborne processing transponder, and / or an NTN entity. In some configurations, satellite 420 may demodulate uplink radio frequency signals and may modulate baseband signals derived from uplink radio signals to generate downlink radio frequency transmissions. Satellite 420 may transmit downlink radio frequency signals over serving link 430. Satellite 420 may provide a cellular service area covering UE 120.

[0076] Example 410 illustrates a transparent satellite deployment, which may also be referred to as a bend-tube 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 can be a transparent satellite. Satellite 440 can relay signals received from gateway 450 via feeder link 460. For example, the satellite can receive uplink RF transmissions and can transmit downlink RF transmissions without demodulating the uplink RF transmissions. In some configurations, the satellite can convert the uplink RF transmission frequency received on service link 430 to the uplink RF transmission frequency on feeder link 460, and can amplify and / or filter the uplink RF transmissions. In some configurations, UE 120 shown in Examples 400 and 410 may be associated with Global Navigation Satellite System (GNSS) capability, Global Positioning System (GPS) capability, etc., but not all UEs have this capability. Satellite 440 can provide a cellular service area covering UE 120.

[0077] Service link 430 may include a link between satellite 440 and UE 120, and may include one or more uplinks or downlinks. Feeder link 460 may include a link between satellite 440 and gateway 450, and may include one or more uplinks (e.g., from UE 120 to gateway 450) or downlinks (e.g., from gateway 450 to UE 120).

[0078] Both feeder link 460 and service link 430 may experience Doppler effects due to the movement of satellites 420 and 440 and the potential movement of UE 120. These Doppler effects may be significantly greater than those in terrestrial networks. The Doppler effect on feeder link 460 can be compensated to some extent, but may still be associated with a certain amount of uncompensated frequency error. In addition, gateway 450 may be associated with residual frequency error, and / or satellites 420 / 440 may be associated with airborne frequency error. These sources of frequency error may cause the receive downlink frequency at UE 120 to drift from the target downlink frequency.

[0079] Satellites 420 and 440 can be in geostationary orbit (GSO) or geosynchronous equatorial orbit (GEO), for example, at an altitude of 36,000 km above the Earth. The satellite's velocity relative to the Earth can be negligible, but it has a propagation delay exceeding 500 milliseconds (ms), compared to 25 ms for a low Earth orbit (LEO) satellite at 600 km above the Earth. In NTNs where the distance between UE 120 and the satellite may be greater than 600 km, changes in path loss may not be adequately reflected in changes in propagation delay. It is expected that UE 120 will always be able to autonomously pre-compensate for propagation delay up to the reference point, and therefore can perform timing advance (TA) verification more directly, rather than relying on indirect parameters such as RSRP. Due to the propagation delay, UE 120 can use TA for communication timing alignment. TA can notify UE 120 to send communications earlier than scheduled by the TA amount. If the propagation distance between UE 120 and network entities changes, TA verification may be required. Additionally, if the satellite is in a non-geostationary orbit (NGSO), it may not always be available for UE 120.

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

[0081] Figure 5 is a schematic diagram illustrating an example 500 of transmitting a CG-SDT associated with a 4-step Random Access Channel (RACH) procedure according to the present case. As shown in Figure 5, network entities 510 (e.g., base station 110, satellite 420, satellite 440) and UE 520 (e.g., UE 120) can communicate with each other to transmit an SDT as part of a 4-step RACH procedure on the NTN.

[0082] Depending on the deployment, CG-SDT resources can be made available across individual cell service areas within a satellite. According to the various configurations described herein, UE 520 can be configured for CG-SDT on the NTN. For example, as shown in element symbol 525, network entity 510 can send CG-SDT configuration for the NTN. CG-SDT may include parameters such as MAC application TA Kmac, which delays the application of downlink configurations indicated by the MAC control element (MAC CE). The duration of Kmac may include the duration between the UE 520's reception of an initiation command (e.g., downlink control information (DCI)) and the UE 520's application of the initiation command. This parameter may include a time offset Koffset, which delays RACH procedures initiated by entity downlink control channel (PDCCH) communications (e.g., DCI) and uplink transmissions scheduled by the CG. This Koffset may be CG-SDT-specific to the NTN. Koffset may be shared by cell service areas or UE-specific. In some access networks, CG-SDT can be referred to as "Pre-configured Uplink Resource (PUR)".

[0083] As shown in component symbol 530, network entity 510 can send system information for verifying this parameter (which is for NTN). The system information may include, for example, timing relationship verification information for verifying MAC TA Kmac and time offset Koffset.

[0084] As shown in component symbol 535, network entity 510 can use system information to verify the parameter. This may include, for example, using timing relationship verification information to verify MAC TA Kmac and time offset Koffset. Verification may include performing a measurement and determining whether the measurement meets one or more RSRP thresholds (e.g., minimum RSRP, maximum RSRP). Verification may also include determining whether the measurement is performed during a time interval or a timer period.

[0085] UE 520 can execute a RACH procedure to establish an RRC connection with network entity 510. UE 520 can be in an inactive state (e.g., RRC inactive state) to conserve battery power and network resources during infrequent data traffic. "Inactive state" can refer to a UE operating in an inactive communication mode. To re-enter an active state, UE 520 can execute a RACH procedure. The RACH procedure can involve signal transmission in a 2-step (2-step RACH procedure) or 4-step (4-step RACH procedure). As the first step of a 4-step RACH procedure and as indicated by element symbol 540, UE 520 can send a Random Access Message (RAM), which may include a preamble signal (sometimes referred to as a Random Access Preamble Signal, PRACH Preamble Signal, or RAM Preamble Signal). The message including the preamble signal may be referred to as Message 1, msg1, MSG1, First Message, or Initial Message in the 4-step RACH procedure. The Random Access Message may include a Random Access Preamble Signal Identifier.

[0086] Network entity 510 can receive RAM preamble signals sent by UE 520. If network entity 510 successfully receives and decodes the RAM preamble signals, it can then receive and decode the RAM payload. As shown in element symbol 545, network entity 510 can send a Random Access Response (RAR) as a reply to the preamble signals. The message including the RAR may be referred to as message 2, msg2, MSG2, or the second message in the four-step random access procedure. In some cases, the RAR may indicate the detected random access preamble signal identifier (e.g., received from UE 520 in msg1). Alternatively or concurrently, the RAR may indicate the resource allocation to be used by UE 520 to send message 3 (msg3).

[0087] In some configurations, as part of the second step of the 4-step RACH procedure, network entity 510 may send PDCCH communications for RAR. PDCCH communications (e.g., DCI) may schedule entity downlink shared channel (PDSCH) communications that include RAR. For example, PDCCH communications may indicate resource allocation for PDSCH communications. Also as part of the second step of the 4-step RACH procedure, network entity 510 may send PDSCH communications for RAR according to the schedule of the PDCCH communications. PDCCH may include MTC PDCCH (MPDCCH) for MTC devices or NB PDCCH (NPDCCH) for NB-IoT devices. PDSCH may include NB PDSCH (NPDSCH) for NB-IoT devices.

[0088] As indicated by component symbol 550, UE 520 may send an RRC connection request message. The RRC connection request message may be referred to as message 3, msg3, MSG3, or the third message in the 4-step RACH procedure. In some configurations, the RRC connection request may include the UE identifier, uplink control information (UCI), and / or Entity Uplink Shared Channel (PUSCH) communication (e.g., an RRC connection request). The PUSCH may include NB PUSCH (NPUSCH) format 1 for NB-IoT devices. The Entity Uplink Control Channel (PUCCH) may include NPUSCH format 2 for NB-IoT devices. UE 520 may switch between different modes, at least in part, based on various commands and / or communications received from network entity 510, and UE 520 may send an RRC Resume Request in msg3 to transition from an RRC inactive state to an RRC active state. The RRC recovery request can also establish some security for messages from UE 520 to network entity 510 by verifying the identity of UE 520. UE 520 can include data such as SDT in msg3 with the RRC recovery request. SDT can be a small amount of data that can be sent even if UE 520 is not fully connected. In many applications, UE 520 can generate only a small amount of data in a short pulse during data communication. 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. SDT can be configured or scheduled by CG. UE 520 can establish SDT PDCP and send SDT resource blocks (RBs) configured for small data.

[0089] When data arrives for Data Radio Bearers (DRBs) or Signal Radio Bearers (SRBs) enabled by SDT (i.e., SDT RBs), the criteria used to select between SDT and non-SDT procedures include at least the following: UE 520 checks whether the available data amount is less than a data amount threshold, and if both a Normal Uplink Carrier (NUL) and a Supplementary Uplink Carrier (SUL) are configured and SDT resources are configured, UE 520 will perform carrier selection for SDT. UE 520 will determine whether RSRP is greater than or equal to the RSRP threshold configured for SDT. The RSRP threshold is used to select between SDT and non-SDT procedures (if the RSRP threshold is 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. For CG-SDT and RA-SDT, the data amount threshold (used for selecting between SDT and non-SDT procedures) is the same. The RSRP threshold used for carrier selection is SDT-specific (i.e., configured separately for SDT). The RSRP threshold used for random access (RA) type selection is SDT-specific (i.e., configured separately for SDT).

[0090] If the above criteria are met, if the CG-SDT resource is configured and valid on the selected uplink carrier, and if UE 520 can detect that the RSRP of the Synchronization Signal Block (SSB) is higher than the RSRP threshold configured for the CG-SDT standard, then UE 520 selects CG-SDT and initiates RRC recovery for SDT using the selected CG-SDT resource. Otherwise, UE 520 checks whether the RA-SDT resource is configured and valid on the selected UL carrier. This check is similar to the general RACH resource selection and check. If the RA-SDT criteria are met, then UE 520 selects RA-SDT and performs RA-SDT. UE 520 will use an SDT-specific RSRP threshold (e.g., 4-step RA-SDT or 2-step RA-SDT) to perform RA type selection. Otherwise, UE 520 may perform general RRC recovery (i.e., without performing SDT). The SSB's Entity Broadcast Channel (PBCH) may include a per-cell service area PBCH for MTC devices or a per-cell service area NB PBCH (NPBCH) for NB IoT devices.

[0091] For initial CG-SDT transmission, if the RSRP of any SSB is not higher than the RSRP threshold, then UE 520 will not select any SSB. If the RA-SDT standard is met, then UE 520 can select RA-SDT.

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

[0093] As indicated by component symbol 560, UE 520 can use the CG-SDT parameters for NTN to transmit SDT. This can be done during the SDT follow-up data transmission period 562 after the RACH procedure or the configuration for uplink grant. In the follow-up data transmission (after successful contention resolution), UE 520 can use CG to transmit data, or monitor dynamic grant (DG) via Cell Service Area RNTI (C-RNTI) in a separate shared search space (CSS) in RA-SDT (if configured). During the SDT follow-up data transmission period, network entity 510 can allow UE 520 to transmit SDT-type data during RRC inactive or RRC idle states without UE 520 entering RRC connected or RRC active states. UE 520 can transmit SDT-type data from a buffer that holds SDT-type data during the SDT follow-up data transmission period. UE 520 can transmit data until the buffer is empty. As shown in component symbol 565, network entity 510 can respond to uplink data by sending downlink data. As shown in component symbol 570, UE 520 can send additional uplink data, which may or may not include SDT. As shown in component symbol 575, an RRCRelease message can be sent at the end to terminate the SDT procedure from the perspective of RRC.

[0094] The configuration of CG resources used for UE uplink small data transmission can be included in the RRRCRelease message. The RRRCRelease message is also used to reconfigure or release CG-SDT resources when the UE is in RRC inactivity. CG resource configuration can include type 1 CG configuration. Network configuration can support multiple CG-SDT configurations per carrier in RRC inactivity. For CG-SDT, subsequent data transmissions can use either CG resources or DG. UE 520 can support retransmissions for CG-SDT using DG.

[0095] During subsequent new CG transmission phases, UE 520 re-evaluates the SSB for CG resource selection purposes. Because a new UE-specific RNTI for SDT may not exist, UE 520 can monitor PDCCH communications addressed by the C-RNTI in the CG-SDT. The C-RNTI can be pre-configured in the RRC connection. Dynamic retransmission mechanisms based on cell service area-specific RNTIs (CS-RNTIs) can be reused for CG-SDT. UE 520 can start a window after CG / DG transmissions for CG-SDT. UE 520 can support multiple Hybrid Automatic Repeat Request (HARQ) procedures for uplink CG-SDT. CG-SDT resources can be configured on both NUL and SUL. UL carrier selection is performed before CG-SDT selection. UE 520 can release CG-SDT resources when the SDT TA timer (TAT-SDT) expires during RRC inactivity. When UE 520 initiates the RRC recovery procedure from a different cell service area than the one that received the RRC Reseal, UE 520 should release CG-SDT resources (if they are stored).

[0096] By providing and verifying parameters in the NTN-specific CG-SDT configuration, UE 520 can transmit SDT within the NTN. These parameters improve timing alignment and communication between UE 520 and network entity 510. Improved communication saves processing and signal transmission resources.

[0097] As mentioned above, Figure 5 is provided as an example. Other examples may differ from the example described with respect to Figure 5.

[0098] Figure 6 is a schematic diagram illustrating an example 600 of parameters that can be included in the CG-SDT configuration according to the content of this case.

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

[0100] As mentioned above, the CG-SDT configuration can include parameters such as Koffset. Koffset can be configured in the system information and used during initial access, at least in the cell service area-specific Koffset configuration, which is used in all beams within the cell service area. The UE-specific Koffset can be provided and updated by network entity 510 using MAC CE. MAC CE can provide differential UE-specific Koffset values. The complete UE-specific Koffset value can be equal to the cell service area-specific Koffset value minus the differential UE-specific Koffset value. When UE 520 is not provided with a Koffset value other than the Koffset value signaled in the system information, the Koffset value signaled in the system information can be used for all timing relationships requiring Koffset enhancement.

[0101] The Koffset value, signaled in the system information, can be used for the transmission timing of PUSCH in RAR or rollback RAR grant scheduling. The Koffset value can be used for the transmission timing of Msg3 retransmissions scheduled by DCI format 0_0, which have CRC using temporary cell service area RNTI (TC-RNTI) scrambling. The Koffset value can be used for the transmission timing of HARQ acknowledgment (HARQ-ACK) on PUCCH for contention-resolved PDSCH scheduled by DCI format 1_0, which has CRC using TC-RNTI scrambling. The Koffset value can be used for the transmission timing of HARQ-ACK on PUCCH for MsgB scheduled by DCI format 1_0, which has CRC using MsgB-RNTI scrambling.

[0102] Koffset can be applied to indicate the first transmission opportunity for a PUSCH in a configured authorization type 2, in the same way as applying Koffset to the transmission timing of PUSCHs in DCI scheduling. The Koffset value signaled in the system information can be used for the PRACH timing relationship of PDCCH commands. The unit of Koffset can be the number of time slots for a given subcarrier interval. For a random access procedure initiated by a PDCCH command received in a downlink time slot, UE 520 can determine the next available PRACH opportunity after the uplink time slot following the downlink time slot and after the Koffset, to transmit the commanded PRACH.

[0103] For NTN CG-SDT configurations, in some cases, CG-SDT parameters can be NTN-specific and / or supplementary to parameters used for terrestrial networks. For example, parameters used for TA authentication may include NTN-specific RSRP thresholds. These RSRP thresholds may differ from, or supplement, the RSRP thresholds used for terrestrial networks. NTN-specific parameters can be obtained in a UE-specific, cell service area-specific, or satellite-specific manner. The Koffset used for CG-SDT in the NTN can be used for SDT transmissions and for subsequent transmissions after the initial CG-SDT transmission (e.g., new transmissions or retransmissions of PUCCH and PUSCH scheduled by the PDCCH in the CG-SDT search space).

[0104] Several options exist for the Koffset used for CG-SDT in NTN. As a first option, a cell service area shared Koffset (provided in the system information) can be used for subsequent transmissions after the initial CG-SDT transmission. As a second option, the Koffset can be UE-specific, configured when UE 520 is in RRC connected mode, stored, and used for subsequent transmissions after the initial transmission. As a third option, UE 520 can be configured with a separate UE-specific Koffset for CG-SDT in the RRC release message. In any case, network entity 510 can explicitly reconfigure the Koffset in RRC inactive mode.

[0105] Another CG-SDT configuration parameter for NTN can be Kmac, as described above. Kmac information can be carried in the system information. The unit of Kmac can be the number of time slots for a given subcarrier interval. The value range of Kmac can be 1-512 ms. When no Kmac value is provided to UE 520, UE 520 can assume Kmac=0. If UE 520 is provided with a Kmac value, then when UE 520 transmits a PUCCH with HARQ-ACK information in uplink time slot n (this HARQ-ACK information corresponds to the PDSCH carrying the MAC CE command in time slot x in the downlink configuration), it can receive the information from the downlink time slot. The first time slot thereafter applies the UE 520 action based on the downlink configuration, where μ is the subcarrier spacing (SCS) configuration for PUCCH.

[0106] Figure 7 illustrates Example 700 of the command and startup sequence according to the content of this case. Example 700 illustrates the MAC command received at time slot x, the HARQ-ACK information at time slot n, and the MAC command startup at time slot m. Example 700 illustrates an example of applying isochronous alignment of the MAC application between UE 520 and network entity 510 in the NTN using a Kmac. This results in startup at time slot M. The cell service area public Kmac (provided in the system information) can be used for CG-SDT transmission and subsequent transmissions.

[0107] Kmac can represent scheduling offsets other than Koffset. If the downlink and uplink frame timings are aligned at the gNB, Kmac may not be required for UE actions based on downlink configurations indicated by MAC CE commands in the PDSCH. Kmac may not be required for UE actions based on uplink configurations indicated by MAC CE commands in the PDSCH. If the downlink and uplink frame timings are not aligned at the gNB, Kmac may be required for UE actions based on downlink configurations indicated by MAC CE commands in the PDSCH. Kmac may not be required for UE actions based on uplink configurations indicated by MAC CE commands in the PDSCH. Note that this does not preclude identifying anomalous MAC CE timing relationships that may or may not require Kmac.

[0108] This parameter can include or be related to TA. TA can be calculated as TA = (N TA + N {TA,UE-specific} + N {TA,common} + N {TA,offset} ) x T c. N {TA,offset} can depend on the frequency band and LTE / NR coexistence, and is specified in Section 4.2 of 3GPP Technical Specification (TS) 38.213. T c is specified in Section 4.1 of TS 38.211. N {TA,UE-specific} is the UE-estimated TA used for pre-compensation of serving link delay, which is calculated using the UE location and serving satellite ephemeris. For N {TA,offset}, UE 520 can use the indicated higher-layer common TA parameter. If configured, UE 520 can determine the one-way propagation time (Delay_common) used for calculating N {TA,common} as follows: in , and It is the distance between satellite 610 and the uplink time synchronization reference point divided by the speed of light. The downlink and uplink frames are aligned at the reference point with an offset provided by N(TA,offset). The UE is based on the bidirectional transmission delay between the uplink time reference point and satellite 610, which is used for pre-compensation. Come and remit.

[0109] Example 600 illustrates parameters such as timing components in an NTN. For example, a common TA may exist for communication between relay station 620 and satellite 610. The timing between UE 520 and satellite 610 may include a TA (TA) plus a Kmac, which may consist of at least a general TA (KTA), a UE-specific TA (KTA), a common TA (KTA), a Koffset (KTA, offset), and a Kmac (Kmac). At least some of these timing elements are NTN-specific.

[0110] Other parameters may include cell service area stop time, deactivated HARQ feedback, ephemeris information, and / or polarization. Cell service area stop time can be the time during which the cell service area is valid and before satellite movement invalidates it. Currently, broadcasting cell service area stop time in the System Information Block (SIB) may only apply to quasi-fixed cell service areas (not mobile cell service areas), and there is currently no information to resolve any mobile cell service area-specific details associated with using cell service area stop time to assist in measurements or cell service area reselection. For quasi-fixed cell service areas, the broadcast timing information regarding when a cell service area will cease serving the area refers to the time when the cell service area stops covering the current area. In some cases, if the cell service area stop time is broadcast via system information, CG-SDT resources may become invalid after the broadcast cell service area stop time. Additionally, additional time offset information can be provided to the UE 520 in a cell service area-specific or UE-specific manner. If provided, UE 520 may not be allowed to attempt to transmit on PUSCH using CG-SDT after the cell service area stop time minus the additional time offset received by UE 520. SIB may include a reduced-bandwidth SIB (SIB-BR) for MTC devices or an NB SIB (NSIB) for NB IoT devices.

[0111] For downlink HARQ procedures with disabled HARQ feedback, UE 520 is not expected to receive another set of PDSCHs or time-slot aggregated PDSCHs scheduled for a given HARQ procedure that begins some time after the reception of the last PDSCH or time-slot aggregated PDSCH of that HARQ procedure. In some cases, one or more IDs in the CG-SDT HARQ procedure identifiers (IDs) may be disabled HARQ feedback, and this configuration may be UE-specific.

[0112] Network entity 510 can indicate polarization information for downlink and uplink. Uplink polarization information can be indicated in the SIB. When uplink polarization information is not available, UE 520 can assume the same polarization for uplink and downlink. When polarization signaling is present in the SIB, the SIB can use the appropriate polarization type parameters (e.g., RHCP, LHCP, or linear) to indicate downlink and / or uplink polarization information. For target serving cell service areas, polarization signaling can be supported in the handover command message, or for non-serving cell service areas, polarization signaling can be supported in the Radio Resource Management (RRM) measurement configuration. In some cases, network entity 510 can signal uplink and / or downlink polarization characteristics to UE 520, and this configuration can be satellite-specific and / or cell service area-specific (e.g., UE 520 can obtain this information from system information).

[0113] This parameter may include ephemeris information, which is information related to the trajectory of satellites and / or astronomical objects. Other parameters may include the epoch time (based on reference time) and common TA (NTA) for autonomous pre-compensation of transmission timing (open loop timing adjustment). This parameter may include the validity duration configured by the network for satellite ephemeris data, which indicates the maximum time that UE 520 can apply satellite ephemeris without acquiring new satellite ephemeris. If new or additional ancillary information (i.e., serving satellite ephemeris data or common TA parameters) is unavailable within the associated validity duration, UE 520 may assume that UE 520 has lost uplink synchronization. The NTN ephemeris validity timer should be started / restarted at the epoch time of the ancillary information (i.e., serving satellite ephemeris data) with the configured timer validity duration. A single validity duration may be defined for both serving satellite ephemeris and common TA parameters, at least when signaled in the same SIB message. A single validity duration for both service satellite ephemeris and shared TA-related parameters can be broadcast on the SIB. UE 520 can read system information from the cell service area (satellite-specific). If the validity duration expires, UE 520 can read system information before the initial and subsequent CG-SDT transmissions.

[0114] This parameter may also include cell service area and / or satellite information. The availability of CG-SDT in a UE-specific configuration may not be limited to a single cell service area (i.e., depending on the configuration, when CG-SDT is configured, it may be available in different cell service areas within the same satellite to which the UE 520 is connected, or across satellites). In this scenario, if adjustments are required when the UE 520 moves to one of the cell service areas in the list of cell service areas and / or satellites, the UE 520 may be configured with this list and the set of CG-SDT parameters.

[0115] As mentioned above, Figures 6 and 7 are provided as examples. Other examples may differ from those described for Figures 6 and 7.

[0116] Figure 8 is a schematic diagram illustrating an example 800 of an isochronous line used to provide configuration and system information according to the contents of this case.

[0117] Example 800 illustration: Network entity 510 (e.g., gNB) can send UE-specific CG-SDT configuration and periodically send system information for verifying parameters of the CG-SDT configuration. The UE-specific CG-SDT configuration can be used for PUSCH and / or PUCCH configuration, may include search space configuration for CG-SDT, and may include all or part of the verification criteria and parameters. The system information may include information related to CG-SDT verification associated with the verification criteria (e.g., ephemeris information, NTA, common).

[0118] In some configurations, the UE 520 may meet the following four verification criteria (if configured) for uplink transmissions of CG-SDT: TA verification, timing relationship verification, link quality verification, and cell service area and / or satellite availability verification. Subsequent transmissions after the initial CG-SDT transmission should still meet all or some of these criteria.

[0119] For TA verification, in addition to traditional (terrestrial network) RSRP-based TA verification, some parameters may also be involved, including ephemeris information, NTA, common, and epoch time used for TA verification. UE 520 can receive system information from the cell service area (e.g., satellite-specific). If the validity period expires, UE 520 can read the system information before the initial and subsequent CG-SDT transmissions. Another parameter used for TA verification may include UE location updates. If UE 520 is equipped with a Global Navigation Satellite System (GNSS), UE 520 can update its location based on GNSS readings before transmitting in RRC inactivity. If UE 520 is not equipped with GNSS (e.g., NTN-IoT) and must rely on the TA obtained from network entity 510, and if UE 520 is configured with a timer that allows UE 520 to apply the same TA to uplink transmissions until the configured timer expires, then UE 520 may not use CG-SDT if the remaining time until the timer expires is less than or equal to A ms or B time slots (which are SCS relative to the bandwidth portion (BWP) configured for CG-SDT). A and / or B may be configured by network entity 510 or hardcoded in stored configuration information (according to the standard). UE 520 may reset and restart the timer upon receiving a timing advance command (TAC), or if CG-SDT is reconfigured during RRC inactivity (e.g., the timer is extended).

[0120] UE 520 can use system information to verify timing relationships. Timing relationship verification may involve Kmac and / or Koffset (if configured and included as part of the CG-SDT verification conditions) and can be maintained before uplink transmissions for CG-SDT. If Kmac is not included as part of the verification conditions, it can be signaled separately after the initial CG-SDT transmission. For example, UE 520 can receive PDSCH communications, including Kmac information, scheduled by PDCCH communications within the CG-SDT search space.

[0121] UE 520 can use system information to verify link quality. PDCCH and PDSCH communication can follow the initial transmission on CG-SDT. Link quality verification against downlink receive RSRP thresholds (e.g., + / - RSRP thresholds, RSRP thresholds for TA verification in terrestrial networks) can be used for link quality verification. If the RSRP change relative to a reference RSRP is greater than a specified RSRP threshold, UE 520 may not use CG-SDT. The reference time point (at which the reference RSRP should be measured) can be defined separately and differ from the reference time point used for terrestrial networks (e.g., the reference RSRP is only updated when CG-SDT is configured or reconfigured).

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

[0123] UE 520 can use system information to verify cell service area and / or satellite availability. This may include verifying the cell service area stop time. If the cell service area stop time is broadcast via system information, UE 520 may not use CG-SDT if the remaining time until the cell service area stop time is less than or equal to Yms or Z time slots (which are relative to the SCS of the BWP configured for CG-SDT). Y and / or Z may be configured by network entity 510 and / or hardcoded in stored configuration information. In some cases, if UE 520 receives a TA command or reconfigures the timer via RRC dedicated signal transmission, the cell service area stop time is restarted.

[0124] If a UE-specific configured CG-SDT can be used after (re)selecting a cell service area, then UE 520 can verify the above criteria for the newly (re)selected cell service area and / or satellite. If the newly (re)selected cell service area belongs to the same satellite as the cell service area configured with CG-SDT, then if the criteria are shared between cell service areas, UE 520 can skip a portion of the above criteria.

[0125] Depending on the satellite type to which the cell service area belongs (e.g., GSO, NGSO), some of the above criteria can be defined differently. For example, if the target cell service area belongs to a GSO satellite, UE 520 may be exempt from updating ephemeris information, and NTA,common may be exempt from verification conditions. Different verification criteria can be performed in different time windows, including in terms of the verification frequency before using CG-SDT resources and the start / end positions of verification.

[0126] By using and verifying the parameters configured for NTN's CG-SDT, UE 520 and network entity 510 can improve communication and save resources.

[0127] Example 800 also illustrates the initial transmission of PUSCH CG-SDT by UE 520 and PDCCH communication from network entity 510 (in the CG-SDT search space). PDCCH communication can be used for new PUSCH transmissions or PUSCH retransmissions. PDCCH communication can be used for PDSCH communication or PUCCH communication.

[0128] Example 800 also illustrates subsequent transmissions and receptions after CG-SDT. In some cases, uplink transmission timing requirements can be applied during subsequent transmissions following the initial transmission of CG-SDT, as is the case with Discontinuous Receive (DRX). For example, UE 520 can apply gradual TA adjustments (e.g., as needed) to subsequent transmissions. This contrasts with the initial uplink transmission timing accuracy requirements currently applied to the initial transmission of CG-SDT.

[0129] If UE 520 receives a TAC during subsequent transmissions, UE 520 can apply the TA adjustment accuracy requirement to subsequent transmissions after a TA adjustment delay following the receipt of the TAC. In some cases, UE 520 can maintain a TAC-based closed-loop TA during subsequent transmissions after receiving the TAC. The closed-loop TA can be reset at the next timing of CG-SDT.

[0130] As mentioned above, Figure 8 is provided as an example. Other examples may differ from the example described with respect to Figure 8.

[0131] Figure 9 is a schematic diagram illustrating an exemplary procedure 900 performed by a UE, for example, according to the contents of this case. The exemplary procedure 900 is an instance in which a UE (e.g., UE 520) performs operations associated with using CG-SDT configuration for NTN.

[0132] As shown in Figure 9, in some cases, 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, a UE (e.g., using the communication manager 1108 and / or receiving element 1102 shown in Figure 11) may receive a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN, as described above.

[0133] As further shown in Figure 9, in some configurations, process 900 may include receiving system information associated with the verification of the parameter used for CG-SDT on the NTN (block 920). For example, the UE (e.g., using the communication manager 1108 and / or receiving element 1102 shown in Figure 11) may receive system information associated with the verification of the parameter used for CG-SDT on the NTN, as described above.

[0134] As further shown in Figure 9, in some cases, process 900 may include sending an SDT to a network entity of the NTN using one or more of these parameters (block 930). For example, a UE (e.g., using the communication manager 1108 and / or transmission element 1104 shown in Figure 11) may send an SDT to a network entity of the NTN using one or more of these parameters, as described above.

[0135] Process 900 may include additional states, such as any single state or any combination of states described below and / or in conjunction with one or more other process descriptions described in other parts of this document.

[0136] In the first state, receiving system information associated with CG-SDT verification includes: periodically receiving system information associated with CG-SDT verification.

[0137] In the second state sample, either alone or in combination with the first state sample, the parameter includes the MAC application TA Kmac for delaying the application of the downlink configuration indicated by the MAC CE.

[0138] In the third state sample, either alone or in combination with one or more states in the first or second state sample, the parameter includes a time offset Koffset for delaying the RACH procedure initiated by PDCCH communication and delaying the uplink transmission scheduled by CG, and the time offset Koffset is specific to CG-SDT on NTN.

[0139] In the fourth state sample, the time offset Koffset is shared by the cell service area, either alone or in combination with one or more states from the first to third states.

[0140] In the fifth state, the time offset Koffset is UE-specific, either alone or in combination with one or more states from the first to fourth states.

[0141] In the sixth state sample, either alone or in combination with one or more state samples from the first to fifth states, the system information includes timing relationship verification information for verifying MAC TA Kmac and time offset Koffset, and the process 900 includes: using the timing relationship verification information to verify MAC TA Kmac and time offset Koffset.

[0142] In the seventh state, either alone or in combination with one or more states from the first to the sixth state, the parameter includes ephemeris information and shared TA.

[0143] In the eighth state sample, either alone or in combination with one or more of the first to seventh state samples, the system information includes TA verification information for the verification ephemeris information or the shared TA, and the process 900 includes: using the TA verification information to verify the ephemeris information or the shared TA.

[0144] In the ninth state, either alone or in combination with one or more states from the first to the eighth state, the use of the TA verification information to verify the ephemeris information or the shared TA includes: at least in part based on one or more of the UE's position or timers, using the TA verification information to verify the epoch time or validity duration of the ephemeris information or the shared TA for CG-SDT.

[0145] In the tenth state sample, either alone or in combination with one or more states from the first to the ninth state samples, the parameter includes parameters used for deactivating the HARQ CG-SDT process in the NTN.

[0146] In the eleventh state sample, either alone or in combination with one or more of the first to tenth state samples, the parameter includes the polarization parameter for CG-SDT on the NTN.

[0147] In the twelfth state sample, either alone or in combination with one or more of the first to eleventh state samples, process 900 includes: receiving an indication of a cell service area-specific or UE-specific time offset, and the parameter includes a cell service area stop time during which the cell service area is valid for CG-SDT on the NTN, and after the end of the cell service area stop time minus the time offset, restricting the UE from transmitting CG-SDT on the NTN.

[0148] In the thirteenth state sample, either alone or in combination with one or more states from the first to the twelfth states, the parameter includes cell service area parameters configured for CG-SDT on the NTN or satellite parameters configured for CG-SDT on the NTN.

[0149] In the fourteenth state sample, either alone or in combination with one or more of the first to thirteenth state samples, the system information includes TA verification information specific to CG-SDT, and process 900 includes: using the TA verification information to verify the TA for CG-SDT on NTN.

[0150] In the fifteenth state sample, either alone or in combination with one or more state samples from the first to fourteenth states, the system information includes link quality verification information for verifying the link quality of the CG-SDT on the NTN, and the process 900 includes: using the link quality verification information to verify the link quality of the CG-SDT on the NTN.

[0151] In the sixteenth state sample, verifying the link quality of CG-SDT on the NTN, either alone or in combination with one or more state samples from the first to the fifteenth state samples, includes: verifying the link quality of CG-SDT on the NTN using a measurement threshold for CG-SDT or a power level threshold for CG-SDT on the NTN, wherein the measurement duration of the measurement threshold for CG-SDT differs from that of the measurement threshold for CG-SDT on the terrestrial network, and the power level threshold for CG-SDT on the NTN differs from that of the power level threshold for CG-SDT on the terrestrial network.

[0152] In the seventeenth state sample, either alone or in combination with one or more states from the first to the sixteenth states sample, the system information includes cell service area or satellite verification information for verifying the cell service area or satellite for CG-SDT, and the process 900 includes: using the cell service area or satellite verification information to verify the cell service area or satellite for CG-SDT.

[0153] In the eighteenth sample, either alone or in combination with one or more samples from the first to the seventeenth samples, the verification of the cell service area or satellite for CG-SDT includes: using the cell service area or satellite verification information to verify the cell service area stop time that is valid for CG-SDT on the NTN during its service period.

[0154] In the nineteenth state sample, either alone or in combination with one or more states from the first to the eighteenth states, process 900 includes: skipping the verification of the parameter for the CG-SDT on the NTN based at least in part on the CG-SDT configuration.

[0155] In the twentieth state, either alone or in combination with one or more states from the first to the nineteenth states, it further includes: applying timing advance adjustment to subsequent uplink transmissions after sending the SDT.

[0156] In the 21st state sample, either alone or in combination with one or more of the 1st to 20th state samples, process 900 includes: receiving a TAC, maintaining the TAC-based closed loop timing advance during subsequent uplink transmissions, and resetting the closed loop timing advance in the next transmission opportunity of the CG-SDT on the NTN.

[0157] Although Figure 9 illustrates exemplary blocks of process 900, in some versions, process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those shown in Figure 9. Alternatively, two or more blocks of process 900 may be executed concurrently.

[0158] Figure 10 is a schematic diagram illustrating an exemplary process 1000 performed, for example, by a network entity according to the content of this case. The exemplary process 1000 is an example in which a network entity (e.g., network entity 510) performs operations associated with sending CG-SDT configuration for NTN.

[0159] As shown in Figure 10, in some cases, process 1000 may include: sending a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN (block 1010). For example, a network entity (e.g., using the communication manager 1208 and / or transmission element 1204 shown in Figure 12) may send a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN, as described above.

[0160] As further shown in Figure 10, in some configurations, process 1000 may include sending system information associated with the verification of the parameter used for CG-SDT on the NTN (block 1020). For example, a network entity (e.g., using the communication manager 1208 and / or transmission element 1204 shown in Figure 12) may send system information associated with the verification of the parameter used for CG-SDT on the NTN, as described above.

[0161] As further shown in Figure 10, in some configurations, process 1000 may include receiving the SDT (block 1030) at least partially based on one or more of the parameters. For example, a network entity (e.g., using the communication manager 1208 and / or receiving element 1202 shown in Figure 12) may receive the SDT at least partially based on one or more of the parameters, as described above.

[0162] Process 1000 may include additional states, such as any single state or any combination of states described below and / or in conjunction with one or more other process descriptions described in other parts of this document.

[0163] In the first state, the parameter includes MAC application timing advance (TA) Kmac, which is used to delay the application configured by the downlink as indicated by the MAC CE.

[0164] In the second state, either alone or in combination with the first state, the parameter includes a time offset Koffset for delaying random access procedures initiated by physical downlink control channel communication and delaying uplink transmissions scheduled by CG, and the time offset Koffset is specific to CG-SDT on NTN.

[0165] In the third state sample, either alone or in combination with one or more states from the first and second states, the system information includes timing relationship verification information for verifying MAC TA Kmac and time offset Koffset.

[0166] In the fourth state sample, either alone or in combination with one or more of the first to third state samples, the parameter includes ephemeris information and a shared TA, and the system information includes TA verification information for verifying the validity duration of the ephemeris information or the shared TA.

[0167] In the fifth state sample, either alone or in combination with one or more state samples from the first to fourth states, the system information includes one or more of the following: TA verification information specific to CG-SDT, link quality verification information for verifying the link quality of CG-SDT on NTN, or cell service area or satellite verification information for verifying cell service areas or satellites for CG-SDT.

[0168] In the sixth state sample, either alone or in combination with one or more of the first to fifth state samples, it further includes: receiving a subsequent uplink transmission with TA adjustment after receiving the SDT.

[0169] In the seventh state sample, either alone or in combination with one or more of the first to sixth state samples, process 1000 includes: sending a TAC, maintaining the TAC-based closed loop timing advance during subsequent uplink transmissions, and resetting the closed loop timing advance in the next transmission opportunity of CG-SDT on the NTN.

[0170] Although Figure 10 illustrates various exemplary blocks of process 1000, in some versions, process 1000 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to those shown in Figure 10. Alternatively, two or more blocks of process 1000 may be executed concurrently.

[0171] Figure 11 is a schematic diagram of an exemplary device 1100 for wireless communication. Device 1100 may be a UE (e.g., UE 520), or a UE may include device 1100. In some embodiments, device 1100 includes a receiving element 1102 and a transmitting element 1104, which can communicate with each other (e.g., via one or more buses and / or one or more other elements). As shown, device 1100 can use the receiving element 1102 and the transmitting element 1104 to communicate with another device 1106 (such as a UE, base station, or another wireless communication device). As further shown, device 1100 may include a communication manager 1108. Communication manager 1108 can control and / or otherwise manage one or more operations of the receiving element 1102 and / or the transmitting element 1104. In some embodiments, communication manager 1108 may include one or more antennas, a modem, a controller / processor, memory, or a combination thereof of the UE 120 described in conjunction with Figure 2. Communication manager 1108 may be, or may be similar to, communication manager 150 shown in Figures 1 and 2. For example, in some embodiments, communication manager 1108 may be configured to perform one or more of the functions described as being performed by communication manager 150. In some embodiments, communication manager 1108 may include receiving element 1102 and / or transmitting element 1104. Communication manager 1108 may also include authentication element 1110, etc.

[0172] In some embodiments, device 1100 may be configured to perform one or more operations described herein in conjunction with Figures 1-8. Alternatively, device 1100 may be configured to perform one or more processes described herein, such as process 900 of Figure 9. In some embodiments, device 1100 and / or one or more elements shown in Figure 11 may include one or more elements of the UE described in conjunction with Figure 2. Alternatively, one or more elements shown in Figure 11 may be implemented within one or more elements described in conjunction with Figure 2. Alternatively, one or more elements in the set of elements may be implemented at least partially as software stored in memory. For example, an element (or a portion of an element) 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 that element.

[0173] Receiver 1102 may receive communications from device 1106, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other elements of device 1100. In some embodiments, receiver 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signal to one or more other elements of device 1100. In some embodiments, receiver 1102 may include one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof, of the UE described in conjunction with FIG. 2.

[0174] Transmission element 1104 can send communications, such as reference signals, control information, data communications, or combinations thereof, to device 1106. In some embodiments, one or more other elements of device 1100 can generate communications and provide the generated communications to transmission element 1104 for transmission to device 1106. In some embodiments, transmission element 1104 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 1106. In some embodiments, transmission element 1104 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof, as described in conjunction with FIG. 2. In some embodiments, transmission element 1104 may coexist with receiver element 1102 in a transceiver.

[0175] The receiving element 1102 can receive a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. The receiving element 1102 can also receive system information associated with the verification of these parameters for the CG-SDT on the NTN. The transmitting element 1104 can use one or more of these parameters to send the SDT to the network entity of the NTN.

[0176] The receiving element 1102 can receive an indication of a cell service area-specific or UE-specific time offset, which may include a cell service area stop time during which the cell service area is valid for CG-SDT on the NTN, and may restrict the UE from sending CG-SDT on the NTN after the cell service area stop time ends and the time offset is subtracted.

[0177] Verification element 1110 can skip verification of this parameter for CG-SDT on NTN, at least in part, based on the CG-SDT configuration.

[0178] Receiver 1102 can receive TAC. Transmitter 1104 can maintain TAC-based closed-loop timing advance during subsequent uplink transmissions. Transmitter 1104 can reset closed-loop timing advance in the next transmission opportunity of CG-SDT on NTN.

[0179] The number and arrangement of elements shown in Figure 11 are provided as examples. In practice, additional elements, fewer elements, different elements, or elements with different arrangements may exist compared to those shown in Figure 11. Furthermore, two or more elements shown in Figure 11 may be implemented within a single element, or a single element shown in Figure 11 may be implemented as multiple distributed elements. Alternatively or alternatively, a set of (one or more) elements shown in Figure 11 may perform one or more functions described as being performed by another set of elements shown in Figure 11.

[0180] Figure 12 is a schematic diagram of an exemplary device 1200 for wireless communication. Device 1200 may be a network entity (e.g., network entity 510), or a network entity may include device 1200. In some embodiments, device 1200 includes a receiving element 1202 and a transmitting element 1204, which can communicate with each other (e.g., via one or more buses and / or one or more other elements). As shown, device 1200 can use the receiving element 1202 and the transmitting element 1204 to communicate with another device 1206 (such as a UE, base station, or another wireless communication device). As further shown, device 1200 may include a communication manager 1208. Communication manager 1208 may control and / or otherwise manage one or more operations of the receiving element 1202 and / or the transmitting element 1204. In some embodiments, communication manager 1208 may include one or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entity described in conjunction with Figure 2. Communication manager 1208 may be, or may be similar to, communication manager 150 shown in Figures 1 and 2. For example, in some embodiments, communication manager 1208 may be configured to perform one or more of the functions described as being performed by communication manager 150. In some embodiments, communication manager 1208 may include receiving element 1202 and / or transmitting element 1204. Communication manager 1208 may include generating element 1210, etc.

[0181] In some embodiments, device 1200 may be configured to perform one or more operations described herein in conjunction with Figures 1-8. Alternatively, device 1200 may be configured to perform one or more processes described herein, such as process 1000 of Figure 10. In some embodiments, device 1200 and / or one or more elements shown in Figure 12 may include one or more elements of the network entity described in conjunction with Figure 2. Alternatively, one or more elements shown in Figure 12 may be implemented within one or more elements described in conjunction with Figure 2. Alternatively, one or more elements in the set of elements may be implemented at least partially as software stored in memory. For example, an element (or a portion of an element) 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 that element.

[0182] Receiver 1202 may receive communications from device 1206, such as reference signals, control information, data communications, or combinations thereof. Receiver 1202 may provide the received communications to one or more other elements of device 1200. In some embodiments, receiver 1202 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signal to one or more other elements of device 1200. In some embodiments, receiver 1202 may include one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof, in conjunction with the network entities described in FIG. 2.

[0183] Transmitting element 1204 can send communications, such as reference signals, control information, data communications, or combinations thereof, to device 1206. In some embodiments, one or more other elements of device 1200 can generate communications and provide the generated communications to transmitting element 1204 for transmission to device 1206. In some embodiments, transmitting element 1204 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 1206. In some embodiments, transmitting element 1204 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof, in conjunction with the network entities described in FIG. 2. In some embodiments, transmitting element 1204 may coexist with receiving element 1202 in a transceiver.

[0184] Generating element 1210 can generate a UE-specific CG-SDT configuration with parameters specific to the CG-SDT in the NTN. Transmitting element 1204 can transmit the CG-SDT configuration for the NTN. Transmitting element 1204 can transmit system information associated with the verification of these parameters for the CG-SDT on the NTN. Receiving element 1202 can receive the SDT based at least in part on one or more of these parameters.

[0185] Transmitting element 1204 can send a TAC. Receiving element 1202 can maintain the closed-loop timing advance based on the TAC during subsequent uplink transmissions. Receiving element 1202 can reset the closed-loop timing advance in the next transmission opportunity of CG-SDT on the NTN.

[0186] The number and arrangement of elements shown in Figure 12 are provided as examples. In practice, additional elements, fewer elements, different elements, or elements with different arrangements may exist compared to those shown in Figure 12. Furthermore, two or more elements shown in Figure 12 may be implemented within a single element, or a single element shown in Figure 12 may be implemented as multiple distributed elements. Alternatively or alternatively, a set of (one or more) elements shown in Figure 12 may perform one or more functions described as being performed by another set of elements shown in Figure 12.

[0187] The following provides an overview of some aspects of the case:

[0188] Sample 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving a UE-specific CG-SDT configuration having parameters for Configurable Authorized (CG) Small Data Transmission (SDT) (CG-SDT) specific to a non-terrestrial network (NTN); receiving system information associated with verification 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.

[0189] State 2: According to the method of State 1, receiving system information associated with CG-SDT verification includes: periodically receiving system information associated with CG-SDT verification.

[0190] State 3: According to the method of State 1 or 2, wherein the parameter includes MAC application timing advance (TA) Kmac for delaying the application of the downlink configuration indicated by the Media Access Control (MAC) control element (MAC CE).

[0191] State 4: According to the method of State 3, wherein the parameter includes a time offset Koffset for delaying the random access procedure initiated by the entity downlink control channel communication and delaying the uplink transmission scheduled by the CG, and wherein the time offset Koffset is specific to the CG-SDT on the NTN.

[0192] State 5: Based on the method of State 4, where the time offset Koffset is shared by the cell service area.

[0193] State 6: According to the method of State 4, where the time offset Koffset is UE-specific.

[0194] State 7: According to the method of State 6, wherein the time offset Koffset is configured when the UE is in Radio Resource Control Connection Mode.

[0195] State 8: According to the method of State 6, wherein the time offset Koffset is a separate UE-specific Koffset configured in the Radio Resource Control Release Message for CG-SDT.

[0196] State 9: According to the method of State 6, wherein the time offset Koffset is reconfigured in the radio resource control inactive mode.

[0197] State 10: The method according to any one of States 4-9, wherein the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset, and wherein the method further includes: using the timing relationship verification information to verify the MAC TA Kmac and the time offset Koffset.

[0198] State 11: According to the method of State 3, wherein the MAC TA Kmac is received in a separate message in the CG-SDT search space.

[0199] State 12: The method according to any one of states 1-11, wherein the parameter includes ephemeris information and common timing advance (TA).

[0200] State 13: According to the method of State 12, wherein the system information includes TA verification information for verifying the ephemeris information or the shared TA, and wherein the method further includes: using the TA verification information to verify the ephemeris information or the shared TA.

[0201] State 14: According to the method of State 13, wherein using the TA verification information to verify the ephemeris information or the shared TA includes: using the TA verification information to verify the epoch time or validity duration of the ephemeris information or the shared TA for CG-SDT, at least in part based on one or more of the UE's location or timers.

[0202] State 15: The method according to any one of states 1-14, wherein the parameter includes parameters for enabling the Mixed Automatic Repeat Request (CG-SDT) process on the NTN.

[0203] State 16: The method according to any one of states 1-15, wherein the parameter includes the polarization parameter for CG-SDT on NTN.

[0204] State 17: The method according to any one of states 1-16 further includes: receiving an indication of a cell service area-specific or UE-specific time offset, wherein the parameter includes a cell service area stop time during which the cell service area is valid for CG-SDT on the NTN, and after the end of the cell service area stop time minus the time offset, restricting the UE from transmitting CG-SDT on the NTN.

[0205] State 18: The method according to any one of states 1-17, wherein the parameter includes cell service area parameters configured for CG-SDT on NTN or satellite parameters configured for CG-SDT on NTN.

[0206] State 19: The method according to any one of states 1-18, wherein the parameter includes a set of CG-SDT parameters associated with a configured list of cell service areas.

[0207] Sample 20: The method according to any one of Samples 1-19, wherein the parameter includes a set of CG-SDT parameters associated with a configured list of satellites.

[0208] State 21: The method according to any one of states 1-20, wherein the system information includes timing advance (TA) verification information specific to CG-SDT, and wherein the method further includes: using the TA verification information to verify the TA for CG-SDT on NTN.

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

[0210] Sample 23: The method according to any one of Samples 1-22, wherein the system information includes link quality verification information for verifying the link quality of CG-SDT on NTN, and wherein the method further includes: using the link quality verification information to verify the link quality of CG-SDT on NTN.

[0211] Sample 24: According to the method of Sample 23, verifying the link quality of CG-SDT on NTN includes: using a measurement threshold for CG-SDT or a power level threshold for CG-SDT on NTN to verify the link quality of CG-SDT on NTN, wherein the measurement duration of the measurement threshold for CG-SDT is different from that of the measurement threshold for CG-SDT on terrestrial networks, and the power level threshold for CG-SDT on NTN is different from that of the power level threshold for CG-SDT on terrestrial networks.

[0212] State 25: The method according to any one of States 1-24, wherein the system information includes cell service area or satellite verification information for verifying cell service areas or satellites for CG-SDT, and wherein the method includes: using the cell service area or satellite verification information to verify cell service areas or satellites for CG-SDT.

[0213] Sample 26: According to the method of Sample 25, wherein verifying the cell service area or satellite for CG-SDT includes: using the cell service area or satellite verification information to verify the cell service area stop time that is effective for CG-SDT on NTN during its service period.

[0214] State 27: According to the method of State 26, if the UE receives a timing advance command or the timer is reconfigured via a dedicated radio resource control signal, the cell service area stop time is restarted.

[0215] State 28: The method according to any one of states 1-27 further includes: skipping the verification of the parameter for CG-SDT on NTN based at least in part on the CG-SDT configuration.

[0216] State 29: The method according to any one of states 1-28, wherein the one or more processors are configured to: skip the verification of the parameter for CG-SDT on NTN based at least in part on the fact that the newly reselected cell service area belongs to the same satellite as the previous cell service area and has a shared standard with the previous cell service area.

[0217] State 30: The method according to any one of states 1-29, wherein the one or more processors are configured to: skip the verification of the parameter for CG-SDT on NTN based at least in part on the satellite type associated with the cell service area.

[0218] State 31: The method according to any one of states 1-30, wherein the one or more processors are configured to perform verification of the parameter for CG-SDT on NTN within one or more time windows.

[0219] State 32: The method according to any one of states 1-31 further includes: after the transmission of SDT, applying timing advance adjustment to subsequent uplink transmissions.

[0220] State 33: The method according to any one of states 1-32 further includes: receiving a timing advance command (TAC); maintaining the closed loop timing advance based on the TAC during subsequent uplink transmission; and resetting the closed loop timing advance in the next transmission opportunity of CG-SDT on the NTN.

[0221] Sample 34: A method of wireless communication performed by a network entity of a non-terrestrial network (NTN), comprising: transmitting a user equipment (UE) specific CG-SDT configuration having parameters of a Configurable Authorized (CG) Small Data Transmission (SDT) (CG-SDT) specific to the NTN; transmitting system information associated with authentication of the parameters for the CG-SDT on the NTN; and receiving the SDT based at least in part on one or more of the parameters.

[0222] State 35: According to the method of State 34, wherein the parameter includes MAC application timing advance (TA) Kmac for delaying the application of the downlink configuration indicated by the Media Access Control (MAC) control element (MAC CE).

[0223] State 36: According to the method of State 35, wherein the parameter includes a time offset Koffset for delaying the random access procedure initiated by the entity downlink control channel communication and delaying the uplink transmission scheduled by the CG, and wherein the time offset Koffset is specific to the CG-SDT on the NTN.

[0224] State 37: According to the method of State 36, the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset.

[0225] Sample 38: The method according to any one of Samples 34-37, wherein the parameter includes ephemeris information and common timing advance (TA), and wherein the system information includes TA verification information for verifying the validity duration of the ephemeris information or the common TA.

[0226] Sample 39: The method according to any one of Samples 34-38, wherein the system information includes one or more of the following: timing advance (TA) verification information specific to CG-SDT, link quality verification information for verifying the link quality of CG-SDT on NTN, or cell service area or satellite verification information for verifying cell service area or satellite for CG-SDT.

[0227] State 40: The method according to any one of states 34-39 further includes: after receiving the SDT, receiving a subsequent uplink transmission with timing advance adjustment.

[0228] State 41: The method according to any one of states 34-40 further includes: sending a timing advance command (TAC); maintaining the closed loop timing advance based on the TAC during subsequent uplink transmission; and resetting the closed loop timing advance in the next transmission opportunity of CG-SDT on the NTN.

[0229] Version 42: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of versions 1-41.

[0230] Sample 43: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to any one of Samples 1-41.

[0231] Sample 44: An apparatus for wireless communication, comprising at least one component for performing the method according to any one of Samples 1-41.

[0232] Sample 45: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of Samples 1-41.

[0233] Sample 46: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of the device, cause the device to perform the method according to any one of Samples 1-41.

[0234] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the various forms to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or modifications and variations can be derived from the practice of such forms.

[0235] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. "Software" should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, executable threads, programs and / or functions, etc., regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It is evident that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement such systems and / or methods is not limited to this type of implementation. Therefore, this document describes the operation and behavior of the system and / or method without reference to any specific software code, as those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0236] As used in this article, depending on the context, "meeting the threshold" can mean: a value greater than the threshold, a value greater than or equal to the threshold, a value less than the threshold, a value less than or equal to the threshold, a value equal to the threshold, a value not equal to the threshold, etc.

[0237] Although specific combinations of features are described in the request and / or disclosed in the specification, such combinations are not intended to limit the disclosure of individual states. Many of these features may be combined in ways not specifically described in the request and / or disclosed in the specification. The disclosure of individual states includes each dependent request combined with other requests in each of the request sets. As used herein, the term "at least one" in the list of items refers to any combination of such items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c, 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 ordering of a, b, and c).

[0238] No element, operation, or instruction used herein should be construed as critical or necessary unless explicitly stated otherwise. Furthermore, as used herein, the article "a (a, an)" is intended to include one or more items and may be used interchangeably with "one or more." Furthermore, as used herein, the article "the" is intended to include one or more items referenced in connection with the article "the," and may be used interchangeably with "the one or more." Furthermore, as used herein, the terms "collection" and "group" are intended to include one or more items and may be used interchangeably with "one or more." Where the intent is only one item, the term "only one" or similar language is used. Furthermore, as used herein, the term "has (has, have, having)" or similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., an element "having" A may also have B). Furthermore, unless explicitly stated otherwise, the term "based on" is intended to mean "at least partially based on." Furthermore, as used herein, the term "or" is intended to be inclusive when used consecutively and may be used interchangeably with "and / or" unless otherwise expressly stated (e.g., when used in conjunction with "one of the two" or "only one of them").

[0239] 100: Wireless Network 102a: Macrocell Service Area 102b: Microcell Service Area 102c: Nanoparticle service area 110:Base station 110a: Macro Base Station 110b: Micro Base Station 110c: Femtocell Base Station 110d: Relay Base Station 120:UE 120a:UE 120b:UE 120c:UE 120d:UE 120e:UE 130: Network Controller 135: Satellite 136: Circular Polarization 138: Linear Polarization 140: Communication Manager 150: Communication Manager 200: Examples 212: Source 220: Launch Processor 230: TXMIMO processor 232a: Modem 232t: Modem 234a: Antenna 234t: Antenna 236: MIMO Detector 238: Receiver Processor 239: Data Slot 240: Controller / Processor 242: Memory 244: Communication Unit 246: Scheduler 252a: Antenna 252r: Antenna 254a: Modem 254r: Modem 256: MIMO Detector 258: Receiver Processor 260: Data Slot 262: Source 264: Send Processor 266: TXMIMO processor 280: Controller / Processor 282: Memory 284: Outer shell 290: Controller / Processor 292: Memory 294: Communication Unit 300: Non-converged base station 305: Service Management and Orchestration (SMO) Framework 310: Central Unit 311: Open eNB 315: Non-RTRIC 320: Core Network 325: Near-RTRIC 330: Distributed Unit 340: Radio Unit 390: Open Cloud 400: Deployment of Regenerative Satellites 410: Transparent Satellite Deployment 420: Satellite 430: Service Link 440: Satellite 450: Gate 460: Feeder Link 500: Instance 510: Network Entity 520:UE 525: Operation 530: Operation 535: Operation 540: Operation 545: Operation 550: Operation 555: Operation 560: Operation 562: Transmission period 565: Operation 570: Operation 575: Operation 600: Instance 610: Satellite 620: Relay Station 700: Instance 800: Instance 900: Process 910: UE-specific CG-SDT configuration 920: Operation 930: Operation 1000: Process 1010: Operation 1020: Operation 1030: Operation 1100: Device 1102: Receiving element 1104: Transmission element 1106: Device 1108: Communication Manager 1110: Device 1200: Device 1202: Receiving element 1204: Transmission element 1206: Device 1208: Communication Manager 1210: Generating element A1: Interface E2: Link O1: Interface O2: Interface

[0240] Domestic storage information (please note in order of storage institution, date, and number) none Overseas storage information (please note in the order of storage country, institution, date, and number) none

Claims

1. A user equipment (UE) for wireless communication, comprising: One memory; and one or more processors coupled to the memory, the one or more processors being configured to: receive a UE-specific CG-SDT configuration from a network entity of a non-terrestrial network (NTN) having parameters specific to the Configurable Authorized (CG) Small Data Transmission (SDT) (CG-SDT) in the NTN; receive system information from the network entity of the NTN associated with the verification of the parameters for the CG-SDT on the NTN; and use one or more of the parameters to send an SDT to the network entity of the NTN.

2. The UE as described in request item 1, wherein, in order to receive system information associated with CG-SDT authentication, the one or more processors are configured to periodically receive system information associated with CG-SDT authentication.

3. The UE as described in Request 1, wherein the parameters include a MAC application timing advance (TA) Kmac for delaying an application configured in a downlink by a Media Access Control (MAC) control element (MAC CE).

4. The UE as described in claim 3, wherein the parameters include a time offset Koffset for delaying a random access procedure initiated by downlink control channel communication of an entity and for delaying uplink transmissions scheduled by the CG, and wherein the time offset Koffset is specific to the CG-SDT on the NTN.

5. The UE as described in request item 4, wherein the time offset Koffset is shared by the cell service area.

6. The UE as described in request item 4, wherein the time offset Koffset is UE-specific.

7. The UE as described in request item 6, wherein the time offset Koffset is configured when the UE is in a radio resource control connection mode.

8. The UE as described in Request 6, wherein the time offset Koffset is a separate UE-specific Koffset configured for CG-SDT in a Radio Resource Control Release Message.

9. The UE as described in request item 6, wherein the time offset Koffset is reconfigured in a radio resource control inactive mode.

10. The UE as described in request item 4, wherein the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset, and wherein the one or more processors are configured to use the timing relationship verification information to verify the MAC TA Kmac and the time offset Koffset.

11. The UE as described in claim 3, wherein the MAC TA Kmac is received in a single message within a CG-SDT search space.

12. The UE as described in Request 1, wherein such parameters include ephemeris information and common timing advance (TA).

13. The UE as described in request item 12, wherein the system information includes TA verification information for verifying the ephemeris information or the shared TA, and wherein the one or more processors are configured to use the TA verification information to verify the ephemeris information or the shared TA.

14. The UE as described in request item 13, wherein, in order to verify the ephemeris information or the shared TA, the one or more processors are configured to use the TA to verify the information, including: The TA verification information is used to verify the ephemeris information used for CG-SDT or the epoch time or validity duration of the shared TA, based at least in part on one or more of the UE’s location or a timer.

15. The UE as described in Request 1, wherein the parameters include a parameter for enabling a Hybrid Automatic Repeat Request (CG-SDT) procedure on the NTN.

16. The UE as described in Request 1, wherein the parameters include a polarization parameter for CG-SDT on the NTN.

17. The UE as described in claim 1, wherein the one or more processors are configured to: receive an indication of a time offset specific to a cell service area or specific to the UE, and wherein the parameters include a cell service area stop time during which a serving cell service area is valid for a CG-SDT on the NTN, and after the end of the cell service area stop time minus the time offset, restrict the UE from transmitting a CG-SDT on the NTN.

18. The UE as described in Request 1, wherein the parameters include a cell service area parameter configured for the CG-SDT on the NTN or a satellite parameter configured for the CG-SDT on the NTN.

19. The UE as described in Request 1, wherein the parameters include a set of CG-SDT parameters associated with a configured list of cell service areas.

20. The UE as described in Request 1, wherein such parameters include a set of CG-SDT parameters associated with a configured satellite inventory.

21. The UE as described in Request 1, wherein the system information includes timing advance (TA) verification information specific to CG-SDT, and wherein the one or more processors are configured to use the TA verification information to verify a TA for CG-SDT on the NTN.

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

23. The UE as described in Request 1, wherein the system information includes link quality verification information for verifying the link quality of a CG-SDT on the NTN, and wherein the one or more processors are configured to use the link quality verification information to verify the link quality of the CG-SDT on the NTN.

24. The UE as described in claim 23, wherein, in order to verify the link quality of the CG-SDT on the NTN, the one or more processors are configured to: use a measurement threshold for the CG-SDT or a power level threshold for the CG-SDT on the NTN to verify the link quality of the CG-SDT on the NTN, wherein the measurement threshold for the CG-SDT has a measurement duration different from that of a measurement threshold for the CG-SDT on a terrestrial network, and the power level threshold for the CG-SDT on the NTN is different from that of the CG-SDT on the terrestrial network.

25. The UE as described in claim 1, wherein the system information includes cell service area or satellite verification information for verifying a cell service area or satellite for CG-SDT, and wherein the one or more processors are configured to use the cell service area or satellite verification information to verify the cell service area or satellite for CG-SDT.

26. The UE as described in claim 25, wherein, in order to verify the cell service area or satellite for CG-SDT, the one or more processors are configured to: use the cell service area or satellite verification information to verify a cell service area stop time during which a serving cell service area is valid for CG-SDT on the NTN.

27. The UE as described in claim 26, wherein if the UE receives a timing advance command or a timer is reconfigured via a dedicated radio resource control signal, the cell service area stop time is restarted.

28. The UE as described in Request 1, wherein the one or more processors are configured to: skip the verification of such parameters of the CG-SDT on the NTN, at least in part, based on the CG-SDT configuration.

29. The UE as described in Request 1, wherein the one or more processors are configured to: skip verification of the parameters of CG-SDT on the NTN, at least in part, based on the fact that a newly reselected cell service area belongs to the same satellite as a previous cell service area and has a shared standard with the previous cell service area.

30. The UE as described in Request 1, wherein the one or more processors are configured to: skip verification of such parameters of CG-SDT on the NTN, at least in part, based on a satellite type associated with a cell service area.

31. The UE as described in Request 1, wherein the one or more processors are configured to perform verification of the parameters of the CG-SDT on the NTN within one or more time windows.

32. The UE as described in request item 1, wherein the one or more processors are configured to apply a timing advance adjustment to a subsequent uplink transmission after the transmission of the SDT.

33. The UE as described in claim 1, wherein the one or more processors are configured to: receive a timing advance command (TAC); maintain a TAC-based closed-loop timing advance during subsequent uplink transmissions; and reset the closed-loop timing advance at the next transmission timing of the CG-SDT on the NTN.

34. A network entity in a non-terrestrial network (NTN) for wireless communication, comprising: One memory; and one or more processors coupled to the memory, the one or more processors being configured to: transmit a user equipment (UE) specific CG-SDT configuration having parameters specific to the Configurable Grant (CG) Small Data Transfer (SDT) (CG-SDT) in the NTN; transmit system information associated with verification of the parameters for the CG-SDT on the NTN; and receive an SDT based at least in part on one or more of the parameters.

35. The network entity as described in claim 34, wherein the parameters include a MAC application timing advance (TA) Kmac for delaying an application configured on a downlink by a media access control (MAC) control element (MAC CE).

36. The network entity as described in claim 35, wherein the parameters include a time offset Koffset for delaying a random access procedure initiated by downlink control channel communication of an entity and for delaying uplink transmissions scheduled by CG, and wherein the time offset Koffset is specific to CG-SDT on the NTN.

37. The network entity as described in claim 36, wherein the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset.

38. The network entity as described in claim 34, wherein the parameters include ephemeris information and a common timing advance (TA), and wherein the system information includes TA verification information for verifying a validity duration of the ephemeris information or the common TA.

39. The network entity as described in claim 34, wherein the system information includes one or more of the following: timing advance (TA) verification information specific to CG-SDT, link quality verification information for verifying the link quality of CG-SDT on the NTN, or cell service area or satellite verification information for verifying a cell service area or satellite for CG-SDT.

40. The network entity as described in claim 34, wherein the one or more processors are configured to receive a subsequent uplink transmission with a timing advance adjustment after the reception of the SDT.

41. The network entity as described in claim 34, wherein the one or more processors are configured to: send a timing advance command (TAC); maintain a TAC-based closed-loop timing advance during subsequent uplink transmissions; and reset the closed-loop timing advance at the next transmission opportunity of the CG-SDT on the NTN.

42. A method of wireless communication performed by a user equipment (UE), comprising the steps of: receiving from a network entity of a non-terrestrial network (NTN) a UE-specific CG-SDT configuration having parameters of a Configurable Authorized (CG) Small Data Transmission (SDT) (CG-SDT) specific to the NTN; receiving from the network entity of the NTN system information associated with the verification of the parameters for the CG-SDT on the NTN; and sending an SDT to the network entity of the NTN using one or more of the parameters.

43. The method as described in claim 42, wherein the parameters include a MAC application timing advance (TA) Kmac for delaying an application configured for a downlink by a media access control (MAC) control element (MAC CE).

44. The method as described in claim 43, wherein the parameters include a time offset Koffset for delaying a random access procedure initiated by downlink control channel communication of an entity and for delaying uplink transmissions scheduled by CG, and wherein the time offset Koffset is specific to CG-SDT on the NTN.

45. The method as described in claim 44, wherein the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset, and wherein the method includes: Use the timing relationship verification information to verify the MAC TA Kmac and the time offset Koffset.

46. ​​The method as described in claim 45, wherein the system information includes TA verification information for verifying ephemeris information or shared timing advance (TA), and wherein the method includes: Use the TA verification information to verify the ephemeris information or the shared TA.

47. The method as described in claim 42, wherein the system information includes timing advance (TA) verification information specific to CG-SDT, and wherein the method includes: Use the TA verification information to verify a TA used for CG-SDT on this NTN.

48. The method as described in claim 42, wherein the system information includes link quality verification information for verifying the link quality of a CG-SDT on the NTN, and wherein the method includes: Use the link quality verification information to verify the link quality of the CG-SDT on the NTN.

49. The method as described in claim 42, wherein the system information includes cell service area or satellite verification information for verifying a cell service area or satellite for CG-SDT, and wherein the method includes: Use the cell service area or satellite verification information to verify the cell service area or satellite used for CG-SDT.

50. The method as described in request item 42 further includes the step of: applying a timing advance adjustment to a subsequent uplink transmission after the transmission of the SDT.

51. A method of wireless communication performed by a network entity in a non-terrestrial network (NTN), comprising the steps of: transmitting a user equipment (UE)-specific CG-SDT configuration having parameters specific to a configured authorized (CG) small data transmission (SDT) (CG-SDT) in the NTN; transmitting system information associated with authentication 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.

52. The method as described in claim 51, wherein the parameters include a MAC application timing advance (TA) Kmac for delaying an application of a downlink configuration indicated by a Media Access Control (MAC) control element (MAC CE), wherein the parameters include a time offset Koffset for delaying a random access procedure initiated by an entity downlink control channel communication and delaying an uplink transmission scheduled by a CG, and wherein the time offset Koffset is specific to the CG-SDT on the NTN.

53. An apparatus for wireless communication, comprising: A component for receiving a user equipment (UE)-specific CG-SDT configuration having parameters specific to the Configurable Authorized (CG) Small Data Transmission (SDT) (CG-SDT) in a network entity of a non-terrestrial network (NTN); a component for receiving system information associated with the verification of the parameters used for the CG-SDT on the NTN from the network entity of the NTN; and a component for sending the SDT to the network entity of the NTN using one or more of the parameters.

54. The apparatus as claimed in claim 53, wherein the parameters include a MAC application timing advance (TA) Kmac for delaying an application of a downlink configuration indicated by a Media Access Control (MAC) control element (MAC CE), wherein the parameters include a time offset Koffset for delaying a random access procedure initiated by a physical downlink control channel communication and delaying an uplink transmission scheduled by a CG, and wherein the time offset Koffset is specific to the CG-SDT on the NTN.

55. The apparatus of claim 54, wherein the system information includes timing relationship verification information for verifying the MAC TA Kmac and the time offset Koffset, and wherein the apparatus comprises: The component used to verify the MAC TA Kmac and the time offset Koffset using the timing relationship verification information.

Images