Flight path reporting format for unmanned aerial vehicles

Abstract

The exchange of flight path information between a mobile network and an unmanned aerial vehicle (UAV) assumes a particular format (typically a waypoint format) for the flight path information. However, in certain circumstances, the mobile network may prefer flight path information in other formats, such as a polygonal format (also known as a "flight volume format"). The techniques and apparatus described herein provide greater flexibility in formatting requests for flight path information and encoding responses to such requests. For example, a base station may send a request for flight path information with a format indicator that informs the UAV of the desired format of the requested flight path information. The UAV may then provide the flight path information based on the format indicator.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 018,444, filed on April 30, 2020, entitled “FLIGHT PATH REPORTING FORMAT FOR UNMANNED AERIAL VEHICLES,” and U.S. Non-Provisional Patent Application No. 17 / 226,480, filed on April 9, 2021, entitled “FLIGHT PATH REPORTING FORMAT FOR UNMANNED AERIAL VEHICLES,” and these two applications are expressly incorporated herein by reference. Technical Field

[0003]

[0013] Generally speaking, aspects of the present disclosure relate to wireless communications and techniques and apparatus for flight path reporting for unmanned aerial vehicles. Background Art

[0004] Wireless communication systems have been 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 communication network may include multiple base stations (BSs), wherein the BS is capable of supporting communication for multiple user equipments (UEs). The UE may communicate with the BS via a downlink and an uplink. The downlink (or forward link) refers to the communication link from the BS to the UE, while the uplink (or reverse link) refers to the communication link from the UE to the BS. As further described in detail herein, the BS may be referred to as a Node B, gNB, Access Point (AP), Radio Head, Transmission Reception Point (TRP), 5G BS, 5G Node B, and the like.

[0006] The above multiple access technologies have been adopted in a variety of telecommunication standards to provide a universal protocol that enables different wireless communication devices to communicate on a city-wide, national-wide, regional-wide, and even global scale. 5G (which may also be referred to as New Radio (NR)) is an evolutionary set of LTE mobile standards released by the Third Generation Partnership Project (3GPP). 5G is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, making full use of new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also referred to as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology and carrier aggregation. However, with the continuous increase in demand for mobile broadband access, there is a need to further improve LTE and 5G technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0007] The exchange of flight path information between a mobile network and an unmanned aerial vehicle (UAV) assumes a specific format for flight path information (typically a waypoint format). However, in certain environments, a base station or other parts of a mobile network may prefer flight path information in other formats, such as a polygonal format (also known as a "flight volume format"). For example, a UAV may need to register a flight path with an authority in a specific format other than a waypoint format. When a base station requests flight path information, the UAV may have to expend computing resources to re-encode the flight path into waypoints, even though the base station can easily use the specific format required by the authority. In another example, a base station may use a specific format to calculate a radio access network (RAN) handover of the UAV to another base station. The base station may have to expend computing resources to re-encode waypoints received from the UAV into a specific format for RAN handover, even though the UAV already has a copy of the flight path encoded in the specific format.

[0008] Some techniques and apparatus described herein provide greater flexibility in formatting requests for flight path information and encoding responses to such requests. For example, the techniques and apparatus described herein may provide an indicator of the format of the flight path information included in a container for the flight path information. Thus, a base station may send a request with an indicator that informs the UAV of the desired format for the requested flight path information. The UAV may then provide the flight path information in a container encoded according to the format indicator.

[0009] The flexibility provided by the techniques and apparatus described herein can reduce computing resources consumed by a UAV and / or a mobile network in providing and / or using flight path information. For example, a UAV can save computing resources when a mobile network provides a format indicator that requests flight path information in a format in which the UAV already stores flight path information. In another example, a mobile network can save computing resources by requesting flight path information in a format that the mobile network can use directly, rather than converting from another format provided by the UAV (e.g., re-encoding a series of waypoints).

[0010] In one aspect of the present disclosure, a method, a user equipment (UE), a network node, a network device, an apparatus, and a computer program product are provided.

[0011] In some aspects, the method may be performed by a UE. The method may include: receiving an indication of a format among a plurality of formats for reporting flight path information to a network node; receiving a request for the flight path information; and sending the flight path information to the network node according to the format and based at least in part on receiving the request for the flight path information.

[0012] In some aspects, the UE may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive an indication of a format among a plurality of formats for reporting flight path information to a network node; receive a request for the flight path information; and send the flight path information to the network node according to the format and based at least in part on receiving the request for the flight path information.

[0013] In some aspects, the apparatus may include: a unit for receiving an indication of a format among a plurality of formats for reporting flight path information to a network node; a unit for receiving a request for the flight path information; and a unit for sending the flight path information to the network node according to the format and based at least in part on receiving the request for the flight path information.

[0014] In some aspects, the computer program product may include a non-transitory computer-readable medium having one or more instructions stored thereon. When the one or more instructions are executed by one or more processors of a UE, the one or more processors may be caused to perform operations such as: receiving an indication of a format among a plurality of formats for reporting flight path information to a network node; receiving a request for the flight path information; and sending the flight path information to the network node according to the format and based at least in part on receiving the request for the flight path information.

[0015] In some aspects, the method may be performed by a network node. The method may include: sending an indication of a format among a plurality of formats for reporting flight path information of the UE to a UE; sending a request for the flight path information to the UE; and receiving the flight path information from the UE according to the format and based at least in part on sending the request for the flight path information.

[0016] In some aspects, the network node may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: send an indication of a format among a plurality of formats for reporting flight path information of the UE to a UE; send a request for the flight path information to the UE; and receive the flight path information from the UE according to the format and based at least in part on sending the request for the flight path information.

[0017] In some aspects, the apparatus may include: a unit for sending an indication of a format among multiple formats for reporting flight path information of the UE to a UE; a unit for sending a request for the flight path information to the UE; and a unit for receiving the flight path information from the UE according to the format and based at least in part on sending the request for the flight path information.

[0018] In some aspects, the computer program product may include a non-transitory computer-readable medium having one or more instructions stored thereon. When the one or more instructions are executed by one or more processors of a network node, the one or more processors may be caused to perform the following operations: sending an indication of a format of a plurality of formats for reporting flight path information of the UE to a UE; sending a request for the flight path information to the UE; and receiving the flight path information from the UE according to the format and based at least in part on sending the request for the flight path information.

[0019] In some aspects, the method may be performed by a network device. The method may include: receiving information identifying a UE and a format among a plurality of formats in which the UE reports flight path information; identifying a base station serving the UE; and sending a format indicator identifying the format and a UE identifier identifying the UE to the base station.

[0020] In some aspects, the network device may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive information identifying a UE and a format among a plurality of formats in which the UE reports flight path information; identify a base station serving the UE; and send a format indicator identifying the format and a UE identifier identifying the UE to the base station.

[0021] In some aspects, the apparatus may include: a unit for receiving information identifying a UE and a format among a plurality of formats in which the UE reports flight path information; a unit for identifying a base station serving the UE; and a unit for sending a format indicator identifying the format and a UE identifier identifying the UE to the base station.

[0022] In some aspects, the computer program product may include a non-transitory computer-readable medium storing one or more instructions. When the one or more instructions are executed by one or more processors of a network device, the one or more processors may perform the following operations: receiving information identifying a UE and a format among a plurality of formats in which the UE reports flight path information; identifying a base station serving the UE; and sending a format indicator identifying the format and a UE identifier identifying the UE to the base station.

[0023] Aspects of the present invention generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network devices, wireless communication devices and / or processing systems as fully described with reference to the accompanying drawings and descriptions and as illustrated in the accompanying drawings and descriptions.

[0024] In order to better understand the following specific embodiments, the features and technical advantages of the examples according to the present disclosure have been generally summarized to a considerable extent. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as the basis for modifying or designing other structures for the same purpose of performing the present disclosure. These equivalent constructions do not depart from the scope of protection of the attached claims. When considering the following specific embodiments in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (about their organization and method of operation), and the associated advantages will be better understood. Each of these drawings is provided for illustration and description purposes only, and is not used as a limitation to the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 is a diagram illustrating an example of a wireless communication network.

[0026] Figure 2is a diagram showing an example of a base station communicating with a user equipment (UE) in a wireless communication network.

[0027] Figure 3 is a diagram illustrating an example of an unmanned aerial vehicle (UAV) in a wireless communication network.

[0028] Figure 4 is a diagram showing an example of flight path information exchange between a base station and a UE.

[0029] Figure 5 is a diagram showing an example of flight path information exchange between a base station and a UE using a prescribed format.

[0030] Figure 6 is a flow chart of a method of wireless communication performed by a UE.

[0031] Figure 7 is a flow chart of a method of wireless communication performed by a network node.

[0032] Figure 8 is a flow chart of a method of wireless communication performed by a network device.

[0033] Fig. 9 is a conceptual data flow diagram illustrating the flow of data between different components in an example apparatus.

