Flight path server in core network

Abstract

An apparatus may be a first network entity configured to: receive first information regarding a flight path of at least one wireless device from a second network entity or a first wireless device; receiving, from the second network entity or the first wireless device, an indication of storing second information regarding the flight path of the at least one wireless device based on the first information; and transmitting third information about the flight path of the at least one wireless device to a third network entity based on the second information. An apparatus may be a second network entity configured to: receive first information regarding a flight path of at least one wireless device from a first wireless device; and sending, to the first network entity, an indication of storing second information regarding the flight path of the at least one wireless device.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of Greek Patent Application Serial No. 20220100920, filed on November 9, 2022, entitled "FLIGHTPATH SERVER IN CORE NETWORK", which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to communication systems, and more particularly to communication and control systems related to unmanned aerial vehicles (UAVs).

[0004] Introduction

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple access techniques capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access techniques include code - division multiple access (CDMA) systems, time - division multiple access (TDMA) systems, frequency - division multiple access (FDMA) systems, orthogonal frequency - division multiple access (OFDMA) systems, single - carrier frequency - division multiple access (SC - FDMA) systems, and time - division synchronous code - division multiple access (TD - SCDMA) systems.

[0006] These multiple access techniques have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., related to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine - type communication (mMTC), and ultra - reliable low - latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long - Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access techniques and telecommunication standards that employ these techniques. Summary of the Invention

[0007] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary of the invention is not an extensive review of all contemplated aspects. This summary of the invention neither identifies key or critical elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a first network entity configured to receive first information about a flight path of at least one wireless device from a second network entity or a first wireless device. The apparatus may also be configured to receive, based on the first information, an indication from the second network entity or the first wireless device to store second information about the flight path of the at least one wireless device. The apparatus may further be configured to send third information about the flight path of the at least one wireless device to a third network entity based on the second information.

[0009] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a second network entity configured to receive first information about a flight path of at least one wireless device from a first wireless device. The apparatus may also be configured to send an indication to store second information about the flight path of the at least one wireless device to a first network entity.

[0010] To achieve the foregoing and related purposes, one or more aspects include the features described comprehensively below and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0012] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0013] Figure 2B is a diagram illustrating an example of a downlink (DL) channel within a subframe according to various aspects of the present disclosure.

[0014] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0015] Figure 2D is a diagram illustrating an example of an uplink (UL) channel within a subframe according to various aspects of the present disclosure.

[0016] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0017] Figure 4 is a diagram illustrating an example of UE positioning based on reference signal measurements.

[0018] Figure 5 It is a call flow diagram illustrating the FP information storage, FP information authorization, and / or FP information verification functions in an environment according to some aspects of the present disclosure.

[0019] Figure 6 It is a call flow diagram illustrating the FP information storage and retrieval functions of the FP information authorization and / or FP information verification functions in an environment according to some aspects of the present disclosure.

[0020] Figure 7 It is a call flow diagram illustrating the FP information storage and retrieval functions of the FP information authorization and / or FP information verification functions in an environment according to some aspects of the present disclosure.

[0021] Figure 8 Illustrates components of a system including a UAS-NF according to some aspects of the present disclosure, where the UAS-NF implements an FP server that interacts with an external server USS and a core network associated with the NG-RAN and at least one UE / UAV.

[0022] Figure 9 It is a flowchart of a method for wireless communication.

[0023] Figure 10 It is a flowchart of a method for wireless communication.

[0024] The component can be an FP server component of the network entity 1460 configured to perform the functions described in conjunction with Figures 9 to 1 1 and recited by the component.

[0025] Figure 11A It is a flowchart of a method for wireless communication.

[0026] Figure 11B It is a flowchart of a method for wireless communication.

[0027] Figure 12 It is a flowchart of a method for wireless communication.

[0028] Figure 13 It is a flowchart of a method for wireless communication.

[0029] Figure 14 It is a diagram illustrating an example of the hardware implementation for a network entity.

[0030] Figure 15 It is a diagram illustrating an example of the hardware implementation for a network entity. Detailed Description

[0031] In some aspects of wireless communication, a wireless device such as a user equipment (UE) or a UAV may report flight path (FP) information to a radio access network (RAN) and an access and mobility management function (AMF) of a core network. The radio access network (RAN) and / or the AMF may not store the FP information for later use and may subsequently request the FP information from the UE or the UAV, for example, via an air interface and / or radio resource control (RRC) signaling. Thus, the FP information may be unavailable, or if the context of the UE or the UAV is lost at a RAN node or the AMF, for example, if the UE or the UAV is in the RRC IDLE mode or is handed over to another cell for service. In some aspects, the FP information may also be provided to an external server, such as a UAV management server (UAS) service provider (USS) or a drone system traffic management (UTM) server, for coordination among UAVs associated with different networks (e.g., the RAN). In some aspects, the USS or the UTM server may be, for example, a country-specific service provider or server associated with a civil aviation authority. In some aspects, an FP server may be provided in the core network to store the FP information received from one or more of the UE, the UAV, the USS, the UTM, or other sources and to provide FP information management in the core network.

[0032] The detailed description set forth below in connection with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. For a thorough understanding of the various concepts, the detailed description includes specific details. However, the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0033] Certain aspects of a telecommunications system are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the drawings by various blocks, components, circuits, processes, algorithms, etc., collectively referred to as "elements". These elements may be implemented using either electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

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

[0035] Thus, in one or more example aspects, embodiments, and / or use cases, the described functions can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. As an example, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium capable of storing computer-executable code in the form of instructions or data structures that can be accessed by a computer.

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

[0037] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functionality may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc.) may be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

[0038] A centralized base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0039] Base station operation or network design may consider the aggregation characteristics of base station functionality. For example, a split base station may be used in an integrated access backhaul (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)). Splitting may include distributing functions across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which may enable flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0040] Figure 1 FIG. 100 is a diagram illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a split base station architecture. The split base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 through one or more split base station units, such as a near-real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via a respective midhaul link, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via a respective fronthaul link. The RU 140 may communicate with a respective UE 104 via one or more radio frequency (RF) access links. In some embodiments, the UE 104 may be served simultaneously by multiple RUs 140.

[0041] Each unit (i.e., CU 110, DU 130, RU 140, and the near RT RIC 125, non-RT RIC 115, and SMO framework 105) may include one or more interfaces or be coupled to one or more interfaces that are 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 the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive signals or transmit signals to one or more of the other units via the wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) that is configured to receive and / or transmit signals to one or more of the other units via the wireless transmission medium.

[0042] In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, the CU 110 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 units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0043] The DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high Physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially based on a functional split (such as those defined by 3GPP). In some aspects, the DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0044] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both, at least in part based on function splitting (such as lower layer function splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0045] The SMO framework 105 may be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 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 the O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 110, the DU 130, the RU 140, and the near RT RIC 125. In some embodiments, the SMO framework 105 may communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some embodiments, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.

[0046] The non-RT RIC 115 can be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125 (such as via the A1 interface). The near-RT RIC 125 can 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 the E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB to the near-RT RIC 125.

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

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

[0049] Some UEs 104 may use device-to-device (D2D) communication links 158 to communicate with each other. D2D communication links 158 may use DL / UL wireless wide area network (WWAN) spectrum. D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through various wireless D2D communication systems, such as for example Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, LTE, or NR.

[0050] The wireless communication system may also include a Wi-Fi AP 150 that communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, e.g., in the 5 GHz unlicensed spectrum, etc. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0051] The electromagnetic spectrum is generally subdivided into various categories, frequency bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally referred to (interchangeably) as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is generally (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 by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0052] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating frequency bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz - 24.25 GHz). The bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as Frequency Range Designation FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0053] Considering the above aspects, unless otherwise specifically stated, if the term "sub-6 GHz" etc. is used herein, it may broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" etc. is used herein, it may broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

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

[0055] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission and reception point (TRP), network node, network entity, network equipment, or some other suitable term. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including CU and DU) and an RU, or as a disaggregated base station including one or more of CU, DU, and / or RU. A set of base stations including disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0056] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, a UAS 167, one or more location servers 168, and other functional entities. The AMF 161 is a control node that processes signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of Authentication and Key Agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, in general, one or more location servers 168 may include one or more location / locationing servers, which may include one or more of the GMLC 165, the LMF 166, a Position Determination Entity (PDE), a Serving Mobile Location Center (SMLC), a Mobile Positioning Center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, location estimation, and optional speed calculations based on these measurements. The signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a Satellite Positioning System (SPS) 170 (e.g., a Global Navigation Satellite System (GNSS), a Global Positioning System (GPS), a Non-Terrestrial Network (NTN), or one or more of other satellite positioning / location systems), an LTE signal, a Wireless Local Area Network (WLAN) signal, a Bluetooth signal, a Terrestrial Beacon System (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR Enhanced Cell ID (NR E-CID) method, an NR signal (e.g., multi-round-trip time (multi-RTT), DL Angle of Departure (DL-AoD), DL Time Difference of Arrival (DL-TDOA), UL Time Difference of Arrival (UL-TDOA), and UL Angle of Arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0057] In some aspects, the core network components can interact with components of the external network 194. The external network can include a USS 196 or a UTM server (not shown). The external network 194 can be associated with the management function of the UAVs associated with the core network 120.

[0058] Examples of UEs 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar function devices. Some of the UEs in the UEs 104 can be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). The UEs 104 can also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, radio units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, cell phones, user agents, mobile clients, clients, or some other suitable term. In some scenarios, the term UE can also apply to one or more companion devices, such as in a device cluster arrangement. One or more of these devices can access the network jointly and / or access the network individually.

[0059] See again Figure 1, in some aspects, the core network 120 may be configured with a UAS 167 including an FP server component 198, which may be configured to receive first information about the flight path of at least one wireless device from a second network entity or a first wireless device. The FP server component 198 may also be configured to receive, based on the first information, an indication from the second network entity or the first wireless device to store second information about the flight path of the at least one wireless device. The FP server component 198 may also be configured to send third information about the flight path of the at least one wireless device to a third network entity based on the second information. In some aspects, the core network 120 may also be configured with an AMF 161 and / or an LMF 166 that may include a UAV FP component 199, which may be configured to receive first information about the flight path of at least one wireless device from a first wireless device. The UAV FP component 199 may also be configured to send an indication to a first network entity to store second information about the flight path of the at least one wireless device. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar domains, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0060] Figure 2A FIG. 200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG. 230 is a diagram illustrating an example of a DL channel within a 5G NR subframe. Figure 2C FIG. 250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG. 280 is a diagram illustrating an example of a UL channel within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexing (FDD) (where, for a specific set of subcarriers (carrier system bandwidth), the subframes within the set of subcarriers are dedicated to DL or UL), or may be time division duplexing (TDD) (where, for a specific set of subcarriers (carrier system bandwidth), the subframes within the set of subcarriers are dedicated to both DL and UL). In Figure 2A 、 Figure 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (where most are DL), where D is DL, U is UL, and F is flexibly available between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0 and 1 are all-DL and all-UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with the slot format by receiving a slot format indicator (SFI) (configured dynamically via downlink control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0061] Figures 2A to 2D The frame structure is illustrated, and aspects of the present disclosure can apply to other wireless communication technologies that may have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe can include one or more slots. A subframe can also include mini-slots, which can include 7, 4, or 2 symbols. Each slot can include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot can include 14 symbols, and for extended CP, each slot can include 12 symbols. The symbols on the DL can be cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) symbols. The symbols on the UL can be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled with 1 / SCS.

