System architecture for direct NTN communication without feed link

Abstract

A method for wireless communication at a network entity and related devices is provided. In the method, the network entity receives, from a first user equipment (UE), a communication signal for end-to-end (E2E) communication with a second UE. The communication signal includes identification data for identifying the second UE for the E2E communication. The network entity also routes the communication signal through the network entity, where the communication signal bypasses a ground-based feed link, and sends the communication signal to the second UE to enable the E2E communication between the first UE and the second UE.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. non-provisional patent application No. 18 / 295,663, filed April 4, 2023, entitled “SYSTEM ARCHITECTURE FOR DIRECTNTN COMMUNICATION WITHOUT A FEEDER LINK”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to system architectures for direct non-terrestrial network (NTN) communication without a power supply link. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This invention is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided for wireless communication at a first user equipment (UE). The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to: generate identification data identifying a second UE for direct non-terrestrial network (NTN) communication; and transmit a communication signal including the identification data to a network entity for the network entity to route the communication signal to the second UE, thereby enabling the direct NTN communication with the second UE, wherein the communication signal bypasses a terrestrial-based feeder link.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. Based at least in part on information stored in the memory, the at least one processor may be configured to: receive from a first UE a communication signal for direct NTN communication with a second UE, wherein the communication signal includes identification data for identifying the second UE for the direct NTN communication; route the communication signal through the network entity, wherein the communication signal bypasses a terrestrial-based feeder link; and transmit the communication signal to the second UE to enable the direct NTN communication between the first UE and the second UE.

[0009] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0012] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0013] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0014] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0015] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0016] Figure 4 This is a diagram illustrating an example of NTN communication with a power supply link.

[0017] Figure 5A This is a diagram illustrating an example of NTN coverage.

[0018] Figure 5B This is a diagram illustrating an example of NTN coverage extension via ISL.

[0019] Figure 6A This is a diagram illustrating examples of data routing in the control plane by an NTN platform with CN functionality, according to various aspects of this disclosure.

[0020] Figure 6B This is a diagram illustrating examples of data routing in the user plane by an NTN platform with CN functionality, according to various aspects of this disclosure.

[0021] Figure 7A This is a diagram illustrating examples of UE connections to the control plane of an NTN platform with satellite relay capabilities, according to various aspects of this disclosure.

[0022] Figure 7B This is a diagram illustrating examples of data routing in the user plane by an NTN platform with satellite relay capabilities, according to various aspects of this disclosure.

[0023] Figure 8 This is a diagram illustrating examples of data routing on the control plane according to various aspects of this disclosure.

[0024] Figure 9 This is a diagram illustrating examples of data routing on the user plane according to various aspects of this disclosure.

[0025] Figure 10 This is a diagram illustrating examples of data routing for E2E links on the control plane according to various aspects of this disclosure.

[0026] Figure 11This is a diagram illustrating examples of data routing for E2E links on the user plane according to various aspects of this disclosure.

[0027] Figure 12 This is a diagram illustrating examples of data routing for E2E links on the control plane according to various aspects of this disclosure.

[0028] Figure 13 This is a diagram illustrating examples of NTN platforms used as SL relays according to various aspects of this disclosure.

[0029] Figure 14 This is a call flowchart illustrating a method of wireless communication according to various aspects of this disclosure.

[0030] Figure 15 This is a flowchart illustrating various methods of wireless communication at a network entity according to various aspects of this disclosure.

[0031] Figure 16 This is a flowchart illustrating various methods of wireless communication at a network entity according to various aspects of this disclosure.

[0032] Figure 17 This is a flowchart illustrating various methods of wireless communication at a UE according to various aspects of this disclosure.

[0033] Figure 18 This is a flowchart illustrating various methods of wireless communication at a UE according to various aspects of this disclosure.

[0034] Figure 19 These are illustrations illustrating specific hardware implementations used for example devices and / or network entities.

[0035] Figure 20 This is a diagram illustrating an example of a hardware implementation used for an example network entity. Detailed Implementation

[0036] Various aspects relate to communication systems as a whole. Some aspects more specifically relate to system architectures for direct NTN communication without a feeder link. In some examples, a network entity may be configured to: receive communication signals from a first UE for end-to-end (E2E) communication with a second UE. The communication signals may include identification data for identifying the second UE for the E2E communication. The network entity may also be configured to: route the communication signals through itself, whereby the communication signals bypass a terrestrial feeder link; and transmit the communication signals to the second UE to enable the E2E communication between the first UE and the second UE. In some aspects, the E2E communication may be direct NTN communication. In some aspects, the network entity may be equipped with a core set of network functions and may route the communication signals through this core set of network functions. In some aspects, the network entity may be equipped with a satellite relay function and may route the communication signals through this satellite relay function.

[0037] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by using network entities to route communication signals from one UE to another and bypassing terrestrial feeder links, the described techniques can be used to reduce latency and feeder link load by enabling direct NTN communication between UEs. Additionally, by enabling direct NTN communication between UEs without feeder links, the described techniques can be used to provide better service availability and reliability in situations where feeder links are unavailable.

[0038] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0039] Various apparatuses and methods are described below, and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0040] As an example, an element, or any part of an element, or any combination of elements, may be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0041] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. As examples, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0042] While aspects, implementations, and / or use cases are described herein by way of example, other or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0043] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0044] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0045] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations advocated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. The various units in a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0046] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as F1 interfaces. DUs 130 may communicate with one or more RUs 140 via corresponding fronthaul links. RUs 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served simultaneously by multiple RUs 140.

[0047] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) 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 the associated processor or controller providing instructions to the communication interfaces of these units, 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, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive and / or transmit signals to one or more other units via wireless transmission media.

[0048] In some aspects, the CU 110 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 the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 110 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). The CU 110 can be implemented to communicate with the DU 130 for network control and signaling, as needed.

[0049] DU 130 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Medium 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.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0050] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 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, 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 140 may be implemented to handle over-the-air (OTA) communication with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communication with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration enables the implementation of the DU 130 and CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0051] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 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 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 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 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115, which is configured to support the functionality of the SMO framework 105.

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

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

[0054] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell), and the secondary component carrier can be referred to as the secondary cell (SCell).

[0055] Some UEs 104 can communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 can use DL / UL Wireless Wide Area Network (WWAN) spectrum. The D2D communication link 158 can use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through various wireless D2D communication systems, such as Bluetooth. TM (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.) TM(Wi-Fi is a trademark of the Wi-Fi Alliance, LTE or NR)

[0056] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP 150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

[0057] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Although a portion of FR1 is greater than 6GHz, it is often referred to (interchangeably) as the "sub-6GHz" band in various documents and articles. Similar naming issues sometimes arise with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0058] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands for these IF bands as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range designations FR2-2 (52.6 GHz – 71 GHz), FR4 (71 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher bands falls within the EHF band.

[0059] In view of the above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0060] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0061] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0062] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that processes signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, a location determination entity (PDE), a serving mobile location center (SMLC), a mobile location center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or the base station 102 serving UE 104. The measured signals may be based on one or more of the following systems / signals / sensors: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0063] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0064] Refer again Figure 1 In some aspects, UE 104 may include a direct NTN communication component 198. The direct NTN communication component 198 may be configured to: generate identification data identifying a second UE for direct NTN communication; and transmit a communication signal including the identification data to a network entity for the network entity to route the communication signal to the second UE, thereby enabling direct NTN communication with the second UE, wherein the communication signal bypasses a terrestrial-based feeder link. In some aspects, base station 102 may include a direct NTN communication component 199. The direct NTN communication component 199 may be configured to: receive a communication signal from a first UE for direct NTN communication with the second UE, wherein the communication signal includes identification data identifying the second UE for the direct NTN communication; route the communication signal through the network entity, wherein the communication signal bypasses a terrestrial-based feeder link; and transmit the communication signal to the second UE to enable direct NTN communication between the first UE and the second UE. While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0065] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2CFigure 250 illustrates an example of the second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured using the 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). Note that the following description also applies to the 5G NR frame structure as TDD.

[0066] Figures 2A to 2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL can be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0067]

[0068]

[0069] Table 1: Parameter Set, SCS, and CP

[0070] For a normal CP (14 symbols / slot), different parameter sets μ0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set μ, there are 14 symbols / slot and 2... μ One time slot / subframe. The subcarrier spacing can be equal to 2μ*15kHz, where μ is a parameter set from 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples are provided for a normal CP with 14 symbols per time slot and a parameter set μ=2 with 4 time slots per subframe. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more different bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0071] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0073] Figure 2BExamples 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) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the 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 DM-RS. 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 (also known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Blocks (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0074] like Figure 2C As illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or second symbol of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb structures within that comb structure. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0075] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may 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 hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0076] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with upper-layer packet data unit (PDU) delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0077] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal cluster based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. Channel estimation from channel estimator 374 is used to determine the decoding and modulation scheme, as well as for spatial processing. The channel estimation can be derived from a reference signal and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0078] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0079] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

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

