Reduced flight path reporting overhead

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network node may send a flight path information request indicating a differential flight path report configuration associated with UE flight path information associated with a user equipment (UE). The network node may receive the UE flight path information, the UE flight path information based at least in part on the differential flight path report configuration. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 63 / 378,835, filed on October 7, 2022, entitled “REDUCED FLIGHT PATH REPORTING OVERHEAD,” and U.S. non-provisional patent application No. 18 / 473,710, filed on September 25, 2023, entitled “REDUCED FLIGHT PATH REPORTING OVERHEAD,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for reduced flight path reporting overhead. Background Art

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

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

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

[0007] An unmanned aerial vehicle (UAV) user equipment (UE) that changes position may experience multiple radio link failures and / or multiple transitions to idle mode while in the air and / or in flight. A network node communicating with the UAV UE may lose flight path information associated with the UAV based at least in part on the UAV transitioning to the idle mode. Therefore, the network node 110 may send a request for flight path information from the UAV based at least in part on the UAV reconnecting to the network node and / or the UAV transitioning to a connected state. Alternatively or additionally, the UAV UE may send a reply including the flight path information. Multiple requests for flight path information and multiple flight path information replies may increase the overhead associated with maintaining a wireless link between the UAV and the network node and / or consume a certain amount of air interface resources, which results in increased data transfer latency within the wireless network, reduced capacity of the wireless network (e.g., the wireless network can serve fewer devices) and / or reduced data throughput.

[0008] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a network node. The method may include sending a flight path information request indicating a differential flight path reporting configuration associated with UE flight path information associated with a UE. The method may include receiving the UE flight path information, the UE flight path information being based at least in part on the differential flight path reporting configuration.

[0009] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a UE. The method may include receiving an indication that a network node supports differential flight path information. The method may include receiving a flight path information request from the network node. The method may include sending a response to the flight path information request based at least in part on the network node supporting the differential flight path information.

[0010] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a UE. The method may include: detecting a UE flight path change that satisfies a threshold. The method may include: sending a flight path change indication to a network node.

[0011] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a network node. The method may include: receiving last reported UE flight path information from a UE. The method may include: receiving a flight path change indication associated with a UE flight path change from the UE without sending a flight path information request.

[0012] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or collectively, to: send a flight path information request indicating a differential flight path reporting configuration, the differential flight path reporting configuration being associated with UE flight path information associated with a UE. The one or more processors may be configured, individually or collectively, to: receive the UE flight path information, the UE flight path information being based at least in part on the differential flight path reporting configuration.

[0013] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or collectively, to: receive an indication that a network node supports differential flight path information. The one or more processors may be configured to: receive a flight path information request from the network node. The one or more processors may be configured to: send a response to the flight path information request based at least in part on the network node supporting the differential flight path information.

[0014] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to: detect a UE flight path change that satisfies a threshold. The one or more processors may be configured individually or collectively to: send a flight path change indication to a network node.

[0015] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or collectively, to: receive last reported UE flight path information from a UE. The one or more processors may be configured, individually or collectively, to: receive a flight path change indication associated with a UE flight path change from the UE without sending a flight path information request.

[0016] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by an apparatus. The set of instructions, when executed by one or more processors of the apparatus, may cause the apparatus to: send a flight path information request indicating a differential flight path reporting configuration associated with UE flight path information associated with a UE. The set of instructions, when executed by one or more processors of the apparatus, may cause the apparatus to: receive the UE flight path information, the UE flight path information being based at least in part on the differential flight path reporting configuration.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a device. The instruction set, when executed by one or more processors of the device, may cause the device to: receive an indication that a network node supports differential flight path information. The instruction set, when executed by one or more processors of the device, may cause the device to: receive a flight path information request from the network node. The instruction set, when executed by one or more processors of the device, may cause the device to: send a response to the flight path information request based at least in part on the network node supporting the differential flight path information.

[0018] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by an apparatus. The instruction set, when executed by one or more processors of the apparatus, may cause the apparatus to: detect a UE flight path change that satisfies a threshold. The instruction set, when executed by one or more processors of the apparatus, may cause the apparatus to: send a flight path change indication to a network node.

[0019] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by an apparatus. The set of instructions, when executed by one or more processors of the apparatus, may cause the apparatus to: receive last reported UE flight path information from a UE. The set of instructions, when executed by one or more processors of the apparatus, may cause the apparatus to: receive a flight path change indication associated with a UE flight path change from the UE without sending a flight path information request.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for sending a flight path information request indicating a differential flight path reporting configuration associated with UE flight path information associated with a UE. The apparatus may include: means for receiving the UE flight path information, the UE flight path information being based at least in part on the differential flight path reporting configuration.

[0021] Some aspects described herein are directed to an apparatus for wireless communication. The apparatus may include means for receiving an indication that a network node supports differential flight path information. The apparatus may include means for receiving a flight path information request from the network node. The apparatus may include means for sending a response to the flight path information request based at least in part on the network node supporting the differential flight path information.

[0022]

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for detecting a UE flight path change that satisfies a threshold. The apparatus may include means for sending a flight path change indication to a network node.

[0023] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for receiving last reported UE flight path information from a UE. The apparatus may include: means for receiving a flight path change indication associated with a UE flight path change from the UE without sending a flight path information request.

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

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

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

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

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

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

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

[0031] Figure 4 is a diagram illustrating an example of an unmanned aerial vehicle UE in a wireless communication network environment according to the present disclosure.

[0032] Figure 5 is a diagram illustrating an example of a wireless communication process between a UE, a first network node, and a second network node according to the present disclosure.

[0033] Figure 6 is a diagram illustrating an example of a wireless communication process between a UE and a network node according to the present disclosure.

[0034] Figure 7 is a diagram illustrating an example process performed, for example, at a network node or at an apparatus of a network node according to the present disclosure.

[0035] Figure 8 is a diagram illustrating an example process performed, for example, at a UE or a device of a UE according to the present disclosure.

[0036] Fig. 9 is a diagram illustrating an example process performed, for example, at a UE or a device of a UE according to the present disclosure.

[0037] Fig.10 is a diagram illustrating an example process performed, for example, at a network node or at an apparatus of a network node according to the present disclosure.

[0038] Fig.11 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0039] Fig.12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0040] An unmanned aerial vehicle (UAV) user equipment (UE) that changes position may experience multiple radio link failures and / or multiple transitions to idle mode while in the air and / or in flight. A network node communicating with the UAV UE may lose flight path information associated with the UAV based at least in part on the UAV transitioning to the idle mode. Therefore, the network node 110 may send a request for flight path information from the UAV based at least in part on the UAV reconnecting to the network node and / or the UAV transitioning to a connected state. Alternatively or additionally, the UAV UE may send a reply including the flight path information. Multiple requests for flight path information and multiple flight path information replies may increase the overhead associated with maintaining a wireless link between the UAV and the network node and / or consume a certain amount of air interface resources, which results in increased data transfer latency within the wireless network, reduced capacity of the wireless network (e.g., the wireless network can serve fewer devices) and / or reduced data throughput.

[0041] Various aspects described herein generally relate to reduced flight path reporting overhead. Some aspects more specifically relate to a network node that commands a UE to send differential flight path information. In some aspects, the network node may send a flight path information request indicating a differential flight path reporting configuration, the differential flight path reporting configuration being associated with UE flight path information. For example, the network node may send the flight path information to the UE, and the flight path information request may indicate return differential flight path information. In some aspects, the network node may receive the UE flight path information, and the UE flight path information may be based at least in part on the differential flight path reporting configuration. For example, the UE flight path information may indicate differential flight path information.

[0042] Differential flight path information can reduce overhead signaling associated with maintaining a wireless link between a network node and a UAV UE. Reduced overhead signaling can reduce the amount of air interface resources used by the overhead signaling, and can subsequently result in reduced data transfer latency within the wireless network, increased capacity of the wireless network (e.g., the wireless network can serve more devices), and / or increased data throughput.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0057] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

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

[0060] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may send a flight path information request indicating a differential flight path reporting configuration associated with UE flight path information associated with a UE, and receive the UE flight path information based at least in part on the differential flight path reporting configuration.

[0061] In some aspects, as described in more detail elsewhere herein, the communication manager 150 may receive from the UE the last reported UE flight path information; and receive from the UE a flight path change indication associated with a UE flight path change without sending a flight path information request. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0062] In some aspects, a UE (e.g., UE 120) may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may receive an indication that a network node supports differential flight path information; receive a flight path information request from the network node; and send a response to the flight path information request based at least in part on the network node supporting the differential flight path information.

[0063] In some aspects, as described in greater detail elsewhere herein, the communications manager 140 may detect a UE flight path change that satisfies a threshold; and send a flight path change indication to a network node. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

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

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

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

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

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

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

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

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

[0072] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the may perform one or more techniques associated with reduced flight path reporting overhead, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 7 The process 700 Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 1000 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 7 The process 700 Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 The process 1000 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0073] In some aspects, a network node (e.g., network node 110) includes: a component for sending a flight path information request indicating a differential flight path reporting configuration, the differential flight path reporting configuration being associated with UE flight path information associated with the UE; and / or a component for receiving the UE flight path information, the UE flight path information being based at least in part on the differential flight path reporting configuration.

[0074] Alternatively or additionally, the network node includes: a component for receiving the last reported UE flight path information from the UE; and / or a component for receiving a flight path change indication associated with a UE flight path change from the UE without sending a flight path information request. The components for the network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0075] In some aspects, a UE (e.g., UE 120) includes: a component for receiving an indication that a network node supports differential flight path information; a component for receiving a flight path information request from the network node; and / or a component for sending a response to the flight path information request based at least in part on the network node supporting the differential flight path information.

[0076] Alternatively or additionally, the UE includes: a component for detecting a UE flight path change that satisfies a threshold; and / or a component for sending a flight path change indication to a network node. The components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

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

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

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

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

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

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

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

[0084] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

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

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

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

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

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

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

[0091] Figure 4 4 is a diagram illustrating an example 400 of an unmanned aerial vehicle (UAV) UE in a wireless communication network environment according to the present disclosure. Figure 4 As shown, example 400 includes a network node 110 and a UAV UE 120 (also referred to herein as UAV 120 ).

[0092] UAV 120 includes aircraft without a human pilot and may also be referred to as an unmanned aircraft (UA), drone, remotely piloted vehicle (RPV), remotely piloted aircraft (RPA), remotely operated aircraft (ROA), or unmanned aerial vehicle. UAV 120 may have various shapes, sizes, configurations, characteristics, etc. for various purposes and applications. In some implementations, UAV 120 may include one or more sensors, such as electromagnetic spectrum sensors (e.g., visual spectrum, infrared or near infrared cameras, radar systems, etc.), biosensors, temperature sensors, and / or chemical sensors, etc. UAV 120 may include one or more components for communicating with one or more network nodes 110.

[0093] The UAV 120 may communicate with the network node 110 via a Uu interface. For example, the UAV 120 may send uplink communications to the network node 110 and / or receive downlink communications from the network node 110 via the Uu interface. Such Uu connectivity may be used to support different applications for the UAV 120, such as video transmission from the UAV 120 or C2 communications for remote command and control of the UAV 120, etc.