[0062]

[0063] Table 1: Parameter Sets, SCS, and CP

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

[0065] A resource grid can be used to represent the frame structure. Each time slot includes resource blocks (RBs) (also referred to as physical RBs (PRBs)) that extend over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0066] As Figure 2A illustrated, some of the REs carry reference (pilot) signals (RSs) for the UE. The RSs can include demodulation RSs (DM-RSs) (designated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs) for channel estimation at the UE. The RSs can also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0067] Figure 2BIllustrates examples of various DL channels within a subframe of a frame. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), where each CCE includes six Resource Element Groups (REGs), and each REG includes 12 consecutive Resource Elements (REs) in the OFDM symbols of an RB. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., common search space, UE-specific search space) during the PDCCH monitoring occasion on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) can be in symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine subframe / symbol timing and the physical layer identity. The Secondary Synchronization Signal (SSS) can be in symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of RBs in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

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

[0069] Figure 2DIllustrates examples of various UL channels within a subframe of a frame. The PUCCH can be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0070] Figure 3 Is a block diagram of communication between a base station 310 in an access network and a UE 350. In the DL, Internet Protocol (IP) packets can be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with the broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0071] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to signal constellations based on various modulation schemes such as binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM). The encoded and modulated symbols may then be split into parallel streams. Subsequently, each stream may be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is precoded in space to generate multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the encoding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 350 and / or channel state feedback. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with the corresponding spatial stream for transmission.

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

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

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

[0075] Channel estimates derived by the channel estimator 358 based on reference signals or feedback sent by the base station 310 may be used by the TX processor 368 to select appropriate decoding and modulation schemes and facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via a separate transmitter 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

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

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

[0078] At least one of TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects in conjunction with Figure 1 FP server component 198.

[0079] At least one of TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects in conjunction with Figure 1 UAV FP component 199.

[0080] Figure 4 FIG. 400 is a diagram illustrating an example of UE positioning based on reference signal measurements. UE 404 may transmit UL-SRS 412 at time T SRS_TX and receive a downlink positioning reference signal (PRS) (DL-PRS) 410 at time T PRS_RX . TRP 406 may receive UL-SRS 412 at time T SRS_RX and transmit DL-PRS 410 at time T PRS_TX . UE 404 may receive DL-PRS 410 before transmitting UL-SRS 412, or may transmit UL-SRS 412 before receiving DL-PRS 410. In both cases, a positioning server (e.g., location server 168) or UE 404 may determine RTT 414 based on ||T SRS_RX - T PRS_TX |-|T SRS_TX - T PRS_RX ||. Thus, multi-RTT positioning may utilize the UE Rx-Tx time difference measurement of downlink signals received from multiple TRPs 402, 406 and measured by UE 404 (i.e., |T SRS_TX - T PRS_RX |) and the DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), as well as the measured TRP Rx-Tx time difference measurement of uplink signals transmitted from UE 404 at multiple TRPs 402, 406 (i.e., |T SRS_RX - T PRS_TX |) and UL-SRS-RSRP. UE 404 uses the assistance data received from the positioning server to measure the UE Rx-Tx time difference measurement (and the DL-PRS-RSRP of the received signal), and TRPs 402, 406 use the assistance data received from the positioning server to measure the gNB Rx-Tx time difference measurement (and the UL-SRS-RSRP of the received signal). These measurements may be used at the positioning server or UE 404 to determine the RTT, which is used to estimate the location of UE 404. Other methods for determining the RTT are possible, such as using DL-TDOA and / or UL-TDOA measurements.

[0081] DL-AoD positioning can utilize the measured DL-PRS-RSRP of the downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 uses the assistance data received from the positioning server to measure the DL-PRS-RSRP of the received signals, and the resulting measurements, together with the azimuth of departure (A-AoD), zenith angle of departure (Z-AoD), and other configuration information, are used to position the UE 404 relative to the neighboring TRPs 402, 406.

[0082] DL-TDOA positioning can utilize the DL reference signal time difference (RSTD) (and DL-PRS-RSRP) of the downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 uses the assistance data received from the positioning server to measure the DL RSTD (and DL-PRS-RSRP) of the received signals, and the resulting measurements, together with other configuration information, are used to position the UE 404 relative to the neighboring TRPs 402, 406.

[0083] UL-TDOA positioning can utilize the UL relative time of arrival (RTOA) (and UL-SRS-RSRP) of the uplink signals transmitted from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 use the assistance data received from the positioning server to measure the UL-RTOA (and UL-SRS-RSRP) of the received signals, and the resulting measurements, together with other configuration information, are used to estimate the location of the UE 404.

[0084] UL-AoA positioning can utilize the measured azimuth of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of the uplink signals transmitted from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 use the assistance data received from the positioning server to measure the A-AoA and Z-AoA of the received signals, and the resulting measurements, together with other configuration information, are used to estimate the location of the UE 404.

[0085] Additional positioning methods can be used to estimate the location of the UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. Note that data / measurements from various techniques can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / complete measurements, and / or replace / provide missing information.

[0086] In some aspects of wireless communication, a wireless device such as a UE or UAV can send to the AMF of the RAN and the core network (e.g., Figure 1The AMF 161) reports FP information. The RAN and / or AMF may not store the FP information for later use and may subsequently request the FP information from the UE or UAV, for example, via the air interface and / or RRC signaling. Therefore, the FP information may be unavailable, or if the context of the UE or UAV is lost at the RAN node or AMF, for example, if the UE or UAV is in the RRC IDLE mode or handed over to another cell for service. In some aspects, the FP information may also be provided to an external server, such as a USS or UTM server, for coordination between UAVs associated with different networks (e.g., the RAN). In some aspects, the USS or UTM server may be, for example, a country-specific service provider or server associated with a civil aviation authority.

[0087] In some aspects, a UAS network function (UAS-NF) may be provided within the core network to serve UAVs and / or UEs associated with the core network. The UAS-NF may be associated with the core network and may be supported by the network exposure function (NEF) and / or the service capability exposure function (SCEF) of the core network. In some aspects, the UAS-NF may use the NEF and / or SCEF exposure services for UAV authentication and / or authorization, UAV flight authorization, UAV-UAV controller (UAV-UAVC) pairing authorization, related re-authentication and / or re-authorization or revocation. In some aspects, the UAS-NF may use the NEF and / or SCEF for location reporting, presence monitoring, obtaining a list of airborne UEs in a geographical area and QoS control, and / or traffic filtering for command and control (C2) communication. In some aspects, the UAS-NF may coordinate with the USS to assist in UAV ID assignment at the civil aviation authority (CAA) level. Figures 5 to 7 Illustrates different functions that may be provided and / or implemented by an FP server implemented in the UAS-NF.

[0088] Figure 5FIG. 500 is a call flow diagram illustrating FP information storage and FP information authorization and / or FP information verification functions in an environment according to some aspects of the present disclosure. In some aspects, the UE / UAV 502 may send FP information 512 to an associated RAN 504 (e.g., NG-RAN). In some aspects, the UE / UAV 502 may be a UE, UAV, drone, or other component of the RAN 504. In some aspects, the FP information 512 provided by the UE / UAV 502 may indicate and / or identify a sequence of waypoints. In some aspects, the waypoint may be a location associated with a planned flight path. In some aspects, the sequence of waypoints may be represented by one or more geographical area descriptions (GADs). In some aspects, for example, for a Universal Mobile Telecommunications System (UMTS), the waypoint may be indicated via one or more of the following: ellipsoidal point, ellipsoidal point with an uncertainty circle, ellipsoidal point with an uncertainty ellipse, polygon, ellipsoidal point with altitude, ellipsoidal point with altitude and uncertainty ellipsoid, or ellipsoidal arc. In some aspects, the sequence of waypoints may be associated with a set of timestamps (e.g., a sequence of timestamps corresponding to the sequence of waypoints). In some aspects, the set of timestamps may include one or more of an absolute timestamp (e.g., a timestamp represented relative to a global reference frame or a shared reference frame) or a relative time (e.g., a timestamp represented relative to the local time maintained at the UE / UAV 502 or relative to the start or end waypoint of the FP). The FP information 512 may also include at least one ID of the UE / UAV 502. In some aspects, the at least one ID may be one of a Generic Public Subscription Identifier (GPSI) or a Subscription Permanent Identifier (SUPI). In some aspects, the FP information 512 may be provided in a first format associated with the UE / UAV 502 or the RAN 504.

[0089] In some aspects, the RAN 504 may then provide the FP information 514 (e.g., the FP information 512 provided by the UE / UAV 502) to the core network (CN) 506 (e.g., the AMF). The CN 506 may send the FP information 516 to the UAS-NF 507 via the Nnef 508 (e.g., an interface provided by the UAS-NF or an FP server implemented within the UAS-NF). In some aspects, the FP information 516 may include an indication to store second information regarding the flight path of the UE / UAV 502. If the first format is different from the format used by the UAS-NF 507, the UAS-NF 507 (or the FP server implemented by the UAS-NF 507) may convert the FP information 516 received in the first format to a second format for storing the FP information at 520 in the UAS-NF (or the FP server) at 518. In some aspects, if the first format is the same as the second format for storing the FP information at the UAS-NF, the UAS-NF 507 may not convert the FP information 516. Alternatively or additionally, the UAS-NF 507 may not convert the FP information 516 from the first format to the second format, and in some aspects, the UAS-NF may store the FP information 516 in the first format together with an indication to store the FP information in the first format.

[0090] In some aspects, the UAS-NF 507 may convert the FP information stored at 520 from the second format (or another format in which the FP information is stored) to a third format at 522. In some aspects, the conversion at 522 may be triggered by an event associated with an authentication or verification operation. For example, when receiving FP information from the UE and / or UAV (e.g., the UE / UAV 502), an authorization and / or verification operation may be performed. As part of the authorization and / or verification operation (e.g., via a function call such as "Naf_FlightPathInfoVerify"), the FP information converted at 522 may be provided to the USS 510 as the FP information 524 via an interface such as the Naf 509. Based on the FP information 524, the USS may process the FP information 524 at 526. In some aspects, the processing at 526 may include checking the FP information 524 against the FP information associated with one or more UE / UAVs or locations stored at the USS 510 (e.g., including the UE / UAV 502 and other relevant UE or UAVs associated with a specific location or area) to verify and / or authorize the FP indicated in the FP information 524. In some aspects, the processing at 526 may include associating the FP information 524 (e.g., including one of GPSI or SUPI) with an identifier assigned by the USS or an ID assigned by the relevant CAA.