[0081] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0082] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0083] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets between transport and logical channels. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0084] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform coupling. Figure 1 The various aspects of the direct NTN communication component 198.

[0085] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform coupling. Figure 1 The various aspects of the direct NTN communication component 199.

[0086] In traditional satellite communications, satellites can connect to terrestrial network infrastructure via feed links to facilitate data transmission within the NTN, which can act as a gateway for the non-terrestrial network (NTN). Figure 4 Figure 400 illustrates an example of NTN communication with a power supply link. Figure 4 In this configuration, a first UE (UE1 402) can communicate with a second UE (UE2 404) via satellite 410, which is connected to a terrestrial network 420 via a feed link. During this process, satellite 410 can function as either a transparent satellite or a regenerating satellite. The transparent satellite receives communication signals from the UE and retransmits them back to the ground or another UE without extensive onboard signal processing. The regenerating satellite performs onboard signal processing and routing on the received communication signals. The regenerating satellite can perform onboard signal processing related to base station functions (e.g., gNB functions) with or without an inter-satellite link (ISL) for communicating with neighboring satellites. In some examples, the regenerating satellite can incorporate gNB-DU functions and process gNB-DU payloads, such as physical (PHY) layer processing, media access control (MAC) layer processing, and radio link control (RLC) layer processing.

[0087] In environments where NTN provides extensive coverage, two communicating UEs are highly likely to be covered by the same NTN. Furthermore, using ISL between nearby satellites can further extend the coverage area of ​​direct NTN communication, thereby improving connectivity between UEs. By enabling direct communication between UEs without a terrestrial network (NW), latency and feeder link load can be reduced, allowing communication even in the presence of feeder link coverage gaps. Figure 5A This is an example illustration of NTN coverage, shown in diagram 500. Figure 5A In this context, multiple UEs (e.g., UE1, UE2, UE3, and UE4) can be within the coverage area of ​​satellite 502. Figure 5B Figure 550 illustrates an example of NTN coverage extension via ISL. Figure 5BIn this system, multiple satellites (e.g., satellites 1, 552, and 554) can be connected via ISL to extend the coverage area of ​​direct NTN communication. This allows for the coverage of more UEs (e.g., UE1 through UE6) than a single satellite (e.g., satellite 502) can provide.

[0088] Furthermore, leveraging control plane characteristics can enhance the overall performance and efficiency of the communication system without involving terrestrial NWs. This capability supports scenarios where feeder links to terrestrial NWs become unavailable, enabling future NTN networks to operate independently of terrestrial networks (TN NWs).

[0089] The example aspect presented in this paper provides a system architecture that does not rely on a feeder link to the terrestrial NW and allows NTN communication without a gateway. This is especially important when the feeder link to the NTN NW becomes unavailable.

[0090] In some respects, an NTN platform may be equipped with base station (gNB) and core network (CN) functions. The base station may include functions required for (radio) access to the network, such as functions managed at the access layer (AS). CN functions may include at least one of user plane functions (UPF), access and mobility management functions (AMF), session management functions (SMF), and / or data network (DN) or server capabilities. Data may be routed from a UE to its peer UE via the onboard CN / DN. As used herein, "non-terrestrial network" or "NTN" may refer to a communications network that primarily utilizes satellite or other airborne platforms to provide connectivity. "NTN platform" may refer to the network infrastructure (e.g., satellite) that provides connectivity within an NTN network, and "NTN communications" refers to communications conducted via the NTN.

[0091] The potential impacts of various aspects of this disclosure on the CN include dynamic interconnection between mobile satellites, CN nodes, and / or UEs, as well as handover between serving satellites. The incorporation of CN functionality can lead to increased satellite complexity and power consumption due to the integration of multiple network components and functionalities onto the satellite. To address these challenges, the proposed solutions may be transparent to the radio access network (RAN) or have a minimal impact on the RAN.

[0092] Figure 6A Figure 600 illustrates examples of data routing in the control plane by an NTN platform with CN functionality, according to various aspects of this disclosure. Figure 6AIn this context, the NTN platform (e.g., satellite 604) may be equipped with CN functionality, and control plane data can be routed from a UE (e.g., UE 602) to the CN functionality residing on the NTN platform (e.g., satellite 634) via the onboard CN / DN. Communication between the UE (e.g., UE 602) and the NTN platform (e.g., satellite 634) may include data on AS layer 610, which may include PHY layer 612, MAC layer 614, RLC layer 616, PDCP layer 618, and RRC layer 619. Additionally, the NTN platform (e.g., satellite 634) may terminate the Non-Access Stratum (NAS) layer 620 (the layer between the UE and the CN node) with the UE (e.g., UE 602) on the control plane. In some aspects, CN functions residing on different satellites may interconnect and / or coordinate with each other. Figure 6B Figure 650 illustrates examples of data routing in the user plane by an NTN platform with CN functionality, according to various aspects of this disclosure. Figure 6B In this context, the NTN platform (e.g., satellite 654) may be equipped with CN functionality and can route data from one UE (e.g., UE 652) to another UE (e.g., UE 656) via the onboard CN / DN. Data to be routed by the NTN platform (e.g., satellite 654) may include data on AS layer 660, which may include PHY layer 662, MAC layer 664, RLC layer 666, PDCP layer 668, and / or SDAP layer 670. Additionally, the NTN platform (e.g., satellite 604) may also route data on the Non-Access Stratum (NAS) layer on the control plane, which may include PDU layer 672. E2E data (e.g., data in the upper layers) can be communicated via the AS layer and NAS layer.

[0093] In some aspects, the NTN platform may be equipped with satellite relay functionality (e.g., via satellite relay cells), which may include routing capabilities enabling E2E services to be routed from one UE to another via one or more satellites in the network. Furthermore, the UE-Radio Access Network (RAN) air interface may serve as a baseline for communication between the UE and satellites. In one example, the UE-Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) air interface may serve as a baseline for communication between the UE and satellites. In another example, the UE-New Radio (NR) Radio Access Network (UE-NR RAN) air interface may serve as a baseline for communication between the UE and satellites. In some aspects, the NTN platform may be equipped with RAN nodes that integrate routing / relay functionality. In some aspects, existing protocols and procedures (particularly the Uu protocols and / or procedures above the AS layer) may be modified. For example, certain side link (SL) or SL relay protocols and procedures can be considered and used to modify Uu protocols and procedures, such as including consideration of side link (SL) security schemes and authorization schemes to ensure E2E link security and UE authorization, respectively.

[0094] Uu Radio Resource Control (RRC) functionality can be utilized to provide control. This approach, by adding relay / routing functionality to onboard base stations (e.g., gNBs), may result in increased satellite complexity and power consumption. However, the overall increase is less than that observed in schemes incorporating CN functionality into the satellite. Additionally, this proposed architecture may lead to changes in RAN-related technical specifications to accommodate onboard relay functionality.

[0095] Figure 7A Figure 700 illustrates an example of a UE connecting to the control plane of an NTN platform with satellite relay capabilities, according to various aspects of this disclosure. Figure 7A In this configuration, the NTN platform (e.g., satellite 704) may be equipped with an onboard RAN node (e.g., gNB) that can terminate the control plane connection of the UE (e.g., UE 702) at AS layer 730. Control data between UE 702 and the NTN platform (e.g., satellite 704) can be transmitted on the control plane via PHY layer 710, MAC layer 712, RLC layer 714, PDCP layer 716, and RRC layer 718. In some aspects, RRC functions residing on different satellites (e.g., satellites 734, 736) can interconnect / coordinate with each other, for example, via ISL 738. Figure 7B Figure 750 illustrates examples of data routing in the user plane by an NTN platform with spaceborne relay capabilities, according to various aspects of this disclosure. Figure 7BIn this context, the NTN platform (e.g., satellites 784 and 786 connected via ISL788) may be equipped with onboard relay capabilities and can relay data from one UE (e.g., UE 752) to another UE (e.g., UE 756). Data to be relayed by the NTN platform (e.g., satellites 784 and 786) may include data on AS layer 770, which may include PHY layer 760, MAC layer 762, RLC layer 764, PDCP layer 766, and SDAP layer 768. In some aspects, some of the listed layers may or may not be used (e.g., SDAP layer 768 and / or PDCP layer 766 may be optional for AS layer 770). User data such as E2E data (e.g., data in upper layer 780) may be communicated on top of AS layer 770. In some aspects, additional layers may be added, and these additional layers may be used to identify E2E communication links and / or routing paths, for example, such as... Figure 9 , Figure 10 , Figure 11 and Figure 12 As shown later.

[0096] In some respects, for NTN platforms equipped with satellite relay capabilities, a Layer 3 (L3) relay mechanism can be implemented. This L3 relay mechanism can utilize satellite relay cells to manage and update routes by implementing an additional layer or function above the AS layer. This additional layer may take into account factors such as IP, Quality of Service (QoS) flows, Radio Bearers (RBs), Logical Channels (LCHs), Radio Network Temporary Identifiers (RNTIs), the location of peer UEs, and / or headers at the additional layer or function. In some respects, this additional layer may be referred to as the identification layer.