[0094] like Figure 4 As shown, in some examples, network node 110 may send a request for flight path information to UAV 120. UAV 120 may receive the request for flight path information, and if the flight path information is available at UAV 120, UAV 120 may send the flight path information to network node 110. In some examples, UAV 120 may indicate to network node 110 whether UAV 120 has available flight path information (e.g., when initiating an RRC connection between UAV 120 and network node 110). The flight path information may indicate a planned or expected flight path of UAV 120. In some examples, the flight path information may include a set of waypoints (p1, p2, ..., p n ) and the corresponding timestamps (t1, t2, …, t n ). Waypoints (p1, p2, …, p n ) indicates the planned or estimated position of the UAV 120, and the timestamps (t1, t2, ..., t n ) indicates that the UAV 120 is at the corresponding waypoint (p1, p2, ..., p n ) is expected to arrive at . For example, Figure 4As shown, p1, t1 indicates the position and expected arrival time of the first waypoint (waypoint 1), p2, t2 indicates the position and expected arrival time of the second waypoint (waypoint 2), p3, t3 indicates the position and expected arrival time of the third waypoint (waypoint 3), and p4, t4 indicates the position and expected arrival time of the fourth waypoint (waypoint 4). In some examples, the network can use the flight path information to track how many UAVs are to be served in the area at a given time.

[0095] While airborne and / or in flight, the UAV may enter an idle state (e.g., an RRC_IDLE state). To illustrate, the UAV may experience a radio link failure (RLF) based at least in part on moving from a first location with strong coverage from a network node to a second location with weaker coverage from the network node relative to the first location. For example, a radiation pattern of a network node may direct a main lobe of radiation toward ground coverage (e.g., non-airborne UEs) and a side lobe of the radiation pattern toward airborne coverage. Thus, while airborne and / or in flight, a UAV at a moving location may experience multiple RLFs and / or multiple transitions to idle mode.

[0096] The network node may lose flight path information associated with the UAV based at least in part on the UAV transitioning to the idle mode. Thus, the network node 110 may send a request for flight path information from the UAV based at least in part on the UAV reconnecting to the network node and / or the UAV transitioning to a connected state (e.g., an RRC_CONNECTED state), and the UAV may send a reply including the flight path information as described above. In some aspects, the flight path information returned by the UAV after transitioning back to the connected state may include minimal changes relative to previous flight information at an earlier time. That is, the flight path information may include information commensurate with previous flight path information (e.g., information within a range of values ​​and / or within a threshold). Therefore, multiple requests for flight path information and multiple flight path information replies (e.g., associated with multiple transitions of the UAV between the idle state and the connected state) may increase the overhead associated with maintaining a wireless link between the UAV and the network node and / or consume a certain amount of air interface resources, which results in increased data transmission latency within the wireless network, reduced capacity of the wireless network (e.g., the wireless network can serve fewer devices) and / or reduced data throughput.

[0097] Some techniques and apparatus described herein provide reduced flight path reporting overhead. In some aspects, a network node may communicate a flight path information request to a core network, and the flight path information request may be associated with a UE (e.g., a specific UE 120 and / or a specific UAV 120). The network node may receive a response to the flight path information request from the core network. As an example, the core network may include in the response previous flight path information and / or a flight path identifier (ID) associated with the UE. As another example, the core network may include in the response an indication that the core network lacks flight path information associated with the UE. Based at least in part on the response from the core network, the network node may send a flight path query to the UE. Alternatively or additionally, the network node may send an indication indicating that the network node supports differential flight path information. In some aspects, the flight path query may indicate the flight path ID and / or timestamp, enabling the UE to send less flight path information to the network node, such as differential flight path information and / or an indication of no flight path information, and to reduce overhead associated with maintaining a wireless link between the network node and the UAV by using fewer air interface resources relative to sending full flight path information.

[0098] In some aspects, a UE (e.g., UE 120 and / or UAV 120) may receive an indication that a network node supports differential flight path information. Alternatively or additionally, the UE may receive a flight path query from the network node, and the UE may send a response to the flight path information request based at least in part on the network node supporting the differential flight path information. For example, the UE may send the differential flight path information and / or an indication of no flight path information by using fewer air interface resources relative to sending full flight path information, and / or reduce overhead associated with maintaining a wireless link between the network node and the UAV.

[0099] In some aspects, a UE (e.g., UE 120 and / or UAV 120) may detect a UE flight path change (e.g., a flight path change of flight path information associated with the UE) that satisfies a threshold. Based at least in part on detecting the UE flight path change, the UE may send a flight path change indication to a network node. In some aspects, the UE may send the flight path change indication to the network node without receiving a flight path query from the network node. Sending the flight path change indication (e.g., without receiving a flight path query) may reduce overhead associated with maintaining a wireless link between the network node and the UAV.

[0100] In some aspects, a network node (e.g., network node 110) may receive last reported UE flight path information associated with a UE (e.g., UE 120 and / or UAV 120). In some aspects, the network node may receive the last reported UE flight path information from the UE, for example, based at least in part on sending a request and / or query for UE flight path information to the UE. The network node may identify the UE flight path information as the last reported UE flight path information based at least in part on a timestamp. Alternatively or additionally, the network node may receive the last reported UE flight path information from a core network. In some aspects, after the network node receives the last reported UE flight path information, the network node may receive a flight path change indication associated with a UE flight path change from the UE without sending a flight path query. Receiving the flight path change indication without sending a flight path query may reduce overhead associated with maintaining a wireless link between the network node and the UAV.

[0101] Differential flight path information can reduce overhead signaling associated with maintaining a wireless link between the network node and the UAV, and can subsequently reduce the amount of air interface resources used by the overhead signaling. Reducing air interface resource consumption can result in reduced data transfer latency within a wireless network, increased capacity of the wireless network (e.g., the wireless network can serve more devices), and / or increased data throughput.

[0102] As indicated above, Figure 4 is provided as an example 400 of a UAV. Other examples may be related to Figure 4 The content described is different.

[0103] Figure 5 is a diagram of an example 500 of a wireless communication process between a UE 120 (e.g., UE 502 and / or UAV 120), a first network node 504 (e.g., network node 110), and a second network node 506 (e.g., another network node 110 and / or a core network node) according to the present disclosure.

[0104] As indicated by reference numeral 510, the first network node 504 can send an indication of flight path capabilities supported by the first network node 504, and the UE 502 can receive the indication. For illustration, the first network node 504 can broadcast the indication of the flight path capabilities in system information (SI), and the UE 502 can receive the flight path capabilities by retrieving the SI. In other examples, the first network node 504 can indicate the flight path capabilities in a unicast message and based at least in part on establishing a connection with the UE 502.

[0105] As an example of a flight path capability, the first network node 504 may send an indication of support for differential flight path information. Alternatively or additionally, the first network node 504 may send a flight path capability configuration. For illustration, the first network node 504 may indicate the current state of the flight path capability, such as by indicating that differential flight path support (e.g., of the first network node 504) has been enabled and / or disabled. For example, the SI may optionally include and / or exclude a binary tag (e.g., an optional differentialFlightPathReporting tag). The absence of the binary tag may indicate that the first network node 504 does not include support for differential flight path information reporting and / or that differential flight path information reporting is disabled. The presence of the (optional) binary tag may indicate that the first network node 504 supports differential flight path information reporting. The first value of the tag (e.g., "0") may indicate a disabled state of differential flight path information reporting at the first network node 504, and the second value of the tag (e.g., "1") may indicate an enabled state of differential flight path information reporting at the first network node 504.

[0106] As another example of flight path capability configuration, first network node 504 can indicate a time span (e.g., validity duration) associated with validating differential flight path information, as described below. First network node 504 can broadcast the flight path capability configuration information in the SI based at least in part on establishing a connection with UE 502 (as described with reference numeral 515) and / or can send the flight path capability configuration information in a multicast and / or unicast message.

[0107] In some aspects, the first network node 504 may indicate triggering events associated with autonomous and / or asynchronous reporting of differential flight path information as at least a portion of the flight path capability configuration and / or differential flight path configuration information included in the flight path configuration information. For example, the differential flight path configuration information may indicate any combination of a position change threshold, a time change threshold, a lateral positioning change threshold, a longitudinal positioning change threshold, and / or an altitude change threshold, and a UE (e.g., UE 502) that detects that a threshold has been met (or vice versa) may determine to autonomously send the differential flight path information, as described below. The first network node 504 may broadcast different differential flight path configuration information in an SI or send the differential flight path configuration information in a unicast message based at least in part on establishing a connection with the UE 502 (as described with respect to reference numeral 515).

[0108] As indicated by reference numeral 515, the UE 502 and the first network node 504 may establish a connection, such as a communication link (e.g., a wireless link). Alternatively or additionally, the network node 110 and the UE 120 may communicate via the connection based at least in part on any combination of layer 1 signaling (e.g., downlink control information (DCI) and / or uplink control information (UCI)), layer 2 signaling (e.g., MAC control element (CE)), and / or layer 3 signaling (e.g., RRC signaling). For illustration, the network node 110 may request UE capability information via RRC signaling, and / or the UE 120 may send the UE capability information via RRC signaling. As part of communicating via the communication link, the network node 110 may send configuration information via layer 3 signaling (e.g., RRC signaling), and activate and / or deactivate a specific configuration indicated in the configuration information via layer 2 signaling (e.g., MAC CE) and / or layer 1 signaling (e.g., DCI). For illustration, the network node 110 may send the configuration information via layer 3 signaling at a first time point associated with the UE's tolerance of communication delay, and the network node 110 may send activation of the configuration via layer 2 signaling and / or layer 1 signaling at a second time point associated with the UE's intolerance of communication delay.

[0109] The order in which first network node 504 sends the flight path capabilities and first network node 504 and UE 502 establish a connection may differ from the order included in example 500. To illustrate, first network node 504 and UE 502 may first establish a connection, and first network node 504 may send the flight path capabilities after the connection is established, such as by sending and / or indicating the flight path capabilities to UE 502 in a unicast message (e.g., to UE 502).

[0110] As indicated by reference numeral 520, the first network node 504 may send the flight path information request, such as by sending the flight path information request in a unicast message (e.g., RRC signaling), and the UE 502 may receive the flight path information request. In some aspects, the first network node 504 may determine that the connection with the UE 502 is an initial connection and / or a first connection with the UE 502. Based at least in part on determining that the connection is an initial connection and / or a first connection, the first network node 504 may send the flight path information request. Alternatively or additionally, the first network node 504 may send the flight path information request independently of whether the connection is a first connection or a subsequent connection. That is, the first network node 504 may send the flight path information request based at least in part on establishing and / or reestablishing a connection with the UE 502. In some aspects, (e.g., if applicable to the UE 502) the first network node 504 may indicate a timestamp in the flight path information request, such as a timestamp associated with the last reported flight path information.

[0111] As an example, the first network node 504 may send an information element (IE) indicating a configuration for returning flight path information. For example, the first network node 504 may send a UE information request IE configured as follows:

[0112] UEInformationRequest::=SEQUENCE{

[0113] IdleModeMeasurementReq-r15 ENUMERATED{true}OPTIONAL,--Need ON

[0114] flightPathInfoReq FlightPathInfoReportConfig OPTIONAL,--Need ON

[0115] nonCriticalExtension UEInformationRequest-v1710-IEs OPTIONAL

[0116] }

