Data transmission using storage and forwarding satellites

Abstract

Certain aspects of the present disclosure provide techniques for storing and forwarding data transmissions in a non-terrestrial network (NTN). A method for wireless communication by a user equipment (UE) includes obtaining information of one or more NTN entities configured to store UE data. The method includes selecting one of the one or more NTN entities based on the information. The method includes outputting uplink data to the NTN entity.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Patent Application No. 18 / 359,748, filed July 26, 2023, which is incorporated herein by reference. Background Technology Technical Field

[0004] Various aspects of this disclosure relate to wireless communication, and more specifically to techniques for transmitting data using stored and forwarded satellites.

[0005] Related technical descriptions

[0006] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with multiple users by sharing available wireless communication system resources.

[0007] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of ​​wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0008] One aspect provides a method for wireless communication by a user equipment (UE). The method includes receiving information from one or more non-terrestrial network (NTN) entities configured to store UE data. The method includes selecting one of the one or more NTN entities based on the information, and transmitting uplink data to the NTN entity.

[0009] On the other hand, a method for wireless communication by an NTN entity is provided. The method includes: outputting to a UE information of one or more NTN entities, including the NTN entity, configured to store UE data, the information indicating one or more of the following: the amount of UE data the NTN entity is configured to store or the duration for which the NTN entity is configured to store the UE data.

[0010] Other aspects provide: an apparatus capable of operating, being configured, or otherwise adapted to perform one or more of the foregoing methods and / or those methods described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those methods described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising: code for performing the foregoing methods and those methods described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those methods described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks.

[0011] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0012] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0013] Figure 1 An example wireless communication network is depicted.

[0014] Figure 2 An example decomposed base station architecture is described.

[0015] Figure 3 Various aspects of the example base station and example user equipment are described.

[0016] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0017] Figure 5A An example NTN is depicted.

[0018] Figure 5B An example NTN architecture is described.

[0019] Figure 6A An example storage and forwarding deployment is described.

[0020] Figure 6B Another example of storage and forwarding deployment is described.

[0021] Figure 7 The process flow for communication in the network between the UE, NTN entity and ground station is described.

[0022] Figure 8 A method for wireless communication by a UE is described.

[0023] Figure 9 A method for wireless communication by an NTN entity is described.

[0024] Figure 10 Various aspects of the example communication device are described.

[0025] Figure 11 Various aspects of the example communication device are described. Detailed Implementation

[0026] This disclosure provides apparatus, methods, processing systems, and computer-readable media for transmitting data using stored and forwarded satellites.

[0027] In store-and-forward operations, when the UE is within satellite coverage, it can send uplink data to the satellite in the NTN. The satellite can store the uplink data until it has connectivity with the ground station. When connectivity is established, the satellite forwards the UE data to the ground station, which can then provide the UE data to the intended recipient. The ground station can provide a downlink response to the satellite, and once the UE is within satellite coverage, the satellite forwards the downlink response to the UE.

[0028] In an NTN network, UEs may have discontinuous coverage because satellites orbit globally. Furthermore, coverage can be intermittent due to the loss of connectivity between satellites and ground stations. Satellites may have limited storage capacity during store-and-forward operations. Therefore, satellites may have storage quotas and / or storage durations. Storage quotas and / or durations may be associated with Quality of Service (QoS), priority, or both.

[0029] Various aspects of this disclosure provide signaling information to the UE for use in satellite / cell selection and reselection. In some aspects, this information includes storage quotas and / or data storage durations for serving satellites and / or neighboring satellites. Various aspects of this disclosure further provide techniques for logical channel prioritization of satellite-based signaling notification information for the UE. Various aspects of this disclosure further provide techniques for satellite / cell selection or reselection of satellite-based signaling notification information for the UE.

[0030] The techniques presented in this paper enable store-and-forward operations in NTN even under conditions of discontinuous coverage and intermittent connectivity.

[0031] An introduction to wireless communication networks

[0032] The techniques and methods described herein can be used in a variety of wireless communication networks. While aspects may be described herein using terms commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0033] Figure 1 An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0034] Generally, wireless communication network 100 includes various network entities (optionally, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). For example, various functions of the network and various devices associated with and interacting with the network can be considered network entities. Furthermore, wireless communication network 100 includes terrestrial aspects, such as terrestrial network entities (e.g., BS 102), and non-terrestrial aspects, such as satellite 140 and aircraft 145, which may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipment.

[0035] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0036] Figure 1Various example UE 104s are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, wireless communication devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0037] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., transmitting or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to BS 102 and / or downlink (DL) (also known as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0038] BS 102 may generally include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver function, transmit / receive point, and / or others. Each BS in BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0039] Although BS 102 is described as a single communication device in various aspects, it can be implemented in a variety of configurations. For example, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0040] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0041] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz to 7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz to 71,000MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further defined according to subranges (such as a first subrange FR2-1 including 24,250MHz to 52,600MHz and a second subrange FR2-2 including 52,600MHz to 71,000MHz). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0042] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0043] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Therefore, some base stations (e.g., Figure 1The beamforming 182 of the BS 180 (180) with the UE 104 can be used to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182''. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may or may not be the same. Similarly, the transmission and reception directions of UE 104 may or may not be the same.

[0044] The wireless communication network 100 also includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0045] Some UEs 104 may use device-to-device (D2D) communication links 158 to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0046] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0047] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP service 176, which may include, for example, the Internet, intranet, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming media service, and / or other IP services.

[0048] The BM-SC 170 provides functionality for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or can be used to schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS services to BS 102 belonging to a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0049] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196.

[0050] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0051] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides the UE with IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming services, and / or other IP services.

[0052] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0053] Figure 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some specific implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0054] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include 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 of the units, or an associated processor or controller providing instructions to the unit's communication interface, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally or alternatively, the units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers) configured to receive signals on wireless transmission media or transmit signals to one or more other units, or both.

[0055] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 210 may be implemented to communicate with DU 230 for network control and signaling notification as needed.

[0056] DU 230 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may host one or more of the following: a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional splits, such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0057] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, an RU240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration enables the implementation of the DU 230 and CU 210 in cloud-based RAN architectures such as vRAN architectures.

[0058] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating 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 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, SMO framework 205 can communicate directly with one or more RU 240s via the O1 interface. SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of SMO framework 205.

[0059] The non-RT RIC 215 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, that connects one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

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

[0061] Figure 3 Various aspects of examples BS 102 and UE 104 are described.

[0062] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively referred to as 334), transceivers 332a-332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various functions described herein related to wireless communication.

[0063] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively referred to as 352), transceivers 354a-354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieved from data source 362) and the wireless reception of data (e.g., provided to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various functions described herein related to wireless communication.

[0064] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. The control information may be for a Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical HARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Shared PDCCH (GC PDCCH), and / or others. In some examples, this data may be for a Physical Downlink Shared Channel (PDSCH).

[0065] The transmitter processor 320 can process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0066] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t can process its corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a-332t can be transmitted via antennas 334a-334t respectively.

[0067] To receive downlink transmissions, UE 104 includes antennas 352a-352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a-354r respectively. Each demodulator in transceivers 354a-354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0068] The MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a-354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes (e.g., demodulates, deinterleaves, and decodes) the detected symbols, provides the decoded data for UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0069] Regarding example uplink transmission, UE 104 also includes a transmit processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmit processor 364 may also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmit processor 364 may be pre-decoded by TX MIMO processor 366, where applicable, further processed by modulators in transceivers 354a-354r (e.g., for SC-FDM), and transmitted to BS 102.

[0070] At BS 102, uplink signals from UE 104 can be received by antennas 334a-334t, processed by demodulators in transceivers 332a-332t, detected by MIMO detector 336 where applicable, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 339 and the decoded control information to controller / processor 340.

[0071] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0072] Scheduler 344 can schedule UE to transmit data on the downlink and / or uplink.