[0097] When each UE is restricted to communicating with one peer UE, routing can be performed based on the identity of the sending UE. The UE can be controlled by the NTN node via the Uu interface, allowing the UE to camp in different RRC states, obtain appropriate AS configuration, and support mobility. To transmit user plane data over E2E links, the UE can employ the Uu radio protocol stack. To facilitate this approach, additional layers or functions can be implemented at the UE.

[0098] Figure 8 Figure 800 illustrates examples of data routing on the control plane according to various aspects of this disclosure. Figure 8In this configuration, a UE (e.g., UE1) can connect to satellite 804 via a Uu air interface used for PHY layer 812, MAC layer 814, RLC layer 816, PDCP layer 818, and RRC layer 820. Satellite 804 can have different RRC entities, each corresponding to one UE. That is, satellite 804 can use one RRC entity to control the operation of UE1 802 and another RRC entity to control the operation of UE2 806.

[0099] Figure 9 Figure 900 illustrates examples of data routing on a user plane according to various aspects of this disclosure. Figure 9In this configuration, the UE (UE1 902) can use the Uu air interface to transmit user plane data for the E2E link. The Additional Layer (AL) layer 910 can be implemented on the AS layer 920 (which may include the PHY layer 922, MAC layer 924, RLC layer 926, PDCP layer 928, and / or SDAP layer 930). The AL layer 910 can be used to transmit data for identifying the source UE (e.g., UE1 902) and / or the destination UE (e.g., UE2 906). The data for identifying the source UE (e.g., UE1 902) and / or the destination UE (e.g., UE2 906) can be based on the IP address of the source UE (e.g., UE1 902) and / or the destination UE (e.g., UE2 906), the QoS flow associated with the data, the RB associated with the data, the LCH associated with the data, the RNTI of the source UE and / or the destination UE, the location of the peer / destination UE, and / or the header at the AL layer. In some aspects, data identifying the source UE (e.g., UE1 902) and / or the destination UE (e.g., UE2 906) may be appended to and / or associated with a packet to be sent to the destination UE (e.g., UE2 906). After the NTN platform / node receives the packet, it may use the data identifying the destination UE (e.g., UE2 906) to forward the packet to that destination UE (e.g., UE2 906). In some aspects, data identifying the source UE (e.g., UE1 902) and / or the destination UE (e.g., UE2 906) may be sent to the destination UE (e.g., UE2 906) along with the packet. Therefore, once the data identifying the source UE (e.g., UE1 902) and / or the destination UE (e.g., UE2 906) is received, the destination UE (e.g., UE2 906) can recognize the source UE (e.g., UE1 902) that generated the packet. In some respects, before data used to identify a source UE (e.g., UE1 902) and / or a destination UE (e.g., UE2 906) is sent by an NTN platform / node to the destination UE (e.g., UE2 906), the NTN platform / node may process and / or modify the data so that it can be correctly understood by the destination UE (e.g., UE2 906). When the sending UE (UE1 902) is restricted to communicating with a peer / destination UE, the data used to identify the destination UE (e.g., UE2 906) may be based on the identity of the sending UE (UE1 902).

[0100] In some aspects, two UEs can establish an E2E control layer, such as an E2E RRC / NAS layer, which is transmitted through the NTN node and the NR Uu PDCP layer and the layers below the PDCP layer. The E2E RRC / NAS layer can be used to optimize E2E and joint link control, such as E2E link establishment and release and link mobility management.

[0101] Figure 10 Figure 1000 illustrates examples of data routing for E2E links on the control plane according to various aspects of this disclosure. Figure 10 In this implementation, the E2E RRC / NAS layer 1020 can be implemented for one UE (e.g., UE1 1002) to control and / or coordinate the operation of another UE (e.g., UE2 1006). The E2E RRC / NAS layer 1020 can be transmitted on top of the AL layer 1018, PDCP layer 1016, RLC layer 1014, MAC layer 1012, and PHY layer 1010. In some aspects, after the NTN platform / node receives E2E RRC / NAS data from the transmitting UE (e.g., UE1 1002), the NTN platform can use the information associated with the AL layer 1018 to identify the destination UE (e.g., UE2 1006) and forward packets to that destination UE (e.g., UE2 1006).

[0102] In some aspects, a Layer 2 (L2) relay mechanism can be implemented, which uses satellite cells to implement additional layers or functions above the RLC layer to route data packets. The UE can be controlled by the NTN node via the Uu interface, thereby enabling the UE to camp in different RRC states, obtain appropriate configurations, and support mobility.

[0103] To transmit E2E user plane data, layers below the PDCP layer can terminate at each UE and satellite, while layers above the PDCP layer can terminate at both end UEs. Both the Uu and PC5 interfaces can be implemented for these layers. The current PC5 PDCP and PC5 SDAP layers can be modified, and additional layers can be added at the UE.

[0104] Figure 11 Figure 1100 illustrates examples of data routing for E2E links on the user plane according to various aspects of this disclosure. Figure 11In this configuration, the UE (UE1 1102) can use the Uu air interface to transmit user plane data for the E2E link. The Additional Layer (AL) layer 1110 can be implemented on top of the RLC layer. The AL layer 1110 can be used to transmit data identifying the destination UE (e.g., UE2 1106) to which data is to be transmitted. The PDCP layer 1112 and the layers above the PDCP layer can each terminate at both UEs (UE1 11102 and UE2 1106). Satellite 1104 can process data from the PHY layer 1120, MAC layer 1122, RLC layer 1124, and AL layer 1110 of UE1 11102 and transmit the processed data to UE2 1106. Data on the PDCP layer 1112 and SDAP layer 1114 can be transmitted to UE2 1106 via the Uu air interface or the side link (PC5) interface.

[0105] Figure 12 Figure 1200 is an illustration of examples of data routing for E2E links on the control plane according to various aspects of this disclosure. Figure 12 In this configuration, the E2E RRC / NAS layer 1220 can be implemented for one UE (e.g., UE1 1202) to control and / or coordinate the operation of another UE (e.g., UE2 1206). The E2E RRC / NAS layer 1220 can be transmitted on top of the PDCP layer 1212. Figure 12 In the example, AL layer 1210 can be on top of RLC layer 1208.

[0106] One of the key advantages of the L2 relay mechanism is that the satellite is not involved in E2E security, which is handled at the PDCP layer 1212, which terminates at both end UEs (e.g., UE1 1202 and UE2 1206). E2E control layers, such as the E2E RRC / NAS layer 1220, are transmitted via the NTN node and the PDCP layer 1212. Layers below the PDCP layer terminate at the satellite 1204 and each UE (e.g., UE1 1202 and UE2 1206), while the PDCP layer 1212 and the E2E RRC / NAS layer 1220 terminate at both end UEs (UE1 1202 and UE2 1206).

[0107] In some respects, the NTN platform can be used as a side-link (SL) relay, such as an SL UE-to-UE (U2U) relay. Within this NTN platform, the NTN payload can act as an SL relay to facilitate data transfer from one UE to another. Figure 13 Figure 1300 illustrates examples of an NTN platform used as an SL relay according to various aspects of this disclosure. Figure 13In this context, the NTN platform (satellite 1304) can receive data from or send data to a UE (e.g., UE1 1302 and UE2 1306) via a sidelink interface.

[0108] Since traditional sidelink designs are not optimized for long-distance communication, modifications to the specifications can be made to accommodate this new functionality. Therefore, separate sidelink capabilities, distinct from legacy sidelink operations, can be implemented for the UE. This approach may increase satellite complexity, requiring different air interfaces for regular NTN communication over terrestrial NWs and direct NTN communication bypassing terrestrial NWs.

[0109] To adapt to these different communication scenarios, the UE can implement both sidelink and Uu interface. However, due to the inherently limited capabilities of sidelink relay, this approach may exhibit lower efficiency and robustness compared to NTN platforms equipped with satellite relay functionality.

[0110] Table 2 illustrates various architectures for direct NTN communication according to various aspects of this disclosure.

[0111]

[0112] Table 2: Comparison of architectures for direct NTN communication

[0113] This disclosure introduces a novel direct NTN communication architecture that offers several functional benefits compared to existing approaches. This innovative architecture is designed to reduce latency and feeder link load, providing a more efficient and responsive communication experience. The direct NTN communication architecture also supports situations where feeder links to terrestrial NWs are unavailable or experience coverage holes, ensuring more reliable connectivity in challenging conditions. A key advantage of the proposed architecture is its ability to enable future NTN networks to operate independently of TN NWs. This flexibility provides the foundation for more general and adaptable network configurations in rapidly evolving communication environments. Furthermore, the proposed system architecture aims to reuse current protocol stack layers at the UE and satellite levels, minimizing additional complexity at these network elements. Therefore, aspects of this disclosure are more commercially viable and deployment-friendly compared to existing solutions.