[0117] And the first network node 504 may include an optional flightpathInfoReq (eg, an instance of FlightPathInfoReportConfig IE) to indicate a request for flight path information. The FlightPathInfoReportConfig IE may be configured as follows: FlightPathInfoReportConfig::=SEQUENCE{

[0118] maxWayPointNumber INTEGER(1..maxWayPoint-r15),

[0119] includeTimeStamp ENUMERATED{true}OPTIONAL,

[0120] timeStampofLastReportedFlightPath< <timestamp>>OPTIONAL

[0121] }

[0122] Wherein maxWayPointNumber indicates the maximum number of waypoints to be included in the flight path information, the optional field includeTimeStamp indicates whether to return a timestamp associated with the flight path information, and the optional field timeStampofLastReportedFlightPath indicates a timestamp associated with previous flight path information. In some aspects, the first network node 504 may omit the optional field timeStampofLastReportedFlightPath based at least in part on not having previous flight path information associated with the UE 502.

[0123] Alternatively or additionally, the FlightPathInfoReportConfig IE may be configured as follows:

[0124] FlightPathInfoReportConfig::=SEQUENCE{

[0125] maxWayPointNumber INTEGER(1..maxWayPoint-r15),

[0126] includeTimeStamp ENUMERATED{true}OPTIONAL,

[0127] differentialReporting ENUMERATED{true}OPTIONAL

[0128] }

[0129] Wherein maxWayPointNumber indicates the maximum number of waypoints to be included in the flight path information, the optional field includeTimeStamp indicates whether a timestamp associated with the flight path information is returned, and the optional field differentialReporting may indicate whether differential flight path reporting is enabled (e.g., via a true value) or disabled (via a false value) at the UE 502. For example, differential flight path reporting being enabled may instruct the UE 502 to maintain the reported flight path information, such as in a last reported flight path buffer that is local to the UE 502 and enables the UE 502 to store the reported flight path information (e.g., full flight path information and / or differential flight path information). Alternatively or additionally, differential flight path reporting being enabled may instruct the UE 502 to store a timestamp associated with the flight path information (e.g., in a last reported flight path buffer). Differential flight path reporting being disabled and / or the optional differentialReporting field not being present in the flight path information request message may instruct the UE 502 to refresh and / or clear the last reported flight path buffer.

[0130] In some aspects, the first network node 504 may send a validity duration as at least part of the flight path information request. For example, the first network node 504 may send a differentialFlightPathReportValidityDuration field (e.g., as part of the FlightPathInfoReportConfig IE and / or separate from the FlightPathInfoReportConfig IE) indicating a time span that is validly associated with the differential flight path report and / or the baseline flight path information. For illustration, the UE 502 may calculate a time difference between a current timestamp and a timestamp associated with the last reported flight path information. Based at least in part on the time difference within the validity duration, the UE 502 may report differential flight path information based at least in part on the last reported flight path information. Alternatively or additionally, the UE 502 may refresh and / or clear the last reported flight path buffer and / or send full flight path information outside the validity duration based at least in part on the time difference.

[0131] As shown by reference numeral 525, UE 502 may send UE flight path information, and first network node 504 may receive the UE flight path information. For example, the UE flight path information may include a planned flight path or an expected flight path of UE 502, such as by specifying one or more waypoints and / or one or more timestamps. A waypoint may indicate a planned location or an expected location of UE 502, and an associated timestamp may indicate an expected arrival time at a corresponding waypoint. Alternatively or additionally, the UE flight path information may include a timestamp indicating a time point at which the UE flight path information was generated. A waypoint may include and / or indicate the planned location or the expected location based at least in part on any combination of an ellipsoid, a polygon, a horizontal velocity, and / or a vertical velocity. Each indicated waypoint may be associated with a corresponding location.

[0132] In some aspects, the UE flight path information may include full flight path information, the full flight path information including any combination of one or more absolute waypoints (e.g., absolute position information and / or absolute speed information), one or more absolute timestamps (e.g., absolute time), a maximum number of waypoints, and / or a maximum number of timestamps. The maximum number of waypoints and / or the maximum number of timestamps may be RRC-configured by the first network node 504 to the UE 502, as described above. The UE 502 may send the full flight path information based at least in part on not having an assigned flight path identifier and / or based at least in part on determining that the connection with the first network node 504 is an initial connection and / or a first connection to the first network node 504.

[0133] In other aspects, such as described below with respect to reference numeral 575, the UE flight path information may include differential flight path information indicating one or more changes relative to the baseline full flight path information, such as updating a first waypoint included in the baseline full flight path information, removing a second waypoint from the baseline full flight path information, and / or adding a third waypoint to the baseline full flight path information. Indicating a change in the baseline full flight path information may reduce a first amount of content (e.g., a number of entries) included in the differential flight path information relative to a second amount of content included in the baseline full flight path information. Reducing the amount of content may reduce overhead associated with maintaining a wireless link between the first network node 504 and the UE 502 and / or may reduce an amount of air interface resources used by the overhead. Reducing air interface resource consumption may result in reduced data transfer latency within a wireless network, increased capacity of the wireless network (e.g., the wireless network may serve more devices), and / or increased data throughput.

[0134] Based at least in part on sending the UE flight path information, UE 502 may store the UE flight path information in a last reported flight path buffer that is local to UE 502. That is, UE 502 may track and / or record the UE flight path information generated and / or sent by UE 502. Alternatively or additionally, UE 502 may store one or more timestamps associated with the UE flight path information in the last reported flight path buffer, such as a first timestamp indicating a first time point at which UE 502 generated the UE flight path information and / or a second timestamp indicating a second time point at which UE 502 sent the UE flight path information (e.g., to the first network node 504).

[0135] In some aspects, the UE 502 may send the full flight path information as the UE flight path information based at least in part on the last reported flight path buffer being empty. For example, the first network node 504 may indicate that differential reporting is enabled as described above, and the UE 502 may determine that the last reported flight path buffer is empty. Therefore, the UE 502 may send the full flight path information based at least in part on the last reported flight path buffer being empty. Alternatively or additionally, the UE 502 may send the differential flight path information as the UE flight path information based at least in part on any combination of verifying the last reported flight path information (e.g., via a validity duration) and / or differential reporting being enabled. In some aspects, the UE 502 may refresh and / or clear the last reported flight path buffer, examples of which have been provided above.

[0136] UE 502 may send the UE flight path information based at least in part on an IE, such as a FlightPathInfoReport IE. As an example, FlightPathInfoReport may be configured as follows:

[0137] FlightPathInfoReport::=SEQUENCE{

[0138] flightPath SEQUENCE(SIZE(1..maxWayPoint))OF WayPointLocationOPTIONAL,

[0139] flightPathDifferential flightPathDifferential

[0140] }

[0141] Wherein the optional field flightPath indicates a sequence and / or array of waypoints (e.g., full flight path information), and the optional IE field FlightPathDifferential may indicate differential flight path information. The UE 502 may omit both the optional field flightPath and the optional IE field flightPathDifferential to indicate that the flight path information has not changed. Alternatively or additionally, the UE 502 may omit the optional IE field flightPath based at least in part on including the optional IE field flightPathDifferential to indicate differential flight path information, or may omit the optional IE field flightPathDifferential based at least in part on including the optional field flightPath to indicate full flight path information. Therefore, the UE 502 may include the optional field flightPath in the FlightPathInfoReport IE based at least in part on sending the full flight path information, and the UE 502 may include the optional IE field flightPathDifferential to indicate differential flight path information. The FlightPathDifferential IE may be configured as follows: FlightPathDifferential::=SEQUENCE{ /

[0142] updatedNodes SEQUENCE(SIZE(1..maxWayPoint))OF WayPointLocationOPTIONAL,

[0143] deletedNodes SEQUENCE(SIZE(1..maxWayPoint))OF WayPointLocationOPTIONAL

[0144] }

[0145] The optional field updatedNodes may indicate one or more updated waypoints and / or newly added waypoints at UE 502 relative to the last reported flight path information, as at least a part of the differential flight path information, and the optional field deletedNodes may indicate one or more deleted waypoints at UE 502 relative to the last reported flight path information, as at least a part of the differential flight path information.

[0146] As indicated by reference numeral 530, the first network node 504 may send flight path information, and the second network node 506 may receive the flight path information. Alternatively or additionally, the first network node 504 may store the flight path information locally (e.g., in a local memory and / or a local last reported flight path buffer). As an example, the first network node 504 may send full flight path information associated with the UE 502. In some aspects, the first network node 504 may store and / or forward full flight path information received from the UE 502, such as the full flight path information sent by the UE 502, based at least in part on establishing an initial connection with the first network node 504. Alternatively or additionally, the first network node 504 may generate (e.g., stored locally and / or forwarded to the second network node 506) the full flight path information based at least in part on the last reported flight path information and the differential flight path information. In some aspects, the first network node 504 may send and / or indicate a timestamp associated with the UE flight path information, such as a first timestamp received with the UE flight path information (e.g., indicating a generation time) and / or a second timestamp indicating a reception time of the UE flight path information (e.g., received by the first network node 504).

[0147] The first network node 504 may communicate the UE flight path information to the second network node 506 based at least in part on a Next Generation Application Protocol (NGAP) process associated with the core network. In some aspects, the NGAP may provide one or more signaling services between the first network node 504 and the access and mobility management function (AMF) at the second network node 506. An example class 1 NGAP process may include any combination of an AMF configuration update process, a RAN configuration update process, a handover (HO) preparation process, and / or a HO resource allocation process. An example class 2 NGAP process may include a downlink RAN ​​configuration transfer process, a downlink RAN ​​state transfer process, and / or a downlink non-access stratum (NAS) transmission process. In some aspects, the NGAP may include a UE flight path management process, and the UE flight path management process may be a NGAP process based at least in part on the AMF at the second network node 506 and / or communicating with the AMF. The second network node 506 and / or the AMF at the second network node 506 may store the flight path information as previous flight path information.

[0148] Alternatively or additionally, based at least in part on one or more context management procedures, the second network node 506 may store the flight path information and / or the first network node 504 may retrieve the flight path information. For illustration, during an initial context establishment management procedure (e.g., an establishment request), the second network node 506 may indicate to the first network node 504, via the AMF, support for providing flight path related information as at least part of the context information, and in an establishment response, the first network node 504 may indicate the flight path information, such as one or more waypoints, differential waypoint information, and / or timestamps. At a later point in time, such as described below with respect to reference numerals 560 and 565, the first network node 504 may send a retrieve UE information message to the second network node 506 and / or initiate a retrieve UE information procedure with the second network node 506 to obtain the flight path information stored by the AMF, and the second network node 506 may send the flight path information based at least in part on a UE information transfer message and / or a UE information transfer procedure.

[0149] While example 500 includes first network node 504 sending the flight path information to second network node 506, other examples may exclude first network node 504 from sending the flight path information to second network node 506. For example, as described above, first network node 504 may store the flight path information locally as described above, and in some aspects, may not send the flight path information to second network node 506.