[0034] Fig.10 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0035] Fig.11 is a conceptual data flow diagram illustrating the flow of data between different components in an example apparatus.

[0036] Fig.12 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0037] Fig.13 is a conceptual data flow diagram illustrating the flow of data between different components in an example apparatus.

[0038] Fig.14 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system. DETAILED DESCRIPTION

[0039] The specific embodiments described below in conjunction with the accompanying drawings are intended only to describe various configurations, rather than to represent that the concepts described herein can be implemented only in these configurations. In order to have a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is obvious to those of ordinary skill in the art that these concepts can be implemented without using these specific details. In some instances, in order to avoid obscuring these concepts, known structures and components are shown in block diagram form.

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

[0041] For example, an element or any part of an element or any combination of elements can be implemented using a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, separate hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. 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, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms.

[0042] Therefore, in one or more exemplary embodiments, the functions described herein can be implemented with hardware, software, firmware or any combination thereof. When implemented using software, these functions can be stored or encoded into one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that a computer can access. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), compact disc ROM (CD-ROM), or other optical disc storage, disk storage or other magnetic storage device, a combination of computer-readable media of the aforementioned type, or any other medium that can be used to store computer executable code in the form of instructions or data structures and can be accessed by a computer.

[0043] It should be noted that although this document uses terms that are generally associated with 3G and / or 4G wireless technologies to describe aspects of the present invention, various aspects of the present disclosure may also be applicable to communication systems based on other generations (e.g., 5G and subsequent technologies, including 5G technology).

[0044] Figure 1 is a diagram showing a wireless network 100 in which various aspects of the present disclosure may be implemented. The wireless network 100 may be an LTE network or some other wireless network (e.g., a 5G network). The wireless network 100 may include a plurality of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE), and a BS may also be referred to as a base station, 5G BS, Node B, gNB, 5G NB, access point, transmission reception point (TRP), and the like. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term "cell" is used.

[0045] A BS 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), allowing unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area, allowing unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home), allowing restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "5G BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably.

[0046] In some examples, the cell need not be stationary, and the geographic area of ​​the cell may move according to the location of the mobile BS. In some examples, the BSs may be interconnected with each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (e.g., direct physical connections, virtual networks, etc.) using any appropriate transport network.

[0047] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and send transmissions of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, a relay station 110d may communicate with the macro BS 110a and the UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0048] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a higher transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0049] The network device 130 may be coupled to a group of BSs and provide coordination and control for these BSs. The network device 130 may communicate with these BSs via a backhaul. These BSs may also communicate with each other, for example, directly or indirectly via a wireless backhaul or a wired backhaul.

[0050] UE 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be stationary or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE 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 device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biosensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio device), a vehicle-mounted component or sensor, a smart meter / sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless medium or a wired medium.

[0051] Some UEs may be considered as machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. For example, MTC and eMTC UEs include robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that can communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node may provide, for example, a connection to a network or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 (e.g., a processor component, a memory component, etc.).

[0052] Generally, in a given geographic area, any number of wireless networks can be deployed. Each wireless network can support a specific RAT and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. Each frequency can 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 can be deployed.

[0053] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station) allocates resources for communications between some or all devices and equipment within a service area or cell of the scheduling entity. In the present disclosure, as further discussed below, a scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, the subordinate entities utilize resources allocated by the scheduling entity.

[0054] The base station is not the only entity that acts as a scheduling entity. That is, in some examples, the UE can act as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE acts as a scheduling entity, and other UEs use the resources scheduled by the UE for wireless communication. The UE can act as a scheduling entity in a peer-to-peer (P2P) network and / or a mesh network. In the mesh network example, in addition to communicating with the scheduling entity, the UE can also optionally communicate directly with each other.

[0055] Thus, in a wireless communication network having scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more subordinate entities may communicate using the scheduled resources. The resources may be scheduled based at least in part on the mobility of a UE using the wireless communication network. For example, when the UE is an unmanned aerial vehicle (UAV), the wireless communication network may schedule the resources based at least in part on the flight path of the UAV. The wireless communication network may use the flight path to assign a base station to serve the UE and determine when the mobility of the UE warrants a handoff between base stations in the wireless communication network.

[0056] As indicated above, Figure 1 This is provided only as an example. Other examples can be found in Figure 1 The examples described are different.

[0057] Figure 2 A block diagram of a design of a base station 110 and a UE 120 is shown, where the base station 110 may be Figure 1UE 120 may be one of the base stations in Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0058] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select a modulation and coding scheme (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also 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) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, and / or reference symbols (if any), and provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 can process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog signals, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding can be used to generate synchronization signals to transmit other information.

[0059] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or other base stations and may provide received signals to demodulators (DEMODs) 254a to 254r. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if any), and provide detected symbols. A receive (RX) processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. 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, a channel quality indicator (CQI) parameter, and the like.

[0060] On the uplink, at the UE 120, a transmit processor 264 may receive data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from a controller / processor 280 and process the data and control information. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted back to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and may communicate with network device 130 via communication unit 244. Network device 130 may include communication unit 294, controller / processor 290, and memory 292.

[0061] Controller / processor 240 of base station 110, controller / processor 280 of UE 120, controller / processor 290 of network device 130, and / or Figure 2Any other component of may perform one or more techniques associated with flight path reporting of an unmanned aerial vehicle, as described in further detail elsewhere herein. For example, controller / processor 240 of base station 110, controller / processor 280 of UE 120, controller / processor 290 of network device 130, and / or Figure 2 Any other component may perform or direct e.g. Figure 6 Method 600, Figure 7 Method 700, Figure 8 The operations of method 800 and / or other processes as described herein. Memories 242, 282, and memory 292 may store data and program codes for BS 110, UE 120, and network device 130, respectively. Scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0062] As indicated above, Figure 2 This is provided only as an example. Other examples can be found in Figure 2 The examples described are different.

[0063] Figure 3 is a diagram illustrating an example of a UAV 120 in a wireless communication network environment 300. Figure 3 As shown in FIG, environment 300 may include one or more UEs 120 (which may include one or more UAVs 120 (hereinafter individually referred to as "UAVs 120" and collectively referred to as "UAVs 120")), a radio access network (RAN) 305, a core network 320, a UAV provider service (USS) device 315, and a ground control system (GCS) 310. The devices in environment 300 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0064] The UAV 120 includes an aircraft without a human pilot and may also be referred to as an unmanned aerial vehicle (UA), a drone, a remotely piloted vehicle (RPV), a remotely piloted aircraft (RPA), or a remotely operated aircraft (ROA). The UAV 120 may have a variety of shapes, sizes, configurations, characteristics, etc. for a variety of purposes and applications. In some embodiments, the UAV 120 may include one or more sensors, such as electromagnetic spectrum sensors (e.g., visible spectrum, infrared or near infrared cameras, radar systems, etc.), biosensors, temperature sensors, chemical sensors, etc. In some embodiments, the UAV 120 may include one or more components for communicating with one or more base stations 110. Additionally or alternatively, the UAV 120 may send information to the GCS 310 and / or may be able to receive information from the GCS 310, such as sensor data, flight plan information, etc. Such information may be transmitted directly (e.g., via a radio resource control (RRC) signal, etc.) and / or via a base station 110 on the RAN 305.

[0065] The RAN 305 includes one or more radio access networks, such as a code division multiple access (CDMA) RAN, a time division multiple access (TDMA) RAN, a frequency division multiple access (FDMA) RAN, a universal terrestrial radio access network (UTRAN), an evolved UTRAN (E-UTRAN) (e.g., a long term evolution (LTE) RAN, an advanced LTE (LTE-A) RAN, an unlicensed LTE (LTE-U) RAN, etc.), and / or the like. The RAN 305 may include one or more base stations 110 for providing access to the core network 320 for the UAV 120.

[0066] The base station 110 includes one or more devices capable of transmitting traffic (e.g., audio, video, text, and / or other traffic) destined for and / or received from the UAV 120. In some embodiments, the base station 110 may include an evolved Node B (eNB) associated with an LTE RAN that receives traffic from and / or sends traffic to the GCS 310 and / or USS equipment 315 via the core network 320. Additionally or alternatively, one or more base stations 110 may be associated with a RAN that is not associated with an LTE network.

[0067] The base station 110 may send traffic to and / or receive traffic from the UAV 120 via an air interface. The base station 110 may include different types of base stations, such as a macrocell base station or a small cell base station (e.g., a microcell base station, a picocell base station, and / or a femtocell base station). A macrocell base station may cover a relatively large geographic area (e.g., a radius of several kilometers). A small cell base station may be a lower power base station than a macrocell base station, which may operate in the same or different frequency bands (e.g., licensed, unlicensed, etc.) as the macrocell base station.

