Sending aircraft mobility data to user equipment

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, an aircraft monitoring function (ASF) in a new radio (NR) network may send a request for aircraft mobility data to a broadcast automatic dependent monitoring (ADS-B) server, where the aircraft mobility data is associated with an aircraft configured to communicate with a user equipment (UE). The ASF may receive the aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft. The ASF may send the aircraft mobility data to the UE, where the aircraft mobility data indicates an aircraft NR identifier, and where the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for transmitting aircraft mobility data to user equipment (UE). Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] In some specific implementations, an apparatus for wirelessly communicating at an aircraft surveillance function (ASF) in a new radio (NR) network includes a memory and one or more processors coupled to the memory, the one or more processors configured to: send a request for aircraft mobility data to an automatic dependent surveillance-broadcast (ADS-B) server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with a user equipment (UE); receive the aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and send the aircraft mobility data to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier.

[0006] In some specific implementations, an apparatus for wireless communication at a UE includes a memory and one or more processors coupled to the memory, the one or more processors configured to: send an initial request for aircraft mobility data to an ASF in an NR network, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE; receive aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by an ADS-B server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and perform an action based at least in part on the aircraft mobility data.

[0007] In some specific implementations, a method of wireless communication performed by an ASF in a NR network includes sending a request for aircraft mobility data to an ADS-B server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with a UE; receiving the aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and sending the aircraft mobility data to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier.

[0008] In some specific implementations, a method of wireless communication performed by a UE includes sending an initial request for aircraft mobility data to an ASF in a NR network, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE; receiving the aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by an ADS-B server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and performing an action based at least in part on the aircraft mobility data.

[0009] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of an ASF, cause the ASF to: send a request for aircraft mobility data to an ADS-B server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with a UE; receive the aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and send the aircraft mobility data to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier.

[0010] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: send an initial request for aircraft mobility data to an ASF in a NR network, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE; receive aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by an ADS-B server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and perform an action based at least in part on the aircraft mobility data.

[0011] In some specific implementations, an apparatus for wireless communication includes a component for sending a request for aircraft mobility data to an ADS-B server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with a UE; a component for receiving the aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and a component for sending the aircraft mobility data to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier.

[0012] In some specific embodiments, an apparatus for wireless communication includes components for sending an initial request for aircraft mobility data to an ASF in a NR network, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the apparatus; components for receiving the aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by an ADS-B server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and components for performing an action based at least in part on the aircraft mobility data.

[0013] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0014] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0015] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of air-to-ground (ATG) communication according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of aircraft-based ATG expansion according to the present disclosure.

[0022] Figures 6 to 13is a diagram illustrating an example associated with transmitting aircraft mobility data to a UE according to the present disclosure.

[0023] Figure 14 to Figure 15 is a diagram illustrating an example process associated with sending aircraft mobility data to a UE according to the present disclosure.

[0024] Figure 16 to Figure 17 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0025] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

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

[0027] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0028] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). For another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0029] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0030] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0031] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with the network node 110. In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

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

[0033] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0034] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0035] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.

[0036] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

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

[0039] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem 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).

[0040] 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.

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

[0042] In some aspects, an aircraft surveillance function (ASF) in a NR network (e.g., ASF 124) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a request for aircraft mobility data to an Automatic Dependent Surveillance-Broadcast (ADS-B) server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with a UE; receive the aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and send the aircraft mobility data to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0043] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may send an initial request for aircraft mobility data to an ASF in an NR network, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE; receive the aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by an ADS-B server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and perform an action based at least in part on the aircraft mobility data. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0044] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The content described is different.

[0045] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0046] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120, and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0047] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

[0049] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0050] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 6 to 17 )Aspects of any of the methods described herein.

[0051] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 6 to 17 ) or any aspect of any of the methods described herein.

[0052] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the ASF may perform one or more techniques associated with sending aircraft mobility data to the UE, as described in more detail elsewhere herein. In some aspects, the ASF described herein includes Figure 2 One or more components of the base station 110 shown and / or include Figure 2 One or more components of the UE 120 shown. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.14 The process of 1400 Fig.15 1500 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Fig.14 The process of 1400 Fig.15 The operations of the process 1500 and / or other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0053] In some aspects, an ASF in a NR network (e.g., ASF 124) includes means for sending a request for aircraft mobility data to an ADS-B server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with a UE; means for receiving aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and / or means for sending aircraft mobility data to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier. In some aspects, means for the ASF to perform operations described herein may include, for example, one or more of a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, means for the ASF to perform operations described herein may include, for example, one or more of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0054] In some aspects, a UE (e.g., UE 120) includes means for sending an initial request for aircraft mobility data to an ASF in a NR network, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE; means for receiving aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by an ADS-B server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and / or means for performing an action based at least in part on the aircraft mobility data. Means for the UE to perform operations described herein may include, for example, one or more of the following: a communications manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0055] Although Figure 2The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0056] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The content described is different.

[0057] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

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

[0059] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0060] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0061] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, or both.

[0062] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 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, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0063] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partitioning (such as that defined by 3GPP). In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0064] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions, or low PHY layer functions (such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc.) based on functional splitting (e.g., functional splitting defined by 3GPP). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0065] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 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 (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0066] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

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

[0068] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The content described is different.

[0069] Figure 4 is a diagram illustrating an example 400 of air-to-ground communications according to the present disclosure.

[0070] like Figure 4As shown, air-to-ground (ATG) communications can allow an ATG network node 402 on the ground to communicate with an aircraft 404 and a UE associated with the aircraft 404 (e.g., a UE carried by a passenger on the aircraft 404). The ATG network can be deployed inland (e.g., which may include disaster areas) and / or coastal areas. In the ATG network, the ATG network node 402 on the ground can be associated with an upwardly tilted antenna. The aircraft 404 in the air can be associated with an antenna located on the lower side of the aircraft. The UE associated with the aircraft 404 can be connected to the ATG network via onboard customer premises equipment (CPE) (e.g., in-cabin WiFi or a small cell). ATG communications can provide various advantages over satellite communications, such as lower cost, higher throughput, and lower latency. ATG communications can support various types of services, such as in-flight passenger communications (e.g., commercial flights and / or business aviation, which can include takeoff / landing and climb / descent scenarios), airline operations communications (e.g., aircraft maintenance, flight planning, and / or weather), and / or air traffic control (e.g., backup to systems in aviation licensed bands). ATG communications can be used as a backup to systems in aviation licensed bands. ATG communications can enable in-flight connectivity.

[0071] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The content described is different.

[0072] ATG can be extended to serve ground UEs by aircraft. In aircraft-based ATG extension, commercial aircraft can be used to extend coverage in areas without ground network nodes. The typical cruising altitude of commercial aircraft (e.g., 10 kilometers) can allow line of sight (LOS) propagation of more than 200 kilometers. The density of commercial aircraft can vary from region to region, but is usually relatively dense during daytime. For example, in some areas, at least one aircraft can be visible within 50 kilometers-100 kilometers.

[0073] Aircraft-based ATG expansion can provide various advantages over non-terrestrial network (NTN) deployment. Aircraft-based ATG expansion does not require the launch of satellites, which can reduce deployment costs (e.g., the cost can be used only for software upgrades based on existing / upcoming ATG CPE) and achieve faster time to market. Aircraft-based ATG expansion can provide better link budget due to the aircraft altitude of 10 kilometers compared to the satellite altitude of 1000 kilometers.