[0073] In various respects, BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from a data source 312, a scheduler 344, one or more memories 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, transceivers 332a-332t, antennas 334a-334t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 334a-334t, transceivers 332a-332t, RX MIMO detectors 336, a controller / processor 340, a receive processor 338, a scheduler 344, one or more memories 342, and / or other aspects described herein.

[0074] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from a data source 362, one or more memories 382, ​​a transmitting processor 364, a controller / processor 380, a TX MIMO processor 366, transceivers 354a-354t, antennas 352a-352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 352a-352t, transceivers 354a-354t, RX MIMO detectors 356, a controller / processor 380, a receiving processor 358, one or more memories 382, ​​and / or other aspects described herein.

[0075] In some respects, the processor can be configured to perform various operations (such as those associated with the methods described herein) and to send (output) data to or receive data from another interface configured to send or receive data, respectively.

[0076] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0077] Specifically, Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0078] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) Figure 4B and Figure 4D The system bandwidth (as depicted in the text) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0079] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0080] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X is flexibly used between DL and UL. The UE can configure the time slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0081] In some respects, the number of time slots within a subframe is based on the time slot configuration and parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 6 allow 1, 2, 4, 8, 16, 32, and 64 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 time slots per subframe, respectively. Therefore, for time slot configuration 0 and parameter set μ, there are 14 symbols per time slot and 2µ time slots per subframe. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 6. Therefore, the parameter set... It has a subcarrier spacing of 15 kHz and a parameter set It has a subcarrier spacing of 960 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D It provides slot configuration 0 with 14 symbols per slot and parameter set with 4 slots per subframe. Example: The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0082] like Figure 4A , Figure 4B , Figure 4C and Figure 4DAs depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0083] like Figure 4A As illustrated in the example, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0084] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0085] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0086] The secondary synchronization signal (SSS) can be located within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing.

[0087] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Block (SIB)) not transmitted via the PBCH, and / or paging messages.

[0088] like Figure 4CAs illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0089] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0090] All aspects related to non-terrestrial networks

[0091] Satellite-based NTNs are crucial for providing connectivity to global coverage, including rural and offshore areas, and are fundamental to supporting important use cases. NTN generally refers to a network or network segment that uses satellite-borne RF resources. NTN signaling can be regenerated (with onboard NTN processing) or transparent (e.g., where the satellite transmits its received content back to Earth only with amplification and an offset from uplink to downlink frequencies).

[0092] Figure 5A An example of a wireless communication network 500a including NTN entity 140 is illustrated. In some examples, wireless communication network 500a may implement aspects of wireless communication network 100. For example, wireless communication network 500a may include a ground station such as BS 102, UE 104, and NTN entities such as satellite 140. In the case of a terrestrial network, BS 102 may serve a coverage area or cell 110a, and in the case of a non-terrestrial network, NTN entity 140 may serve a coverage area 110b. Some NTNs may employ airborne platforms (e.g., drones or balloons) and / or spaceborne platforms (e.g., satellites).

[0093] As part of wireless communication within the NTN, NTN entity 140 can communicate with BS 102 and UE 104. In the case of a terrestrial network, UE 104 can communicate with BS 102 via communication link 514, referred to as a feeder link. In the case of NTN wireless communication, NTN entity 140 can be the serving cell for UE 104 via communication link 516, referred to as a serving link. In some respects, NTN entity 140 can act as a repeater (or remote radio head) for BS 102 and UE 104. For example, BS 102 can communicate with NTN entity 140 via communication link 518, and NTN entity 140 can relay signaling between BS 102 and UE 104 via communication links 516 and 518. NTN entity 140 can communicate with a terrestrial gateway (e.g., a disc-shaped satellite dish) via a feeder link. BS 102 can be co-located with the gateway, deployed behind the gateway, and / or deployed on satellite 140.

[0094] NTN beams can cover an area of ​​100km to 1000km for LEO satellites and an area of ​​200km to 3500km for GEO satellites. For example... Figure 5B As illustrated, an NG-RAN 500b deployment may include a satellite 140 and an NTN gateway (GW) 505 that act as a cellular link between the UE 104 and the terrestrial network (TN) gNB 102 (and the 5G core network 190). NG-RAN 500b typically refers to a radio access network for 5G that provides both NR and LTE radio access. The link between the UE 104 and the satellite 140 is typically referred to as a serving link, while the link between the satellite and the GW is typically referred to as a feeder link.

[0095] In some respects, as satellite 140 moves in its orbit, it communicates with different UEs. As the satellite orbits, it communicates with different UEs via different beams. The uplink signal from the UE experiences a round-trip delay (RTD), which is typically the sum of the delay on the serving link and the delay on the feeder link. The maximum RTD is typically approximately 541.46 ms for GEO satellites, 25.77 ms for LEO satellites at an altitude of 600 km, and 41.77 ms for LEO satellites at an altitude of 1200 km. Compared to the speed of LEO satellites, the speed of the UE is generally negligible.

[0096] When satellite 140 moves and UE 104 is outside the coverage area 110b of satellite 140, it is referred to as discontinuous coverage. Furthermore, when satellite 140 may not have a feeder link connection to a ground station, it is referred to as intermittent coverage.

[0097] Various aspects related to data transmission using store-and-forward methods

[0098] Various aspects of this disclosure relate to data transmission using store-and-forward operations. By enabling an NTN entity (e.g., a satellite) to collect uplink data from a UE in one geographic location, store the UE data, and later forward the UE data to a ground station (e.g., a gateway or UE) in another geographic location, store-and-forward addresses discontinuous and intermittent coverage.

[0099] NTN standardization efforts focus on transparent payload architectures, where satellite platforms must connect to ground station gateways to provide satellite access services to devices. These transparent payload architectures require complex ground segment infrastructure in low Earth orbit (LEO) constellation deployments to achieve global coverage. Satellite network deployments targeting the delivery of latency-tolerant applications, such as NB-IoT, are a primary mMTC use case and benefit from architectures based on the use of regenerative payloads in satellites and support for store-and-forward operations, where satellite access remains operational even when satellites are not connected to ground stations. Specifically, such approaches would allow for extended satellite service coverage in areas where satellites cannot connect to ground stations (e.g., at sea or in very remote areas lacking ground station infrastructure), thereby improving ground segment affordability by enabling operation with fewer ground stations and allowing for more robust operation of satellites under intermittent feeder link operation.

[0100] Figure 6A Example storage and forwarding deployment 600a is described.

[0101] In the store-and-forward operation within the NTN network, Mobile Station Initiated (MO) traffic transmitted from UE 104 can be implemented in two steps. In the first step, during serving link availability, when UE 104 is within the coverage area of ​​one or more NTN entities (e.g., satellites 140a, 140b, and 140c), UE 104 transmits uplink data packets to the NTN (e.g., to satellite 140c as shown). Satellite 140c stores the uplink data packets. In the second step, during feeder link availability, satellite 140c connects to a ground station, such as gateway 505 or base station 102, and satellite 140c now forwards the data packets to the ground station. The ground station can then forward the packets directly to the destination receiver. Satellite 140c also receives response downlink data from the ground station to deliver back to UE 104 the next time serving link availability is available for both satellite 140c and UE 104.

[0102] Figure 6BAnother example of a store-and-forward deployment 600b is depicted. As shown, when satellite 140c is orbiting in a global orbit, satellite 140c collects uplink data from UE 104, stores the uplink data, and offloads the uplink to a ground station (gateway 505 or base station 102) and receives response downlink data.

[0103] Satellites may have limited storage capacity. Therefore, satellites may have a limited amount of UE data that can be stored, and a limited duration for which the satellite stores the data. Various aspects of this disclosure provide the UE with information about the amount of satellite data the UE can use to select cells / satellites. In some aspects, the storage capacity and / or duration are associated with data and / or UE priority or QoS objectives. In some aspects, the storage capacity or duration is associated with logical channels. Various aspects of this disclosure also provide techniques for the UE to perform satellite / cell selection and reselection, as well as logical channel priority ordering, based on information about the satellites. In some aspects, the UE further receives cell prohibition information applicable to legacy UEs that do not support store-and-forward operations, and cell prohibition information applicable to non-legacy UEs that support store-and-forward operations.