[0114] Figure 14 This is a call flow diagram 1400 illustrating a method of wireless communication according to various aspects of this disclosure. Each example aspect is described in conjunction with UE 1402, base station 1404, UE 1406, and base station 1408. These aspects may be performed by the aggregated base station 1404 and / or by one or more components of base station 1404 (e.g., such as CU 110, DU 130, and / or RU 140) and UE 1402.

[0115] like Figure 14 As shown, UE 1402 (e.g., the first UE) can generate identification data identifying the second UE at 1410. The second UE can be UE 1406.

[0116] At 1412, UE 1402 may send a communication signal to a base station (e.g., base station 1404) for E2E communication with a second UE. This communication signal may include identification data identifying the first UE and / or the second UE for the E2E communication. In some aspects, the E2E communication may be direct NTN communication. For example, refer to... Figure 9 UE 902 may send a communication signal to the base station (satellite 904) for direct NTN communication with a second UE (e.g., UE2 906). The communication signal may include identification data for identifying the first UE (e.g., UE1 902) and / or the second UE (e.g., UE2 906) for the direct NTN communication.

[0117] At location 1414, base station 1404 can route communication signals via base station 1404. These communication signals can bypass the ground-based feeder link. For example, refer to... Figure 9 The base station (satellite 904) can route communication signals (data in PHY layer 922, MAC layer 924, RLC layer 926, etc.) through the base station (satellite 904).

[0118] In some respects, at location 1416, base station 1404 can route communication signals through the core network function set. For example, refer to Figure 6A The base station (satellite 604) can route communication signals (route data on AS layer 610 and / or NAS layer 620) through the core network function set.

[0119] In some respects, at location 1418, base station 1404 can route communication signals via its onboard relay function. For example, see reference... Figure 7A The base station (satellite 904) can route communication signals through its onboard relay function.

[0120] In some respects, at 1420, base station 1404 can send communication signals to UE 1406 to enable direct NTN communication between UE 1402 and UE 1406. For example, see reference... Figure 6A The base station (satellite 604) can send communication signals to UE 606 to enable direct NTN communication between UE 602 and UE 606. (Reference) Figure 7AThe base station (satellite 704) can send communication signals to UE 706 to enable direct NTN communication between UE 702 and UE 706. In some aspects, the communication signals may include identification data for identifying the first UE (e.g., UE1 902) and / or the second UE (e.g., UE2 906) used for the direct NTN communication. In one example, the identification data helps the second UE (e.g., UE2 906) identify the first UE (e.g., UE1 902).

[0121] In some respects, base station 1404 can transmit communication signals to UE 1406 via base station 1408. That is, base station 1404 can transmit communication signals to base station 1408 at 1422, and base station 1408 can transmit communication signals to UE 1406 at 1424. For example, refer to... Figure 6A The base station (satellite 634) can send communication signals to the UE 606 through another base station (satellite 636) via an inter-node link (such as ISL 638).

[0122] Figure 15 This is a flowchart 1500 illustrating a method for wireless communication at a network entity according to various aspects of this disclosure. The method can be performed by a network entity. The network entity can be... Figure 1 The base station or base station component in the access network, or core network component (e.g., base station 102, 310, 1404; satellite 604, 654, 704, 754, 1304 or...). Figure 19 (Network entity 1902 in the hardware implementation). This method provides an E2E communication architecture that enhances connectivity between UEs without relying on terrestrial networks or feeder links. The method minimizes latency and reduces load on feeder links, and enables communication between UEs even when feeder links to terrestrial networks are unavailable. Therefore, this method significantly improves the availability and reliability of wireless communication.

[0123] like Figure 15 As shown, at point 1502, the network entity can receive communication signals from the first UE for E2E communication with the second UE. These communication signals may include identification data identifying the second UE used for the E2E communication. The first UE may be UE 104, 350, 602, 652, 702, 752, 1302, 1402, or... Figure 19 The hardware implementation of the device 1904. The second UE can be UE 104, 350, 606, 656, 706, 756, 1306, 1406, or... Figure 19 The hardware implementation of the device 1904. Figure 6A , Figure 6B , Figure 7A , Figure 7B , Figure 13 and Figure 14 Various aspects of the steps in flowchart 1500 are illustrated. For example, refer to... Figure 14 The network entity (base station 1404) can receive communication signals from the first UE 1402 at location 1412 for E2E communication with the second UE 1406. (See reference) Figure 6A The network entity (satellite 604) can receive communication signals from the first UE 602 for E2E communication with the second UE 606. In some aspects, 1502 can be performed by the direct NTN communication component 199.

[0124] At point 1504, this network entity can route communication signals. These communication signals can bypass ground-based feeder links. For example, refer to... Figure 6A The network entity (satellite 604) can route communication signals through itself. These communication signals can bypass ground-based feeder links. In some respects, 1504 can be performed by the direct NTN communication component 199.

[0125] At point 1506, the network entity can send the communication signal to the second UE to enable E2E communication between the first UE and the second UE. For example, refer to Figure 14 The network entity (base station 1404) can send communication signals at 1420 to the second UE 1406 to achieve E2E communication between the first UE 1402 and the second UE 1406. (Reference) Figure 6A The network entity (satellite 604) can send communication signals to the second UE 606 to enable E2E communication between the first UE 602 and the second UE 606. In some aspects, 1506 can be performed by the direct NTN communication component 199.

[0126] Figure 16 This is a flowchart 1600 illustrating a method for wireless communication at a network entity according to various aspects of this disclosure. The method can be performed by the network entity. The network entity can be... Figure 1 The base station or base station component in the access network, or core network component (e.g., base station 102, 310, 1404; satellite 604, 654, 704, 754, 1304 or...). Figure 19 (Network entity 1902 in the hardware implementation). This method provides an E2E communication architecture that enhances connectivity between UEs without relying on terrestrial networks or feeder links. The method minimizes latency and reduces load on feeder links, and enables communication between UEs even when feeder links to terrestrial networks are unavailable. Therefore, this method significantly improves the availability and reliability of wireless communication.

[0127] like Figure 16 As shown, at 1602, the network entity can receive communication signals from the first UE for E2E communication with the second UE. These communication signals may include identification data identifying the second UE used for the E2E communication. The first UE may be UE 104, 350, 602, 652, 702, 752, 1302, 1402, or... Figure 19 The hardware implementation of the device 1904. The second UE can be UE 104, 350, 606, 656, 706, 756, 1306, 1406, or... Figure 19 The hardware implementation of the device 1904. Figure 6A , Figure 6B , Figure 7A , Figure 7B , Figure 13 and Figure 14 Various aspects of the steps in flowchart 1600 are illustrated. For example, refer to... Figure 14 The network entity (base station 1404) can receive communication signals from the first UE 1402 at location 1412 for E2E communication with the second UE 1406. (See reference) Figure 6A The network entity (satellite 604) can receive communication signals from the first UE 602 for E2E communication with the second UE 606. In some aspects, 1602 can be performed by the direct NTN communication component 199.

[0128] At point 1604, this network entity can route communication signals. These communication signals can bypass ground-based feeder links. For example, refer to... Figure 6A The network entity (satellite 604) can route communication signals through itself. These communication signals can bypass ground-based feeder links. In some respects, 1604 can be implemented by the direct NTN communication component 199.

[0129] At point 1606, the network entity can send the communication signal to the second UE to enable E2E communication between the first UE and the second UE. For example, refer to... Figure 14 The network entity (base station 1404) can send communication signals at 1420 to the second UE 1406 to achieve E2E communication between the first UE 1402 and the second UE 1406. (Reference) Figure 6A The network entity (satellite 604) can send communication signals to the second UE 606 to enable E2E communication between the first UE 602 and the second UE 606. In some aspects, 1606 can be performed by the direct NTN communication component 199.

[0130] In some respects, this E2E communication can be direct NTN communication, and the network entity can be the first satellite in the first NTN. For example, see reference... Figure 6A E2E communication between UEs (e.g., UE 602 and UE 606) can be direct NTN communication, and the network entity can be the first satellite (satellite 604) in the first NTN.

[0131] In some aspects, in order to receive the communication signal from the first UE, the network entity may be configured to: receive identification data for identifying at least one of the first UE and the second UE, and in order to send the communication signal to the second UE, the network entity may be configured to: send the identification data for identifying at least one of the first UE and the second UE. For example, refer to Figure 6A In order to receive the communication signal from the first UE (e.g., UE 602), the network entity (e.g., satellite 604) may be configured to: receive identification data for identifying at least one of the first UE (e.g., UE 602) and the second UE (e.g., UE 606), and in order to send the communication signal to the second UE (e.g., UE 606), the network entity (e.g., satellite 604) may be configured to: send the identification data for identifying at least one of the first UE (e.g., UE 602) and the second UE (e.g., UE 606).

