Design of routing management and configuration for autonomous UAV

Abstract

The present disclosure provides for management, canonical use of airspace and flight operations / configurations of UAVs. Within the scope of the present disclosure, route management, mode of operation, emergency override, and network control of UAV routing and operation are possible. An apparatus for wireless communication according to the present disclosure may include a memory and at least one processor coupled to the memory and configured to transmit unmanned aerial vehicle (UAV) data supporting uplink communication and downlink communication with a network entity, and receiving, from the network entity, a message including a UAV driving pattern, the UAV driving pattern indicating that the device flies on the planned route, the device being a UAV.

Description

Background Art Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems that enable route management and configuration of autonomous unmanned aerial vehicles (UAVs).

[0002] introduction

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

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

[0005] For example, some aspects of wireless communication include direct communication between devices, such as device-to-device (D2D), vehicle-to-everything (V2X), etc. There is a need to further improve such direct communication between devices. Improvements related to direct communication between devices may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents the summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] The present disclosure provides for the management and regulation of airspace and flight operations / configurations for unmanned aerial vehicles (UAVs). Route management, operating modes, emergency overrides, and network control of UAV routing and operations are possible within the scope of the present disclosure.

[0008] In various aspects of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). According to an aspect of the present disclosure, an apparatus for wireless communication includes: a memory and at least one processor, the at least one processor being coupled to the memory and configured to: send UAV data supporting uplink communication and downlink communication with a network entity, and receive a message including a UAV driving mode from the network entity, the UAV driving mode indicating that the apparatus is flying on a planned route, the apparatus being a UAV.

[0009] According to one aspect of the present disclosure, a method for wireless communication at a UE includes: sending UAV data supporting uplink communication and downlink communication with a network entity; and receiving a message including a UAV driving mode from the network entity, wherein the UAV driving mode indicates that the UE is flying on a planned route and the UE is a UAV.

[0010] According to one aspect of the present disclosure, a device for wireless communication includes: a component for sending UAV data supporting uplink communication and downlink communication with a network entity; and a component for receiving a message including a UAV driving mode from the network entity, wherein the UAV driving mode indicates that the device is flying on a planned route, and the device is a UAV.

[0011] A non-transitory computer-readable medium according to one aspect of the present disclosure stores computer executable code that, when executed by a processor, causes the processor to: send UAV data supporting uplink and downlink communications with a network entity, and receive a message from the network entity including a UAV driving mode, the UAV driving mode indicating that the device is flying on a planned route, the device being a UAV.

[0012] In various aspects of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a network entity. According to an aspect of the present disclosure, an apparatus for wireless communication includes: a memory and at least one processor, the at least one processor is coupled to the memory and configured to: receive UAV data supporting uplink communication and downlink communication with a UE, the UE being a UAV; and send a message including a UAV driving mode, the UAV driving mode indicating that the UE is flying on a planned route.

[0013] According to one aspect of the present disclosure, a method for wireless communication at a network entity includes: receiving UAV data supporting uplink communication and downlink communication with a UE, the UE being a UAV; and sending a message including a UAV driving mode, the UAV driving mode indicating that the UE is flying on a planned route.

[0014] According to one aspect of the present disclosure, an apparatus for wireless communication includes: a component for receiving UAV data supporting uplink communication and downlink communication with a UE, the UE being a UAV; and a component for sending a message including a UAV driving mode, the UAV driving mode indicating that the UE is flying on a planned route.

[0015] According to one aspect of the present disclosure, a non-transitory computer-readable medium stores computer-executable code that, when executed by a processor, causes the processor to: receive UAV data supporting uplink and downlink communications with a UE, the UE being a UAV; and send a message including a UAV driving mode that indicates that the UE is flying on a planned route.

[0016] To achieve the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0019] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

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

[0021] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

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

[0023] Figure 4is a block diagram illustrating an example decomposed base station architecture in accordance with various aspects of the present disclosure.

[0024] Figure 5 A flow chart illustrating network communications according to an aspect of the present disclosure is illustrated.

[0025] Figure 6 A flow chart illustrating network communications according to an aspect of the present disclosure is illustrated.

[0026] Figure 7 A flow chart illustrating network communications according to an aspect of the present disclosure is illustrated.

[0027] Fig. 8A Network routing planning according to one aspect of the present disclosure is illustrated.

[0028] Figure 8B Network routing planning according to one aspect of the present disclosure is illustrated.

[0029] Figure 8C Network routing planning according to one aspect of the present disclosure is illustrated.

[0030] Fig. 9 A flow chart illustrating network communications according to an aspect of the present disclosure is illustrated.

[0031] FIG. 10A to FIG. 10D is a flow chart of a method of wireless communication at a UE according to an aspect of the present disclosure.

[0032] FIG. 11A to FIG. 11D is a flow chart of a method of wireless communication at a network entity according to an aspect of the present disclosure.

[0033] Fig.12 is a diagram illustrating an example of a hardware implementation of an example apparatus.

[0034] Fig.13 is a diagram illustrating another example of a hardware implementation for another example apparatus. DETAILED DESCRIPTION

[0035] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0036] The present disclosure provides for the management, regulation of airspace and flight operations / configurations of UAVs. Route management, operating modes, emergency overrides, and network control of UAV routing and operations are possible within the scope of the present disclosure.

[0037] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These 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.

[0038] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic piece, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether it is referred to as software, firmware, middleware, microcode, hardware description language or other names, software should be widely interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc.

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

[0040] Figure 11 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0041] The base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, via the EPC 160 or the core network 190) via the third backhaul link 134 (eg, an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0042] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 can include an uplink (UL) (also called a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also called a forward link) transmission from base station 102 to UE 104. The communication link 120 can use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link can be through one or more carriers. For each carrier allocated in the carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 can use a spectrum of up to Y megahertz (MHz) (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

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

[0044] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, a 5 gigahertz (GHz) unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0045] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0046] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is typically (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0047] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this article, the term "below 6 GHz" or the like can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used in this article, it can broadly represent frequencies that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

[0048] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in the traditional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0049] Base station 180 may send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also send beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or different. The transmit direction and receive direction of UE 104 may be the same or different.

[0050] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, an MBMS gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service configuration and delivery. BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and may be responsible for session management (start / stop) and for collecting eMBMS related billing information.

[0051] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides quality of service (QoS) flow and session management. All user IP packets are delivered through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IMS, a packet switching (PS) streaming service, and / or other IP services.

[0052] Base stations may include and / or be referred to as gNBs, Node Bs, eNBs, access points, base transceivers, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmit receive points (TRPs), or some other suitable terminology. Base stations 102 provide access points to EPC 160 or core network 190 for UEs 104. Examples of UEs 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0053] Although the present disclosure may focus on 5G NR, the concepts and aspects described herein may be applicable to other similar areas such as LTE, Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), and / or other wireless / radio access technologies.

[0054] Furthermore, although the present disclosure may focus on UAV communications, the concepts and various aspects described herein may be applicable to other similar areas, such as vehicle-to-everything (V2X) communications, D2D communications, IoT communications, industrial IoT (IIoT) communications, and / or other standards / protocols for communications in wireless / access networks. Additionally or alternatively, the concepts and various aspects described herein may be particularly applicable to one or more specific areas, such as vehicle-to-pedestrian (V2P) communications, pedestrian-to-vehicle (P2V) communications, vehicle-to-infrastructure (V2I) communications, and / or other frameworks / models for communications in wireless / access networks.

[0055] Reference again Figure 1 In certain aspects, the UE 104 may be configured to send UAV data supporting uplink and downlink communications, and receive messages including a UAV driving mode indicating that the device is flying on a planned route, the device being a UAV as shown by the UAV component 198 .

[0056] Reference again Figure 1 In certain aspects, the base station 180 may be configured to: receive UAV data supporting uplink and downlink communications with a UE, the UE being a UAV; and send a message including a UAV driving mode indicating that the UE is flying on a planned route as indicated by the base station component 199.

[0057] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, it is assumed that the 5G NR frame structure is TDD, where subframe 4 is configured with slot format 28 (mainly DL), where D is DL, U is UL, and F is flexibly used between DL / UL, and subframe 3 is configured with slot format 34 (mainly UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mixture of DL, UL and flexible symbols. The slot format is configured for the UE by a received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0058] Other wireless communication technologies may have different frame structures and / or different channels. For example, a 10 millisecond (ms) frame may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbol on the DL may be a cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots in a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15 kilohertz (kHz), where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15 kHz, and the subcarrier spacing for parameter set μ=4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific set of parameters.

[0059] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0060] like Figure 2AAs illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration). x , where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0061] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The PDCCH within a BWP may be referred to as a control resource set (CORESET). Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the position of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH such as the system information block (SIB), and paging messages.

[0062] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0063] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) / negative acknowledgement (NACK) feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

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

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

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

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

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

[0069] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via corresponding transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0070] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

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

[0072] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the UAV component 198.

[0073] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Various aspects of base station component 198 related to 199.

[0074] Figure 4 4 is a block diagram illustrating an example decomposed base station 400 architecture. The decomposed base station 400 architecture may include one or more CUs 410, which may communicate directly with a core network 420 via a backhaul link, or indirectly with a core network 420 through one or more decomposed base station units (such as a near real-time (RT) RIC 425 via an E2 link, or a non-RT RIC 415 associated with a service management and orchestration (SMO) framework 405, or both). The CU 410 may communicate with one or more DUs 430 via corresponding midhaul links, such as an F1 interface. The DU 430 may communicate with one or more RUs 440 via corresponding fronthaul links. The RU 440 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 440.

[0075] Each of the units, namely, CU 410, DU 430, RU 440, and near-RT RIC 425, non-RT RIC 415, and SMO framework 405, may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. In addition, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.

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

[0077] DU 430 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 440. In some aspects, DU 430 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to functional partitioning such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 430 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 430 or with control functions hosted by CU 410.

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

[0079] The SMO framework 405 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 405 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 405 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 490) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 410, DU 430, RU 440, and near-RT RIC 425. In some specific implementations, the SMO framework 405 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 411, via the O1 interface. In addition, in some specific implementations, the SMO framework 405 may communicate directly with one or more RUs 440 via the O1 interface. The SMO framework 405 may also include a non-RT RIC 415 configured to support the functionality of the SMO framework 405 .

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

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

[0082] Unmanned aerial vehicles (UAVs), also known as unmanned autonomous aerial vehicles, have been used as base stations for emergency applications. UAVs have also been used as delivery vehicles to deliver items from warehouses or between buildings.

[0083] For example, UAVs have been flown at altitudes between 100 and 200 meters, covering areas ranging from about 6 square kilometers to over 100 square kilometers. Some of these UAVs are tethered so that the UAV can fly for extended periods of time and have fiber optic or other data connections to ground stations. The UAV mobile base station may also have a satellite link for other communication channels.

[0084] However, these UAV base stations are operated by a network provider (e.g., of network 100) rather than by the individual or entity using the network for flight operations. In one aspect of the present disclosure, a UAV operator may employ wireless network 100 for pre-flight preparation, in-flight operations, flight mission applications, flight path recommendations, flight monitoring and control, and / or other operations for UAV monitoring and control.

[0085] In one aspect of the present disclosure, automatic routing of UAVs for delivering cargo is possible. The UAVs can be piloted (fly) by the network 100, and the UAV (which can be a UE 104) routes can be planned by the network 100. The UAVs can be controlled to deliver cargo on the ground or high in the air to the upper floors of a building.

[0086] In one aspect of the present disclosure, UAVs may be used to deliver supplies, food, medicine, etc. during a lockdown for health reasons. The UAVs may be controlled by the network 100, by UAV autopilots, by UAV controllers, or by some combination of network / autopilots / controllers, as desired.

[0087] In one aspect of the present disclosure, UAV communication and UAV delivery may be combined. The network 100 may assist UAV autopilot and / or automatic routing for delivery services via 3GPP or other protocols. Routing and flight management of the UAV may be performed by edge computing of a base station (e.g., gNB) or access and mobility management function (e.g., AMF 192, 193) within the network 100. UAV route planning, delivery destination, delivery time, etc., and tracking during UAV travel may also be performed by the network 100.

[0088] In one aspect of the present disclosure, UAV route planning can support one or more UAV control modes. UAV (which may be referred to as UE 104 in this article) can signal the network 100 to notify the UAV mode support capability, for example, whether the UAV can support the network-controlled driving mode, the UAV autopilot mode, the handheld controller driving mode or the mixture of the above modes. Then, the network 100 can communicate UAV information, and the UAV information involves UAV routes, UAV operating modes (network-controlled modes, autopilot modes, controller driving modes or hybrid modes), departure time, routing information and / or other information about UAV delivery routes and timing. The operation of the network 100 can be completed by the base station 102, AMF 192 or 193, UPF 195 or UAV route management server (URM) (which may be other AMF 193 or UPF 195). URM can also be referred to as an unmanned aerial system traffic management server (UTM).

[0089] Information may be sent from and / or received at the UAV. Information that may originate from the UAV or an entity operating the UAV via IP services 176 and / or 197 may be delivery order information, UAV related information (licenses, capabilities, etc.). Information that may originate from network 100 may include management functions, configuration related information, obstacle information, route planning, speed through certain portions of the route, etc.

[0090] Figure 5A flow chart illustrating network communications according to an aspect of the present disclosure is illustrated.

[0091] Diagram 500 illustrates a UAV 502 transmitting UAV data 504 to a network entity 505 (which may be a server or application controlling the UAV, such as a URM server or a third-party server in communication with the network 100). The network entity 505 may, in turn, transmit the UAV data 504 or information associated with the UAV data 504 to a network entity 506 (which may be a base station 102 / 180). Alternatively, the UAV 502 may transmit the UAV data 504 directly to the network entity 506. The UAV data 504 may include a communication channel for the network 100 and / or the network entity 506 to communicate with the UAV 502, the UAV 502 capabilities, the driving modes supported by the UAV 502, the preferred driving mode of the UAV 502, or other UAV 502-specific information that provides support to the UAV for downlink and uplink communications with the network entity 506 (e.g., a unique identity (which may be a 3GPP identity), UE capabilities of the UAV, etc.).

[0092] The UAV 502 may send a message including the driving modes 507 it supports to the network entity 506. In this example, the message may be separate from the UAV data 504, although in other examples, the supported driving modes 507 may be part of the UAV data 504. The driving modes that the UAV 502 may support may include a network-controlled driving mode, a UAV autopilot mode, a handheld controller driving mode, a hybrid of the above modes, or a combination of any of the foregoing modes. The network entity 506 alone or in conjunction with one or more other parts of the network 100 (e.g., AMF 192, AMF 193, UPF 195, etc.) determines the driving mode of the UAV 502 from at least the supported driving modes 507, which may be referred to as the "determined mode" of the UAV 502 operation in box 508. The network entity 506 then sends the determined / determined UAV driving mode 510 message to the UAV 502. Then, in box 512, the UAV 502 can operate in the determined UAV driving mode 510.

[0093] As part of the UAV data 504 or the message including the supported driving modes 507, the user may provide a preferred driving mode 514 for the UAV 502. For example, but not by way of limitation, the UAV data 504 or the preferred driving mode 514 may include a preferred driving mode of UAV autopilot, controller driving, or network driving, or a mixed mode of driving the UAV 502 (e.g., one of the supported driving modes 507). This may be provided to the network entity 506 by the UAV 502 or by an application that communicates with the network entity 506, for example, via the IP services 176 and / or 197 (e.g., the network entity 505). In one aspect of the present disclosure, the UAV 502 may not report its supported driving modes 507 and preferred modes to the network entity 506. In this regard, the network entity 506 may provide the UAV 502 with a default operating mode of the UAV 502, such as a network controlled mode or a UAV autopilot mode.

[0094] As part of the UAV data 504, a message including supported driving modes 507 and / or preferred driving modes 514, or a different message, the UAV 502 may send other data, such as the departure time of the UAV 502, the departure three-dimensional (3D) position of the UAV 502, the destination 3D position of the UAV 502, the arrival time of the UAV 502, the flight capabilities of the UAV 502, the operator license of the UAV 502, the mission type of the UAV 502, the location of obstacles in the planned route of the UAV 502, the real-time 3D position of the UAV 502, the heading of the UAV 502, the speed of the UAV 502, the battery status of the UAV 502, and / or characteristics of the UAV 502.

[0095] As part of the mode determination block 508, the network entity 506 may use a priority determination strategy in which the operational priority of the UAV 502 may be changed based on the destination of the UAV 502, other UAV traffic, route geometry, QoS, or other factors. For example, if any of the aforementioned factors indicate that the network-controlled driving mode has a higher priority than the UAV-controlled driving mode, the network entity 506 may choose to provide the network-controlled driving mode to the UAV 502, or alternatively, if any of the aforementioned factors indicate that the UAV-controlled driving mode has a higher priority than the network-controlled driving mode, the network entity 506 may choose to provide the UAV-controlled driving mode to the UAV 502.