[0091] Based on the processing of the FP information 524 at 526, the USS may send the FP information 528. In some aspects, the FP information 528 may include the FP information in the third format. In some aspects, the FP information 528 may include verification information that indicates whether the FP information 524 is consistent with the FP information regarding the UE / UAV 502 stored at the USS 510. In some aspects, the FP information 528 may include authorization information.

[0092] In some aspects, the UAS-NF 507 may process the FP information 528 at 530 to determine whether the information included in the FP information 528 should be reported or communicated to the CN 506 (e.g., the AMF or LMF of the CN 506) and ultimately to the UE / UAV 502 or other UE or UAV associated with the CN 506. This determination may be based on additional communication from the CN 506 (e.g., a request for stored or updated FP information), for example, as described below with respect to Figure 6 and Figure 7 The UAS-NF 507 may send and the CN 506 may receive the FP information 532. The CN 506 may send the FP information 534 to the RAN 504 for the RAN 504 to send it to the UE / UAV 502 as the FP information 536. In some aspects, the RAN 504 may alternatively or additionally send the FP information to one or more other UE or UAV associated with the CN 506 or the RAN 504 based on one or more of the FP information 528, 532, or 534.

[0093] Figure 6FIG. 600 is a call flow diagram illustrating an FP information storage and retrieval function for authorizing and / or verifying FP information in an environment according to some aspects of the present disclosure. In some aspects, a UE / UAV 602 may send FP information 612 to an associated RAN 604 (e.g., an NG-RAN). In some aspects, the UE / UAV 602 may be a UE, a UAV, a drone, or other component of the RAN 604. In some aspects, the FP information 612 provided by the UE / UAV 602 may indicate and / or identify a sequence of waypoints. In some aspects, the sequence of waypoints may be represented by one or more GADs. In some aspects, for example, for UMTS, the waypoint may be indicated by one or more of the following: an ellipsoidal point, an ellipsoidal point with an uncertainty circle, an ellipsoidal point with an uncertainty ellipse, a polygon, an ellipsoidal point with a height, an ellipsoidal point with a height and an uncertainty ellipsoid, or an ellipsoidal arc. In some aspects, the sequence of waypoints may be associated with a set of timestamps (e.g., a sequence of timestamps corresponding to the sequence of waypoints). In some aspects, the set of timestamps may include one or more of an absolute timestamp (e.g., a timestamp represented relative to a global reference frame or a shared reference frame) or a relative time (e.g., a timestamp represented relative to the local time maintained at the UE / UAV 602 or relative to the start or end waypoint of the FP). The FP information 612 may also include at least one ID of the UE / UAV 602. In some aspects, the at least one ID may be one of a GPSI or a subscription permanent identifier SUPI. In some aspects, the FP information 612 may be provided in a first format associated with the UE / UAV 602 or the RAN 604.

[0094] In some aspects, the RAN 604 may then provide the FP information 614 (e.g., the FP information 612 provided by the UE / UAV 602) to the core network (CN) 606 (e.g., the AMF). The CN 606 may send the FP information 616 to the UAS-NF 607 via the Nnef 608 (e.g., an interface provided by the UAS-NF or an FP server implemented within the UAS-NF). In some aspects, the FP information 616 may include an indication to store second information regarding the flight path of the UE / UAV 602 (e.g., a function call such as "Nnef_FlightInfoStore"). If the first format is different from the format used by the UAS-NF 607, the UAS-NF 607 (or the FP server implemented by the UAS-NF) may convert the FP information 616 received in the first format to a second format for storing the FP information in the UAS-NF (or the FP server) at 620 at 618. In some aspects, if the first format is the same as the second format for storing the FP information at the UAS-NF, the UAS-NF 607 may not convert the FP information 616. Alternatively or additionally, the UAS-NF 607 may not convert the FP information 616 from the first format to the second format, and in some aspects, the UAS-NF may store the FP information 616 in the first format together with an indication to store the FP information in the first format.

[0095] In some aspects, the UAS-NF 607 may additionally receive the FP information 622 from the USS 610 (or some other external server) via the Naf 609. The FP information 622 may indicate the FP information associated with one or more UEs or UAVs (e.g., including the UE / UAV 602 or other UEs or UAVs associated with the UAS-NF 607 or the CN 606). In some aspects, the FP information may be sent in a third format that is the same as or different from the first format and the second format. In some aspects, the FP information 622 may be associated with an authorization or authentication operation performed by the USS 610 and / or the UAS-NF 607. In some aspects, the FP information 622 may include the FP information of UEs and / or UAVs that are not associated with the CN 606 or the RAN 604 but operate in the same location or area as one or more UEs or UAVs associated with the CN 606 or the RAN 604.

[0096] In some aspects, the UAS-NF 607 may convert the FP information 622 received from the USS 610 at 624 into a second format and may store the FP information 622 at 626. For the FP information 616, in some aspects, the FP information 622 may be stored in a third format, and the FP information is received in this third format together with an indication of the format for later conversion. The CN 606 may send and the UAS-NF 607 may receive a request 628 (e.g., via a function call such as "Nnef_FlightInfoRetrieve" for the current FP information) for the FP information stored by the UAS-NF 607 related to a specific UE or UAV or a group of UEs and / or UAVs (e.g., one or more UEs or UAVs including the UE / UAV 602). The request 628 may be associated with one or more components of the CN 606 (such as the AMF or the LMF). The request may include one or more IDs of the specific UE or UAV or the group of UEs and / or UAVs.

[0097] In some aspects, based on the request 628, the UAS-NF may identify the stored information related to the request 628 at 630 and convert the stored information (converting it into a format associated with the request 628). The stored information identified at 630 may be based on one or more of the FP information 616 received from the CN 606 or the FP information 622 received from the USS 610. The UAS-NF 607 may then send the FP information 632 to the CN 606 (e.g., to the AMF or the LMF associated with the request 628) based on the information stored by the UAS-NF 607. The CN 606 may then send the FP information 634 to the RAN 604, and the RAN 604 in turn may send the FP information 636 to the UE / UAV 602. In some aspects, the CN 606 and / or the RAN 604 may additionally or alternatively send the FP information to one or more UEs and / or UAVs (e.g., a group of one or more UEs or UAVs located in the same location or area) related to the requested FP information based on the FP information 632 and / or 634.

[0098] Figure 7FIG. 700 is a call flow diagram illustrating an FP information storage and retrieval function that authorizes and / or verifies FP information in an environment according to some aspects of the present disclosure. In some aspects, a UE / UAV 702 may send FP information 712 to an associated RAN 704 (e.g., an NG-RAN). In some aspects, the UE / UAV 702 may be a UE, a UAV, a drone, or another component of the RAN 704. In some aspects, the FP information 712 provided by the UE / UAV 702 may indicate and / or identify a sequence of waypoints. In some aspects, the sequence of waypoints may be represented by one or more GADs. In some aspects, for example, for UMTS, the waypoints may be indicated via one or more of the following: ellipsoidal points, ellipsoidal points with an uncertainty circle, ellipsoidal points with an uncertainty ellipse, polygons, ellipsoidal points with height, ellipsoidal points with height and uncertainty ellipsoids, or ellipsoidal arcs. In some aspects, the sequence of waypoints may be associated with a set of timestamps (e.g., a sequence of timestamps corresponding to the sequence of waypoints). In some aspects, the set of timestamps may include one or more of absolute timestamps (e.g., timestamps represented relative to a global reference frame or a shared reference frame) or relative times (e.g., timestamps represented relative to local time maintained at the UE / UAV 702 or relative to the start or end waypoints of the FP). The FP information 712 may also include at least one ID of the UE / UAV 702. In some aspects, the at least one ID may be one of a GPSI or a subscription permanent identifier SUPI. In some aspects, the FP information 712 may be provided in a first format associated with the UE / UAV 702 or the RAN 704.

[0099] In some aspects, the RAN 704 may then provide FP information 714 (e.g., the FP information 712 provided by the UE / UAV 702) to the core network (CN) 706 (e.g., the AMF). The CN 706 may send the FP information 716 to the UAS-NF 707 via the Nnef 708 (e.g., an interface provided by the UAS-NF or an FP server implemented within the UAS-NF). In some aspects, the FP information 716 may include an indication to store second information regarding the flight path of the UE / UAV 702 (e.g., a function call such as "Nnef_FlightInfoStore"). If the first format is different from the format used by the UAS-NF 707, the UAS-NF 707 (or the FP server implemented by the UAS-NF 707) may convert the FP information 716 received in the first format to a second format for storing the FP information in the UAS-NF (or the FP server) at 720 at 718. In some aspects, if the first format is the same as the second format for storing the FP information at the UAS-NF, the UAS-NF 707 may not convert the FP information 716. Alternatively or additionally, the UAS-NF 707 may not convert the FP information 716 from the first format to the second format, and in some aspects, the UAS-NF may store the FP information 716 in the first format together with an indication to store the FP information in the first format.

[0100] The CN 706 may send and the UAS-NF 707 may receive a request 722 (e.g., via the function calls "Nnef_FlightInfoRetrieve_notification" or "Nnef_FlightPathInfoStore_notification" for an update of the FP information) for the FP information subsequently received by the UAS-NF 707 related to a specific UE or UAV or a group of UEs and / or UAVs (e.g., one or more UEs or UAVs including the UE / UAV 702). The request 722 may be associated with one or more components of the CN 706 (such as the AMF or the LMF). The request may include one or more IDs of the specific UE or UAV or the group of UEs and / or UAVs.

[0101] In some aspects, the UAS-NF 707 may additionally receive FP information 724 from the USS 710 (or some other external server) via the Naf 709. The FP information 724 may indicate FP information associated with one or more UEs or UAVs (e.g., including the UE / UAV 702 or other UEs or UAVs associated with the UAS-NF 707 or the CN 706). In some aspects, the FP information may be sent in a third format that is the same as or different from the first and second formats. In some aspects, the FP information 724 may be associated with an authorization or authentication operation performed by the USS 710 and / or the UAS-NF 707. In some aspects, the FP information 724 may include FP information of UEs and / or UAVs that are not associated with the CN 706 or the RAN 704 but operate in the same location or area as one or more UEs or UAVs associated with the CN 706 or the RAN 704.

[0102] In some aspects, the UAS-NF 707 may convert the FP information 724 received from the USS 710 into a second format and may store the FP information 724. For the FP information 716, in some aspects, the FP information 724 may be stored in a third format, and the FP information is received in this third format together with an indication of the format for later conversion. In some aspects, based on the request 722, the UAS-NF may identify the stored information related to the request 722 at 726 and convert the stored information (converted into a format associated with the request 722). The stored information identified at 726 may be based on one or more of the FP information 716 received from the CN 706 or the FP information 724 received from the USS 710. The UAS-NF 707 may then send the FP information 728 to the CN 706 (e.g., to the AMF or LMF associated with the request 722) based on the information stored by the UAS-NF 707. The CN 706 may then send the FP information 730 to the RAN 704, and the RAN 704 in turn may send the FP information 732 to the UE / UAV 702. In some aspects, the CN706 and / or the RAN 704 may additionally or alternatively send FP information to one or more UEs and / or UAVs (e.g., a group of one or more UEs or UAVs located in the same location or area) related to the requested FP information based on the FP information 728 and / or 730.