[0104] Example operations of entities in a communication network

[0105] Figure 7 A process flow 700 is described for communication within the network between NTN entity 706, ground station 702, and UE 704. In some aspects, ground station 702 may be related to... Figure 1 and Figure 3 BS 102 or related descriptions and depictions Figure 2 An example of a decomposed base station depicted and described. NTN Entity 706 may be about... Figure 1 And an example of satellite 140 depicted and described in Figure 6. Similarly, UE 704 could be about Figure 1 and Figure 3 An example of UE 104 is depicted and described. However, in other respects, UE 104 may be another type of wireless communication device, BS 102 may be another type of network entity or network node, and NTN entity 706 may be another type of NTN entity, such as those described herein.

[0106] As shown in the figure, at operation 708, UE 704 receives NTN information from one or more NTN entities. As shown in the figure, NTN information can be received from NTN entity 706. In some cases, NTN information can be received from a ground station.

[0107] In some respects, NTN information is provided to UE 704 via broadcast messages. For example, NTN information may be broadcast to UE 704 in a System Information Block (SIB) (such as in SIB1 or other SIBs carrying serving satellite information).

[0108] In some respects, NTN information is information of NTN entity 706. In some respects, NTN information is NTN information of one or more adjacent NTN entities. In some respects, NTN information is provided to UE 704 via UE-specific signaling. For example, NTN information may be provided to UE 704 via a dedicated RRC message or a dedicated non-access stratum (NAS) message.

[0109] In some aspects, NTN information can be UE-specific, satellite-specific, cell-specific, QoS-specific, uplink and downlink data-specific, and / or logical channel-specific. Therefore, different NTN information can be provided for different UEs, satellites, cells, QoS data, uplink and downlink data, and / or logical channels.

[0110] In some respects, NTN information is the data storage quota of NTN entity 706. The data storage quota is the maximum amount of UE data that NTN entity 706 can store.

[0111] In some aspects, NTN information is the storage duration quota of NTN entity 706. The storage duration quota can be the maximum duration for which NTN entity 706 stores UE data before discarding it. For example, the storage duration quota can be the duration for which NTN entity 706 waits to receive a response downlink data message for the data from the ground station before discarding it. The storage duration quota can also correspond to the duration for which UE 704 waits for response downlink data before retrying UL data transmission. In some aspects, the storage duration quota is the duration for which NTN entity 706 stores the response downlink data before discarding it (which may be the same as or separate from the storage duration quota for uplink UE data).

[0112] At operation 710, UE 704 selects the NTN entity to access and transmits uplink data to that NTN entity. In some respects, this selection is based on the NTN information received at operation 708.

[0113] In some aspects, UE 704 checks the data storage quota information of the NTN entity before initiating random access. If the uplink data of UE 704 is not greater than the storage quota of NTN entity 706, UE 704 initiates random access with NTN entity 706. If the uplink data of UE 704 exceeds the storage quota of NTN entity 706, UE 704 may leave the cell and attempt to find another suitable cell. In some aspects, UE 704 may use the cell only for the registration update process and request the large data storage quota of NTN entity 706. In some aspects, UE 704 may notify its upper layer of the data storage quota of NTN entity 706, thereby limiting uplink data to meet the data storage quota. If NTN entity 706 increases its data storage quota upon request or UE 704 limits uplink data, UE 704 may continue to initiate random access.

[0114] In some respects, UE 704 checks the data storage duration information of the NTN entity before initiating random access. If UE 704's uplink data is not latency-sensitive and the data storage duration of NTN entity 706 is sufficient, UE 704 initiates random access with NTN entity 706. If UE 704's uplink data is latency-sensitive and the data storage duration of NTN entity 706 is insufficient, UE 704 may leave the cell and attempt to find another suitable cell. In some respects, UE 704 may use the cell only for the registration update process and request the large data storage duration of NTN entity 706.

[0115] In some aspects, logical channel prioritization is based on NTN information. In some aspects, each logical channel is configured using store-and-forward data storage quotas and / or data storage duration. In some aspects, each logical channel is configured based on whether the logical channel is subject to store-and-forward data storage quotas and / or data storage duration. Upon receiving an uplink grant, UE 704 may select a logical channel configured using store-and-forward data storage quotas and / or data storage durations that satisfy NTN entity 706.