[0096] Figure 6 A flow chart illustrating network communications according to an aspect of the present disclosure is illustrated.

[0097] Diagram 600 illustrates a UAV 602 transmitting a routing request 604 to a network entity 606 (which may be a base station or a server or application controlling the UAV, such as a URM server or a third-party server in communication with the network 100). The routing request 604 may include the 3D position of the UAV 602, the departure time and destination of the UAV 602, the capabilities of the UAV 602 such as supported speeds, operating permissions, mission priorities, locations of obstacles (as measured by the UAV 602), the real-time 3D position of the UAV 602, heading, speed, battery status, a communication channel for the network 100 and / or the network entity 606 to communicate with the UAV 602, or other specific information of the UAV 602. Diagram 600 illustrates an aspect of the present disclosure in which the network entity 606 or other portion of the network 100 may determine that the UAV 602 is to be controlled by a network driving mode of operation.

[0098] In one aspect of the present disclosure, if the UAV 602 destination and timing (e.g., flight duration, destination delivery time, etc.) are indicated by the UAV 602 or UAV application (controller), the UAV 602 or UAV controller may transmit route information (e.g., in a route request 604) to a network entity 606, which may be a base station 102. Depending on the destination of the UAV 602, i.e., whether the destination is within the coverage of the base station 102 / network entity 606, the network entity 606 may have different behaviors and / or responses to the UAV 602, as shown by the route information 608. This route information 610 is then transmitted by the network entity 606 to the UAV 602, which then uses the route information 610 to operate the UAV 602 in block 612.

[0099] In one aspect of the present disclosure, the UAV 602 may provide the destination and timing information in the routing request 604. The network entity 606 may use the provided destination and timing information in determining routing information 608, which may also be provided to the UAV 602 as route information 610. Alternatively, if the UAV 602 destination and timing are provided to the network entity 606 (e.g., base station 102 / 180) from a different network entity (e.g., a URM server via an application on a server) rather than from the UAV 602 or a UAV controller, the network entity 606 may provide the route information 610 to the UAV 602 (which the UAV may download along with the route plan).

[0100] The route information 610 may also include other information about the route of the UAV 602. For example, but not by way of limitation, the route information 610 may include the route path, the location-dependent maximum allowed speed, the location-dependent maximum allowed altitude along the route, the expected departure time, the expected arrival time, the location of obstacles along the route collected by the network entity 606, and other information about the route that may be used by the UAV 602. In addition, the route information 610 may provide various levels of accuracy, for example, from meter level to street level, block level, or accuracy marked by a network entity (e.g., network entity level, such as anchor gNB level or cell level) to provide altitude information or 3D position information of the route to be followed by the UAV 602.

[0101] As part of the routing request 604, the UAV 602 may send other data, such as the departure time of the UAV 602, the departure three-dimensional (3D) position of the UAV 602, the destination 3D position of the UAV 602, the arrival time of the UAV 602, the flight capabilities of the UAV 602, the operator license of the UAV 602, the mission type of the UAV 602, the location of obstacles in the planned route of the UAV 602, the real-time 3D position of the UAV 602, the heading of the UAV 602, the speed of the UAV 602, the battery status of the UAV 602, and / or characteristics of the UAV 602.

[0102] Figure 7 A flow chart illustrating network communications according to an aspect of the present disclosure is illustrated.

[0103] Diagram 700 illustrates a UAV 702 transmitting UAV-determined autopilot route data 704 to a network entity 706 (which may be a base station or a server or application controlling the UAV, such as a URM server or a third-party server in communication with the network 100). The route data 704 may include a route calculated by the UAV 702 (or an application controlling the UAV 702), departure and destination locations and times, UAV operating permissions, mission priority, real-time UAV 3D position, heading, speed, battery status, and / or other route-specific and / or UAV-specific data (e.g., a reference position of the UAV). Diagram 700 illustrates an aspect of the present disclosure in which the UAV 702 may request a self-determined autopilot operating mode.

[0104] In block 708, the network entity 706 reviews the route data 704 and determines the appropriateness of the route data 704. The network entity 706 or another portion of the network 100 responds with an approval / rejection message 710 to the UAV 702. Then, in block 712, the UAV 702 acts on the received approval / rejection message 710.

[0105] If the approval / rejection message 710 is an approval of the UAV route data 704, the UAV 702 may then operate as described in the UAV autonomous driving route request. If the approval / rejection message 710 is a rejection of the UAV route data 704, the network entity 706 may indicate an alternative UAV 702 route, indicate that a network-controlled driving mode of the UAV 702 should be used, or request that the UAV 702 calculate new route data for transmission in another route data 704 message.

[0106] As part of the flowchart 700, the UAV 702 may transmit the driving data 714 to ensure that the UAV 702 is on the approved route transmitted to the UAV in the approval / rejection message 710 by periodically reporting the UAV 702 position to the network entity 706, through position indication or sensing by the network entity 706, via the UAV 702's visit to a particular base station 102 during flight, etc. For example, the UAV 702 periodically transmits the UAV's geographic location to the network entity 706 during transportation of the UAV on the planned route (e.g., via periodic 3D position reporting of the UAV 702 using, for example, GPS). In another example, the UAV 702 may transmit measurements of reference signals to the network entity 706 during transportation of the UAV on the planned route (e.g., via position indication, via CSI reports, or other measurement reports including measurements indicating the geographic location of the UAV). In another example, the UAV 702 may send a reference signal to the network entity during the UAV's transportation on the planned route (e.g., via reflections of the received reference signal, where the network entity 706 may determine the geographic location of the UAV by sensing the reflected reference signal). In another example, the UAV 702 may send cell information to the network entity during the UAV's transportation on the planned route (e.g., cell information such as a cell ID for accessing a specific base station, where the cell information may indicate the cell and therefore the geographic location of the UAV to the network entity 706). If the network entity determines that the UAV 702 is not on the approved route based on the geographic location information, the network entity 706 may transmit a correction message 716 to the UAV 702 (and / or to a UAV controller and / or to a different network entity such as a URM server), which may redirect the UAV 702 to the correct route, redirect the UAV to an alternative route, command the UAV 702 to return to the departure point, or provide other instructions.

[0107] As part of the route data 704, or as part of the driving data 714, the UAV 702 may send other data, such as the departure time of the UAV 702, the departure three-dimensional (3D) position of the UAV 702, the destination 3D position of the UAV 702, the arrival time of the UAV 702, the flight capabilities of the UAV 702, the operator license of the UAV 702, the mission type of the UAV 702, the location of obstacles in the planned route of the UAV 702, the real-time 3D position of the UAV 702, the heading of the UAV 702, the speed of the UAV 702, the battery status of the UAV 702, and / or characteristics of the UAV 702.

[0108] Fig. 8A Network routing planning according to an aspect of the present disclosure is illustrated. Diagram 801 illustrates an aspect of the present disclosure, where a UAV 800 is to be controlled by a network driving mode of operation.

[0109] In one aspect of the present disclosure, network 100 or portions of network 100 may plan a route for UAV 800. Base station 802, which may be similar to base station 102, may have a service area 804 or cell. If a departure point 806 and a destination 808 of UAV 800 are within the service area 804 of base station 802, base station 802 may perform route planning for route 810 of UAV 800 (e.g., as previously described with respect to FIG. 1 ). Figures 5 to 7 In combination with the network controlled driving mode described).

[0110] Figure 8B Network routing planning according to an aspect of the present disclosure is illustrated. Diagram 803 illustrates an aspect of the present disclosure, where the UAV 800 is to be controlled by a network driving mode of operation.

[0111] The route that UAV 800 may travel between departure point 806 and destination 808 may be in different service areas or cells. For example, but not by way of limitation, there may be multiple base stations along the route of UAV 800, such as base station 802 having service area 804, base station 812 having service area 814, and base station 816 having service area 818. If departure point 806 and destination 808 are in different service areas, and / or traverse multiple service areas, each base station may calculate a portion of the overall route of UAV 800, or an anchor base station in a pool of base stations including base stations 802, 812, 816 may calculate the overall route.

[0112] For example, but not by way of limitation, base station 802 having service area 804 may calculate portion 820 of the overall route, base station 812 having service area 814 may calculate portion 822 of the overall route, and base station 816 having service area 818 may calculate portion 824 of the overall route for UAV 800 between departure point 806 and destination 808. These base stations may perform route planning for their respective route portions or segments, such as described previously with respect to FIG. Figures 5 to 7 Incorporating network-controlled driving modes as described.

[0113] Figure 8C Network routing planning according to an aspect of the present disclosure is illustrated. Diagram 805 illustrates an aspect of the present disclosure in which the UAV 800 is to be controlled by a network driving mode of operation.

[0114] In one aspect of the present disclosure, a network entity 826 (which may be, for example, an AMF 192, 193, a URM server, or a multi-access edge cloud (MEC)) other than the base station 802 (and / or base stations 812, 816) may provide route calculation for the UAV 800, regardless of whether the departure point 806 and the destination 808 are in the same service area 804. In one aspect, the network entity 826 may perform route planning if its application provides the UAV destination and timing to the base stations 802, 812, 816. In another aspect, even though the destination 808 and / or the UAV route timing may be indicated by the UAV 800 or the UAV controller (rather than by the network entity 826), the route 810 decision and planning remains under the control of the network entity 826.

[0115] Fig. 9 A flow chart illustrating network communications according to an aspect of the present disclosure is illustrated.

[0116] In one aspect of the present disclosure, diagram 900 illustrates a UAV 902 transmitting UAV-determined autopilot route data 904 to a network entity 906 (which may be a base station or a server or application controlling the UAV, such as a URM server or a third-party server in communication with the network 100). For example, the UAV 902 may provide the route data 904 to the network entity 906 (e.g., the base station 102 / 180) in an RRC message or configuration. The route data 904 may include a route calculated by the UAV 902 (or by an application controlling the UAV 902), departure and destination locations and times, UAV operating permissions, mission priority, real-time UAV 3D position, heading, speed, battery status, and / or other route-specific and / or UAV-specific data. Diagram 900 illustrates an aspect of the present disclosure in which the UAV 902 may request a self-determined autopilot operating mode, similar to Figure 7 .

[0117] As part of the UAV-computed route data 904, the UAV 902 may compute a route plan and propose the route plan to the network entity 906. The UAV-computed data 904 may be transmitted from the UAV 902 to the network entity 906 via an RRC message or configuration. Alternatively, the UAV 902 may transmit the UAV-computed data 904 directly to the AMF server 910 and / or another portion of the network 100 via non-access stratum (NAS) signaling.

[0118] For example, here, with Figure 7 Unlike the example of , here the network entity 906 may not be able to determine whether to approve or deny the requested route of the UAV indicated in the route data 904. For example, this situation may be as follows Figure 8B As shown, where the departure point 806 and the destination 808 are in different cells, in which case the base station 802 may not be able to approve / reject the portions 822, 824 of the UAV's route, or this situation may be as follows Figure 8C As shown, a network entity 826 other than the base station 802 performs route calculation for the UAV 800. In this case, the network entity 906 may forward the route data 904 calculated by the UAV to the AMF server 910 (or another network entity) via a request 908 for approval or rejection. Alternatively, instead of the UAV 902 transmitting the route data 904 to the network entity 906 via RRC as in this example, in another example, the UAV 902 may transmit the route data 904 directly to the AMF server 910 (or other network entity in the EPC 160 or the core network 190) via NAS signaling. The AMF server 910 may be AMF 192, 193 or other server coupled to the network entity 906 via the network 100 or the IP service 176 and / or the IP service 197. Similar to Figure 7 In the example of FIG. 7 , the AMF server 910 may review the route data 904 in block 912 and determine the appropriateness of the route data 904. The AMF server 910 may then transmit an approval / rejection message 914 to the network entity 906.

[0119] In response to receiving the approval / rejection message 914 from the AMF server 910 (or other network entity), the network entity 906 or another portion of the network 100 may then transmit an approval / rejection message 916 to the UAV 902. The approval / rejection message 916 may be the same as the approval / rejection message 914 (i.e., the network entity 906 may effectively relay the approval / rejection message 914 to the UAV 902). This example may apply to a case where the UAV 902 transmits the route data 904 to the network entity 906 via RRC signaling. In another example where the UAV 902 transmits the route data 904 to the AMF server 910 (or other network entity) via NAS signaling, the AMF server 910 (or other network entity) may transmit the approval / rejection message 916 directly to the UAV 902. In either case (RRC or NAS), the UAV 902 then acts on the received approval / rejection message 916 in block 918.

[0120] As part of the UAV calculated data 904, the UAV 902 may calculate a route plan and propose the route plan to the network entity 906. The UAV calculated data 904 may be transmitted from the UAV 902 to the network entity 906 via an RRC message or configuration. Alternatively, the UAV 902 may transmit the UAV calculated data 904 directly to the AMF server 910 and / or another portion of the network 100 via NAS signaling.

[0121] As UAV 902 flies, network entity 906 or AMF server 910 (or other network entity) may update or reconfigure UAV calculated route data 904 to ensure that UAV 902 remains under control of network entity 906 and / or network 100. This process may be similar to that described with respect to Figure 7 The process described (e.g., if the network entity 906 or AMF server 910 determines through periodic UAV position reporting, position indication or sensing or base station cell information indication that the UAV 902 deviates from its approved route, the UAV 902 reconfigures its route and / or switches its mode to a network-controlled driving mode).

[0122] For example, as part of the flowchart 900, the UAV 902 may transmit driving data 920 by periodically reporting the UAV 902 location to the network entity 906, through location sensing by the network entity 906, via the UAV 902's access to particular base stations 102 during flight, etc., to ensure that the UAV 902 is on an approved route transmitted to the UAV in an approval / rejection message 916. If the UAV 902 is not on the approved route, the network entity 906 may transmit a correction message 922 to the UAV 902 (and / or a UAV control server), which may redirect the UAV 902 to the correct route, an alternative route, return the UAV 902 to a starting point, or other instructions.

[0123] If the UAV 902 is operating in a controller routing mode (UAV controller driving mode), which can be implemented by a handheld controller 926 of a given UAV 902, the UAV 902 can be triggered to switch to a network controlled driving mode or a UAV autopilot mode based on one of various conditions, and thus provide route data 904 to the network entity 906 or the AMF server 910 (or other network entity). In one example, the UAV 902 can sense that a command and control (C2) link 924 between the UAV 902 and the controller 926 has been lost for a period of time (a first condition) or that the C2 link has become weak (a second condition). For example, but not by way of limitation, a change in a characteristic of the C2 link can be sensed by the UAV 902. Such a change in characteristic can be a connection loss of the C2 link 924 for a threshold period of time (a first condition), a reference signal received power (RSRP) of a reference signal carried in the C2 link 924 being lower than a threshold (a second condition), or other changed characteristics of the C2 link 924. In another example, the controller 926 may request to change the operating mode of the UAV 902 (third condition) via the UAV 902 or other connection to the network entity 906. For example, the controller 926 (which may itself be a UE) may transmit a request to the network entity 906 or to the AMF server 910 (or other network entity) to switch the UAV 902 to a network-controlled driving mode or a UAV autonomous driving mode (third condition).

[0124] In one aspect of the present disclosure, the UAV 902 and / or the controller 926 may trigger an operational mode change of the UAV 902 from a controller 926 mode to a network driving mode and / or a UAV autonomous driving mode. The operational mode change may be triggered by the UAV 902, the controller 926, or the network entity 906, which may be based on the UAV 902 reporting to the network entity 906 that the C2 link 924 is lost. For example, the UAV 902 or the UAV controller 926 may trigger a mode switch from a handheld controller driving mode to a network controlled driving mode or a UAV autonomous control driving mode based on any of the aforementioned conditions (e.g., the first condition, the second condition, or the third condition). In another example, the UAV 902 may provide a measurement report of the C2 link 924 to the network entity 906, and if the measurement report indicates that the C2 link is lost or sufficiently impaired (e.g., the first condition or the second condition), the network entity 906 may trigger the mode switch itself, such as previously described with respect to Figure 5 For example, the network entity 906 (e.g., the network entity 506) can determine the mode at box 508 and transmit the UAV driving mode 510 to the UAV 502 at box 512 for operation.

[0125] In one aspect of the present disclosure, when a switch in operating mode is triggered by the UAV 902 or the controller 926, the UAV 902 or the UAV controller 926 may transmit a request to the network entity 906 for route data 904 or other data calculated by the UAV. The UAV 902 and / or the controller 926 may then wait within a specific time window for an approval / rejection message 916 (or other message) that provides the UAV 902 with new routing information for network-controlled driving or autopilot information approving the UAV 902 for UAV auto-controlled driving. Such a request may include a reason or condition for the request (e.g., a first condition, a second condition, or a third condition), and may optionally also include a preferred operating mode of the UAV 902 (e.g., Figure 5 The network entity 906 may be configured to determine the preferred driving mode 514 of the UAV 902. Figure 5 The UAV driving mode 510), routing configuration and / or other data is responded to as part of the approval / rejection 916 message (or other message).