[0103] Figure 8 FIG. 800 is a diagram illustrating components of a system including a UAS-NF 810 according to some aspects of the present disclosure, where the UAS-NF implements an FP server 812 that interacts with an external server USS 820 and a core network 830 associated with an NG-RAN 840 and at least one UE / UAV 850. As combined withFigures 5 to 7 As described, the UAS-NF 810 can receive FP information from the core network via or in association with a function call such as "Nnef_FlightInfoStore" 833 provided (or exposed) by an interface (Nnef) 816. In some aspects, the FP information can be received at the core network 830 via the RAN 840 from one or more UEs or UAVs including the UE / UAV 850. The core network 830 (e.g., components of the core network such as the AMF or LMF) can send additional function calls and / or requests to the USA-NF 810, such as "Nnef_FlightPathInfoRetrieve" 834 for retrieving stored information from the UAS-NF 810 and more specifically from the FP server 812, or "Nnef_FlightPathInfoStore_notification" 835 and / or "Nnef_FlightInfoRetrieve_notification" 836 for requesting a notification of an update to the FP information of one or more UEs or UAVs. The core network 830 can receive FP information or an FP information update from the UAS-NF 810, as described in connection with Figure 6 the FP information 632 and Figure 7 the FP information 728.

[0104] The UAS-NF 810 can further interact with an external server USS 820 via the interface Naf 818. For example, the UAS-NF can receive FP information 822 from the USS 820 via the Naf 818. Additionally, the UAS-NF 810 can send a verification request 824 (e.g., "Naf_FlightPathInfoVerify") to the USS 820 and, in response, receive verification information 826. In some aspects, the UAS-NF 810 and the USS 820 can alternatively or additionally exchange authorization requests and authorizations.

[0105] As shown in the figure, the FP server 812 may include an FP information database 814, which may include a data structure for storing FP information. Although described as a database, in different aspects, the FP information database 814 may be implemented as different data structures for storing and / or organizing data. The first data structure Nnef_FlightPathInfo 860 may include information, which includes UAV information 861 (e.g., identifiers such as GPSI or SUPI), FP information 862 indicating a set of waypoints, a format indication 863 indicating the format of the FP information 862, a timestamp 864 indicating a set of timestamps (objective timestamps or relative timestamps) associated with the FP information 862 (e.g., waypoints in the set of FP information 862), and a result 865 (e.g., the result of an authorization or verification operation). The second data structure Naf_FlightPathInfo 870 may include information, which includes UAV information 871 (e.g., identifiers such as GPSI, SUPI, or CAA-level UAV ID), FP information 872 indicating a set of waypoints, a format indication 873 indicating the format of the FP information 872, a timestamp 874 indicating a set of timestamps (objective timestamps or relative timestamps) associated with the FP information 872 (e.g., waypoints), and a result 875 (e.g., the result of an authorization or verification operation).

[0106] The waypoint is indicated in FP information 862 or FP information 872 via one or more of the following: an ellipsoidal point, an ellipsoidal point with an uncertainty circle, an ellipsoidal point with an uncertainty ellipse, a polygon, an ellipsoidal point with altitude, an ellipsoidal point with altitude and uncertainty ellipsoid, or an ellipsoidal arc. The format indication 863 or 873 may indicate which method in the waypoint indication method is used for the associated FP information. In some aspects, the FP information of different UEs or UAVs may be stored in the same data structure in different formats (e.g., Nnef_FlightPathInfo 860 or Naf_FlightPathInfo 870). In some aspects, the FP information of the same UE or UAV may be stored in different data structures in different formats (e.g., Nnef_FlightPathInfo 860 or Naf_FlightPathInfo 870). In some aspects, the data entries in one or more data structures of the FP information database 814 may be associated with an indication of time, which is associated with the reception or storage of the FP information associated with the data entry. In some aspects, the indicated time may be used to determine which data entry among multiple data entries associated with the same UE or UAV in one or more data structures is the most recent (e.g., the latest or current). In some aspects, the source of the FP information may be associated with the data entries in the one or more data structures, and the source identifier may alternatively or additionally be used to determine the precedence and / or authority of conflicting data entries for the same UE or UAV.

[0107] Figure 9 is a flowchart 900 of a method of wireless communication. The method may be performed by a UAS-NF or an FP server implemented by a UAS-NF (e.g., UAS167; UAS-NF 507, 607, 707, or 810; network entity 1460). At 902, the FP server may receive first information about the flight path of at least one wireless device from a second network entity or a first wireless device. For example, 902 may be performed by Figure 14 the network interface 1480, the network processor 1412, or the FP server component 198. In some aspects, the second network entity may be a component (e.g., AMF) of a core network associated with both the at least one wireless device and the first network entity (e.g., an FP server or a UAS-NF implementing an FP server). In some aspects, the UAS-NF or the FP server may be implemented as a function of the core network.

[0108] In some aspects, the first information may correspond to a first information format. The first information may be associated with an identification of a sequence of waypoints. In some aspects, the sequence of waypoints may be represented by one or more GADs. In some aspects, for example, for UMTS, the waypoint may be indicated by one or more of the following: an ellipsoidal point, an ellipsoidal point with an uncertainty circle, an ellipsoidal point with an uncertainty ellipse, a polygon, an ellipsoidal point with altitude, an ellipsoidal point with altitude and uncertainty ellipsoid, or an ellipsoidal arc. In some aspects, a set of waypoints in the sequence of waypoints may be associated with a set of timestamps, and the set of timestamps may include one or more of absolute time or relative time. In some aspects, the at least one wireless device may be the first wireless device. In some aspects, the at least one wireless device may be at least one of a UAV, a drone, or a UE. In some aspects, the first information regarding the flight path of the at least one wireless device may include at least one ID of the at least one wireless device. In some aspects, the at least one ID may be one of a GPSI, a SUPI, or a CAA level ID (e.g., an ID previously assigned to a UE or UAV by a USS or UTM). For example, referring to Figures 5 to 7 , UAS-NF 507, 607, or 707 may receive FP information 516, 616, or 716 from CN 506, 606, or 706 (based on FP information 512, 612, or 712 or FP information 514, 614, or 714 sent by UE / UAV 502, 602, or 702 or by RAN 504, 604, or 704).

[0109] At 904, the FP server may receive an indication to store second information regarding the flight path of the at least one wireless device based on the first information. For example, 904 may be performed by Figure 14 the network interface 1480, the network processor 1412, or the FP server component 198. In some aspects, the FP server may receive the indication to store the second information together with the first information received at 902. In some aspects, the second information corresponds to a second information format. Referring to Figures 5 to 8 , UAS-NF 507, 607, 707, or 810 may receive an indication to store FP information 516, 616, 716, or 831 as part of receiving FP information 516, 616, 716, or 831 (e.g., Nnef_FlightPathInfoStore 833 may include FP information 831).

[0110] The FP server can convert the first information in the first information format into the second information in the second information format for storage. In some aspects, the information format can be associated with the identification of a sequence of waypoints. In some aspects, the sequence of waypoints can be represented by one or more GADs. In some aspects, for example, for UMTS, the waypoint can be indicated by one or more of the following: an ellipsoidal point, an ellipsoidal point with an uncertainty circle, an ellipsoidal point with an uncertainty ellipse, a polygon, an ellipsoidal point with altitude, an ellipsoidal point with altitude and an uncertainty ellipsoid, or an ellipsoidal arc. If the first information format is the same as the second information format, the FP may not convert the first information. For example, referring to Figures 5 to 7 , UAS-NF 507, 607, or 707 can convert the FP information 516, 616, or 716 from the first information format to the second information format at 518, 618, or 718.

[0111] The FP server can further convert the second information in the second information format into a third information in a third information format. In some aspects, different information formats can be associated with different ways of identifying a sequence of waypoints, a start (or takeoff) position, and / or a destination (or landing) position. In some aspects, the sequence of waypoints can be represented by one or more GADs. In some aspects, for example, for UMTS, the waypoint can be indicated by one or more of the following: an ellipsoidal point, an ellipsoidal point with an uncertainty circle, an ellipsoidal point with an uncertainty ellipse, a polygon, an ellipsoidal point with altitude, an ellipsoidal point with altitude and an uncertainty ellipsoid, or an ellipsoidal arc. If the third information format is the same as the second information format, the FP may not convert the second information. For example, referring to Figures 5 to 7 , UAS-NF 507, 607, or 707 can convert the FP information stored by UAS-NF 597, 607, or 707 from the second information format to the third information format at 522, 624, or 726.

[0112] At 910, the FP server can send third information about the flight path of the at least one wireless device to a third network entity based on the second information. For example, 910 can be performed by Figure 14Performed by the network interface 1480, network processor 1412, or FP server component 198. In some aspects, the third information corresponds to a third information format. In some aspects, at least two of the first information format, the second information format, or the third information format may be different information formats. In some aspects, the third information may be sent to the third network entity in a verification request for verifying the third information regarding the flight path of the at least one wireless device. In some aspects, the third entity may be a USS that provides authentication and / or verification services. In some aspects, the third information may be sent to the third network entity in an authorization request for authorizing the flight path of the at least one wireless device included in the third information. For example, referring to Figure 5 and Figure 8 , the UAS-NF 507 or 810 may send the FP information 524 as part of a verification request associated with the FP information 524 or as part of a verification request 824 based on the information 516.

[0113] The FP server may receive verification information from the third network entity in response to sending the third information. For example, 912 may be performed by Figure 14 the network interface 1480, network processor 1412, or FP server component 198. In some aspects, the verification information may indicate whether the third information is consistent with fourth flight path information (e.g., fourth FP information stored at the third entity) regarding the flight path of the at least one wireless device at the third network entity. In some aspects, the verification information may include an authorization indication that indicates whether the flight path of the at least one wireless device included in the third flight path information has been authorized by the third network entity or a fourth entity associated with the third network entity (e.g., CAA). For example, referring to Figure 5 and Figure 8 , the UAS-NF 507 or 810 may receive the FP information 528 or verification information 826 (including verification and / or authorization information) based on the FP information 524 associated with the verification and / or authorization request.

[0114] Figure 10 is a flowchart 1000 of a method of wireless communication. The method may be performed by a UAS-NF or an FP server implemented by a UAS-NF (e.g., UAS167; UAS-NF 507, 607, 707, or 810; network entity 1460). At 1002, the FP server may receive first information regarding the flight path of at least one wireless device from a second network entity or a first wireless device. For example, 1002 may be performed by Figure 14executed by the network interface 1480, network processor 1412, or FP server component 198. In some aspects, the second network entity may be a component of the core network (e.g., AMF) associated with both the at least one wireless device and the first network entity (e.g., FP server or UAS-NF implementing the FP server). In some aspects, the UAS-NF or the FP server may be implemented as a function of the core network.