[0150] As indicated by reference numeral 535, second network node 506 can send a flight path identifier associated with UE 502, and first network node 504 can receive the flight path identifier. In some aspects, second network node 506 can indicate the flight path identifier as a new flight path identifier to be assigned to UE 502. That is, second network node 506 can determine that UE 502 does not have an assigned flight path identifier based at least in part on receiving flight path information (as described with respect to reference numeral 530). For example, the flight path information can not include a flight path identifier, and second network node 506 can determine to assign the flight path identifier to UE 502. Second network node 506 can store the flight path identifier with the previous flight path information.

[0151] As indicated by reference numeral 540, the first network node 504 may send the flight path identifier, and the UE 502 may receive the flight path identifier. As an example, the first network node 504 may indicate the flight path identifier to the UE 502 based at least in part on an Unmanned Aerial Vehicle Unmanned Systems Service Provider Authorization and / or Authentication (UUAA) process and / or a UUAA procedure. Alternatively or additionally, the first network node 504 may store the flight path identifier locally (e.g., in a memory and / or buffer associated with the last reported flight path information).

[0152] As indicated by reference numeral 545, a time span may occur, and at a point in time within the time span, UE 502 and first network node 504 may be disconnected from each other. As an example, UE 502 may transition to idle mode and / or disconnect from first network node 504 based at least in part on experiencing a radio link failure (RLF). UE 502 may identify the RLF based at least in part on one or more signal metrics (e.g., RSSI and / or RSRP) failing to meet a quality threshold. As a result, UE 502 and first network node 504 may be disconnected from each other.

[0153] As shown by reference numeral 550, the first network node 504 can send an indication of the flight path capabilities supported by the first network node 504 as described with respect to reference numeral 510, such as by broadcasting the indication of the flight path capabilities in an SI, and the UE 502 can receive the indication of the flight path capabilities. However, in other examples, the first network node 504 can indicate the flight path capabilities, the flight path capability configuration, and / or different flight path configuration information in a unicast message and based at least in part on establishing a connection with the UE 502.

[0154] The first network node 504 may send a flight path capability configuration along with the flight path capability, such as a current state of the flight path capability. Alternatively or additionally, the first network node 504 may indicate differential flight path configuration information that specifies triggering events for autonomously and / or asynchronously reporting differential flight path information. For example, the differential flight path configuration information may indicate any combination of a position change threshold, a time change threshold, a lateral position change threshold, a longitudinal position change threshold, and / or an altitude change threshold. In some aspects, the first network node 504 may indicate a validity duration associated with validating the differential flight path information.

[0155] As shown by reference numeral 555, UE 502 and first network node 504 may re-establish a connection and / or establish a new connection and / or may re-establish a communication link (eg, a wireless link). For visual clarity, Figure 5 UE 502 is shown reestablishing a connection with first network node 504, but in other examples, UE 502 may establish a connection with a different network node other than first network node 504 (e.g., UE 502 may establish a connection with a third network node), and UE 502 may send the flight path identifier to the different network node. In some aspects, and based at least in part on establishing a connection with first network node 504 (and / or a different network node), UE 502 may send the flight path identifier, and first network node 504 may receive the flight path identifier, such as the flight path identifier received by UE 502 as described with respect to reference numeral 540.

[0156] As indicated by reference numeral 560, the first network node 504 may send a flight path query and the second network node 506 may receive the flight path query. In some aspects, the first network node 504 may communicate the flight path identifier received from the UE 502 as at least a portion of the flight path query. The sending of the flight path query and / or the indication of the flight path identifier may explicitly and / or implicitly request stored flight path information from the AMF at the second network node 506, such as previous flight path information stored by the AMF and associated with the flight path identifier, such as the flight path information described with respect to reference numeral 530.

[0157] Alternatively or additionally, the first network node 504 may request the stored flight path information based at least in part on a setup request procedure and a setup response procedure. In some aspects, the first network node 504 may request the stored flight path information based at least in part on a retrieve UE information procedure and a UE information transfer procedure. Thus, the flight path query may be based at least in part on the setup request procedure and / or the UE information transfer procedure.

[0158] While example 500 includes first network node 504 requesting stored flight path information from second network node 506, other examples may exclude first network node 504 requesting stored flight path information from second network node 506. For example, first network node 504 may store flight path information locally as described above, and may obtain the flight path information associated with UE 502 locally and based at least in part on a flight path identifier received from UE 502.

[0159] As indicated by reference numeral 565, the second network node 506 may send a response to the flight path query, and the first network node 504 may receive the response to the flight path query. In some aspects, the response from the second network node 506 may include previous UE flight path information (e.g., flight path information from UE 502 stored at the second network node 506) and / or a timestamp associated with the previous UE flight path information. For example, the second network node 506 may obtain the previous UE flight path information based at least in part on retrieving the previous UE flight path information from the AMF at the second network node 506. In some aspects, the second network node 506 may select the previous flight path information based at least in part on receiving the flight path identifier as at least part of the flight path query. Thus, the previous UE flight path information may be based at least in part on the last reported UE flight path information associated with UE 502. In some aspects, the response to the flight path query may be based at least in part on establishing a response procedure and / or a UE information transfer procedure.

[0160] While example 500 includes first network node 504 receiving the response to the flight path query from second network node 506, other examples may exclude first network node 504 from receiving the response from second network node 506. For example, first network node 504 may store flight path information locally as described above, and obtain the flight path information associated with UE 502 locally and based at least in part on a flight path identifier received from UE 502. Therefore, and based at least in part on not sending the flight path query, first network node 504 may not receive a response.

[0161] As shown by reference numeral 570, the first network node 504 may send a flight path information request, and the UE 502 may receive the flight path information request. For example, the first network node 504 may send the flight path information request based at least in part on the UEInformationRequest IE and / or the FlightPathInfoReportConfig IE as described above. In some aspects, the flight path information request may be based at least in part on the response to the flight path query. Alternatively or additionally, the flight path information request may include a timestamp associated with the previous UE flight path information (e.g., indicated by the second network node 506 as described with respect to reference numeral 565 and / or indicated by the UE 502 as described with respect to reference numeral 525). The first network node 504 may send the flight path information based at least in part on establishing a connection with the UE 502 and / or using a unicast message.

[0162] As shown by reference numeral 575, UE 502 may send UE flight path information, and first network node 504 may receive the UE flight path information. For example, UE 502 may send the UE flight path information based at least in part on receiving the flight path information request. Thus, the UE flight path information may be sent as at least a portion of a flight path information request response. UE 502 may send the UE flight path information and / or the flight path information request response based at least in part on an IE, such as, for example, a FlightPathInfoReport IE as described above. In some aspects, UE 502 may send full flight path information as the UE flight path information. For illustration, UE 502 may determine that a validity period indicated by first network node 504 has expired, such as by determining that a time difference fails to satisfy the validity period, and based at least in part on the validity period having expired, UE 502 may determine that sending differential flight path information is invalid. Thus, UE 502 may send the full flight path information and / or may update the last reported flight path buffer and / or store the full flight path information in the last reported flight path buffer. Alternatively or additionally, as described above, UE 502 may store a timestamp in the last reported flight path buffer. In some aspects, to update the last reported flight path buffer, UE 502 may remove expired flight path information stored in the last reported flight path buffer and / or overwrite the expired flight path information.

[0163] Alternatively or additionally, UE 502 may send the differential flight path information as UE flight path information. For example, UE 502 may determine that the differential flight path information is valid based at least in part on the time difference satisfying the validity duration. Thus, UE 502 may send the differential flight path information based at least in part on determining that the differential flight path information is valid. UE 502 may send the flight path identifier along with the UE flight path information, including full flight path information and / or differential flight path information.

[0164] The UE 502 may generate the differential flight path information based at least in part on comparing the current waypoint to a previous waypoint, such as a previous waypoint stored in the last reported flight path buffer and / or a previous waypoint associated with a timestamp indicated by the first network node 504 in the flight path information request. The UE may evaluate and / or compare the current waypoint to the previous waypoint in various ways, such as by calculating a change and / or difference between an attribute of the current waypoint and a corresponding attribute of the previous waypoint and determining whether the change and / or the difference satisfies a differential threshold. The differential threshold may be based at least in part on a differential flight path information configuration as described above. Some examples may include the UE 502 evaluating a change in position, a change in longitude, a change in latitude, and / or a time difference between the current waypoint and the previous waypoint.

[0165] UE 502 may include in the differential flight path information an indication of a change that satisfies the differential threshold. For example, the differential flight path information may indicate any combination of updating a first waypoint included in a previous UE flight path information (e.g., stored in the last reported flight path buffer), removing a second waypoint from the previous UE flight path information, and / or adding a third waypoint to the previous UE flight path information. Alternatively or additionally, UE 502 may use the differential flight path information to indicate a timestamp associated with the differential flight path information. For example, UE 502 may select the previous full flight path information based at least in part on a first timestamp (e.g., based at least in part on an optional field timeStampofLastReportedFlightPath as described above), and / or may select the previous full flight path information as the full flight path information stored in the last reported flight path buffer. UE 502 may generate and / or calculate the differential flight path information at a second point in time (e.g., a current time), and may indicate the second point in time as a second timestamp. Therefore, UE 502 may use the differential flight path information to indicate the second timestamp.

[0166] The following pseudo-code provides an example FindDifferentialFlightPath algorithm that may be implemented by UE 502 to calculate the differential flight path information:

[0167]

[0168]

[0169] Where FP(t) represents the FindDifferentialFlightPath algorithm at time = t. The notation Fp(t) = {w} indicates that the flight path information query algorithm returns {w}, where w is a waypoint that can be represented as w = (x, τ), x represents the location that characterizes the waypoint, and τ represents the time that characterizes the waypoint (which may be optional). The variables updatedNodes = [] and retainedNodes = [] represent corresponding arrays of waypoints.

[0170] In the pseudo-code above, Δx and Δτ may each represent a respective change threshold, such as one or more change thresholds indicated by the first network node 504. For discussion purposes, Δx and Δτ are shown as a location change threshold and a time change threshold, respectively, in the pseudo-code, but the UE 502 may include and / or omit other combinations of change thresholds as part of the FindDifferentialFlightPath algorithm (an example of which is provided above).

[0171] In some aspects, the UE 502 may perform the FindDifferentialFlightPath algorithm at time t'. As shown in the pseudocode, the UE 502 may compare one or more waypoints (denoted as w') of the current flight path calculated by the UE 502 with one or more previously reported waypoints (denoted as w). For illustration, the UE 502 may compare a first time (denoted as τ') associated with the current waypoint with a second time (denoted as τ) associated with the last reported waypoint based at least in part on a time change threshold. Alternatively or additionally, the UE 502 may compare a first position (denoted as x') associated with the current waypoint with a second position (denoted as x) associated with the last reported waypoint based at least in part on a position change threshold. The UE 502 may determine whether to update waypoints, add waypoints, and / or remove waypoints as part of the differential flight path information based at least in part on the comparison and whether the change threshold has been met. Alternatively or additionally, UE 502 may indicate that the waypoint has not changed based at least in part on omitting the waypoint from the differential flight path information based at least in part on the comparison to the change threshold.

[0172] UE 502 may compare each waypoint included in the current flight path information with each waypoint included in the last reported flight path information (as shown by using a for loop), may add and / or update waypoints as part of the differential flight path information (as shown by using an if-else statement), and / or may remove waypoints as part of the differential flight path information (as shown by using an if-else statement).