[0126] As part of the UAV calculated data 904, or as part of the driving data 920, the UAV 902's departure time, the UAV 902's departure three-dimensional (3D) position, the UAV 902's destination 3D position, the UAV 902's arrival time, the UAV 902's flight capabilities, the UAV 902's operator license, the UAV 902's mission type, the location of obstacles in the UAV 902's planned route, the UAV 902's real-time 3D position, the UAV 902's heading, the UAV 902's speed, the UAV 902's battery status, and the UAV 902's characteristics.

[0127] FIG. 10A to FIG. 10D 1000 is a flow chart of a method of wireless communication according to an aspect of the present disclosure. The method may be performed by a UE (eg, UE 104, 350; UAV 502, 602, 702, 800, 902, device 1202). Optional aspects are illustrated in dashed lines.

[0128] refer to Fig. 10A In 1002, the UE sends unmanned aerial vehicle (UAV) data supporting uplink communication and downlink communication with a network entity. For example, 1002 can be performed by the sending component 1234.

[0129] At 1004, the UE receives a message from a network entity including a UAV driving mode, the UAV driving mode indicating that the UE is flying on a planned route, the UE being a UAV. For example, 1004 can be performed by the UAV data component 1240.

[0130] At 1006, the UE may perform additional procedures. These procedures refer to FIG. 10B to FIG. 10D Give a description.

[0131] refer to Fig. 10B For example, at 1008, the UE may send a second message indicating at least one driving mode supported by the UAV to the network entity, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV. In this regard, 1008 may be performed by the sending component 1234.

[0132] At 1010, as another example, the UE may send route information to the network entity based on the UAV driving mode being a network-controlled driving mode, the route information including one or more of the following: UAV location, departure time of the UAV, departure location of the UAV, destination location of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) location, UAV heading, UAV speed, UAV battery status, and UAV characteristics. In this regard, 1010 may be performed by a sending component 1234.

[0133] At 1012, as another example, the UE may receive route information from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information further being received based on a destination location of the UAV or an expected departure time of the UAV from an application server in communication with the network entity. In this regard, 1012 may be performed by the UAV data component 1240.

[0134] Additionally, at 1012, as another example, the UE may receive route information from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information including one or more of the following: a routing path of the UAV, a position-dependent allowed speed of the UAV, a position-dependent altitude of the UAV, an expected departure time of the UAV, an expected arrival time of the UAV, and a location of obstacles in the planned route of the UAV. In this regard, 1012 may be performed by the UAV data component 1240.

[0135] At 1014, as another example, the UE may send the UAV calculated route information to the network entity based on the UAV driving mode being the UAV autonomous driving mode, and the UE may receive an indication of approval or rejection of the planned route associated with the UAV calculated route information from the network entity at 1016. In this regard, 1014 and 1016 may be performed by the sending component 1234 and the UAV data component 1240, respectively.

[0136] At 1018, as another example, the UE can receive route information from a network entity based on the UAV driving mode being switched to a network-controlled driving mode based on the refusal. In this regard, 1018 can be performed by the UAV data component 1240.

[0137] At 1020 , as another example, the UE can periodically send the geographic location of the UAV to the network entity during the transportation of the UAV on the planned route. In this regard, 1020 can be performed by the sending component 1234 .

[0138] At 1022 , as another example, the UE can send measurements of a reference signal to a network entity during transportation of the UAV on the planned route, the measurements indicating the geographic location of the UAV. In this regard, 1022 can be performed by a sending component 1234 .

[0139] At 1024 , as another example, the UE can send a reference signal to a network entity during transportation of the UAV on the planned route, the reference signal indicating the geographic location of the UAV. In this regard, 1024 can be performed by the sending component 1234 .

[0140] At 1026 , as another example, the UE can send cell information to the network entity during the transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV. In this regard, 1026 can be performed by the sending component 1234 .

[0141] refer to Fig. 10C As another example, at 1027, the UE may receive a second message instructing the UAV to follow the planned route or return to the departure location of the UAV based on the geographic location of the UAV indicating that the UAV is not on the planned route. In this regard, 1027 may be performed by the UAV data component 1240.

[0142] At 1028, as another example, the UE may receive route information from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating the entirety of the planned route based on the UAV's destination location being within a cell of the network entity. In this regard, 1028 may be performed by the UAV data component 1240.

[0143] At 1030, as another example, the UE may receive route information from a network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of a planned route based on the UAV's destination location being within a cell of a different network entity. In this regard, 1030 may be performed by the UAV data component 1240.

[0144] At 1032 , as another example, the UE can receive calculated route information originating from a different network entity from the network entity based on the UAV driving mode being a network-controlled driving mode. In this regard, 1032 can be performed by the UAV data component 1240 .

[0145] At 1034, as another example, the UE may send the UAV calculated route information to the network entity in a radio resource control (RRC) message based on the UAV driving mode being the UAV automatic driving mode; and at 1036, the UE may receive from the network entity an indication of approval or rejection of a planned route originating from the network entity or a different network entity, the planned route being associated with the UAV calculated route information. In this regard, 1034 and 1036 may be performed by a sending component 1234 and a UAV data component 1240, respectively.

[0146] refer to Fig. 10D At 1037, as another example, the UE may send the route information calculated by the UAV to different network entities in a non-access stratum (NAS) message based on whether the UAV driving mode is a UAV autonomous driving mode; and at 1038, the UE may receive an indication of approval or rejection of the planned route associated with the route information calculated by the UAV from different network entities. In this regard, 1037 and 1038 may be performed by the sending component 1234 and the UAV data component 1240, respectively.

[0147] At 1040, as another example, the UE may send the UAV calculated route information in a radio resource control (RRC) message or a non-access stratum (NAS) message based on the UAV driving mode being the UAV autopilot mode, at 1042, the UE may receive an indication of a rejection of the planned route associated with the UAV calculated route information, and at 1044, the UE may receive the route information of the UAV autopilot mode or the network controlled driving mode based on the rejection. In this regard, 1040 may be performed by the sending component 1234, and 1042 and 1044 may be performed by the UAV data component 1240.

[0148] At 1046, as another example, the UE may send a request to the network entity to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode based on a change in the characteristics of a command and control (C2) link between the UAV and the UAV controller; and at 1048, the UE may receive a different UAV driving mode from the network entity in response to the request, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode. In this regard, 1046 and 1048 may be performed by the sending component 1234 and the UAV data component 1240, respectively.

[0149] At 1050, as another example, the UE may receive a different UAV driving mode from the network entity in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode. In this regard, 1050 may be performed by the UAV data component 1240.

[0150] At 1052, as another example, the UE may send a report indicating measurements associated with a command and control (C2) link between the UAV and the UAV controller, and the UE may receive a different UAV driving mode from the network entity in response to the report at 1054. In this regard, 1052 and 1054 may be performed by the transmission component 1234 and the UAV data component 1240, respectively.

[0151] FIG. 11A to FIG. 11D 1100 is a flow chart of a method of wireless communication. The method may be performed by a network entity (e.g., base station 102 / 180, 310; network entity 506, 606, 706, 802, 812, 816, 906, device 1302). Optional aspects are illustrated by dashed lines. Although the following description specifically refers to a base station as a network entity, it should be understood that a network entity different from a base station (e.g., AMF, URM server, MEC server, etc.) may perform one or more of the following steps.

[0152] At 1102, a base station receives unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a UE, the UE being a UAV. For example, 1102 can be performed by the UAV data component 1340.

[0153] At 1104 , the base station sends a message including a UAV driving mode indicating that the UE is flying on the planned route. For example, 1104 can be performed by the sending component 1334 .

[0154] At 1106, the base station may perform additional processes. These processes refer to FIG. 11B to FIG. 11D Give a description.

[0155] refer to Fig. 11B At 1108, for example, the base station may receive a second message indicating to the network entity at least one driving mode supported by the UAV, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV. In this regard, 1108 may be performed by the UAV data component 1340.

[0156] At 1110, as another example, the base station may receive route information based on the UAV driving mode being a network-controlled driving mode, the route information including one or more of the following: UAV location, departure time of the UAV, departure location of the UAV, destination location of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) location, UAV heading, UAV speed, UAV battery status, and UAV characteristics. In this regard, 1110 may be performed by the UAV data component 1340.

[0157] At 1112, as another example, the base station can send route information based on the UAV driving mode being a network-controlled driving mode, the route information further being sent based on the destination location of the UAV or the expected departure time of the UAV from an application server in communication with the network entity. In this regard, 1112 can be performed by a sending component 1334.

[0158] At 1112, as another example, the base station can send route information based on the UAV driving mode being the network-controlled driving mode, the route information including one or more of the following: a routing path of the UAV, a position-dependent allowed speed of the UAV, a position-dependent altitude of the UAV, an expected departure time of the UAV, an expected arrival time of the UAV, and a location of obstacles in the planned route of the UAV. In this regard, 1106 can be performed by the sending component 1334.

[0159] At 1114, as another example, the base station can receive the route information calculated by the UAV based on the UAV driving mode being the UAV autopilot mode, and at 1116, the base station can send an indication of approval or rejection of the planned route associated with the route information calculated by the UAV. In this regard, 1114 and 1116 can be performed by the UAV data component 1340 and the sending component 1334, respectively.

[0160] At 1118, as another example, the base station can send route information based on the UAV driving mode based on the refusal to be switched to a network-controlled driving mode. In this regard, 1118 can be performed by a sending component 1334.

[0161] At 1120 , as another example, the base station can periodically receive the geographic location of the UAV during the transportation of the UAV on the planned route. In this regard, 1120 can be performed by the UAV data component 1340 .

[0162] At 1122 , as another example, the base station can receive measurements of a reference signal during the UAV's transit on the planned route, the measurements indicating the geographic location of the UAV. In this regard, 1122 can be performed by the UAV data component 1340 .

[0163] At 1124, as another example, the base station can receive a reference signal during the UAV's transit on the planned route, the reference signal indicating the geographic location of the UAV. In this regard, 1124 can be performed by the UAV data component 1340.

[0164] At 1126 , as another example, the base station can receive cell information during the UAV's transit on the planned route, the cell information indicating the geographic location of the UAV. In this regard, 1126 can be performed by the UAV data component 1340 .

[0165] refer to Fig. 11C At 1127, as another example, based on the geographic location of the UAV indicating that the UAV is not on the planned route, the base station can send a second message instructing the UAV to follow the planned route or return to the departure location of the UAV. In this regard, 1127 can be performed by the sending component 1334.

[0166] At 1128, as another example, the base station can send route information based on the UAV driving mode being a network-controlled driving mode, the route information indicating the entirety of the planned route based on the UAV's destination location being within the cell of the network entity. In this regard, 1128 can be performed by a sending component 1334.

[0167] At 1130, as another example, the base station can send route information based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of the planned route based on the UAV's destination location being within a cell of a different network entity. In this regard, 1130 can be performed by a sending component 1334.

[0168] At 1132 , as another example, the base station can transmit the calculated route information originating from different network entities based on the UAV driving mode being a network-controlled driving mode. In this regard, 1132 can be performed by a transmitting component 1334 .

[0169] At 1134, as another example, the base station can receive the route information calculated by the UAV in a radio resource control (RRC) message based on the UAV driving mode being the UAV autopilot mode, and at 1136, the base station can send an indication of approval or rejection of a planned route originating from a different network entity, the planned route being associated with the route information calculated by the UAV. In this regard, 1134 and 1136 can be performed by the UAV data component 1340 and the sending component 1334, respectively.

[0170] refer to Fig.11D At 1138, as another example, the base station may receive the route information calculated by the UAV in a radio resource control (RRC) message based on the UAV driving mode being the UAV autopilot mode, at 1140, the base station may send an indication of a rejection of the planned route associated with the UAV calculated route information, and at 1142, the base station may send the route information of the UAV autopilot mode or the network controlled driving mode based on the rejection. In this regard, 1138, 1140, and 1142 may be performed by the UAV data component 1340 and the sending component 1334, respectively.

[0171] At 1144, as another example, the base station may receive a request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode based on a change in a characteristic of a command and control (C2) link between the UAV and the UAV controller, and at 1146, the base station may send a different UAV driving mode in response to the request, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode. In this regard, 1144 and 1146 may be performed by the UAV data component 1340 and the sending component 1334, respectively.

[0172] At 1148, as another example, the base station can send a different UAV driving mode in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode. In this regard, 1148 can be performed by the sending component 1334.

[0173] At 1150, as another example, the base station can receive a report indicating measurements associated with a command and control (C2) link between the UAV and the UAV controller, and the base station can transmit a different UAV driving mode in response to the report at 1152. In this regard, 1150 and 1152 can be performed by the UAV data component 1340 and the transmission component 1334, respectively.

[0174] Fig.121 is a diagram 1200 illustrating an example of a hardware implementation for an apparatus 1202. The apparatus 1202 is a UE and includes a cellular baseband processor 1204 (also referred to as a modem) coupled to a cellular RF transceiver 1222 and one or more subscriber identity modules (SIM) cards 1220, an application processor 1206 coupled to a secure digital (SD) card 1208 and a screen 1210, a Bluetooth module 1212, a wireless local area network (WLAN) module 1214, a global positioning system (GPS) module 1216, and a power supply 1218. The cellular baseband processor 1204 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 1222. The cellular baseband processor 1204 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1204 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1204, causes the cellular baseband processor 1204 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1204 when executing the software. The cellular baseband processor 1204 also includes a receiving component 1230, a communication manager 1232, and a transmitting component 1234. The communication manager 1232 includes one or more illustrated components. The components within the communication manager 1232 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1204. The cellular baseband processor 1204 may be a component of the UE 350 and may include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1202 may be a modem chip and include only the baseband processor 1204, and in another configuration, the device 1202 may be the entire UE (e.g., see Figure 3 350), and includes the aforementioned additional modules of device 1202.

[0175] The communication manager 1232 includes a UAV data component 1240 that is configured to receive a message including a UAV driving mode that indicates that the UE is flying on a planned route, the UE being a UAV, for example, as described in conjunction with 1004.

[0176] The sending component 1234 can send a second message indicating to the network entity a driving mode supported by at least one UAV, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV, as described with respect to 1008.

[0177] The sending component 1234 can send route information to the network entity based on the UAV driving mode being a network-controlled driving mode, and the route information includes one or more of the following items: UAV position, UAV departure time, UAV departure position, UAV destination position, UAV arrival time, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics, as described with respect to 1010.

[0178] The UAV data component 1240 can receive route information from the network entity based on the UAV driving mode being a network-controlled driving mode, and the route information is further received based on the destination location of the UAV or the expected departure time of the UAV from an application server that communicates with the network entity, as described with respect to 1012.

[0179] The UAV data component 1240 can receive route information from a network entity based on the UAV driving mode being a network-controlled driving mode, the route information including one or more of the following: a routing path of the UAV, a position-related allowed speed of the UAV, a position-related altitude of the UAV, an expected departure time of the UAV, an expected arrival time of the UAV, and the locations of obstacles in the planned route of the UAV, as described with respect to 1012.

[0180] The sending component 1234 can send the route information calculated by the UAV to the network entity based on the UAV driving mode being the UAV autonomous driving mode, and the UAV data component 1240 can receive an indication of approval or rejection of the planned route associated with the route information calculated by the UAV from the network entity, as described with respect to 1014 and 1016, respectively.

[0181] The UAV data component 1240 can receive route information from a network entity based on the UAV driving mode being switched to a network-controlled driving mode based on the refusal, as described with respect to 1018.

[0182] The sending component 1234 can periodically send the geographic location of the UAV to the network entity during the transportation of the UAV on the planned route, as described with respect to 1020.

[0183] The sending component 1234 can send measurements of the reference signal to the network entity during the UAV's transportation on the planned route, the measurements indicating the geographic location of the UAV, as described with respect to 1022.

[0184] The sending component 1234 can send a reference signal to a network entity during the transportation of the UAV on the planned route, the reference signal indicating the geographic location of the UAV, as described with respect to 1024.

[0185] The sending component 1234 can send cell information to the network entity during the transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV, as described with respect to 1026.

[0186] The UAV data component 1240 can receive a second message instructing the UAV to follow the planned route or return to the UAV's departure location based on the UAV's geographic location indicating that the UAV is not on the planned route, as described with respect to 1027.

[0187] The UAV data component 1240 can receive route information from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating the entirety of the planned route within the cell of the network entity based on the destination location of the UAV, as described with respect to 1028.