[0132] In some aspects, the network entity may be a first network entity, and in order to transmit the communication signal, the network entity may be configured to transmit the communication signal to the second UE via a second network entity. The second network entity may be a second satellite in the first NTN, and the first network entity and the second network entity may be connected via an inter-node link. For example, refer to... Figure 6A The network entity can be a first network entity (satellite 634), and in order to transmit the communication signal, the network entity (satellite 634) can be configured to transmit the communication signal to the second UE 606 via a second network entity (satellite 636). The second network entity (satellite 636) can be a second satellite in the first NTN, and the first network entity (satellite 634) and the second network entity (satellite 636) can be connected via an inter-node link (e.g., ISL 638).

[0133] In some aspects, the network entity may be equipped with a core set of network functions, and in order to route communication signals through the network entity, the network entity may be configured to route the communication signals at 1610 via the core set of network functions of the network entity. The core set of network functions may include at least one of UPF, AMF, and SMF. For example, refer to... Figure 6AThe network entity (satellite 604) may be equipped with a core set of network functions. In order to route communication signals, the network entity (satellite 604) may be configured to route the communication signals through the core set of network functions of the network entity (satellite 604).

[0134] In some aspects, in order to receive communication signals for E2E communication, the network entity can be configured to receive the communication signal from the first UE via a sidelink interface at point 1608. In order to transmit the communication signal, the network entity can be configured to transmit the communication signal to the second UE via a sidelink interface at point 1614. For example, refer to... Figure 13 The network entity (satellite 1304) can be configured to receive the communication from the first UE 1302 via a side link interface and send the communication signal to the second UE 1306 via a side link interface.

[0135] In some respects, the network entity may be equipped with spaceborne relay functionality. To route communication signals through the network entity, the network entity may be configured to route the communication signals at point 1612 via its spaceborne relay functionality. For example, refer to... Figure 7A The network entity (satellite 704) may be equipped with a satellite relay function. Furthermore, the network entity (satellite 704) may be configured to route communication signals from UE 702 to UE 706 via this satellite relay function.

[0136] In some respects, this identification data can be received via an identification layer. For example, refer to... Figure 9 The identification data can be received via the identification layer (AL layer 910).

[0137] In some respects, this identification data may be based on one or more of the following: the IP address of the second UE, QoS flow, RB, LCH, RNTI, the location of the peer UE, or the identification layer header. For example, refer to Figure 9 The identification data in AL layer 910 may be based on one or more of the following: the IP address of the second UE 906, QoS flow, RB, LCH, RNTI, location of the peer UE, or the header of the identification layer (AL layer 910).

[0138] In some respects, this identification data can be based on the ID of the first UE. For example, refer to Figure 9 The identification data (in AL layer 910) can be based on the ID of the first UE 902.

[0139] In some aspects, the communication signal may also include first data on the AS layer. To receive the communication signal for E2E communication, the network entity may be configured to receive first data from a first UE via the UE-RAN air interface. To transmit the communication signal, the network entity may be configured to transmit the first data to a second UE via the UE-RAN air interface. For example, refer to... Figure 9 The communication signal may also include first data on AS layer 920. To receive the communication signal for E2E communication, the network entity (satellite 904) may be configured to receive the first data (data on AS layer 920) from the first UE 902 via the UE-RAN air interface (e.g., Uu air interface). To transmit the communication signal, the network entity (satellite 904) may be configured to transmit the first data to the second UE 906 via the UE-RAN air interface (e.g., Uu air interface).

[0140] In some respects, the AS layer may include one or more of the following: PHY layer, MAC layer, RLC layer, PDCP layer, or SDAP layer. For example, see reference... Figure 9 AS layer 920 may include one or more of the following: PHY layer 922, MAC layer 924, RLC layer 926, PDCP layer 928, or SDAP layer 930.

[0141] In some respects, this identifier layer can be higher than the AS layer in the layer set. For example, see reference. Figure 9 The identifier layer (AL layer 910) can be higher than the AS layer 920 in the layer set.

[0142] In some aspects, the communication signal may also include second data at the user layer, and the first transmission of the second data may include a first termination set at the first UE and the second UE. For example, refer to Figure 7B The communication signal may also include second data on the user layer (upper layer 780), and the first transmission of the second data includes a first termination set at the first UE 752 and the second UE 756.

[0143] In some aspects, the communication signal may also include third data on the E2E control layer for controlling the operation of the second UE. A second transmission of this third data may include a second termination set at both the first UE and the second UE. For example, refer to... Figure 10 The communication signal may also include third data on the E2E control layer (E2E RRC / NAS layer 1020) for controlling the operation of the second UE 1006. A second transmission of this third data may include a second termination set at both the first UE 1002 and the second UE 1006.

[0144] In some aspects, the communication signal may also include first data at the PHY layer, MAC layer, and RLC layer. To receive the communication signal for E2E communication, the network entity may be configured to receive first data from a first UE via the UE-RAN air interface. To transmit the communication signal, the network entity may be configured to transmit the first data to a second UE via the UE-RAN air interface. For example, refer to... Figure 9 The communication signal may also include first data on the PHY layer 922, MAC layer 924, and RLC layer 926. To receive the communication signal for E2E communication, the network entity (satellite 904) may be configured to receive the first data from the first UE 902 via the UE-RAN air interface (e.g., the Uu air interface). To transmit the communication signal, the network entity (satellite 904) may be configured to transmit the first data to the second UE 906 via the UE-RAN air interface (e.g., the Uu air interface).

[0145] In some respects, this identifier layer can be higher than the RLC layer in the layer set. For example, refer to Figure 12 The identifier layer (AL layer 1210) may be higher than the RLC layer 1208 in the layer set.

[0146] In some aspects, the communication signal may also include second data on the PDCP layer of the E2E user plane, and the first transmission of the second data may include a first termination set at the first UE and the second UE. For example, refer to Figure 11 The communication signal may also include second data on the PDCP layer 1112 of the E2E user plane. The first transmission of the second data may include a first termination set at the first UE 1102 and the second UE 1106.

[0147] In some respects, this second data can be transmitted via the UE-RAN air interface or the side link (PC5) interface. For example, refer to Figure 11 The second data (data in PDCP layer 1112) can be sent via the UE-RAN air interface (e.g., Uu air interface) or the side link (PC5) interface.

[0148] In some aspects, the communication signal may also include third data on the E2E control layer for controlling the operation of the second UE. A second transmission of this third data may include a second termination set at both the first UE and the second UE. For example, refer to... Figure 12 The communication signal may also include third data on the E2E control layer (E2E RRC / NAS layer 1220) for controlling the operation of the second UE 1206. The second transmission of the third data (data on the E2E RRC / NAS layer 1220) may include a second termination set at the first UE 1202 and the second UE 1206.

[0149] In some aspects, the network entity may be equipped with a set of radio access network functions, and in order to route communication signals through the network entity, the network entity may be configured to route the communication signals through the set of radio access network functions of the network entity. For example, refer to Figure 7A The network entity (satellite 704) may be equipped with a set of radio access network functions, and the network entity (satellite 704) may be configured to route the communication signal through the set of radio access network functions of the network entity (satellite 704).

[0150] In some aspects, the radio access network function set may include at least a portion of the functions of a spaceborne access network node. For example, refer to Figure 7A The set of radio access network functions in satellite 704 may include at least a portion of the functions of onboard access network nodes.

[0151] Figure 17 This is a flowchart 1700 illustrating a method for wireless communication at a first UE according to various aspects of this disclosure. The method can be performed by the first UE. The first UE can be UE 104, 350, 602, 652, 702, 752, 1302, 1402, or... Figure 19 The hardware implementation of the device 1904 provides an E2E communication architecture that enhances connectivity between UEs without relying on terrestrial networks or feeder links. This method minimizes latency and reduces load on feeder links, enabling communication between UEs even when feeder links to terrestrial networks are unavailable. Therefore, this method significantly improves the availability and reliability of wireless communication.

[0152] like Figure 17 As shown, at position 1702, the first UE can generate identification data to identify a second UE used for E2E communication. This second UE can be UE 104, 350, 606, 656, 706, 756, 1306, 1406, or... Figure 19 The hardware implementation of the device 1904. Figure 6A , Figure 6B , Figure 7A , Figure 7B , Figure 13 and Figure 14 Various aspects of the steps in flowchart 1700 are illustrated. For example, refer to... Figure 14 The first UE 1402 may generate identification data at 1410 to identify the second UE 1406 for E2E communication. In some respects, 1702 may be performed by the direct NTN communication component 198.

[0153] At point 1704, the first UE can send a communication signal including the identification data to a network entity for the network entity to route the communication signal to the second UE, thereby enabling E2E communication with the second UE. This communication signal can bypass the terrestrial-based feeder link. The network entity can be... Figure 1 The base station or base station component in the access network, or core network component (e.g., base station 102, 310, 1404; satellite 604, 654, 704, 754, 1304 or...). Figure 19 The network entity in the specific hardware implementation (1902). For example, refer to Figure 14 The first UE 1402 can send a communication signal including identification data to a network entity (base station 1404) at 1412, so that the network entity (base station 1404) can route the communication signal to the second UE 1406, thereby enabling E2E communication with the second UE 1406. This communication signal can bypass the terrestrial-based feeder link. In some aspects, 1704 can be performed by the direct NTN communication component 198.