[0173] In some aspects, UE 502 may send a flight path information request response indicating that there is no change in the UE flight path information as the UE flight path information. For example, UE 502 may determine that there is no change and / or the difference satisfies the difference threshold. Therefore, as described above, UE 502 may indicate that there is no change in the UE flight path information.

[0174] As indicated by reference numeral 580, the first network node 504 may send flight path information, and the second network node 506 may receive the flight path information. As a first example, the first network node 504 may communicate differential flight path information received from the UE 502 (e.g., as UE flight path information). As a second example, the first network node 504 may communicate full flight path information based at least in part on the UE flight path information to the second network node 506. For example, the first network node 504 may receive differential flight path information from the UE 502, and may generate the full flight path information based at least in part on the response from the second network node 506 (e.g., indicating previous UE flight path information) and the differential flight path information from the UE 502. Alternatively or additionally, the first network node 504 may communicate the full flight path information received from the UE 502. In some aspects, the first network node 504 may communicate the flight path information to the second network node 506 based at least in part on the NGAP process as described above. Alternatively or additionally, the first network node 504 may communicate, along with the flight path information (e.g., full flight path information and / or differential flight path information), a timestamp associated with generation of the flight path information, such as a timestamp indicated by the UE 502 and / or a timestamp captured by the first network node 504. Based at least in part on receiving the flight path information, the second network node 506 and / or the AMF at the second network node 506 may store the flight path information and / or the timestamp associated with the flight path information as previous flight path information.

[0175] While example 500 includes first network node 504 sending the flight path information to second network node 506, other examples may exclude first network node 504 from sending the flight path information to second network node 506. For example, as described above, first network node 504 may store the flight path information locally as described above, and in some aspects, may not send the flight path information to second network node 506.

[0176] Differential flight path information can reduce overhead signaling associated with maintaining a wireless link between the network node and the UAV, and can subsequently reduce the amount of air interface resources used by the overhead signaling. Reducing air interface resource consumption can result in reduced data transfer latency within a wireless network, increased capacity of the wireless network (e.g., the wireless network can serve more devices), and / or increased data throughput.

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

[0178] Figure 6 600 is a diagram illustrating an example of a wireless communication process between a UE 602 (e.g., UE 120 and / or UE 502) and a network node 604 (e.g., network node 110 and / or first network node 504) according to the present disclosure. Aspects of the wireless communication process described with respect to example 600 may be combined with aspects of the wireless communication process described with respect to example 500.

[0179] As shown by reference numeral 610, UE 602 can detect a flight path change. In some aspects, UE 602 can detect the UE flight path change based at least in part on the last reported UE flight path information. For example, and as described with respect to Figure 5 As described, UE 602 may receive an indication of one or more change thresholds from network node 604, and UE 6-2 may use the change thresholds to detect changes between current flight path information and last reported UE flight path information.

[0180] As indicated by reference numeral 620, the UE 602 may send a flight path change indication, and the network node 604 may receive the flight path change indication. In some aspects, the UE 602 may send the flight path change indication based at least in part on detecting a UE flight path change and / or based at least in part on receiving an indication that the network node 604 supports differential flight path information.

[0181] As an example, the UE 602 may send the flight path change indication in a MAC CE. In some aspects, the flight path change indication may specify that updated flight path information is available. As another example, the UE 602 may initiate and / or send a UE assistance information message (e.g., a UEAssistanceInformation message) indicating that updated flight path information is available. Based at least in part on receiving the flight path change indication, the network node 604 may determine whether to send a flight path information request, such as regarding Figure 5 That is, the network node 604 may send a flight path information request message associated with retrieving updated flight path information and / or current UE flight path information, and the UE 602 may receive the flight path information request message.

[0182] Alternatively or additionally, the UE 602 may indicate current UE flight path information (e.g., full flight path information and / or differential flight path information) as at least part of the flight path change indication (e.g., the UE flight path change). In some aspects, the UE 602 may autonomously indicate the current UE flight path information without receiving a flight path information request from the network node 604. For example, the UE 602 may trigger and / or initiate sending a UE information response message (e.g., sending a UEInformationResponse message without a request), and may indicate the current UE flight path information in the UE information response message. As described above, the UE 602 may indicate the current UE flight path information based at least in part on indicating the full flight path information and / or by indicating the differential flight path information. However, in other aspects, the UE 602 may send and / or indicate the current UE flight path information based at least in part on receiving a request from the network node 604.

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

[0184] Figure 7 is a diagram illustrating an example process 700 performed, for example, at a network node or at an apparatus of a network node in accordance with the present disclosure. Example process 700 is an example of operations in which the apparatus or the network node (eg, network node 110) performs operations associated with reduced flight path reporting overhead.

[0185] like Figure 7 As shown in FIG. 7 , in some aspects, process 700 may include sending a flight path information request indicating a differential flight path reporting configuration associated with UE flight path information associated with the UE (block 710). For example, the network node (e.g., using Fig.11 The depicted communications manager 150 and / or sending component 1104) may send a flight path information request indicating a differential flight path reporting configuration associated with UE flight path information associated with the UE, as described above.

[0186] like Figure 7 As further shown, in some aspects, process 700 may include receiving the UE flight path information, the UE flight path information being based at least in part on the differential flight path reporting configuration (block 720). Fig.11 The depicted communications manager 150 and / or receiving component 1102) can receive the UE flight path information based at least in part on the differential flight path reporting configuration, as described above.

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

[0188] In a first aspect, process 700 includes communicating a flight path query associated with the UE to a core network and receiving a response to the flight path query from the core network, and the flight path information request is based at least in part on the response from the core network.

[0189] In a second aspect, process 700 includes communicating full flight path information to the core network, and the full flight path information is based at least in part on the UE flight path information.

[0190] In a third aspect, the UE flight path information includes the full flight path information.

[0191] In a fourth aspect, the UE flight path information includes differential flight path information, and process 700 includes generating the full flight path information based at least in part on the response from the core network and the differential flight path information.

[0192] In a fifth aspect, the response from the core network includes previous UE flight path information, and the differential flight path information indicates at least one of: updating a first waypoint included in the previous UE flight path information, removing a second waypoint from the previous UE flight path information, or adding a third waypoint to the previous UE flight path information.

[0193] In a sixth aspect, the response from the core network includes previous UE flight path information associated with the UE and a first timestamp associated with the previous UE flight path information, the differential flight path information is at least partially based on the first timestamp and the second timestamp, and the full flight path information is generated at least partially based on the previous UE flight path information and the differential flight path information.

[0194] In a seventh aspect, process 700 includes sending an indication indicating support for differential flight path information.

[0195] In an eighth aspect, the indication indicates that differential flight path support is enabled.

[0196] In a ninth aspect, sending the indication comprises broadcasting the indication in system information.

[0197] In a tenth aspect, the indication is a first indication, and process 700 includes sending a second indication of a validity duration associated with verifying the differential flight path information.

[0198] In an eleventh aspect, the flight path information request includes a timestamp based at least in part on previous UE flight path information.

[0199] In a twelfth aspect, process 700 includes receiving the timestamp from a core network.

[0200] In a thirteenth aspect, process 700 includes receiving the timestamp from the UE along with the previous UE flight path information.

[0201] In a fourteenth aspect, process 700 includes receiving a flight path information request response from the UE indicating no change in UE flight path information.

[0202] In a fifteenth aspect, process 700 includes receiving a flight path identifier from the UE, communicating the flight path identifier to a core network, and receiving UE flight path information based at least in part on the flight path identifier from the core network.

[0203] In a sixteenth aspect, the flight path information request includes a timestamp associated with previous UE flight path information associated with the UE.

[0204] In a seventeenth aspect, the previous UE flight path information is based at least in part on last reported UE flight path information associated with the UE.

[0205] In an eighteenth aspect, process 700 includes receiving the last reported UE flight path information from a core network.

[0206] In a nineteenth aspect, process 700 includes receiving the last reported UE flight path information from the UE before sending the flight path information request.

[0207] In a twentieth aspect, process 700 includes sending differential flight path configuration information.

[0208] In a twenty-first aspect, the differential flight path configuration information includes at least one of the following: a position change threshold, a time change threshold, a lateral positioning change threshold, a longitudinal positioning change threshold, or an altitude change threshold.

[0209] In a twenty-second aspect, sending the differential flight path configuration information includes broadcasting the differential flight path configuration information in system information.

[0210] In a twenty-third aspect, sending the differential flight path configuration information includes sending the differential flight path configuration information in a unicast message.

[0211] In a twenty-fourth aspect, process 700 includes communicating the UE flight path information to a core network based at least in part on NGAP procedures associated with the core network.

[0212] In a twenty-fifth aspect, the NGAP process includes a UE flight path management process.

[0213] In a twenty-sixth aspect, process 700 includes communicating to the core network a timestamp associated with generation of the UE flight path information.

[0214] In a twenty-seventh aspect, the NGAP process is based at least in part on an AMF at the core network.

[0215] In a twenty-eighth aspect, process 700 includes receiving a flight plan identifier associated with the UE from the core network, and communicating the flight plan identifier to the UE.

[0216] In a twenty-ninth aspect, process 700 includes requesting stored flight path information from an AMF at a core network, and receiving the stored flight path information as a response from the core network based at least in part on the AMF at the core network.

[0217] In a thirtieth aspect, requesting the stored flight path information comprises requesting the stored flight path information based at least in part on establishing a request procedure and establishing a response procedure.

[0218] In a thirty-first aspect, requesting the stored flight path information includes requesting the stored flight path information based at least in part on a retrieve UE information procedure and a UE information transfer procedure.

[0219] In a thirty-second aspect, process 700 includes receiving differential flight path information from the UE as the UE flight path information, and communicating the differential flight path information to a core network.

[0220] In a thirty-third aspect, process 700 includes locally storing the UE flight path information.

[0221] although Figure 7 Example blocks of process 700 are shown, but in some aspects, process 700 may include Figure 7 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0222] Figure 8 is a diagram illustrating an example process 800 performed, for example, at a UE or an apparatus of a UE, according to the present disclosure. Example process 800 is an example in which the apparatus or the UE (eg, UE 120) performs operations associated with reduced flight path reporting overhead.

[0223] like Figure 8 As shown, in some aspects, process 800 may include receiving an indication that a network node supports differential flight path information (block 810). For example, the UE (e.g., using Fig.12 The depicted communications manager 140 and / or receiving component 1202) can receive an indication that a network node supports differential flight path information, as described above.

[0224] like Figure 8 As further shown, in some aspects, process 800 may include receiving a flight path information request from the network node (block 820). Fig.12 The depicted communications manager 140 and / or receiving component 1202) can receive a flight path information request from the network node, as described above.

[0225] like Figure 8 As further shown, in some aspects, process 800 may include sending a response to the flight path information request based at least in part on the network node supporting the differential flight path information (block 830). Fig.12 The depicted communications manager 140 and / or sending component 1204) can send a response to the flight path information request based at least in part on the network node supporting the differential flight path information, as described above.

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

[0227] In a first aspect, sending the response includes sending UE flight path information based at least in part on receiving the flight path information request, and process 800 includes updating a last reported flight path buffer based at least in part on the UE flight path information.

[0228] In a second aspect, the UE flight path information includes full flight path information.