[0188] The UAV data component 1240 can receive route information from a network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of a planned route within a cell of a different network entity based on the destination location of the UAV, as described with respect to 1030.

[0189] The UAV data component 1240 can receive calculated route information originating from different network entities based on the UAV driving mode being a network-controlled driving mode, as described with respect to 1032.

[0190] The sending component 1234 can send the route information calculated by the UAV to the network entity in a radio resource control (RRC) message based on the UAV driving mode being the UAV autonomous driving mode, and the UAV data component 1240, the UE can receive from the network entity an indication of approval or rejection of a planned route originating from a different network entity, the planned route being associated with the route information calculated by the UAV, as described by 1034 and 1036, respectively.

[0191] The sending component 1234 can send the UAV calculated route information to different network entities in a non-access stratum (NAS) message based on the UAV driving mode being a UAV autonomous driving mode, and the UAV data component 1240 can receive indications of approval or rejection of the planned route associated with the UAV calculated route information from different network entities, as described by 1037 and 1038 respectively.

[0192] The sending component 1234 can send the route information calculated by the UAV in a radio resource control (RRC) message or a non-access stratum (NAS) message based on the UAV driving mode being a UAV autonomous driving mode, and the UAV data component 1240 can receive an indication of a rejection of the planned route associated with the route information calculated by the UAV, and the UAV data component 1240 can receive the route information of the UAV autonomous driving mode or the network-controlled driving mode based on the rejection, as described by 1040, 1042 and 1044 respectively.

[0193] The sending component 1234 can send a request to the network entity to switch the UAV driving mode to a network-controlled driving mode or a UAV automatic driving mode based on a change in the characteristics of the command and control (C2) link between the UAV and the UAV controller, and the UAV data component 1240 can receive a different UAV driving mode from the network entity in response to the request, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode, as described by 1046 and 1048 respectively.

[0194] The UAV data component 1240 can receive a different UAV driving mode from a network entity in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode, and the different UAV driving mode is one of the network-controlled driving mode or the UAV autonomous driving mode, as described by 1050.

[0195] The sending component 1234 can send a report indicating measurements associated with a command and control (C2) link between the UAV and the UAV controller, and the UAV data component 1240 can receive different UAV driving modes from the network entity in response to the report, as described by 1052 and 1054, respectively.

[0196] The device may include executing FIG. 10A to FIG. 10D The additional components of each box of the algorithm in the preceding flowchart. Therefore, FIG. 10A to FIG. 10D Each block in the aforementioned flow chart of can 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, which are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by a processor, or some combination thereof.

[0197] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes: a component for sending unmanned aerial vehicle (UAV) data supporting uplink communication and downlink communication with a network entity; and a component for receiving a message from the network entity including a UAV driving mode, wherein the UAV driving mode indicates that the device is flying on a planned route, and the device is a UAV.

[0198] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes a component for sending a second message indicating to a network entity at least one driving mode supported by the UAV, wherein the UAV driving mode is at least partially based on the driving mode supported by the at least one UAV.

[0199] In one configuration, the device 1202, in particular the cellular baseband processor 1204, includes: a component for sending route information to a network entity based on the UAV driving mode being a network-controlled driving mode, the route information including one or more of the following: UAV location, UAV departure time, UAV departure location, UAV destination location, UAV arrival time, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) location, UAV heading, UAV speed, UAV battery status and UAV characteristics.

[0200] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes a component for receiving route information from a network entity based on the UAV driving mode being a network-controlled driving mode, the route information being further received based on a destination location of the UAV or an expected departure time of the UAV from an application server in communication with the network entity.

[0201] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes a component for receiving route information from a network entity based on the UAV driving mode being a network-controlled driving mode, the route information including one or more of the following: a routing path of the UAV, a position-dependent allowed speed of the UAV, a position-dependent altitude of the UAV, an expected departure time of the UAV, an expected arrival time of the UAV, and locations of obstacles in the planned route of the UAV.

[0202] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes: a component for sending route information calculated by the UAV to a network entity based on the UAV driving mode being a UAV autonomous driving mode; and a component for receiving an indication of approval or rejection of a planned route associated with the route information calculated by the UAV from the network entity.

[0203] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes components for receiving route information from a network entity based on the UAV driving mode being switched to a network-controlled driving mode based on the refusal.

[0204] In one configuration, the apparatus 1202, and in particular the cellular baseband processor 1204, includes means for periodically sending the geographic location of the UAV to a network entity during transit of the UAV on a planned route.

[0205] In one configuration, the apparatus 1202, and in particular the cellular baseband processor 1204, includes means for sending measurements of a reference signal to a network entity during transportation of the UAV on a planned route, the measurements indicating a geographic location of the UAV.

[0206] In one configuration, the apparatus 1202, and in particular the cellular baseband processor 1204, includes means for sending a reference signal to a network entity during transportation of the UAV on a planned route, the reference signal indicating the geographic location of the UAV.

[0207] In one configuration, the apparatus 1202, and in particular the cellular baseband processor 1204, includes means for sending cell information to a network entity during transportation of the UAV on a planned route, the cell information indicating a geographic location of the UAV.

[0208] In one configuration, the apparatus 1202, and in particular the cellular baseband processor 1204, includes components for receiving a second message instructing the UAV to follow the planned route or return to the UAV's departure location based on the UAV's geographic location indicating that the UAV is not on the planned route.

[0209] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes a component for receiving route information from a network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating the entirety of the planned route based on the UAV's destination location being within a cell of the network entity.

[0210] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes a component for receiving route information from a network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of a planned route based on the UAV's destination location being within a cell of a different network entity.

[0211] In one configuration, the apparatus 1202, and in particular the cellular baseband processor 1204, includes components for receiving, from the network entity, calculated route information originating from a different network entity based on the UAV driving mode being a network-controlled driving mode.

[0212] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes: a component for sending route information calculated by the UAV to a network entity in a radio resource control (RRC) message based on whether the UAV driving mode is a UAV autonomous driving mode; and a component for receiving an indication of approval or rejection of a planned route originating from a different network entity from the network entity, the planned route being associated with the route information calculated by the UAV.

[0213] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes: a component for sending UAV calculated route information to different network entities in a non-access stratum (NAS) message based on whether the UAV driving mode is a UAV autonomous driving mode; and a component for receiving an indication of approval or rejection of a planned route associated with the UAV calculated route information from the different network entities.

[0214] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes: a component for sending UAV calculated route information in a radio resource control (RRC) message or a non-access stratum (NAS) message based on whether the UAV driving mode is a UAV autonomous driving mode; a component for receiving an indication of a rejection of a planned route associated with the UAV calculated route information; and a component for receiving route information of the UAV autonomous driving mode or a network controlled driving mode based on the rejection.

[0215] In one configuration, the device 1202, in particular the cellular baseband processor 1204, includes: a component for sending a request to a network entity to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode based on a change in the characteristics of a command and control (C2) link between the UAV and the UAV controller; and a component for receiving a different UAV driving mode from the network entity in response to the request, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

[0216] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes a component for receiving a different UAV driving mode from a network entity in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

[0217] In one configuration, the device 1202, and in particular the cellular baseband processor 1204, includes: a component for sending a report indicating measurements associated with a command and control (C2) link between the UAV and a UAV controller; and a component for receiving different UAV driving modes from a network entity in response to the report.

[0218] The aforementioned means may be one or more of the aforementioned components of the apparatus 1202 configured to perform the functions recited by the aforementioned means. As described above, the apparatus 1202 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Therefore, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0219] Fig.13 1300 is an example of a hardware implementation for an apparatus 1302. The apparatus 1302 is a BS and includes a baseband unit 1304. The baseband unit 1304 can communicate with the UE 104 via a cellular RF transceiver. The baseband unit 1304 may include a computer-readable medium / memory. The baseband unit 1304 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 1304, causes the baseband unit 1304 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1304 when executing the software. The baseband unit 1304 also includes a receiving component 1330, a communication manager 1332, and a sending component 1334. The communication manager 1332 includes one or more of the illustrated components. The components within the communication manager 1332 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1304. The baseband unit 1304 may be a component of the BS 310 and may include a memory 376 and / or at least one of the TX processor 316 , the RX processor 370 , and the controller / processor 375 .

[0220] The communications manager 1332 includes a UAV data component 1340 that receives unmanned aerial vehicle (UAV) data that supports uplink and downlink communications with a user equipment (UE), the UE being a UAV, for example, as described in conjunction with 1102 .

[0221] The UAV data component 1340 may receive a second message indicating to the network entity at least one UAV supported driving mode, wherein the UAV driving mode is based at least in part on the at least one UAV supported driving mode, as described with respect to 1108.

[0222] The UAV data component 1340 can receive route information based on the UAV driving mode being a network-controlled driving mode, and the route information includes one or more of the following: UAV location, UAV departure time, UAV departure location, UAV destination location, UAV arrival time, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) location, UAV heading, UAV speed, UAV battery status and UAV characteristics, as described with respect to 1110.

[0223] The sending component 1334 can send route information based on the UAV driving mode being a network-controlled driving mode, and the route information is further sent based on the destination location of the UAV or the expected departure time of the UAV from an application server that communicates with the network entity, as described with respect to 1112.

[0224] The sending component 1334 can send route information based on the UAV driving mode being a network-controlled driving mode, and the route information includes one or more of the following: the routing path of the UAV, the position-related allowed speed of the UAV, the position-related altitude of the UAV, the expected departure time of the UAV, the expected arrival time of the UAV, and the location of obstacles in the planned route of the UAV, as described with respect to 1112.

[0225] The UAV data component 1340 can receive the route information calculated by the UAV based on the UAV driving mode being the UAV autonomous driving mode, and the sending component 1334 can send an indication of approval or rejection of the planned route associated with the route information calculated by the UAV, as described with respect to 1114 and 1116, respectively.

[0226] The sending component 1334 can send route information based on the UAV driving mode based on the refusal to be switched to a network-controlled driving mode, as described with respect to 1118.

[0227] The UAV data component 1340 can periodically receive the geographic location of the UAV during the UAV's transit on the planned route, as described with respect to 1120.

[0228] The UAV data component 1340 can receive measurements of reference signals during the UAV's transit on the planned route, the measurements indicating the UAV's geographic location, as described with respect to 1122.

[0229] The UAV data component 1340 can receive a reference signal during the UAV's transit on the planned route, the reference signal indicating the UAV's geographic location, as described with respect to 1124.

[0230] The UAV data component 1340 can receive cell information during the UAV's transportation on the planned route, which cell information indicates the geographic location of the UAV, as described with respect to 1126.

[0231] The sending component 1334 can send a second message instructing the UAV to follow the planned route or return to the UAV's starting location based on the UAV's geographic location indicating that the UAV is not on the planned route, as described with respect to 1127.

[0232] The sending component 1334 can send route information based on the UAV driving mode being a network-controlled driving mode, and the route information indicates the entirety of the planned route within the cell of the network entity based on the destination location of the UAV, as described with respect to 1128.

[0233] The sending component 1334 can send route information based on the UAV driving mode being a network-controlled driving mode, and the route information indicates a portion of the planned route within a cell of a different network entity based on the destination location of the UAV, as described with respect to 1130.

[0234] The sending component 1334 can send the calculated route information originating from different network entities based on the UAV driving mode being a network-controlled driving mode, as described with respect to 1132.

[0235] The UAV data component 1340 can receive the route information calculated by the UAV in a radio resource control (RRC) message based on the UAV driving mode being a UAV autonomous driving mode, and the sending component 1334 can send an indication of approval or rejection of a planned route originating from a different network entity, which planned route is associated with the route information calculated by the UAV, as described by the UAV data component 1340 and the sending component 1334, respectively.

[0236] The UAV data component 1340 can receive the route information calculated by the UAV in a radio resource control (RRC) message based on the UAV driving mode being the UAV autonomous driving mode, the sending component 1334 can send an indication of a rejection of the planned route associated with the route information calculated by the UAV, and the sending component 1334 can send the route information of the UAV autonomous driving mode or the network controlled driving mode based on the rejection, as described by 1138, 1140 and 1142 respectively.

[0237] The UAV data component 1340 can receive a request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode based on a change in the characteristics of the command and control (C2) link between the UAV and the UAV controller, and the sending component 1334 can send a different UAV driving mode in response to the request, which is one of the network-controlled driving mode or the UAV autonomous driving mode, as described by 1144 and 1146 respectively.

[0238] The sending component 1334 can send a different UAV driving mode in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode, and the different UAV driving mode is one of the network-controlled driving mode or the UAV autonomous driving mode, as described by 1148.

[0239] The UAV data component 1340 can receive reports indicating measurements associated with a command and control (C2) link between the UAV and a UAV controller, and the sending component 1334 can send different UAV driving modes in response to the reports, as described by 1150 and 1152, respectively.

[0240] The device may include executing FIG. 11A to FIG. 11D The additional components of each box of the algorithm in the preceding flowchart. Therefore, FIG. 11A to FIG. 11D Each block in the aforementioned flow chart of can 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, which are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium so as to be implemented by a processor, or some combination thereof.

[0241] In one configuration, the device 1302, and in particular the baseband unit 1304, includes: a component for receiving unmanned aerial vehicle (UAV) data supporting uplink communication and downlink communication with a user equipment (UE), the UE being a UAV; and a component for sending a message including a UAV driving mode, the UAV driving mode indicating that the UE is flying on a planned route.

[0242] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes components for: the UAV data component 1340 can receive a second message indicating to a network entity at least one UAV supported driving mode, wherein the UAV driving mode is at least partially based on the at least one UAV supported driving mode.

[0243] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes: a component for receiving route information based on the UAV driving mode being a network-controlled driving mode, the route information including one or more of the following: UAV location, UAV departure time, UAV departure location, UAV destination location, UAV arrival time, UAV flight capabilities, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) location, UAV heading, UAV speed, UAV battery status, and UAV characteristics.

[0244] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes: a component for sending route information based on the UAV driving mode being a network-controlled driving mode, the route information being further sent based on the destination location of the UAV or the expected departure time of the UAV originating from an application server communicating with a network entity.

[0245] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes a component for sending route information based on the UAV driving mode being a network-controlled driving mode, the route information including one or more of the following: a routing path of the UAV, a position-related allowed speed of the UAV, a position-related altitude of the UAV, an expected departure time of the UAV, an expected arrival time of the UAV, and the location of obstacles in the planned route of the UAV.

[0246] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes: a component for receiving route information calculated by the UAV based on the UAV driving mode being the UAV autonomous driving mode; and a component for sending an indication of approval or rejection of the planned route associated with the route information calculated by the UAV.

[0247] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes components for sending route information based on the UAV driving mode being switched to a network-controlled driving mode based on the refusal.

[0248] In one configuration, the apparatus 1302, and in particular the cellular baseband processor 1304, includes components for periodically receiving the geographic location of the UAV during transit of the UAV on a planned route.

[0249] In one configuration, the apparatus 1302, and in particular the cellular baseband processor 1304, includes means for receiving measurements of a reference signal during transit of the UAV on a planned route, the measurements being indicative of the geographic location of the UAV.

[0250] In one configuration, the apparatus 1302, and in particular the cellular baseband processor 1304, includes means for receiving a reference signal during transit of the UAV on a planned route, the reference signal being indicative of the geographic location of the UAV.

[0251] In one configuration, the apparatus 1302, and in particular the cellular baseband processor 1304, includes means for receiving cell information during transportation of the UAV on a planned route, the cell information indicating a geographic location of the UAV.

[0252] In one configuration, the apparatus 1302, and in particular the cellular baseband processor 1304, includes components for sending a second message instructing the UAV to follow the planned route or return to the UAV's departure location based on the UAV's geographic location indicating that the UAV is not on the planned route.

[0253] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes a component for sending route information based on the UAV driving mode being a network-controlled driving mode, the route information indicating the entirety of the planned route based on the UAV's destination location being within a cell of the network entity.

[0254] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes a component for sending route information based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of the planned route based on the UAV's destination location being within a cell of a different network entity.

[0255] In one configuration, the apparatus 1302, and in particular the cellular baseband processor 1304, includes components for transmitting calculated route information originating from a different network entity based on whether the UAV driving mode is a network-controlled driving mode.

[0256] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes: a component for receiving route information calculated by the UAV in a radio resource control (RRC) message based on whether the UAV driving mode is a UAV autonomous driving mode; and a component for sending an indication of approval or rejection of a planned route originating from a different network entity, the planned route being associated with the route information calculated by the UAV.

[0257] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes: a component for receiving UAV calculated route information in a radio resource control (RRC) message based on the UAV driving mode being a UAV autonomous driving mode; a component for sending an indication of a rejection of a planned route associated with the UAV calculated route information; and a component for sending route information of the UAV autonomous driving mode or a network controlled driving mode based on the rejection.