[0068] The GCS 310 includes one or more devices capable of managing the UAV 120 and / or the flight plan of the UAV 120. For example, the GCS 310 may include a server device, a desktop computer, a laptop computer, or a similar device. In some embodiments, the GCS 310 may communicate with one or more devices (e.g., UAV 120, USS device 315, etc.) of the environment 300 to receive information about the flight plan of the UAV 120 and / or provide suggestions associated with such flight plans, as described elsewhere herein. In some embodiments, the GCS 310 may allow a user to control the UAV 120. Additionally or alternatively, the GCS 310 may use a neural network and / or other artificial intelligence (AI) to control the UAV 120. In some embodiments, the GCS 310 may be included in a data center, a cloud computing environment, a server farm, etc. including multiple GCS 310. Although shown as being outside the core network 320, in some aspects, the GCS 310 may reside at least partially within the core network 320.

[0069] The USS device 315 includes one or more devices capable of receiving, storing, processing, and / or providing information associated with the UAV 120 and / or the GCS 310. For example, the USS device 315 may include a desktop computer, a laptop computer, a tablet computer, a mobile phone, or a similar device. In some embodiments, the UAV 120 may interact with the USS device 315 to register a flight plan; receive approval, analysis, and / or recommendations related to the flight plan, and the like.

[0070] The core network 320 includes a network that enables communication between the RAN 305 (e.g., the base station 110) and one or more devices and / or networks connected to the core network 320. For example, the core network 320 may include an evolved packet core (EPC). The core network 320 may include one or more core network devices 325, such as one or more mobility management entities (MMEs) and / or access and mobility management functions (AMFs) (hereinafter referred to as "MME / AMFs") 330, one or more network exposure functions (NEFs) and / or service capability exposure functions (SCEFs) (hereinafter referred to as "NEF / SCEFs") 335, and / or other entities and / or functions that provide mobility functions for the UAV 120 and enable the UAV 120 to communicate with other devices of the environment 300.

[0071] The MME / AMF 330 includes one or more network devices (e.g., one or more server devices) capable of managing authentication, activation, deactivation, and / or mobility functions associated with the UAV 120 connected to the core network 320. In some embodiments, the MME / AMF 330 may perform operations related to authentication of the UAV 120. The MME / AMF 330 may perform operations associated with handing over the UAV 120 from the first base station 110 to the second base station 110 when the UAV 120 transitions from a first cell associated with the first base station 110 to a second cell associated with the second base station 110. Additionally or alternatively, the MME / AMF 330 may select another MME and / or AMF (not shown) to which the UAV 120 should hand over (e.g., when the UAV 120 moves out of the range of the MME / AMF 330). In some embodiments, the MME / AMF 330 may communicate with the UAV 120 (e.g., via the base station 110 ) to obtain information about the location of the UAV 120 and / or the reachability of the UAV 120 , and may send the information to the NEF / SCEF 335 .

[0072] The NEF / SCEF 335 includes one or more network disclosure devices (e.g., one or more server devices) that can disclose capabilities, events, information, etc. in one or more wireless networks to help other devices in one or more wireless networks efficiently discover network services and / or utilize network resources. In some embodiments, the NEF / SCEF 335 may include an NEF associated with a 5G network and / or an SCEF associated with an LTE network, which receives and / or sends services from and to the UAV 120 via the MME / AMF 330 and the base station 110, and receives and / or sends services from and to the USS device 315. In some embodiments, the NEF / SCEF 335 may obtain a data structure (e.g., approval of a flight plan for the UAV 120) from the USS device 315, and divide the data structure into a plurality of data segments. In some embodiments, the NEF / SCEF 335 may determine the location and / or reachability of the UAV 120 and / or the communication capabilities of the base station 110 to determine how to send a plurality of data segments to the UAV 120.

[0073] One or more of the core network devices 325 may correspond to the network devices 130, as described above in conjunction with Figure 1 The USS device 315 may communicate with a core network 320 (eg, a UAV flight management system (UFMS)) using one or more interfaces. The UFMS may be external to the GCS 310, or may reside at least partially within the GCS 310.

[0074] As indicated above, Figure 3 Other examples can be found in Figure 3 The examples described are different.

[0075] Figure 4 4 is a diagram illustrating an example 400 of flight path information exchange between a base station and a UAV. Figure 4 As shown in , the UE may be a UAV and may communicate with a base station. For example, the UE may establish an RRC connection with the base station.

[0076] At 405, the base station may send a request for flight path information to the UE. For example, the base station may send a UEInformationRequest message, where a flightPathInfoReq field and / or a flag thereof as "1", "TRUE", or any other indicator that flight path information is sought, is included in the message. The base station may assume that the flight path information will be encoded as a series of waypoints for the UE.

[0077] In some aspects, the base station may send the message via an RRC connection. Additionally or alternatively, the request may be sent to the UE as a non-access stratum (NAS) message by an MME / AMF of a core network serving the base station. In some aspects, when the base station also requests the UE to include a timestamp with the requested flight path information, the base station may set the includeTimeStamp Boolean value to "1", "TRUE", etc.

[0078] The UE may encode a response to the UEInformationRequest message in a FlightPathInfoReport container (e.g., as defined in a 3GPP specification). By using the FlightPathInfoReport container, the UE may implicitly indicate that the response is encoded as a series of waypoints. When available, the UE may populate the TimeStamp field with the timestamp at which the UE expects to arrive at the waypoint of the flight path. For example, the UE may populate the TimeStamp field based at least in part on determining that the includeTimeStamp Boolean value is set to "1", "TRUE", etc.

[0079] At 410, based at least in part on receiving the UEInformationRequest message from the base station, the UE may send a UEInformationResponse message with a populated FlightPathInfoReport container to the base station 110. In some aspects, the UE may send the response over an RRC connection. Additionally or alternatively, the UE may send the response as a NAS message to an MME / AMF of a core network serving the base station.

[0080] Figure 4 The example exchange depicted in assumes that a particular format (typically a waypoint format) is used for flight path information, as described above. However, in certain circumstances, a base station may prefer flight path information in other formats, such as a polygonal format (also known as a "flight volume format"), etc. For example, a UAV may need to register a flight path with an authority in a particular format other than a waypoint format. When a base station requests flight path information, the UAV may expend computational resources to re-encode the flight path into waypoints, even though the base station can easily use the particular format required by the authority instead of the waypoint format. Additionally or alternatively, the base station may use the particular format to compute a RAN handoff of the UAV to another base station. The base station may expend computational resources to re-encode a flight path received from the UAV into a particular format for RAN handoff, even though the UAV already has an available copy of the flight path encoded in the particular format.

[0081] As indicated above, Figure 4Other examples can be found in Figure 4 The examples described are different.

[0082] In this article, we combine Figure 5-14 Some techniques and apparatus described herein provide greater flexibility for formatting requests for flight path information and encoding responses to such requests. For example, the techniques and apparatus described herein may provide a FlightPathInfoReport definition that includes an indicator for the format of flight path information contained in a FlightPathInfoReport container. Although the following description describes a flight path report definition as a FlightPathInfoReport definition and a flight path container as a FlightPathInfoReport container, the description is equally applicable to other types of definitions that include flight path information format indicators, and other types of containers that can carry flight path information, respectively. Thus, a base station may send a UEInformationRequest message with a FlightPathInfoFormat indicator that notifies the UAV of the desired format of the requested flight path information. Although the subsequent description describes the request message as a UEInformationRequest message and the flight path format indicator as a FlightPathInfoFormat indicator, the description is equally applicable to other types of messages that can carry requests for information, and other types of indicators that can notify the desired format of flight path information, respectively. The UAV may then provide the flight path information in a FlightPathInfoReport container encoded according to the FlightPathInfoFormat indicator.

[0083] The flexibility provided by the techniques and apparatus described herein can reduce computing resources consumed by a UAV and / or a base station in providing and / or using flight path information. For example, a UAV can save computing resources when a base station provides a FlightPathInfoFormat indicator that requests flight path information in a format in which the UAV already has stored flight path information. Additionally or alternatively, a base station can save computing resources by requesting flight path information in a format that the base station can use directly, rather than having to convert from another format provided by the UAV (e.g., re-encoding a series of waypoints).

[0084] Figure 5 5 is a diagram illustrating an example 500 of flight path information exchange between base station 110 and UE 120 using a prescribed format according to the present disclosure. Figure 5As shown, UE 120 can communicate with one or more network nodes (e.g., base station 110) on a mobile network (e.g., 5G network, LTE network, etc.). Figure 5 In the example shown, UE 120 communicates with base station 110 on a mobile network (e.g., using RRC signaling, etc.). However, the following description is also applicable to UE 120 communicating with a portion of a core network (e.g., network device 130) (e.g., MME / AMF, etc.) supporting base station 110, for example, using NAS signaling, etc.

[0085] like Figure 5 As further shown in FIG. 1 , the core network may include one or more network devices (eg, network device 130). Figure 3 As described above, the network device 130 may be an MME / AMF, NEF / SCEF, UFMS, etc. For example, the network device 130 may be connected to the network device 130 via the UFMS and / or as described above. Figure 3 Another similar interface is described, communicating with USS device 315.