[0115] In some aspects, the first information may correspond to a first information format. The first information may be associated with the identification of a sequence of waypoints. In some aspects, the sequence of waypoints may be represented by one or more GADs. In some aspects, for example, for UMTS, the waypoint may be indicated via one or more of the following: ellipsoidal point, ellipsoidal point with an uncertainty circle, ellipsoidal point with an uncertainty ellipse, polygon, ellipsoidal point with altitude, ellipsoidal point with altitude and uncertainty ellipsoid, or ellipsoidal arc. In some aspects, the set of waypoints in the sequence of waypoints may be associated with a set of timestamps, and the set of timestamps may include one or more of absolute time or relative time. In some aspects, the at least one wireless device may be the first wireless device. In some aspects, the at least one wireless device may be at least one of a UAV, drone, or UE. In some aspects, the first information about the flight path of the at least one wireless device may include at least one ID of the at least one wireless device. In some aspects, the at least one ID may be one of a GPSI, SUPI, or CAA level ID (e.g., an ID previously assigned to the UE or UAV by USS or UTM). For example, referring to Figures 5 to 7 , the UAS-NF 507, 607, or 707 may receive FP information 516, 616, or 716 from the CN 506, 606, or 706 (based on the FP information 512, 612, or 712 or FP information 514, 614, or 714 sent by the UE / UAV 502, 602, or 702 or by the RAN 504, 604, or 704).

[0116] At 1004, the FP server may receive an indication to store second information about the flight path of the at least one wireless device based on the first information. For example, 1004 may be performed by Figure 14 the network interface 1480, network processor 1412, or FP server component 198. In some aspects, the FP server may receive the indication to store the second information together with the first information received at 1002. In some aspects, the second information corresponds to a second information format. Referring to Figures 5 to 8, UAS-NF 507, 607, 707, or 810 may receive an indication to store FP information 516, 616, 716, or 831 as part of receiving FP information 516, 616, 716, or 831 (e.g., Nnef_FlightPathInfoStore 833 may include FP information 831).

[0117] At 1006, the FP server may convert the first information in the first information format to the second information in the second information format for storage. For example, 1006 may be performed by Figure 14 network processor 1412 or FP server component 198 of. In some aspects, the information format may be associated with the identification of a sequence of waypoints. In some aspects, the sequence of waypoints may be represented by one or more GADs. In some aspects, for example, for UMTS, the waypoint may be indicated by one or more of the following: an ellipsoidal point, an ellipsoidal point with an uncertainty circle, an ellipsoidal point with an uncertainty ellipse, a polygon, an ellipsoidal point with altitude, an ellipsoidal point with altitude and uncertainty ellipsoid, or an ellipsoidal arc. If the first information format is the same as the second information format, at 1006, the FP may not convert the first information. For example, referring to Figures 5 to 7 , UAS-NF 507, 607, or 707 may convert FP information 516, 616, or 716 from the first information format to the second information format at 518, 618, or 718.

[0118] At 1008, the FP server may convert the second information in the second information format to the third information in the third information format. For example, 1008 may be performed by Figure 14 network processor 1412 or FP server component 198 of. In some aspects, the information format may be associated with the identification of a sequence of waypoints. In some aspects, the sequence of waypoints may be represented by one or more GADs. In some aspects, for example, for UMTS, the waypoint may be indicated by one or more of the following: an ellipsoidal point, an ellipsoidal point with an uncertainty circle, an ellipsoidal point with an uncertainty ellipse, a polygon, an ellipsoidal point with altitude, an ellipsoidal point with altitude and uncertainty ellipsoid, or an ellipsoidal arc. If the third information format is the same as the second information format, at 1008, the FP may not convert the second information. For example, referring to Figures 5 to 7 , UAS-NF 507, 607, or 707 may convert the FP information stored by UAS-NF 597, 607, or 707 from the second information format to the third information format at 522, 624, or 726.

[0119] At 1010, the FP server may send third information about the flight path of the at least one wireless device to a third network entity based on the second information. For example, 1010 may be performed by Figure 14 's network interface 1480, network processor 1412, or FP server component 198. In some aspects, the third information corresponds to a third information format. In some aspects, at least two of the first information format, the second information format, or the third information format may be different information formats. In some aspects, the third information may be sent to the third network entity in a verification request for verifying the third information about the flight path of the at least one wireless device. In some aspects, the third entity may be a USS that provides authentication and / or verification services. In some aspects, the third information may be sent to the third network entity in an authorization request for authorizing the flight path of the at least one wireless device included in the third information. For example, referring to Figure 5 and Figure 8 , the UAS-NF 507 or 810 may send FP information 524 as part of a verification request associated with the FP information 524 or as part of a verification request 824 based on the information 516.

[0120] Finally, at 1012, the FP server may receive verification information from the third network entity. For example, 1012 may be performed by Figure 14 's network interface 1480, network processor 1412, or FP server component 198. In some aspects, the verification information may indicate whether the third information is consistent with fourth flight path information (e.g., fourth FP information stored at the third entity) about the flight path of the at least one wireless device at the third network entity. In some aspects, the verification information may include an authorization indication that indicates whether the flight path of the at least one wireless device included in the third flight path information has been authorized by the third network entity or a fourth entity associated with the third network entity (e.g., CAA). For example, referring to Figure 5 and Figure 8 , the UAS-NF 507 or 810 may receive FP information 528 or verification information 826 (including verification and / or authorization information) based on the FP information 524 associated with the verification and / or authorization request.

[0121] In some aspects, in addition to receiving and storing the first flight path information from the first entity, the FP server may further expose additional functions for the first entity (e.g., components of the core network such as the AMF and / or LMF). The additional functions may involve retrieving the stored information or subscribing to updates related to at least one UE or UAV associated with the core network. Figure 11AFlowchart 1100 of a method for wireless communication. This method may be performed by the UAS-NF or by an FP server (e.g., UAS 167; UAS-NF 507, 607, 707, or 810; network entity 1460) implemented by the UAS-NF that performs the method for wireless communication illustrated in flowchart 1000. In some aspects, flowchart 1100 may follow 1006 or 1012 of flowchart 1000. At 1102, the FP server may receive a request for information regarding the flight path of at least one wireless device. For example, 1102 may be performed by Figure 14 the network interface 1480, the network processor 1412, or the FP server component 198. In some aspects, the request for the information regarding the flight path of the at least one wireless device may be received from a second network entity (e.g., AMF) that provided first flight path information or from a fourth network entity (e.g., LMF). In some aspects, the request may indicate an ID (e.g., GPSI, SUPI, or CAA level ID) associated with the at least one wireless device and may further indicate a flight path information format. For example, referring to Figure 6 and Figure 8 , CN 606 or the core network 830 (or a component of CN 606 or the core network 830, such as AMF or LMF) may send and the UAS-NF 607 or 810 may receive an FP information request 628 (e.g., "Nnef_FlightPathInfoRetrieve").

[0122] At 1104, the FP server may send third information regarding the flight path of the at least one wireless device based on second information (e.g., information stored at the FP server). For example, 1104 may be performed by Figure 14 the network interface 1480, the network processor 1412, or the FP server component 198. The third information may be identified based on an ID associated with the at least one wireless device. For example, referring to Figure 6 and Figure 8 , the UAS-NF 607 or 810 may send FP information 632 stored by the UAS-NF 607 or 810.

[0123] Figure 11Bis a flowchart 1150 of a method of wireless communication. This method can be executed by the UAS-NF or by an FP server (e.g., UAS 167; UAS-NF 507, 607, 707, or 810; network entity 1460) implemented by the UAS-NF that executes the method of wireless communication illustrated in flowchart 1000. In some aspects, flowchart 1150 can follow 1006 or 1012 of flowchart 1000. At 1106, the FP server can receive a request to receive an update on the flight path of the at least one wireless device. For example, 1106 can be executed by Figure 14 's network interface 1480, network processor 1412, or FP server component 198. In some aspects, the request for the information on the flight path of the at least one wireless device can be received from a second network entity (e.g., AMF) that provided first flight path information or from a fourth network entity (e.g., LMF). In some aspects, the request can indicate an ID (e.g., GPSI, SUPI, or CAA level ID) associated with the at least one wireless device and can further indicate the flight path information format. For example, referring to Figure 7 and Figure 8 , CN 706 or core network 830 (or components of CN 706 or core network 830, such as AMF or LMF) can send and UAS-NF 707 or 810 can receive request 722 (e.g., function call "Nnef_FlightPathInfoStore_notification" 835 that can be associated with AMF or function call "Nnef_FlightPathInfoRetrieve_notification" 836 that can be associated with one or more of AMF or LMF).

[0124] At 1108, the FP server can receive updated flight path information from a network entity that did not send the request (but may have transmitted a separate request for the same or different UE or UAV ID). For example, 1108 can be executed by Figure 14 's network interface 1480, network processor 1412, or FP server component 198. Based on the source or timing, the updated flight path information can have a higher priority than the previously stored flight path information. In some aspects, the updated flight path information can be based on UAV management operations performed at or by the network entity from which the updated flight path information is received at 1108. The updated flight path information can be received in a third flight path information format. For example, referring to Figure 7 and Figure 8 , UAS-NF 707 or 810 can receive FP information 724 or 822 from USS 710 or 820.

[0125] At 1110, the FP server may send third information about the flight path of the at least one wireless device based on the updated flight path information received at 1108 (e.g., the updated information stored at the FP server). For example, 1110 may be performed by Figure 14 the network interface 1480, the network processor 1412, or the FP server component 198. The third information may be identified based on the ID associated with the at least one wireless device. For example, referring to Figure 6 and Figure 8 , the UAS-NF 707 or 810 may send the FP information 728 stored by the UAS-NF 607 or 810 based on receiving the updated FP information 724 or FP information 822.

[0126] Figure 12 is a flowchart 1200 of a method of wireless communication. The method may be performed by a core network or a core network component such as an AMF (e.g., AMF 161; CN 506, 606, 706, or core network 830; network entity 1560). At 1202, the AMF may receive first information about the flight path of at least one wireless device from a first wireless device. For example, 1202 may be performed by Figure 15 the network interface 1580, the network processor 1512, or the FP server component 198. In some aspects, the first information may correspond to a first information format. The first information may be associated with the identification of a sequence of waypoints. In some aspects, the sequence of waypoints may be represented by one or more GADs. In some aspects, for example, for UMTS, the waypoints may be indicated via one or more of the following: ellipsoidal points, ellipsoidal points with an uncertainty circle, ellipsoidal points with an uncertainty ellipse, polygons, ellipsoidal points with altitude, ellipsoidal points with altitude and uncertainty ellipsoid, or ellipsoidal arcs. In some aspects, the set of waypoints in the sequence of waypoints may be associated with a set of timestamps, and the set of timestamps may include one or more of absolute time or relative time.