[0154] Figure 18 This is a flowchart 1800 illustrating a method for wireless communication at a first UE according to various aspects of this disclosure. The method can be performed by the first UE. The first UE can be UE 104, 350, 602, 652, 702, 752, 1302, 1402, or... Figure 19 The hardware implementation of the device 1904 provides an E2E communication architecture that enhances connectivity between UEs without relying on terrestrial networks or feeder links. This method minimizes latency and reduces load on feeder links, enabling communication between UEs even when feeder links to terrestrial networks are unavailable. Therefore, this method significantly improves the availability and reliability of wireless communication.

[0155] like Figure 18 As shown, at position 1802, the first UE can generate identification data to identify a second UE used for E2E communication. This second UE can be UE 104, 350, 606, 656, 706, 756, 1306, 1406, or... Figure 19 The hardware implementation of the device 1904. Figure 6A , Figure 6B , Figure 7A , Figure 7B , Figure 13 and Figure 14 Various aspects of the steps in flowchart 1800 are illustrated. For example, refer to... Figure 14 The first UE 1402 may generate identification data at 1410 to identify the second UE 1406 for E2E communication. In some respects, 1802 may be performed by the direct NTN communication component 198.

[0156] At point 1804, the first UE can send a communication signal including the identification data to a network entity for the network entity to route the communication signal to the second UE, thereby enabling E2E communication with the second UE. This communication signal can bypass the terrestrial-based feeder link. The network entity can be... Figure 1 The base station or base station component in the access network, or core network component (e.g., base station 102, 310, 1404; satellite 604, 654, 704, 754, 1304 or...). Figure 19 The network entity in the specific hardware implementation (1902). For example, refer to Figure 14 The first UE 1402 can send a communication signal including identification data to a network entity (base station 1404) at 1412, so that the network entity (base station 1404) can route the communication signal to the second UE 1406, thereby enabling E2E communication with the second UE 1406. This communication signal can bypass the terrestrial-based feeder link. In some aspects, 1804 can be performed by the direct NTN communication component 198.

[0157] In some respects, this E2E communication can be direct NTN communication, and the network entity can be the first satellite in the first NTN. For example, see reference... Figure 6A The E2E communication can be direct NTN communication, and the network entity can be the first satellite (satellite 604) in the first NTN.

[0158] In some respects, this identification data can be sent via an identification layer. For example, refer to... Figure 9 The identification data can be sent via the identification layer (AL layer 910).

[0159] In some respects, at 1806, the identification data may be based on one or more of the following: the IP address of the second UE, QoS flow, RB, LCH, RNTI, location of the peer UE, identification layer header, or the ID of the first UE. For example, refer to Figure 9 The identification data in AL layer 910 may be based on one or more of the following: the IP address of the second UE 906, QoS flow, RB, LCH, RNTI, location of the peer UE, or the header of the identification layer (AL layer 910).

[0160] In some aspects, the communication signal may also include first data at the AS layer. To transmit the communication signal, the first UE can be configured to: at 1808, transmit the first data to the network entity via the UE-RAN air interface. For example, refer to... Figure 9The communication signal may also include first data on AS layer 920. In order to send the communication signal, the first UE 902 may be configured to send the first data (data in AS layer 920) to the network entity (satellite 904) via the UE-RAN air interface (e.g., Uu air interface).

[0161] In some respects, the AS layer may include one or more of the following: PHY layer, MAC layer, RLC layer, PDCP layer, or SDAP layer. For example, see reference... Figure 9 AS layer 920 may include one or more of the following: PHY layer 922, MAC layer 924, RLC layer 926, PDCP layer 928, or SDAP layer 930.

[0162] In some respects, this identifier layer can be higher than the AS layer in the layer set. For example, see reference. Figure 9 The identifier layer (AL layer 910) can be higher than the AS layer 920 in the layer set.

[0163] In some aspects, the communication signal may also include first data at the PHY layer, MAC layer, and RLC layer. To transmit the communication signal, the first UE can be configured to transmit the first data to the network entity via the UE-RAN air interface at 1808. For example, refer to... Figure 9 The communication signal may also include first data on the PHY layer 922, MAC layer 924, and RLC layer 926. In order to transmit the communication signal, the first UE 902 may be configured to transmit the first data (e.g., data in the PHY layer 922, MAC layer 924, and RLC layer 926) to the network entity (satellite 904) via the UE-RAN air interface (e.g., Uu air interface).

[0164] In some respects, this identifier layer can be higher than the RLC layer in the layer set. For example, refer to Figure 12 The identifier layer (AL layer 1210) may be higher than the RLC layer 1208 in the layer set.

[0165] Figure 19Figure 1900 illustrates an example of a hardware implementation for device 1904. Device 1904 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1904 may include a cellular baseband processor 1924 (also referred to as a modem) coupled to one or more transceivers 1922 (e.g., cellular RF transceivers). Cellular baseband processor 1924 may include on-chip memory 1924'. In some aspects, device 1904 may also include one or more Subscriber Identity Module (SIM) cards 1920 and an application processor 1906 coupled to a Secure Digital Card (SD) card 1908 and a screen 1910. Application processor 1906 may include on-chip memory 1906'. In some aspects, device 1904 may also include a Bluetooth module 1912, a WLAN module 1914, an SPS module 1916 (e.g., a GNSS module), one or more sensor modules 1918 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1926, a power source 1930, and / or a camera 1932. Bluetooth module 1912, WLAN module 1914, and SPS module 1916 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). Bluetooth module 1912, WLAN module 1914, and SPS module 1916 may include their own dedicated antennas and / or communicate using antenna 1980. Cellular baseband processor 1924 communicates with UE 104 and / or RU associated with the same network entity 1902 via transceiver 1922 through one or more antennas 1980. Cellular baseband processor 1924 and application processor 1906 may each include computer-readable media / memory 1924', 1906' respectively. An additional memory module 1926 may also be considered as computer-readable media / memory. Each computer-readable media / memory 1924', 1906', 1926 may be non-transitory. Cellular baseband processor 1924 and application processor 1906 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by cellular baseband processor 1924 / application processor 1906, the software causes cellular baseband processor 1924 / application processor 1906 to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by cellular baseband processor 1924 / application processor 1906 during software execution.Cellular baseband processor 1924 / application processor 1906 may be a component of UE 350 and may include memory 360 and / or at least one of TX processor 368, RX processor 356, and controller / processor 359. In one configuration, device 1904 may be a processor chip (modem and / or application) and may only include cellular baseband processor 1924 and / or application processor 1906, while in another configuration, device 1904 may be the entire UE (see, for example). Figure 3 The UE 350 includes an additional module for device 1904.

[0166] As discussed above, component 198 can be configured to: generate identification data identifying a second UE for E2E communication; and send a communication signal including the identification data to a network entity for the network entity to route the communication signal to the second UE, thereby enabling E2E communication with the second UE, wherein the communication signal bypasses a terrestrial-based feeder link. Component 198 can also be configured to perform combination. Figure 17 and Figure 18 The flowchart described and / or by Figure 14 Component 198 may be any aspect of the UE 1402's execution. Component 198 may be within the cellular baseband processor 1924, the application processor 1906, or both the cellular baseband processor 1924 and the application processor 1906. Component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, apparatus 1904 may include a variety of components configured for various functions. In one configuration, apparatus 1904 (and specifically cellular baseband processor 1924 and / or application processor 1906) includes: components for generating identification data identifying a second UE for E2E communication; and components for sending a communication signal including the identification data to a network entity for the network entity to route the communication signal to the second UE, thereby enabling the E2E communication with the second UE, wherein the communication signal bypasses a terrestrial-based feeder link. Apparatus 1904 may also include components for performing combined Figure 17 and Figure 18 The flowchart describes the aspects and / or are composed of Figure 14The component may be any aspect of the functions performed by UE 1402. This component may be a component 198 of device 1904 configured to perform the functions described therein. As described above, device 1904 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions described therein.

[0167] Figure 20 Figure 2000 illustrates an example of a hardware implementation for network entity 2002. Network entity 2002 may be a BS, a component of a BS, or implement BS functionality. Network entity 2002 may include at least one of CU 2010, DU 2030, or RU 2040. For example, depending on the layer functionality handled by component 199, network entity 2002 may include CU 2010; both CU 2010 and DU 2030; each of CU 2010, DU 2030, and RU 2040; DU 2030; both DU 2030 and RU 2040; or RU 2040. CU 2010 may include CU processor 2012. CU processor 2012 may include on-chip memory 2012'. In some aspects, CU 2010 may also include an additional memory module 2014 and a communication interface 2018. CU 2010 communicates with DU 2030 via a midhaul link (such as an F1 interface). DU 2030 may include a DU processor 2032. DU processor 2032 may include on-chip memory 2032'. In some aspects, DU 2030 may also include an additional memory module 2034 and a communication interface 2038. DU 2030 communicates with RU 2040 via a fronthaul link. RU 2040 may include an RU processor 2042. RU processor 2042 may include on-chip memory 2042'. In some aspects, RU 2040 may also include an additional memory module 2044, one or more transceivers 2046, an antenna 2080, and a communication interface 2048. RU 2040 communicates with UE 104. On-chip memories 2012', 2032', 2042' and additional memory modules 2014, 2034, 2044 may each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 2012, 2032, and 2042 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor while executing the software.