[0116] In some respects, UE 704 receives auxiliary information from neighboring satellites. The auxiliary information may include the frequency of the neighboring satellite, the cell ID of the neighboring satellite, the data storage quota of the neighboring satellite, the data storage duration of the neighboring satellite, the availability of the next feeder link of the neighboring satellite, and / or the next re-access time of the store-and-forward service area of ​​the neighboring satellite (e.g., based on a fixed reference position on the Earth's surface).

[0117] In some respects, UE 704 uses auxiliary information from neighboring cells to perform cell reselection. For example, UE 704 can reselect to an NTN entity that has the shortest feeder link availability time, the maximum data storage duration, the maximum data storage quota, etc.

[0118] In some cases, UE 704 receives the prohibition message. In some cases, the prohibition message is received together with the NTN message. In some cases, the prohibition message is received separately from the NTN message.

[0119] The prohibition information can indicate which satellites or cells are prohibited for UE 704 to access. In some aspects, the prohibition information includes legacy prohibition information that can be read by both legacy UEs that do not support store-and-forward operations and non-legacy UEs that support store-and-forward operations. Legacy UEs may follow the legacy prohibition information. In some aspects, the prohibition information also includes store-and-forward prohibition information (e.g., new additional prohibition bits). UEs that support store-and-forward operations further check and follow the store-and-forward prohibition information. Legacy UEs do not check or follow the store-and-forward prohibition information. UEs that support store-and-forward operations may use the store-and-forward prohibition information to overwrite the legacy prohibition information. When performing satellite / cell selection reselection, the UE may follow the prohibition information.

[0120] At operation 712, UE 704 sends uplink data to the selected NTN entity 706 (e.g., after performing initial access with the NTN entity).

[0121] At operation 714, NTN entity 706 stores UE data (e.g., if the amount of uplink data does not exceed the data storage quota of NTN entity 706).

[0122] At operation 718, ground station 702 sends response downlink data to NTN entity 706 (e.g., if the duration has not yet exceeded the data storage quota of NTN entity 706).

[0123] At operation 720, the response downlink data is forwarded to UE 704.

[0124] In some respects, UE 704 further identifies the NTN entities from which it monitors downlink response data. Although Figure 7 The example illustrates UE 704 receiving downlink response data from NTN entity 706. However, in some respects, UE 704 may receive downlink response data from an NTN entity different from NTN entity 706 to which UE 704 has uploaded uplink data.

[0125] In some aspects, UE 704 transmits to NTN entity 706 an indication of whether UE 704 will track the same NTN entity 706 and monitor downlink response data from NTN entity 706, or will track and monitor a different NTN entity to obtain response downlink data. In some aspects, UE 704 may instruct UE 704 to monitor and receive response downlink data from any NTN entity that can deliver response downlink data earliest. In response, UE 704 may be configured to monitor response downlink data using the next satellite access time or wake-up time. In some aspects, the network determines the satellite access or wake-up time of UE 704 based on the data's QoS, the UE's priority, the logical channel associated with the data, the satellite's response data storage quota, and / or the satellite's response storage duration quota.

[0126] In some respects, the network determines whether UE 704 will track and monitor the same NTN entity or a different NTN to obtain downlink data in response, and instructs UE 704 accordingly. In other respects, the network makes this decision based on the UE's subscription, the UE's priority, and / or network capabilities (such as the availability of multiple satellites and / or ground stations).

[0127] Example operations performed by user equipment

[0128] Figure 8 It shows the user equipment (UE) (such as Figure 1 and Figure 3 Example of a method 800 for wireless communication of UE 104.

[0129] Method 800 begins at step 805 by obtaining information about one or more NTN entities configured to store UE data. In some cases, this step involves operations such as those described in reference [reference needed]. Figure 10 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0130] In some respects, the information of each NTN entity in one or more NTN entities includes one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store UE data.

[0131] In some respects, the NTN entity is configured to store either the amount of UE data or the duration of UE data, which is associated with the QoS of the UE data or logical channel.

[0132] In some respects, one or more of the amount of UE data that an NTN entity is configured to store or the duration for which an NTN entity is configured to store UE data are associated with at least one of the following: the priority of the UE data or the priority of the UE.

[0133] In some respects, the amount of UE data that an NTN entity is configured to store or the duration for which an NTN entity is configured to store UE data is UE-specific.

[0134] In some respects, one or more of the amount of UE data that an NTN entity is configured to store or the duration for which an NTN entity is configured to store UE data are NTN entity-specific.

[0135] In some respects, one or more of the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store UE data are cell-specific.

[0136] In some aspects, one or more of the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store UE data include: a first amount of downlink UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store downlink UE data, and a second amount of uplink UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store uplink UE data.

[0137] In some respects, obtaining information about one or more NTN entities includes obtaining a broadcast system information block (SIB) indicating one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store UE data.

[0138] In some respects, obtaining information about one or more NTN entities includes obtaining dedicated signaling indicating one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store UE data.

[0139] In some respects, obtaining information about one or more NTN entities includes obtaining the amount of UE data that the NTN entity is configured to store.

[0140] Method 800 then proceeds to step 810, where one NTN entity from one or more NTN entities is selected based on information. In some cases, the operation of this step involves, as described in the reference... Figure 10 The circuitry and / or code described for selection, or that can be executed by the circuitry and / or the code.

[0141] In some aspects, method 800 further includes: determining, before initiating random access with one or more NTN entities, whether the amount of uplink data at the UE is greater than the amount of UE data that the NTN entities are configured to store. In some cases, this step involves operations as described in reference [reference needed]. Figure 10 The circuit and / or code described for determination, or that can be executed by the circuit and / or the code.

[0142] In some aspects, method 800 further includes selecting a different NTN entity when the amount of uplink data at the UE is greater than the amount of UE data that the NTN entity is configured to store. In some cases, the operation of this step involves, as described in the reference... Figure 10 The circuitry and / or code described for selection, or that can be executed by the circuitry and / or the code.

[0143] In some aspects, method 800 further includes requesting a larger amount of uplink data from the NTN entity when the amount of uplink data at the UE is greater than the amount of UE data that the NTN entity is configured to store. In some cases, this step involves operations as described in reference [reference missing]. Figure 10 The circuitry and / or code described for the request, or that can be executed by the circuitry and / or the code.

[0144] In some aspects, method 800 further includes limiting the amount of uplink data transmitted to the NTN entity when the amount of uplink data at the UE is greater than the amount of UE data configured to be stored by the NTN entity. In some cases, the operation of this step involves, as described in reference... Figure 10 The circuitry and / or code described for the restriction, or that can be executed by the circuitry and / or the code.

[0145] In some aspects, method 800 further includes initiating random access with the NTN entity when the amount of uplink data at the UE is equal to or less than the amount of UE data configured to be stored by the NTN entity. In some cases, the operation of this step involves, as described in reference [reference] Figure 10 The circuitry described for initiating the process and / or the code for initiating the process, or the circuitry and / or the code that can be executed by the process.

[0146] Method 800 then proceeds to step 815, where uplink data is output to the NTN entity. In some cases, this step involves operations as described in the reference. Figure 10 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0147] In some respects, obtaining information about one or more NTN entities includes obtaining the duration during which the NTN entity was configured to store UE data.

[0148] In some aspects, method 800 also includes outputting uplink data to one or more NTN entities. In some cases, this step involves operations such as those described in the references. Figure 10 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0149] In some aspects, method 800 also includes: monitoring responses to uplink data during the period in which the NTN entity is configured to store UE data. In some cases, the operation of this step involves, as referenced... Figure 10 The circuitry and / or code described for monitoring, or that can be executed by the circuitry and / or the code.

[0150] In some aspects, method 800 also includes: retransmitting uplink data when no response is received during the period in which the NTN entity is configured to store UE data. In some cases, the operation of this step involves, as described in reference... Figure 10 The circuitry and / or code for retransmission described, or that can be executed by the circuitry and / or the code.

[0151] In some aspects, method 800 further includes: selecting an NTN entity to initiate random access with based on the duration during which the NTN entity has been configured to store UE data. In some cases, this step involves operations as described in reference [reference needed]. Figure 10 The circuitry and / or code described for selection, or that can be executed by the circuitry and / or the code.

[0152] In some respects, the NTN entity to which to initiate random access includes: when the UE has uplink data with a delay target, selecting an NTN entity with a shorter data storage duration.

[0153] In some respects, the NTN entity to which to initiate random access includes: when the UE has latency-sensitive uplink data, selecting an NTN entity with a longer data storage history.

[0154] In some respects, one or more of the amounts of UE data that an NTN entity is configured to store or the duration for which an NTN entity is configured to store UE data are logically channel specific.

[0155] In some aspects, method 800 further includes: obtaining an indication of whether one or more of the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store UE data applies to the logical channel for each of a plurality of logical channels. In some cases, the operation of this step involves, as referenced... Figure 10 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0156] In some aspects, method 800 further includes: selecting a logical channel for outputting uplink data to an NTN entity based on whether the logical channel among a plurality of logical channels satisfies the amount of UE data that one or more NTN entities are configured to store or the duration for which the NTN entity is configured to store UE data. In some cases, the operation of this step involves, as referenced... Figure 10 The circuitry and / or code described for selection, or that can be executed by the circuitry and / or the code.

[0157] In some aspects, method 800 further includes: indicating whether one or more of the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store UE data applies to the logical channel for each of a plurality of logical channels. In some cases, the operation of this step involves, as referenced... Figure 10 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0158] In some aspects, method 800 further includes: obtaining auxiliary information from the serving NTN entity indicating information about one or more neighboring NTN entities, wherein the information includes the frequency of the one or more neighboring NTN entities, cell identifier (ID), the amount of UE data configured to be stored by the NTN entity, the duration for which the NTN entity is configured to store UE data, the next feeder link availability time, the time of the next access to the store and forward service area, or a combination thereof. In some cases, the operation of this step involves, as referenced... Figure 10 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0159] In some aspects, method 800 also includes: reselecting one NTN entity from one or more adjacent NTN entities based on the information. In some cases, this step involves operations such as those described in the reference. Figure 10 The circuitry and / or code described for reselection, or that can be executed by the circuitry and / or the code.

[0160] In some aspects, method 800 further includes: outputting uplink data to one of one or more NTN entities. In some cases, this step involves operations as described in the reference. Figure 10 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0161] In some aspects, method 800 also includes: outputting an indication of whether the UE expects a response to uplink data from an NTN entity or another NTN entity. In some cases, the operation of this step involves, as referenced... Figure 10 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0162] In some aspects, method 800 also includes obtaining an indication of the time of the monitoring response to uplink data. In some cases, this step involves operations such as those described in reference... Figure 10 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0163] In some aspects, method 800 also includes: obtaining an indication of the NTN entity whose response to uplink data is to be monitored. In some cases, this step involves operations such as those described in reference [reference needed]. Figure 10 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0164] In some aspects, method 800 further includes: obtaining a first cell prohibition indication that one or more NTN entities are prohibited. In some cases, the operation of this step involves, as referenced... Figure 10 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0165] In some aspects, method 800 further includes: obtaining a second cell prohibition indication that one or more NTN entities are prohibited. In some cases, the operation of this step involves, as referenced... Figure 10 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0166] In some aspects, method 800 further includes: when the UE does not support store-and-forward operations, only following a first cell prohibition instruction; and when the UE supports store-and-forward operations, only following a second cell prohibition instruction. In some cases, the operation of this step involves, as referenced... Figure 10 The circuitry described for compliance and / or the code for compliance, or the circuitry and / or the code that can be executed.