[0127] In some aspects, the at least one wireless device may be the first wireless device. In some aspects, the at least one wireless device may be at least one of a UAV, a drone, or a UE. In some aspects, the first information about the flight path of the at least one wireless device may include at least one ID of the at least one wireless device. In some aspects, the at least one ID may be one of a GPSI, a SUPI, or a CAA level ID (e.g., an ID previously assigned to a UE or UAV by a USS or UTM). For example, referring to Figures 5 to 7, CN 506, 606, or 706 may receive FP information 514, 614, or 714 from RAN 504, 604, or 704 (based on the FP information 512, 612, or 712 sent by UE / UAV 502, 602, or 702).

[0128] At 1204, the AMF may send an indication to a first network entity to store second information regarding the flight path of the at least one wireless device. For example, 1204 may be performed by Figure 15 the network interface 1580, the network processor 1512, or the FP server component 198. In some aspects, the first network entity may be an FP server or a UAS-NF implementing an FP server. In some aspects, the first network entity may expose network functions and / or interfaces to receive function calls including function calls for FP information storage (e.g., Nnef_FlightPathInfoStore function call). In some aspects, the UAS-NF or the FP server may be implemented as a function of the core network. In some aspects, the second information may correspond to a second information format for indicating the waypoints. In some aspects, the first information format may be different from the second information format, and the conversion may be performed by the first network entity. However, if the first information format is the same as the second information format, the FP may not convert the first information. For example, referring to Figures 5 to 7 , CN 506, 606, or 706 may send FP information 516, 616, or 716, which may include a request to store the second information.

[0129] In some aspects, the UAS-NF may expose functions for flight path information retrieval, and the AMF may send a request for information regarding the flight path of the at least one wireless device. In some aspects, the request for information regarding the flight path of the at least one wireless device may be sent to the first network entity. In some aspects, the request may indicate an ID associated with the at least one wireless device (e.g., GPSI, SUPI, or CAA level ID) and may further indicate the flight path information format. For example, referring to Figure 6 and Figure 8 , CN 606 or the core network 830 (or components of CN 606 or the core network 830, such as the AMF) may send and the UAS-NF 607 or 810 may receive an FP information request 628 (e.g., "Nnef_FlightPathInfoRetrieve").

[0130] The AMF may receive third information regarding the flight path of the at least one wireless device based on the second information (e.g., information stored at the FP server) in response to sending the request. For example, 1208 may be performed byFigure 15 performed by the network interface 1580, network processor 1512, or FP server component 198. The third information may be identified based on an ID associated with the at least one wireless device. For example, referring to Figure 6 and Figure 8 , CN 606 or the core network 830 may receive and UAS-NF 607 or 810 may send the FP information 632 stored by UAS-NF 607 or 810.

[0131] In some aspects, the UAS-NF may expose a function for flight path information update, and the AMF may send a request to receive an update on the flight path of the at least one wireless device. In some aspects, the request for the information on the flight path of the at least one wireless device may be sent to the first network entity. In some aspects, the request may indicate an ID associated with the at least one wireless device (e.g., GPSI, SUPI, or CAA level ID) and may further indicate the flight path information format. For example, referring to Figure 7 and Figure 8 , CN 706 or the core network 830 (or a component of CN 706 or the core network 830, such as the AMF) may send and UAS-NF 707 or 810 may receive a request 722 (e.g., the function call "Nnef_FlightPathInfoStore_notification" 835 that may be associated with the AMF or the function call "Nnef_FlightPathInfoRetrieve_notification" 836 that may be associated with the AMF).

[0132] The FP server may receive updated flight path information from a network entity that did not send the request (but may have transmitted a separate request for the same or a different UE or UAV ID). Based on the source or timing, the updated flight path information may have a higher priority than the previously stored flight path information. In some aspects, the updated flight path information may be based on UAV management operations performed at or by the network entity from which the updated flight path information is received. The updated flight path information may be received in a fourth flight path information format. For example, referring to Figure 7 and Figure 8 , UAS-NF 707 or 810 may receive FP information 724 or 822 from USS 710 or 820.

[0133] The AMF may receive fourth information about the flight path of the at least one wireless device in response to sending the request to receive the update, based on the updated flight path information received by the first network entity (e.g., the updated information stored at the FP server). For example, 1212 may be performed by Figure 15 the network interface 1580, the network processor 1512, or the FP server component 198. The fourth information may be identified based on an ID associated with the at least one wireless device. For example, referring to Figure 6 and Figure 8 , based on receiving updated FP information 724 or FP information 822, the CN 706 and the core network 830 may receive and the UAS-NF 707 or 810 may send the FP information 728 stored by the UAS-NF 607 or the FP information update 832 stored by the UAS-NF 810.

[0134] Figure 13 is a flowchart 1300 of a method of wireless communication. The method may be performed by a core network or a core network component such as an AMF (e.g., AMF 161; CN 506, 606, 706, or core network 830; network entity 1560). At 1302, the AMF may receive first information about the flight path of at least one wireless device from a first wireless device. For example, 1302 may be performed by Figure 15 the network interface 1580, the network processor 1512, or the FP server component 198. In some aspects, the first information may correspond to a first information format. The first information may be associated with an identification of a sequence of waypoints. In some aspects, the sequence of waypoints may be represented by one or more GADs. In some aspects, for example, for UMTS, the waypoint may be indicated via one or more of the following: an ellipsoidal point, an ellipsoidal point with an uncertainty circle, an ellipsoidal point with an uncertainty ellipse, a polygon, an ellipsoidal point with altitude, an ellipsoidal point with altitude and uncertainty ellipsoid, or an ellipsoidal arc. In some aspects, the set of waypoints in the sequence of waypoints may be associated with a set of timestamps, and the set of timestamps may include one or more of absolute time or relative time.

[0135] In some aspects, the at least one wireless device may be the first wireless device. In some aspects, the at least one wireless device may be at least one of a UAV, a drone, or a UE. In some aspects, the first information about the flight path of the at least one wireless device may include at least one ID of the at least one wireless device. In some aspects, the at least one ID may be one of a GPSI, a SUPI, or a CAA level ID (e.g., an ID previously assigned to a UE or a UAV by a USS or a UTM). For example, referring to Figures 5 to 7CN 506, 606, or 706 may receive FP information 514, 614, or 714 from RAN 504, 604, or 704 (based on the FP information 512, 612, or 712 sent by UE / UAV 502, 602, or 702).

[0136] At 1304, the AMF may send an indication to a first network entity to store second information regarding the flight path of the at least one wireless device. For example, 1304 may be performed by Figure 15 the network interface 1580, the network processor 1512, or the FP server component 198. In some aspects, the first network entity may be an FP server or a UAS-NF implementing an FP server. In some aspects, the first network entity may expose network functions and / or interfaces to receive function calls including function calls for FP information storage (e.g., Nnef_FlightPathInfoStore function call). In some aspects, the UAS-NF or the FP server may be implemented as a function of the core network. In some aspects, the second information may correspond to a second information format for indicating the waypoints. In some aspects, the first information format may be different from the second information format, and the conversion may be performed by the first network entity. However, if the first information format is the same as the second information format, the FP may not convert the first information. For example, referring to Figures 5 to 7 CN 506, 606, or 706 may send FP information 516, 616, or 716, which may include a request to store the second information.

[0137] At 1306, the AMF may send a request for information regarding the flight path of the at least one wireless device. For example, 1306 may be performed by Figure 15 the network interface 1580, the network processor 1512, or the FP server component 198. In some aspects, the request for the information regarding the flight path of the at least one wireless device may be sent to the first network entity. In some aspects, the request may indicate an ID associated with the at least one wireless device (e.g., GPSI, SUPI, or CAA level ID) and may further indicate the flight path information format. For example, referring to Figure 6 and Figure 8 CN 606 or the core network 830 (or a component of CN 606 or the core network 830, such as the AMF) may send and the UAS-NF 607 or 810 may receive an FP information request 628 (e.g., "Nnef_FlightPathInfoRetrieve").

[0138] At 1308, the AMF may receive third information about the flight path of the at least one wireless device based on the second information (e.g., information stored at the FP server). For example, 1308 may be performed by Figure 15 the network interface 1580, network processor 1512, or FP server component 198. The third information may be identified based on an ID associated with the at least one wireless device. For example, referring to Figure 6 and Figure 8 , the CN 606 or core network 830 may receive and the UAS-NF 607 or 810 may send FP information 632 stored by the UAS-NF 607 or 810.

[0139] At 1310, the AMF may send a request to receive an update on the flight path of the at least one wireless device. For example, 1310 may be performed by Figure 15 the network interface 1580, network processor 1512, or FP server component 198. In some aspects, the request for information on the flight path of the at least one wireless device may be sent to the first network entity. In some aspects, the request may indicate an ID associated with the at least one wireless device (e.g., GPSI, SUPI, or CAA level ID) and may further indicate a flight path information format. For example, referring to Figure 7 and Figure 8 , the CN 706 or core network 830 (or a component of the CN 706 or core network 830, such as the AMF) may send and the UAS-NF 707 or 810 may receive request 722 (e.g., the function call "Nnef_FlightPathInfoStore_notification" 835 that may be associated with the AMF or the function call "Nnef_FlightPathInfoRetrieve_notification" 836 that may be associated with the AMF).

[0140] The FP server may receive updated flight path information from a network entity that did not send the request (but may have transmitted a separate request for the same or a different UE or UAV ID). Based on the source or timing, the updated flight path information may have a higher priority than the previously stored flight path information. In some aspects, the updated flight path information may be based on UAV management operations performed at or by the network entity from which the updated flight path information is received. The updated flight path information may be received in a fourth flight path information format. For example, referring to Figure 7 and Figure 8 , the UAS-NF 707 or 810 may receive FP information 724 or 822 from the USS 710 or 820.

[0141] At 1312, the AMF may receive fourth information regarding the flight path of the at least one wireless device based on the updated flight path information received by the first network entity (e.g., the updated information stored at the FP server). For example, 1312 may be performed by Figure 15 the network interface 1580, the network processor 1512, or the FP server component 198. The fourth information may be identified based on the ID associated with the at least one wireless device. For example, referring to Figure 6 and Figure 8 , based on receiving updated FP information 724 or FP information 822, the CN 706 and the core network 830 may receive and the UAS-NF 707 or 810 may send the FP information 728 stored by the UAS-NF 607 or the updated FP information 832 stored by the UAS-NF 810.

[0142] Figure 14 FIG. 1400 is a diagram illustrating an example of a hardware implementation for the network entity 1460. In one example, the network entity 1460 may be located within the core network 120. The network entity 1460 may include a network processor 1412. The network processor 1412 may include on-chip memory 1412'. In some aspects, the network entity 1460 may further include additional memory modules 1414. The network entity 1460 communicates directly (e.g., backhaul link) or indirectly (e.g., through the RIC) with the CU 1402 via the network interface 1480. The on-chip memory 1412' and the additional memory modules 1414 may each be regarded as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. The processor 1412 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the processor when executing the software.