[0168] As discussed above, component 199 can be configured to: receive from a first UE a communication signal for E2E communication with a second UE, wherein the communication signal includes identification data for identifying the second UE for the E2E communication; route the communication signal through the network entity, wherein the communication signal bypasses a terrestrial-based feeder link; and transmit the communication signal to the second UE to enable the E2E communication between the first UE and the second UE. Component 199 can also be configured to perform combination. Figure 15 and Figure 16 The flowchart described and / or by Figure 14 The base station 1404 performs any aspect of the process. Component 199 may be located within one or more processors of one or more of CU 2010, DU 2030, and RU 2040. Component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 2002 may include a variety of components configured for various functions. In one configuration, network entity 2002 includes: components for receiving communication signals from a first UE for E2E communication with a second UE, wherein the communication signals include identification data for identifying the second UE for the E2E communication; components for routing the communication signals through the network entity, wherein the communication signals bypass a terrestrial-based feeder link; and components for transmitting the communication signals to the second UE to enable the E2E communication between the first UE and the second UE. Network entity 2002 may also include components for performing a combination Figure 15 and Figure 16 The flowchart describes the aspects and / or are composed of Figure 14 The component can be any of the aspects performed by the base station 1404 in the network entity. This component can be component 199 of the network entity 2002 configured to perform the functions described therein. As described above, the network entity 2002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component can be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions described therein.

[0169] This disclosure provides a method for wireless communication at a UE. The method may include: receiving from a first UE a communication signal for end-to-end (E2E) communication with a second UE, wherein the communication signal includes identification data for identifying the second UE for the E2E communication; routing the communication signal through a network entity, wherein the communication signal bypasses a terrestrial-based feeder link; and transmitting the communication signal to the second UE to achieve the E2E communication between the first UE and the second UE. This method provides an E2E communication architecture that enhances connectivity between UEs without relying on a terrestrial network or feeder link. The method minimizes latency and reduces load on the feeder link, and enables communication between UEs even when the feeder link to the terrestrial network is unavailable. Therefore, this method significantly improves the availability and reliability of wireless communication.

[0170] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0171] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements, where the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices via a set of devices. A device configured to "output" data (such as transmission, signaling, or messaging) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to "receive" data (such as transmission, signaling, or messaging) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims.Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims. Terms such as “module,” “mechanism,” “element,” and “device” cannot replace the term “component.” Therefore, no claim element will be understood as a component plus function unless the element is expressly stated using the phrase “component for…”.

[0172] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless otherwise stated otherwise.

[0173] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0174] Aspect 1 is a method for wireless communication at a network entity. The method may include: receiving from a first UE a communication signal for end-to-end (E2E) communication with a second UE, wherein the communication signal includes identification data for identifying the second UE for the direct NTN communication; routing the communication signal through the network entity, wherein the communication signal bypasses a terrestrial-based feeder link; and transmitting the communication signal to the second UE to enable the E2E communication between the first UE and the second UE.

[0175] Aspect 2 is the method according to aspect 1, wherein the E2E communication may be direct NTN communication, and the network entity may be a first satellite in a first NTN.

[0176] Aspect 3 is the method according to aspect 2, wherein receiving the communication signal from the first UE may include: receiving identification data for identifying at least one of the first UE and the second UE, and sending the communication signal to the second UE may include: sending the identification data for identifying at least one of the first UE and the second UE.

[0177] Aspect 4 is the method according to Aspect 2, wherein the network entity may be a first network entity, and sending the communication signal may include: sending the communication signal to the second UE via a second network entity. The second network entity may be a second satellite in the first NTN, and the first network entity and the second network entity may be connected via an inter-node link.

[0178] Aspect 5 is the method according to any one of Aspects 3 to 4, wherein the network entity may be equipped with a core network function set, and routing the communication signals through the network entity may include: routing the communication signals through the core network function set of the network entity. The core network function set may include at least one of UPF, AMF, and SMF.

[0179] Aspect 6 is a method according to any one of Aspects 2 to 5, wherein receiving the communication signal for the E2E communication may include: receiving the communication signal from the first UE via a side link interface, and wherein sending the communication signal may include: sending the communication signal to the second UE via the side link interface.

[0180] Aspect 7 is the method according to any one of Aspects 2 to 5, wherein the network entity may be equipped with a spaceborne relay function, and wherein routing the communication signals through the network entity may include: routing the communication signals through the spaceborne relay function of the network entity.

[0181] Aspect 8 is the method according to aspect 7, wherein the identification data can be received via an identification layer.

[0182] Aspect 9 is the method according to aspect 8, wherein the identification data may be based on one or more of the following: the IP address of the second UE, QoS flow, RB, LCH, RNTI, location of the peer UE, header of the identification layer, or ID of the first UE.

[0183] Aspect 10 is the method according to any one of Aspects 7 to 9, wherein the communication signal may further include first data on the AS layer. Receiving the communication signal for the E2E communication may include: receiving the first data from the first UE via the UE-RAN air interface, and sending the communication signal may include: sending the first data to the second UE via the UE-RAN air interface.

[0184] Aspect 11 is the method according to aspect 10, wherein the AS layer may include one or more of the following: PHY layer, MAC layer, RLC layer, PDCP layer or SDAP layer.

[0185] Aspect 12 is the method according to any one of aspects 10 to 11, wherein the identifier layer may be higher than the AS layer in the layer set.

[0186] Aspect 13 is the method according to aspect 12, wherein the communication signal may further include second data on the user layer, and the first transmission of the second data may include a first termination set at the first UE and the second UE.

[0187] Aspect 14 is the method according to aspect 13, wherein the communication signal may further include third data on the E2E control layer for controlling the operation of the second UE, and the second transmission of the third data may include a second termination set at the first UE and the second UE.

[0188] Aspect 15 is a method according to any one of Aspects 7 to 14, wherein the communication signal may further include first data on the PHY layer, MAC layer and RLC layer, and receiving the communication signal for the direct NTN communication may include: receiving the first data from the first UE via the Uu air interface, and wherein sending the communication signal may include: sending the first data to the second UE via the UE-RAN air interface.

[0189] Aspect 16 is the method according to aspect 15, wherein the identifier layer may be higher than the RLC layer in the layer set.

[0190] Aspect 17 is the method according to aspect 16, wherein the communication signal may further include second data on the PDCP layer over E2EUP, and the first transmission of the second data may include a first termination set at the first UE and the second UE.

[0191] Aspect 18 is the method according to aspect 17, wherein the second data may be transmitted via the UE-RAN air interface or side link (PC5) interface.

[0192] Aspect 19 is the method according to any one of Aspects 17 to 18, wherein the communication signal may further include third data on the E2E control layer for controlling the operation of the second UE. A second transmission of the third data may include a second termination set at both the first UE and the second UE.

[0193] Aspect 20 is the method according to aspect 2, wherein the network entity may be equipped with a set of radio access network functions, and routing the communication signals through the network entity may include: routing the communication signals through the set of radio access network functions of the network entity.

[0194] Aspect 21 is the method according to aspect 20, wherein the radio access network function set may include at least a portion of the functions of the onboard access network node.

[0195] Aspect 22 is an apparatus for wireless communication at a UE, the apparatus comprising: a memory; and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to perform a method according to any one of aspects 1 to 21.

[0196] Aspect 23 is the apparatus according to aspect 22, the apparatus further comprising at least one of a transceiver or an antenna, the transceiver or the at least one of the antennas being coupled to the at least one processor and configured to receive the communication signal.

[0197] Aspect 24 is an apparatus for conducting wireless communication, the apparatus including components for implementing the method according to any one of aspects 1 to 21.

[0198] Aspect 25 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement the method according to any one of aspects 1 to 21.

[0199] Aspect 26 is a method for wireless communication at a UE. The method may include: generating identification data identifying a second UE for E2E communication; and sending a communication signal including the identification data to a network entity for the network entity to route the communication signal to the second UE, thereby enabling the E2E communication with the second UE. The communication signal may bypass a terrestrial-based feeder link.

[0200] Aspect 27 is the method according to aspect 26, wherein the E2E communication may be direct NTN communication, and the network entity may be a first satellite in a first NTN.

[0201] Aspect 28 is a method according to any one of Aspects 26 to 27, wherein the identification data may be transmitted via an identification layer, and the identification data may be based on one or more of the following: the IP address of the second UE, QoS flow, RB, LCH, RNTI, location of the peer UE, header of the identification layer, or ID of the first UE.

[0202] Aspect 29 is the method according to aspect 28, wherein the communication signal may further include first data on the AS layer, the identification layer may be higher than the AS layer in the layer set, and sending the communication signal may include: sending the first data to the network entity via the UE-RAN air interface.

