Techniques for federating non-ground networks and aircraft relay networks

By implementing priority sorting configuration based on location, timing and number of non-terrestrial relay nodes in wireless communication devices, the priority sorting problem of wireless communication devices between non-terrestrial networks and aircraft relay nodes is solved, efficient communication resource management and power consumption are achieved.

CN119908095APending Publication Date: 2025-04-29QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280100112.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-09-23
Publication Date
2025-04-29

AI Technical Summary

Technical Problem

The prior art is difficult to effectively solve the priority ranking problem of wireless communication equipment between non-terrestrial networks and aircraft relay nodes, resulting in waste of communication resources and increased power consumption.

Method used

By implementing a priority sort configuration at the user equipment (UE), wireless communications are prioritized based on the number of locations, timings, or non-terrestrial relay nodes associated with the UE, ensuring communication with the most suitable non-terrestrial entity.

Benefits of technology

It realizes more efficient wireless communication resource management, reduces communication resource waste and power consumption, and improves communication efficiency and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119908095A_ABST
    Figure CN119908095A_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) can be configured to receive a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more non-terrestrial network (NTN) nodes. The UE can be configured to communicate one or more messages based on the prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] The following relates to wireless communications, including techniques for communicating with non-terrestrial network (NTN) nodes and aircraft nodes.

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0003] A method for wireless communication at a user equipment (UE) is described. The method may include receiving a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more non-terrestrial network (NTN) nodes. The method may also include communicating one or more messages based on the prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.

[0004] An apparatus for wireless communication at a UE is described. The apparatus may include: a processor; and a memory coupled to the processor and configured to receive a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more NTN nodes. The processor may also be configured to communicate one or more messages based on the prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.

[0005] Another apparatus for wireless communication at a UE is described. The apparatus may include means for receiving a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more NTN nodes. The apparatus may also include means for communicating one or more messages based on the prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.

[0006] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to receive a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more NTN nodes. The instructions may also be executable to communicate one or more messages based on the prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.

[0007] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: prioritizing wireless communications with the one or more non-terrestrial relay nodes or the one or more NTN nodes based on the number of non-terrestrial relay nodes according to the prioritization configuration, wherein the one or more messages may be communicated with a non-terrestrial relay node among the one or more non-terrestrial relay nodes or an NTN node among the one or more NTN nodes according to the prioritization.

[0008] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for prioritizing wireless communications with the one or more non-terrestrial relay nodes or the one or more NTN nodes based on a comparison between the number of non-terrestrial relay nodes and a threshold number.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: prioritizing wireless communications with the one or more non-terrestrial relay nodes based on the number of non-terrestrial relay nodes being greater than or equal to the threshold number; and prioritizing wireless communications with the one or more NTN nodes based on the number of non-terrestrial relay nodes being less than the threshold number.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of the threshold number via the control message, wherein the comparison may be based on the control message.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a distance metric between the UE and the number of non-terrestrial relay nodes within the target area of ​​the location associated with the UE, wherein the priority ranking may be based on the distance metric.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of the target area via the control message.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for monitoring synchronization signal blocks, discovery messages, or both from the one or more non-terrestrial relay nodes or the one or more NTN nodes based on the priority ranking configuration and the amount of non-terrestrial relay nodes, wherein communicating the one or more messages may be based on the monitoring.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving, via the control message, an indication of a model for estimating the number of non-terrestrial relay nodes within the target area for the location associated with the UE; and estimating the number of non-terrestrial relay nodes within the target area for the UE based on the model, wherein the one or more messages may be communicated based on the estimate.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: communicating the one or more messages with an NTN node among the one or more NTN nodes; performing a handover process from the NTN node to a non-terrestrial relay node among the one or more non-terrestrial relay nodes based on the number of non-terrestrial relay nodes; and communicating one or more additional messages with the non-terrestrial relay node based on the handover process.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: communicating the one or more messages includes receiving the one or more messages from the NTN node, the one or more messages including information associated with the non-ground relay node, the handover process may be performed based on the information, and the information includes an identifier associated with the non-ground relay node, communication parameters for communicating with the non-ground relay node, a heading associated with the non-ground relay node, a location associated with the non-ground relay node, or any combination thereof.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: communicating the one or more messages includes receiving the one or more messages from the non-terrestrial relay node, the one or more messages including information associated with the NTN node, the handover process may be performed based on the information, and the information includes an identifier associated with the NTN node, communication parameters for communicating with the NTN node, a location associated with the NTN node, or any combination thereof.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: communicating the one or more messages with a non-terrestrial relay node among the one or more non-terrestrial relay nodes; performing one or more measurements associated with the one or more messages communicated with the non-terrestrial relay node; performing a handover process from the non-terrestrial relay node to an NTN node among the one or more NTN nodes based on the one or more measurements and measurement thresholds; and communicating one or more additional messages with the NTN node based on the handover process.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a capability message indicating the UE's ability to perform wireless communications with the one or more non-terrestrial relay nodes and the one or more NTN nodes, wherein the control message indicating the priority sorting configuration may be received based on the capability message.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for communicating the one or more messages with an additional wireless device via a relay link provided by a non-terrestrial relay node of the one or more non-terrestrial relay nodes or an NTN node of the one or more NTN nodes.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more non-terrestrial relay nodes include an aircraft, an unmanned aerial vehicle (UAV), a high altitude platform (HAP) device, or any combination thereof, and the NTN node includes a satellite.

[0022] A method for wireless communication at a UE is described. The method may include performing an access procedure according to a prioritization configuration associated with the access procedure, the prioritization configuration indicating a priority list including respective priorities for a terrestrial network entity, a non-terrestrial relay node, and an NTN node. The method may also include communicating one or more messages with one of the terrestrial network entity, the non-terrestrial relay node, or the NTN node based on the access procedure.

[0023] An apparatus for wireless communication at a UE is described. The apparatus may include: a processor; and a memory coupled to the processor and configured to perform an access procedure according to a priority ranking configuration associated with the access procedure, the priority ranking configuration indicating a priority list including respective priorities for a terrestrial network entity, a non-terrestrial relay node, and an NTN node. The processor may also be configured to communicate one or more messages with one of the terrestrial network entity, the non-terrestrial relay node, or the NTN node based on the access procedure.

[0024] Another apparatus for wireless communication at a UE is described. The apparatus may include means for performing an access procedure according to a prioritization configuration associated with the access procedure, the prioritization configuration indicating a priority list including respective priorities for a terrestrial network entity, a non-terrestrial relay node, and an NTN node. The apparatus may also include means for communicating one or more messages with one of the terrestrial network entity, the non-terrestrial relay node, or the NTN node based on the access procedure.

[0025] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to perform an access procedure according to a priority ranking configuration associated with the access procedure, the priority ranking configuration indicating a priority list including respective priorities for a terrestrial network entity, a non-terrestrial relay node, and an NTN node. The instructions may also be executable to communicate one or more messages with one of the terrestrial network entity, the non-terrestrial relay node, or the NTN node based on the access procedure.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the priority sorting configuration indicates a first priority associated with a ground network entity, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for: prioritizing wireless communications with the ground network entity, the non-ground relay node, or the NTN node based on a comparison of the first priority, the second priority, and the third priority.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for monitoring synchronization signal blocks, discovery messages, or both from the terrestrial network entity, the non-terrestrial relay node, and the NTN node according to corresponding periodicities that may be based on the corresponding priorities indicated via the priority sorting configuration, wherein communicating the one or more messages may be based on the monitored synchronization signal blocks, discovery messages, or both.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the access process includes a discovery process, an initial access process, or both.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more non-terrestrial relay nodes include an aircraft, a UAV, a HAP device, or any combination thereof, and the NTN node includes a satellite.

[0030] A method for wireless communication at a network entity is described. The method may include outputting a control message indicating a prioritization configuration associated with prioritization of wireless communication at a UE, the prioritization configuration indicating relative priorities associated with at least a non-terrestrial relay node and an NTN node. The method may also include outputting or obtaining one or more messages via a relay link provided by a non-terrestrial relay node or an NTN node based on the prioritization configuration.

[0031] An apparatus for wireless communication at a network entity is described. The apparatus may include: a processor; and a memory coupled to the processor and configured to output a control message indicating a prioritization configuration associated with prioritization of wireless communication at a UE, the prioritization configuration indicating relative priorities associated with at least a non-terrestrial relay node and an NTN node. The processor may also be configured to output or obtain one or more messages via a relay link provided by a non-terrestrial relay node or an NTN node based on the prioritization configuration.

[0032] Another apparatus for wireless communication at a network entity is described. The apparatus may include means for outputting a control message indicating a prioritization configuration associated with prioritization of wireless communication at a UE, the prioritization configuration indicating relative priorities associated with at least a non-terrestrial relay node and an NTN node. The apparatus may also include means for outputting or obtaining one or more messages via a relay link provided by a non-terrestrial relay node or an NTN node based on the prioritization configuration.

[0033] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to output a control message indicating a prioritization configuration associated with prioritization of wireless communication at a UE, the prioritization configuration indicating relative priorities associated with at least a non-terrestrial relay node and an NTN node. The instructions may also be executable to output or obtain one or more messages via a relay link provided by a non-terrestrial relay node or an NTN node based on the prioritization configuration.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting an indication of a threshold number of non-terrestrial relay nodes via the control message, wherein outputting or obtaining the one or more messages may be based on the number of non-terrestrial relay nodes in the target area of ​​the UE and the threshold number of non-terrestrial relay nodes.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting an indication of the target area via the control message, wherein outputting or obtaining the one or more messages may be based on outputting the indication of the target area.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting, via the control message, an indication of a model for estimating the number of non-terrestrial relay nodes within the target area for the UE, wherein outputting or obtaining the one or more messages may be based on outputting the indication of the model.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the prioritization configuration indicates a fixed priority list including respective priorities associated with ground network entities, non-ground relay nodes, and NTN nodes, and outputting or obtaining the one or more messages may be based on the respective priorities.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more non-terrestrial relay nodes include an aircraft, a UAV, a HAP device, or any combination thereof, and the NTN node includes a satellite. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 An example of a wireless communication system supporting techniques for uniting an NTN and an aircraft relay network in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 2 An example of a network architecture supporting techniques for federating an NTN and an aircraft relay network in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Figure 3 An example of a wireless communication system supporting techniques for uniting an NTN and an aircraft relay network in accordance with one or more aspects of the present disclosure is illustrated.

[0042] Figure 4A and Figure 4B An example of a wireless communication system supporting techniques for uniting an NTN and an aircraft relay network in accordance with one or more aspects of the present disclosure is illustrated.

[0043] Figure 5A and Figure 5B An example of a wireless communication system supporting techniques for uniting an NTN and an aircraft relay network in accordance with one or more aspects of the present disclosure is illustrated.

[0044] Figure 6 An example of a process flow supporting techniques for federating an NTN and an aircraft relay network in accordance with one or more aspects of the present disclosure is illustrated.

[0045] Figure 7 and Figure 8 A block diagram of a device supporting techniques for federating an NTN and an aircraft relay network in accordance with one or more aspects of the present disclosure is shown.

[0046] Fig. 9 A block diagram of a communications manager supporting techniques for federating an NTN and an aircraft relay network is shown in accordance with one or more aspects of the present disclosure.

[0047] Fig.10 A diagram of a system including devices supporting techniques for federating NTNs and aircraft relay networks is shown in accordance with one or more aspects of the present disclosure.

[0048] Fig.11 and Fig.12A block diagram of a device supporting techniques for federating an NTN and an aircraft relay network in accordance with one or more aspects of the present disclosure is shown.

[0049] Fig.13 A block diagram of a communications manager supporting techniques for federating an NTN and an aircraft relay network is shown in accordance with one or more aspects of the present disclosure.

[0050] Fig.14 A diagram of a system including devices supporting techniques for federating NTNs and aircraft relay networks is shown in accordance with one or more aspects of the present disclosure.

[0051] Figures 15 to 18 A flow chart illustrating a method of supporting techniques for federating an NTN and an aircraft relay network in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0052] Some wireless communication systems may include non-ground entities, such as aircraft, UAV, Zeppelin airship, satellite, etc. In some cases, when a wireless device (e.g., UE) is outside the cellular coverage of a ground network entity (such as a base station or other network entity), the wireless device may be able to communicate with the non-ground entity. In such cases, the UE may be able to connect to the non-ground entity so that the non-ground entity can relay wireless communications to and from the UE. For the purposes of this disclosure, different types of non-ground entities may be referred to as non-ground relay nodes (e.g., aircraft, UAV, etc.) or NTN nodes (e.g., satellites). Non-ground relay nodes may act as UEs, integrated access and backhaul (IAB) nodes, network entities, or any combination thereof, and may be configured to relay communications between wireless devices (such as UEs and ground entities, other non-ground entities, or both). NTN nodes may include non-ground entities (such as satellites) that are associated with NTNs and communicatively coupled to ground entities (such as NTN gateways).

[0053] There may be trade-offs in communicating with different types of non-ground entities. For example, satellites can provide larger coverage areas (e.g., less frequent handovers). However, compared to the transmit power used to send messages to other types of devices (such as ground network entities and / or aircraft), the UE can utilize the increased transmit power (and therefore power consumption) when sending messages to the satellite. In addition, compared to communication with satellites (e.g., lower transmit power), communication with aircraft may be more cost-effective and energy-efficient, but may support a smaller coverage area, which may lead to more frequent handovers. In addition, aircraft density may vary depending on geographic location and time (e.g., fewer aircraft at night, fewer aircraft in rural areas relative to urban areas). Some technologies do not provide rules or conditions for controlling what type of non-ground entity the UE expects to communicate with. When there are no explicit rules or conditions for determining what type of wireless device to communicate with, the UE may attempt to perform communication with the aircraft when it is more suitable for the UE to perform communication with the satellite, or vice versa, which may result in an unsuccessful discovery process at the UE, waste of communication resources, and increased power consumption.