[0143] As discussed above, the FP server component 198 is configured to receive first information regarding the flight path of at least one wireless device from a second network entity or a first wireless device, where the first information corresponds to a first information format; receive an indication to store second information regarding the flight path of the at least one wireless device from the second network entity or the first wireless device based on the first information, where the second information corresponds to a second information format; and send third information regarding the flight path of the at least one wireless device to a third network entity based on the second information, where the third information corresponds to a third information format. The FP server component 198 can be located within the processor 1412. The FP server component 198 can be one or more hardware components specifically configured to perform the processes / algorithms, implemented by one or more processors configured to perform the processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. The network entity 1460 can include various components configured for various functions. In one configuration, the network entity 1460 includes components for receiving first information regarding the flight path of at least one wireless device from a second network entity or a first wireless device. In one configuration, the network entity 1460 includes components for receiving an indication to store second information regarding the flight path of the at least one wireless device from the second network entity or the first wireless device based on the first information. In one configuration, the network entity 1460 includes components for sending third information regarding the flight path of the at least one wireless device to a third network entity based on the second information. In one configuration, the network entity 1460 includes components for converting the first information in the first information format to the second information in the second information format before storing the second information. In one configuration, the network entity 1460 includes components for converting the second information in the second information format to the third information in the third information format before sending the third information. In one configuration, the network entity 1460 includes components for receiving verification information from the third network entity, where the verification information indicates whether the third information is consistent with fourth flight path information regarding the flight path of the at least one wireless device at the third network entity. In one configuration, the network entity 1460 includes components for receiving a request for information regarding the flight path of the at least one wireless device from one of the second network entity or the fourth network entity. In one configuration, the network entity 1460 includes components for sending fourth information regarding the flight path of the at least one wireless device to at least one of the second network entity and the fourth network entity based on the second information. In one configuration, the network entity 1460 includes components for receiving a request from the second network entity to receive an update regarding the flight path of the at least one wireless device.In one configuration, network entity 1460 includes components for receiving fourth information from one of the third network entity, the first wireless device, or the fourth network entity, the fourth information including an update to the second information regarding the flight path of the at least one wireless device. In one configuration, network entity 1460 includes components for sending fifth information regarding the update to the second information regarding the flight path of the at least one wireless device to the second network entity based on the fourth information. The components may be the FP server components of network entity 1460 configured to perform the functions described and documented by the components. Figures 9 to 11B The functions described and documented by the components.

[0144] Figure 15 FIG. 1500 is a diagram illustrating an example of a hardware implementation for network entity 1560. In one example, network entity 1560 may be located within core network 120. Network entity 1560 may include network processor 1512. Network processor 1512 may include on-chip memory 1512'. In some aspects, network entity 1560 may also include additional memory module 1514. Network entity 1560 communicates with CU 1502 directly (e.g., backhaul link) or indirectly (e.g., through RIC) via network interface 1580. On-chip memory 1512' and additional memory module 1514 may each be regarded as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Processor 1512 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the processor when executing the software.

[0145] As discussed above, the UAV FP component 199 is configured to receive first information regarding a flight path of at least one wireless device from a first wireless device, where the first information corresponds to a first information format; and to send an indication to a first network entity to store second information regarding the flight path of the at least one wireless device, where the second information corresponds to a second information format. The UAV FP component 199 may be located within the processor 1512. The UAV FP component 199 may be one or more hardware components specifically configured to perform the processes / algorithms, implemented by one or more processors configured to perform the processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. The network entity 1560 may include various components configured for various functions. In one configuration, the network entity 1560 includes components for receiving first information regarding a flight path of at least one wireless device from a first wireless device. In one configuration, the network entity 1560 includes components for sending an indication to a first network entity to store second information regarding the flight path of the at least one wireless device. In one configuration, the network entity 1560 includes components for sending a request to the first network entity for information regarding the flight path of the at least one wireless device. In one configuration, the network entity 1560 includes components for receiving third information regarding the flight path of the at least one wireless device from the first network entity based on the second information. In one configuration, the network entity 1560 includes components for sending a request to the first network entity to receive an update regarding the flight path of the at least one wireless device. In one configuration, the network entity 1560 includes components for receiving third information regarding an update to the flight path of the at least one wireless device from the first network entity. The components may be the UAV FP component 199 of the network entity 1560 configured to perform the functions discussed in conjunction with Figure 12 and Figure 13 and recited by the components.

[0146] In some aspects, the FP server may be implemented in the UAS-NF, as discussed above. The FP server may store flight path information received via the RAN and / or the AMF from a UAV or UE associated with the core network. The UAS-NF may additionally perform FP format conversion on FP information received from a UAV or UE associated with the core network or from an external server in different formats. The FP server may provide an interface and / or network functions for components of the associated core network and a set of external servers.

[0147] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is merely illustrative of the exemplary method. It should be understood that, based on design preferences, the specific order or hierarchy of the boxes in the process / flowchart can be rearranged. Additionally, some boxes can be combined or omitted. The appended method claims present the elements of the various boxes in an exemplary order, but are not limited to the specific order or hierarchy presented.

[0148] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims, and the singular forms of elements are not intended to mean "one and only one" but "one or more" unless specifically stated otherwise. Terms such as "if," "when," and "while" do not denote a direct temporal relationship or reaction. That is, these phrases, such as "when...," do not mean an immediate action in response to or during the occurrence of an action, but simply imply that if the condition is met, then the action will occur, without requiring a specific or immediate time limitation for the occurrence of the action. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or having an advantage over other aspects. Unless specifically stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them," including any combination of A, B, and / or C, may include multiple A's, multiple B's, or multiple C's. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be construed as a collection of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first and second devices or indirectly between the first and second devices through a collection of devices. All structural and functional equivalents of elements of the aspects described throughout this disclosure that are known or later will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. Additionally, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc. are not intended to substitute for the word "component." Thus, no claim element shall be construed as a means-plus-function unless the element is expressly recited using the phrase "means for...".

[0149] As used herein, the phrase "based on" should not be construed to refer to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be construed as "at least based on A", unless specifically stated otherwise.

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

[0151] Aspect 1 is a method for wireless communication at a first network entity, the method comprising: receiving, from a second network entity or a first wireless device, first information regarding a flight path of at least one wireless device, wherein the first information corresponds to a first information format; receiving, based on the first information, an indication from the second network entity or the first wireless device to store second information regarding the flight path of the at least one wireless device, wherein the second information corresponds to a second information format; and transmitting, based on the second information, third information regarding the flight path of the at least one wireless device to a third network entity, wherein the third information corresponds to a third information format.

[0152] Aspect 2 is the method according to Aspect 1, wherein the first information is received in the first information format, and the method further comprises: converting the first information in the first information format to the second information in the second information format before storing the second information; and converting the second information in the second information format to the third information in the third information format before transmitting the third information.

[0153] Aspect 3 is the method according to Aspect 2, wherein at least two of the first information format, the second information format, or the third information format are different information formats, and wherein at least two of the first information format, the second information format, or the third information format are associated with an identification of a sequence of waypoints via one or more of the following: a first ellipsoidal point, a second ellipsoidal point with an uncertainty circle, a third ellipsoidal point with an uncertainty ellipse, a polygon, a fourth ellipsoidal point with a first altitude, a fifth ellipsoidal point with a second altitude and an uncertainty ellipsoid, or an ellipsoidal arc.

[0154] Aspect 4 is the method according to Aspect 3, wherein a set of waypoints in the sequence of waypoints is associated with a set of timestamps, wherein the set of timestamps includes one or more of absolute time or relative time.

[0155] Aspect 5 is the method according to any one of Aspects 1 to 4, wherein the first information about the flight path of the at least one wireless device includes at least one ID of the at least one wireless device, and the at least one ID is one of a GPSI, a SUPI, or a CAA level ID.

[0156] Aspect 6 is the method according to any one of Aspects 1 to 5, wherein the third information is sent to the third network entity in a verification request for verifying the third information about the flight path of the at least one wireless device, and the method further includes: receiving verification information from the third network entity, the verification information indicating whether the third information is consistent with fourth flight path information about the flight path of the at least one wireless device at the third network entity.

[0157] Aspect 7 is the method according to Aspect 6, wherein the first network entity is a drone management server or a UAS-NF, the second network entity is an AMF, the first wireless device is a UE or a component in a RAN, and the third network entity is a USS.

[0158] Aspect 8 is the method according to any one of Aspects 1 to 7, wherein the at least one wireless device is at least one of a drone, an unmanned aerial vehicle, or a UE.

[0159] Aspect 9 is the method according to any one of Aspects 1 to 8, and the method further includes: receiving a request for fourth information about the flight path of the at least one wireless device from one of the second network entity or the fourth network entity; and sending the fourth information about the flight path of the at least one wireless device to at least one of the second network entity and the fourth network entity based on the second information.

[0160] Aspect 10 is the method according to any one of Aspects 1 to 9, and the method further includes: receiving a request from the second network entity to receive an update about the flight path of the at least one wireless device; receiving fourth information from one of the third network entity, the first wireless device, or the fourth network entity, the fourth information including an update to the second information about the flight path of the at least one wireless device; and sending fifth information about the update to the second information about the flight path of the at least one wireless device to the second network entity based on the fourth information.

[0161] Aspect 11 is a method for wireless communication at a second network entity, the method comprising: receiving, from a first wireless device, first information regarding a flight path of at least one wireless device, wherein the first information corresponds to a first information format; and sending an indication to a first network entity to store second information regarding the flight path of the at least one wireless device, wherein the second information corresponds to a second information format.

[0162] Aspect 12 is the method according to aspect 11, the method further comprising: sending a request to the first network entity for third information regarding the flight path of the at least one wireless device; and receiving, from the first network entity, the third information regarding the flight path of the at least one wireless device based on the second information.

[0163] Aspect 13 is the method according to any one of aspects 11 or 12, the method further comprising: sending a request to the first network entity to receive an update regarding the flight path of the at least one wireless device; and receiving, from the first network entity, third information regarding an update to the flight path of the at least one wireless device.

[0164] Aspect 14 is the method according to any one of aspects 11 to 13, wherein the first information format and the second information format are associated with an identification of a sequence of waypoints via one or more of the following: a first ellipsoidal point, a second ellipsoidal point with an uncertainty circle, a third ellipsoidal point with an uncertainty ellipse, a polygon, a fourth ellipsoidal point with a first height, a fifth ellipsoidal point with a second height and an uncertainty ellipsoid, or an ellipsoidal arc.

[0165] Aspect 15 is the method according to aspect 14, wherein the first information format and the second information format are different information formats.

[0166] Aspect 16 is the method according to any one of aspects 14 or 15, wherein a set of waypoints in the sequence of waypoints is associated with a set of timestamps, wherein the set of timestamps includes one or more of absolute time or relative time.