[0167] In some respects, one or more NTN entities include satellites.

[0168] In one aspect, method 800 or any aspect thereof may be made by means of a device (such as...) Figure 10 The communication device 1000 performs the operation, and the device includes various components that can be operated, configured, or adapted to perform the method 800. The communication device 1000 is described in more detail below.

[0169] It should be noted that Figure 8 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0170] Example operations performed by network entities

[0171] Figure 9 An example of a method 900 for wireless communication by a network entity such as an NTN entity (e.g., satellite 140) is shown. In some aspects, the operation of method 900 can be controlled by a ground station (e.g., Figure 1 and Figure 3 BS 102 or as about Figure 2 The decomposed base station under discussion is implemented.

[0172] Method 900 begins at step 905 by outputting information to the User Equipment (UE) of one or more NTN entities, including a Non-Terrestrial Network (NTN) entity, configured to store UE data. This information indicates one or more of the following: the amount of UE data the NTN entity is configured to store, or the duration for which the NTN entity is configured to store UE data. In some cases, the operation of this step involves, as referenced... Figure 11 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0173] In some respects, one or more of the amounts of UE data stored by an NTN entity or the duration for which an NTN entity is configured to store UE data are associated with the Quality of Service (QoS) of the UE data or logical channels.

[0174] In some respects, one or more of the amount of UE data that an NTN entity is configured to store or the duration for which an NTN entity is configured to store UE data are associated with at least one of the following: the priority of the UE data or the priority of the UE.

[0175] In some respects, the amount of UE data that an NTN entity is configured to store or the duration for which an NTN entity is configured to store UE data is UE-specific.

[0176] In some respects, one or more of the amount of UE data that an NTN entity is configured to store or the duration for which an NTN entity is configured to store UE data are NTN entity-specific.

[0177] In some respects, one or more of the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store UE data are cell-specific.

[0178] In some aspects, one or more of the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store UE data include: a first amount of downlink UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store downlink UE data, and a second amount of uplink UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store uplink UE data.

[0179] In some respects, outputting information about one or more NTN entities includes outputting a Broadcast System Information Block (SIB) indicating one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store UE data.

[0180] In some respects, outputting information about one or more NTN entities includes outputting dedicated signaling indicating one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store UE data.

[0181] In some respects, outputting information about one or more NTN entities includes: outputting the amount of UE data that the NTN entity is configured to store.

[0182] In some aspects, method 900 further includes: obtaining a larger quantity of UE data for at least one of one or more NTN entities configured to store UE data. In some cases, the operation of this step involves, as referenced... Figure 11 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0183] In some aspects, method 900 also includes configuring the NTN entity to store a larger amount of UE data in response to the request. In some cases, the operation of this step involves, as referenced... Figure 11 The circuitry and / or code described for configuration, or that can be executed by the circuitry and / or the code.

[0184] In some respects, the information output for one or more NTN entities includes: the duration for which the output NTN entity is configured to store UE data.

[0185] In some respects, one or more of the amounts of UE data that an NTN entity is configured to store or the duration for which an NTN entity is configured to store UE data are logically channel specific.

[0186] In some aspects, method 900 further includes: outputting auxiliary information from the serving NTN entity indicating information about one or more neighboring NTN entities, wherein the information includes the frequency of the one or more neighboring NTN entities, cell identifier (ID), the amount of UE data configured to be stored by the NTN entity, the duration for which the NTN entity is configured to store UE data, the next feeder link availability time, the time of the next access to the store and forward service area, or a combination thereof. In some cases, the operation of this step involves, as referenced... Figure 11 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0187] In some aspects, method 900 further includes: obtaining an indication of the NTN from which the UE expects a response to uplink data. In some cases, the operation of this step involves, as referenced... Figure 11 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0188] In some aspects, method 900 also includes: outputting an indication of the time for the UE to monitor the response to uplink data. In some cases, this step involves operations such as those described in reference... Figure 11 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0189] In some aspects, method 900 also includes: outputting an indication of an NTN entity for the UE to monitor responses to uplink data. In some cases, the operation of this step involves, as referenced... Figure 11 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0190] In some aspects, method 900 further includes: outputting a first cell prohibition indication indicating that one or more NTN entities are prohibited for use by a UE that does not support store-and-forward operations. In some cases, the operation of this step involves, as referenced... Figure 11 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0191] In some aspects, method 900 further includes: outputting a second cell prohibition indication indicating whether one or more NTN entities are prohibited from being used by a UE to support store-and-forward operations. In some cases, the operation of this step involves, as referenced... Figure 11 The circuitry and / or code described for the output, or the circuitry and / or code that can be executed by the output.

[0192] In some respects, one or more NTN entities include satellites.

[0193] In some aspects, method 900 also includes receiving uplink data from the UE to another UE. In some cases, this step involves operations as described in reference [reference needed]. Figure 11 The circuitry and / or code described for receiving, or that can be executed by the circuitry and / or the code.

[0194] In some aspects, method 900 also includes providing uplink data to a ground station associated with another UE. In some cases, this step involves operations such as those described in reference [reference needed]. Figure 11 The circuitry described is used to provide the circuitry and / or the code used to provide the circuitry, or the circuitry and / or the code that can be executed.

[0195] In some respects, the network entity is a satellite.

[0196] In one aspect, method 900 or any aspect thereof may be made by means of a device (such as...) Figure 11 The communication device 1100 performs the operation, and the device includes various components that can operate, be configured, or be adapted to perform the method 900. The communication device 1100 is described in more detail below.

[0197] It should be noted that Figure 9 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0198] Example communication device

[0199] Figure 10 Various aspects of the example communication device 1000 are described. In some aspects, the communication device 1000 is user equipment, such as those mentioned above. Figure 1 and Figure 3 The UE 104 described.

[0200] Communication device 1000 includes a processing system 1002 coupled to a transceiver 1054 (e.g., a transmitter and / or receiver). Transceiver 1054 is configured to transmit and receive signals for communication device 1000 via antenna 1056, such as various signals as described herein. Processing system 1002 may be configured to perform processing functions of communication device 1000, including processing signals received by communication device 1000 and / or to be transmitted by the communication device.

[0201] Processing system 1002 includes one or more processors 1004. In various aspects, the one or more processors 1004 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as per [reference to...]. Figure 3 As described. One or more processors 1004 are coupled to a computer-readable medium / memory 1028 via a bus 1052. In some aspects, the computer-readable medium / memory 1028 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 1004, cause one or more processors 1004 to perform actions related to... Figure 8 The described method 800 or any aspect thereof. It should be noted that references to processors performing the functions of communication device 1000 may include one or more processors 1004 performing those functions of communication device 1000.

[0202] In the depicted example, computer-readable medium / memory 1028 stores codes (e.g., executable instructions), such as code 1030 for obtaining, code 1032 for selecting, code 1034 for outputting, code 1036 for determining, code 1038 for requesting, code 1040 for restricting, code 1042 for initiating, code 1044 for monitoring, code 1046 for retransmission, code 1048 for reselection, and code 1050 for compliance. Processing the code 1030 for obtaining, code 1032 for selecting, code 1034 for outputting, code 1036 for determining, code 1038 for requesting, code 1040 for restricting, code 1042 for initiating, code 1044 for monitoring, code 1046 for retransmission, code 1048 for reselection, and code 1050 enables the communication device 1000 to perform operations related to... Figure 8 The method described 800 or any aspect thereof.