[0258] In one configuration, the device 1302, in particular the cellular baseband processor 1304, includes: a component for receiving a request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode based on a change in the characteristics of a command and control (C2) link between the UAV and a UAV controller; and a component for sending a different UAV driving mode in response to the request, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

[0259] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes a component for sending a different UAV driving mode in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

[0260] In one configuration, the device 1302, and in particular the cellular baseband processor 1304, includes components for receiving a report indicating measurements associated with a command and control (C2) link between the UAV and a UAV controller, and the sending component 1334 can send different UAV driving modes in response to the report.

[0261] The aforementioned means may be one or more of the aforementioned components of the apparatus 1302 configured to perform the functions recited by the aforementioned means. As described above, the apparatus 1302 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Therefore, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0262] The present disclosure provides for the management, regulation of airspace and flight operations / configurations of UAVs. Route management, operating modes, emergency overrides, and network control of UAV routing and operations are possible within the scope of the present disclosure.

[0263] Further disclosure is included in the appendix.

[0264] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not meant to be limited to the specific order or hierarchy provided.

[0265] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein the elements mentioned in the singular are not intended to represent "one and only one", unless specifically so stated, but "one or more". Terms such as "if", "when ......" and "while ......" should be interpreted as "under the conditions of ......", rather than meaning an immediate time relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but only mean that if the conditions are met, the action will occur without a specific or immediate time constraint to make the action occur. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having an advantage over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include 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,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “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, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," and "device" cannot replace the word "component." Therefore, no claim element will be construed as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0266] The following examples are merely illustrative and may be combined with aspects of other embodiments or teachings described herein, but are not limited thereto.

[0267] Embodiment 1 is a device for wireless communication, the device comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to: send unmanned aerial vehicle (UAV) data supporting uplink communication and downlink communication to a network entity; and receive a message including a UAV driving mode from the network entity, the UAV driving mode indicating that the device is flying on a planned route, the device being a UAV.

[0268] Embodiment 2 is a device according to embodiment 1, wherein the at least one processor is further configured to: send a second message to the network entity indicating at least one driving mode supported by the UAV, wherein the UAV driving mode is at least partially based on the at least one driving mode supported by the UAV.

[0269] Embodiment 3 is a device according to embodiment 2, wherein the second message also indicates a preferred driving mode of the UAV, wherein the UAV driving mode is the preferred driving mode of the UAV.

[0270] Embodiment 4 is a device according to embodiment 2 or 3, wherein the at least one processor is further configured to: send route information to the network entity based on that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: the departure time of the UAV, the departure three-dimensional (3D) position of the UAV, the destination 3D position of the UAV, the arrival time of the UAV, the UAV flight capability, the UAV operator license, the UAV mission type, the location of obstacles in the planned route of the UAV, the real-time UAV 3D position, the UAV heading, the UAV speed, the UAV battery status and the UAV characteristics.

[0271] Embodiment 5 is a device according to embodiment 2 or 3, wherein the at least one processor is further configured to: receive route information from the network entity based on that the UAV driving mode is a network-controlled driving mode, and the route information is further received based on the destination location of the UAV or the expected departure time of the UAV from an application server communicating with the network entity.

[0272] Embodiment 6 is a device according to any one of embodiments 1 to 3, wherein the at least one processor is further configured to: receive route information from the network entity based on that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: the routing path of the UAV, the position-related allowed speed of the UAV, the position-related allowed height of the UAV, the expected departure time of the UAV, the expected arrival time of the UAV, and the location of obstacles in the planned route of the UAV.

[0273] Embodiment 7 is a device according to any one of embodiments 1 to 6, wherein based on the fact that the UAV driving mode is a network-controlled driving mode, the planned route is associated with a route path accuracy, and the route path accuracy is at the meter level, street level, block level or network entity level.

[0274] Embodiment 8 is a device according to any one of embodiments 1 to 7, wherein the UAV driving mode is based at least in part on one or more of the UAV destination, the quality of service (QoS) of the uplink communication or the downlink communication, the geometry of the planned route, and the UAV traffic in the planned route.

[0275] Embodiment 9 is a device according to any one of embodiments 1 to 3, wherein the at least one processor is further configured to: send the route information calculated by the UAV to the network entity based on the UAV driving mode being the UAV automatic driving mode; and receive an indication of approval or rejection of the planned route associated with the route information calculated by the UAV from the network entity.

[0276] Embodiment 10 is a device according to embodiment 9, wherein the route information calculated by the UAV includes one or more of the following items: UAV position, departure time of the UAV, departure 3D position of the UAV, destination 3D position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

[0277] Embodiment 11 is an apparatus according to embodiment 9 or 10, wherein the at least one processor is further configured to: receive route information from the network entity based on the UAV driving mode based on the refusal to be switched to the network-controlled driving mode.

[0278] Embodiment 12 is an apparatus according to any one of embodiments 1 to 3 and 9 to 11, wherein the at least one processor is further configured to: periodically send the geographic location of the UAV to the network entity during the transportation of the UAV on the planned route.

[0279] Embodiment 13 is an apparatus according to any one of embodiments 1 to 3 and 9 to 12, wherein the at least one processor is further configured to: send measurements of reference signals to the network entity during transportation of the UAV on the planned route, the measurements indicating the geographic location of the UAV.

[0280] Embodiment 14 is a device according to any one of embodiments 1 to 3 and 9 to 13, wherein the at least one processor is further configured to: send a reference signal to the network entity during the transportation of the UAV on the planned route, and the reference signal indicates the geographic location of the UAV.

[0281] Embodiment 15 is a device according to any one of embodiments 1 to 3 and 9 to 14, wherein the at least one processor is further configured to: send cell information to the network entity during the transportation of the UAV on the planned route, and the cell information indicates the geographic location of the UAV.

[0282] Embodiment 16 is a device according to any one of embodiments 1 to 3 and 9 to 15, wherein the at least one processor is further configured to: based on the geographic location of the UAV indicating that the UAV is not on the planned route, receive a second message instructing the UAV to follow the planned route or return to the starting location of the UAV.

[0283] Embodiment 17 is a device according to any one of embodiments 1 to 3 and 9 to 16, wherein the UAV driving mode is one of the following: a UAV automatic driving mode, a network-controlled driving mode, a UAV controller driving mode, or a combination of at least two of the UAV automatic driving mode, the network-controlled driving mode, and the UAV controller driving mode.

[0284] Embodiment 18 is a device according to any one of embodiments 1 to 8 and 17, wherein the at least one processor is further configured to: receive route information from the network entity based on that the UAV driving mode is a network-controlled driving mode, and the route information indicates the entirety of the planned route based on that the destination location of the UAV is within the cell of the network entity.

[0285] Embodiment 19 is a device according to any one of embodiments 1 to 8 and 17, wherein the at least one processor is further configured to: receive route information from the network entity based on that the UAV driving mode is a network-controlled driving mode, and the route information indicates a portion of the planned route based on that the destination location of the UAV is within a cell of a different network entity.

[0286] Embodiment 20 is a device according to any one of embodiments 1 to 8 and 17, wherein the at least one processor is further configured to: receive calculated route information originating from different network entities from the network entity based on the UAV driving mode being a network-controlled driving mode.

[0287] Embodiment 21 is a device according to any one of embodiments 1 to 3 and 9 to 17, wherein the at least one processor is further configured to: send the route information calculated by the UAV to the network entity in a radio resource control (RRC) message based on the UAV driving mode being a UAV autonomous driving mode; and receive an indication of approval or rejection of the planned route from the network entity or a different network entity, the planned route being associated with the route information calculated by the UAV.

[0288] Embodiment 22 is a device according to any one of embodiments 1 to 3 and 9 to 17, wherein the at least one processor is further configured to: send route information calculated by the UAV to different network entities in a non-access stratum (NAS) message based on that the UAV driving mode is a UAV autonomous driving mode; and receive an indication of approval or rejection of the planned route associated with the route information calculated by the UAV from the different network entities.

[0289] Embodiment 23 is a device according to any one of embodiments 1 to 3, 9 to 17, 21 and 22, wherein the at least one processor is further configured to: send route information calculated by the UAV in a radio resource control (RRC) message or a non-access stratum (NAS) message based on that the UAV driving mode is a UAV autonomous driving mode; receive an indication of a rejection of the planned route associated with the route information calculated by the UAV; and receive route information of the UAV autonomous driving mode or the network-controlled driving mode based on the rejection.

[0290] Embodiment 24 is a device according to any one of Embodiments 1 to 3 and 17, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: send a request to the network entity to switch the UAV driving mode to a network-controlled driving mode or a UAV automatic driving mode based on a change in the characteristics of a command and control (C2) link between the UAV and the UAV controller; and receive a different UAV driving mode from the network entity in response to the request, wherein the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

[0291] Embodiment 25 is the apparatus of embodiment 24, wherein the change in the characteristic of the C2 link is a loss of connectivity of the C2 link.

[0292] Embodiment 26 is an apparatus according to embodiment 24, wherein the change in the characteristic of the C2 link is that a reference signal received power (RSRP) of a reference signal carried in the C2 link is lower than a threshold.

[0293] Embodiment 27 is an apparatus as in any one of embodiments 24 to 26, wherein the request indicates the change in the characteristic of the C2 link.

[0294] Embodiment 28 is an apparatus according to any one of embodiments 24 to 27, wherein the request also indicates a preferred driving mode of the UAV.

[0295] Embodiment 29 is a device according to any one of embodiments 1 to 3 and 17, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: receive a different UAV driving mode from the network entity in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV automatic driving mode, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

[0296] Embodiment 30 is an apparatus according to any one of Embodiments 1 to 3 and 17, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: send a report indicating measurements associated with a command and control (C2) link between the UAV and the UAV controller; and receive a different UAV driving mode from the network entity in response to the report.

[0297] Embodiment 31 is an apparatus according to any one of embodiments 1 to 30, wherein the network entity is a base station.

[0298] Embodiment 32 is a method for wireless communication at a user equipment (UE), the method comprising steps performed by the apparatus of any one of embodiments 1 to 31.

[0299] Embodiment 33 is a device for wireless communication, the device comprising: a component for sending unmanned aerial vehicle (UAV) data supporting uplink communication and downlink communication with a network entity; and a component for receiving a message including a UAV driving mode from the network entity, the UAV driving mode indicating that the device is flying on a planned route, the device being a UAV.

[0300] Embodiment 34 is a non-transitory computer-readable medium storing computer executable code, which, when executed by a processor, causes the processor to: send unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a network entity; and receive a message from the network entity including a UAV driving mode, wherein the UAV driving mode indicates that the device is flying on a planned route, wherein the device is a UAV.

[0301] Embodiment 35 is a device for wireless communication, the device comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to: receive unmanned aerial vehicle (UAV) data supporting uplink communication and downlink communication with a user equipment (UE), the UE being a UAV; and send a message including a UAV driving mode, the UAV driving mode indicating that the UE is flying on a planned route.

[0302] Embodiment 36 is a device according to embodiment 35, wherein the at least one processor is further configured to: receive a second message indicating a driving mode supported by at least one UAV, wherein the UAV driving mode is at least partially based on the driving mode supported by the at least one UAV.

[0303] Embodiment 37 is a device according to embodiment 36, wherein the second message also indicates the UAV preferred driving mode, wherein the UAV driving mode is the UAV preferred driving mode.

[0304] Embodiment 38 is a device according to embodiment 36 or 37, wherein the at least one processor is further configured to: receive route information based on that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

[0305] Embodiment 39 is a device according to embodiment 36 or 37, wherein the at least one processor is further configured to: send route information based on that the UAV driving mode is a network-controlled driving mode, and the route information is further sent based on the destination location of the UAV or the expected departure time of the UAV from an application server communicating with the device.

[0306] Embodiment 40 is a device according to any one of embodiments 35 to 37, wherein the at least one processor is further configured to: send route information based on that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: the routing path of the UAV, the position-related allowed speed of the UAV, the position-related allowed height of the UAV, the expected departure time of the UAV, the expected arrival time of the UAV, and the location of obstacles in the planned route of the UAV.

[0307] Embodiment 41 is a device according to any one of embodiments 35 to 40, wherein based on the fact that the UAV driving mode is a network-controlled driving mode, the planned route is associated with a route path accuracy, and the route path accuracy is at the meter level, street level, block level or network entity level.

[0308] Embodiment 42 is a device according to any one of Embodiments 35 to 41, wherein the UAV driving mode is based at least in part on one or more of the UAV destination, the quality of service (QoS) of the uplink communication or the downlink communication, the geometry of the planned route, and the UAV traffic in the planned route.

[0309] Embodiment 43 is a device according to any one of embodiments 35 to 37, wherein the at least one processor is further configured to: receive route information calculated by the UAV based on that the UAV driving mode is a UAV automatic driving mode; and send an indication of approval or rejection of the planned route associated with the route information calculated by the UAV.

[0310] Embodiment 44 is a device according to embodiment 43, wherein the route information calculated by the UAV includes one or more of the following items: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

[0311] Embodiment 45 is an apparatus according to embodiment 43 or 44, wherein the at least one processor is further configured to: send route information based on the UAV driving mode based on the refusal to be switched to the network-controlled driving mode.

[0312] Embodiment 46 is an apparatus according to any one of embodiments 35 to 37 and 43 to 45, wherein the at least one processor is further configured to: periodically receive the geographic location of the UAV during the transportation of the UAV on the planned route.

[0313] Embodiment 47 is an apparatus according to any one of Embodiments 35 to 37 and 43 to 46, wherein the at least one processor is further configured to: receive measurements of reference signals during transportation of the UAV on the planned route, the measurements indicating the geographic location of the UAV.

[0314] Embodiment 48 is a device according to any one of embodiments 35 to 37 and 43 to 47, wherein the at least one processor is further configured to: receive a reference signal during the transportation of the UAV on the planned route, and the reference signal indicates the geographic location of the UAV.

[0315] Embodiment 49 is a device according to any one of embodiments 35 to 37 and 43 to 48, wherein the at least one processor is further configured to: receive cell information during the transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV.

[0316] Embodiment 50 is a device according to any one of embodiments 35 to 37 and 43 to 49, wherein the at least one processor is further configured to: based on the geographic location of the UAV indicating that the UAV is not on the planned route, send a second message instructing the UAV to follow the planned route or return to the starting location of the UAV.

[0317] Embodiment 51 is a device according to any one of Embodiments 35 to 37 and 43 to 50, wherein the UAV driving mode is one of the following: a UAV automatic driving mode, a network-controlled driving mode, a UAV controller driving mode, or a combination of at least two of the UAV automatic driving mode, the network-controlled driving mode, and the UAV controller driving mode.

[0318] Embodiment 52 is a device according to embodiments 35 to 42 and 51, wherein the at least one processor is further configured to: send route information based on that the UAV driving mode is a network-controlled driving mode, and the route information indicates the entirety of the planned route based on the destination location of the UAV being within the cell of the device.

[0319] Embodiment 53 is a device according to embodiments 35 to 42 and 51, wherein the device is a network entity, and wherein the at least one processor is further configured to: send route information based on that the UAV driving mode is a network-controlled driving mode, and the route information indicates a portion of the planned route based on the destination location of the UAV being within a cell of a different network entity.

[0320] Embodiment 54 is a device according to embodiments 35 to 42 and 51, wherein the device is a network entity, and wherein the at least one processor is further configured to: send calculated route information originating from different network entities based on the UAV driving mode being a network-controlled driving mode.

[0321] Embodiment 55 is a device according to any one of embodiments 35 to 37 and 43 to 51, wherein the device is a network entity, and wherein the at least one processor is further configured to: receive route information calculated by the UAV in a radio resource control (RRC) message based on that the UAV driving mode is a UAV autonomous driving mode; and send an indication of approval or rejection of the planned route originating from a different network entity, the planned route being associated with the route information calculated by the UAV.

[0322] Embodiment 56 is a device according to any one of embodiments 35 to 37, 43 to 51 and 55, wherein the at least one processor is further configured to: receive route information calculated by the UAV in a radio resource control (RRC) message based on that the UAV driving mode is a UAV autonomous driving mode; send an indication of a rejection of the planned route associated with the route information calculated by the UAV; and send route information of the UAV autonomous driving mode or the network-controlled driving mode based on the rejection.

[0323] Embodiment 57 is an apparatus according to any one of Embodiments 35 to 37 and 51, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: receive a request to switch the UAV driving mode to a network-controlled driving mode or a UAV automatic driving mode based on a change in the characteristics of a command and control (C2) link between the UAV and the UAV controller; and send a different UAV driving mode in response to the request, wherein the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

[0324] Embodiment 58 is an apparatus according to embodiment 57, wherein the change in the characteristic of the C2 link is a loss of connectivity of the C2 link.

[0325] Embodiment 59 is an apparatus according to embodiment 57, wherein the change in the characteristic of the C2 link is that a reference signal received power (RSRP) of a reference signal carried in the C2 link is lower than a threshold.