[0167] Aspect 17 is the method according to any one of aspects 11 to 16, wherein the first information regarding the flight path of the at least one wireless device includes at least one ID of the at least one wireless device, wherein the at least one ID is one of a GPSI, a SUPI, or a CAA level ID.

[0168] Aspect 18 is the method according to any one of aspects 11 to 17, wherein the first network entity is a drone management server or a UAS-NF, wherein the second network entity is an AMF, and wherein the first wireless device is a UE or a component in a RAN.

[0169] Aspect 19 is the method according to any one of aspects 11 to 18, wherein the at least one wireless device is at least one of a drone, an unmanned aerial vehicle, or a UE.

[0170] Aspect 20 is a device for wireless communication at a device, the device including a memory and at least one processor, the at least one processor being coupled to the memory and being configured to implement any one of aspects 1 to 19 at least in part based on information stored in the memory.

[0171] Aspect 21 is the method according to aspect 20, the method further including a transceiver or an antenna coupled to the at least one processor.

[0172] Aspect 22 is a device for wireless communication at a device, the device including components for implementing any one of aspects 1 to 19.

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

Claims

1. An apparatus for wireless communication at a first network entity, the apparatus comprises: a memory; and at least one processor coupled to the memory and configured, at least in part based on information stored in the memory, to: receive first information about a flight path of at least one wireless device from a second network entity or a first wireless device, wherein the first information corresponds to a first information format; receive, based on the first information, an indication from the second network entity or the first wireless device to store second information about the flight path of the at least one wireless device, wherein the second information corresponds to a second information format; and send, based on the second information, third information about the flight path of the at least one wireless device to a third network entity, wherein the third information corresponds to a third information format.

2. The apparatus according to claim 1, wherein, in order to receive the first information, the at least one processor is configured to receive the first information in the first information format, and the at least one processor is further configured to: convert the first information in the first information format to the second information in the second information format before the at least one processor is configured to store the second information; and convert the second information in the second information format to the third information in the third information format before the at least one processor is configured to send the third information.

3. The apparatus according to claim 2, wherein at least two of the first information format, the second information format, or the third information format are different information formats, and wherein at least two of the first information format, the second information format, or the third information format are associated with an identification of a sequence of waypoints via one or more of the following: a first ellipsoidal point, a second ellipsoidal point with an uncertainty circle, a third ellipsoidal point with an uncertainty ellipse, a polygon, a fourth ellipsoidal point with a first altitude, a fifth ellipsoidal point with a second altitude and an uncertainty ellipsoid, or an ellipsoidal arc.

4. The apparatus according to claim 3, wherein a set of waypoints in the sequence of waypoints is associated with a set of timestamps, wherein the set of timestamps includes one or more of absolute time or relative time.

5. The apparatus according to claim 1, wherein the first information about the flight path of the at least one wireless device includes at least one identifier (ID) of the at least one wireless device, wherein the at least one ID is one of a General Public Subscription Identifier (GPSI), a Subscription Permanent Identifier (SUPI), or a Civil Aviation Authority (CAA) level ID.

6. The apparatus according to claim 1, wherein the at least one processor is configured to send the third information to the third network entity in a verification request for verifying the third information about the flight path of the at least one wireless device, and the at least one processor is further configured to: Receive authentication information from the third network entity, the authentication information indicating whether the third information is consistent with fourth flight path information regarding the flight path of the at least one wireless device at the third network entity.

7. The apparatus according to claim 6, wherein the first network entity is a drone management server or a drone system network function (UAS-NF), wherein the second network entity is an access and mobility management function (AMF), wherein the first wireless device is a user equipment (UE) or a component in a radio access network (RAN), and wherein the third network entity is a UAS service provider (USS).

8. The apparatus according to claim 1, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to receive the first information, the at least one processor is configured to receive the first information via at least one of the transceiver or the antenna, and wherein the at least one wireless device is at least one of a drone, an unmanned aerial vehicle or a user equipment (UE).

9. The apparatus according to claim 1, wherein the at least one processor is further configured to: Receive a request for fourth information regarding the flight path of the at least one wireless device from one of the second network entity or the fourth network entity; and Send the fourth information regarding the flight path of the at least one wireless device to at least one of the second network entity and the fourth network entity based on the second information.

10. The apparatus according to claim 1, wherein the at least one processor is further configured to: Receive a request from the second network entity to receive an update regarding the flight path of the at least one wireless device; Receive fourth information from one of the third network entity, the first wireless device or the fourth network entity, the fourth information including an update to the second information regarding the flight path of the at least one wireless device; and Send fifth information regarding the update to the second information regarding the flight path of the at least one wireless device to the second network entity based on the fourth information.

11. An apparatus for wireless communication at a second network entity, the apparatus comprises: a memory; and at least one processor coupled to the memory, and at least partially based on information stored in the memory, the at least one processor is configured to: Receive first information regarding the flight path of at least one wireless device from a first wireless device, wherein the first information corresponds to a first information format; and Send an indication to a first network entity to store second information regarding the flight path of the at least one wireless device, wherein the second information corresponds to a second information format.

12. The apparatus according to claim 11, wherein the at least one processor is further configured to: Send a request for third information regarding the flight path of the at least one wireless device to the first network entity; and Receive, from the first network entity, the third information regarding the flight path of the at least one wireless device based on the second information.

13. The apparatus according to claim 11, wherein the at least one processor is further configured to: Send a request to the first network entity to receive an update regarding the flight path of the at least one wireless device; and Receive, from the first network entity, third information regarding an update to the flight path of the at least one wireless device.

14. The apparatus according to claim 11, wherein the first information format and the second information format are associated with an identification of a sequence of waypoints via one or more of the following: a first ellipsoidal point, a second ellipsoidal point with an uncertainty circle, a third ellipsoidal point with an uncertainty ellipse, a polygon, a fourth ellipsoidal point with a first altitude, a fifth ellipsoidal point with a second altitude and an uncertainty ellipsoid, or an ellipsoidal arc.

15. The apparatus according to claim 14, wherein the first information format and the second information format are different information formats.

16. The apparatus according to claim 14, wherein a set of waypoints in the sequence of waypoints is associated with a set of timestamps, wherein the set of timestamps includes one or more of absolute time or relative time.

17. The apparatus according to claim 11, wherein the first information regarding the flight path of the at least one wireless device includes at least one identifier (ID) of the at least one wireless device, wherein the at least one ID is one of a General Public Subscription Identifier (GPSI), a Subscription Permanent Identifier (SUPI), or a Civil Aviation Authority (CAA) level ID.

18. The apparatus according to claim 11, wherein the first network entity is an unmanned aerial vehicle management server or a Drone System Network Function (UAS-NF), wherein the second network entity is an Access and Mobility Management Function (AMF), and wherein the first wireless device is a User Equipment (UE) or a component in a Radio Access Network (RAN).

19. The apparatus according to claim 11, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, to receive the first information, the at least one processor is configured to receive the first information via at least one of the transceiver or the antenna, wherein the at least one wireless device is at least one of an unmanned aerial vehicle, a drone, or a User Equipment (UE).

20. A method for wireless communication at a first network entity, the method comprises: Receive, from a second network entity or a first wireless device, first information regarding the flight path of at least one wireless device, wherein the first information corresponds to a first information format; receiving, based on the first information, an indication from the second network entity or the first wireless device to store second information regarding the flight path of the at least one wireless device, wherein the second information corresponds to a second information format; and sending, based on the second information, third information regarding the flight path of the at least one wireless device to a third network entity, wherein the third information corresponds to a third information format.

21. The method according to claim 20, wherein at least two of the first information format, the second information format, or the third information format are different information formats, and wherein at least two of the first information format, the second information format, or the third information format are associated with an identification of a sequence of waypoints via one or more of the following: a first ellipsoidal point, a second ellipsoidal point with an uncertainty circle, a third ellipsoidal point with an uncertainty ellipse, a polygon, a fourth ellipsoidal point with a first altitude, a fifth ellipsoidal point with a second altitude and an uncertainty ellipsoid, or an ellipsoidal arc; and wherein a set of waypoints in the sequence of waypoints is associated with a set of timestamps, wherein the set of timestamps includes one or more of absolute time or relative time.

22. The method according to claim 20, wherein the first information regarding the flight path of the at least one wireless device includes at least one identifier (ID) of the at least one wireless device, wherein the at least one ID is one of a general public subscription identifier (GPSI), a subscription permanent identifier (SUPI), or a Civil Aviation Authority (CAA) level ID.

23. The method according to claim 20, wherein the third information is sent to the third network entity in a verification request for verifying the third information regarding the flight path of the at least one wireless device, the method further comprising: receiving verification information from the third network entity, the verification information indicating whether the third information is consistent with fourth flight path information regarding the flight path of the at least one wireless device at the third network entity.

24. The method according to claim 20, the method further comprising: receiving a request for fourth information regarding the flight path of the at least one wireless device from one of the second network entity or a fourth network entity; and sending, based on the second information, the fourth information regarding the flight path of the at least one wireless device to at least one of the second network entity and the fourth network entity.

25. The method according to claim 20, the method further comprising: receiving a request from the second network entity to receive an update regarding the flight path of the at least one wireless device; receiving fourth information from one of the third network entity, the first wireless device, or a fourth network entity, the fourth information including an update to the second information regarding the flight path of the at least one wireless device; and Send fifth information regarding the update of the second information about the flight path of the at least one wireless device to the second network entity based on the fourth information.

26. A method for wireless communication at a second network entity, the method comprises: Receiving, from a first wireless device, first information about the flight path of at least one wireless device, wherein the first information corresponds to a first information format; and Sending an indication to a first network entity to store second information about the flight path of the at least one wireless device, wherein the second information corresponds to a second information format.

27. The method according to claim 26, the method further comprises: Sending a request to the first network entity for third information about the flight path of the at least one wireless device; and Receiving, based on the second information, the third information about the flight path of the at least one wireless device from the first network entity.

28. The method according to claim 26, the method further comprises: Sending a request to the first network entity to receive an update about the flight path of the at least one wireless device; and Receiving, from the first network entity, third information about an update to the flight path of the at least one wireless device.

29. The method according to claim 26, wherein the first information format and the second information format are different information formats, and wherein the first information format and the second information format are associated with an identification of a waypoint sequence via one or more of the following: a first ellipsoidal point, a second ellipsoidal point with an uncertainty circle, a third ellipsoidal point with an uncertainty ellipse, a polygon, a fourth ellipsoidal point with a first altitude, a fifth ellipsoidal point with a second altitude and an uncertainty ellipsoid, or an ellipsoidal arc; and wherein a set of waypoints in the waypoint sequence is associated with a set of timestamps, wherein the set of timestamps includes one or more of absolute time or relative time.

30. The method according to claim 26, wherein the first information about the flight path of the at least one wireless device includes at least one identifier (ID) of the at least one wireless device, wherein the at least one ID is one of a Generic Public Subscription Identifier (GPSI), a Subscription Permanent Identifier (SUPI), or a Civil Aviation Authority (CAA) level ID.

Images