[0086] At 505, network device 130 may receive information from USS device 315 identifying a UE (e.g., UE 120) and a format of a plurality of formats for reporting flight path information by UE 120. The plurality of formats may include at least a waypoint format and a polygon format (also referred to as a "flight volume format").

[0087] In some aspects, the information identifying the UE 120 and the format may be received based at least in part on the authorization of the flight plan for the UE 120. For example, when the USS device 315 authorizes the flight plan, the USS device 315 may send the information to the network device 130. The USS device 315 may send the information to the network device 130 using the UFMS and / or another interface.

[0088] In some aspects, the information identifying the UE and the format is received from the USS device 315 or from a core network device (e.g., network device 130) in communication with the USS device 315. For example, the information identifying the UE 120 and the format may be received from the USS device 315 via a SCEF application programming interface (API) or a NEF API.

[0089] In some aspects, the information identifying the UE 120 may include at least one of the following: a UAV identifier, a public subscription identifier (GPSI), another type of identifier, or a combination thereof. For example, during the registration of the UAV 120 with the USS device 315, the USS device 315 may have assigned a UAV identifier, a GPSI, and / or other type of identifier.

[0090] At 510, network device 130 may identify a base station (e.g., base station 110) serving UE 120. For example, network device 130 may include an MME / AMF serving UE 120 and may obtain a stored indication of base station 110 serving UE 120. Additionally or alternatively, network device 130 may include an NEF / SCEF for identifying the MME / AMF serving UE 120.

[0091] At 515, the network device 130 may send a format indicator identifying the format and a UE identifier identifying the UE 120 to the base station 110. In some aspects, the network device 130 may include an MME / AMF serving the UE 120 that sends the format indicator and the UE identifier to the base station 110. Additionally or alternatively, the network device 130 may include an NEF / SCEF for identifying the MME / AMF serving the UE 120 that sends the format indicator and the UE identifier to the MME / AMF for transmission to the base station 110.

[0092] In some aspects, the UE identifier may include at least one of a UAV identifier, a GPSI, or a combination thereof. The UE identifier may be the same identifier received by the network device 130 (as described above in conjunction with reference numeral 505), or may be a different identifier. For example, the network device 130 may receive a UAV identifier, obtain a GPSI corresponding to the UAV identifier, and send the GPSI. In another example, the network device 130 may receive a GPSI, obtain a UAV identifier corresponding to the GPSI, and send the UAV identifier. In another example, the network device 130 may receive a first UAV identifier assigned by the USS device 315, obtain a second UAV identifier corresponding to the first UAV identifier and assigned by the network device 130 and / or the base station 110, and send the second UAV identifier.

[0093] In some aspects, the format indicator and the UE identifier are sent to the base station 110 based at least in part on the authorization of the flight plan for the UE 120. For example, when the flight plan for the UE 120 is approved, the USS device 315 may send information to the network device 130 (e.g., information identifying the UE 120 and / or the format for the UE 120 to report the flight path information, as described above in conjunction with reference number 505) to trigger the network device 130 to send the format indicator and the UE identifier to the base station 110.

[0094] At 520, the base station 110 may send to the UE 120 an indication of a format among a plurality of formats for reporting the flight path information of the UE 120 to a network node (e.g., the base station 110). In some aspects, the format may be a static format stored in a memory of the UE 120. For example, the UE 120 may store the flight path information according to a static format (e.g., a polygonal format or other format). Additionally or alternatively, the base station 110 may obtain a format indicator as described above in conjunction with reference numeral 515.

[0095] Additionally or alternatively, the format may be determined based at least in part on the format indicator and a UE identifier identifying the UE. For example, the format indicator and the UE identifier may be received from network device 130, as described above in conjunction with reference numeral 515. In some aspects, the format indicator and the UE identifier may be received based at least in part on an authorization of a flight plan for UE 120, as described above in conjunction with reference numeral 515.

[0096] In some aspects, a format for reporting the flight path information may be indicated in at least one of a configuration message or a NAS message. For example, as described above, the format indicator may be included in an RRC message from the base station 110. Additionally or alternatively, as described above, the format indicator may be included in a NAS message from the MME / AMF, etc.

[0097] As described above, the format for reporting flight path information may be indicated in a flight path information report configuration information element of a message. For example, the format indicator may be a FlightPathInfoFormat element defined in a FlightPathInfoReportConfig container of the message. Although the following description describes the flight path format indicator as a FlightPathInfoFormat element and the flight path report container as a FlightPathInfoReportConfig container, the description is equally applicable to other types of elements that may indicate a flight path information format, and other types of containers that may respectively carry flight path information.

[0098] In some aspects, base station 110 may send the indication based at least in part on an indicator received from network device 130, as described above in connection with reference numeral 515. Additionally or alternatively, base station 110 may send the indication based at least in part on a stored indicator that obtains a format preferred by base station 110. For example, base station 110 may store the indicator based on a preference of base station 110 for flight path information in a polygonal format or other format.

[0099] At 525, base station 110 may send a request for flight path information to UE 120. In some aspects, the request and indication may be sent together. For example, base station 110 may combine the transmissions associated with reference numerals 520 and 525 by sending a UEInformationRequest message including a FlightPathInfoFormat element used as an indication. Alternatively, the request and indication may be sent separately.

[0100] In some aspects, the request may be indicated using a flight path information request field of a UE information request message. For example, as described above, the request may use a flightPathInfoReq field (e.g., marked as "1" or "TRUE" or other value) in a UEInformationRequest message to indicate the request. Although the subsequent description describes the request field as a flightPathInfoReq field, the description is equally applicable to other types of fields that may indicate an information request. Base station 110 may send a UEInformationRequest message to UE 120.

[0101] At 530, based at least in part on receiving the request for flight path information, UE 120 may send the flight path information to a network node (e.g., base station 110) according to a format. In some aspects, the flight path information may be sent in a flight path information report. For example, as described above, UE 120 may send a UEInformationResponse message having a FlightPathInfoReport container populated with the flight path information. Although the subsequent description describes the response message as a UEInformationResponse message and the flight path information container as a FlightPathInfoReport container, the description is equally applicable to other types of messages that may carry a response, and other types of containers that may carry flight path information, respectively. The FlightPathInfoReport container may conform to a FlightPathInfoReportConfig definition.

[0102] In some aspects, as described above, UE 120 may include in the UEInformationResponse message the corresponding time associated with the flight path information. For example, UE 120 may include at least one of the following: when the format is a waypoint format, the corresponding time at which UE 120 is expected to arrive at a waypoint in the set of waypoints indicated in the flight path information; when the format is a polygon format, the corresponding time at which UE 120 is expected to occupy a polygon in the set of polygons indicated in the flight path information; and so on.

[0103] In some aspects, the corresponding time that the UE 120 is expected to occupy a polygon in the set of polygons may include at least one of the following: the corresponding time that the UE 120 is expected to enter the polygon; the corresponding time that the UE 120 is expected to exit the polygon; the corresponding duration that the UE 120 is expected to occupy the polygon; and / or a combination thereof. The UE 120 may include the corresponding time that the UE 120 is expected to occupy the polygon in the set of polygons based at least in part on determining that the includeTimeStamp Boolean value included in the UEInformationRequest message is set to "1", "TRUE", etc. Although the subsequent description describes the timestamp indicator as the includeTimeStamp Boolean value, the description is equally applicable to other types of indicators that the UE can use to determine whether to include the corresponding time in the flight path information.

[0104] Base station 110 may receive the flight path information based at least in part on sending the request for the flight path information.For example, base station 110 may receive a UEInformationResponse message from UE 120 in response to sending the UEInformationResponse message to UE 120.

[0105] At 535, base station 110 may use the received flight path information to communicate with UE 120. For example, base station 110 may use the received flight path information to manage a RAN handover of UE 120 to another base station and / or perform one or more other types of communications with UE 120 based at least in part on the received flight path information.

[0106] As indicated above, Figure 5 Other examples can be found in Figure 5 The examples described are different.

[0107] Figure 6 600 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, Figure 1 UE 120, Fig. 9 Device 902, etc.) is used to execute.

[0108] At 610, the UE may receive an indication of a format in a plurality of formats for reporting flight path information to a network node. For example, the UE may receive (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) an indication of a format for reporting flight path information to a network node, as described above. In some aspects, the plurality of formats may include at least a waypoint format and a polygon format (also referred to as a "flight volume format"). In some aspects, the format for reporting flight path information may be indicated in at least one of a configuration message (e.g., an RRC message) or a NAS message.

[0109] At 620, the UE may receive a request for flight path information. For example, the UE may receive (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) a request for flight path information, as described above. In some aspects, the request may include an indication of a format as described above in connection with reference numeral 610, or may be received separately. In some aspects, the request may be indicated using a flight path information request field of a UE information request message.