[0203] One or more processors 1004 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1028, including circuitry such as: circuitry 1006 for acquisition, circuitry 1008 for selection, circuitry 1010 for output, circuitry 1012 for determination, circuitry 1014 for request, circuitry 1016 for restriction, circuitry 1018 for initiation, circuitry 1020 for monitoring, circuitry 1022 for retransmission, circuitry 1024 for reselection, and circuitry 1026 for compliance. By utilizing the circuits 1006 for acquisition, 1008 for selection, 1010 for output, 1012 for determination, 1014 for request, 1016 for restriction, 1018 for initiation, 1020 for monitoring, 1022 for retransmission, 1024 for reselection, and 1026 for compliance, the communication device 1000 can perform actions related to... Figure 8 The method described 800 or any aspect thereof.

[0204] The various components of the communication device 1000 can provide for performing tasks related to... Figure 8 The components of the described method 800 or any aspect thereof. For example, components for sending, transmitting, or outputting for transmission may include... Figure 3 The transceiver 354 and / or antenna 352 of the illustrated UE104 and / or Figure 10 The communication device 1000 includes a transceiver 1054 and an antenna 1056. Components for receiving or acquiring data may include... Figure 3 The transceiver 354 and / or antenna 352 of the UE 104 are illustrated. Figure 10 The transceiver 1054 and antenna 1056 of the communication device 1000.

[0205] Figure 11 Various aspects of the example communication device 1100 are described. In some aspects, the communication device 1100 is a network entity, such as... Figure 1 and Figure 3 BS 102 or as about Figure 2 The decomposed base station under discussion.

[0206] Communication device 1100 includes a processing system 1105 coupled to a transceiver 1175 (e.g., a transmitter and / or receiver) and / or a network interface 1185. Transceiver 1175 is configured to transmit and receive signals for communication device 1100 via antenna 1180, such as various signals as described herein. Network interface 1185 is configured to transmit and receive signals for communication device 1100 via a communication link (such as those described herein). Figure 2The described backhaul link, midhaul link, and / or fronthaul link receive and transmit signals for communication device 1100. Processing system 1105 can be configured to perform processing functions of communication device 1100, including processing signals received by communication device 1100 and / or to be transmitted by the communication device.

[0207] Processing system 1105 includes one or more processors 1110. In various aspects, the one or more processors 1110 may represent one or more of a receive processor 338, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340, as per [reference to...]. Figure 3 As described. One or more processors 1110 are coupled to a computer-readable medium / memory 1140 via a bus 1170. In some aspects, the computer-readable medium / memory 1140 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1110, cause the one or more processors 1110 to perform actions related to... Figure 9 The method 900 described herein or any aspect thereof. It should be noted that references to the processor performing the function of the communication device 1100 may include one or more processors 1110 of the communication device 1100 performing that function.

[0208] In the depicted example, computer-readable medium / memory 1140 stores code (e.g., executable instructions), such as code 1145 for output, code 1150 for acquisition, code 1155 for configuration, code 1160 for receiving, and code 1165 for providing. Processing the code 1145 for output, the code 1150 for acquisition, the code 1155 for configuration, the code 1160 for receiving, and the code 1165 for providing enables the communication device 1100 to perform actions related to... Figure 9 The method described 900 or any aspect thereof.

[0209] One or more processors 1110 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1140, including circuitry such as: circuitry 1115 for output, circuitry 1120 for acquisition, circuitry 1125 for configuration, circuitry 1130 for receiving, and circuitry 1135 for providing. Processing using the circuitry 1115 for output, the circuitry 1120 for acquisition, the circuitry 1125 for configuration, the circuitry 1130 for receiving, and the circuitry 1135 for providing enables the communication device 1100 to perform operations related to... Figure 9 The method described 900 or any aspect thereof.

[0210] The various components of the communication device 1100 can provide for performing tasks related to... Figure 9 The components of the described method 900 or any aspect thereof. Components for transmitting, conveying, or outputting for transmission may include... Figure 3 The transceiver 332 and / or antenna 334 of the illustrated BS 102 and / or Figure 11 The communication device 1100 includes a transceiver 1175 and an antenna 1180. Components for receiving or acquiring data may include... Figure 3 The transceiver 332 and / or antenna 334 of the BS 102 are illustrated. Figure 11 The transceiver 1175 and antenna 1180 of the communication device 1100.

[0211] Example

[0212] Specific implementation examples are described in the following numbered clauses: Clause 1: A method for wireless communication by a user equipment (UE), the method comprising: obtaining information on one or more non-terrestrial network (NTN) entities configured to store UE data; selecting one of the one or more NTN entities based on the information; and outputting uplink data to the NTN entity.

[0213] Clause 2: According to the method described in Clause 1, the information of each of the one or more NTN entities includes one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data.

[0214] Clause 3: According to the method described in Clause 2, one or more of the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data are associated with the Quality of Service (QoS) of the UE data or logical channel.

[0215] Clause 4: In any combination of Clauses 2 to 3, the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data is associated with at least one of the following: the priority of the UE data or the priority of the UE.

[0216] Clause 5: The method according to any combination of Clauses 2 to 4, wherein one or more of the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data is UE-specific.

[0217] Clause 6: The method described in any combination of Clauses 2 to 5, wherein one or more of the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data is NTN entity specific.

[0218] Clause 7: The method described in any combination of Clauses 2 to 6, wherein one or more of the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data is cell-specific.

[0219] Clause 8: The method according to any combination of Clauses 2 to 7, wherein the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data comprises: a first amount of downlink UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the downlink UE data, and a second amount of uplink UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the uplink UE data.

[0220] Clause 9: The method according to any combination of Clauses 2 to 8, wherein obtaining the information of the one or more NTN entities includes obtaining a Broadcast System Information Block (SIB) indicating one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data.

[0221] Clause 10: The method according to any combination of Clauses 2 to 9, wherein obtaining the information of the one or more NTN entities includes obtaining dedicated signaling indicating one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data.

[0222] Clause 11: The method according to any combination of Clauses 2 to 10, wherein obtaining the information of the one or more NTN entities includes: obtaining the amount of UE data that the NTN entity is configured to store.

[0223] Clause 12: The method according to Clause 11 further includes: determining, before initiating random access with one or more NTN entities, whether the amount of uplink data at the UE is greater than the amount of UE data that the NTN entity is configured to store.

[0224] Clause 13: The method according to Clause 12 further includes: selecting a different NTN entity when the amount of uplink data at the UE is greater than the amount of UE data that the NTN entity is configured to store.

[0225] Clause 14: The method according to any combination of Clauses 12 to 13, the method further comprising: requesting a larger amount of uplink data of the NTN entity when the amount of uplink data at the UE is greater than the amount of UE data that the NTN entity is configured to store.

[0226] Clause 15: The method according to any combination of Clauses 12 to 14, the method further comprising: limiting the amount of uplink data transmitted to the NTN entity when the amount of uplink data at the UE is greater than the amount of UE data that the NTN entity is configured to store.

[0227] Clause 16: The method according to any combination of Clauses 12 to 15, the method further comprising: initiating random access with the NTN entity when the amount of uplink data at the UE is equal to or less than the amount of UE data that the NTN entity is configured to store.

[0228] Clause 17: The method according to any combination of Clauses 2 to 16, wherein obtaining the information of the one or more NTN entities includes: obtaining the duration during which the NTN entity is configured to store the UE data.

[0229] Clause 18: The method according to Clause 17 further includes: outputting uplink data to an NTN entity in one or more NTN entities; monitoring a response to the uplink data during the duration during which the NTN entity is configured to store the UE data; and retransmitting the uplink data if no response is received during the duration during which the NTN entity is configured to store the UE data.

[0230] Clause 19: The method according to any combination of Clauses 17 to 18, the method further comprising: selecting an NTN entity to initiate random access with based on the duration during which the NTN entity is configured to store the UE data.

[0231] Clause 20: The method according to Clause 19, wherein selecting the NTN entity to initiate random access with includes: when the UE has uplink data with a delay target, selecting an NTN entity with a shorter data storage duration.