[0054] Thus, one or more aspects of the present disclosure relate to a prioritization configuration that can be used to define the relative priority of non-terrestrial entities. For example, one or more aspects of the present disclosure may enable a UE to be configured with a prioritization configuration for communicating with an aircraft, a satellite, or both. In some implementations, the prioritization configuration defines rules or conditions that can be used to determine whether the UE prioritizes wireless communications with an aircraft (e.g., a non-terrestrial relay node) over wireless communications with a satellite (e.g., an NTN node) (or vice versa). For example, in some cases, the prioritization configuration may enable the UE to perform initial access procedures and / or discovery procedures with satellites and aircraft according to different periodicities.

[0055] In some implementations, a prioritization configuration may define a fixed priority list including relative priorities for different types of wireless nodes (e.g., an example fixed priority list may prioritize ground nodes over aircraft, and aircraft over satellites). In such cases, the priority list may be signaled to the UE, or predefined at the UE. In other implementations, the prioritization configuration may include a variable priority based on the number of aircraft near the UE. For example, if the number of aircraft near the UE (e.g., within a target area or target radius) is greater than a certain threshold, the prioritization configuration may enable the UE to prioritize communications with aircraft over communications with satellites. In addition, the prioritization configuration may enable the UE to prioritize communications with satellites over communications with aircraft (e.g., if the number of aircraft in the target radius or target area relative to the UE is less than a threshold).

[0056] As will be described in further detail herein, the threshold number of aircraft may be configured at the UE, signaled to the UE (e.g., by a network entity), or both. In addition, the threshold number of aircraft may be determined or modified based on one or more parameters, including network conditions, latency / performance requirements at the UE (e.g., Quality of Service (QoS) metrics), etc.

[0057] The techniques described herein may enable a wireless device (e.g., a UE) to determine what types of non-terrestrial entities the wireless device may prioritize in different scenarios. Specifically, the prioritization configurations described herein may enable the wireless device to prioritize different types of non-terrestrial entities in different situations based on what types of non-terrestrial entities are expected to or more likely to exhibit better wireless communication performance with the wireless device. In this regard, the techniques described herein may enable the wireless device to establish wireless communications with different types of non-terrestrial entities in a manner that improves the efficiency and reliability of wireless communications between the wireless device and the corresponding non-terrestrial entities.

[0058] Aspects of the disclosure are first described in the context of wireless communication systems. Aspects of the disclosure are additionally described in the context of example process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams relating to techniques for joining NTNs and aircraft relay networks.

[0059] Figure 1 An example of a wireless communication system 100 supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0060] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communication according to one or more radio access technologies (RATs).

[0061] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0062] As described herein, a node, which may be referred to as a node, a network node, a network entity 105, or a wireless node, may be a base station 140 (e.g., any base station 140 described herein), a UE 115 (e.g., any UE 115 described herein), a network controller, an apparatus, a device, a computing system, one or more components, and / or another suitable processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE 115. As another example, the network node may be a network entity 105 or a base station 140. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE 115, the second network node may be a base station 140, and the third network node may be a UE 115. In another aspect of this example, the first network node may be a UE 115, the second network node may be a base station 140, and the third network node may be a base station 140. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE 115, base station 140, devices, equipment, computing systems, etc. may include disclosure of UE 115, base station 140, devices, equipment, computing systems, etc. as network nodes. For example, a disclosure that UE 115 is configured to receive information from base station 140 also discloses that the first network node is configured to receive information from the second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., UE 115 is configured to receive information from a base station also discloses that the first network node is configured to receive information from the second network node), a broader example of a narrower example may be interpreted inversely, but in a broad, open-ended manner. In the above example in which UE 115 is configured to receive information from base station 140 and also discloses that the first network node is configured to receive information from a second network node, the first network node may refer to a first UE 115 configured to receive information, a first base station 140, a first device, a first equipment, a first computing system, a first one or more components, a first processing entity, etc.; and the second network node may refer to a second UE 115, a second base station 140, a second device, a second equipment, a second computing system, a second one or more components, a second processing entity, etc.

[0063] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0064] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0065] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a gigabit NodeB (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home NodeB, a home eNodeB, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0066] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an IAB network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0067] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0068] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0069] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support paging message communications in an NTN as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may be additionally or alternatively performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0070] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0071] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0072] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive", or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0073] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0074] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0075] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, for which Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each radio frame having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0076] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0077] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0078] Physical channels may be multiplexed according to various techniques in order to communicate using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0079] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0080] A macro cell covers a relatively large geographic area (e.g., a radius of several thousand kilometers) and may allow unrestricted access by a UE 115 having a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 having a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0081] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0082] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0083] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Application examples of MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0084] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0085] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0086] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0087] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0089] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this article, the term "below 6 GHz" and the like can be broadly referred to as frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" and the like are used in this article, they can be broadly referred to as frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0090] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration combined with component carriers operating using licensed bands (e.g., LAA). Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0091] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0092] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0093] The network entity 105 or the UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communications with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 in different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmit directions. Transmissions in different beam directions may be used to identify (e.g., by a transmitting device (such as the network entity 105), or by a receiving device (such as the UE 115)) beam directions for later transmission or reception by the network entity 105.

[0094] Some signals, such as data signals associated with a particular receiving device, may be sent by network entity 105 in a single beam direction, e.g., a direction associated with a receiving device, such as UE 115. In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent in one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 in different directions and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0095] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or not precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent by network entity 105 in one or more directions, UE 115 may employ similar techniques to send signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals in a single direction (e.g., to send data to a receiving device).

[0096] A receiving device (e.g., UE 115) may try multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a network entity 105. For example, a receiving device may try multiple reception directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different reception configurations or reception directions. In some examples, a receiving device may use a single reception configuration to receive along a single beam direction (e.g., when receiving a data signal). The single reception configuration may be aligned on a beam direction determined based on listening according to different reception configuration directions (e.g., a beam direction determined to have the highest signal strength, the highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0097] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or packet data convergence protocol (PDCP) layer may be IP-based. The radio link control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. The medium access control (MAC) layer may perform priority handling and multiplexing of logical channels to transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports radio bearers of user plane data between the UE 115 and the network entity 105 or the core network 130. At the physical layer, transport channels may be mapped to physical channels.

[0098] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data through communication link 125. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0099] The wireless communication system 100 may support NTN communications between network nodes of the wireless communication system 100. For example, the wireless communication system 100 may be an example of an NTN that supports communications between NTN nodes and ground network nodes. For example, as described herein, the network entity 105 may refer to a ground communication device (such as a base station 140) or a non-ground communication device (such as a satellite 185, a balloon, a drone, a non-ground node 195, a high altitude platform (HAP) station, or another non-ground device). The NTN network entity 105 may be connected to the ground network entity 105 (e.g., communicate with the ground network entity) via a gateway 190. In some examples, the NTN network entity 105 may correspond to a first cell type (e.g., an NTN cell type), and the ground network entity 105 may correspond to a second cell type (e.g., a ground cell type) different from the first cell type.

[0100] In some examples, the NTN network entity 105 may provide coverage to areas where the ground network entity 105 may not be available. The channel corresponding to the NTN network entity 105 may be characterized by a strong line-of-sight condition because the signal provided by the NTN network entity 105 may be reflected at the sky (e.g., as opposed to the signal corresponding to the ground network entity 105 that may travel on the ground). The coverage area of ​​the beam radiated from the NTN network entity 105 may have relatively clear boundaries (e.g., compared to the ground network entity 105 beam boundaries), and the UE 115 may operate within a single beam service area (e.g., except in the case where the UE 115 is located at the boundary between two service areas). In some examples, the service area of ​​the beam corresponding to the NTN network entity 105 may be larger than the service area of ​​the beam corresponding to the ground network entity 105.

[0101] The NTN network entity 105, such as the satellite 185, may move over time and support various coverage scenarios. For example, the NTN network entity 105 may support a mobile cell or beam coverage scenario, where the cell coverage area or beam coverage area moves along with the satellite 185. Alternatively, the NTN network entity 105 may support a quasi-earth fixed cell or beam coverage scenario, where the cell coverage area of ​​the beam coverage area remains static for a period of time as the NTN network entity 105 moves through space.

[0102] Additionally or alternatively, the wireless communication system 100 may support one or more non-ground nodes 195. For the purposes of this disclosure, non-ground nodes 195 may include, but are not limited to, aircraft, UAVs, drones, HAPs, etc. For example, Figure 1 As shown, UE 115 may be communicatively coupled to satellite 185 (eg, NTN node), non-terrestrial node 195 , or both via one or more communication links 125 .

[0103] The network entity 105 may include a network entity communication manager 101 to manage communications between the network entity 105 and other devices in the wireless communication system 100. In a similar manner, the UE communication manager 102 may manage communications between the UE 115 and other devices in the wireless communication system 100.

[0104] In some aspects, the wireless communication system 100 may support a prioritization configuration for defining relative priorities of non-terrestrial entities. Specifically, the techniques described herein may enable a UE 115 of the wireless communication system 100 to be configured with a prioritization configuration that defines rules or conditions for determining whether the UE 115 desires to prioritize wireless communications with an aircraft (e.g., a non-terrestrial relay node) over wireless communications with a satellite (e.g., an NTN node) (or vice versa).

[0105] In some implementations, the prioritization configuration may define a fixed priority list that includes relative priorities for different types of wireless nodes (e.g., a fixed priority may prioritize ground nodes over aircraft, and aircraft over satellites). In such cases, the priority list may be signaled to the UE 115, or predefined at the UE 115. In other implementations, the prioritization configuration may include a variable priority based on the number of aircraft in the vicinity of the UE 115. For example, if the number of aircraft in the vicinity of the UE 115 is greater than a certain threshold, the prioritization configuration may cause the UE 115 to prioritize communications with aircraft over communications with satellites. Additionally, if the number of aircraft in the vicinity of the UE 115 is less than a threshold, the prioritization configuration may cause the UE 115 to prioritize communications with satellites over communications with aircraft.

[0106] The techniques described herein may enable a wireless device (e.g., UE 115) to determine what types of non-terrestrial entities the wireless device desires to prioritize in different scenarios. Specifically, the prioritization configurations described herein may enable the wireless device to prioritize different types of non-terrestrial entities in different situations based on what types of non-terrestrial entities desire or are more likely to exhibit better wireless communication performance with the wireless device. In this regard, the techniques described herein may enable the wireless device to establish wireless communications with different types of non-terrestrial entities in a manner that improves the efficiency and reliability of wireless communications between the wireless device and the corresponding non-terrestrial entities.

[0107] Figure 2An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with a core network 130-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served by multiple RUs 170-a simultaneously.

[0108] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0109] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to process user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0110] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

[0111] In some examples, lower layer functions may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, this configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0112] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0113] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

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

[0115] Figure 3 An example of a wireless communication system 300 supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 can implement aspects of the wireless communication system 100, the network architecture 200, or both. For example, the wireless communication system 300 can support a prioritization configuration that enables a wireless device to prioritize different types of non-ground entities, such as reference Figure 1 As described.

[0116] The wireless communication system 300 may include a UE 115-a, a network entity 105-a, one or more aircraft 305-a, 305-b, 305-c, and 305-d (e.g., non-terrestrial relay nodes), and one or more satellites 310-a, 310-b (e.g., NTN nodes). In this regard, the wireless communication system 300 may include an example of an NTN. The UE 115-a may communicate with a corresponding device (e.g., network entity 105-a, aircraft 305, satellite 310) using one or more communication links. For example, the UE 115-a may communicate with the network entity 105-a via a communication link 330-a, wherein the communication link 330-a may include an example of an access link (e.g., a Uu link). The communication link 330-a may include a bidirectional link, which may include both uplink communication and downlink communication. For example, UE 115-a may send an uplink transmission, such as an uplink control signal or an uplink data signal, to network entity 105-a via communication link 330-a, and network entity 105-a may send a downlink transmission, such as a downlink control signal or a downlink data signal, to UE 115-a via communication link 330-a.

[0117] Similarly, UE 115-a may be configured to establish a communication link with one or more of the aircraft 305, satellite 310, or both. In such cases, the communication link 330 (e.g., communication link 330-b, 330-c) between UE 115-a and aircraft 305, satellite 310, or both may be an example of a Uu link, a side link (e.g., a PC5 link), a relay link, an IAB backhaul link, or any combination thereof. In some cases, the type of entity with which UE 115-a is communicating (e.g., network entity 105-a, aircraft 305, satellite 310) may be transparent or non-transparent to UE 115-a. In addition, aircraft 305 and satellite 310 may be configured to communicate with each other. For example, some aircraft 305 are expected to support satellite-based communications and air-to-ground (ATG)-based communications.

[0118] In some aspects, the satellites 310 may be associated with one or more NTN gateways, which may be located on the ground or in the air (e.g., onboard, in space, etc.). For example, a first satellite 310-a may be associated with a ground-based NTN gateway, which may be communicatively coupled to a network entity 105-a. In this example, the NTN gateway may facilitate communications to and from the satellite 310-a via a feeder link between the NTN gateway and the satellite 310-a.