[0326] Embodiment 60 is an apparatus according to any one of embodiments 57 to 59, wherein the request indicates the change in the characteristic of the C2 link.

[0327] Embodiment 61 is an apparatus according to any one of embodiments 57 to 60, wherein the request also indicates a preferred driving mode of the UAV.

[0328] Embodiment 62 is a device according to any one of embodiments 35 to 37 and 51, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: send a different UAV driving mode in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV automatic driving mode, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

[0329] Embodiment 63 is an apparatus according to any one of Embodiments 35 to 37 and 51, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: receive a report indicating measurements associated with a command and control (C2) link between the UAV and the UAV controller; and send a different UAV driving mode in response to the report.

[0330] Embodiment 64 is an apparatus according to any one of embodiments 35 to 63, wherein the apparatus is a base station.

[0331] Embodiment 65 is a method for wireless communication at a network entity, the method comprising steps performed by an apparatus described in any one of Embodiments 35 to 64.

[0332] Embodiment 66 is a device for wireless communication, the device comprising: a component for receiving unmanned aerial vehicle (UAV) data supporting uplink communication and downlink communication with a user equipment (UE), the UE being a UAV; and a component for sending a message including a UAV driving mode, the UAV driving mode indicating that the UE is flying on a planned route.

[0333] Embodiment 67 is a non-transitory computer-readable medium storing computer executable code, which, when executed by a processor, causes the processor to: receive unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a user equipment (UE), the UE being a UAV; and send a message including a UAV driving mode, the UAV driving mode indicating that the UE is flying on a planned route.

[0334]

[0335]

[0336]

[0337]

[0338]

[0339]

[0340]

[0341]

[0342]

[0343]

[0344]

Claims

1. A device for wireless communication, the device comprising: Memory; and at least one processor coupled to the memory and configured to: transmitting unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with network entities; as well as A message including a UAV driving mode is received from the network entity, the UAV driving mode indicating that the device is to fly on a planned route, the device being a UAV.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: Send a second message indicating to the network entity at least one driving mode supported by the UAV, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV.

3. An apparatus according to claim 2, wherein the second message also indicates a UAV preferred driving mode, wherein the UAV driving mode is the UAV preferred driving mode.

4. The apparatus of claim 2, wherein the at least one processor is further configured to: Route information is sent to the network entity based on the fact that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: the departure time of the UAV, the departure three-dimensional (3D) position of the UAV, the destination 3D position of the UAV, the arrival time of the UAV, the UAV flight capability, the UAV operator license, the UAV mission type, the position of obstacles in the planned route of the UAV, the real-time UAV 3D position, the UAV heading, the UAV speed, the UAV battery status and the UAV characteristics.

5. The apparatus of claim 2, wherein the at least one processor is further configured to: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, and the route information is further received based on a destination location of the UAV or an expected departure time of the UAV from an application server that communicates with the network entity.

6. The apparatus of claim 1, wherein the at least one processor is further configured to: Route information is received from the network entity based on the fact that the UAV driving mode is a network-controlled driving mode, the route information including one or more of the following: a routing path of the UAV, a position-related allowed speed of the UAV, a position-related allowed altitude of the UAV, an expected departure time of the UAV, an expected arrival time of the UAV, and locations of obstacles in the planned route of the UAV.

7. The apparatus according to claim 1, wherein based on the UAV driving mode being a network-controlled driving mode, the planned route is associated with a route path accuracy, and the route path accuracy is at the meter level, street level, block level, or network entity level.

8. An apparatus according to claim 1, wherein the UAV driving mode is based at least in part on one or more of a UAV destination, a quality of service (QoS) of the uplink communication or the downlink communication, a geometry of the planned route, and UAV traffic in the planned route.

9. The apparatus of claim 1 , wherein the at least one processor is further configured to: sending the UAV calculated route information to the network entity based on the UAV driving mode being the UAV autonomous driving mode; and An indication of approval or rejection of the planned route associated with the route information calculated by the UAV is received from the network entity.

10. The apparatus of claim 9, wherein the route information calculated by the UAV comprises one or more of: UAV location, departure time of the UAV, departure 3D location of the UAV, destination 3D location of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) location, UAV heading, UAV speed, UAV battery status, and UAV characteristics.

11. The apparatus of claim 9, wherein the at least one processor is further configured to: Receiving route information from the network entity based on the UAV driving mode based on the refusal to switch to the network-controlled driving mode.

12. The apparatus of claim 1, wherein the at least one processor is further configured to: The geographic location of the UAV is periodically transmitted to the network entity during transportation of the UAV on the planned route.

13. The apparatus of claim 1, wherein the at least one processor is further configured to: Measurements of a reference signal are sent to the network entity during transit of the UAV on the planned route, the measurements indicating a geographic location of the UAV.

14. The apparatus of claim 1, wherein the at least one processor is further configured to: A reference signal is sent to the network entity during transportation of the UAV on the planned route, the reference signal indicating the geographic location of the UAV.

15. The apparatus of claim 1, wherein the at least one processor is further configured to: The cell information is sent to the network entity during transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV.

16. The apparatus of claim 1, wherein the at least one processor is further configured to: A second message is received based on the geographic location of the UAV indicating that the UAV is not on the planned route and instructing the UAV to follow the planned route or return to the starting location of the UAV.

17. The apparatus of claim 1, wherein the UAV driving mode is one of: UAV autopilot mode, Network-controlled driving modes, UAV controller driving mode, or A combination of at least two of the UAV autonomous driving mode, the network controlled driving mode and the UAV controller driving mode.

18. The apparatus of claim 1, wherein the at least one processor is further configured to: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating an entirety of the planned route based on a destination location of the UAV being within a cell of the network entity.

19. The apparatus of claim 1, wherein the at least one processor is further configured to: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of the planned route based on a destination location of the UAV being within a cell of a different network entity.

20. The apparatus of claim 1, wherein the at least one processor is further configured to: Calculated route information originating from a different network entity is received from the network entity based on the UAV driving mode being a network-controlled driving mode.

21. The apparatus of claim 1, wherein the at least one processor is further configured to: sending the UAV calculated route information to the network entity in a radio resource control (RRC) message based on the UAV driving mode being the UAV autonomous driving mode; and An indication of approval or rejection of the planned route originating from the network entity or a different network entity is received from the network entity, the planned route being associated with route information calculated by the UAV.

22. The apparatus of claim 1, wherein the at least one processor is further configured to: sending the UAV calculated route information to different network entities in a non-access stratum (NAS) message based on the UAV driving mode being the UAV autonomous driving mode; and An indication of approval or rejection of the planned route associated with the route information calculated by the UAV is received from the different network entity.

23. The apparatus of claim 1, wherein the at least one processor is further configured to: sending, in a radio resource control (RRC) message or a non-access stratum (NAS) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; receiving an indication of a rejection of the planned route associated with the route information calculated by the UAV; as well as Based on the refusal to receive route information of the UAV autonomous driving mode or network-controlled driving mode.

24. The apparatus of claim 1, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: sending a request to the network entity to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode based on a change in a characteristic of a command and control (C2) link between the UAV and a UAV controller; and A different UAV driving mode is received from the network entity in response to the request, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

25. The apparatus of claim 24, wherein the change in the characteristic of the C2 link is a loss of connectivity of the C2 link.

26. The apparatus of claim 24, wherein the change in the characteristic of the C2 link is that a reference signal received power (RSRP) of a reference signal carried in the C2 link is lower than a threshold.

27. The apparatus of claim 24, wherein the request indicates the change in the characteristic of the C2 link.

28. An apparatus according to claim 27, wherein the request also indicates a preferred driving mode of the UAV.

29. The apparatus of claim 1, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: A different UAV driving mode is received from the network entity in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

30. The apparatus of claim 1, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: sending a report indicating measurements associated with a command and control (C2) link between the UAV and a UAV controller; and A different UAV driving mode is received from the network entity in response to the report.

31. The apparatus of claim 1, wherein the network entity is a base station.

32. A method of wireless communication at a user equipment (UE), the method comprising: transmitting unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with network entities; as well as A message including a UAV driving mode is received from the network entity, the UAV driving mode indicating that the UE is flying on a planned route, the UE being a UAV.

33. The method according to claim 32, further comprising: Send a second message indicating to the network entity at least one driving mode supported by the UAV, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV.

34. A method according to claim 33, wherein the second message also indicates a UAV preferred driving mode, wherein the UAV driving mode is the UAV preferred driving mode.

35. The method of claim 33, further comprising: Route information is sent to the network entity based on the fact that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

36. The method of claim 33, further comprising: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, and the route information is further received based on a destination location of the UAV or an expected departure time of the UAV from an application server that communicates with the network entity.

37. The method of claim 32, further comprising: Route information is received from the network entity based on the fact that the UAV driving mode is a network-controlled driving mode, the route information including one or more of: a routing path of the UAV, a position-related allowed speed of the UAV, a position-related altitude of the UAV, an expected departure time of the UAV, an expected arrival time of the UAV, and locations of obstacles in the planned route of the UAV.

38. The method of claim 32, wherein based on the UAV driving mode being a network-controlled driving mode, the planned route is associated with a route path accuracy, and the route path accuracy is at the meter level, street level, block level, or network entity level.

39. A method according to claim 32, wherein the UAV driving mode is based at least in part on one or more of the UAV destination, the quality of service (QoS) of the uplink communication or the downlink communication, the geometry of the planned route, and the UAV traffic in the planned route.

40. The method of claim 32, further comprising: sending, to the network entity, route information calculated by the UAV based on the UAV driving mode being the UAV autonomous driving mode; as well as An indication of approval or rejection of the planned route associated with the route information calculated by the UAV is received from the network entity.

41. A method according to claim 40, wherein the route information calculated by the UAV includes one or more of the following: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

42. The method of claim 40, further comprising: Receiving route information from the network entity based on the UAV driving mode based on the refusal to switch to the network-controlled driving mode.

43. The method of claim 32, further comprising: The geographic location of the UAV is periodically transmitted to the network entity during transportation of the UAV on the planned route.

44. The method of claim 32, further comprising: Measurements of a reference signal are sent to the network entity during transit of the UAV on the planned route, the measurements indicating a geographic location of the UAV.

45. The method of claim 32, further comprising: A reference signal is sent to the network entity during transportation of the UAV on the planned route, the reference signal indicating the geographic location of the UAV.

46. ​​The method of claim 32, further comprising: The cell information is sent to the network entity during transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV.

47. The method of claim 32, further comprising: A second message is received based on the geographic location of the UAV indicating that the UAV is not on the planned route and instructing the UAV to follow the planned route or return to the starting location of the UAV.

48. The method of claim 32, wherein the UAV driving mode is one of: UAV autopilot mode, Network-controlled driving modes, UAV controller driving mode, or A combination of at least two of the UAV autonomous driving mode, the network controlled driving mode and the UAV controller driving mode.

49. The method of claim 32, further comprising: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating an entirety of the planned route based on a destination location of the UAV being within a cell of the network entity.

50. The method of claim 32, further comprising: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of the planned route based on a destination location of the UAV being within a cell of a different network entity.

51. The method of claim 32, further comprising: Calculated route information originating from a different network entity is received from the network entity based on the UAV driving mode being a network-controlled driving mode.

52. The method of claim 32, further comprising: sending, to the network entity, route information calculated by the UAV in a radio resource control (RRC) message based on the UAV driving mode being a UAV autonomous driving mode; as well as An indication of approval or rejection of the planned route originating from a different network entity is received from the network entity, the planned route being associated with route information calculated by the UAV.

53. The method of claim 32, further comprising: sending, in a non-access stratum (NAS) message, route information calculated by the UAV to different network entities based on the UAV driving mode being a UAV autonomous driving mode; as well as An indication of approval or rejection of the planned route associated with the route information calculated by the UAV is received from the different network entity.

54. The method of claim 32, further comprising: sending, in a radio resource control (RRC) message or a non-access stratum (NAS) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; receiving an indication of a rejection of the planned route associated with the route information calculated by the UAV; as well as Based on the refusal to receive route information of the UAV autonomous driving mode or network-controlled driving mode.

55. The method of claim 32, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: sending a request to the network entity to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode based on a change in a characteristic of a command and control (C2) link between the UAV and a UAV controller; as well as A different UAV driving mode is received from the network entity in response to the request, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

56. The method of claim 55, wherein the change in the characteristic of the C2 link is a loss of connectivity of the C2 link.

57. The method of claim 55, wherein the change in the characteristic of the C2 link is that a reference signal received power (RSRP) of a reference signal carried in the C2 link is below a threshold.

58. The method of claim 55, wherein the request indicates the change in the characteristic of the C2 link.

59. A method according to claim 58, wherein the request also indicates a preferred driving mode of the UAV.

60. The method of claim 32, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: A different UAV driving mode is received from the network entity in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

61. The method of claim 32, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: sending a report indicative of measurements associated with a command and control (C2) link between the UAV and a UAV controller; as well as A different UAV driving mode is received from the network entity in response to the report.

62. The method of claim 32, wherein the network entity is a base station.

63. An apparatus for wireless communication, the apparatus comprising: means for transmitting unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a network entity; and Means for receiving a message from the network entity including a UAV driving mode, the UAV driving mode indicating that the device is to fly on a planned route, the device being a UAV.

64. A non-transitory computer readable medium storing computer executable code, which, when executed by a processor, causes the processor to: transmitting unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a network entity; and A message including a UAV driving mode is received from the network entity, the UAV driving mode indicating that a device is flying on a planned route, the device being a UAV.

65. An apparatus for wireless communication, the apparatus comprising: Memory; and at least one processor coupled to the memory and configured to: receiving unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a user equipment (UE), the UE being the UAV; as well as A message is sent including a UAV driving mode, wherein the UAV driving mode indicates that the UE is flying on a planned route.

66. The apparatus of claim 65, wherein the at least one processor is further configured to: A second message is received indicating a driving mode supported by at least one UAV, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV.

67. An apparatus according to claim 66, wherein the second message also indicates a UAV preferred driving mode, wherein the UAV driving mode is the UAV preferred driving mode.

68. The apparatus of claim 66, wherein the at least one processor is further configured to: Route information is received based on that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

69. The apparatus of claim 66, wherein the at least one processor is further configured to: Route information is sent based on the UAV driving mode being a network-controlled driving mode, and the route information is further sent based on the destination location of the UAV or the expected departure time of the UAV from an application server in communication with the device.

70. The apparatus of claim 65, wherein the at least one processor is further configured to: Route information is sent based on the fact that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: the routing path of the UAV, the position-related allowed speed of the UAV, the position-related altitude of the UAV, the expected departure time of the UAV, the expected arrival time of the UAV, and the location of obstacles in the planned route of the UAV.

71. An apparatus according to claim 65, wherein based on the UAV driving mode being a network-controlled driving mode, the planned route is associated with a route path accuracy, and the route path accuracy is at the meter level, street level, block level or network entity level.

72. An apparatus according to claim 65, wherein the UAV driving mode is based at least in part on one or more of a UAV destination, a quality of service (QoS) of the uplink communication or the downlink communication, a geometry of the planned route, and UAV traffic in the planned route.

73. The apparatus of claim 65, wherein the at least one processor is further configured to: receiving route information calculated by the UAV based on the UAV driving mode being the UAV autonomous driving mode; and An indication of approval or rejection of the planned route is sent in association with the route information calculated by the UAV.

74. An apparatus according to claim 73, wherein the route information calculated by the UAV includes one or more of the following: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

75. The apparatus of claim 73, wherein the at least one processor is further configured to: Route information is sent based on the UAV driving mode and based on the refusal to switch to a network-controlled driving mode.

76. The apparatus of claim 65, wherein the at least one processor is further configured to: The geographic location of the UAV is periodically received during transportation of the UAV on the planned route.

77. The apparatus of claim 65, wherein the at least one processor is further configured to: Measurements of a reference signal are received during transit of the UAV on the planned route, the measurements indicating a geographic location of the UAV.

78. The apparatus of claim 65, wherein the at least one processor is further configured to: A reference signal is received during transportation of the UAV on the planned route, the reference signal indicating the geographic location of the UAV.

79. The apparatus of claim 65, wherein the at least one processor is further configured to: Cell information is received during transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV.

80. The apparatus of claim 65, wherein the at least one processor is further configured to: A second message is sent instructing the UAV to follow the planned route or return to the starting location of the UAV based on the geographic location of the UAV indicating that the UAV is not on the planned route.

81. The apparatus of claim 65, wherein the UAV driving mode is one of: UAV autopilot mode, Network-controlled driving modes, UAV controller driving mode, or A combination of at least two of the UAV autonomous driving mode, the network controlled driving mode and the UAV controller driving mode.