[0229] In a third aspect, process 800 includes determining that the differential flight path information is invalid based at least in part on a validity duration, and sending the UE flight path information includes sending the full flight path information based at least in part on determining that the differential flight path information is invalid.

[0230] In a fourth aspect, updating the last reported flight path buffer includes removing the stored flight path information from the last reported flight path buffer.

[0231] In a fifth aspect, process 800 includes storing the full flight path information in the last reported flight path buffer.

[0232] In a sixth aspect, the UE flight path information includes the differential flight path information.

[0233] In a seventh aspect, process 800 includes determining that the differential flight path information is valid based at least in part on a validity duration, and sending the UE flight path information includes sending the differential flight path information as the UE flight path information based at least in part on determining that the differential flight path information is valid.

[0234] In an eighth aspect, the differential flight path information indicates at least one of: updating a first waypoint included in a previous UE flight path information, removing a second waypoint from the previous UE flight path information, or adding a third waypoint to the previous UE flight path information.

[0235] In a ninth aspect, process 800 includes generating the differential flight path information based at least in part on comparing a current waypoint to a previous waypoint.

[0236] In a tenth aspect, comparing the current waypoint to the previous waypoint includes determining whether a change between the current waypoint and the previous waypoint satisfies a difference threshold.

[0237] In an eleventh aspect, the change comprises at least one of: a change in position, or a time difference between the current waypoint and the previous waypoint.

[0238] In a twelfth aspect, updating the last reported flight path buffer includes storing a timestamp associated with the UE flight path information in the last reported flight path buffer.

[0239] In a thirteenth aspect, the indication indicates that differential flight path support is enabled.

[0240] In a fourteenth aspect, receiving the indication comprises receiving the indication in system information.

[0241] In a fifteenth aspect, the indication is a first indication, and process 800 includes receiving a second indication of a validity duration associated with verifying the differential flight path information.

[0242] In a sixteenth aspect, the flight path information request includes a timestamp based at least in part on previous UE flight path information associated with the UE.

[0243] In a seventeenth aspect, receiving the flight path information request includes receiving the flight path information request based at least in part on a unicast message.

[0244] In an eighteenth aspect, process 800 includes sending a flight path information request response indicating no change in UE flight path information.

[0245] In a nineteenth aspect, process 800 includes sending a flight path information request response including a flight path identifier.

[0246] In a twentieth aspect, process 800 includes receiving the flight path identifier from the network node based at least in part on a UUAA process.

[0247] In a twenty-first aspect, the flight path information request includes a timestamp associated with previous UE flight path information.

[0248] In a twenty-second aspect, the previous UE flight path information is based at least in part on last reported UE flight information associated with the UE.

[0249] In a twenty-third aspect, process 800 includes receiving differential flight path configuration information.

[0250] In a twenty-fourth aspect, the differential flight path configuration information includes at least one of: a position change threshold, a time change threshold, a lateral positioning change threshold, a longitudinal positioning change threshold, or an altitude change threshold.

[0251] In a twenty-fifth aspect, receiving the differential flight path configuration information includes receiving the differential flight path configuration information in system information.

[0252] In a twenty-sixth aspect, receiving the differential flight path configuration information includes receiving the differential flight path configuration information in a unicast message.

[0253] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0254] Fig. 9 is a diagram illustrating an example process 900 performed, for example, at a UE or at an apparatus of a UE in accordance with the present disclosure. Example process 900 is an example in which the apparatus or the UE (eg, UE 120) performs operations associated with reduced flight path reporting overhead.

[0255] like Fig. 9 As shown, in some aspects, process 900 may include detecting a UE flight path change that satisfies a threshold (block 910). For example, the UE (e.g., using Fig.12 The depicted communications manager 140 and / or flight path information manager component 1208) can detect a UE flight path change that satisfies a threshold, as described above.

[0256] like Fig. 9 As further shown, in some aspects, process 900 may include sending a flight path change indication to a network node (block 920). Fig.12 The depicted communications manager 140 and / or sending component 1204) can send a flight path change indication to a network node, as described above.

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

[0258] In a first aspect, the UE flight path change is based at least in part on last reported UE flight path information.

[0259] In a second aspect, sending the flight path change indication includes sending the flight path change indication in a MAC CE.

[0260] In a third aspect, sending the flight path change indication includes sending the flight path change indication in a UE assistance information message.

[0261] In a fourth aspect, process 900 includes sending current UE flight path information indicating a change in the UE flight path.

[0262] In a fifth aspect, the current UE flight path information includes full flight path information or differential flight path information.

[0263] In a sixth aspect, process 900 includes receiving a flight path information request from the network node, and sending the current UE flight path information is based at least in part on receiving the flight path information request from the network node.

[0264] In a seventh aspect, sending the current UE flight path information includes autonomously sending the current UE flight path information.

[0265] In an eighth aspect, process 900 includes receiving an indication that the network node supports differential flight path information, and sending the flight path change indication is based at least in part on receiving the indication that the network node supports the differential flight path information.

[0266] although Fig. 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0267] Fig.10 is a diagram illustrating an example process 1000 performed, for example, at a network node or at an apparatus of a network node in accordance with the present disclosure. Example process 1000 is an example in which the apparatus or the network node (eg, network node 110) performs operations associated with reduced flight path reporting overhead.

[0268] like Fig.10 As shown, in some aspects, process 1000 may include receiving last reported UE flight path information from the UE (block 1010). For example, the network node (e.g., using Fig.11 The depicted communications manager 150 and / or receiving component 1102) can receive last reported UE flight path information from the UE, as described above.

[0269] like Fig.10 As further shown, in some aspects, process 1000 may include receiving, from the UE, a flight path change indication associated with a UE flight path change without sending a flight path information request (block 1020). Fig.11 The depicted communications manager 150 and / or receiving component 1102) can receive a flight path change indication associated with a UE flight path change from the UE without sending a flight path information request, as described above.

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

[0271] In a first aspect, the UE flight path change is based at least in part on the last reported UE flight path information.

[0272] In a second aspect, receiving the flight path change indication comprises receiving the flight path change indication in a MAC CE.

[0273] In a third aspect, receiving the flight path change indication includes receiving the flight path change indication in a UE assistance information message.

[0274] In a fourth aspect, process 1000 includes receiving current UE flight path information including the flight path change indication.

[0275] In a fifth aspect, the current UE flight path information includes full flight path information or differential flight path information.

[0276] In a sixth aspect, process 1000 includes sending the flight path information request to the UE based at least in part on receiving the flight path change indication, and receiving the current UE flight path information is based at least in part on receiving the flight path information request from the network node.

[0277] In a seventh aspect, receiving the current UE flight path information includes autonomously receiving the current UE flight path information without sending the flight path information request.

[0278] although Fig.10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Fig.10 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0279] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a network node, or a network node may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may use receiving component 1102 and transmitting component 1104 to communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 1100 may include a communication manager 150. Communication manager 150 may include one or more of a flight path information manager component 1108, etc.

[0280] In some aspects, the apparatus 1100 may be configured to perform Figures 4 to 10 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 7 The process 700 Fig.10 In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by one or more controllers or one or more processors to perform the function or operation of the component.

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

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

[0283] The sending component 1104 can send a flight path information request indicating a differential flight path reporting configuration associated with UE flight path information associated with the UE. The receiving component 1102 can receive the UE flight path information based at least in part on the differential flight path reporting configuration.

[0284] The flight path information manager component 1108 can communicate a flight path query associated with the UE to a core network. Alternatively or additionally, the receiving component 1102 can receive a response to the flight path query from the core network, and the flight path information request can be based at least in part on the response from the core network. In some aspects, the flight path information manager component 1108 can communicate full flight path information to the core network, and the full flight path information can be based at least in part on the UE flight path information.

[0285] The sending component 1104 can send an indication indicating support for differential flight path information.Alternatively or additionally, the receiving component 1102 can receive a timestamp from a core network.In some aspects, the receiving component 1102 can receive the timestamp from the UE along with the previous UE flight path information.

[0286] Receiving component 1102 can receive a flight path information request response from the UE indicating no change in UE flight path information. Alternatively or additionally, receiving component 1102 can receive a flight path identifier from the UE. Flight path information manager component 1108 can communicate the flight path identifier to a core network. In some aspects, receiving component 1102 can receive UE flight path information from the core network based at least in part on the flight path identifier.

[0287] The receiving component 1102 can receive the last reported UE flight path information from the core network. In some aspects, the receiving component 1102 can receive the last reported UE flight path information from the UE before sending the flight path information request. Alternatively or additionally, the sending component 1104 can send the differential flight path configuration information.

[0288] The flight path information manager component 1108 can communicate the UE flight path information to the core network based at least in part on a NGAP process associated with the core network. Alternatively or additionally, the flight path information manager component 1108 can communicate a timestamp associated with the generation of the UE flight path information to the core network. In some aspects, the receiving component 1102 can receive a flight plan identifier associated with the UE from the core network. The flight path information manager component 1108 can communicate the flight plan identifier to the UE.

[0289] The flight path information manager component 1108 can request the stored flight path information from the AMF at the core network.Alternatively or additionally, the receiving component 1102 can receive the stored flight path information as a response from the core network based at least in part on the AMF at the core network.

[0290] Receiving component 1102 can receive differential flight path information from the UE as the UE flight path information. In some aspects, flight path information manager component 1108 can communicate the differential flight path information to a core network. Alternatively or additionally, flight path information manager component 1108 can store the UE flight path information locally.

[0291] The receiving component 1102 can receive last reported UE flight path information from the UE. The receiving component 1102 can receive a flight path change indication associated with a UE flight path change from the UE without sending a flight path information request. In some aspects, the receiving component 1102 can receive current UE flight path information including the flight path change indication. The sending component 1104 can send the flight path information request to the UE based at least in part on receiving the flight path change indication, and receiving the current UE flight path information is based at least in part on receiving the flight path information request from the network node.

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

[0293] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a UE, or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 140. Communication manager 140 may include one or more of a flight path information manager component 1208, etc.

[0294] In some aspects, the apparatus 1200 may be configured to perform Figures 4 to 10 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 8 The process of 800 Fig. 9 In some aspects, Fig.12 The device 1200 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by one or more controllers or one or more processors to perform the function or operation of the component.

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

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

[0297] Receiving component 1202 can receive an indication that a network node supports differential flight path information. Receiving component 1202 can receive a flight path information request from the network node. Sending component 1204 can send a response to the flight path information request based at least in part on the network node supporting the differential flight path information.

[0298] The flight path information manager component 1208 can determine that the differential flight path information is invalid based at least in part on the validity duration. Alternatively or additionally, the flight path information manager component 1208 can store the full flight path information in a last reported flight path buffer. In some aspects, the flight path information manager component 1208 can determine that the differential flight path information is valid based at least in part on the validity duration. The flight path information manager component 1208 can generate the differential flight path information based at least in part on comparing the current waypoint to a previous waypoint.

[0299] The sending component 1204 can send a flight path information request response indicating that there is no change in the UE flight path information. Alternatively or additionally, the sending component 1204 can send a flight path information request response including a flight path identifier. In some aspects, the receiving component 1202 can receive the flight path identifier from the network node based at least in part on a UUAA procedure.