[0119] In this regard, the wireless communication system 300 may include an example of a heterogeneous network in which ground infrastructure (e.g., network entity 105-a) is complemented and supplemented by non-ground nodes (e.g., NTNs). As will be described in further detail herein, the NTNs may facilitate synchronization, scheduling, HARQ, and mobility within the wireless communication system 300.

[0120] In some aspects, the NTN (e.g., wireless communication system 300) may include different types of non-ground entities, such as UAVs, HAP stations or devices, aircraft 305, and satellites 310, such as low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, and geostationary orbit (GEO) satellites. The corresponding non-ground entities may operate at varying altitudes. For example, a UAV may operate at an altitude of approximately 100 meters, wherein a HAP may operate at an altitude between ten kilometers (km) and twenty kilometers, and an aircraft may operate at an altitude between nine kilometers and twelve kilometers. Similarly, a LEO satellite may operate at an altitude of 500km to 1200km, a MEO satellite may operate at an altitude of 5000km to 2500km, and a GEO satellite may operate at an altitude of 36,000km or more.

[0121] The varying altitudes at which the corresponding non-terrestrial nodes operate may result in varying sizes of coverage areas supported by the corresponding non-terrestrial nodes. For example, a UAV may operate at a lower altitude than a LEO satellite, and thus may support a smaller coverage area (e.g., a smaller cell) than a LEO satellite. Similarly, a LEO satellite may operate at a lower altitude than a GEO satellite, and thus may support a smaller coverage area (e.g., a smaller cell) than a GEO satellite.

[0122] The communication between UE 115-a and / or network entity 105-a and non-ground nodes (e.g., aircraft 305, satellite 310) may be referred to as ATG communication. ATG communication and network evolution may enable wireless communications to be relayed by non-ground nodes for non-cellular coverage areas. The wireless communication system 300 may exhibit coexistence between ATG and International Mobile Telecommunications (IMT) terrestrial networks, where non-ground nodes may exhibit large inter-site distances (ISDs) and coverage (e.g., 300 km).

[0123] In some implementations, non-ground nodes, such as commercial aircraft 305 and satellites 310, may be used to extend the coverage area of ​​the wireless communication system 300 that is not otherwise reachable via ground nodes, such as the network entity 105-a. In other words, when the UE 115-a is out of cellular coverage relative to the network entity 105-a, the UE 115-a may be able to communicate with the non-ground entity (e.g., aircraft 305, satellite 310). In such cases, the UE 115-a may be able to connect to the non-ground entity so that the non-ground entity can relay wireless communications to and from the UE 115-a. Such relay capabilities enabled by the non-ground entity may facilitate SoS message delivery and data communications (e.g., emergency communications) in non-cellular coverage areas and enable general cellular coverage. For example, in the event that UE 115-a is out of coverage of network entity 105-a, UE 115-a may be able to send a SoS message to aircraft 305, where the aircraft is configured to relay the SoS message to network entity 105-a.

[0124] However, communication with different types of non-terrestrial entities may be associated with corresponding trade-offs. For example, NTN nodes such as satellite 310 may provide a larger coverage area (e.g., less frequent handovers), but may increase the transmit power (and therefore power consumption) associated with messages sent from UE 115-a to satellite 310. In addition, the use of satellite 310 relays may require the manufacture and launch of additional satellites, which may be cost-prohibitive in some situations and locations. In addition, compared to communication with satellite 310 (e.g., lower transmit power), communication between UE 115-a and aircraft 305 may be more cost-effective and energy-efficient. However, compared to satellite 310, aircraft 305 may exhibit a smaller coverage area, which may result in more frequent handovers. In addition, aircraft density may vary depending on geographic location and time (e.g., fewer aircraft at night).

[0125] Some wireless communication systems do not provide rules or conditions that control what type of non-terrestrial entity a UE 115 desires to communicate with. When there are no explicit rules or conditions for determining what type of wireless device to communicate with, the UE 115 performs an unsuccessful discovery process, which may result in wasted communication resources and increased power consumption at the UE 115.

[0126] Thus, aspects of the present disclosure relate to techniques for a joint NTN and aircraft relay network that enable communication with both the NTN and the aircraft relay. Specifically, the techniques described herein relate to a prioritization configuration 335 for defining relative priorities of non-terrestrial entities. In other words, a UE 115-a may be configured with a prioritization configuration 335 that defines rules or conditions for determining whether a UE 115-a desires to prioritize wireless communications with an aircraft 305 (e.g., a non-terrestrial relay node) over wireless communications with a satellite 310 (e.g., an NTN node) (or vice versa).

[0127] According to the techniques described herein, the prioritization configuration 335 may enable the UE 115-a to prioritize different types of non-terrestrial nodes over other types of non-terrestrial nodes in different situations based on a variety of considerations or parameters. Parameters that may be considered when prioritizing different types of non-terrestrial nodes may include, but are not limited to: different priorities for different network connections (e.g., fixed priority, dynamic priority), satellite to aircraft handoffs (e.g., location-based triggering from satellite 310 to aircraft 305, RSRP-based handoff from aircraft 305 to satellite 310), different aircraft types (e.g., aircraft 305 operating as a gNB, IAB, or UE feature and different options for interface type), etc.

[0128] For example, with reference to the wireless communication system 300, the UE 115-a may be configured with a prioritization configuration 335 for prioritizing wireless connections with different types of wireless entities, such as ground entities (e.g., network entity 105-a), non-ground relay nodes (e.g., aircraft 305), NTN nodes (e.g., satellite 310), or any combination thereof. The prioritization configuration 335 may be pre-configured at the UE 115-a, signaled to the UE 115-a, or both. For example, the UE 115-a may receive control signaling (e.g., RRC, SIB, DCI, MAC-CE) from the network entity 105-a indicating the prioritization configuration 335.

[0129] In some cases, the UE 115-a may be configured with multiple prioritization configurations 335 and may select which prioritization to use or activate based on signaling from the network entity 105-a or other devices, based on certain network conditions, etc. In some aspects, each prioritization configuration 335 may define different rules or conditions for determining which wireless entities the UE 115-a desires to prioritize.

[0130] For example, in some implementations, the prioritization configuration 335 may include or define a fixed priority between different types of wireless devices. In other words, the prioritization configuration 335 may include or indicate a fixed priority list for initial access (or discovery), wherein the priority list indicates a relative priority metric or ranking between different types of wireless devices / nodes. In some cases, the prioritization configuration 335 associated with the fixed priority list may be indicated by the network entity 105-a (e.g., the last connected gNB), predefined by the network, or both when the UE 115-a is in the RRC connected state.

[0131] For example, the prioritization configuration 335 may include a fixed priority list that causes the UE 115-a to prioritize terrestrial nodes (e.g., network entity 105-a) over satellite 310, and to prioritize satellite 310 over aircraft 305 relay (e.g., priority order {terrestrial gNB, satellite, aircraft relay}). By way of another example, another prioritization configuration 335 may include a fixed priority list that causes the UE 115-a to prioritize terrestrial nodes (e.g., network entity 105-a) over aircraft 305 relay, and to prioritize aircraft 305 relay over satellite 310 (e.g., priority order {terrestrial gNB, aircraft relay, satellite}). The priority list associated with the fixed prioritization configuration 335 may be extended to different types of non-terrestrial nodes, such as UAVs, HAPs, etc. In addition, the priority list may include or define different priorities for different types or categories of non-terrestrial nodes, different types / categories of aircraft, different types / categories of satellites, etc.

[0132] In some aspects, the prioritization configuration 335 may cause the UE 115-a to attempt initial access and / or discovery with different types of nodes according to different periodicities or frequencies. For example, the UE 115-a may be configured with a prioritization configuration 335 associated with a fixed priority list that causes the UE 115-a to prioritize terrestrial nodes (e.g., network entity 105-a) over satellite 310 and satellite 310 over aircraft 305 relays (e.g., priority {terrestrial gNB, satellite, aircraft relay}). Figure 3 As shown, UE 115-a may attempt to perform initial access and / or discovery with corresponding devices according to different sets 315 of communication opportunities associated with different periodicities 320 based on a prioritization configuration 335. Specifically, the prioritization configuration 335 may cause UE 115-a to perform initial access / discovery with network entity 105 more frequently than satellite 310, and to perform initial access / discovery with satellite 310 more frequently than aircraft 305.

[0133] For example, the UE 115-a may attempt to perform initial access / discovery with the network entity 105 within a first set 315-a of communication opportunities associated with a first periodicity. Similarly, the UE 115-a may attempt to perform initial access / discovery with the satellite 310 within a second set 315-b of communication opportunities associated with a second periodicity 320-b, and may attempt to perform initial access / discovery with the satellite 310 within a third set 315-c of communication opportunities associated with a third periodicity 320-c. In other words, the UE 115-a may monitor SSBs, discovery messages, or both from respective devices according to different periodicities 320.

[0134] In this example, the first periodicity 320-a may be shorter (e.g., more frequent) than the second periodicity 320-b, indicating that the UE 115-a is configured to prioritize connections with the network entity 105 over connections with the satellite 310 in accordance with the prioritization configuration 335. Similarly, the second periodicity 320-b may be shorter (e.g., more frequent) than the third periodicity 320-c, indicating that the UE 115-a is configured to prioritize connections with the satellite 310 over connections with the aircraft 305 in accordance with the prioritization configuration 335. In other words, a higher priority node may be associated with a lower / shorter periodicity 320, where a lower priority node may be associated with a higher / longer periodicity 320.

[0135] In additional or alternative embodiments, some prioritization configurations 335 may include dynamic priorities, where the relative priorities of different types of wireless nodes may vary based on certain parameters or characteristics. The parameters or characteristics that the dynamic prioritization configurations 335 may consider may include, but are not limited to, the number of aircraft 305 and / or satellites 310 accessible to the UE 115-a, the distance between the UE 115-a and the aircraft 305 and / or satellite 310, the quality of communication between the UE 115-a and the aircraft 305 and / or satellite 310, or any combination thereof.

[0136] For example, in some cases, the prioritization configuration 335 may include a dynamic priority that enables the UE 115-a to prioritize different types of wireless entities based on a number (e.g., an average number, a median number, an estimated number) (N) of aircraft 305 within a target area 325 (e.g., a target cell radius, a target cell area) from the UE 115a. Figure 3 As shown, the number of aircraft 305 within target area 325 is three (e.g., aircraft 305-a, 305-b, and 305-c) because a fourth aircraft 305-d is located outside of target area 325 (and therefore may be unreachable by UE 115-a). In addition, dynamic prioritization configuration 335 may include rules or conditions that enable UE 115-a to determine different priorities for different types or categories of non-ground nodes, different types / categories of aircraft, different types / categories of satellites, etc.

[0137] In some implementations, the target area 325 may be defined or determined relative to different devices, geographic locations, etc. In other words, the center of the target area may be the UE 115 or other wireless device, a particular geographic location (e.g., a GNSS location area), etc. For example, the UE 115-a may be the center of the target area 325 such that the target area 325 moves along with the UE 115-a.

[0138] In some cases, the number of aircraft 305 (N) within the target area 325 may be a function of both location and time (e.g., N(location, time)). In other words, the number of aircraft 305 within the target area 325 for the UE 115-a may be based on the location of the UE 115-a and the timing associated with the UE 115-a (e.g., time of day). For example, the number of aircraft 305 within the target area 325 of the UE 115-a may be greater during the daytime than at night when fewer aircraft 305 are flying. As another example, the number of aircraft 305 within the target area 325 may be different when the UE 115-a is located near an airport or in a densely populated city compared to a rural area.

[0139] In some aspects, according to the dynamic prioritization configuration 335, the relative priority of different types of wireless nodes may be determined by comparing the number of aircraft 305 within the target area 325 to a threshold number. The threshold number may be preconfigured at the UE 115-a, signaled to the UE 115-a (e.g., via RRC signaling), or both. For example, if the number of aircraft 305 within the target area 325 is greater than or equal to the threshold number (e.g., N(location, time) ≥ Thresh), the prioritization configuration 335 may cause the UE 115-a to prioritize aircraft 305 relays over satellites 310 (e.g., prioritize non-terrestrial relay nodes over NTN nodes). Additionally, if the number of aircraft 305 within the target area 325 is less than the threshold number (e.g., N(location, time) < Thresh), the prioritization configuration 335 may cause the UE 115-a to prioritize satellites 310 over aircraft 305 relays (e.g., prioritize NTN nodes over non-terrestrial relay nodes). In such cases, the dynamic prioritization configuration 335 may additionally enable the UE 115 - a to prioritize ground nodes (eg, network entity 105 - a ) over aircraft 305 and satellites 310 , regardless of the number of nearby aircraft 305 .

[0140] In additional or alternative implementations, the dynamic prioritization configuration 335 may enable the UE 115-a to determine relative priorities between different types of nodes based on distances (e.g., distance metrics) between the UE 115-a and the aircraft 305. For example, the UE 115-a may calculate or estimate a distance metric between the UE 115-a and one or more aircraft 305 (e.g., aircraft 305 within the target area 325), and may be configured to determine relative priorities of the aircraft 305 and the satellites 310 based on the distance metric. For example, the UE 115-a may be configured to prioritize the aircraft 305 over the satellites 310 if the average distance metric is less than or equal to a certain distance threshold, and to prioritize the satellites 310 over the aircraft 305 if the average distance metric is greater than the distance threshold.