82. The apparatus of claim 65, wherein the at least one processor is further configured to: Route information is sent based on the UAV driving mode being a network-controlled driving mode, the route information indicating the entirety of the planned route based on the destination location of the UAV being within the cell of the device.

83. The apparatus of claim 65, wherein the apparatus is a network entity, and wherein the at least one processor is further configured to: Route information is sent based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of the planned route based on a destination location of the UAV being within a cell of a different network entity.

84. The apparatus of claim 65, wherein the apparatus is a network entity, and wherein the at least one processor is further configured to: Calculated route information originating from different network entities is sent based on the UAV driving mode being a network-controlled driving mode.

85. The apparatus of claim 65, wherein the apparatus is a network entity, and wherein the at least one processor is further configured to: receiving, in a radio resource control (RRC) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; and An indication of approval or rejection of the planned route from a different network entity is sent, the planned route being associated with the route information calculated by the UAV.

86. The apparatus of claim 65, wherein the at least one processor is further configured to: receiving, in a radio resource control (RRC) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; transmitting an indication of a rejection of the planned route associated with the route information calculated by the UAV; and Based on the refusal to send route information of the UAV autonomous driving mode or network-controlled driving mode.

87. The apparatus of claim 65, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: receiving a request to switch a driving mode of the UAV to a network-controlled driving mode or a UAV autonomous driving mode based on a change in a characteristic of a command and control (C2) link between the UAV and a UAV controller; and A different UAV driving mode is sent in response to the request, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

88. The apparatus of claim 87, wherein the change in the characteristic of the C2 link is a loss of connectivity of the C2 link.

89. The apparatus of claim 87, wherein the change in the characteristic of the C2 link is a reference signal received power (RSRP) of a reference signal carried in the C2 link being below a threshold.

90. The apparatus of claim 87, wherein the request indicates the change in the characteristic of the C2 link.

91. An apparatus according to claim 90, wherein the request also indicates a preferred driving mode of the UAV.

92. The apparatus of claim 65, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: A different UAV driving mode is sent in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV automatic driving mode, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

93. The apparatus of claim 65, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: receiving a report indicating measurements associated with a command and control (C2) link between the UAV and a UAV controller; and A different UAV driving mode is sent in response to the report.

94. The apparatus of claim 65, wherein the apparatus is a base station.

95. A method for wireless communication at a network entity, the method comprising: receiving unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a user equipment (UE), the UE being the UAV; as well as A message is sent including a UAV driving mode, wherein the UAV driving mode indicates that the UE is flying on a planned route.

96. The method of claim 95, further comprising: Receive a second message indicating to the network entity at least one driving mode supported by the UAV, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV.

97. A method according to claim 96, wherein the second message also indicates a preferred driving mode of the UAV, wherein the UAV driving mode is the preferred driving mode of the UAV.

98. The method of claim 96, further comprising: Route information is received based on that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

99. The method of claim 96, further comprising: Route information is sent based on the UAV driving mode being a network-controlled driving mode, and the route information is further sent based on a destination location of the UAV or an expected departure time of the UAV from an application server that communicates with the network entity.

100. The method of claim 95, further comprising: Route information is sent based on the fact that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: the routing path of the UAV, the position-related allowed speed of the UAV, the position-related altitude of the UAV, the expected departure time of the UAV, the expected arrival time of the UAV, and the location of obstacles in the planned route of the UAV.

101. The method of claim 95, wherein based on the UAV driving mode being a network-controlled driving mode, the planned route is associated with a route path accuracy, and the route path accuracy is at the meter level, street level, block level, or network entity level.

102. A method according to claim 95, wherein the UAV driving mode is based at least in part on one or more of the UAV destination, the quality of service (QoS) of the uplink communication or the downlink communication, the geometry of the planned route, and the UAV traffic in the planned route.

103. The method of claim 95, further comprising: receiving route information calculated by the UAV based on the UAV driving mode being the UAV autonomous driving mode; as well as An indication of approval or rejection of the planned route is sent in association with the route information calculated by the UAV.

104. A method according to claim 103, wherein the route information calculated by the UAV includes one or more of the following: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

105. The method of claim 103, further comprising: Route information is sent based on the UAV driving mode and based on the refusal to switch to a network-controlled driving mode.

106. The method of claim 95, further comprising: The geographic location of the UAV is periodically received during transportation of the UAV on the planned route.

107. The method of claim 95, further comprising: Measurements of a reference signal are received during transit of the UAV on the planned route, the measurements indicating a geographic location of the UAV.

108. The method of claim 95, further comprising: A reference signal is received during transportation of the UAV on the planned route, the reference signal indicating the geographic location of the UAV.

109. The method of claim 95, further comprising: Cell information is received during transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV.

110. The method of claim 95, further comprising: A second message is sent instructing the UAV to follow the planned route or return to the starting location of the UAV based on the geographic location of the UAV indicating that the UAV is not on the planned route.

111. The method of claim 95, wherein the UAV driving mode is one of: UAV autopilot mode, Network-controlled driving modes, UAV controller driving mode, or A combination of at least two of the UAV autonomous driving mode, the network controlled driving mode and the UAV controller driving mode.

112. The method of claim 95, further comprising: Route information is sent based on the UAV driving mode being a network-controlled driving mode, the route information indicating the entirety of the planned route based on the destination location of the UAV being within a cell of the network entity.

113. The method of claim 95, further comprising: Route information is sent based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of the planned route based on a destination location of the UAV being within a cell of a different network entity.

114. The method of claim 95, further comprising: Calculated route information originating from different network entities is sent based on the UAV driving mode being a network-controlled driving mode.

115. The method of claim 95, further comprising: receiving, in a radio resource control (RRC) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; as well as An indication of approval or rejection of the planned route from a different network entity is sent, the planned route being associated with the route information calculated by the UAV.

116. The method of claim 95, further comprising: receiving, in a radio resource control (RRC) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; sending an indication of a rejection of the planned route associated with the route information calculated by the UAV; as well as Based on the refusal to send route information of the UAV autonomous driving mode or network-controlled driving mode.

117. The method of claim 95, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: receiving a request to switch a driving mode of the UAV to a network-controlled driving mode or a UAV autonomous driving mode based on a change in a characteristic of a command and control (C2) link between the UAV and a UAV controller; as well as A different UAV driving mode is sent in response to the request, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

118. The method of claim 117, wherein the change in the characteristic of the C2 link is a loss of connectivity of the C2 link.

119. The method of claim 117, wherein the change in the characteristic of the C2 link is that a reference signal received power (RSRP) of a reference signal carried in the C2 link is lower than a threshold.

120. The method of claim 117, wherein the request indicates the change in the characteristic of the C2 link.

121. A method according to claim 120, wherein the request also indicates a preferred driving mode of the UAV.

122. The method of claim 95, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: A different UAV driving mode is sent in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV automatic driving mode, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

123. The method of claim 95, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: receiving a report indicating measurements associated with a command and control (C2) link between the UAV and a UAV controller; as well as A different UAV driving mode is sent in response to the report.

124. The method of claim 95, wherein the network entity is a base station.

125. An apparatus for wireless communication, the apparatus comprising: means for receiving unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a user equipment (UE), the UE being a UAV; and Means for sending a message including a UAV driving mode indicating that the UE is flying on a planned route.

126. A non-transitory computer readable medium storing computer executable code, which, when executed by a processor, causes the processor to: receiving unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a user equipment (UE), the UE being the UAV; and A message is sent including a UAV driving mode, wherein the UAV driving mode indicates that the UE is flying on a planned route.

127. An apparatus for wireless communication, the apparatus comprising: Memory; and at least one processor coupled to the memory and configured to: Sending an unmanned aerial vehicle (UAV) supporting uplink and downlink communications with a network entity data; as well as A message including a UAV driving mode is received from the network entity, the UAV driving mode indicating that the device is to fly on a planned route, the device being a UAV.

128. The apparatus of claim 127, wherein the at least one processor is further configured to: Send a second message indicating to the network entity at least one driving mode supported by the UAV, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV.

129. An apparatus according to claim 128, wherein the second message also indicates a preferred driving mode of the UAV, wherein the UAV driving mode is the preferred driving mode of the UAV.

130. The apparatus of claim 128 or 129, wherein the at least one processor is further configured to: Route information is sent to the network entity based on the fact that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: the departure time of the UAV, the departure three-dimensional (3D) position of the UAV, the destination 3D position of the UAV, the arrival time of the UAV, the UAV flight capability, the UAV operator license, the UAV mission type, the position of obstacles in the planned route of the UAV, the real-time UAV 3D position, the UAV heading, the UAV speed, the UAV battery status and the UAV characteristics.

131. The apparatus of any one of claims 128 to 129, wherein the at least one processor is further configured to: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, and the route information is further received based on a destination location of the UAV or an expected departure time of the UAV from an application server that communicates with the network entity.

132. The apparatus of any one of claims 127 to 129, wherein the at least one processor is further configured to: Route information is received from the network entity based on the fact that the UAV driving mode is a network-controlled driving mode, the route information including one or more of the following: a routing path of the UAV, a position-related allowed speed of the UAV, a position-related allowed altitude of the UAV, an expected departure time of the UAV, an expected arrival time of the UAV, and locations of obstacles in the planned route of the UAV.

133. An apparatus according to any one of claims 127 to 132, wherein based on the fact that the UAV driving mode is a network-controlled driving mode, the planned route is associated with a route path accuracy, and the route path accuracy is at the meter level, street level, block level or network entity level.

134. An apparatus according to any one of claims 127 to 133, wherein the UAV driving mode is based at least in part on one or more of a UAV destination, a quality of service (QoS) of the uplink communication or the downlink communication, a geometry of the planned route, and UAV traffic in the planned route.

135. The apparatus of any one of claims 127 to 129, wherein the at least one processor is further configured to: sending the UAV calculated route information to the network entity based on the UAV driving mode being the UAV autonomous driving mode; and An indication of approval or rejection of the planned route associated with the route information calculated by the UAV is received from the network entity.

136. An apparatus according to claim 135, wherein the route information calculated by the UAV includes one or more of the following: UAV position, departure time of the UAV, departure 3D position of the UAV, destination 3D position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

137. The apparatus of claim 135 or 136, wherein the at least one processor is further configured to: Receiving route information from the network entity based on the UAV driving mode based on the refusal to switch to the network-controlled driving mode.

138. The apparatus of any one of claims 127 to 129 and 135 to 137, wherein the at least one processor is further configured to: The geographic location of the UAV is periodically transmitted to the network entity during transportation of the UAV on the planned route.

139. The apparatus of any one of claims 127 to 129 and 135 to 138, wherein the at least one processor is further configured to: Measurements of a reference signal are sent to the network entity during transit of the UAV on the planned route, the measurements indicating a geographic location of the UAV.

140. The apparatus of any one of claims 127 to 129 and 135 to 139, wherein the at least one processor is further configured to: A reference signal is sent to the network entity during transportation of the UAV on the planned route, the reference signal indicating the geographic location of the UAV.

141. The apparatus of any one of claims 127 to 129 and 135 to 140, wherein the at least one processor is further configured to: The cell information is sent to the network entity during transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV.

142. The apparatus of any one of claims 127 to 129 and 135 to 141, wherein the at least one processor is further configured to: A second message is received based on the geographic location of the UAV indicating that the UAV is not on the planned route and instructing the UAV to follow the planned route or return to the starting location of the UAV.

143. The apparatus of any one of claims 127 to 142, wherein the UAV driving mode is one of: UAV autopilot mode, Network-controlled driving modes, UAV controller driving mode, or A combination of at least two of the UAV autonomous driving mode, the network controlled driving mode and the UAV controller driving mode.

144. The apparatus of any one of claims 127 to 134 and 143, wherein the at least one processor is further configured to: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating an entirety of the planned route based on a destination location of the UAV being within a cell of the network entity.

145. The apparatus of any one of claims 127 to 134 and 143, wherein the at least one processor is further configured to: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of the planned route based on a destination location of the UAV being within a cell of a different network entity.

146. The apparatus of any one of claims 127 to 134 and 143, wherein the at least one processor is further configured to: Calculated route information originating from a different network entity is received from the network entity based on the UAV driving mode being a network-controlled driving mode.

147. The apparatus of any one of claims 127 to 129 and 135 to 143, wherein the at least one processor is further configured to: sending the UAV calculated route information to the network entity in a radio resource control (RRC) message based on the UAV driving mode being the UAV autonomous driving mode; and An indication of approval or rejection of the planned route originating from the network entity or a different network entity is received from the network entity, the planned route being associated with route information calculated by the UAV.

148. The apparatus of any one of claims 127 to 129 and 135 to 143, wherein the at least one processor is further configured to: sending the UAV calculated route information to different network entities in a non-access stratum (NAS) message based on the UAV driving mode being the UAV autonomous driving mode; and An indication of approval or rejection of the planned route associated with the route information calculated by the UAV is received from the different network entity.

149. The apparatus of any one of claims 127 to 129, 135 to 143, 147, and 148, wherein the at least one processor is further configured to: sending, in a radio resource control (RRC) message or a non-access stratum (NAS) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; receiving an indication of a rejection of the planned route associated with the route information calculated by the UAV; as well as Based on the refusal to receive route information of the UAV autonomous driving mode or network-controlled driving mode.

150. The apparatus of any one of claims 127 to 129 and 143, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: sending a request to the network entity to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode based on a change in a characteristic of a command and control (C2) link between the UAV and a UAV controller; and A different UAV driving mode is received from the network entity in response to the request, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

151. The apparatus of claim 150, wherein the change in the characteristic of the C2 link is a loss of connectivity of the C2 link.

152. The apparatus of claim 150, wherein the change in the characteristic of the C2 link is a reference signal received power (RSRP) of a reference signal carried in the C2 link being below a threshold.

153. The apparatus of any one of claims 150 to 152, wherein the request indicates the change in the characteristic of the C2 link.

154. An apparatus according to any one of claims 150 to 153, wherein the request also indicates a preferred driving mode of the UAV.

155. The apparatus of any one of claims 127 to 129 and 143, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: A different UAV driving mode is received from the network entity in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

156. The apparatus of any one of claims 127 to 129 and 143, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: sending a report indicating measurements associated with a command and control (C2) link between the UAV and a UAV controller; and A different UAV driving mode is received from the network entity in response to the report.

157. The apparatus of any one of claims 127 to 156, wherein the network entity is a base station.

158. A method of wireless communication at a user equipment (UE), the method comprising: transmitting unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with network entities; as well as A message including a UAV driving mode is received from the network entity, the UAV driving mode indicating that the UE is flying on a planned route, the UE being a UAV.

159. The method of claim 158, further comprising: Send a second message indicating to the network entity at least one driving mode supported by the UAV, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV.

160. A method according to claim 159, wherein the second message also indicates a preferred driving mode of the UAV, wherein the UAV driving mode is the preferred driving mode of the UAV.

161. The method of any one of claims 159 to 160, further comprising: Route information is sent to the network entity based on the fact that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

162. The method of any one of claims 159 to 160, further comprising: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, and the route information is further received based on a destination location of the UAV or an expected departure time of the UAV from an application server that communicates with the network entity.

163. The method of any one of claims 158 to 160, further comprising: Route information is received from the network entity based on the fact that the UAV driving mode is a network-controlled driving mode, the route information including one or more of: a routing path of the UAV, a position-related allowed speed of the UAV, a position-related altitude of the UAV, an expected departure time of the UAV, an expected arrival time of the UAV, and locations of obstacles in the planned route of the UAV.

164. A method according to any one of claims 158 to 163, wherein based on the fact that the UAV driving mode is a network-controlled driving mode, the planned route is associated with a route path accuracy, and the route path accuracy is at the meter level, street level, block level or network entity level.

165. A method according to any one of claims 158 to 164, wherein the UAV driving mode is based at least in part on one or more of a UAV destination, a quality of service (QoS) of the uplink communication or the downlink communication, a geometry of the planned route, and UAV traffic in the planned route.

166. The method of any one of claims 158 to 160, further comprising: sending, to the network entity, route information calculated by the UAV based on the UAV driving mode being the UAV autonomous driving mode; as well as An indication of approval or rejection of the planned route associated with the route information calculated by the UAV is received from the network entity.

167. A method according to claim 166, wherein the route information calculated by the UAV includes one or more of the following: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

168. The method of claim 166 or 167, further comprising: Receiving route information from the network entity based on the UAV driving mode based on the refusal to switch to the network-controlled driving mode.

169. The method of any one of claims 158 to 160 and 166 to 168, further comprising: The geographic location of the UAV is periodically transmitted to the network entity during transportation of the UAV on the planned route.

170. The method of any one of claims 158 to 160 and 166 to 169, further comprising: Measurements of a reference signal are sent to the network entity during transit of the UAV on the planned route, the measurements indicating a geographic location of the UAV.

171. The method of any one of claims 158 to 160 and 166 to 170, further comprising: A reference signal is sent to the network entity during transportation of the UAV on the planned route, the reference signal indicating the geographic location of the UAV.