[0203] Aspect 30 is the method according to aspect 29, wherein the AS layer may include one or more of the following: PHY layer, MAC layer, RLC layer, PDCP layer or SDAP layer.

[0204] Aspect 31 is the method according to any one of aspects 28 to 30, wherein the communication signal may further include first data on the PHY layer, MAC layer and RLC layer, and transmitting the communication signal may include: transmitting the first data to the network entity via the UE-RAN air interface.

[0205] Aspect 32 is the method according to aspect 31, wherein the identifier layer may be higher than the RLC layer in the layer set.

[0206] Aspect 33 is an apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to perform a method according to any one of aspects 26 to 32.

[0207] Aspect 34 is the apparatus according to aspect 33, the apparatus further comprising at least one of a transceiver or an antenna, the transceiver or the at least one of the antennas being coupled to the at least one processor and configured to transmit the communication signal.

[0208] Aspect 35 is an apparatus for conducting wireless communication, the apparatus including components for implementing the method according to any one of aspects 26 to 32.

[0209] Aspect 36 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement the method according to any one of aspects 26 to 32.

Claims

1. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and At least one processor, coupled to the memory, and configured, based at least in part on information stored in the memory, to: The first user equipment (UE) receives a communication signal for end-to-end (E2E) communication with a second UE, wherein the communication signal includes identification data for identifying the second UE for the E2E communication; The communication signals are routed through the network entity, wherein the communication signals bypass the ground-based power supply link; as well as The communication signal is sent to the second UE to realize the E2E communication between the first UE and the second UE.

2. The apparatus according to claim 1, further comprising: A transceiver coupled to the at least one processor, wherein, in order to receive the communication signal, the at least one processor is configured to receive the communication signal via the transceiver, and wherein the E2E communication is direct non-terrestrial network (NTN) communication, and the network entity is a first satellite in a first NTN.

3. The apparatus of claim 2, wherein, in order to receive the communication signal from the first UE, the at least one processor is configured to: receive identification data for identifying at least one of the first UE and the second UE, and in order to send the communication signal to the second UE, the at least one processor is configured to: send the identification data for identifying at least one of the first UE and the second UE.

4. The apparatus of claim 2, wherein the network entity is a first network entity, and wherein, in order to transmit the communication signal, the at least one processor is configured to: The communication signal is sent to the second UE via a second network entity, wherein the second network entity is a second satellite in the first NTN, and the first network entity and the second network entity are connected via an inter-node link.

5. The apparatus of claim 2, wherein the network entity is equipped with a core set of network functions, and wherein, in order to route the communication signals through the network entity, the at least one processor is configured to: The communication signals are routed through the core network function set of the network entity, wherein the core network function set includes at least one of User Plane Function (UPF), Access and Mobility Management Function (AMF), and Session Management Function (SMF).

6. The apparatus of claim 2, wherein, in order to receive the communication signal for the E2E communication, the at least one processor is configured to: The communication signal is received from the first UE via a sidelink interface, and wherein, in order to transmit the communication signal, the at least one processor is configured to: The communication signal is sent to the second UE via the side link interface.

7. The apparatus of claim 2, wherein the network entity is equipped with a spaceborne relay function, and wherein, in order to route the communication signals through the network entity, the at least one processor is configured to: The communication signals are routed through the onboard relay function of the network entity.

8. The apparatus of claim 7, wherein, in order to receive the communication signal, the at least one processor is configured to receive the identification data via an identification layer.

9. The apparatus of claim 8, wherein the identification data is based on one or more of the following: The Internet Protocol (IP) address of the second UE, Quality of Service (QoS) flow, Radio bearer (RB), Logical Channel (LCH) Radio Network Temporary Identifier (RNTI) The location of the peer UE The header of the identifier layer or The identifier (ID) of the first UE.

10. The apparatus of claim 8, wherein the communication signal further comprises first data on the access layer (AS), wherein, in order to receive the communication signal for the E2E communication, the at least one processor is configured to: The first data is received from the first UE via the UE-Radio Access Network (RAN) air interface, and In order to transmit the communication signal, the at least one processor is configured to: The first data is sent to the second UE via the UE-RAN air interface.

11. The apparatus of claim 10, wherein the AS layer comprises one or more of the following: Physical (PHY) layer Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer or Service Data Adaptation Protocol (SDAP) layer.

12. The apparatus of claim 10, wherein the identifier layer is higher than the AS layer in the layer set.

13. The apparatus of claim 12, wherein the communication signal further includes second data on the user layer, and wherein the first transmission of the second data includes a first termination set at the first UE and the second UE.

14. The apparatus of claim 12, wherein the communication signal further includes third data on the E2E control layer for controlling the operation of the second UE, wherein the second transmission of the third data includes a second termination set at the first UE and the second UE.

15. The apparatus of claim 8, wherein the communication signal further comprises first data on the physical (PHY) layer, the media access control (MAC) layer, and the radio link control (RLC) layer, wherein, in order to receive the communication signal for the E2E communication, the at least one processor is configured to: The first data is received from the first UE via the UE-Radio Access Network (RAN) air interface, and In order to transmit the communication signal, the at least one processor is configured to: The first data is sent to the second UE via the UE-RAN air interface.

16. The apparatus of claim 15, wherein the identifier layer is higher than the RLC layer in the layer set.

17. The apparatus of claim 16, wherein the communication signal further comprises second data on the Packet Data Convergence Protocol (PDCP) layer on the E2E user plane (UP), and wherein the first transmission of the second data includes a first termination set at the first UE and the second UE.

18. The apparatus of claim 17, wherein, in order to receive the communication signal, the at least one processor is configured to receive the second data via the UE-RAN air interface or side link (PC5) interface.

19. The apparatus of claim 17, wherein the communication signal further includes third data on the E2E control layer for controlling the operation of the second UE, wherein the second transmission of the third data includes a second termination set at the first UE and the second UE.

20. The apparatus of claim 2, wherein the network entity is equipped with a set of radio access network functions, and wherein, in order to route the communication signals through the network entity, the at least one processor is configured to: The communication signals are routed through the set of radio access network functions of the network entity.

21. The apparatus of claim 20, wherein the radio access network function set includes at least a portion of the functions of a spaceborne access network node.

22. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: Memory; and At least one processor, coupled to the memory, and configured, based at least in part on information stored in the memory, to: Generate identification data for the second UE used in end-to-end (E2E) communication; and A communication signal including the identification data is sent to a network entity so that the network entity can route the communication signal to the second UE, thereby enabling the E2E communication with the second UE, wherein the communication signal bypasses the ground-based power supply link.

23. The apparatus of claim 22, further comprising: A transceiver coupled to the at least one processor, wherein, in order to transmit the communication signal, the at least one processor is configured to transmit the communication signal via the transceiver, and wherein the E2E communication is direct non-terrestrial network (NTN) communication, and the network entity is a first satellite in a first NTN.

24. The apparatus of claim 23, wherein, in order to transmit the communication signal, the at least one processor is configured to: transmit the identification data via an identification layer, and wherein the identification data is based on one or more of the following: The Internet Protocol (IP) address of the second UE, Quality of Service (QoS) flow, Radio bearer (RB), Logical Channel (LCH) Radio Network Temporary Identifier (RNTI) The location of the peer UE The header of the identifier layer or The identifier (ID) of the first UE.

25. The apparatus of claim 24, wherein the communication signal further includes first data on an access layer (AS) layer, the identity layer being higher than the AS layer in the layer set, and wherein, in order to transmit the communication signal, the at least one processor is configured to: The first data is transmitted to the network entity via the UE-Radio Access Network (RAN) (UE-RAN) air interface.

26. The apparatus of claim 25, wherein the AS layer comprises one or more of the following: Physical (PHY) layer Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer or Service Data Adaptation Protocol (SDAP) layer.

27. The apparatus of claim 24, wherein the communication signal further comprises first data on the physical (PHY) layer, media access control (MAC) layer, and radio link control (RLC) layer, wherein, in order to transmit the communication signal, the at least one processor is configured to: The first data is transmitted to the network entity via the UE-Radio Access Network (RAN) (UE-RAN) air interface.

28. The apparatus of claim 27, wherein the identifier layer is higher than the RLC layer in the layer set.

29. A method for wireless communication at a network entity, the method comprising: The first user equipment (UE) receives a communication signal for end-to-end (E2E) communication with a second UE, wherein the communication signal includes identification data for identifying the second UE for the E2E communication; The communication signals are routed through the network entity, wherein the communication signals bypass the ground-based power supply link; as well as The communication signal is sent to the second UE to realize the E2E communication between the first UE and the second UE.

30. A method for wireless communication at a first user equipment (UE), the method comprising: Generate identification data for the second UE used in end-to-end (E2E) communication; as well as A communication signal including the identification data is sent to a network entity so that the network entity can route the communication signal to the second UE, thereby enabling the E2E communication with the second UE, wherein the communication signal bypasses the ground-based power supply link.

Images