[0074] Figure 5 is a diagram illustrating an example 500 of aircraft-based ATG expansion according to the present disclosure.

[0075] like Figure 5As shown, the first aircraft 404a can communicate with the remote UE 120 on the ground. The remote UE 120 can be in an area without a ground network node. The first aircraft 404a can be associated with an ATG network node 402 (e.g., a base station), an IAB, a UE, a relay, or an intelligent repeater. The first aircraft 404a can communicate with the second aircraft 404b. The first aircraft 404a and the second aircraft 404b can both communicate with the ATG network node 402 on the ground. The first aircraft 404a can be able to expand the coverage of the remote UE 120 on the ground.

[0076] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The content described is different.

[0077] For aircraft-based ATG expansion, it may be necessary to position the aircraft as a cellular node, but this may be associated with various challenges, such as uncertainty in the aircraft trajectory. The aircraft trajectory may be associated with a navigation error of up to 3.6 kilometers. The regional navigation (RNAV) standard may require that the aircraft maintain a total system error of no more than 3.6 kilometers for 95% of the total flight time. The aircraft trajectory may be associated with temporary adjustments to the trajectory, such as high-frequency temporary adjustments caused by departure delays and weather such as thunderclouds. The positioning of the aircraft can be determined using the NR position management function (LMF), but the available resources may not be sufficient to achieve the target accuracy of aircraft positioning. The UE may be within one kilometer of the network node, while a commercial aircraft may be about 10 kilometers away from the network node. The positioning of the aircraft can be determined by transmitting a global navigation satellite system (GNSS) signal using NR, but this requires high throughput. Each aircraft may need to transmit a GNSS signal every half second as required in an aircraft monitoring system, which may waste radio and power resources.

[0078] In various aspects of the techniques and apparatus described herein, a UE may send an initial request for aircraft mobility data to an ASF in an NR network. The aircraft mobility data may be associated with an aircraft (e.g., an aircraft UE / gNB) configured to communicate with the UE. The ASF may send a request for aircraft mobility data to an ADS-B server and based at least in part on the initial request. The ASF may receive aircraft mobility data from the ADS-B server and based at least in part on the request. The aircraft mobility data may indicate an aircraft number associated with the aircraft. The aircraft number may be an aircraft flight number or an aircraft registration number (e.g., a unique number assigned to a particular aircraft). The ASF may send the aircraft mobility data to the UE. The aircraft mobility data may indicate an aircraft NR identifier, wherein the aircraft NR identifier may be based at least in part on a mapping between an aircraft number and an aircraft NR identifier. The UE may perform an action based at least in part on the aircraft mobility data.

[0079] In some aspects, an ADS-B server may be used to determine the positioning of an aircraft UE / gNB. The NR network may request aircraft mobility data (or ADS-B data) associated with an aircraft UE / gNB from an ADS-B server. The aircraft mobility data may be identified by an aircraft flight number (e.g., call sign) and a registration number (e.g., tail number). One aircraft (or registration number) may serve different flights. NR aircraft nodes such as gNBs, IABs, UEs, relays, etc. may be identified using identifiers assigned by a cellular system in the NR network. The identifier assigned by the cellular system may include a global gNB identifier, which may be based at least in part on a public land mobile network (PLMN) identifier and a gNB identifier. The identifier assigned by the cellular system may include a UE identifier, which may be based at least in part on a global unique temporary identifier (GUTI) and a cell radio network temporary identifier (C-RNTI). Aircraft mobility data may be shared between an ADS-B server and the NR network, and an aircraft flight / registration number associated with the aircraft mobility data may be mapped to an identifier assigned by a cellular system in the NR network (e.g., an NR identifier, such as a gNB identifier or a UE identifier). The NR network may obtain position data, speed data, direction data associated with an aircraft UE / gNB (or aircraft IAB / relay), etc. in the NR network from the aircraft mobility data. The NR network may determine the position data, speed data, and direction data associated with an aircraft UE / gNB by using aircraft mobility data received from an existing aircraft monitoring system (e.g., an ADS-B server). Reusing real-time aircraft mobility data from an existing aircraft monitoring system (e.g., an ADS-B server) may save radio and power resources for a gNB / UE that utilizes the aircraft mobility data.

[0080] Figure 6 is a diagram illustrating an example 600 associated with sending aircraft mobility data to a UE in accordance with the present disclosure.