[0232] Clause 21: The method according to any combination of Clauses 19 to 20, wherein selecting the NTN entity to initiate random access with it includes: when the UE has latency-sensitive uplink data, selecting an NTN entity with a longer data storage duration.

[0233] Clause 22: The method according to any combination of Clauses 2 to 21, wherein one or more of the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data is logical channel specific.

[0234] Clause 23: The method according to Clause 22 further includes: obtaining an indication for each of a plurality of logical channels whether one or more of the amount of UE data that the NTN entity is configured to store or the duration during which the NTN entity is configured to store the UE data applies to the logical channel.

[0235] Clause 24: The method according to any combination of Clauses 22 to 23, the method further comprising: selecting the logical channel for outputting uplink data to the NTN entity based on whether the logical channel among a plurality of logical channels satisfies the amount of UE data that the NTN entity of the one or more NTN entities is configured to store or the duration that the NTN entity is configured to store the UE data.

[0236] Clause 25: The method according to any combination of Clauses 1 to 24, further comprising: obtaining auxiliary information from the serving NTN entity indicating information about one or more neighboring NTN entities, wherein the information includes the frequency of the one or more neighboring NTN entities, cell identifier (ID), the amount of UE data that the NTN entity is configured to store, the duration for which the NTN entity is configured to store the UE data, the next feeder link availability time, the time of the next access to the store and forward service area, or a combination thereof.

[0237] Clause 26: The method according to Clause 25 further includes: reselecting one of the one or more adjacent NTN entities based on the information.

[0238] Clause 27: The method according to any combination of Clauses 1 to 26, the method further comprising: outputting uplink data to one of the one or more NTN entities; and outputting an indication of whether the UE expects a response to the uplink data from the NTN entity or another NTN entity.

[0239] Clause 28: The method according to Clause 27 further includes: obtaining an indication of the time of the monitoring response to the uplink data.

[0240] Clause 29: The method according to any combination of Clauses 1 to 28, the method further comprising: obtaining an indication of an NTN entity to monitor responses to the uplink data.

[0241] Clause 30: The method according to any one of Clauses 1 to 29, further comprising: obtaining a first cell prohibition indication indicating that the one or more NTN entities are prohibited; obtaining a second cell prohibition indication indicating whether one or more of the one or more NTN entities are prohibited; and when the UE does not support store and forward operation, following only the first cell prohibition indication, and when the UE supports store and forward operation, following only the second cell prohibition indication.

[0242] Clause 31: The method described under any combination of Clauses 1 to 30, wherein the one or more NTN entities include satellites.

[0243] Clause 32: A method for wireless communication by a network entity, the method comprising: outputting to a user equipment (UE) information of one or more NTN entities, including a non-terrestrial network (NTN) entity, configured to store UE data, the information indicating one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration for which the NTN entity is configured to store the UE data.

[0244] Clause 33: The method according to Clause 32, wherein one or more of the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data are associated with the Quality of Service (QoS) of the UE data or logical channel.

[0245] Clause 34: In any combination of Clauses 32 to 33, the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data is associated with at least one of the following: the priority of the UE data or the priority of the UE.

[0246] Clause 35: The method described in any combination of Clauses 32 to 34, wherein one or more of the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data is UE-specific.

[0247] Clause 36: The method described in any combination of Clauses 32 to 35, wherein one or more of the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data is NTN entity specific.

[0248] Clause 37: The method described in any combination of Clauses 32 to 36, wherein one or more of the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data is cell-specific.

[0249] Clause 38: The method according to any combination of Clauses 32 to 37, wherein the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data comprises: a first amount of downlink UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the downlink UE data, and a second amount of uplink UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the uplink UE data.

[0250] Clause 39: The method according to any combination of Clauses 32 to 38, wherein outputting the information of the one or more NTN entities includes outputting a Broadcast System Information Block (SIB) indicating one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data.

[0251] Clause 40: The method according to any combination of Clauses 32 to 39, wherein outputting the information of the one or more NTN entities includes outputting dedicated signaling indicating one or more of the following: the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data.

[0252] Clause 41: The method according to any combination of Clauses 32 to 40, wherein outputting the information of the one or more NTN entities includes: outputting the amount of UE data that the NTN entity is configured to store.

[0253] Clause 42: The method according to any combination of Clauses 32 to 41, the method further comprising: obtaining a request for a larger amount of UE data configured to be stored in at least one of the one or more NTN entities; and configuring the NTN entity to store the larger amount of UE data in response to the request.

[0254] Clause 43: The method according to any combination of Clauses 32 to 42, wherein outputting the information of the one or more NTN entities includes: outputting the duration in which the NTN entity is configured to store the UE data.

[0255] Clause 44: The method described in any combination of Clauses 32 to 43, wherein one or more of the amount of UE data that the NTN entity is configured to store or the duration that the NTN entity is configured to store the UE data is logical channel specific.

[0256] Clause 45: The method according to any combination of Clauses 32 to 44, the method further comprising: outputting an indication for each of a plurality of logical channels whether one or more of the amount of UE data that the NTN entity is configured to store or the duration during which the NTN entity is configured to store the UE data applies to the logical channel.

[0257] Clause 46: The method according to any combination of Clauses 32 to 45, further comprising: outputting auxiliary information from the serving NTN entity indicating information about one or more neighboring NTN entities, wherein the information includes the frequency of the one or more neighboring NTN entities, cell identifier (ID), the amount of UE data that the NTN entity is configured to store, the duration for which the NTN entity is configured to store the UE data, the next feeder link availability time, the time of the next access to the store and forward service area, or a combination thereof.

[0258] Clause 47: The method according to any combination of Clauses 32 to 46, the method further comprising: obtaining an indication of the NTN that the UE expects to receive a response to uplink data from it.

[0259] Clause 48: The method according to any combination of Clauses 32 to 47, the method further comprising: outputting an indication of the time for the UE to monitor the response to uplink data.

[0260] Clause 49: The method according to any combination of Clauses 32 to 48, the method further comprising: outputting an indication to an NTN entity for the UE to monitor responses to uplink data.

[0261] Clause 50: The method according to any combination of Clauses 32 to 49, the method further comprising: outputting a first cell prohibition indication indicating that the one or more NTN entities are prohibited from use by a UE that does not support store-and-forward operations; and outputting a second cell prohibition indication indicating whether one or more of the one or more NTN entities are prohibited from use by a UE that supports store-and-forward operations.

[0262] Clause 51: The method described under any combination of Clauses 32 to 50, wherein the one or more NTN entities include satellites.

[0263] Clause 52: The method according to any combination of Clauses 32 to 51 further includes: receiving uplink data from the UE to another UE; and providing the uplink data to a ground station associated with the other UE.

[0264] Clause 53: The method described under any combination of Clauses 32 to 52, wherein the network entity is a satellite.

[0265] Clause 54: An apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method according to any combination of Clauses 1 to 53.

[0266] Clause 55: An apparatus comprising components for performing the method according to any combination of Clauses 1 to 53.

[0267] Clause 56: A non-transitory computer-readable medium comprising executable instructions that, when executed by a processor of a device, cause the device to perform any combination of methods according to Clauses 1 to 53.

[0268] Clause 57: A computer program product embodied on a computer-readable storage medium, the computer program product comprising code for performing the methods described in any combination of Clauses 1 to 53.

[0269] Additional Notes

[0270] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described in some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Additionally, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of these claims.

[0271] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0272] As used herein, "processor," "at least one processor," or "one or more processors" generally refers to a single processor configured to perform one or more operations, or multiple processors configured to jointly perform one or more operations. In the case of multiple processors, the execution of one or more operations may be divided among different processors, but one processor may perform multiple operations, and multiple processors may jointly perform a single operation. Similarly, "memory," "at least one memory," or "one or more memory" generally refers to a single memory configured to store data and / or instructions, or multiple memories configured to jointly store data and / or instructions. A UE may include: one or more memories storing processor-executable code; and one or more processors coupled to one or more memories. A network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to one or more memories.