[0300] The receiving component 1202 can receive differential flight path configuration information. Alternatively or additionally, the flight path information manager component 1208 can detect a UE flight path change that satisfies a threshold. The sending component 1204 can send a flight path change indication to a network node. In some aspects, the sending component 1204 can send current UE flight path information indicating the UE flight path change.

[0301] The receiving component 1202 can receive a flight path information request from the network node, and sending the current UE flight path information is based at least in part on receiving the flight path information request from the network node. Alternatively or additionally, the receiving component 1202 can receive an indication that the network node supports differential flight path information, and send the flight path change indication based at least in part on receiving the indication that the network node supports the differential flight path information.

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

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

[0304] Aspect 1: A method of wireless communication performed by a device of a network node, the method comprising: sending a flight path information request indicating a differential flight path reporting configuration, the differential flight path reporting configuration being associated with UE flight path information associated with a user equipment (UE); and receiving the UE flight path information, the UE flight path information being at least partially based on the differential flight path reporting configuration.

[0305] Aspect 2: According to the method of Aspect 1, the method also includes: communicating a flight path query associated with the UE to a core network; and receiving a response to the flight path query from the core network, wherein the flight path information request is at least partially based on the response from the core network.

[0306] Aspect 3: The method according to aspect 2 further comprises: communicating full flight path information to the core network, wherein the full flight path information is based at least in part on the UE flight path information.

[0307] Aspect 4: The method according to aspect 3, wherein the UE flight path information includes the full flight path information.

[0308] Aspect 5: A method according to aspect 3, wherein the UE flight path information includes differential flight path information, and the method further comprises: generating the full flight path information based at least in part on the response from the core network and the differential flight path information.

[0309] Aspect 6: A method according to Aspect 5, wherein the response from the core network includes previous UE flight path information, and wherein the differential flight path information indicates at least one of the following: updating a first waypoint included in the previous UE flight path information, removing a second waypoint from the previous UE flight path information, or adding a third waypoint to the previous UE flight path information.

[0310] Aspect 7: A method according to Aspect 5 or Aspect 6, wherein the response from the core network includes previous UE flight path information associated with the UE and a first timestamp associated with the previous UE flight path information, wherein the differential flight path information is at least partially based on the first timestamp and the second timestamp, and wherein generating the full flight path information is at least partially based on the previous UE flight path information and the differential flight path information.

[0311] Aspect 8: According to the method according to any one of aspects 1 to 7, the method also includes: sending an indication indicating support for the differential flight path information.

[0312] Aspect 9: The method according to aspect 8, wherein the indication indicates that differential flight path support is enabled.

[0313] Aspect 10: The method according to aspect 8 or aspect 9, wherein sending the indication comprises: broadcasting the indication in system information.

[0314] Aspect 11: The method according to any one of aspects 8 to 10, wherein the indication is a first indication, and the method further comprises: sending a second indication of a validity duration associated with verifying the differential flight path information.

[0315] Aspect 12: The method according to any one of aspects 1 to 11, wherein the flight path information request includes a timestamp based at least in part on previous UE flight path information.

[0316] Aspect 13: The method according to aspect 12 further comprises: receiving the timestamp from a core network.

[0317] Aspect 14: The method according to aspect 12, the method further comprising: receiving the timestamp from the UE together with the previous UE flight path information.

[0318] Aspect 15: According to the method according to any one of Aspects 1 to 14, the method further includes: receiving a flight path information request response from the UE indicating that the UE flight path information has not changed.

[0319] Aspect 16: According to the method described in any one of Aspects 1 to 15, the method also includes: receiving a flight path identifier from the UE; communicating the flight path identifier to a core network; and receiving UE flight path information based at least in part on the flight path identifier from the core network.

[0320] Aspect 17: The method according to any one of aspects 1 to 16, wherein the flight path information request includes a timestamp associated with previous UE flight path information associated with the UE.

[0321] Aspect 18: The method according to aspect 17, wherein the previous UE flight path information is based at least in part on last reported UE flight path information associated with the UE.

[0322] Aspect 19: According to the method of aspect 18, the method further comprises: receiving the last reported UE flight path information from a core network.

[0323] Aspect 20: The method according to aspect 18, the method further comprising: receiving the last reported UE flight path information from the UE before sending the flight path information request.

[0324] Aspect 21: According to the method described in any one of Aspects 1 to 20, the method further includes: sending differential flight path configuration information.

[0325] Aspect 22: The method according to Aspect 21, wherein the differential flight path configuration information includes at least one of the following: a position change threshold, a time change threshold, a lateral positioning change threshold, a longitudinal positioning change threshold, or an altitude change threshold.

[0326] Aspect 23: The method according to Aspect 21 or Aspect 22, wherein sending the differential flight path configuration information comprises: broadcasting the differential flight path configuration information in system information.

[0327] Aspect 24: The method according to any one of Aspects 21 to 23, wherein sending the differential flight path configuration information comprises: sending the differential flight path configuration information in a unicast message.

[0328] Aspect 25: According to any one of aspects 1 to 24, the method also includes: communicating the UE flight path information to the core network based at least in part on a Next Generation Application Protocol (NGAP) process associated with the core network.

[0329] Aspect 26: The method according to Aspect 25, wherein the NGAP process includes a UE flight path management process.

[0330] Aspect 27: The method according to aspect 25 or aspect 26 further comprises: sending a timestamp associated with the generation of the UE flight path information to the core network.

[0331] Aspect 28: A method according to any one of aspects 25 to 27, wherein the NGAP process is at least partially based on an access and mobility management function (AMF) at the core network.

[0332] Aspect 29: According to any one of Aspects 25 to 28, the method further includes: receiving a flight plan identifier associated with the UE from the core network; and communicating the flight plan identifier to the UE.

[0333] Aspect 30: According to the method described in any one of Aspects 1 to 29, the method also includes: requesting stored flight path information from an access and mobility management function (AMF) at a core network; and receiving the stored flight path information as a response from the core network based at least in part on the AMF at the core network.

[0334] Aspect 31: The method according to aspect 30, wherein requesting the stored flight path information includes: requesting the stored flight path information based at least in part on establishing a request procedure and establishing a response procedure.

[0335] Aspect 32: The method according to aspect 30, wherein requesting the stored flight path information includes: requesting the stored flight path information based at least in part on a retrieve UE information procedure and a UE information transfer procedure.

[0336] Aspect 33: According to the method according to any one of Aspects 1 to 32, the method also includes: receiving differential flight path information from the UE as the UE flight path information; and communicating the differential flight path information to a core network.

[0337] Aspect 34: According to the method according to any one of Aspects 1 to 33, the method also includes: storing the UE flight path information locally.

[0338] Aspect 35: A method of wireless communication performed by a device of a user equipment (UE), the method comprising: receiving an indication indicating that a network node supports differential flight path information; receiving a flight path information request from the network node; and sending a response to the flight path information request based at least in part on the network node supporting the differential flight path information.

[0339] Aspect 36: A method according to Aspect 35, wherein sending the response includes: sending UE flight path information based at least in part on receiving the flight path information request, and wherein the method also includes: updating the last reported flight path buffer based at least in part on the UE flight path information.

[0340] Aspect 37: The method according to Aspect 36, wherein the UE flight path information includes full flight path information.

[0341] Aspect 38: According to the method described in Aspect 37, the method also includes: determining that the differential flight path information is invalid based at least in part on the validity period; and wherein sending the UE flight path information includes: sending the full flight path information based at least in part on determining that the differential flight path information is invalid, wherein sending the UE flight path information includes: sending the full flight path information based at least in part on determining that the differential flight path information is invalid.

[0342] Aspect 39: The method according to Aspect 38, wherein updating the last reported flight path buffer includes: removing stored flight path information from the last reported flight path buffer.

[0343] Aspect 40: According to the method of Aspect 39, the method also includes: storing the full flight path information in the last reported flight path buffer.

[0344] Aspect 41: The method according to aspect 36, wherein the UE flight path information includes the differential flight path information.

[0345] Aspect 42: According to the method described in Aspect 41, the method also includes: determining that the differential flight path information is valid based at least in part on a validity period, wherein sending the UE flight path information includes: sending the differential flight path information as the UE flight path information based at least in part on determining that the differential flight path information is valid, wherein sending the UE flight path information includes: sending the differential flight path information as the UE flight path information based at least in part on determining that the differential flight path information is valid.

[0346] Aspect 43: A method according to Aspect 41, wherein the differential flight path information indicates at least one of: updating a first waypoint included in previous UE flight path information, removing a second waypoint from the previous UE flight path information, or adding a third waypoint to the previous UE flight path information.

[0347] Aspect 44: The method according to Aspect 41 further includes: generating the differential flight path information based at least in part on comparing the current waypoint with the previous waypoint.

[0348] Aspect 45: The method according to aspect 44, wherein comparing the current waypoint with the previous waypoint includes: determining whether the change between the current waypoint and the previous waypoint satisfies a difference threshold.

[0349] Aspect 46: The method according to aspect 45, wherein the change comprises at least one of the following: a change in position, or a time difference between the current waypoint and the previous waypoint.

[0350] Aspect 47: The method according to aspect 36, wherein updating the last reported flight path buffer includes: storing a timestamp associated with the UE flight path information in the last reported flight path buffer.

[0351] Aspect 48: A method according to any one of Aspects 35 to 47, wherein the indication indicates that differential flight path support is enabled.

[0352] Aspect 49: The method according to aspect 48, wherein receiving the indication comprises: receiving the indication in system information.

[0353] Aspect 50: The method according to Aspect 48 or Aspect 49, wherein the indication is a first indication, and the method further comprises: receiving a second indication of a validity duration associated with verifying the differential flight path information.

[0354] Aspect 51: A method according to any one of aspects 35 to 50, wherein the flight path information request includes a timestamp based at least in part on previous UE flight path information associated with the UE.

[0355] Aspect 52: The method according to any one of aspects 35 to 51, wherein receiving the flight path information request includes: receiving the flight path information request based at least in part on a unicast message.

[0356] Aspect 53: According to the method of any one of Aspects 35 to 52, the method further includes: sending a flight path information request response indicating that the UE flight path information has not changed.

[0357] Aspect 54: According to the method described in any one of Aspects 35 to 53, the method further includes: sending a flight path information request response including a flight path identifier.

[0358] Aspect 55: The method according to Aspect 54 further comprises: receiving the flight path identifier from the network node based at least in part on an unmanned aerial vehicle unmanned system service provider authorization and / or authentication (UUAA) process.

[0359] Aspect 56: A method according to any one of aspects 35 to 55, wherein the flight path information request includes a timestamp associated with previous UE flight path information.

[0360] Aspect 57: The method according to aspect 56, wherein the previous UE flight path information is based at least in part on last reported UE flight information associated with the UE.

[0361] Aspect 58: According to the method described in any one of Aspects 35 to 57, the method further includes: receiving differential flight path configuration information.

[0362] Aspect 59: A method according to Aspect 58, wherein the differential flight path configuration information includes at least one of the following: a position change threshold, a time change threshold, a lateral positioning change threshold, a longitudinal positioning change threshold, or an altitude change threshold.

[0363] Aspect 60: The method according to Aspect 58, wherein receiving the differential flight path configuration information comprises: receiving the differential flight path configuration information in system information.