[0081] like Figure 6As shown, the ADS-B server 128 may send aircraft mobility data (e.g., aircraft position, speed, and direction information) to the ATG network node 402 (e.g., ATG-gNB). The ATG network may perform a mapping of an aircraft flight number and / or registration number associated with the aircraft mobility data to an identifier in the NR system. The ATG network node 402 may perform position / speed-based control of an aircraft UE / gNB 602 (e.g., aircraft #i, aircraft #j, and aircraft #k) based at least in part on the aircraft mobility information. The ATG network node 402 may send the aircraft mobility data and a corresponding identifier (e.g., an identifier associated with the NR system) to the UE 120. The UE 120 may perform timing advance (TA) and frequency compensation with respect to the aircraft UE / gNB 602 (e.g., aircraft #i) based at least in part on the aircraft mobility data.

[0082] In some aspects, the position (as well as speed and direction) associated with the aircraft UE / gNB 602 may be determined by reusing data from an existing aircraft monitoring system such as ADS-B. In ADS-B, the aircraft UE / gNB 602 may broadcast its GNSS position, speed, heading, flight number, etc. every half second. ADS-B ground stations may collect aircraft mobility data (or ADS-B data) to air traffic control centers. An open server for real-time global aircraft mobility data may be available. Reusing data to locate the aircraft UE / gNB 602 may effectively utilize existing high-performance aircraft positioning systems that may already have aircraft mobility data such as position, speed, and direction.

[0083] In some aspects, ADS-B can provide access to weather and flight information. ADS-B can provide real-time accuracy, shared situational awareness, and advanced applications for pilots and controllers, etc. Aircraft UE / gNB 602 can broadcast GNSS position, speed, heading, flight number, etc. by using ADS-B OUT equipment, which can use 1090MHz and 978MHz frequencies and use mode S transponder every half second. Aircraft UE / gNB 602 can also use ADS-B IN equipment to receive aircraft mobility data. ADS-B ground stations can send aircraft mobility data to air traffic control centers. Aircraft mobility data can indicate flight identification (e.g., flight number), 24-bit aircraft address (e.g., globally unique fuselage code), location (e.g., latitude and longitude), location integrity / accuracy (e.g., global positioning system (GPS) horizontal protection limit), pressure and geometric altitude, vertical rate (e.g., climb / descent rate), track angle and ground speed (e.g., speed), emergency instructions and / or special location identification. Real-time ADS-B may be preferred for air traffic control surveillance, and general aviation may be safer with ADS-B's traffic, weather, and flight information services.

[0084] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The content described is different.

[0085] Figure 7 is a diagram illustrating an example 700 associated with sending aircraft mobility data to a UE according to the present disclosure. Figure 7 As shown, example 700 includes communications between an ASF (e.g., ASF 124), an ADS-B server (e.g., ADS-B server 128), and a UE (e.g., UE 120). In some aspects, the ADS-B server and the UE may be included in a wireless network (such as wireless network 100).

[0086] As shown by reference numeral 702, an ASF in the NR network (which may be associated with an application function or a third party server) may receive an initial request for aircraft mobility data from a UE. The aircraft mobility data may be associated with an aircraft configured to communicate with the UE. The ASF may communicate with the UE via an access and mobility management function (AMF) in the NR network ( Figure 7 ) receives an initial request from the UE. The initial request may originate from the UE. The UE may receive an initial request from the UE via the network node ( Figure 7The ASF may be associated with an application function or a third-party server, and may be associated with a wired communication scheme (e.g., a network cable or optical fiber, or a virtual interface in software).

[0087] In some aspects, the initial request may indicate a reference location associated with the UE and a radius associated with the reference location. The radius may indicate a maximum range between the aircraft and the UE. The initial request may indicate an aircraft NR identifier associated with the aircraft. In some aspects, the ASF may receive an initial request from the UE based at least in part on an AMF notification to the UE indicating that the UE is within a defined distance from an edge of a ground network. The UE may receive an AMF notification from the AMF. The ASF may receive an initial request from the UE based on a request periodicity based at least in part on downlink signal measurements.

[0088] As indicated by reference numeral 704, the ASF may send a request for mobility data to the ADS-B server. The ASF may send the request to the ADS-B server based at least in part on an initial request received at the ASF from the UE.

[0089] As indicated by reference numeral 706, the ASF may receive aircraft mobility data from an ADS-B server and based at least in part on the request. The aircraft mobility data may indicate an aircraft number associated with the aircraft. The aircraft number may be an aircraft flight number or an aircraft registration number. In some aspects, the ASF may filter the aircraft mobility data associated with the aircraft number based at least in part on a reference location and a radius associated with the reference location.

[0090] As indicated by reference numeral 708, the ASF may send aircraft mobility data to the UE, wherein the aircraft mobility data may indicate an aircraft NR identifier. The aircraft NR identifier may be based at least in part on a mapping between an aircraft number and an aircraft NR identifier. The ASF may provide a network open function (NEF) ( Figure 7 The ASF may send aircraft mobility data requested from the ADS-B server to the AMF based at least in part on scheduling rather than based on an initial request received from the AMF, network node, or UE.

[0091] In some aspects, the aircraft may be an aircraft UE, and the mapping between the aircraft number and the aircraft NR identifier may be based at least in part on the mapping between the aircraft registration number and the international mobile subscriber identity (IMSI) or GUTI. In some aspects, the aircraft may be or may include an aircraft network node, and the mapping between the aircraft number and the aircraft NR identifier may be based at least in part on the mapping between the aircraft registration number and the global network node identifier. In some aspects, the aircraft may be an aircraft network node DU, and the mapping between the aircraft number and the aircraft NR identifier may be based at least in part on the mapping between the aircraft registration number and the global network node identifier and the network node DU identifier. In some aspects, the aircraft may be an aircraft IAB, and the mapping between the aircraft number and the aircraft NR identifier may be based at least in part on the mapping between the aircraft registration number and the global IAB identifier. In some aspects, the aircraft may be an aircraft repeater, and the mapping between the aircraft number and the aircraft NR identifier may be based at least in part on the mapping between the aircraft registration number and the global repeater identifier. In some aspects, the aircraft may be an aircraft relay, and the mapping between the aircraft number and the aircraft NR identifier may be based at least in part on a mapping between the aircraft registration number and the global relay identifier.

[0092] As shown at reference numeral 710, the UE may perform actions based at least in part on the aircraft mobility data. For example, the UE may determine whether the UE is within a coverage area of ​​the aircraft based at least in part on the aircraft mobility data. The UE may send a message based at least in part on determining that the UE is within the coverage area of ​​the aircraft. As another example, the UE may employ timing advance and frequency compensation based at least in part on the aircraft mobility data.

[0093] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The content described is different.

[0094] Figure 8 is a diagram illustrating an example 800 associated with sending aircraft mobility data to a UE in accordance with the present disclosure.

[0095] In some aspects, the NR system 802 may obtain aircraft mobility data from an ADS-B system. The ASF in the NR system 802 may support obtaining aircraft mobility data (or ADS-B data) from an ADS-B system. The NR system 802 may obtain aircraft mobility data (e.g., position, speed, and / or direction) from an ADS-B system. The aircraft mobility data may be associated with an aircraft flight / registration number. The NR system 802 may perform a mapping between an aircraft flight / registration number and an NR identifier. For example, a network open function (NE) of the NR system 802 may determine which aircraft node (e.g., aircraft UE / gNB / IAB) is associated with aircraft mobility data identified by an aircraft flight / registration number from an ADS-B system. In addition, the UE may request aircraft mobility data based at least in part on one or more triggering events.

[0096] like Figure 8 As shown, an ADS-B server 128 associated with an ADS-B system may send an indication of an aircraft flight / registration number and corresponding aircraft mobility data (e.g., position, speed, and / or direction information) to an NR system 802. The indication may traverse a data interface 804 associated with the NR system 802. The NR system 802 may perform an identifier mapping based at least in part on the aircraft flight / registration number via an identifier mapping unit 806, during which the NR system 802 may identify an aircraft UE / gNB identifier corresponding to the aircraft flight / registration number. The aircraft UE / gNB identifier may be associated with the NR system 802. The NR system 802 may identify the aircraft UE / gNB identifier using a lookup table, which may include multiple aircraft flight / registration numbers and corresponding aircraft UE / gNB identifiers. The NR system 802 may provide an indication of the aircraft UE / gNB identifier and the corresponding aircraft mobility data to an ATG-gNB / UE 808 associated with the NR system 802.

[0097] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The content described is different.

[0098] Fig. 9 is a diagram illustrating an example 900 associated with sending aircraft mobility data to a UE in accordance with the present disclosure.

[0099] like Fig. 9As shown, ASF 124 may be included in the NR system to support the collection of aircraft mobility data (or ADS-B data). ASF 124 may be an application function, or ASF 124 may be a third-party server. ASF 124 may request aircraft mobility data from an ADS-B server 128 associated with the ADS-B system, which aircraft mobility data may include information related to the position, speed, heading, etc. of the aircraft. UE / gNB 120 / 110 may send a request for aircraft mobility data to ASF 124. In other words, ASF 124 may request aircraft mobility data from ADS-B server 128 based at least in part on the request received from UE / gNB 120 / 110. ASF 124 may obtain aircraft mobility data from ADS-B server 128, and ASF 124 may respond to UE / gNB 120 / 110 with the aircraft mobility data. The ASF 124 may respond to the UE / gNB 120 / 110 via the NEF 126 and the AMF 122, which may be based at least in part on aircraft identifier mapping that may occur between the ADS-B system and the NR system (e.g., a mapping between an aircraft flight / registration number and an NR identifier (such as a UE identifier or a gNB identifier)). The aircraft identifier mapping may occur in the NEF 126, which may be located between the ASF 124 and the AMF 122. The ASF 124, the NEF 126, and the AMF 122 may be associated with an NR 5G Core (5G-C) network. The UE / gNB 120 / 110 may be associated with an NR RAN network.

[0100] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 The content described is different.

[0101] Fig.10 1 is a diagram illustrating an example 1000 associated with sending aircraft mobility data to a UE according to the present disclosure. Fig.10 As shown, example 1000 includes an AMF (e.g., AMF 122), an ASF (e.g., ASF 124), an NEF (e.g., NEF 126), an ADS-B server (e.g., ADS-B server 128) (not shown), a UE (e.g., UE 120), and a network node (e.g., network node 110, which may be a gNB) (wherein the UE and the gNB are in Fig.10 In some aspects, the AMF, ASF, NEF, ADS-B server, UE, and network nodes may be included in a wireless network (such as wireless network 100).

[0102] As shown by reference numeral 1002, the gNB / UE may send a request for aircraft mobility data to the ASF. The request may be sent by the AMF, the gNB, or the UE. The AMF may forward the request to the ASF of the gNB / UE. The ASF may be capable of supporting aircraft mobility data (or ADS-B data). As shown by reference numeral 1004, the ASF may send aircraft mobility data to the NEF. The ASF may send aircraft mobility data based at least in part on a request or at least in part on a regular schedule (for example, the ASF may periodically send aircraft mobility data). The aircraft mobility data may be identified by an aircraft flight / registration number. The ASF may receive aircraft mobility data from an ADS-B server based at least in part on a connection between the ASF and the ADS-B server. As shown by reference numeral 1006, the NEF may send aircraft mobility data to the AMF. At this time, the aircraft mobility data may be identified by an aircraft NR identifier. The NEF may determine the aircraft NR identifier from the aircraft flight / registration number using a lookup table that may include multiple aircraft flight / registration numbers and corresponding aircraft NR identifiers (e.g., aircraft UE / gNB identifiers). As indicated by reference numeral 1008, the AMF may send aircraft mobility data to the gNB / UE, where the aircraft mobility data may be identified by the aircraft NR identifier. The gNB / UE may use the aircraft mobility data to perform actions (e.g., TA and frequency compensation).

[0103] In some aspects, a request for aircraft mobility data from the AMF / gNB / UE to the ASF may indicate various types of optional information. The request may indicate a reference location and corresponding radius information. For example, the request may indicate the gNB / UE location and the maximum range of the connecting aircraft and the gNB / UE. The ASF may provide aircraft mobility data in an area, which may correspond to a circle with a corresponding radius centered on the reference location. The request may indicate the NR identifier of the aircraft for which the aircraft mobility data is requested. For example, the request may indicate the IMSI or GUTI of the aircraft UE, or the request may indicate the global gNB identifier of the aircraft gNB. The ASF may provide aircraft mobility data associated with the NR identifier indicated in the request. The NEF may map the NR identifier in the request to an aircraft flight / registration number in the communication link between the AMF, NEF, and ASF. When the reference location and corresponding radius information and / or NR identifier of the aircraft are not indicated in the request, the ASF may provide aircraft mobility data associated with global aircraft (e.g., aircraft traveling in multiple areas).

[0104] As indicated above, Fig.10 are provided as examples. Other examples can be found in the Fig.10 The content described is different.

[0105] Fig.11 1 is a diagram illustrating an example 1100 associated with sending aircraft mobility data to a UE according to the present disclosure. Fig.11 As shown, example 1000 includes an AMF (e.g., AMF 122), an ASF (e.g., ASF 124), an NEF (e.g., NEF 126), an ADS-B server (e.g., ADS-B server 128) (not shown), a UE (e.g., UE 120), and a network node (e.g., network node 110, which may be a gNB) (wherein the UE and the gNB are in Fig.11 In some aspects, the AMF, ASF, NEF, ADS-B server, UE, and network nodes may be included in a wireless network (such as wireless network 100).

[0106] As shown by reference numeral 1102, based at least in part on a procedure initiated by the gNB / UE, the gNB / UE may send a request for local aircraft mobility data to the ASF. The request may also indicate a local reference position (e.g., the gNB / UE position) and radius information (e.g., the maximum range of the connecting aircraft and the gNB / UE). The gNB / UE may send a request to the ASF, wherein the request may indicate information of a local area (e.g., the gNB / UE coverage area of ​​the aircraft). Alternatively, the gNB / UE may send a request to the AMF, and the AMF may forward the request to the ASF. As shown by reference numeral 1104, the ASF may request aircraft mobility data (or ADS-B data) from an ADS-B server. The ASF may send a request to the ADS-B server based at least in part on the request received from the gNB / UE. As shown by reference numeral 1106, the ASF may filter the aircraft mobility data received from the ADS-B server based at least in part on the local reference position and the radius. In other words, the ASF may filter the aircraft mobility data based at least in part on the requested area (e.g., a circle with a radius centered at the local reference location). As indicated by reference numeral 1108, the ASF may send the local aircraft mobility data to the NEF. As indicated by reference numeral 1110, the NEF may map the aircraft flight / registration number associated with the local aircraft mobility data to an NR identifier. As indicated by reference numeral 1112, the NEF may send the local aircraft mobility data associated with the NR identifier to the gNB / UE. In other words, the ASF may filter the aircraft mobility data based on the requested area, and the ASF may provide the result to the gNB / UE via the NEF and the AMF, where the NEF may map the aircraft identifier between the ASF and the AMF.

[0107] As indicated above, Fig.11 are provided as examples. Other examples can be found in the Fig.11 The content described is different.

[0108] Fig.12 1 is a diagram illustrating an example 1200 associated with sending aircraft mobility data to a UE according to the present disclosure. Fig.12 As shown, example 1000 includes an AMF (e.g., AMF 122), an ASF (e.g., ASF 124), an NEF (e.g., NEF 126), an ADS-B server (e.g., ADS-B server 128) (not shown), a UE (e.g., UE 120), and a network node (e.g., network node 110, which may be a gNB) (wherein the UE and the gNB are in Fig.12 In some aspects, the AMF, ASF, NEF, ADS-B server, UE, and network nodes may be included in a wireless network (such as wireless network 100).

[0109] As shown by reference numeral 1202, based at least in part on a procedure initiated by the AMF, the AMF may send a request for aircraft mobility data to the ASF. The AMF may periodically request aircraft mobility data from the ASF, or the AMF may request aircraft mobility data from the ASF based at least in part on a triggering event. As shown by reference numeral 1204, the ASF may request aircraft mobility data (or ADS-B data) from an ADS-B server. The ASF may request aircraft mobility data from the ADS-B based at least in part on a request received from the AMF.

[0110] Alternatively, based at least in part on the ASF-initiated procedure, the ASF may forward (or push) aircraft mobility data requested from the ADS-B server to the AMF according to a regular schedule. In other words, the ASF may periodically request aircraft mobility data from the ADS-B server, and the ADS-B server may send aircraft mobility data to the ASF, which may forward the aircraft mobility data to the AMF.

[0111] As indicated by reference numeral 1206, the ASF may send the aircraft mobility data to the NEF. As indicated by reference numeral 1208, the NEF may map the aircraft flight / registration number associated with the aircraft mobility data to the NR identifier. As indicated by reference numeral 1210, the NEF may send the aircraft mobility data associated with the NR identifier to the gNB / UE.

[0112] As indicated above, Fig.12 are provided as examples. Other examples can be found in the Fig.12 The content described is different.

[0113] In some aspects, a mapping between an aircraft flight / registration number and an NR identifier may be performed, wherein the mapping may involve accessing a lookup table storing multiple aircraft flight / registration numbers and corresponding NR identifiers. The ADS-B server may only provide aircraft mobility data identified by an aircraft flight number, in which case the ASF may need to map the aircraft flight number associated with the aircraft mobility data to the aircraft registration number. The NEF may map the aircraft registration number associated with the aircraft mobility data to the NR identifier. In the opposite direction, the NEF may map the NR identifier to the aircraft registration number. The NEF may perform the mapping based at least in part on an ASF to NEF to AMF communication link, or the NEF may perform the mapping based at least in part on an AMF to NEF to ASF communication link. In some aspects, for an aircraft UE, the aircraft registration number may be mapped to an IMSI / GUTI, or vice versa. For an aircraft gNB, the aircraft registration number may be mapped to a global gNB identifier, or vice versa. For an aircraft gNB-DU, the aircraft registration number may be mapped to the global gNB identifier plus the gNB-DU identifier, or vice versa. For an aircraft IAB, the aircraft registration number may be mapped to the global IAB identifier, or vice versa. For an aircraft repeater (e.g., a smart repeater), the aircraft registration number may be mapped to the global repeater identifier, or vice versa. For an aircraft relay, the aircraft registration number may be mapped to the global relay identifier, or vice versa.

[0114] In some aspects, the UE may send a request for aircraft mobility data to the gNB or directly to the AMF, which may request the aircraft mobility data from the ASF. The UE may send the request based at least in part on various triggering events. When the UE is about to leave the ground network, the UE may be pre-configured with aircraft mobility data to connect to the aircraft after the lost ground network connection. The UE may send a message only when the aircraft is predicted to be in its coverage area, which may save power for the UE. The aircraft mobility data may indicate whether the aircraft is predicted to be in the coverage area. The UE may adopt TA and frequency compensation based at least in part on the aircraft mobility data. The UE may periodically request aircraft mobility data from the ASF after receiving an AMF notification, which may indicate that the UE is at the edge of the ground network. The UE may request aircraft mobility data based at least in part on a request period, which may be reduced when the RSRP measurement, RSRQ measurement and / or signal to interference plus noise ratio (SINR) of the downlink signal decreases.

[0115] Fig.13 is a diagram illustrating an example 1300 associated with sending aircraft mobility data to a UE in accordance with the present disclosure.

[0116] like Fig.13 As shown, UE 120 may receive an AMF notification from the AMF. The AMF notification may indicate that UE 120 is at the edge of the ground network. In other words, the AMF notification may indicate that UE 120 is likely to leave the ground network. After receiving the AMF notification, UE 120 may request aircraft mobility data from the ASF in a periodic manner. For example, UE 120 may send a request 1302 after each period t1. When the RSRP / RSRQ / SINR measurement of the downlink signal decreases, UE 120 may send a request 1302 according to a reduced periodicity (e.g., period t2). In other words, UE 120 may wait for a shorter time period before sending the next request 1304. Based on the aircraft mobility data, UE 120 may determine whether UE 120 is still within the coverage of the aircraft, and UE 120 may send a message to save power only when the aircraft is predicted to be within its coverage area.

[0117] As indicated above, Fig.13 are provided as examples. Other examples can be found in the Fig.13 The content described is different.

[0118] Fig.14 1 is a diagram illustrating an example process 1400 performed, for example, by an ASF in an NR network in accordance with the present disclosure. The example process 1400 is an example in which an ASF in an NR network (e.g., ASF 124) performs operations associated with sending aircraft mobility data to a UE.

[0119] like Fig.14 As shown, in some aspects, process 1400 may include sending a request to an ADS-B server for aircraft mobility data, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE (block 1410). For example, an ASF (e.g., using Fig.16 The communication manager 150 and / or the sending component 1604 depicted in FIG. 1 may send a request for aircraft mobility data to an ADS-B server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE, as described above.

[0120] like Fig.14 As further shown, in some aspects, process 1400 may include receiving aircraft mobility data from an ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number (block 1420). For example, the ASF (e.g., using Fig.16The communication manager 150 and / or receiving component 1602 depicted in FIG. 1 may receive aircraft mobility data from an ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number, as described above.

[0121] like Fig.14 As further shown, in some aspects, process 1400 may include sending aircraft mobility data to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number and an aircraft NR identifier (block 1430). Fig.16 The communication manager 150 and / or the sending component 1604 depicted in FIG. 1 may send aircraft mobility data to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number and an aircraft NR identifier, as described above.

[0122] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0123] In the first aspect, the ASF is associated with an application function or a third party server.

[0124] In a second aspect, either alone or in combination with the first aspect, process 1400 includes receiving an initial request for aircraft mobility data from an AMF in the NR network, wherein the initial request originates from one of a UE, a network node, or the AMF, and the request is sent to an ADS-B server based at least in part on the initial request received at the ASF.

[0125] In a third aspect, alone or in combination with one or more of the first and second aspects, the initial request indicates a reference position associated with the UE and a radius associated with the reference position, and the radius indicates a maximum range between the aircraft and the UE.

[0126] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the initial request indicates an aircraft NR identifier associated with the aircraft.

[0127] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, an initial request is received from the UE based at least in part on an AMF notification to the UE indicating that the UE is within a defined distance from an edge of a terrestrial network, and the initial request is received according to a request periodicity based at least in part on downlink signal measurements.

[0128] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 1400 includes filtering aircraft mobility data associated with an aircraft number based at least in part on a reference location and a radius associated with the reference location.

[0129] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 1400 includes sending aircraft mobility data to a NEF in the NR network for mapping between aircraft numbers and aircraft NR identifiers.

[0130] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, process 1400 includes sending aircraft mobility data requested from an ADS-B server to an AMF in an NR network based at least in part on scheduling rather than on an initial request for aircraft mobility data received from one of the AMF, a network node, or a UE.

[0131] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, process 1400 includes receiving an initial request for aircraft mobility data from an AMF in an NR network, wherein the initial request originates from the AMF according to a schedule.

[0132] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the aircraft is an aircraft UE, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the IMSI or GUTI; the aircraft is an aircraft network node, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the global network node identifier; the aircraft is an aircraft network node DU, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the global network node identifier and the network node DU identifier; the aircraft is an aircraft IAB, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the global IAB identifier; the aircraft is an aircraft repeater, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the global repeater identifier; or the aircraft is an aircraft relay, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the global relay identifier.

[0133] although Fig.14 Example blocks of process 1400 are shown, but in some aspects, process 1400 may include Fig.14Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1400. Additionally or alternatively, two or more blocks of the blocks of process 1400 may be performed in parallel.

[0134] Fig.15 1 is a diagram illustrating an example process 1500 performed, for example, by a UE in accordance with the present disclosure. Example process 1500 is an example in which a UE (eg, UE 120) performs operations associated with sending aircraft mobility data to the UE.

[0135] like Fig.15 As shown, in some aspects, process 1500 may include sending an initial request for aircraft mobility data to an ASF in the NR network, where the aircraft mobility data is associated with an aircraft configured to communicate with the UE (block 1510). For example, a UE (e.g., using Fig.17 The communication manager 140 and / or sending component 1704 depicted in FIG. 1 may send an initial request for aircraft mobility data to an ASF in the NR network, where the aircraft mobility data is associated with an aircraft configured to communicate with the UE, as described above.

[0136] like Fig.15 As further shown, in some aspects, process 1500 may include receiving aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number and the aircraft NR identifier indicated by the ADS-B server, and wherein the aircraft number is an aircraft flight number or an aircraft registration number (block 1520). For example, a UE (e.g., using Fig.17 The communication manager 140 and / or receiving component 1702 depicted in FIG. 1 may receive aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by an ADS-B server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number, as described above.

[0137] like Fig.15 As further shown, in some aspects, process 1500 may include performing an action based at least in part on the aircraft mobility data (block 1530). For example, a UE (e.g., using Fig.17 The communication manager 140 and / or action component 1708 depicted in FIG. 1 may perform actions based at least in part on the aircraft mobility data, as described above.

[0138] Process 1500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0139] In a first aspect, process 1500 includes sending an initial request to an ASF via one or more of a network node or an AMF.

[0140] In a second aspect, either alone or in combination with the first aspect, process 1500 includes receiving an AMF notification from an AMF in an NR network indicating that the UE is within a defined distance from an edge of a terrestrial network, wherein an initial request is sent based at least in part on the AMF notification, and the initial request is sent according to a request periodicity based at least in part on downlink signal measurements.

[0141] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1500 includes determining whether the UE is within a coverage area of ​​the aircraft based at least in part on aircraft mobility data, and sending a message based at least in part on determining that the UE is within the coverage area of ​​the aircraft, or employing timing advance and frequency compensation based at least in part on the aircraft mobility data.

[0142] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the ASF is associated with an application function or a third party server.

[0143] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, aircraft mobility data is received from an ADS-B server based at least in part on a request for aircraft mobility data sent to the ADS-B server, wherein the request is based at least in part on an initial request from a UE.

[0144] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the initial request indicates a reference position associated with the UE and a radius associated with the reference position, and the radius indicates a maximum range between the aircraft and the UE.

[0145] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the initial request indicates an aircraft NR identifier associated with the aircraft.

[0146] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 1500 includes receiving aircraft mobility data via a NEF in the NR network associated with a mapping between an aircraft number and an aircraft NR identifier.

[0147] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the aircraft is an aircraft UE, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the IMSI or GUTI; the aircraft is an aircraft network node, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the global network node identifier; the aircraft is an aircraft network node DU, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the global network node identifier and the network node DU identifier; the aircraft is an aircraft IAB, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the global IAB identifier; the aircraft is an aircraft repeater, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the global repeater identifier; or the aircraft is an aircraft relay, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on the mapping between the aircraft registration number and the global relay identifier.

[0148] although Fig.15 Example blocks of process 1500 are shown, but in some aspects, process 1500 may include Fig.15 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1500. Additionally or alternatively, two or more blocks of the blocks of process 1500 may be performed in parallel.

[0149] Fig.16 1 is a diagram of an example apparatus 1600 for wireless communication according to the present disclosure. Apparatus 1600 may be an ASF in an NR network, or an ASF in an NR network may include apparatus 1600. In some aspects, apparatus 1600 includes a receiving component 1602 and a sending component 1604, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1600 may communicate with another apparatus 1606 (such as a UE, a base station, or another wireless communication device) using receiving component 1602 and sending component 1604. As further shown, apparatus 1600 may include a communication manager 150. Communication manager 150 may include filter component 1608, etc.

[0150] In some aspects, the apparatus 1600 may be configured to perform Figures 6 to 13 Additionally or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as Fig.14 In some aspects, the apparatus 1600 and / or Fig.16 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig.16 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0151] The receiving component 1602 may receive communications from the device 1606, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1602 may provide the received communications to one or more other components of the device 1600. In some aspects, the receiving component 1602 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1600. In some aspects, the receiving component 1602 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described ASF.

[0152] Transmit component 1604 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1606. In some aspects, one or more other components of device 1600 may generate communications and may provide the generated communications to transmit component 1604 for transmission to device 1606. In some aspects, transmit component 1604 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1606. In some aspects, transmit component 1604 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described ASF. In some aspects, the transmit component 1604 can be co-located with the receive component 1602 in a transceiver.

[0153] The sending component 1604 can send a request for aircraft mobility data to the ADS-B server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE. The receiving component 1602 can receive the aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number. The sending component 1604 can send the aircraft mobility data to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier.

[0154] The receiving component 1602 may receive an initial request for aircraft mobility data from an AMF in the NR network, wherein the initial request originates from one of a UE, a network node, or an AMF, and the request is sent to an ADS-B server based at least in part on the initial request received at the ASF in the NR network. The filter component 1608 may filter the aircraft mobility data associated with the aircraft number based at least in part on a reference location and a radius associated with the reference location. The receiving component 1602 may receive an initial request for aircraft mobility data from an AMF in the NR network, wherein the initial request originates from the AMF according to a schedule.

[0155] Fig.16 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.16 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.16 Two or more components shown may be implemented in a single component, or Fig.16 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.16 The assembly (one or more components) shown may be described as being executable by Fig.16 Another collection of components shown performs one or more functions.

[0156] Fig.171 is a diagram of an example apparatus 1700 for wireless communication according to the present disclosure. Apparatus 1700 may be a UE, or a UE may include apparatus 1700. In some aspects, apparatus 1700 includes a receiving component 1702 and a sending component 1704, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1700 may communicate with another apparatus 1706 (such as a UE, a base station, or another wireless communication device) using receiving component 1702 and sending component 1704. As further shown, apparatus 1700 may include a communication manager 140. Communication manager 140 may include action component 1708, etc.

[0157] In some aspects, the apparatus 1700 may be configured to perform Figures 6 to 13 Additionally or alternatively, the apparatus 1700 may be configured to perform one or more processes described herein, such as Fig.15 In some aspects, the apparatus 1700 and / or Fig.17 One or more of the components shown in the figure may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Fig.17 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0158] The receiving component 1702 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1706. The receiving component 1702 may provide the received communications to one or more other components of the device 1700. In some aspects, the receiving component 1702 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1700. In some aspects, the receiving component 1702 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0159] The transmitting component 1704 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1706. In some aspects, one or more other components of the device 1700 may generate communications and may provide the generated communications to the transmitting component 1704 for transmission to the device 1706. In some aspects, the transmitting component 1704 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1706. In some aspects, the transmitting component 1704 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 1704 can be co-located with the receive component 1702 in a transceiver.

[0160] The sending component 1704 can send an initial request for aircraft mobility data to an ASF in the NR network, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE. The receiving component 1702 can receive the aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by an ADS-B server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number. The action component 1708 can perform an action based at least in part on the aircraft mobility data.

[0161] Fig.17 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.17 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.17 Two or more components shown may be implemented in a single component, or Fig.17 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.17 The assembly (one or more components) shown may be described as being executable by Fig.17 Another collection of components shown performs one or more functions.

[0162] The following provides an overview of some aspects of the disclosure:

[0163] Aspect 1: A method of wireless communication performed by an aircraft surveillance function (ASF) in a new radio (NR) network, comprising: sending a request for aircraft mobility data to an automatic dependent surveillance-broadcast (ADS-B) server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with a user equipment (UE); receiving the aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and sending the aircraft mobility data to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier.

[0164] Aspect 2: The method according to aspect 1, wherein the ASF is associated with an application function or a third-party server.

[0165] Aspect 3: The method according to any one of Aspects 1 to 2 further includes: receiving an initial request for the aircraft mobility data from an access and mobility management function (AMF) in the NR network, wherein the initial request originates from one of the UE, the network node or the AMF, and wherein the request is sent to the ADS-B server based at least in part on the initial request received at the ASF.

[0166] Aspect 4: The method according to aspect 3, wherein the initial request indicates a reference position associated with the UE and a radius associated with the reference position, and wherein the radius indicates a maximum range between the aircraft and the UE.

[0167] Aspect 5: The method according to aspect 3, wherein the initial request indicates the aircraft NR identifier associated with the aircraft.

[0168] Aspect 6: A method according to Aspect 3, wherein the initial request is received from the UE based at least in part on an AMF notification to the UE, the AMF notification indicating that the UE is within a defined distance from an edge of a terrestrial network, and wherein the initial request is received based on a request periodicity based at least in part on downlink signal measurements.

[0169] Aspect 7: The method according to any one of aspects 1 to 6, further comprising: filtering the aircraft mobility data associated with the aircraft number based at least in part on a reference position and a radius associated with the reference position.

[0170] Aspect 8: The method according to any one of Aspects 1 to 7, wherein sending the aircraft mobility data comprises sending the aircraft mobility data to a network openness function (NEF) in the NR network for the mapping between the aircraft number and the aircraft NR identifier.

[0171] Aspect 9: A method according to any one of Aspects 1 to 8, wherein sending the aircraft mobility data includes sending the aircraft mobility data requested from the ADS-B server to the access and mobility management function (AMF) in the NR network based at least in part on scheduling rather than based on an initial request for the aircraft mobility data received from one of the AMF, the network node, or the UE.

[0172] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: receiving an initial request for the aircraft mobility data from an access and mobility management function (AMF) in the NR network, wherein the initial request originates from the AMF according to scheduling.

[0173] Aspect 11: A method according to any one of aspects 1 to 10, wherein: the aircraft is an aircraft UE, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on a mapping between the aircraft registration number and an international mobile subscriber identity or a globally unique temporary identifier; the aircraft is an aircraft network node, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on a mapping between the aircraft registration number and a global network node identifier; the aircraft is an aircraft network node distributed unit (DU), and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on a mapping between the aircraft registration number and a global network node identifier. a mapping between a global network node identifier and a network node DU identifier; the aircraft is an aircraft integrated access and backhaul (IAB), and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global IAB identifier; the aircraft is an aircraft repeater, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global repeater identifier; or the aircraft is an aircraft relay, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global relay identifier.

[0174] Aspect 12: A method of wireless communication performed by a user equipment (UE), comprising: sending an initial request for aircraft mobility data to an aircraft surveillance function (ASF) in a new radio (NR) network, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE; receiving aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by a broadcast automatic dependent surveillance (ADS-B) server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and performing an action based at least in part on the aircraft mobility data.

[0175] Aspect 13: The method according to aspect 12, wherein sending the initial request comprises sending the initial request to the ASF via one or more of a network node or an access and mobility management function.

[0176] Aspect 14: The method according to any one of Aspects 12 to 13 further includes: receiving an AMF notification from an access and mobility management function (AMF) in the NR network indicating that the UE is within a limited distance from the edge of the terrestrial network, wherein the initial request is sent at least in part based on the AMF notification, and wherein the initial request is sent according to a request periodicity based at least in part on downlink signal measurement.

[0177] Aspect 15: A method according to any one of Aspects 12 to 14, wherein performing the action includes: determining whether the UE is within the coverage area of ​​the aircraft based at least in part on the aircraft mobility data, and sending a message based at least in part on determining that the UE is within the coverage area of ​​the aircraft; or adopting timing advance and frequency compensation based at least in part on the aircraft mobility data.

[0178] Aspect 16: The method according to any one of Aspects 12 to 15, wherein the ASF is associated with an application function or a third-party server.

[0179] Aspect 17: A method according to any one of Aspects 12 to 16, wherein the aircraft mobility data is received from the ADS-B server based at least in part on a request for aircraft mobility data sent to the ADS-B server, wherein the request is based at least in part on the initial request from the UE.

[0180] Aspect 18: The method according to any one of aspects 12 to 17, wherein the initial request indicates a reference position associated with the UE and a radius associated with the reference position, and wherein the radius indicates a maximum range between the aircraft and the UE.

[0181] Aspect 19: The method according to any one of aspects 12 to 18, wherein the initial request indicates the aircraft NR identifier associated with the aircraft.

[0182] Aspect 20: A method according to any one of Aspects 12 to 19, wherein receiving the aircraft mobility data comprises receiving the aircraft mobility data via a network exposure function (NEF) in the NR network associated with the mapping between the aircraft number and the aircraft NR identifier.

[0183] Aspect 21: A method according to any one of Aspects 12 to 20, wherein: the aircraft is an aircraft UE, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on a mapping between the aircraft registration number and an international mobile subscriber identity or a globally unique temporary identifier; the aircraft is an aircraft network node, and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on a mapping between the aircraft registration number and a global network node identifier; the aircraft is an aircraft network node distributed unit (DU), and the mapping between the aircraft number and the aircraft NR identifier is at least partially based on a mapping between the aircraft registration number and a global network node identifier. a mapping between a global network node identifier and a network node DU identifier; the aircraft is an aircraft integrated access and backhaul (IAB), and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global IAB identifier; the aircraft is an aircraft repeater, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global repeater identifier; or the aircraft is an aircraft relay, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global relay identifier.

[0184] Aspect 22: An apparatus for wireless communication at a device, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 11.

[0185] Aspect 23: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 11.

[0186] Aspect 24: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 1 to 11.

[0187] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 11.

[0188] Aspect 26: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 11.

[0189] Aspect 27: An apparatus for wireless communication at a device, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 12 to 21.

[0190] Aspect 28: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 12 to 21.

[0191] Aspect 29: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 12 to 21.

[0192] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 12 to 21.

[0193] Aspect 31: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 12 to 21.

[0194] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the foregoing disclosure or may be acquired from practice of the various aspects.

[0195] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

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

[0197] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0198] Any element, action or instruction used herein should not be interpreted as critical or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at an aircraft surveillance function (ASF) in a new radio (NR) network, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: sending a request for aircraft mobility data to an automatic dependent surveillance-broadcast (ADS-B) server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with a user equipment (UE); receiving the aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; as well as The aircraft mobility data is sent to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier.

2. The apparatus according to claim 1, wherein the ASF is associated with an application function or a third-party server.

3. The apparatus of claim 1 , wherein the one or more processors are further configured to: An initial request for the aircraft mobility data is received from an access and mobility management function (AMF) in the NR network, wherein the initial request originates from one of the UE, a network node, or the AMF, and wherein the request is sent to the ADS-B server based at least in part on the initial request received at the ASF.

4. The apparatus of claim 3, wherein the initial request indicates a reference location associated with the UE and a radius associated with the reference location, and wherein the radius indicates a maximum range between the aircraft and the UE.

5. The apparatus of claim 3, wherein the initial request indicates the aircraft NR identifier associated with the aircraft.

6. The apparatus of claim 3 , wherein the initial request is received from the UE based at least in part on an AMF notification to the UE, the AMF notification indicating that the UE is within a defined distance from an edge of a terrestrial network, and wherein the initial request is received according to a request periodicity based at least in part on downlink signal measurements.

7. The apparatus of claim 1 , wherein the one or more processors are further configured to: The aircraft mobility data associated with the aircraft number is filtered based at least in part on a reference location and a radius associated with the reference location.

8. The apparatus of claim 1 , wherein to send the aircraft mobility data, the one or more processors are configured to send the aircraft mobility data to a network open function (NEF) in the NR network for the mapping between the aircraft number and the aircraft NR identifier.

9. The apparatus of claim 1 , wherein the one or more processors are further configured to: An initial request for the aircraft mobility data is received from an access and mobility management function (AMF) in the NR network, wherein the initial request originates from the AMF according to a schedule.

10. The apparatus of claim 1 , wherein the one or more processors are configured to send the aircraft mobility data requested from the ADS-B server to an access and mobility management function (AMF) in the NR network based at least in part on scheduling rather than based on an initial request for the aircraft mobility data received from one of the AMF, a network node, or the UE.

11. The device according to claim 1, wherein: The aircraft is an aircraft UE, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and an International Mobile Subscriber Identity or a Globally Unique Temporary Identifier; The aircraft is an aircraft network node, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global network node identifier; The aircraft is an aircraft network node distributed unit (DU), and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global network node identifier and a network node DU identifier; the aircraft being an aircraft Integrated Access and Backhaul (IAB), and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global IAB identifier; The aircraft is an aircraft repeater, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global repeater identifier; or The aircraft is an aircraft relay, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global relay identifier.

12. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: sending an initial request for aircraft mobility data to an aircraft surveillance function (ASF) in a new radio (NR) network, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE; receiving aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by an Automatic Dependent Surveillance-Broadcast (ADS-B) server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and An action is performed based at least in part on the aircraft mobility data.

13. The apparatus of claim 12, wherein to send the initial request, the one or more processors are configured to send the initial request to the ASF via one or more of a network node or an access and mobility management function.

14. The apparatus of claim 12, wherein the one or more processors are further configured to: Receiving an AMF notification from an access and mobility management function (AMF) in the NR network indicating that the UE is within a defined distance from an edge of a terrestrial network, wherein the initial request is sent at least in part based on the AMF notification, and wherein the initial request is sent according to a request periodicity based at least in part on downlink signal measurements.

15. The apparatus of claim 12, wherein to perform the actions, the one or more processors are configured to: determining whether the UE is within a coverage area of ​​the aircraft based at least in part on the aircraft mobility data, and sending a message based at least in part on determining that the UE is within the coverage area of ​​the aircraft; or Timing advance and frequency compensation are employed based at least in part on the aircraft mobility data.

16. The apparatus of claim 12, wherein the ASF is associated with an application function or a third-party server.

17. The apparatus of claim 12, wherein the aircraft mobility data is received from the ADS-B server based at least in part on a request for aircraft mobility data sent to the ADS-B server, wherein the request is based at least in part on the initial request from the UE.

18. The apparatus of claim 12, wherein the initial request indicates a reference location associated with the UE and a radius associated with the reference location, and wherein the radius indicates a maximum range between the aircraft and the UE.

19. The apparatus of claim 12, wherein the initial request indicates the aircraft NR identifier associated with the aircraft.

20. The apparatus of claim 12, wherein to receive the aircraft mobility data, the one or more processors are configured to receive the aircraft mobility data via a network exposure function (NEF) in the NR network associated with the mapping between the aircraft number and the aircraft NR identifier.

21. The apparatus of claim 12, wherein: The aircraft is an aircraft UE, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and an International Mobile Subscriber Identity or a Globally Unique Temporary Identifier; The aircraft is an aircraft network node, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global network node identifier; The aircraft is an aircraft network node distributed unit (DU), and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global network node identifier and a network node DU identifier; the aircraft being an aircraft Integrated Access and Backhaul (IAB), and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global IAB identifier; The aircraft is an aircraft repeater, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global repeater identifier; or The aircraft is an aircraft relay, and the mapping between the aircraft number and the aircraft NR identifier is based at least in part on a mapping between the aircraft registration number and a global relay identifier.

22. A method of wireless communication performed by an aircraft surveillance function (ASF) in a new radio (NR) network, comprising: sending a request for aircraft mobility data to an automatic dependent surveillance-broadcast (ADS-B) server, wherein the aircraft mobility data is associated with an aircraft configured to communicate with a user equipment (UE); receiving the aircraft mobility data from the ADS-B server and based at least in part on the request, wherein the aircraft mobility data indicates an aircraft number associated with the aircraft, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; as well as The aircraft mobility data is sent to the UE, wherein the aircraft mobility data indicates an aircraft NR identifier, and wherein the aircraft NR identifier is based at least in part on a mapping between the aircraft number and the aircraft NR identifier.

23. The method according to claim 22, further comprising: An initial request for the aircraft mobility data is received from an access and mobility management function (AMF) in the NR network, wherein the initial request originates from one of the UE, a network node, or the AMF, and wherein the request is sent to the ADS-B server based at least in part on the initial request received at the ASF.

24. The method of claim 22, further comprising: The aircraft mobility data associated with the aircraft number is filtered based at least in part on a reference location and a radius associated with the reference location.

25. The method of claim 22, wherein sending the aircraft mobility data comprises sending the aircraft mobility data to a network opening function (NEF) in the NR network for the mapping between the aircraft number and the aircraft NR identifier.

26. A method of wireless communication performed by a user equipment (UE), comprising: sending an initial request for aircraft mobility data to an aircraft surveillance function (ASF) in a new radio (NR) network, wherein the aircraft mobility data is associated with an aircraft configured to communicate with the UE; receiving aircraft mobility data from the ASF and based at least in part on the initial request, wherein the aircraft mobility data indicates an aircraft NR identifier associated with the aircraft, wherein the aircraft NR identifier is based at least in part on a mapping between an aircraft number indicated by an Automatic Dependent Surveillance-Broadcast (ADS-B) server and the aircraft NR identifier, and wherein the aircraft number is an aircraft flight number or an aircraft registration number; and An action is performed based at least in part on the aircraft mobility data.

27. The method of claim 26, wherein sending the initial request comprises sending the initial request to the ASF via one or more of a network node or an access and mobility management function.

28. The method of claim 26, further comprising: Receiving an AMF notification from an access and mobility management function (AMF) in the NR network indicating that the UE is within a defined distance from an edge of a terrestrial network, wherein the initial request is sent at least in part based on the AMF notification, and wherein the initial request is sent according to a request periodicity based at least in part on downlink signal measurements.

29. The method of claim 26, wherein performing the action comprises: determining whether the UE is within a coverage area of ​​the aircraft based at least in part on the aircraft mobility data, and sending a message based at least in part on determining that the UE is within the coverage area of ​​the aircraft; or Timing advance and frequency compensation are employed based at least in part on the aircraft mobility data.

30. The method of claim 26, wherein receiving the aircraft mobility data comprises receiving the aircraft mobility data via a network exposure function (NEF) in the NR network associated with the mapping between the aircraft number and the aircraft NR identifier.

Images