[0110] At 630, the UE may send the flight path information to the network node according to the format. For example, the UE may send the flight path information to the network node according to the format and based at least in part on receiving the request for the flight path information (e.g., using the receive processor 258, the transmit processor 264, the controller / processor 280, the memory 282, etc.), as described above. In some aspects, the flight path information may be sent in a flight path information report. In some aspects, the flight path information may indicate at least one of: if the format is a waypoint format, a corresponding time that the UE is expected to arrive at a waypoint in a set of waypoints indicated in the flight path information; or if the format is a polygon format, a corresponding time that the UE is expected to occupy a polygon in the set of polygons indicated in the flight path information.

[0111] The method 600 may include additional aspects, such as any single aspect or any combination of the aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0112] In a first aspect, the plurality of formats includes at least a waypoint format and a polygon format.

[0113] In a second aspect, alone or in combination with the first aspect, the format for reporting the flight path information is indicated in at least one of a configuration message or a non-access stratum message.

[0114] In a third aspect, alone or in combination with one or more of the first and second aspects, the format for reporting the flight path information is indicated in a flight path information reporting configuration information element of the configuration message.

[0115] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the request is indicated using a flight path information request field of a UE information request message.

[0116] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the flight path information is sent in a flight path information report.

[0117] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the flight path information indicates at least one of the following: if the format is a waypoint format, the corresponding time at which the UE is expected to arrive at a waypoint in the set of waypoints indicated in the flight path information, or if the format is a polygon format, the corresponding time at which the UE is expected to occupy a polygon in the set of polygons indicated in the flight path information.

[0118] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the corresponding time that the UE is expected to occupy the polygon in the polygon set includes at least one of the following: the corresponding time that the UE is expected to enter the polygon, the corresponding time that the UE is expected to exit the polygon, the corresponding duration that the UE is expected to occupy the polygon, or a combination thereof.

[0119] Although Figure 6 An exemplary block diagram of method 600 is shown, but in some aspects, the Figure 6 The method 600 may include additional blocks, fewer blocks, different blocks, or blocks in a different arrangement than described in the method 600. Additionally or alternatively, two or more of the blocks of the method 600 may be performed in parallel.

[0120] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a network node (eg, Figure 1 Base station 110, Fig.11 1102, etc.) to execute.

[0121] At 710, a network node may send, to a UE, an indication of a format among a plurality of formats for reporting flight path information of the UE. For example, a network node may send, to a UE (e.g., using receive processor 238, controller / processor 240, memory 242, etc.), an indication of a format among a plurality of formats for reporting flight path information of the UE, as described above. In some aspects, the plurality of formats may include at least a waypoint format and a polygon format (also referred to as a "flight volume format"). In some aspects, the format may be a static format stored in a memory of the UE, and / or may be determined based at least in part on a format indicator and a UE identifier identifying the UE.

[0122] At 720, the network node may send a request for flight path information to the UE. For example, the network node may send a request for flight path information to the UE (e.g., using receive processor 238, controller / processor 240, memory 242, etc.), as described above. In some aspects, the request may include an indication of a format as described above in conjunction with reference numeral 710, or may be sent separately. In some aspects, the request may be indicated using a flight path information request field of a UE information request message.

[0123] At 730, the network node may receive flight path information from the UE according to a format. For example, the network node may receive flight path information from the UE (e.g., using receive processor 238, controller / processor 240, memory 242, etc.) according to a format and based at least in part on sending a request for flight path information, as described above. In some aspects, the flight path information may be received in a flight path information report. In some aspects, the flight path information may indicate at least one of: a corresponding time that the UE is expected to arrive at a waypoint in a set of waypoints indicated in the flight path information, if the format is a waypoint format; or a corresponding time that the UE is expected to occupy a polygon in the set of polygons indicated in the flight path information, if the format is a polygon format.

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

[0125] In a first aspect, the format is a static format stored in a memory of the UE.

[0126] In a second aspect, alone or in combination with the first aspect, the format is determined at least in part based on a format indicator and a UE identifier identifying the UE, wherein the format indicator and the UE identifier are received from a network device in a core network associated with the network node.

[0127] In a third aspect, alone or in combination with one or more of the first and second aspects, the format indicator and the UE identifier are received based at least in part on an authorization of a flight plan for the UE.

[0128] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the plurality of formats includes at least a waypoint format and a polygon format.

[0129] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the format for reporting the flight path information is indicated in at least one of a configuration message or a non-access stratum message.

[0130] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the format for reporting the flight path information is indicated in a flight path information report configuration information element of the configuration message.

[0131] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the request is indicated using a flight path information request field of a UE information request message.

[0132] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the flight path information is received in a flight path information report.

[0133] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, the flight path information indicates at least one of the following: if the format is a waypoint format, the corresponding time at which the UE is expected to arrive at a waypoint in the set of waypoints indicated in the flight path information, or if the format is a polygon format, the corresponding time at which the UE is expected to occupy a polygon in the set of polygons indicated in the flight path information.

[0134] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the corresponding time that the UE is expected to occupy the polygon in the polygon set includes at least one of the following: the corresponding time that the UE is expected to enter the polygon, the corresponding time that the UE is expected to exit the polygon, the corresponding duration that the UE is expected to occupy the polygon, or a combination thereof.

[0135] Although Figure 7 An exemplary block diagram of method 700 is shown, but in some aspects, the Figure 7The method 700 may include additional blocks, fewer blocks, different blocks, or blocks in a different arrangement than described in the method 700. Additionally or alternatively, two or more of the blocks of the method 700 may be performed in parallel.

[0136] Figure 8 8 is a flow chart of a method 800 for wireless communication. The method may be performed by a network device (e.g., Figure 1 Network equipment 130, Fig.13 1302, etc.) to execute.

[0137] At 810, the network device may receive information identifying a UE and a format in a plurality of formats for the UE to report flight path information. For example, the network device may receive (e.g., using receive processor 238, controller / processor 240, memory 242, etc.) information identifying a UE and a format in which the UE reports flight path information, as described above. In some aspects, the plurality of formats may include at least a waypoint format and a polygon format (also referred to as a "flight volume format"). In some aspects, the information identifying the UE and the format may be received from a USS device or from a core network device in communication with the USS device.

[0138] At 820, the network device may identify a base station serving the UE. For example, the network device may (e.g., using the receive processor 238, the controller / processor 240, the memory 242, etc.) identify the base station serving the UE, as described above. In some aspects, the network device may include an MME / AMF that serves the UE and identifies the base station serving the UE. Additionally or alternatively, the network device may include communicating with the MME / AMF that serves the UE to identify the NEF / SCEF of the base station serving the UE.

[0139] At 830, the network device may send a format indicator identifying the format and a UE identifier identifying the UE to the base station. For example, the network device may send the format indicator and the UE identifier identifying the UE to the base station (e.g., using the receive processor 238, the controller / processor 240, the memory 242, etc.), as described above. In some aspects, the UE identifier may be the same as the received information identifying the UE. Additionally or alternatively, the network device may determine the UE identifier based at least in part on the received information identifying the UE.

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

[0141] In a first aspect, the information identifying the UE and the format is received based at least in part on an authorization of a flight plan for the UE.

[0142] In a second aspect, alone or in combination with the first aspect, the format indicator and the UE identifier are sent to the base station based at least in part on an authorization of a flight plan for the UE.

[0143] In a third aspect, alone or in combination with one or more of the first and second aspects, the information identifying the UE and the format is received from a USS device or from a core network device in communication with the USS device.

[0144] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the information identifying the UE and the format is received from the USS device via a SCEF API or a NEF API.

[0145] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the information identifying the UE includes at least one of an unmanned aerial vehicle identifier, a public subscription identifier, or a combination thereof.

[0146] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the UE identifier comprises at least one of an unmanned aerial vehicle identifier, a public subscription identifier, or a combination thereof.

[0147] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the plurality of formats includes at least a waypoint format and a polygon format.

[0148] Although Figure 8 An exemplary block diagram of method 800 is shown, but in some aspects, the Figure 8 The method 800 may include additional blocks, fewer blocks, different blocks, or blocks in a different arrangement than described in the method 800. Additionally or alternatively, two or more of the blocks of the method 800 may be performed in parallel.

[0149] Fig. 9 900 is a conceptual data flow diagram illustrating the flow of data between different components in an example apparatus 902. The apparatus 902 may be a UE (eg, UE 120). In some aspects, the apparatus 902 includes a receiving component 904, a formatting component 906, and / or a transmitting component 908.