[0141] In some aspects, the target area 325 (e.g., a target cell radius), the threshold number of aircraft, or both may be signaled to the UE 115-a, preconfigured at the UE 115-a, defined by the network, or any combination thereof. For example, in some aspects, the dynamic prioritization configuration 335, the target area 325, the threshold number, or any combination thereof may be indicated by the network entity 105-a (e.g., the last connected gNB) when the UE 115-a is in an RRC connected state.

[0142] As described herein, the number of aircraft 305 near UE 115-a (e.g., within target area 325) may vary based on time and location. For example, for the same location, the density of aircraft 305 may be reduced at night relative to daytime. Thus, in some aspects, UE 115-a may be configured with a model for estimating the number of aircraft 305 (e.g., non-ground relay nodes) within the target area. For example, UE 115-a may receive control signaling from network entity 105-a, wherein the control signaling indicates a dynamic priority sorting configuration 335 and a model for estimating the number of aircraft 305 in target area 325. Thus, UE 115-a may be configured to estimate the number of nearby aircraft 305 according to the model, and the relative priority of different types of nodes may be determined based on the estimated number of aircraft 305.

[0143] In additional or alternative implementations, the network (e.g., network entity 105-a) may be configured to determine / estimate the number of aircraft 305 in target area 325, and may be configured to signal the determined / estimated number to UE 115-a. In some aspects, UE 115-a may be configured to monitor signals according to different periodicities 320 based on relative priorities determined according to dynamic prioritization configuration 335.

[0144] As described herein, the UE 115-a may be configured with multiple prioritization configurations 335. In such cases, the UE 115-a may switch between the prioritization configurations 335 based on explicit signaling or based on satisfying certain parameters / conditions. For example, if the distance between the UE 115-a and a current GNSS location associated with the UE 115-a (e.g., the GNSS location of the UE 115-a when attempting to perform a search) and an original GNSS location (e.g., the original GNSS location of the UE 115-a when the UE 115-a received the configuration) is greater than a certain distance threshold, the UE 115-a may be configured to fall back to a fixed prioritization configuration 335 associated with a fixed or default priority list.

[0145] In some aspects, the UE 115-a may be configured to establish wireless communications with respective wireless devices (e.g., the network entity 105-a, the aircraft 305, the satellite 310) in accordance with the relative priority order determined according to the prioritization configuration 335. For example, where the prioritization configuration 335 causes the UE 115-a to prioritize the aircraft 305 over the satellite 310, the UE 115-a may be configured to monitor for signals (e.g., SSB, discovery messages) from the aircraft 305. Similarly, where the prioritization configuration 335 causes the UE 115-a to prioritize the satellite 310 over the aircraft 305, the UE 115-a may be configured to monitor for signals (e.g., SSB, discovery messages) from the satellite 310.

[0146] Subsequently, after establishing wireless communication with aircraft 305 or satellite 310, UE 115-a may be configured to communicate message 340 with the corresponding device. Figure 3 As shown, UE 115-a may communicate one or more messages 340-a with aircraft 305-b (e.g., non-ground node). By another example, UE 115-a may communicate one or more messages 340-b with satellite 310-a. In some cases, aircraft 305 / satellite 310 may be configured to relay wireless communications to and from UE 115-a. For example, aircraft 305 may be used to relay communications from UE 115-a to network entity 105-a, and vice versa. In this regard, the ability of UE 115-a to communicate with aircraft 305 and satellite 310 may enable UE 115-a to maintain network connectivity, even when UE 115-a is originally out of coverage (e.g., unreachable) relative to ground nodes such as network entity 105-a.

[0147] In some cases, due to the movement of satellites 310 and aircraft 305 relative to UE 115-a, UE 115-a may desire to perform a handover procedure between two aircraft 305, between two satellites 310, between a satellite 310 and an aircraft 305, etc. Figure 4A and Figure 4B A handoff between satellite 310 and aircraft 305 is further shown and described.

[0148] Figure 4A and Figure 4B Examples of wireless communication systems 400-a, 400-b that support techniques for joint NTN and aircraft relay networks according to one or more aspects of the present disclosure are illustrated. In some examples, aspects of wireless communication systems 400-a, 400-b may implement aspects of wireless communication system 100, network architecture 200, wireless communication system 300, or any combination thereof, or be implemented by these aspects. Specifically, wireless communication systems 400-a and 400-b illustrate techniques for UE 115 to perform handover procedures from satellite to aircraft and from aircraft to satellite, respectively.

[0149] In some aspects, the techniques described herein may utilize location-based triggering to perform a handover from satellite 410 to aircraft 405 (e.g., a handover from an NTN node to a non-terrestrial relay node). Specifically, when there are one or more aircraft 405 supporting relay services flying over a remote area, a remote UE 115 with a satellite 410 connection may switch (or handover) from a satellite 410 connection to an aircraft 405 relay connection for data delivery. In such cases, UE 115 may desire to support communications with both NTN nodes (e.g., satellite 410) and non-terrestrial relay nodes (e.g., aircraft 405). Such capabilities may be reported to the network, such as through UE capability signaling.

[0150] For example, referring to the first wireless communication system 400-a, the UE 115-b may be in active communication with a satellite 410-a, where the satellite 410-a is associated with a cell coverage area 440-a, and where the satellite 410-a is moving according to a movement direction 435-a (e.g., moving from left to right across the page over time). In this example, the UE 115-b may determine that the aircraft 405-a has (or is about to) enter a target area 425-a associated with the UE 115-b, and may therefore perform a handoff procedure from the satellite 410-a to the aircraft 405-a. In some cases, satellite 410-a may obtain information associated with aircraft 405-a via gateway 430 (e.g., gateways 430-a, 430-b) or via a direct link between satellite 410-a and aircraft 405-a, where such information may be communicated to UE 115-b to facilitate handover decisions and facilitate communications between UE 115-b and aircraft 405-a.

[0151] Information associated with aircraft 405-a may include, but is not limited to, the trajectory 420-a of aircraft 405-a, the location of aircraft 405-a, the altitude of aircraft 405-a, communication parameters used to communicate with aircraft 405-a, etc., where the information may be communicated to UE 115-b (or identified by the UE) to facilitate the handover process.

[0152] For example, UE 115-b (or other device) may determine, based on the aircraft's position and trajectory 420-a, that aircraft 405-a is likely to be within target area 425-a for a sufficient time interval (e.g., a time interval greater than a threshold time interval), and may therefore perform a handoff procedure from satellite 410-a to aircraft 405-a. By way of another example, if UE 115-b determines that aircraft 405-a will only be within target area 425-a for a short time interval (as determined by the aircraft 405-a's position and trajectory 420-a), UE 115-b may avoid performing a handoff procedure from satellite 410-a to aircraft 405-a and may continue to communicate with satellite 410-a.

[0153] Additionally, in some cases, information associated with satellite 410-a, such as the location and / or direction of movement 435-a of satellite 410-a, may be used to facilitate handover decisions. Figure 4A As shown, UE 115-b may determine based on the position of satellite 410-a and / or moving direction 435-a that UE 115-b may soon be unable to communicate with satellite 410-a, and may therefore perform a handover process from satellite 410-a to aircraft 405-a.

[0154] Continuing with reference to the first wireless communication system 400-a, from the perspective of the UE 115-b, performing a handoff procedure from the satellite 410-a to the aircraft 405-a may achieve power savings at the UE 115-b because transmissions to the aircraft 405-a may be associated with a lower transmit power than transmissions to the satellite 410-a. The varying transmit power may be attributed to the fact that the aircraft 405-a may be at a much lower altitude (e.g., 10 km) than the altitude of the satellite 410-a (e.g., LEO satellites are at 600 km to 2000 km) and because the path loss for communications is proportional to the square of the distance between the devices.

[0155] Furthermore, the techniques described herein may utilize a signal quality based (e.g., RSRP based) trigger in the context of switching from aircraft 405 to satellite 410. In some cases, when layer 1 (L1) and / or layer 3 (L3) measurements of the UE-aircraft link are below a threshold, a UE 115 with aircraft 405 relay service may handover from the aircraft 405 relay connection to the satellite 410 connection for data delivery.

[0156] For example, referring to the second wireless communication system 400-b, the UE 115-c may be in active communication with the aircraft 405-b. In addition, the second wireless communication system 400-b may include a satellite 410-b associated with a cell coverage area 440-b, and wherein the satellite 410-b moves according to a moving direction 435-b (e.g., moving from right to left across the page over time). In this example, the UE 115-c may perform measurements associated with signals received from the aircraft 405-b (e.g., RSRP, RSRQ, CQI, SNR, SINR), and may determine that the corresponding measurements fail to meet a threshold (e.g., determine that RSRP < Thresh). In this example, the UE 115-c may perform a handover process from the aircraft 405-b to the satellite 410-b based on the failure of the measurements to meet the quality / performance threshold. Once again, the UE 115-c may desire to support both NTN and aircraft relay capabilities, as reported to the network.

[0157] In addition, as described herein, the aircraft 405-b may be configured to obtain information associated with the satellite 410-b (e.g., via an ATG-gNB link or an aircraft-satellite link) in order to facilitate a handover process from the aircraft 405-b to the satellite 410-b. The information associated with the satellite 410-b may include, but is not limited to, the altitude or trajectory of the satellite 410-b, the position of the satellite 410-b, the trajectory 420-b of the aircraft 405-b, communication parameters for communicating with the satellite 410-b, etc., which may be communicated to the UE 115-c (or identified by the UE) to facilitate the handover process.

[0158] In some implementations, the techniques described herein may additionally or alternatively utilize trajectory (e.g., direction of movement 435), altitude (e.g., LEO, MEO, GEO), and / or position information associated with satellite 410 when performing a handover process between satellite 410 and aircraft 405. For example, in Figure 4B In the context of , when performing a handover from an aircraft 405-b to a satellite 410-b, a UE 115-c may be configured to determine, based on the position and movement direction 435-b of the satellite 410-b, that the satellite 410-b may be able to communicate with the UE 115-c for a sufficient time interval (e.g., a time interval greater than a certain threshold time interval), and thus a handover process from the aircraft 405-b to the satellite 410-b may be performed. In other words, in the presence of multiple candidate satellites 410, the UE 115-c may be configured to evaluate which satellite 410 to handover to based on the movement direction 435 (e.g., trajectory, heading) and / or position of the corresponding satellite 410.

[0159] By way of another example, UE 115-a may perform a handover process from a first satellite 410 (e.g., Satellite 1) to an aircraft 405, and may subsequently perform a handover process from the aircraft 405 to a second satellite 410 (e.g., Satellite 2). In this example, the second satellite 410 (Satellite 2) may be different from the first satellite 410 (Satellite 1). In addition, UE 115 may determine to hand over to the second satellite 410 (rather than returning to the first satellite 410) based on the moving direction 435, altitude, and / or position of the corresponding satellite. Specifically, the orbital period (or speed of movement relative to the rotation of the earth) of the corresponding satellite 410 may be based on the altitude of the corresponding satellite 410. The higher the altitude of the satellite 410, the faster the corresponding satellite 410 moves (e.g., a LEO satellite moves faster than a MEO satellite, and a MEO satellite moves faster than a GEO satellite). Therefore, in this example, UE 115 may perform a handover process to the second satellite 410 based on the second satellite 410 being associated with a lower altitude and / or a higher rate of movement. Due to the lower altitude and / or slower rate of travel, the second satellite 410 may be able to communicate with the UE 115 for a longer time interval than the first satellite 410 .

[0160] Figure 5A and Figure 5BExamples of wireless communication systems 500-a, 500-b supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure are illustrated. In some examples, aspects of the wireless communication systems 500-a, 500-b may implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, the wireless communication systems 400-a, 400-b, or any combination thereof.

[0161] In some implementations, non-ground entities (e.g., aircraft) may be configured to operate as different types of wireless devices. Specifically, different types of aircraft may be configured to operate as a gNB (e.g., network entity 105, base station), IAB node, or UE 115. Aircraft operating as different types of wireless nodes (e.g., gNB, IAB node, UE 115) may affect different types of communication links between corresponding devices and handover procedures between corresponding devices.

[0162] For example, the first wireless communication system 500-a may include a UE 115-d, a network entity 105-b, a satellite 510-a, and an aircraft 505-a configured to operate as a gNB (e.g., network entity 105) or an IAB node. In this example, UE 115-d may communicate with aircraft 505-a and satellite 510-a (and network entity 105-b) via an access link or a Uu link. If aircraft 505-a operates as a gNB node, the interface between aircraft 505-a and satellite 510-a may be an Xn interface. In addition, if aircraft 505-a operates as an IAB node, the interface between aircraft 505-a and satellite 510-a may be an IAB backhaul interface. The IAB-MT feature of aircraft 505-a may receive some data from satellite 510-a via IAB backhaul. Additionally, the aircraft 505 - a may communicate with the network entity 105 - b via a relay or IAB backhaul link.

[0163] In some aspects, a switching process (e.g., a handover process) between respective wireless nodes at UE 115-d may utilize mobility and handover processes as described herein. Additionally, aircraft 505-a may relay communications between UE 115-d and network entity 105-b and / or satellite 510-a via respective communication links (e.g., aircraft-to-satellite links or ATG-gNB links).