[0273] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0274] As used herein, the term "determine" encompasses a wide range of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, searching (e.g., looking in a table, database, or other data structure), assertion, and so on. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Furthermore, "determine" can include parsing, selecting, picking, building, and so on.

[0275] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0276] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean “one and only one,” but rather “one or more.” Unless otherwise specifically stated, the term “some” refers to one or more. No element of any claim shall be interpreted in accordance with 35 USC §112(f) unless that element is explicitly stated using the phrase “for a component of.” All structural and functional equivalents of the elements throughout the various aspects described herein that are known to a person skilled in the art or will later be known are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims.

Claims

1. A user equipment (UE) configured for wireless communication, the UE comprising: a memory comprising computer-executable instructions; and a processor configured to execute the computer-executable instructions and cause the UE to: obtain information of one or more non-terrestrial network (NTN) entities configured to store UE data; select, based on the information, one of the one or more NTN entities; and output uplink data to the NTN entity.

2. The UE of claim 1, wherein the information for each of the one or more NTN entities comprises: at least one of an amount of UE data the NTN entity is configured to store or a duration the NTN entity is configured to store the UE data.

3. The UE of claim 2, wherein the at least one of the amount of UE data the NTN entity is configured to store or the duration the NTN entity is configured to store the UE data is associated with a quality of service (QoS) of the UE data or a logical channel.

4. The UE of claim 2, wherein the at least one of the amount of UE data the NTN entity is configured to store or the duration the NTN entity is configured to store the UE data is associated with at least one of a priority of the UE data or a priority of the UE.

5. The UE of claim 2, wherein the at least one of the amount of UE data the NTN entity is configured to store or the duration the NTN entity is configured to store the UE data is UE-specific.

6. The UE of claim 2, wherein the at least one of the amount of UE data the NTN entity is configured to store or the duration the NTN entity is configured to store the UE data is NTN entity-specific.

7. The UE of claim 2, wherein the at least one of the amount of UE data the NTN entity is configured to store or the duration the NTN entity is configured to store the UE data is cell-specific.

8. The UE of claim 2, wherein the at least one of the amount of UE data the NTN entity is configured to store or the duration the NTN entity is configured to store the UE data comprises: a first amount of downlink UE data the NTN entity is configured to store or a duration the NTN entity is configured to store the downlink UE data, and a second amount of uplink UE data the NTN entity is configured to store or a duration the NTN entity is configured to store the uplink UE data.

9. The UE of claim 2, wherein the processor configured to cause the UE to obtain the information of the one or more NTN entities comprises the processor configured to cause the UE to obtain a broadcast system information block (SIB) indicating one or more of the amount of UE data the NTN entity is configured to store or the duration the NTN entity is configured to store the UE data.

10. The UE of claim 2, wherein the processor configured to cause the UE to obtain the information of the one or more NTN entities comprises the processor configured to cause the UE to obtain dedicated signaling indicating one or more of: the amount of UE data the NTN entity is configured to store or the duration the NTN entity is configured to store the UE data.

11. The UE of claim 2, wherein the processor is configured to cause the UE to obtain the information for the one or more NTN entities comprises: the processor configured to cause the UE to obtain the amount of UE data the NTN entity is configured to store.

12. The UE of claim 11, wherein the processor is further configured to cause the UE to determine whether an amount of uplink data at the UE is greater than the amount of UE data the NTN entity is configured to store prior to initiating random access with an NTN entity of the one or more NTN entities.

13. The UE of claim 12, wherein the processor is further configured to cause the UE to select a different NTN entity when the amount of uplink data at the UE is greater than the amount of UE data the NTN entity is configured to store.

14. The UE of claim 12, wherein the processor is further configured to cause the UE to request a greater amount of uplink data of the NTN entity when the amount of uplink data at the UE is greater than the amount of UE data the NTN entity is configured to store.

15. The UE of claim 12, wherein the processor is further configured to cause the UE to limit an amount of the uplink data transmitted to the NTN entity when the amount of uplink data at the UE is greater than the amount of UE data the NTN entity is configured to store.

16. The UE of claim 12, wherein the processor is further configured to cause the UE to initiate random access with the NTN entity when the amount of uplink data at the UE is equal to or less than the amount of UE data the NTN entity is configured to store.

17. The UE of claim 2, wherein the processor is configured to cause the UE to obtain the information for the one or more NTN entities comprises: wherein the processor is configured to cause the UE to obtain the duration the NTN entity is configured to store the UE data.

18. The UE of claim 17, wherein the processor is further configured to cause the UE to select an NTN entity to initiate random access with based on the duration the NTN entity is configured to store the UE data.

19. The UE of claim 18, wherein the processor is configured to cause the UE to select the NTN entity with which to initiate random access comprises: the processor configured to cause the UE to select an NTN entity with a shorter data storage duration when the UE has uplink data with a delay target.

20. The UE of claim 18, wherein the processor is configured to cause the UE to select the NTN entity with which to initiate random access comprises: the processor configured to cause the UE to select an NTN entity with a longer data storage duration when the UE has delay sensitive uplink data.

21. The UE of claim 2, wherein the at least one of the amount of UE data the NTN entity is configured to store or the duration the NTN entity is configured to store the UE data is logical channel specific.

22. The UE of claim 21, wherein the processor is further configured to cause the UE to obtain, for each logical channel of a plurality of logical channels, an indication of whether one or more of the quantity of UE data that the NTN entity is configured to store for the logical channel or the duration for which the NTN entity is configured to store the UE data applies to the logical channel.

23. The UE of claim 21, wherein the processor is further configured to cause the UE to select a logical channel of a plurality of logical channels for outputting uplink data to an NTN entity based on whether the logical channel satisfies the quantity of UE data that an NTN entity of the one or more NTN entities is configured to store or the duration for which the NTN entity is configured to store the UE data.

24. The UE of claim 1, wherein the processor is further configured to cause the UE to obtain assistance information from a serving NTN entity that indicates information of one or more neighboring NTN entities, wherein the information comprises a frequency, a cell identifier (ID), a quantity of UE data that the NTN entity is configured to store, a duration for which the NTN entity is configured to store the UE data, a next feeder link availability time, a time to next access of a store-and-forward service area, or a combination thereof of the one or more neighboring NTN entities.

25. The UE of claim 1, wherein the processor is further configured to cause the UE to: output uplink data to one of the one or more NTN entities; and output an indication of whether the UE expects a response to the uplink data from the NTN entity or another NTN entity.

26. The UE of claim 25, wherein the processor is further configured to cause the UE to obtain an indication of at least one of: a time to monitor for the response to the uplink data or an NTN entity to monitor for a response to the uplink data.

27. The UE of claim 1, wherein the processor is further configured to cause the UE to: obtain a first cell barred indication that indicates that the one or more NTN entities are barred; obtain a second cell barred indication that indicates whether one or more of the one or more NTN entities are barred; and only follow the first cell barred indication when the UE does not support store-and-forward operations and only follow the second cell barred indication when the UE supports store-and-forward operations.

28. A method for wireless communication by a user equipment (UE), the method comprising: obtaining information of one or more non-terrestrial network (NTN) entities configured to store UE data; selecting one of the one or more NTN entities based on the information; and outputting uplink data to the NTN entity.

29. A network entity configured for wireless communication, the network entity comprising: a memory comprising computer-executable instructions; and a processor configured to execute the computer-executable instructions and cause the network entity to: output, to a user equipment (UE), information of one or more non-terrestrial network (NTN) entities, including an NTN entity, configured to store UE data, the information indicating at least one of: an amount of UE data the NTN entity is configured to store or a duration the NTN entity is configured to store the UE data.

30. A method for wireless communication by a network entity, the method comprising: outputting, to a user equipment (UE), information of one or more non-terrestrial network (NTN) entities, including an NTN entity, configured to store UE data, the information indicating one or more of: an amount of UE data the NTN entity is configured to store or a duration the NTN entity is configured to store the UE data.

Images