[0150] In some aspects, receiving component 904 may receive (e.g., from apparatus 950, such as a network node (e.g., a base station, MME / AMF, etc.) an indication of a format among a plurality of formats for reporting flight path information to a network node. Receiving component 904 may further receive (e.g., from apparatus 950, such as a network node (e.g., a base station, MME / AMF, etc.) a request for flight path information. In some aspects, receiving component 904 may receive the indication of the format as part of the request. Additionally or alternatively, receiving component 904 may receive the indication of the format as a message separate from the request.

[0151] In some aspects, formatting component 906 can determine a format in the indication received by receiving component 904. Formatting component 906 can further obtain the requested flight path information in the determined format. In some aspects, formatting component 906 can re-encode the flight path information if device 902 stores the flight path information in a format different than the determined format.

[0152] In some aspects, transmitting component 908 can transmit the flight path information to a network node (e.g., to apparatus 950, such as a network node (e.g., a base station, MME / AMF, etc.) according to a format. For example, transmitting component 908 can transmit a message with the flight path information obtained by formatting component 906. Based at least in part on receiving a request for flight path information by receiving component 904, transmitting component 908 can transmit the flight path information.

[0153] The apparatus may include means for performing Figure 6 Additional components of each box in the algorithm in the aforementioned method 600, etc. Figure 6 Each of the blocks in the aforementioned method 600, etc., may be performed by a component, and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to perform the stated processing / algorithms, these components may be implemented by a processor configured to perform the stated processing / algorithms, stored in a computer-readable medium so as to be implemented by a processor, or some combination thereof.

[0154] Fig. 9 The number and arrangement of components shown in FIG. are provided as examples. In practice, Fig. 9 There may be additional components, fewer components, different components, or differently arranged components than those shown in . Fig. 9 Two or more components shown in may be implemented in a single component, or Fig. 9 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig. 9A set of components (e.g., one or more components) shown in FIG. 1 may perform operations described as being performed by Fig. 9 One or more functions performed by another set of components shown in FIG.

[0155] Fig.10 1000 is a diagram illustrating an example of a hardware implementation for illustrating an apparatus 902' employing a processing system 1002. The apparatus 902' may be a UE (eg, UE 120).

[0156] The processing system 1002 may be implemented using a bus architecture, which is generally represented by bus 1004. Bus 1004 may include any number of interconnecting buses and bridges depending on the specific application and overall design constraints of the processing system 1002. Bus 1004 links together various circuits including one or more processors and / or hardware components (represented by processor 1006, components 904, 906, and / or 908), and computer readable media / memory 1008. Bus 1004 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and are not described in any further detail.

[0157] The processing system 1002 may be coupled to a transceiver 1010. The transceiver 1010 is coupled to one or more antennas 1012. The transceiver 1010 provides a means for communicating with various other devices over a transmission medium. The transceiver 1010 receives signals from the one or more antennas 1012, extracts information from the received signals, and provides the extracted information to the processing system 1002 (specifically, the receiving component 906). In addition, the transceiver 1010 receives information from the processing system 1002 (specifically, the transmitting component 908), and generates signals to be applied to the one or more antennas 1012 based at least in part on the received information. The processing system 1002 includes a processor 1006 coupled to a computer-readable medium / memory 1008. The processor 1006 is responsible for general processing, which includes executing software stored on the computer-readable medium / memory 1008. When the software is executed by the processor 1006, it causes the processing system 1002 to perform various functions described herein for any particular device. The computer-readable medium / memory 1008 may also be used to store data that is manipulated when the processor 1006 executes software. The processing system also includes at least one of components 904, 906, and / or 908. These components may be software components that run in the processor 1006, reside / stored in the computer-readable medium / memory 1008, one or more hardware modules coupled to the processor 1006, or some combination thereof. The processing system 1002 may be a component of the UE 120 and may include at least one of the memory 282 and / or the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280.

[0158] In some aspects, the apparatus 902 / 902' for wireless communication includes: means for receiving an indication of a format among a plurality of formats for reporting flight path information to a network node; means for receiving a request for flight path information; means for sending the flight path information to the network node according to the format and based at least in part on receiving the request for flight path information, and the like. The aforementioned means may be one or more of the aforementioned components of the processing system 1002 of the apparatus 902 and / or the apparatus 902' configured to perform the functions recited by these aforementioned means. As described elsewhere herein, the processing system 1002 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned means may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations recited herein.

[0159] Fig.10 Provided as an example. Other examples can be combined with Fig.10 The examples described are different.

[0160] Fig.11 1100 is a conceptual data flow diagram illustrating the flow of data between different components in an example apparatus 1102. The apparatus 1102 may be a network node (eg, a base station 110). In some aspects, the apparatus 1102 includes a receiving component 1104, a determining component 1106, and / or a transmitting component 1108.

[0161] In some aspects, determining component 1106 can determine a format among a plurality of formats for reporting flight path information. In some aspects, determining component 1106 can obtain a static format stored in a memory of the UE (e.g., using receiving component 1104 and / or transmitting component 1108), or can obtain a static format associated with apparatus 1102. Additionally or alternatively, determining component 1106 can determine the format based at least in part on the format indicator and a UE identifier identifying the UE. For example, the format indicator and the UE identifier can be received (e.g., using receiving component 1104) from a network device in a core network associated with apparatus 1102.

[0162] In some aspects, transmission component 1108 can send (e.g., to apparatus 1150, such as a UE) an indication of a format for reporting flight path information. For example, transmission component 1108 can use the format from determination component 1106. Transmission component 1108 can further send (e.g., to apparatus 1150, such as a UE) a request for flight path information. In some aspects, transmission component 1108 can include the indication of the format as part of the request. Additionally or alternatively, transmission component 1108 can transmit the indication of the format as a separate message from the request.

[0163] In some aspects, receiving component 1104 can receive the flight path information according to a format (eg, from device 1150 such as a UE).Based at least in part on transmitting component 1108 sending a request for flight path information, receiving component 1104 can receive the flight path information.

[0164] The apparatus may include means for performing Figure 7 Additional components of each box in the algorithm in the aforementioned method 700, etc. Figure 7 Each of the blocks in the aforementioned method 700, etc., may be executed by a component, and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to execute the stated processing / algorithms, these components may be implemented by a processor configured to execute the stated processing / algorithms, stored in a computer-readable medium so as to be implemented by a processor, or some combination thereof.

[0165] Fig.11The number and arrangement of components shown in FIG. are provided as examples. In practice, Fig.11 There may be additional components, fewer components, different components, or differently arranged components than those shown in . Fig.11 Two or more components shown in may be implemented in a single component, or Fig.11 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.11 A set of components (e.g., one or more components) shown in FIG. 1 may perform operations described as being performed by Fig.11 One or more functions performed by another set of components shown in FIG.

[0166] Fig.12 1200 is a diagram illustrating an example of a hardware implementation for illustrating an apparatus 1102' employing a processing system 1202. The apparatus 1102' may be a network node (eg, a base station 110).

[0167] The processing system 1202 may be implemented using a bus architecture, which is generally represented by bus 1204. The bus 1204 may include any number of interconnecting buses and bridges depending on the specific application and overall design constraints of the processing system 1202. The bus 1204 links together various circuits including one or more processors and / or hardware components (represented by processor 1206, components 1104, 1106, and / or 1108), and computer readable media / memory 1208. The bus 1204 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and are not described in any further detail.

[0168] The processing system 1202 may be coupled to a transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1212. The transceiver 1210 provides a means for communicating with various other devices over a transmission medium. The transceiver 1210 receives signals from the one or more antennas 1212, extracts information from the received signals, and provides the extracted information to the processing system 1202 (specifically, the receiving component 1104). In addition, the transceiver 1210 receives information from the processing system 1202 (specifically, the transmitting component 1108), and generates signals to be applied to the one or more antennas 1212 based at least in part on the received information. The processing system 1202 includes a processor 1206 coupled to a computer-readable medium / memory 1208. The processor 1206 is responsible for general processing, which includes executing software stored on the computer-readable medium / memory 1208. When the software is executed by the processor 1206, the processing system 1202 is caused to perform the various functions described herein for any particular apparatus. The computer-readable medium / memory 1208 may also be used to store data that is manipulated when the processor 1206 executes the software. The processing system also includes at least one of the components 1104, 1106, and / or 1108. These components may be software components running in the processor 1206, resident / stored in the computer-readable medium / memory 1208, one or more hardware modules coupled to the processor 1206, or some combination thereof. The processing system 1202 may be a component of the base station 110 and may include at least one of the memory 242 and / or the TX MIMO processor 230, the RX processor 238, and / or the controller / processor 240.

[0169] In some aspects, the apparatus 1102 / 1102' for wireless communication includes: means for sending an indication of a format of a plurality of formats for reporting flight path information of the UE to a UE; means for sending a request for flight path information to the UE; means for receiving flight path information from the UE according to the format and based at least in part on sending the request for flight path information, and the like. The aforementioned means may be one or more of the aforementioned components of the processing system 1202 of the apparatus 1102 and / or the apparatus 1102' configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1202 may include the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240. In one configuration, the aforementioned means may be the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240 configured to perform the functions and / or operations recited herein.

[0170] Fig.131300 is a conceptual data flow diagram illustrating the flow of data between different components in an example apparatus 1302. The apparatus 1302 can be a network device (e.g., network device 130). In some aspects, the apparatus 1302 includes a receiving component 1304, an identifying component 1306, and / or a transmitting component 1308.

[0171] In some aspects, receiving component 1304 may receive information identifying the UE and a format among a plurality of formats for reporting flight path information (e.g., from means 1350 such as a USS device, NEF / SCEF, etc.). In some aspects, receiving component 1304 may receive information identifying the UE and a format for reporting flight path information based at least in part on authorization of a flight plan for the UE (e.g., authorized by a USS device).

[0172] In some aspects, identifying component 1306 can identify a base station serving the UE. In some aspects, identifying component 1306 can obtain an indicator of the base station serving the UE from a memory or from an MME / AMF serving the UE (e.g., using receiving component 1304 and / or transmitting component 1308).

[0173] In some aspects, transmitting component 1308 can transmit a format indicator identifying a format and a UE identifier identifying the UE to the base station identified by identifying component 1306. In some aspects, the UE identifier can be the same as the information identifying the UE received by receiving component 1304. Additionally or alternatively, the UE identifier can be determined based at least in part on the information identifying the UE received by receiving component 1304.

[0174] The apparatus may include means for performing Figure 8 Another component of each box in the algorithm in the aforementioned method 800, etc. Figure 8 Each of the blocks in the aforementioned method 800, etc., may be performed by a component, and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to perform the stated processing / algorithms, these components may be implemented by a processor configured to perform the stated processing / algorithms, stored in a computer-readable medium so as to be implemented by a processor, or some combination thereof.

[0175] Fig.13 The number and arrangement of components shown in FIG. are provided as examples. In practice, Fig.13 There may be additional components, fewer components, different components, or differently arranged components than those shown in . Fig.13 Two or more components shown in may be implemented in a single component, or Fig.13The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.13 A set of components (e.g., one or more components) shown in FIG. 1 may perform operations described as being performed by Fig.13 One or more functions performed by another set of components shown in FIG.

[0176] Fig.14 1400 is a diagram illustrating an example of a hardware implementation for illustrating an apparatus 1302' employing a processing system 1402. The apparatus 1302' may be a network device (eg, network device 130).

[0177] The processing system 1402 may be implemented using a bus architecture, which is generally represented by bus 1404. Bus 1404 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1402. Bus 1404 links together various circuits including one or more processors and / or hardware components (represented by processor 1406, components 1304, 1306, and / or 1308), and computer readable media / memory 1408. Bus 1404 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and are not described in any further detail.

[0178] The processing system 1402 may be coupled to a communication unit 1410. The communication unit 1410 includes a unit for communicating with various other devices via a wired or wireless connection. The communication unit 1410 receives a signal, extracts information from the received signal, and provides the extracted information to the processing system 1402 (specifically, the receiving component 1304). In addition, the communication unit 1410 receives information from the processing system 1402 (specifically, the transmission component 1308), and generates a signal to be sent via a wired or wireless connection based at least in part on the received information. The processing system 1402 includes a processor 1406 coupled to a computer-readable medium / memory 1408. The processor 1406 is responsible for general processing, which includes executing software stored on the computer-readable medium / memory 1408. When the software is executed by the processor 1406, the processing system 1402 performs various functions described herein for any particular device. The computer-readable medium / memory 1408 can also be used to store data that is operated on when the processor 1406 executes the software. The processing system also includes at least one of components 1304, 1306, and / or 1308. These components may be software components running in processor 1406, resident / stored in computer-readable medium / memory 1408, one or more hardware modules coupled to processor 1406, or some combination thereof. Processing system 1402 may be a component of network device 130 and may include memory 292 and / or controller / processor 290.

[0179] In some aspects, the apparatus 1302 / 1302' for wireless communication includes: means for receiving information identifying a UE and a format among a plurality of formats for the UE to report flight path information; means for identifying a base station serving the UE; means for sending a format indicator identifying the format and a UE identifier identifying the UE to the base station, etc. The aforementioned means may be one or more of the aforementioned components of the processing system 1402 of the apparatus 1302 and / or the apparatus 1302' configured to perform the functions described by these aforementioned means. As described elsewhere herein, the processing system 1402 may include the controller / processor 290. In one configuration, the aforementioned means may be the controller / processor 290 configured to perform the functions and / or operations stated herein.

[0180] Fig.14 Provided as an example. Other examples can be combined with Fig.14 The examples described are different.

[0181] It should be understood that the specific order or block hierarchy in the process / flow chart disclosed herein is only an example of an exemplary method. It should be understood that the specific order or block hierarchy in these processes / flow charts can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of various blocks in an exemplary order, but do not mean that they are limited by the specific order or hierarchy provided.

[0182] A summary of some aspects of the disclosure is provided below.

[0183] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving an indication of a format among multiple formats for reporting flight path information to a network node; receiving a request for the flight path information; and sending the flight path information to the network node according to the format and at least partially based on receiving the request for the flight path information.

[0184] Aspect 2: The method according to aspect 1, wherein the multiple formats include at least a waypoint format and a polygon format.

[0185] Aspect 3: The method according to any one of aspects 1-2, wherein the format for reporting the flight path information is indicated in at least one of a configuration message or a non-access stratum message.

[0186] Aspect 4: The method according to aspect 3, wherein the format for reporting the flight path information is indicated in a flight path information reporting configuration information element of the configuration message.

[0187] Aspect 5: The method according to any one of aspects 1-4, wherein the request is indicated using a flight path information request field of a UE information request message.

[0188] Aspect 6: The method according to any one of Aspects 1-5, wherein the flight path information is sent in a flight path information report.

[0189] Aspect 7: A method according to Aspects 1-6, wherein the flight path information indicates at least one of the following: if the format is a waypoint format, the corresponding time at which the UE is expected to arrive at a waypoint in the set of waypoints indicated in the flight path information, or if the format is a polygon format, the corresponding time at which the UE is expected to occupy a polygon in the set of polygons indicated in the flight path information.

[0190] Aspect 8: A method according to Aspect 7, wherein the corresponding time that the UE is expected to occupy the polygon in the polygon set includes at least one of the following items: the corresponding time that the UE is expected to enter the polygon, the corresponding time that the UE is expected to exit the polygon, the corresponding duration that the UE is expected to occupy the polygon, or a combination thereof.

[0191] Aspect 9: A method of wireless communication performed by a network node, comprising: sending an indication of a format among multiple formats for reporting flight path information of the UE to a user equipment (UE); sending a request for the flight path information to the UE; and receiving the flight path information from the UE according to the format and at least partially based on sending the request for the flight path information.

[0192] Aspect 10: The method according to aspect 9, wherein the format is a static format stored in a memory of the UE.

[0193] Aspect 11: A method according to aspects 9-10, wherein the format is determined at least in part based on a format indicator and a UE identifier identifying the UE, wherein the format indicator and the UE identifier are received from a network device in a core network associated with the network node.

[0194] Aspect 12: The method of aspect 11, wherein the format indicator and the UE identifier are received based at least in part on an authorization of a flight plan for the UE.

[0195] Aspect 13: The method according to any one of aspects 9-12, wherein the multiple formats include at least a waypoint format and a polygon format.

[0196] Aspect 14: The method according to any one of aspects 9 to 13, wherein the format for reporting the flight path information is indicated in at least one of a configuration message or a non-access stratum message.

[0197] Aspect 15: The method according to Aspect 14, wherein the format for reporting the flight path information is indicated in a flight path information reporting configuration information element of the configuration message.

[0198] Aspect 16: The method according to any one of aspects 9-15, wherein the request is indicated using a flight path information request field of a UE information request message.

[0199] Aspect 17: A method according to any one of Aspects 9-16, wherein the flight path information is received in a flight path information report.

[0200] Aspect 18: A method according to any one of Aspects 9-17, wherein the flight path information indicates at least one of the following: if the format is a waypoint format, the corresponding time at which the UE is expected to arrive at a waypoint in the set of waypoints indicated in the flight path information, or if the format is a polygon format, the corresponding time at which the UE is expected to occupy a polygon in the set of polygons indicated in the flight path information.

[0201] Aspect 19: A method according to Aspect 18, wherein the corresponding time that the UE is expected to occupy the polygon in the polygon set includes at least one of the following items: the corresponding time that the UE is expected to enter the polygon, the corresponding time that the UE is expected to exit the polygon, the corresponding duration that the UE is expected to occupy the polygon, or a combination thereof.

[0202] Aspect 20. A method of wireless communication performed by a network device, comprising: receiving information identifying a user equipment (UE) and a format among multiple formats for the UE to report flight path information; identifying a base station serving the UE; and sending a format indicator identifying the format and a UE identifier identifying the UE to the base station.

[0203] Aspect 21: The method of aspect 20, wherein the information identifying the UE and the format is received based at least in part on an authorization of a flight plan for the UE.

[0204] Aspect 22: The method according to any one of aspects 20-21, wherein the format indicator and the UE identifier are sent to the base station based at least in part on an authorization of a flight plan for the UE.

[0205] Aspect 23: The method according to any one of aspects 20-22, wherein the information identifying the UE and the format is received from an unmanned aircraft system service provider (USS) device or from a core network device in communication with the USS device.

[0206] Aspect 24: The method according to aspect 23, wherein the information identifying the UE and the format is received from the USS device via a service capability exposure function (SCEF) application programming interface (API) or a network exposure function (NEF) API.

[0207] Aspect 25: The method according to any one of aspects 20-24, wherein the information identifying the UE includes at least one of an unmanned aerial vehicle identifier, a public subscription identifier, or a combination thereof.

[0208] Aspect 26: The method according to any one of Aspects 20-25, wherein the UE identifier includes at least one of an unmanned aerial vehicle identifier, a public subscription identifier, or a combination thereof.

[0209] Aspect 27: The method according to any one of Aspects 20-26, wherein the multiple formats include at least a waypoint format and a polygon format.

[0210] Aspect 28: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1-8.

[0211] Aspect 29: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more of aspects 1-8.

[0212] Aspect 30: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more of aspects 1-8.

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

[0214] Aspect 32: A non-transitory computer-readable medium storing an instruction set for wireless communication, wherein the instruction set includes one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of Aspects 1-8.

[0215] Aspect 33: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 9-19.

[0216] Aspect 34: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more of aspects 9-19.

[0217] Aspect 35: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more of aspects 9-19.

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

[0219] Aspect 37: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of Aspects 9-19.

[0220] Aspect 38: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 20-27.

[0221] Aspect 39: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more of aspects 20-27.

[0222] Aspect 40: An apparatus for wireless communication, comprising at least one means for performing the method according to one or more of aspects 20-27.

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

[0224] Aspect 42: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of aspects 20-27.

[0225] To enable any person of ordinary skill in the art to implement the various aspects described herein, the above description is made around various aspects. For a person of ordinary skill in the art, various modifications to these aspects are obvious, and the overall principle defined herein may also be applicable to other aspects. Therefore, the present invention is not limited to the aspects shown herein, but is consistent with the full scope of the present invention, wherein, unless otherwise specified, modifying a certain component in a singular form does not mean "one and only one", but may be "one or more". The word "exemplary" used herein means "used as an example, illustration or description". Any aspect described as "exemplary" herein should not be interpreted as being more preferred or more advantageous than other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B or C", "at least one of A, B and C", and "A, B, C or any combination thereof", including any combination of A, B and / or C, which may include multiple A, multiple B or multiple C. Specifically, combinations such as "at least one of A, B or C", "at least one of A, B and C", and "A, B, C or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members or some members of A, B or C. All structural and functional equivalents of the components of various aspects described throughout the present disclosure are expressly incorporated herein by reference and are intended to be covered by the claims, and these structural and functional equivalents are or will become known to those of ordinary skill in the art. In addition, no disclosure herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the claims. The constituent elements of the claims should not be interpreted as functional modules unless the constituent elements are explicitly recorded using the wording of "functional modules".

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: receiving an indication of a flight path format of a plurality of flight path formats configured for use in flight path information to be reported to a network node, wherein the plurality of flight path formats includes at least a waypoint flight path format and a volume flight path format indicating a plurality of polygonal sets that the UE is expected to occupy; receiving a request for the flight path information; and The flight path information is sent to the network node according to the flight path format and based at least in part on receiving the request for the flight path information.

2. The method according to claim 1, wherein: The flight path format for reporting the flight path information is indicated in at least one of a configuration message or a non-access stratum message.

3. The method according to claim 2, wherein: The flight path format for reporting the flight path information is indicated in a flight path information reporting configuration information element of the configuration message.

4. The method according to claim 1, wherein: The request is indicated using the Flight Path Information Request field of the UE Information Request message.

5. The method according to claim 1, wherein: The flight path information is sent in a flight path information report.

6. The method according to claim 1, wherein: The flight path information indicates at least one of the following: If the flight path format is a waypoint flight path format, the corresponding time at which the UE is expected to arrive at a waypoint in the set of waypoints indicated in the flight path information, or If the format is the volume flight path format, the UE is expected to occupy corresponding times of polygons in the plurality of polygon sets.

7. The method according to claim 6, wherein: The corresponding time that the UE is expected to occupy the polygon in the plurality of polygon sets includes at least one of the following: the corresponding time when the UE is expected to enter the polygon, the corresponding time at which the UE is expected to exit the polygon, the corresponding duration that the UE is expected to occupy the polygon, or Its combination.

8. The method according to claim 1, wherein: Receiving the indication of the flight path format is based at least in part on authorization of a flight plan for the UE.

9. A method of wireless communication performed by a network node, comprising: sending to a user equipment (UE) an indication of a flight path format from a plurality of flight path formats configured for flight path information to be reported to the network node, wherein the plurality of flight path formats includes at least a waypoint flight path format and a volume flight path format indicating a plurality of polygonal sets that the UE is expected to occupy; sending a request for the flight path information to the UE; and The flight path information is received from the UE according to the flight path format and based at least in part on sending the request for the flight path information.

10. The method according to claim 9, wherein: The flight path format is determined based at least in part on a format indicator and a UE identifier identifying the UE, wherein the format indicator and the UE identifier are received from a network device in a core network associated with the network node.

11. The method according to claim 10, wherein: The format indicator and the UE identifier are received based at least in part on an authorization of a flight plan for the UE.

12. The method according to claim 9, wherein: The flight path format for reporting the flight path information is indicated in at least one of a configuration message or a non-access stratum message.

13. The method according to claim 12, wherein: The flight path format for reporting the flight path information is indicated in a flight path information reporting configuration information element of the configuration message.

14. The method according to claim 9, wherein: The request is indicated using the Flight Path Information Request field of the UE Information Request message.

15. The method according to claim 9, wherein: The flight path information is received in a flight path information report.

16. The method according to claim 9, wherein: The flight path information indicates at least one of the following: If the flight path format is the waypoint flight path format, the corresponding time at which the UE is expected to arrive at a waypoint in the waypoint set indicated in the flight path information, or If the format is the volume flight path format, the UE is expected to occupy corresponding times of polygons in the plurality of polygon sets.

17. The method according to claim 16, wherein: The corresponding time that the UE is expected to occupy the polygon in the plurality of polygon sets includes at least one of the following: the corresponding time when the UE is expected to enter the polygon, the corresponding time at which the UE is expected to exit the polygon, the corresponding duration that the UE is expected to occupy the polygon, or Its combination.

18. A method of wireless communication performed by a network device, comprising: receiving information identifying a user equipment (UE) and a flight path format of a plurality of flight path formats configured for flight path information reported by the UE to a base station, wherein the plurality of flight path formats includes at least a waypoint flight path format and a volume flight path format indicating a plurality of polygonal sets that the UE is expected to occupy; and A format indicator identifying the flight path format and a UE identifier identifying the UE are sent to the base station.

19. The method according to claim 18, wherein: The information identifying the UE and the flight path format is received based at least in part on an authorization of a flight plan for the UE.

20. The method according to claim 18, wherein: The format indicator and the UE identifier are sent to the base station based at least in part on an authorization of a flight plan for the UE.

21. The method according to claim 18, wherein: The information identifying the UE and the flight path format is received from an unmanned aircraft system service provider (USS) device or from a core network device in communication with the USS device.

22. The method according to claim 21, wherein: The information identifying the UE and the flight path format is received from the USS device via a service capability exposure function (SCEF) application programming interface (API) or a network exposure function (NEF) API.

23. The method according to claim 18, wherein: The information identifying the UE includes at least one of an unmanned aerial vehicle identifier, a public subscription identifier, or a combination thereof.

24. The method according to claim 18, wherein: The UE identifier includes at least one of an unmanned aerial vehicle identifier, a public subscription identifier, or a combination thereof.

25. A user equipment (UE) for wireless communication, comprising: one or more memories; as well as One or more processors coupled to the one or more memories, configured alone or in any combination to: receiving an indication of a flight path format of a plurality of flight path formats configured for use in flight path information to be reported to a network node, wherein the plurality of flight path formats includes at least a waypoint flight path format and a volume flight path format indicating a plurality of polygonal sets that the UE is expected to occupy; receiving a request for the flight path information; as well as The flight path information is sent to the network node according to the flight path format and based at least in part on receiving the request for the flight path information.

26. The UE according to claim 25, wherein: The flight path information is sent in a flight path information report.

27. The UE according to claim 25, wherein: The flight path format for reporting the flight path information is indicated in at least one of a configuration message or a non-access stratum message.

28. The UE according to claim 27, wherein: The flight path format for reporting the flight path information is indicated in a flight path information reporting configuration information element of the configuration message.

29. The UE according to claim 25, wherein: The request is indicated using the Flight Path Information Request field of the UE Information Request message.

30. The UE according to claim 25, wherein: Receiving the indication of the flight path format is based at least in part on authorization of a flight plan for the UE.

Images