[0164] In addition, the second wireless communication system 500-b may include a UE 115-e, a network entity 105-c, a satellite 510-b, and an aircraft 505-b configured to operate as a UE 115 node. In this example, the UE 115-e may communicate with the aircraft 505-b and the satellite 510-b via a PC5 (e.g., a side link) and a Uu link, respectively. Figure 5B As shown, the interface between the aircraft 505-b and the satellite 510-b can be a Uu interface. Similarly, the interface between the aircraft 505-b and the network entity 105-c can be a Uu or relay interface. In the context of the second wireless communication system 500-b, the switching process (e.g., handover process) between the corresponding wireless nodes at the UE 115-e can be from Uu to sidelink relay, or vice versa. Additionally, the aircraft 505-b can relay communications between the UE 115-e and the network entity 105-b and / or the satellite 510-b via corresponding communication links (e.g., aircraft to satellite links or ATG-gNB links).

[0165] Figure 6 An example of a process flow 600 for supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 600 may implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, the wireless communication system 300, the wireless communication devices 400-a, 400-b, the wireless communication systems 500-a, 500-b, or any combination thereof. For example, the process flow 500 illustrates that a UE 115-f receives a priority ranking configuration for determining relative priorities between non-ground entities, such as reference Figure 1 - Figure 5 described.

[0166] In some cases, process flow 600 may include UE 115-F, network entity 605, aircraft 610 (e.g., non-terrestrial relay node), and satellite 615 (e.g., NTN node), which may be examples of corresponding devices as described herein. Figure 6 The UE 115-b, network entity 605, aircraft 610, and satellite 615 illustrated in the example may include the following: Figure 3 105 -a, an example of a UE 115-a, a network entity 105-a, an aircraft 305, and a satellite 310 are illustrated in FIG. In some examples, the satellite 615 may be used as a bent pipe / transparent satellite 615, which is configured to relay communications between the UE 115-f and the network entity 605. Similarly, the aircraft 610 may be configured to relay wireless communications to and from the UE 115-f.

[0167] In some examples, the operations illustrated in process flow 600 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software or firmware), or any combination thereof. The following alternative examples may be implemented in which some of the steps are performed in an order different from that described or not performed at all. In some cases, the steps may include additional features not mentioned below, or additional steps may be added.

[0168] At 620, UE 115-f may output (e.g., send) capability information (e.g., a capability message) to network entity 605, the capability information indicating the ability of UE 115-f to perform wireless communications with both non-terrestrial relay nodes (e.g., aircraft 610) and NTN nodes (e.g., satellite 615).

[0169] At 625, the network entity 605 may output (e.g., send) a control signal (e.g., RRC, DSI, SIB, MAC-CE, etc.) to the UE 115-f, which indicates one or more prioritization configurations for prioritizing wireless communications / connections between ground nodes (e.g., network entity 605), non-ground relay nodes (e.g., aircraft 610), NTN nodes (e.g., satellite 615), or any combination thereof. Each respective prioritization configuration may include rules or conditions for determining whether the UE 115-f desires to prioritize what type of wireless nodes in a given situation. In some cases, the network entity 605 may output the control signal based on the capability information received at 620.

[0170] As described herein, a prioritization configuration may include a fixed prioritization configuration and / or a dynamic prioritization configuration. A fixed prioritization configuration may define or include a priority list (e.g., a fixed priority list) that includes relative priorities of terrestrial network entities, non-terrestrial relay nodes, and non-terrestrial network nodes. For example, a fixed prioritization configuration may cause a UE 115-f to prioritize a network entity 605 over a satellite 615, and a satellite 615 over an aircraft 610 (e.g., the relative priorities associated with the respective devices). In such cases, a UE 115-f may be configured to prioritize different types of wireless devices over other types of wireless devices based on a comparison of the relative priorities indicated via the priority list.

[0171] In addition, some prioritization configurations may include dynamic prioritization configurations in which the relative priorities of different types of wireless nodes may vary based on certain parameters or characteristics. The parameters or characteristics that may be considered by the dynamic prioritization configuration may include, but are not limited to, the number of aircraft 610 and / or satellites 615 accessible to the UE 115-f, the distance between the UE 115-f and the aircraft 610 and / or satellite 615, the quality of communication between the UE 115-f and the aircraft 610 and / or satellite 615, or any combination thereof.

[0172] In some implementations, the control signaling may indicate various parameters or characteristics associated with the prioritization configuration. Other parameters that may be indicated via the control signaling may include, but are not limited to, a target area associated with the UE 115-f (e.g., Figure 3 ), a threshold number of aircraft 610 for evaluating relative priority, a model for estimating the number of aircraft 610 near UE 115 - f, and the like.

[0173] At 630, the UE 115-f, the network entity 605, or both may determine or estimate the number of aircraft 610 within the target area for the UE 115-f. The UE 115-f and / or the network entity 605 may perform the determination / estimation at 630 based on the capability information at 620, the control signal at 625, or both. For example, the UE 115-f may estimate the number of aircraft 610 within the target area for the UE 115-f according to a model received via the control signal.

[0174] At 635, the UE 115-f, the network entity 605, or both may determine relative priorities for different types of wireless nodes based on the prioritization configuration. In this regard, the UE 115-f, the network entity 605, or both may determine the relative priorities based on the capability information at 620, the control signal at 625, the estimated number of aircraft 610 within the target area at 630, or any combination thereof.

[0175] For example, in the case of a fixed priority sorting configuration, UE 115-f can determine the relative priority of different types of wireless nodes (e.g., terrestrial nodes, non-terrestrial relay nodes, NTN nodes) by comparing the priorities within the fixed priority lists corresponding to the corresponding nodes.

[0176] By way of another example, in the case of a dynamic prioritization configuration, the UE 115-f may determine the relative priorities of different types of wireless nodes by comparing an estimated number of aircraft 610 within a target area to a threshold number. For example, if the number of aircraft 610 within the target area is greater than or equal to the threshold number (e.g., N(location, time)≥Thresh), the prioritization configuration may cause the UE 115-f to prioritize aircraft 610 relays over satellites 615 (e.g., prioritize non-terrestrial relay nodes over NTN nodes). Additionally, if the number of aircraft 610 within the target area is less than the threshold number (e.g., N(location, time)<Thresh), the prioritization configuration may cause the UE 115-f to prioritize satellites 615 over aircraft 610 relays (e.g., prioritize NTN nodes over non-terrestrial relay nodes).

[0177] In some aspects, the threshold number of aircraft 610 may be signaled by the network entity 605, preconfigured at the UE 115-f, determined by the network, or any combination thereof. Furthermore, in some cases, the threshold number may be determined and / or modified based on certain parameters or conditions, such as traffic load, amount of noise, priority or quality of service (QoS) associated with communications performed at the UE 115-f, or any combination thereof.

[0178] In additional or alternative implementations, the dynamic prioritization configuration may enable the UE 115-f to determine relative priorities between different types of nodes based on distances (e.g., distance metrics) between the UE 115-f and the aircraft 610. For example, the UE 115-f may calculate or estimate distance metrics between the UE 115-f and one or more aircraft 610 (e.g., aircraft 610 within a target area), and may be configured to determine relative priorities for the aircraft 610 and the satellite 615 based on the distance metrics. For example, the UE 115-f may be configured to prioritize the aircraft 610 over the satellite 615 if the average distance metric is less than or equal to a certain distance threshold, and to prioritize the satellite 615 over the aircraft 610 if the average distance metric is greater than the distance threshold.

[0179] At 640, the UE 115-f may monitor a signal (e.g., SSB, discovery message, reference signal) from one of the respective wireless nodes based on the determined priority. For example, where the UE 115-f prioritizes wireless communication / connection with the aircraft 610 at 635 (according to a prioritization configuration), the UE 115-f may be configured to monitor SSB / discovery messages from the aircraft 610 in order to establish wireless communication with the aircraft 610. In this regard, the UE 115-f may perform monitoring at 640 based on sending capability information at 620, receiving control signals at 625, estimating the number of aircraft at 630, determining relative priorities at 635 (e.g., performing prioritization at 635), or any combination thereof.

[0180] At 645, UE 115-f may communicate one or more messages with the wireless node based on the prioritization configuration. Figure 6 As shown, the prioritization configuration may cause the UE 115-f to prioritize wireless communications with the aircraft 610 over wireless communications with the satellite 615, and may therefore communicate one or more messages with the aircraft 610 based on the prioritization (e.g., according to the prioritization configuration). In this regard, the UE 115-f may perform communications at 645 based on sending capability information at 620, receiving control signals at 625, estimating the number of aircraft at 630, determining relative priorities at 635 (e.g., performing prioritization at 635), monitoring signals from the aircraft 610 at 640, or any combination thereof.

[0181] In some implementations, the aircraft 610 may be configured to relay messages to or from the UE 115-f at 645. For example, the aircraft 610 may be configured to receive messages from the UE 115-f and relay / forward those messages to the network entity 605 and / or the aircraft 610. Similarly, in other cases, the aircraft 610 may be configured to receive messages from the network entity 605 and / or the satellite 615 and relay / forward those messages to the UE 115-f.

[0182] Although Figure 6 An example is illustrated in which UE 115-f prioritizes aircraft 610 over satellite 615, but this is for illustrative purposes only. For example, in other cases, at 635, the prioritization configuration may cause UE 115-f to prioritize satellite 615 over aircraft 610. In such cases, UE 115-f may be configured to perform communications with satellite 615 at 645.

[0183] In addition, the relative priority ranking of different types of wireless nodes may determine the relative order in which the UE 115-f attempts to establish a wireless connection. However, the UE 115-f may be configured to establish wireless communications with a lower priority node if the UE 115-f is unable to establish communications with a higher priority node. For example, at 635, the priority ranking configuration may cause the UE 115-f to prioritize the satellite 615 over the aircraft 610. In this example, the UE 115-f may be unable to establish communications with the satellite 615, and therefore may establish communications with the lower priority aircraft 610.

[0184] At 650, UE 115-f may perform measurements on signals (e.g., messages) received from aircraft 610. In some cases, L1 and / or L3 measurements performed on signals received from aircraft 610 may be used to make a handover decision. Specifically, L1 / L3 measurements may be used to trigger a handover process from aircraft 610 to satellite 615. For example, as described herein with respect to Figure 4B As described, the UE 115 - f may be configured to perform a handover procedure from the aircraft 610 to the satellite 615 if the L1 / L3 measurements fail to satisfy one or more thresholds (eg, if RSRP<Thresh).

[0185] At 655, the UE 115-f may receive information associated with the satellite 615 from the aircraft 610 to facilitate the handoff process from the aircraft 610 to the satellite 615. The information associated with the satellite 615 may include, but is not limited to, the position or altitude of the satellite 615, the heading or trajectory of the satellite 615, communication parameters for communicating with the satellite 615, or any combination thereof.

[0186] At 660, the UE 115-f may perform a handover procedure from the aircraft 610 to the satellite 615. The UE 115-f may perform the handover procedure based on performing communications at 625, performing measurements at 650, receiving information associated with the satellite at 655, or any combination thereof. For example, the UE 115-f may be configured to perform a handover procedure from the aircraft 610 to the satellite 615 if the L1 / L3 measurements fail to satisfy one or more thresholds (e.g., if RSRP < Thresh).

[0187] At 665, the UE 115-f may communicate one or more messages with the satellite 615. Specifically, the UE 115-f may communicate with the satellite 615 based on performing the handover procedure at 660. Additionally, the UE 115-f may communicate with the satellite 615 based on the information associated with the satellite 615 received at 655.

[0188] Process flow 600 illustrates a handover process from an aircraft 610 to a satellite 615. In additional or alternative implementations, UE 115-f may be configured to perform a handover process from satellite 615 to aircraft 610. Figure 4A and Figure 4B As described in the first wireless communication system 400-a illustrated in FIG. 1 , the techniques described herein may utilize location-based triggering to perform a handover from a satellite 615 to an aircraft 610. Specifically, when there are one or more aircraft 610 supporting relay services flying over a remote area, a remote UE 115 having a satellite 615 connection may switch (handover) from the satellite 615 connection to the aircraft 610 relay connection for data delivery. In addition, in such cases, the satellite 615 may communicate information associated with the aircraft 610 to the UE 115-f in order to facilitate the handover process. The information associated with the aircraft 610 may include the location, altitude, and / or track / heading of the aircraft 610, communication parameters for communicating with the aircraft 610, and the like.

[0189] The techniques described herein may enable a wireless device (e.g., UE 115-f) to determine what types of non-terrestrial entities the wireless device desires to prioritize in different scenarios. Specifically, the prioritization configurations described herein may enable the UE 115-f to prioritize different types of non-terrestrial entities in different situations based on what types of non-terrestrial entities desire or are more likely to exhibit better wireless communication performance with the wireless device. In this regard, the techniques described herein may enable the UE 115-f to establish wireless communications with different types of non-terrestrial entities in a manner that improves the efficiency and reliability of wireless communications between the UE 115-f and the corresponding non-terrestrial entities.

[0190] Figure 7 A block diagram 700 of a device 705 supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0191] Receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for joint NTN and aircraft relay networks). The information may be communicated to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0192] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to the technology for joint NTN and aircraft relay networks). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0193] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the techniques for uniting NTNs and aircraft relay networks as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0194] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0195] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0196] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0197] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. For example, the communication manager 720 may be configured to or otherwise support components for receiving a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more non-terrestrial network (NTN) nodes. The communication manager 720 may be configured to or otherwise support components for communicating one or more messages based on the prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.