[0364] Aspect 61: The method according to Aspect 58, wherein receiving the differential flight path configuration information includes: receiving the differential flight path configuration information in a unicast message.

[0365] Aspect 62: A method of wireless communication performed by a device of a user equipment (UE), the method comprising: detecting a UE flight path change that satisfies a threshold; and sending a flight path change indication to a network node.

[0366] Aspect 63: The method according to aspect 62, wherein the UE flight path change is based at least in part on the last reported UE flight path information.

[0367] Aspect 64: The method according to any one of aspects 62 to 63, wherein sending the flight path change indication comprises: sending the flight path change indication in a medium access control (MAC) control element (CE).

[0368] Aspect 65: A method according to any one of Aspects 62 to 64, wherein sending the flight path change indication comprises: sending the flight path change indication in a UE assistance information message.

[0369] Aspect 66: According to the method according to any one of Aspects 62 to 65, the method also includes: sending current UE flight path information indicating a change in the UE flight path.

[0370] Aspect 67: The method according to Aspect 66, wherein the current UE flight path information comprises: full flight path information; or differential flight path information.

[0371] Aspect 68: The method according to aspect 66 further includes: receiving a flight path information request from the network node, wherein sending the current UE flight path information is at least partially based on receiving the flight path information request from the network node.

[0372] Aspect 69: The method according to aspect 66, wherein sending the current UE flight path information includes autonomously sending the current UE flight path information.

[0373] Aspect 70: According to the method described in any one of Aspects 62 to 69, the method also includes: receiving an indication indicating that the network node supports differential flight path information, wherein sending the flight path change indication is at least partially based on receiving an indication that the network node supports the differential flight path information.

[0374] Aspect 71: A method of wireless communication performed by an apparatus of a network node, the method comprising: receiving last reported UE flight path information from a user equipment (UE); and receiving a flight path change indication associated with a UE flight path change from the UE without sending a flight path information request.

[0375] Aspect 72: The method according to aspect 71, wherein the UE flight path change is based at least in part on the last reported UE flight path information.

[0376] Aspect 73: The method according to any one of Aspects 71 to 72, wherein receiving the flight path change indication comprises: receiving the flight path change indication in a medium access control (MAC) control element (CE).

[0377] Aspect 74: A method according to any one of Aspects 71 to 73, wherein receiving the flight path change indication comprises: receiving the flight path change indication in a UE assistance information message.

[0378] Aspect 75: According to the method according to any one of Aspects 71 to 74, the method also includes: receiving current UE flight path information including the flight path change indication.

[0379] Aspect 76: A method according to Aspect 75, wherein the current UE flight path information comprises: full flight path information; or differential flight path information.

[0380] Aspect 77: According to the method according to Aspect 75, the method also includes: sending the flight path information request to the UE at least in part based on receiving the flight path change indication, wherein receiving the current UE flight path information is at least in part based on receiving the flight path information request from the network node.

[0381] Aspect 78: The method according to aspect 75, wherein receiving the current UE flight path information includes: autonomously receiving the current UE flight path information without sending the flight path information request.

[0382] Aspect 79: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform one or more of the methods described in Aspects 1 to 34.

[0383] Aspect 80: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform one or more of the methods described in Aspects 1 to 34.

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

[0385] Aspect 82: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 34.

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

[0387] Aspect 84: A device for wireless communication, the device comprising a processing system, the processing system comprising: one or more processors; and one or more memories, the one or more memories being coupled to the one or more processors, the processing system being configured to cause the device to execute one or more of the methods described in Aspects 1 to 34.

[0388] Aspect 85: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors being configured individually or collectively to cause the device to perform one or more of the methods described in Aspects 1 to 34.

[0389] Aspect 86: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform one or more of the methods described in Aspects 35 to 61.

[0390] Aspect 87: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform one or more of the methods described in Aspects 35 to 61.

[0391] Aspect 88: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 35 to 61.

[0392] Aspect 89: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method according to one or more of aspects 35 to 61.

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

[0394] Aspect 91: A device for wireless communication, the device comprising a processing system, the processing system comprising: one or more processors; and one or more memories, the one or more memories being coupled to the one or more processors, the processing system being configured to cause the device to execute one or more of the methods described in Aspects 35 to 61.

[0395] Aspect 92: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors being configured individually or collectively to cause the device to perform one or more of the methods described in Aspects 35 to 61.

[0396] Aspect 93: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform one or more of the methods described in Aspects 62 to 70.

[0397] Aspect 94: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform one or more of the methods described in Aspects 62 to 70.

[0398] Aspect 95: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 62 to 70.

[0399] Aspect 96: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method according to one or more of aspects 62 to 70.

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

[0401] Aspect 98: A device for wireless communication, the device comprising a processing system, the processing system comprising: one or more processors; and one or more memories, the one or more memories being coupled to the one or more processors, the processing system being configured to cause the device to execute one or more of the methods described in Aspects 62 to 70.

[0402] Aspect 99: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors being configured individually or collectively to cause the device to perform one or more of the methods described in Aspects 62 to 70.

[0403] Aspect 100: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform one or more of the methods described in Aspects 71 to 78.

[0404] Aspect 101: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform one or more of the methods described in Aspects 71 to 78.

[0405] Aspect 102: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 71 to 78.

[0406] Aspect 103: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method according to one or more of aspects 71 to 78.

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

[0408] Aspect 105: A device for wireless communication, the device comprising a processing system, the processing system comprising: one or more processors; and one or more memories, the one or more memories being coupled to the one or more processors, the processing system being configured to cause the device to execute one or more of the methods described in Aspects 71 to 78.

[0409] Aspect 106: An apparatus for performing wireless communications at a device, the apparatus comprising: one or more memories; and one or more processors, the one or more processors coupled to the one or more memories, the one or more processors being configured individually or collectively to cause the device to perform one or more of the methods described in Aspects 71 to 78.

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

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

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

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

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

Claims

1. An apparatus for wireless communication at a network node, the apparatus comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and being individually or collectively configured to cause the network node to: sending a flight path information request indicating a differential flight path reporting configuration associated with a user equipment (UE) flight path information associated with the UE; and The UE flight path information is received, the UE flight path information being based at least in part on the differential flight path reporting configuration.

2. The apparatus of claim 1 , wherein the one or more processors are further configured to cause the network node to: communicating a flight path query associated with the UE to a core network; and receiving a response to the flight path query from the core network, Wherein the flight path information request is based at least in part on the response from the core network.

3. The apparatus of claim 2, wherein the UE flight path information comprises differential flight path information, and the one or more processors are further configured to cause the network node to: Full flight path information is generated based at least in part on the response from the core network and the differential flight path information.

4. The apparatus of claim 1 , wherein the one or more processors are further configured to cause the network node to: Sends an indication of support for differential flight path information.

5. The apparatus of claim 4, wherein the one or more processors are further configured to cause the network node to: A second indication of a validity duration associated with verifying the differential flight path information is sent.

6. The apparatus of claim 1, wherein the flight path information request includes a timestamp based at least in part on previous UE flight path information.

7. The apparatus of claim 1 , wherein the one or more processors are further configured to cause the network node to: A flight path information request response is received from the UE indicating that there is no change in UE flight path information.

8. The apparatus of claim 1, wherein the one or more processors are further configured to cause the network node to: receiving a flight path identifier from the UE; communicating the flight path identifier to a core network; and UE flight path information based at least in part on the flight path identifier is received from the core network.

9. The apparatus of claim 1 , wherein the one or more processors are further configured to cause the network node to: Sends differential flight path configuration information.

10. The apparatus of claim 1, wherein the one or more processors are further configured to cause the network node to: The UE flight path information is communicated to a core network based at least in part on Next Generation Application Protocol (NGAP) procedures associated with the core network.

11. The apparatus of claim 1 , wherein the one or more processors are further configured to cause the network node to: requesting stored flight path information from an access and mobility management function (AMF) at the core network; and The stored flight path information is received as a response from the core network based at least in part on the AMF at the core network.

12. The apparatus of claim 1, wherein the one or more processors are further configured to cause the network node to: receiving differential flight path information from the UE as the UE flight path information; and The differential flight path information is communicated to a core network.

13. The apparatus of claim 1 , wherein the one or more processors are further configured to cause the network node to: The UE flight path information is stored locally.

14. An apparatus for wireless communication at a UE, the apparatus comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and configured to cause the UE to: receiving an indication indicating that the network node supports differential flight path information; receiving a flight path information request from the network node; and A response to the flight path information request is sent based at least in part on the network node supporting the differential flight path information.

15. The apparatus of claim 14, wherein in order for the UE to send the response, the one or more processors are configured to cause the UE to: sending UE flight path information based at least in part on receiving the flight path information request, and The one or more processors are further configured to cause the UE to: A last reported flight path buffer is updated based at least in part on the UE flight path information.

16. The apparatus of claim 15, wherein the UE flight path information comprises full flight path information.

17. The apparatus of claim 16, wherein the one or more processors are further configured to cause the UE to: determining that the differential flight path information is invalid based at least in part on a validity duration; and Wherein, in order to enable the UE to send the UE flight path information, the one or more processors are configured to enable the UE to: The full flight path information is sent based at least in part on determining that the differential flight path information is invalid.

18. The apparatus of claim 15, wherein the UE flight path information comprises the differential flight path information.

19. The apparatus of claim 15, wherein the flight path information request includes a timestamp based at least in part on previous UE flight path information associated with the UE.

20. The apparatus of claim 14, wherein the one or more processors are further configured to cause the UE to: A flight path information request response is sent indicating that there is no change in the UE flight path information.

21. The apparatus of claim 14, wherein the one or more processors are further configured to cause the UE to: A flight path information request response is sent including a flight path identifier.

22. The apparatus of claim 14, wherein the one or more processors are further configured to cause the UE to: Receive differential flight path configuration information.

23. An apparatus for wireless communication at a UE, the apparatus comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and configured to cause the UE to: detecting a UE flight path change that satisfies a threshold; and Send flight path change indications to network nodes.

24. The apparatus of claim 23, wherein the UE flight path change is based at least in part on last reported UE flight path information.

25. The apparatus of claim 23, wherein the one or more processors are further configured to cause the UE to: Current UE flight path information is sent indicating a change in the UE flight path.

26. The apparatus of claim 25, wherein the one or more processors are further configured to cause the UE to: receiving a flight path information request from the network node, Wherein sending the current UE flight path information is based at least in part on receiving the flight path information request from the network node.

27. An apparatus for wireless communication at a network node, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the network node to: receiving last reported UE flight path information from a user equipment (UE); and A flight path change indication associated with a UE flight path change is received from the UE without sending a flight path information request.

28. The apparatus of claim 27, wherein in order for the network node to receive the flight path change indication, the one or more processors are configured to cause the network node to: Receiving the flight path change indication in at least one of: Medium Access Control (MAC) Control Element (CE) or UE assistance information message.

29. The apparatus of claim 27, wherein the one or more processors are further configured to cause the network node to: Current UE flight path information including the flight path change indication is received.

30. The apparatus of claim 29, wherein in order for the network node to receive the current UE flight path information, the one or more processors are configured to cause the network node to autonomously receive the current UE flight path information without sending the flight path information request.

Images