172. The method of any one of claims 158 to 160 and 166 to 171, further comprising: The cell information is sent to the network entity during transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV.

173. The method of any one of claims 158 to 160 and 166 to 172, further comprising: A second message is received based on the geographic location of the UAV indicating that the UAV is not on the planned route and instructing the UAV to follow the planned route or return to the starting location of the UAV.

174. The method of any one of claims 158 to 173, wherein the UAV driving mode is one of: UAV autopilot mode, Network-controlled driving modes, UAV controller driving mode, or A combination of at least two of the UAV autonomous driving mode, the network controlled driving mode and the UAV controller driving mode.

175. The method of any one of claims 158 to 165 and 174, further comprising: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating an entirety of the planned route based on a destination location of the UAV being within a cell of the network entity.

176. The method of any one of claims 158 to 165 and 174, further comprising: Route information is received from the network entity based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of the planned route based on a destination location of the UAV being within a cell of a different network entity.

177. The method of any one of claims 158 to 165 and 174, further comprising: Calculated route information originating from a different network entity is received from the network entity based on the UAV driving mode being a network-controlled driving mode.

178. The method of any one of claims 158 to 160 and 166 to 174, further comprising: sending, to the network entity, route information calculated by the UAV in a radio resource control (RRC) message based on the UAV driving mode being a UAV autonomous driving mode; as well as An indication of approval or rejection of the planned route originating from a different network entity is received from the network entity, the planned route being associated with route information calculated by the UAV.

179. The method of any one of claims 158 to 160 and 166 to 174, further comprising: sending, in a non-access stratum (NAS) message, route information calculated by the UAV to different network entities based on the UAV driving mode being a UAV autonomous driving mode; as well as An indication of approval or rejection of the planned route associated with the route information calculated by the UAV is received from the different network entity.

180. The method of any one of claims 158 to 160, 166 to 174, 178 and 179, further comprising: sending, in a radio resource control (RRC) message or a non-access stratum (NAS) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; receiving an indication of a rejection of the planned route associated with the route information calculated by the UAV; as well as Based on the refusal to receive route information of the UAV autonomous driving mode or network-controlled driving mode.

181. The method of any one of claims 158 to 160 and 174, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: sending a request to the network entity to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode based on a change in a characteristic of a command and control (C2) link between the UAV and a UAV controller; as well as A different UAV driving mode is received from the network entity in response to the request, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

182. The method of claim 181, wherein the change in the characteristic of the C2 link is a loss of connectivity of the C2 link.

183. The method of claim 181, wherein the change in the characteristic of the C2 link is that a reference signal received power (RSRP) of a reference signal carried in the C2 link is below a threshold.

184. A method according to any one of claims 181 to 183, wherein the request indicates the change in the characteristic of the C2 link.

185. A method according to any one of claims 181 to 184, wherein the request also indicates a preferred driving mode of the UAV.

186. The method of any one of claims 158 to 160 and 174, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: A different UAV driving mode is received from the network entity in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV autonomous driving mode, the different UAV driving mode being one of the network-controlled driving mode or the UAV autonomous driving mode.

187. The method of any one of claims 158 to 160 and 174, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: sending a report indicative of measurements associated with a command and control (C2) link between the UAV and a UAV controller; as well as A different UAV driving mode is received from the network entity in response to the report.

188. The method of any one of claims 158 to 187, wherein the network entity is a base station.

189. An apparatus for wireless communication, the apparatus comprising: means for transmitting unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a network entity; and Means for receiving a message from the network entity including a UAV driving mode, the UAV driving mode indicating that the device is to fly on a planned route, the device being a UAV.

190. A non-transitory computer readable medium storing computer executable code, which, when executed by a processor, causes the processor to: transmitting unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a network entity; and A message including a UAV driving mode is received from the network entity, the UAV driving mode indicating that a device is flying on a planned route, the device being a UAV.

191. An apparatus for wireless communication, the apparatus comprising: Memory; and at least one processor coupled to the memory and configured to: receiving unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a user equipment (UE), the UE being the UAV; as well as A message is sent including a UAV driving mode, wherein the UAV driving mode indicates that the UE is flying on a planned route.

192. The apparatus of claim 191, wherein the at least one processor is further configured to: A second message is received indicating a driving mode supported by at least one UAV, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV.

193. An apparatus according to claim 192, wherein the second message also indicates a preferred driving mode of the UAV, wherein the UAV driving mode is the preferred driving mode of the UAV.

194. The apparatus of any one of claims 192 to 193, wherein the at least one processor is further configured to: Route information is received based on that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

195. The apparatus of any one of claims 192 to 193, wherein the at least one processor is further configured to: Route information is sent based on the UAV driving mode being a network-controlled driving mode, and the route information is further sent based on the destination location of the UAV or the expected departure time of the UAV from an application server in communication with the device.

196. The apparatus of any one of claims 191 to 193, wherein the at least one processor is further configured to: Route information is sent based on the fact that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: the routing path of the UAV, the position-related allowed speed of the UAV, the position-related altitude of the UAV, the expected departure time of the UAV, the expected arrival time of the UAV, and the location of obstacles in the planned route of the UAV.

197. An apparatus according to any one of claims 191 to 196, wherein based on the fact that the UAV driving mode is a network-controlled driving mode, the planned route is associated with a route path accuracy, and the route path accuracy is at the meter level, street level, block level or network entity level.

198. An apparatus according to any one of claims 191 to 197, wherein the UAV driving mode is based at least in part on one or more of a UAV destination, a quality of service (QoS) of the uplink communication or the downlink communication, a geometry of the planned route, and UAV traffic in the planned route.

199. The apparatus of any one of claims 191 to 193, wherein the at least one processor is further configured to: receiving route information calculated by the UAV based on the UAV driving mode being the UAV autonomous driving mode; and An indication of approval or rejection of the planned route is sent in association with the route information calculated by the UAV.

200. An apparatus according to claim 199, wherein the route information calculated by the UAV includes one or more of the following: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

201. The apparatus of claim 199 or 200, wherein the at least one processor is further configured to: Route information is sent based on the UAV driving mode and based on the refusal to switch to a network-controlled driving mode.

202. The apparatus of any one of claims 191 to 193 and 199 to 201, wherein the at least one processor is further configured to: The geographic location of the UAV is periodically received during transportation of the UAV on the planned route.

203. The apparatus of any one of claims 191 to 193 and 199 to 202, wherein the at least one processor is further configured to: Measurements of a reference signal are received during transit of the UAV on the planned route, the measurements indicating a geographic location of the UAV.

204. The apparatus of any one of claims 191 to 193 and 199 to 203, wherein the at least one processor is further configured to: A reference signal is received during transportation of the UAV on the planned route, the reference signal indicating the geographic location of the UAV.

205. The apparatus of any one of claims 191 to 193 and 199 to 204, wherein the at least one processor is further configured to: Cell information is received during transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV.

206. The apparatus of any one of claims 191 to 193 and 199 to 205, wherein the at least one processor is further configured to: A second message is sent instructing the UAV to follow the planned route or return to the starting location of the UAV based on the geographic location of the UAV indicating that the UAV is not on the planned route.

207. The apparatus of any one of claims 191 to 206, wherein the UAV driving mode is one of: UAV autopilot mode, Network-controlled driving modes, UAV controller driving mode, or A combination of at least two of the UAV autonomous driving mode, the network controlled driving mode and the UAV controller driving mode.

208. The apparatus of any one of claims 191 to 198 and 207, wherein the at least one processor is further configured to: Route information is sent based on the UAV driving mode being a network-controlled driving mode, the route information indicating the entirety of the planned route based on the destination location of the UAV being within the cell of the device.

209. The apparatus of any one of claims 191 to 198 and 207, wherein the apparatus is a network entity, and wherein the at least one processor is further configured to: Route information is sent based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of the planned route based on a destination location of the UAV being within a cell of a different network entity.

210. The apparatus of any one of claims 191 to 198 and 207, wherein the apparatus is a network entity, and wherein the at least one processor is further configured to: Calculated route information originating from different network entities is sent based on the UAV driving mode being a network-controlled driving mode.

211. The apparatus of any one of claims 191 to 193 and 199 to 207, wherein the apparatus is a network entity, and wherein the at least one processor is further configured to: receiving, in a radio resource control (RRC) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; and An indication of approval or rejection of the planned route from a different network entity is sent, the planned route being associated with the route information calculated by the UAV.

212. The apparatus of any one of claims 191 to 193, 199 to 207, and 211, wherein the at least one processor is further configured to: receiving, in a radio resource control (RRC) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; transmitting an indication of a rejection of the planned route associated with the route information calculated by the UAV; and Based on the refusal to send route information of the UAV autonomous driving mode or network-controlled driving mode.

213. The apparatus of any one of claims 191 to 193 and 207, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: receiving a request to switch a driving mode of the UAV to a network-controlled driving mode or a UAV autonomous driving mode based on a change in a characteristic of a command and control (C2) link between the UAV and a UAV controller; and A different UAV driving mode is sent in response to the request, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

214. An apparatus according to claim 213, wherein the change in the characteristic of the C2 link is a loss of connectivity of the C2 link.

215. The apparatus of claim 213, wherein the change in the characteristic of the C2 link is a reference signal received power (RSRP) of a reference signal carried in the C2 link being below a threshold.

216. An apparatus according to any one of claims 213 to 215, wherein the request indicates the change in the characteristic of the C2 link.

217. An apparatus according to any one of claims 213 to 216, wherein the request also indicates a preferred driving mode of the UAV.

218. The apparatus of any one of claims 191 to 193 and 207, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: A different UAV driving mode is sent in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV automatic driving mode, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

219. The apparatus of any one of claims 191 to 193 and 207, wherein the UAV driving mode is a UAV controller driving mode, and wherein the at least one processor is further configured to: receiving a report indicating measurements associated with a command and control (C2) link between the UAV and a UAV controller; and A different UAV driving mode is sent in response to the report.

220. The apparatus of any one of claims 191 to 219, wherein the apparatus is a base station.

221. A method for wireless communication at a network entity, the method comprising: receiving unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a user equipment (UE), the UE being the UAV; as well as A message is sent including a UAV driving mode, wherein the UAV driving mode indicates that the UE is flying on a planned route.

222. The method of claim 221, further comprising: Receive a second message indicating to the network entity at least one driving mode supported by the UAV, wherein the UAV driving mode is based at least in part on the driving mode supported by the at least one UAV.

223. A method according to claim 222, wherein the second message also indicates a preferred driving mode of the UAV, wherein the UAV driving mode is the preferred driving mode of the UAV.

224. The method of claim 222 or 223, further comprising: Route information is received based on that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

225. The method of any one of claims 222 to 223, further comprising: Route information is sent based on the UAV driving mode being a network-controlled driving mode, and the route information is further sent based on a destination location of the UAV or an expected departure time of the UAV from an application server that communicates with the network entity.

226. The method of any one of claims 221 to 223, further comprising: Route information is sent based on the fact that the UAV driving mode is a network-controlled driving mode, and the route information includes one or more of the following items: the routing path of the UAV, the position-related allowed speed of the UAV, the position-related altitude of the UAV, the expected departure time of the UAV, the expected arrival time of the UAV, and the location of obstacles in the planned route of the UAV.

227. A method according to any one of claims 221 to 226, wherein based on the fact that the UAV driving mode is a network-controlled driving mode, the planned route is associated with a route path accuracy, and the route path accuracy is at the meter level, street level, block level or network entity level.

228. A method according to any one of claims 221 to 227, wherein the UAV driving mode is based at least in part on one or more of a UAV destination, a quality of service (QoS) of the uplink communication or the downlink communication, a geometry of the planned route, and UAV traffic in the planned route.

229. The method of any one of claims 221 to 223, further comprising: receiving route information calculated by the UAV based on the UAV driving mode being the UAV autonomous driving mode; as well as An indication of approval or rejection of the planned route is sent in association with the route information calculated by the UAV.

230. A method according to claim 229, wherein the route information calculated by the UAV includes one or more of the following: UAV position, departure time of the UAV, departure position of the UAV, destination position of the UAV, arrival time of the UAV, UAV flight capability, UAV operator license, UAV mission type, location of obstacles in the planned route of the UAV, real-time UAV three-dimensional (3D) position, UAV heading, UAV speed, UAV battery status and UAV characteristics.

231. The method of claim 229 or 230, further comprising: Route information is sent based on the UAV driving mode and based on the refusal to switch to a network-controlled driving mode.

232. The method of any one of claims 221 to 223 and 229 to 231, further comprising: The geographic location of the UAV is periodically received during transportation of the UAV on the planned route.

233. The method of any one of claims 221 to 223 and 229 to 232, further comprising: Measurements of a reference signal are received during transit of the UAV on the planned route, the measurements indicating a geographic location of the UAV.

234. The method of any one of claims 221 to 223 and 229 to 233, further comprising: A reference signal is received during transportation of the UAV on the planned route, the reference signal indicating the geographic location of the UAV.

235. The method of any one of claims 221 to 223 and 229 to 234, further comprising: Cell information is received during transportation of the UAV on the planned route, the cell information indicating the geographic location of the UAV.

236. The method of any one of claims 221 to 223 and 229 to 235, further comprising: A second message is sent instructing the UAV to follow the planned route or return to the starting location of the UAV based on the geographic location of the UAV indicating that the UAV is not on the planned route.

237. The method of any one of claims 221 to 236, wherein the UAV driving mode is one of: UAV autopilot mode, Network-controlled driving modes, UAV controller driving mode, or A combination of at least two of the UAV autonomous driving mode, the network controlled driving mode and the UAV controller driving mode.

238. The method of any one of claims 221 to 228 and 237, further comprising: Route information is sent based on the UAV driving mode being a network-controlled driving mode, the route information indicating the entirety of the planned route based on the destination location of the UAV being within a cell of the network entity.

239. The method of any one of claims 221 to 228 and 237, further comprising: Route information is sent based on the UAV driving mode being a network-controlled driving mode, the route information indicating a portion of the planned route based on a destination location of the UAV being within a cell of a different network entity.

240. The method of any one of claims 221 to 228 and 237, further comprising: Calculated route information originating from different network entities is sent based on the UAV driving mode being a network-controlled driving mode.

241. The method of any one of claims 221 to 223 and 229 to 237, further comprising: receiving, in a radio resource control (RRC) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; as well as An indication of approval or rejection of the planned route from a different network entity is sent, the planned route being associated with the route information calculated by the UAV.

242. The method of any one of claims 221 to 223, 229 to 237 and 241, further comprising: receiving, in a radio resource control (RRC) message, route information calculated by the UAV based on the UAV driving mode being a UAV autonomous driving mode; sending an indication of a rejection of the planned route associated with the route information calculated by the UAV; as well as Based on the refusal to send route information of the UAV autonomous driving mode or network-controlled driving mode.

243. The method of any one of claims 221 to 223 and 237, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: receiving a request to switch a driving mode of the UAV to a network-controlled driving mode or a UAV autonomous driving mode based on a change in a characteristic of a command and control (C2) link between the UAV and a UAV controller; as well as A different UAV driving mode is sent in response to the request, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

244. The method of claim 243, wherein the change in the characteristic of the C2 link is a loss of connectivity of the C2 link.

245. The method of claim 243, wherein the change in the characteristic of the C2 link is that a reference signal received power (RSRP) of a reference signal carried in the C2 link is below a threshold.

246. A method according to any one of claims 243 to 245, wherein the request indicates the change in the characteristic of the C2 link.

247. A method according to any one of claims 243 to 246, wherein the request also indicates a preferred driving mode of the UAV.

248. The method of any one of claims 221 to 223 and 237, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: A different UAV driving mode is sent in response to a UAV controller request to switch the UAV driving mode to a network-controlled driving mode or a UAV automatic driving mode, and the different UAV driving mode is one of the network-controlled driving mode or the UAV automatic driving mode.

249. The method of any one of claims 221 to 223 and 237, wherein the UAV driving mode is a UAV controller driving mode, and the method further comprises: receiving a report indicating measurements associated with a command and control (C2) link between the UAV and a UAV controller; as well as A different UAV driving mode is sent in response to the report.

250. The method of any one of claims 221 to 249, wherein the network entity is a base station.

251. An apparatus for wireless communication, the apparatus comprising: means for receiving unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a user equipment (UE), the UE being a UAV; and Means for sending a message including a UAV driving mode indicating that the UE is flying on a planned route.

252. A non-transitory computer readable medium storing computer executable code, which, when executed by a processor, causes the processor to: receiving unmanned aerial vehicle (UAV) data supporting uplink and downlink communications with a user equipment (UE), the UE being the UAV; and A message is sent including a UAV driving mode, wherein the UAV driving mode indicates that the UE is flying on a planned route.

Images