[0198] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communications at the UE. For example, the communication manager 720 may be configured to or otherwise support a component for performing an access procedure according to a priority ranking configuration associated with the access procedure, the priority ranking configuration indicating a priority list including respective priorities for a ground network entity, a non-ground relay node, and an NTN node. The communication manager 720 may be configured to or otherwise support a component for communicating one or more messages with one of the ground network entity, the non-ground relay node, or the NTN node based on the access procedure.

[0199] By including or configuring the communication manager 720 according to the examples as described herein, the device 705 (e.g., a processor controlling the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof or otherwise coupled thereto) may support techniques that enable a wireless device (e.g., a UE 115) to determine what types of non-terrestrial entities the wireless device desires to prioritize in different scenarios. Specifically, the prioritization configurations described herein may enable the wireless device to prioritize different types of non-terrestrial entities in different situations based on what types of non-terrestrial entities desire or are more likely to exhibit better wireless communication performance with the wireless device. In this regard, the techniques described herein may enable the wireless device to establish wireless communications with different types of non-terrestrial entities in a manner that improves the efficiency and reliability of wireless communications between the wireless device and the corresponding non-terrestrial entities.

[0200] Figure 8 A block diagram 800 of a device 805 supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0201] Receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for joint NTN and aircraft relay networks). The information may be communicated to other components of device 805. Receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0202] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to the technology for joint NTN and aircraft relay networks). In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0203] Device 805 or its various components may be examples of components for performing various aspects of the technology for uniting NTN and aircraft relay networks as described herein. For example, communication manager 820 may include control message reception manager 825, message delivery manager 830, access process manager 835, or any combination thereof. Communication manager 820 may be an example of various aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 810, transmitter 815, or both. For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated with receiver 810, transmitter 815, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0204] According to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. The control message reception manager 825 may be configured to or otherwise support components for receiving a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more non-terrestrial network (NTN) nodes. The message communication manager 830 may be configured to or otherwise support components for communicating one or more messages based on the prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.

[0205] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. The access procedure manager 835 may be configured to or otherwise support components for performing the access procedure according to a priority ranking configuration associated with the access procedure, the priority ranking configuration indicating a priority list including respective priorities for ground network entities, non-ground relay nodes, and NTN nodes. The message communication manager 830 may be configured to or otherwise support components for communicating one or more messages with one of the ground network entities, non-ground relay nodes, or NTN nodes based on the access procedure.

[0206] Fig. 9 A block diagram 900 of a communication manager 920 supporting techniques for uniting NTN and aircraft relay networks according to one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of the techniques for uniting NTN and aircraft relay networks as described herein. For example, the communication manager 920 may include a control message reception manager 925, a message communication manager 930, an access process manager 935, a priority ranking manager 940, a signal monitoring manager 945, a non-ground node manager 950, a handover process manager 955, a measurement manager 960, a capability message sending manager 965, a distance metric manager 970, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0207] According to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. The control message reception manager 925 may be configured to or otherwise support components for receiving a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more non-terrestrial network (NTN) nodes. The message communication manager 930 may be configured to or otherwise support components for communicating one or more messages based on the prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.

[0208] In some examples, the priority manager 940 may be configured as or otherwise support components for prioritizing wireless communications with one or more non-terrestrial relay nodes or one or more NTN nodes based on a number of non-terrestrial relay nodes according to a priority configuration, wherein one or more messages are communicated with a non-terrestrial relay node among the one or more non-terrestrial relay nodes or an NTN node among the one or more NTN nodes according to the priority ranking.

[0209] In some examples, prioritization manager 940 may be configured or otherwise support components for prioritizing wireless communications with one or more non-terrestrial relay nodes or one or more NTN nodes based on a comparison between a number of non-terrestrial relay nodes and a threshold number.

[0210] In some examples, the prioritization manager 940 may be configured or otherwise support components for prioritizing wireless communications with one or more non-terrestrial relay nodes based on the number of non-terrestrial relay nodes being greater than or equal to a threshold number. In some examples, the prioritization manager 940 may be configured or otherwise support components for prioritizing wireless communications with one or more NTN nodes based on the number of non-terrestrial relay nodes being less than a threshold number.

[0211] In some examples, control message reception manager 925 may be configured or otherwise support means for receiving an indication of the threshold quantity via a control message, wherein the comparison is based on the control message.

[0212] In some examples, distance metric manager 970 may be configured or otherwise support components for determining a distance metric between a UE and a number of non-terrestrial relay nodes within a target area associated with a location of the UE, wherein the priority ranking is based on the distance metric.

[0213] In some examples, control message reception manager 925 may be configured or otherwise support components for receiving an indication of a target area via a control message.

[0214] In some examples, the signal monitoring manager 945 may be configured to or otherwise support components for monitoring synchronization signal blocks (SSBs), discovery messages, or both from one or more non-terrestrial relay nodes or one or more NTN nodes based on a priority ranking configuration and a number of non-terrestrial relay nodes, where communication of one or more messages is based on the monitoring.

[0215] In some examples, control message reception manager 925 may be configured or otherwise support components for receiving, via a control message, an indication of a model for estimating the number of non-terrestrial relay nodes within a target area for a location associated with the UE. In some examples, non-terrestrial node manager 950 may be configured or otherwise support components for estimating the number of non-terrestrial relay nodes within a target area for the UE based on the model, wherein one or more messages are communicated based on the estimate.

[0216] In some examples, the message communication manager 930 may be configured or otherwise support components for communicating one or more messages with an NTN node in one or more NTN nodes. In some examples, the handover process manager 955 may be configured or otherwise support components for performing a handover process from an NTN node to a non-terrestrial relay node in one or more non-terrestrial relay nodes based on the number of non-terrestrial relay nodes. In some examples, the message communication manager 930 may be configured or otherwise support components for communicating one or more additional messages with a non-terrestrial relay node based on the handover process.

[0217] In some examples, communicating one or more messages includes receiving one or more messages from the NTN node. In some examples, the one or more messages include information associated with the non-terrestrial relay node. In some examples, the handover process is performed based on the information. In some examples, the information includes an identifier associated with the non-terrestrial relay node, a communication parameter for communicating with the non-terrestrial relay node, a heading associated with the non-terrestrial relay node, a location associated with the non-terrestrial relay node, or any combination thereof.

[0218] In some examples, communicating one or more messages includes receiving one or more messages from a non-terrestrial relay node. In some examples, the one or more messages include information associated with an NTN node. In some examples, the handover process is performed based on the information. In some examples, the information includes an identifier associated with the NTN node, a communication parameter for communicating with the NTN node, a location associated with the NTN node, or any combination thereof.

[0219] In some examples, the message communication manager 930 may be configured to or otherwise support components for communicating one or more messages with a non-terrestrial relay node in one or more non-terrestrial relay nodes. In some examples, the measurement manager 960 may be configured to or otherwise support components for performing one or more measurements associated with one or more messages communicated by the non-terrestrial relay node. In some examples, the handover process manager 955 may be configured to or otherwise support components for performing a handover process from a non-terrestrial relay node to an NTN node in one or more NTN nodes based on one or more measurements and measurement thresholds. In some examples, the message communication manager 930 may be configured to or otherwise support components for communicating one or more additional messages with the NTN node based on the handover process.

[0220] In some examples, the capability messaging manager 965 may be configured to or otherwise support components for sending a capability message indicating the UE's ability to perform wireless communications with one or more non-terrestrial relay nodes and one or more NTN nodes, wherein a control message indicating a priority sorting configuration is received based on the capability message.

[0221] In some examples, the message communication manager 930 may be configured to or otherwise support components for communicating one or more messages with an additional wireless device via a relay link provided by a non-terrestrial relay node in one or more non-terrestrial relay nodes or an NTN node in one or more NTN nodes. In some examples, the one or more non-terrestrial relay nodes include an aircraft, a UAV, a HAP device, or any combination thereof. In some examples, the NTN node includes a satellite.

[0222] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. The access procedure manager 935 may be configured to or otherwise support components for performing the access procedure according to a priority ranking configuration associated with the access procedure, the priority ranking configuration indicating a priority list including respective priorities for ground network entities, non-ground relay nodes, and NTN nodes. In some examples, the message communication manager 930 may be configured to or otherwise support components for communicating one or more messages with one of the ground network entities, non-ground relay nodes, or NTN nodes based on the access procedure.

[0223] In some examples, the prioritization configuration indicates a first priority associated with a ground network entity, and the prioritization manager 940 may be configured as or otherwise support components for prioritizing wireless communications with the ground network entity, non-ground relay node, or NTN node based on a comparison of the first priority, the second priority, and the third priority.

[0224] In some examples, the signal monitoring manager 945 may be configured to or otherwise support components for monitoring synchronization signal blocks, discovery messages, or both from terrestrial network entities, non-terrestrial relay nodes, and NTN nodes according to corresponding periodicities based on corresponding priorities indicated via a priority sorting configuration, wherein one or more messages are communicated based on the monitored SSBs, discovery messages, or both.

[0225] In some examples, the access process includes a discovery process, an initial access process, or both. In some examples, one or more non-terrestrial relay nodes include aircraft, UAVs, HAP devices, or any combination thereof. In some examples, the NTN node includes a satellite.

[0226] Fig.10A diagram of a system 1000 including a device 1005 supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein, or include components thereof. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1045).

[0227] I / O controller 1010 can manage input signals and output signals of device 1005. I / O controller 1010 can also manage peripheral devices that are not integrated into device 1005. In some cases, I / O controller 1010 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1010 may be implemented as part of a processor (such as processor 1040). In some cases, a user may interact with device 1005 via I / O controller 1010 or via hardware components controlled by I / O controller 1010.

[0228] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1015 may communicate bidirectionally via one or more antennas 1025, a wired or wireless link, as described herein. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. The transceiver 1015 or the transceiver 1015 and one or more antennas 1025 may be examples of transmitters 715, transmitters 815, receivers 710, receivers 810, or any combination thereof or components thereof as described herein.

[0229] The memory 1030 may include random access memory (RAM) and read-only memory (ROM). The memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed by the processor 1040, cause the device 1005 to perform various functions described herein. The code 1035 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1035 may not be directly executable by the processor 1040, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1030 may also contain, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0230] Processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to enable device 1005 to perform various functions (e.g., functions or tasks that support technologies for uniting NTN and aircraft relay networks). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform various functions described herein.

[0231] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a UE. For example, the communication manager 1020 may be configured to or otherwise support components for receiving a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more non-terrestrial network (NTN) nodes. The communication manager 1020 may be configured to or otherwise support components for communicating one or more messages based on the prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.

[0232] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the UE. For example, the communication manager 1020 may be configured to or otherwise support a component for performing an access procedure according to a priority ranking configuration associated with the access procedure, the priority ranking configuration indicating a priority list including respective priorities for a ground network entity, a non-ground relay node, and an NTN node. The communication manager 1020 may be configured to or otherwise support a component for communicating one or more messages with one of the ground network entity, the non-ground relay node, or the NTN node based on the access procedure.

[0233] By including or configuring a communication manager 1020 according to examples as described herein, the device 1005 may support techniques that enable a wireless device (e.g., UE 115) to determine what types of non-ground entities the wireless device desires to prioritize in different scenarios. Specifically, the prioritization configurations described herein may enable the wireless device to prioritize different types of non-ground entities in different situations based on what types of non-ground entities desire or are more likely to exhibit better wireless communication performance with the wireless device. In this regard, the techniques described herein may enable the wireless device to establish wireless communications with different types of non-ground entities in a manner that improves the efficiency and reliability of wireless communications between the wireless device and the corresponding non-ground entities.

[0234] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions executable by the processor 1040 to cause the device 1005 to perform various aspects of the techniques for uniting NTNs and aircraft relay networks as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.

[0235] Fig.11 A block diagram 1100 of a device 1105 supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0236] The receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0237] The transmitter 1115 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0238] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the techniques for uniting NTNs and aircraft relay networks as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0239] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0240] Additionally or alternatively, in some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0241] In some examples, communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in conjunction with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0242] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. For example, the communication manager 1120 may be configured to or otherwise support a component for outputting a control message indicating a prioritization configuration associated with prioritization of wireless communications at a UE, the prioritization configuration indicating a relative priority associated with at least a non-terrestrial relay node and an NTN node. The communication manager 1120 may be configured to or otherwise support a component for outputting or obtaining one or more messages via a relay link provided by a non-terrestrial relay node or an NTN node based on the prioritization configuration.

[0243] By including or configuring the communication manager 1120 according to the examples as described herein, the device 1105 (e.g., a processor controlling the receiver 1110, the transmitter 1115, the communication manager 1120, or a combination thereof or otherwise coupled thereto) may support techniques that enable a wireless device (e.g., a UE 115) to determine what types of non-ground entities the wireless device desires to prioritize in different scenarios. Specifically, the prioritization configurations described herein may enable the wireless device to prioritize different types of non-ground entities in different situations based on what types of non-ground entities desire or are more likely to exhibit better wireless communication performance with the wireless device. In this regard, the techniques described herein may enable the wireless device to establish wireless communications with different types of non-ground entities in a manner that improves the efficiency and reliability of wireless communications between the wireless device and the corresponding non-ground entities.

[0244] Fig.12 A block diagram 1200 of a device 1205 supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the device 1105 or network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0245] The receiver 1210 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 1205. In some examples, the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0246] The transmitter 1215 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0247] Device 1205 or its various components may be examples of components for performing various aspects of the technology for uniting NTN and aircraft relay networks as described herein. For example, communication manager 1220 may include control message output manager 1225, message delivery manager 1230, or any combination thereof. Communication manager 1220 may be an example of various aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0248] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The control message output manager 1225 may be configured to or otherwise support components for outputting a control message indicating a prioritization configuration associated with prioritization of wireless communications at a UE, the prioritization configuration indicating relative priorities associated with at least a non-terrestrial relay node and an NTN node. The message communication manager 1230 may be configured to or otherwise support components for outputting or obtaining one or more messages via a relay link provided by a non-terrestrial relay node or an NTN node based on the prioritization configuration.

[0249] Fig.13 A block diagram 1300 of a communication manager 1320 supporting techniques for uniting NTN and aircraft relay networks according to one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of components for performing various aspects of the techniques for uniting NTN and aircraft relay networks as described herein. For example, the communication manager 1320 may include a control message output manager 1325, a message delivery manager 1330, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0250] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. The control message output manager 1325 may be configured to or otherwise support components for outputting a control message indicating a prioritization configuration associated with prioritization of wireless communications at a UE, the prioritization configuration indicating relative priorities associated with at least a non-terrestrial relay node and an NTN node. The message communication manager 1330 may be configured to or otherwise support components for outputting or obtaining one or more messages via a relay link provided by a non-terrestrial relay node or an NTN node based on the prioritization configuration.

[0251] In some examples, the control message output manager 1325 may be configured as or otherwise support components for outputting an indication of a threshold number of non-terrestrial relay nodes via a control message, wherein outputting or obtaining one or more messages is based on the number of non-terrestrial relay nodes within a target area of ​​the UE and the threshold number of non-terrestrial relay nodes.

[0252] In some examples, control message output manager 1325 may be configured or otherwise support components for outputting an indication of a target area via a control message, where outputting or obtaining one or more messages is based on outputting the indication of the target area.

[0253] In some examples, the control message output manager 1325 may be configured as or otherwise support components for outputting, via a control message, an indication of a model for estimating the number of non-terrestrial relay nodes within a target area for a UE, wherein outputting or obtaining one or more messages is based on outputting the indication of the model.

[0254] In some examples, the prioritization configuration indicates a fixed priority list of corresponding priorities associated with ground network entities, non-ground relay nodes, and NTN nodes. In some examples, outputting or obtaining one or more messages is based on the corresponding priorities. In some examples, one or more non-ground relay nodes include aircraft, UAV, HAP devices, or any combination thereof. In some examples, NTN nodes include satellites.

[0255] Fig.14 A diagram of a system 1400 including a device 1405 supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of a device 1105, a device 1205, or a network entity 105 as described herein, or include components thereof. The device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1405 may include components that support output and acquisition of communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).

[0256] The transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1405 may include one or more antennas 1415, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1410 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1415, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1410 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1410, or the transceiver 1410 and one or more antennas 1415, or the transceiver 1410 and one or more antennas 1415 and one or more processors or memory components (e.g., processor 1435 or memory 1425 or both) may be included in a chip or chip assembly installed in the device 1405. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0257] Memory 1425 may include RAM and ROM. Memory 1425 may store computer-readable, computer-executable code 1430 including instructions that, when executed by processor 1435, cause device 1405 to perform various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by processor 1435, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1425 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0258] Processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1435. Processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) to enable device 1405 to perform various functions (e.g., functions or tasks that support technologies for joint NTN and aircraft relay networks). For example, device 1405 or a component of device 1405 may include processor 1435 and memory 1425 coupled to processor 1435, the processor 1435 and memory 1425 being configured to perform various functions described herein. Processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance) that may host functions for performing the functions of device 1405 (e.g., by executing code 1430). Processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within memory 1425). In some specific implementations, processor 1435 may be a component of a processing system. A processing system may refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs that may be passed to other systems or components (e.g., device 1405). For example, a processing system of device 1405 may refer to a system including various other components or subcomponents of device 1405 (such as processor 1435, or transceiver 1410, or communication manager 1420, or other components or combinations of components of device 1405). The processing system of device 1405 can be docked with other components of device 1405, and can process information (such as input or signal) received from other components or output information to other components. For example, a chip or modem of device 1405 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1405 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1405 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0259] In some examples, bus 1440 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1440 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1405, or communications performed between different components of device 1405 that may be co-located or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one component or divided between different components).

[0260] In some examples, communication manager 1420 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1420 may manage delivery of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1420 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other network entities 105. In some examples, communication manager 1420 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0261] According to examples as disclosed herein, the communication manager 1420 may support wireless communications at a network entity. For example, the communication manager 1420 may be configured to or otherwise support a component for outputting a control message indicating a prioritization configuration associated with prioritization of wireless communications at a UE, the prioritization configuration indicating a relative priority associated with at least a non-terrestrial relay node and an NTN node. The communication manager 1420 may be configured to or otherwise support a component for outputting or obtaining one or more messages via a relay link provided by a non-terrestrial relay node or an NTN node based on the prioritization configuration.

[0262] By including or configuring a communication manager 1420 according to examples as described herein, the device 1405 may support techniques that enable a wireless device (e.g., UE 115) to determine what types of non-ground entities the wireless device desires to prioritize in different scenarios. Specifically, the prioritization configurations described herein may enable the wireless device to prioritize different types of non-ground entities in different situations based on what types of non-ground entities desire or are more likely to exhibit better wireless communication performance with the wireless device. In this regard, the techniques described herein may enable the wireless device to establish wireless communications with different types of non-ground entities in a manner that improves the efficiency and reliability of wireless communications between the wireless device and the corresponding non-ground entities.

[0263] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, the processor 1435, the memory 1425, the code 1430, or any combination thereof. For example, the code 1430 may include instructions executable by the processor 1435 to cause the device 1405 to perform various aspects of the techniques for the joint NTN and aircraft relay network as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0264] Fig.15 A flow chart illustrating a method 1500 for supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0265] At 1505, the method may include receiving a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more NTN nodes. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The described control message reception manager 925 is executed.

[0266] At 1510, the method may include communicating one or more messages based on a priority ranking configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The described messaging manager 930 is executed.

[0267] Fig.16 A flowchart illustrating a method 1600 for supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0268] At 1605, the method may include receiving a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more NTN nodes. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig. 9 The described control message reception manager 925 is executed.

[0269] At 1610, the method may include prioritizing wireless communications with one or more non-terrestrial relay nodes or one or more NTN nodes based on the number of non-terrestrial relay nodes according to a prioritization configuration. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig. 9 The described prioritization manager 940 is executed.

[0270] At 1615, the method may include communicating one or more messages based on a prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both, wherein the one or more messages are communicated with a non-terrestrial relay node of the one or more non-terrestrial relay nodes or an NTN node of the one or more NTN nodes according to the prioritization. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig. 9 The described messaging manager 930 is executed.

[0271] Fig.17 A flow chart illustrating a method 1700 for supporting techniques for a joint NTN and aircraft relay network according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0272] At 1705, the method may include performing the access procedure according to a priority ranking configuration associated with the access procedure, the priority ranking configuration indicating a priority list including respective priorities for terrestrial network entities, non-terrestrial relay nodes, and NTN nodes. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig. 9 The described access process manager 935 is executed.

[0273] At 1710, the method may include communicating one or more messages with one of a terrestrial network entity, a non-terrestrial relay node, or an NTN node based on the access procedure. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig. 9 The described messaging manager 930 is executed.

[0274] Fig.18 A flow chart illustrating a method 1800 for supporting techniques for uniting NTN and aircraft relay networks according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 6 as well as Figures 11 to 14 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0275] At 1805, the method may include outputting a control message indicating a prioritization configuration associated with prioritization of wireless communications at the UE, the prioritization configuration indicating relative priorities associated with at least the non-terrestrial relay node and the NTN node. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.13The described control message output manager 1325 is executed.

[0276] At 1810, the method may include outputting or obtaining one or more messages via a relay link provided by a non-terrestrial relay node or NTN node based on a priority ranking configuration. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.13 The described messaging manager 1330 is executed.

[0277] The following provides an overview of various aspects of the disclosure:

[0278] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a control message indicating a priority ranking configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more NTN nodes; and communicating one or more messages based at least in part on the priority ranking configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.

[0279] Aspect 2: According to the method of Aspect 1, the method also includes: according to the priority sorting configuration, prioritizing wireless communications with the one or more non-ground relay nodes or the one or more NTN nodes at least in part based on the number of non-ground relay nodes, wherein according to the priority sorting, the one or more messages are communicated with a non-ground relay node among the one or more non-ground relay nodes or an NTN node among the one or more NTN nodes.

[0280] Aspect 3: According to the method according to Aspect 2, the prioritization also includes: prioritizing wireless communications with the one or more non-ground relay nodes or the one or more NTN nodes based at least in part on a comparison between the number of non-ground relay nodes and a threshold number.

[0281] Aspect 4: According to the method described in Aspect 3, the priority sorting also includes: prioritizing wireless communications with the one or more non-ground relay nodes based on the number of non-ground relay nodes being greater than or equal to the threshold number; and prioritizing wireless communications with the one or more NTN nodes based on the number of non-ground relay nodes being less than the threshold number.

[0282] Aspect 5: The method according to any one of aspects 3 to 4, the method further comprising: receiving an indication of the threshold number via the control message, wherein the comparison is based at least in part on the control message.

[0283] Aspect 6: According to the method described in any one of Aspects 2 to 5, the method also includes: determining a distance metric between the UE and the number of non-ground relay nodes within the target area of ​​the location associated with the UE, wherein the priority sorting is at least partially based on the distance metric.

[0284] Aspect 7: The method according to aspect 6 further comprises: receiving an indication of the target area via the control message.

[0285] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method further includes: monitoring synchronization signal blocks, discovery messages, or both from the one or more non-terrestrial relay nodes or the one or more NTN nodes based at least in part on the priority sorting configuration and the number of non-terrestrial relay nodes, wherein conveying the one or more messages is based at least in part on the monitoring.

[0286] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: receiving, via the control message, an indication of a model for estimating the number of non-ground relay nodes within the target area of ​​the location associated with the UE; and estimating the number of non-ground relay nodes within the target area of ​​the UE based on the model, wherein the one or more messages are conveyed at least in part based on the estimate.

[0287] Aspect 10: According to the method described in any one of Aspects 1 to 9, the method further includes: communicating the one or more messages with an NTN node among the one or more NTN nodes; performing a handover process from the NTN node to a non-ground relay node among the one or more non-ground relay nodes based at least in part on the number of non-ground relay nodes; and communicating one or more additional messages with the non-ground relay node based at least in part on the handover process.

[0288] Aspect 11: A method according to Aspect 10, wherein conveying the one or more messages includes receiving the one or more messages from the NTN node, the one or more messages include information associated with the non-ground relay node, the handover process is performed at least in part based on the information, and the information includes an identifier associated with the non-ground relay node, communication parameters for communicating with the non-ground relay node, a heading associated with the non-ground relay node, a location associated with the non-ground relay node, or any combination thereof.

[0289] Aspect 12: The method according to aspect 10, wherein communicating the one or more messages comprises receiving the one or more messages from the NTN node.

[0290] Aspect 13: The method according to aspect 10, wherein the one or more messages include information associated with the non-terrestrial relay node.

[0291] Aspect 14: The method according to aspect 10, wherein the handover process is performed at least in part based on the information.

[0292] Aspect 15: A method according to Aspect 10, wherein the information includes an identifier associated with the non-ground relay node, communication parameters for communicating with the non-ground relay node, a heading associated with the non-ground relay node, a location associated with the non-ground relay node, or any combination thereof.

[0293] Aspect 16: According to the method described in any one of Aspects 1 to 15, the method also includes: communicating the one or more messages to a non-ground relay node among the one or more non-ground relay nodes; performing one or more measurements associated with the one or more messages communicated by the non-ground relay node; performing a handover process from the non-ground relay node to an NTN node among the one or more NTN nodes based at least in part on the one or more measurements and measurement thresholds; and communicating one or more additional messages to the NTN node based at least in part on the handover process.

[0294] Aspect 17: According to the method described in any one of Aspects 1 to 16, the method further includes: sending a capability message indicating the ability of the UE to perform wireless communications with the one or more non-terrestrial relay nodes and the one or more NTN nodes, wherein the control message indicating the priority sorting configuration is received at least in part based on the capability message.

[0295] Aspect 18: According to any one of Aspects 1 to 17, the method further includes: communicating the one or more messages with an additional wireless device via a relay link provided by a non-terrestrial relay node among the one or more non-terrestrial relay nodes or an NTN node among the one or more NTN nodes.

[0296] Aspect 19: The method according to any one of aspects 1 to 18, wherein the one or more non-terrestrial relay nodes include aircraft, UAVs, HAP devices, or any combination thereof, and the NTN node includes a satellite.

[0297] Aspect 20: The method according to any one of aspects 1 to 18, wherein the one or more non-terrestrial relay nodes include aircraft and the NTN node includes a satellite.

[0298] Aspect 21: The method according to any one of aspects 1 to 18, wherein the one or more non-terrestrial relay nodes include a UAV and the NTN node includes a satellite.

[0299] Aspect 22: The method according to any one of aspects 1 to 18, wherein the one or more non-terrestrial relay nodes include HAP devices and the NTN node includes a satellite.

[0300] Aspect 23: A method for performing wireless communications at a UE, the method comprising: performing an access procedure according to a priority sorting configuration associated with the access procedure, the priority sorting configuration indicating a priority list including corresponding priorities for a ground network entity, a non-ground relay node, and an NTN node; and communicating one or more messages with one of the ground network entity, the non-ground relay node, or the NTN node based at least in part on the access procedure.

[0301] Aspect 24: A method according to Aspect 23, wherein the priority sorting configuration indicates a first priority associated with a ground network entity, a second priority associated with a non-ground relay node, and a third priority associated with an NTN node, and the method further includes: prioritizing wireless communications with the ground network entity, the non-ground relay node, or the NTN node based at least in part on a comparison of the first priority, the second priority, and the third priority.

[0302] Aspect 25: According to the method described in any one of Aspects 23 to 24, the method further includes: monitoring synchronization signal blocks, discovery messages, or both from the ground network entity, the non-ground relay node, and the NTN node based on the corresponding periodicity of the corresponding priority indicated at least in part via the priority sorting configuration, wherein the communication of the one or more messages is at least in part based on the monitored synchronization signal blocks, discovery messages, or both.

[0303] Aspect 26: According to the method described in any one of Aspects 23 to 24, the method further includes: monitoring synchronization signal blocks from the ground network entity, the non-ground relay node and the NTN node based on the corresponding periodicity of the corresponding priority indicated at least in part based on the priority sorting configuration, wherein conveying the one or more messages is at least in part based on the monitored synchronization signal blocks.

[0304] Aspect 27: According to the method described in any one of Aspects 23 to 24, the method further includes: monitoring discovery messages from the ground network entity, the non-ground relay node and the NTN node based on the corresponding periodicity at least partially based on the corresponding priority indicated by the priority sorting configuration, wherein the communication of the one or more messages is at least partially based on the monitored discovery messages.

[0305] Aspect 28: The method according to any one of Aspects 23 to 25, wherein the access procedure comprises a discovery procedure, an initial access procedure, or both.

[0306] Aspect 29: The method according to any one of aspects 23 to 28, wherein the one or more non-terrestrial relay nodes include aircraft, UAVs, HAP devices, or any combination thereof, and the NTN node includes a satellite.

[0307] Aspect 30: A method for wireless communication at a network entity, the method comprising: outputting a control message indicating a priority ranking configuration associated with priority ranking of wireless communication at a UE, the priority ranking configuration indicating a relative priority associated with at least a non-terrestrial relay node and an NTN node; and outputting or obtaining one or more messages via a relay link provided by a non-terrestrial relay node or an NTN node based at least in part on the priority ranking configuration.

[0308] Aspect 31: According to the method described in Aspect 30, the method also includes: outputting an indication of a threshold number of non-ground relay nodes via the control message, wherein outputting or obtaining the one or more messages is at least partially based on the number of non-ground relay nodes in the target area of ​​the UE and the threshold number of non-ground relay nodes.

[0309] Aspect 32: The method according to aspect 31, the method further comprising: outputting an indication of the target area via the control message, wherein outputting or obtaining the one or more messages is at least partially based on outputting the indication of the target area.

[0310] Aspect 33: According to the method described in any one of Aspects 31 to 32, the method further includes: outputting, via the control message, an indication of a model for estimating the number of non-ground relay nodes within the target area of ​​the UE, wherein outputting or obtaining the one or more messages is at least partially based on outputting the indication of the model.

[0311] Aspect 34: A method according to any one of Aspects 30 to 33, wherein the priority sorting configuration indication includes a fixed priority list of corresponding priorities associated with ground network entities, non-ground relay nodes and NTN nodes, and outputting or obtaining the one or more messages is at least partially based on the corresponding priorities.

[0312] Aspect 35: The method according to any one of aspects 30 to 34, wherein the one or more non-terrestrial relay nodes include aircraft, UAVs, HAP devices, or any combination thereof, and the NTN node includes a satellite.

[0313] Aspect 36: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to perform a method according to any one of Aspects 1 to 19.

[0314] Aspect 37: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing a method according to any one of aspects 1 to 19.

[0315] Aspect 38: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 19.

[0316] Aspect 39: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; and a memory, the memory being coupled to the processor, the processor being configured to cause the apparatus to perform a method according to any one of Aspects 23 to 29.

[0317] Aspect 40: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing a method according to any one of aspects 23 to 29.

[0318] Aspect 41: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 23 to 29.

[0319] Aspect 42: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; and a memory, the memory coupled to the processor, the processor being configured to execute the method according to any one of Aspects 30 to 35.

[0320] Aspect 43: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 30 to 35.

[0321] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 30 to 35.

[0322] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0323] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0324] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0325] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0326] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0327] Computer-readable medium includes both non-transient computer storage medium and communication medium, and the communication medium includes any medium that promotes the transfer of computer programs from one location to another location.Non-transient storage medium can be any available medium that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by a general or special computer or a general or special processor in the form of an instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from a website, a server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0328] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0329] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0330] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0331] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0332] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor and configured to: receiving a control message indicating a prioritization configuration to prioritize wireless communications between one or more non-terrestrial relay nodes and one or more non-terrestrial network (NTN) nodes; as well as One or more messages are communicated based at least in part on the prioritization configuration and a number of non-terrestrial relay nodes associated with a location associated with the UE, a timing associated with the UE, or both.

2. The apparatus of claim 1, wherein the processor is further configured to: According to the prioritization configuration, wireless communications with the one or more non-terrestrial relay nodes or the one or more NTN nodes are prioritized based at least in part on the number of non-terrestrial relay nodes, wherein according to the prioritization, the one or more messages are communicated with a non-terrestrial relay node among the one or more non-terrestrial relay nodes or an NTN node among the one or more NTN nodes.

3. The apparatus of claim 2, wherein the processor is further configured to: Wireless communications with the one or more non-terrestrial relay nodes or the one or more NTN nodes are prioritized based at least in part on a comparison between the number of non-terrestrial relay nodes and a threshold number.

4. The apparatus of claim 3, wherein the processor is further configured to: prioritizing wireless communications with the one or more non-terrestrial relay nodes based at least in part on the number of non-terrestrial relay nodes being greater than or equal to the threshold number; and Wireless communications with the one or more NTN nodes are prioritized based at least in part on the number of non-terrestrial relay nodes being less than the threshold number.

5. The device according to claim 3, further comprising: An antenna array is configured to receive an indication of the threshold number via the control message, wherein the comparison is based at least in part on the control message.

6. The apparatus of claim 2, wherein the processor is further configured to: A distance metric is determined between the UE and the number of non-terrestrial relay nodes within a target area of ​​the location associated with the UE, wherein the prioritization is based at least in part on the distance metric.

7. The apparatus of claim 6, wherein the processor is further configured to: An indication of the target area is received via the control message.

8. The apparatus of claim 1, wherein the processor is further configured to: Monitoring synchronization signal blocks, discovery messages, or both from the one or more non-terrestrial relay nodes or the one or more NTN nodes is performed based at least in part on the prioritization configuration and the number of non-terrestrial relay nodes.

9. The apparatus of claim 1, wherein the processor is further configured to: Receiving, via the control message, an indication of a model for estimating the number of non-terrestrial relay nodes within a target area for the location associated with the UE; and estimating the number of non-terrestrial relay nodes within the target area for the UE based on the model, wherein the one or more messages are communicated based at least in part on the estimate.

10. The apparatus of claim 1, wherein the processor is further configured to: communicating the one or more messages with an NTN node of the one or more NTN nodes; performing a handover procedure from the NTN node to a non-terrestrial relay node of the one or more non-terrestrial relay nodes based at least in part on the number of non-terrestrial relay nodes; as well as One or more additional messages are communicated with the non-terrestrial relay node based at least in part on the handover process.

11. The apparatus of claim 10, wherein to communicate the one or more messages, the processor is configured to: The one or more messages are received from the NTN node, wherein the one or more messages include information associated with the non-terrestrial relay node, wherein the handover process is performed at least in part based on the information, and wherein the information includes an identifier associated with the non-terrestrial relay node, communication parameters for communicating with the non-terrestrial relay node, a heading associated with the non-terrestrial relay node, a location associated with the non-terrestrial relay node, or any combination thereof.

12. The apparatus of claim 10, wherein the processor is further configured to: communicating the one or more messages with a non-terrestrial relay node of the one or more non-terrestrial relay nodes; performing one or more measurements associated with the one or more messages communicated by the non-terrestrial relay node; performing a handover procedure from the non-terrestrial relay node to an NTN node of the one or more NTN nodes based at least in part on the one or more measurements and the measurement threshold; as well as One or more additional messages are communicated with the NTN node based at least in part on the handover process.

13. The apparatus of claim 12, wherein to communicate the one or more messages, the processor is configured to: The one or more messages are received from the non-terrestrial relay node, wherein the one or more messages include information associated with the NTN node, wherein the handover process is performed based at least in part on the information, and wherein the information includes an identifier associated with the NTN node, communication parameters for communicating with the NTN node, a location associated with the NTN node, or any combination thereof.

14. The apparatus of claim 1, wherein the processor is further configured to: An indication of an ability of the UE to perform wireless communications with the one or more non-terrestrial relay nodes and the one or more NTN nodes is sent, wherein the control message is received based at least in part on a capability message.

15. The apparatus of claim 1, wherein the processor is further configured to: The one or more messages are communicated with an additional wireless device via a relay link provided by a non-terrestrial relay node of the one or more non-terrestrial relay nodes or an NTN node of the one or more NTN nodes.

16. The apparatus of claim 1, wherein the one or more non-terrestrial relay nodes comprise aircraft, unmanned aerial vehicles, high altitude platform equipment, or any combination thereof, and wherein the NTN node comprises a satellite.

17. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor and configured to: performing the access procedure according to a prioritization configuration associated with the access procedure, wherein the prioritization configuration indicates a priority list including respective priorities for terrestrial network entities, non-terrestrial relay nodes, and non-terrestrial network (NTN) nodes; as well as One or more messages are communicated with one of the terrestrial network entity, the non-terrestrial relay node, or the NTN node based at least in part on the access procedure.

18. The apparatus of claim 17, wherein the prioritization configuration indicates a first priority associated with a terrestrial network entity, a second priority associated with a non-terrestrial relay node, and a third priority associated with an NTN node, wherein the processor is further configured to: Wireless communications with the terrestrial network entity, the non-terrestrial relay node, or the NTN node are prioritized based at least in part on a comparison of the first priority, the second priority, and the third priority.

19. The apparatus according to claim 17, further comprising: An antenna array configured to monitor synchronization signal blocks, discovery messages, or both from the terrestrial network entities, the non-terrestrial relay nodes, and the NTN nodes according to respective periodicities based at least in part on the respective priorities indicated via the priority sorting configuration, wherein the one or more messages are communicated based at least in part on the monitored synchronization signal blocks, discovery messages, or both.

20. The apparatus of claim 17, wherein the access process comprises one of a discovery process or an initial access process.

21. The apparatus of claim 17, wherein the one or more non-terrestrial relay nodes comprise aircraft, unmanned aerial vehicles, high altitude platform equipment, or any combination thereof, and wherein the NTN node comprises a satellite.

22. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; and a memory coupled to the processor and configured to: outputting a control message indicating a prioritization configuration associated with prioritization of wireless communications at a user equipment (UE), wherein the prioritization configuration indicates a relative priority associated with at least a non-terrestrial relay node and a non-terrestrial network (NTN) node; as well as One or more messages are output or obtained via a relay link provided by a non-terrestrial relay node or a non-terrestrial network (NTN) node based at least in part on the prioritization configuration.

23. The apparatus of claim 22, wherein the processor is further configured to: An indication of a threshold number of non-terrestrial relay nodes is output via the control message, wherein the one or more messages are output or obtained based at least in part on the number of non-terrestrial relay nodes in a target area of ​​the UE and the threshold number of non-terrestrial relay nodes.

24. The apparatus of claim 23, wherein the processor is further configured to: An indication of the target area is output via the control message, wherein the one or more messages are output or obtained based at least in part on the indication of the target area.

25. The apparatus according to claim 23, further comprising: An antenna array configured to output, via the control message, an indication of a model for estimating the number of non-terrestrial relay nodes within the target area for the UE, wherein the one or more messages are output or obtained based at least in part on the indication of the model.

26. An apparatus according to claim 22, wherein the prioritization configuration indication includes a fixed priority list of respective priorities associated with terrestrial network entities, non-terrestrial relay nodes, and NTN nodes, and wherein the one or more messages are output or obtained based at least in part on the respective priorities.

27. The apparatus of claim 22, wherein the one or more non-terrestrial relay nodes comprise aircraft, unmanned aerial vehicles, high altitude platform equipment, or any combination thereof, and wherein the NTN node comprises a satellite.

28. A method for wireless communication at a user equipment (UE), the method comprising: receiving a control message indicating a prioritization configuration for prioritizing wireless communications between one or more non-terrestrial relay nodes and one or more non-terrestrial network (NTN) nodes; as well as One or more messages are communicated based at least in part on the prioritization configuration and a number of non-terrestrial relay nodes corresponding to a location associated with the UE, a timing associated with the UE, or both.

29. The method according to claim 28, further comprising: According to the prioritization configuration, wireless communications with the one or more non-terrestrial relay nodes or the one or more NTN nodes are prioritized based at least in part on the number of non-terrestrial relay nodes, wherein according to the prioritization, the one or more messages are communicated with a non-terrestrial relay node among the one or more non-terrestrial relay nodes or an NTN node among the one or more NTN nodes.

30. The method of claim 29, wherein the prioritization further comprises: Wireless communications with the one or more non-terrestrial relay nodes or the one or more NTN nodes are prioritized based at least in part on a comparison between the number of non-terrestrial relay nodes and a threshold number.