Mechanism for unmanned vehicle authorization to operate on cellular network

Abstract

A mechanism for authorization of an unmanned vehicle to operate on a cellular network is disclosed. Methods, systems, and devices for wireless communication are described. A wireless network may receive a message from a wireless device coupled with an air vehicle. The message may include a network identifier, an air identifier, and operational information about the air vehicle. The wireless network may send a message to an air function management system to request the air function management system to authenticate an identity of the air vehicle. The wireless network may also request the air function management system to approve a flight path of the air vehicle. The wireless network may establish a data session with the wireless device based on authentication of the air vehicle and approval of the flight path.

Description

[0001] This application is a divisional application of the Chinese invention patent application with an application date of February 23, 2021, application number 202180015243.0 (international application number PCT / US2021 / 019282), and invention name “Mechanism for authorizing unmanned vehicles to operate on cellular networks”.

[0002] Cross-references

[0003] This patent application claims the benefit of Greek Patent Application No. 20200100097, filed by FACCIN et al. on February 24, 2020, entitled "AMECHANISM FORUNMANNED VEHICLE AUTHORIZATION FOR OPERATION OVER CELLULAR NETWORKS", which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0004] The following relates generally to wireless communications, and more particularly to authorizing unmanned vehicles to operate in a network. Background Art

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may use various technologies, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform extended orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting the communication of multiple communication devices, which may be referred to as user equipment (UE) in addition.

[0006] In some cases, the UE may include or be coupled to an unmanned aerial vehicle (UAV). A wireless communication system may provide services to support aerial operations of the UAV via a connection between the UE and the wireless communication system. However, there are challenges in using a wireless communication system to support aerial operations of the UAV. Summary of the invention

[0007] The described technology relates to improved methods, systems, devices and apparatuses that support authorization of unmanned vehicles to operate in a network. Operations for authenticating unmanned aerial vehicles (UAVs) and authorizing flight operations of UAVs, which may be referred to as UAV service provider (USS) authentication and authorization (USAA) procedures, may be combined with procedures for accessing wireless networks. In some examples, USAA operations may be combined with registration procedures for registering with a wireless network. In some examples, USAA operations may be combined with data session establishment procedures for establishing a data connection using a wireless network. In some examples, USAA operations may be split between registration procedures and data session establishment procedures. In some examples, USAA operations may be combined with attachment procedures for registering with a wireless network and establishing a data session therewith.

[0008] A method of wirelessly communicating at a network is described. The method may include: receiving a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establishing a control plane connection with the wireless device based at least in part on the network identifier; sending a request in the control plane to an air function management system to verify the air vehicle based on the air identifier, wherein the request includes the air identifier and the operational information; receiving a response in the control plane from the air function management system, the response including approval of a flight path for the air vehicle; and establishing a data session for the wireless device based on the approval of the flight path.

[0009] An apparatus for wireless communication at a network is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establish a control plane connection with the wireless device based at least in part on the network identifier; send a request in the control plane to an air function management system to verify the air vehicle based on the air identifier, wherein the request includes the air identifier and the operational information; receive a response in the control plane from the air function management system, the response including approval of a flight path for the air vehicle; and establish a data session for the wireless device based on the approval of the flight path.

[0010] Another apparatus for wireless communication at a network is described. The apparatus may include means for: receiving a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establishing a control plane connection with the wireless device based at least in part on the network identifier; sending a request in the control plane to an air function management system to verify the air vehicle based on the air identifier, wherein the request includes the air identifier and the operational information; receiving a response in the control plane from the air function management system, the response including approval of a flight path for the air vehicle; and establishing a data session for the wireless device based on the approval of the flight path.

[0011] A non-transitory computer-readable medium storing code for wireless communication at a network is described. The code may include instructions executable by a processor to perform the following operations: receiving a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establishing a control plane connection with the wireless device based at least in part on the network identifier; sending a request to an air function management system in the control plane to verify the air vehicle based on the air identifier, wherein the request includes the air identifier and the operational information; receiving a response from the air function management system in the control plane, the response including approval of a flight path for the air vehicle; and establishing a data session for the wireless device based on the approval of the flight path.

[0012] Some examples of methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining an identity of the air functionality management system based on the air identifier.

[0013] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for matching the airborne identifier with an entry in an airborne identifier list based on receiving the message, and initiating a procedure for verifying the airborne vehicle based on the match.

[0014] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for verifying, based on the message, that the wireless device may have a subscription with the network, determining, based on the subscription, that the wireless device may be coupled with the air vehicle, and determining, based on the air identifier, that a procedure for verifying the air vehicle may be performed before the data session for the wireless device may be established.

[0015] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: transmitting a second message to the wireless device, the second message indicating that the procedure for verifying the air vehicle can be performed before the data session can be established and is configured to accept registration of the wireless device, wherein the control plane connection can be established based on transmitting the second message.

[0016] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for: assigning a state to the wireless device in the control plane based on the air identifier, wherein user plane data addressed to the wireless device may be blocked when the state may be assigned to the wireless device; and removing the state when establishing the data session.

[0017] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the operational information includes an identity of an operator, characteristics of the air vehicle, instructions for controllers for the air vehicle, the flight path, or any combination thereof.

[0018] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: transmitting a second message to the wireless device based on establishing the control plane connection, the second message being configured to request information for verifying the air vehicle; and receiving the air identifier of the air vehicle and the operational information about the air vehicle based on the second message.

[0019] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for: receiving a second response from the airborne functional management system based on sending the request, the second response indicating a positive authentication of the air vehicle and being received before the response; and transmitting a second message to the wireless device, the second message being configured to indicate to the wireless device a positive authentication of the air vehicle based on receiving the second response.

[0020] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for the following actions: receiving a third message from the wireless device based on transmitting the second message, the third message being configured to request establishment of the data session.

[0021] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: sending a second request to the airborne functional management system to authorize the flight path based on the second message, wherein the response indicating approval of the flight path may be received based on sending the second request.

[0022] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the second message includes the air identifier of the air vehicle, the operational information about the air vehicle, or both.

[0023] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for generating a traffic filter for communications with the wireless device based on receiving the response indicating approval of the flight path, wherein an exclusive communication path between the wireless device and a controller for the air vehicle may be established based on the traffic filter.

[0024] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: receiving a command for the air vehicle from a controller for the air vehicle in the data plane based on establishing the data session, and transmitting the command to the air vehicle in the data plane.

[0025] A method of wirelessly communicating at an airborne functional management system is described. The method may include: receiving a request from a network to verify an air vehicle coupled to a wireless device, the request including an airborne identifier of the air vehicle and operational information about the air vehicle; verifying the identity of the air vehicle based on the airborne identifier and the operational information; sending a first response to the network including a positive authentication of the air vehicle, wherein a procedure for establishing a data session is initiated between the network and the wireless device based on the first response; receiving a second request from the network to authorize a flight path for the air vehicle based on sending the first response; and sending a second response to the network including approval of the flight path based on the second request.

[0026] An apparatus for wireless communication at an airborne functional management system is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a request from a network to verify an air vehicle coupled to a wireless device, the request including an airborne identifier of the air vehicle and operational information about the air vehicle; verify the identity of the air vehicle based on the airborne identifier and the operational information; send a first response to the network including a positive authentication of the air vehicle, wherein a procedure for establishing a data session is initiated between the network and the wireless device based on the first response; receive a second request from the network to authorize a flight path for the air vehicle based on sending the first response; and send a second response to the network including approval of the flight path based on the second request.

[0027] An apparatus for wireless communication at an airborne functional management system is described. The apparatus may include means for: receiving a request from a network to verify an air vehicle coupled to a wireless device, the request including an airborne identifier of the air vehicle and operational information about the air vehicle; verifying the identity of the air vehicle based on the airborne identifier and the operational information; sending a first response to the network including a positive authentication of the air vehicle, wherein a procedure for establishing a data session is initiated between the network and the wireless device based on the first response; receiving a second request from the network to authorize a flight path for the air vehicle based on sending the first response; and sending a second response to the network including approval of the flight path based on the second request.

[0028] A non-transitory computer-readable medium storing code for wireless communication at an air function management system is described. The code may include instructions executable by a processor to perform the following operations: receiving a request from a network to verify an air vehicle coupled to a wireless device, the request including an air identifier of the air vehicle and operational information about the air vehicle; verifying the identity of the air vehicle based on the air identifier and the operational information; sending a first response to the network including a positive authentication of the air vehicle, wherein a procedure for establishing a data session is initiated between the network and the wireless device based on the first response; receiving a second request from the network to authorize a flight path for the air vehicle based on sending the first response; and sending a second response to the network including approval of the flight path based on the second request.

[0029] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for verifying the authenticity of the request to verify the air vehicle.

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the request includes a first set of credentials for the air vehicle, and wherein the authenticity of the request is verifiable based on the first set of credentials.

[0031] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: identifying second operational information about the air vehicle and a second air identifier that may be stored at the air functional management system based on receiving the request to verify the air vehicle.

[0032] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, verifying the identity of the air vehicle may include operations, features, apparatuses, or instructions for comparing the operational information with the second operational information and comparing the air identifier with the second air identifier, wherein the identity of the air vehicle may be authenticated based on the operational information matching the second operational information and the air identifier matching the second air identifier.

[0033] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, verifying the identity of the air vehicle may include operations, features, apparatus, or instructions for sending the air identifier and the operational information to a flight control system, and receiving a third response from the flight control system, the third response including an affirmative authentication of the air vehicle and received before sending the first response.

[0034] A method for wireless communication at a wireless device coupled to an air vehicle is described. The method may include: transmitting a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establishing a control plane connection with the network based on the network identifier, wherein a request to verify the air vehicle based on the air identifier is sent to an air function management system; receiving a second message from the network in the control plane indicating approval of a flight path for the air vehicle, the second message being configured to trigger establishment of a data session between the wireless device and the network; and establishing the data session with the network based on the second message.

[0035] An apparatus for wireless communication at a wireless device coupled to an air vehicle is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: transmit a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establish a control plane connection with the network based on the network identifier, wherein a request to verify the air vehicle based on the air identifier is sent to an air function management system; receive a second message from the network in the control plane indicating approval of a flight path for the air vehicle, the second message being configured to trigger establishment of a data session between the wireless device and the network; and establish the data session with the network based on the second message.

[0036] Another apparatus for wireless communication at a wireless device coupled to an air vehicle is described. The apparatus may include means for: transmitting a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establishing a control plane connection with the network based on the network identifier, wherein a request to verify the air vehicle based on the air identifier is sent to an air function management system; receiving a second message from the network in the control plane indicating approval of a flight path for the air vehicle, the second message being configured to trigger establishment of a data session between the wireless device and the network; and establishing the data session with the network based on the second message.

[0037] A non-transitory computer-readable medium storing code for wireless communication at a wireless device coupled to an air vehicle is described. The code may include instructions executable by a processor to perform the following operations: transmitting a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establishing a control plane connection with the network based on the network identifier, wherein a request to verify the air vehicle based on the air identifier is sent to an air function management system; receiving a second message from the network in the control plane indicating approval of a flight path for the air vehicle, the second message being configured to trigger establishment of a data session between the wireless device and the network; and establishing the data session with the network based on the second message.

[0038] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: receiving a third message from the network in the control plane based on the request sent to the air function management system, the third message indicating a positive authentication of the air vehicle and being received before the second message; and transmitting a fourth message to the network in the control plane based on receiving the third message, the fourth message being configured to request establishment of the data session and being transmitted before the second message.

[0039] A method of wirelessly communicating at a network is described. The method may include: receiving a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the message is configured to establish a control plane connection and a data session with the network; determining that the wireless device is coupled to the air vehicle based on the network identifier being associated with an air subscription; sending a request to verify the air vehicle to an air function management system based on the determination, wherein the request includes the air identifier and the operational information; receiving a response from the air function management system, the response including an affirmative authentication of the air vehicle and an approval of a flight path for the air vehicle; and establishing a data session for the wireless device based on the affirmative authentication of the air vehicle and the approval of the flight path.

[0040] An apparatus for wireless communication at a network is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the message is configured to establish a control plane connection and a data session with the network; determine that the wireless device is coupled to the air vehicle based on the network identifier being associated with an air subscription; send a request to verify the air vehicle to an air function management system based on the determination, wherein the request includes the air identifier and the operational information; receive a response from the air function management system, the response including an affirmative authentication of the air vehicle and an approval of a flight path for the air vehicle; and establish a data session for the wireless device based on the affirmative authentication of the air vehicle and the approval of the flight path.

[0041] Another apparatus for wireless communication at a network is described. The apparatus may include means for: receiving a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the message is configured to establish a control plane connection and a data session with the network; determining that the wireless device is coupled to the air vehicle based on the network identifier being associated with an air subscription; sending a request to verify the air vehicle to an air function management system based on the determination, wherein the request includes the air identifier and the operational information; receiving a response from the air function management system, the response including an affirmative authentication of the air vehicle and an approval of a flight path for the air vehicle; and establishing a data session for the wireless device based on the affirmative authentication of the air vehicle and the approval of the flight path.

[0042] A non-transitory computer-readable medium storing code for wireless communication at a network is described. The code may include instructions executable by a processor to perform the following operations: receiving a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the message is configured to establish a control plane connection and a data session with the network; determining that the wireless device is coupled to the air vehicle based on the network identifier being associated with an air subscription; sending a request to verify the air vehicle to an air function management system based on the determination, wherein the request includes the air identifier and the operational information; receiving a response from the air function management system, the response including an affirmative authentication of the air vehicle and an approval of a flight path for the air vehicle; and establishing a data session for the wireless device based on the affirmative authentication of the air vehicle and the approval of the flight path.

[0043] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying the air-capability management system based on the air-identifier.

[0044] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: based on receiving the response from the airborne functional management system, transmitting a second message to the wireless device, the second message including a positive authentication of the air vehicle and approval of the flight path and configured to trigger establishment of the data session.

[0045] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for: identifying an access point for routing commands between the wireless device and a controller for the air vehicle based on the message; releasing the data session based on identifying the access point; and establishing a second data session based on the access point, wherein an exclusive communication path may be established between the wireless device and the controller via the access point.

[0046] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for generating a traffic filter for communicating with the wireless device based on establishing the data session, wherein an exclusive communication path between the wireless device and a controller for the air vehicle may be established based on the traffic filter.

[0047] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for: verifying the authenticity of the response received from the airborne functional management system; storing configuration information for the air vehicle based on verifying the authenticity; and transmitting a second message to the wireless device based on verifying the authenticity of the response, the second message including a positive authentication of the air vehicle and approval of the flight path and configured to trigger establishment of the data session.

[0048] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: sending a second message to the radio access network based on receiving the response from the air functionality management system, the second message including information for supporting a radio connection for the air vehicle.

[0049] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the message includes a first indication of an access point providing air service and a configurable parameter set including the air identifier, the operational information about the air vehicle, and a second indication of a controller for the air vehicle.

[0050] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the first indication of the access point may be included in an Evolved Packet System (EPS) Session Management (ESM) container and the configurable parameter set may be included in a Protocol Configuration Option (PCO) field.

[0051] A method of wirelessly communicating at an airborne functional management system is described. The method may include: receiving a request from a network to verify an air vehicle coupled to a wireless device while a procedure for establishing a data session is being performed between the network and the wireless device, the request including an airborne identifier of the airborne vehicle and operational information about the airborne vehicle; verifying the identity of the airborne vehicle and a flight path of the airborne vehicle based on the airborne identifier and the operational information included in the request; and sending a response to the network based on the verification, the response including an affirmative authentication of the airborne vehicle and approval of the flight path.

[0052] An apparatus for wireless communication at an airborne functional management system is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a request from a network to verify an air vehicle coupled to a wireless device while a procedure for establishing a data session is being executed between the network and the wireless device, the request including an airborne identifier of the airborne vehicle and operational information about the airborne vehicle; verify the identity of the airborne vehicle and the flight path of the airborne vehicle based on the airborne identifier and the operational information included in the request; and send a response to the network based on the verification, the response including an affirmative authentication of the airborne vehicle and an approval of the flight path.

[0053] An apparatus for wireless communication at an airborne functional management system is described. The apparatus may include means for: receiving a request from a network to verify an air vehicle coupled to the wireless device while a procedure for establishing a data session is being performed between the network and the wireless device, the request including an airborne identifier of the airborne vehicle and operational information about the airborne vehicle; verifying the identity of the airborne vehicle and a flight path of the airborne vehicle based on the airborne identifier and the operational information included in the request; and sending a response to the network based on the verification, the response including an affirmative authentication of the airborne vehicle and approval of the flight path.

[0054] A non-transitory computer-readable medium storing code for wireless communication at an air function management system is described. The code may include instructions executable by a processor to perform the following operations: receiving a request from a network to verify an air vehicle coupled to a wireless device while a procedure for establishing a data session is being performed between the network and the wireless device, the request including an air identifier of the air vehicle and operational information about the air vehicle; verifying the identity of the air vehicle and a flight path of the air vehicle based on the air identifier and the operational information included in the request; and sending a response to the network based on the verification, the response including an affirmative authentication of the air vehicle and approval of the flight path.

[0055] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for verifying the authenticity of the request to verify the air vehicle.

[0056] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the request includes a first set of credentials for the air vehicle, and wherein the authenticity of the request is verifiable based on the first set of credentials.

[0057] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: identifying second operational information about the air vehicle and a second air identifier that may be stored at the air functional management system based on receiving the request to verify the air vehicle.

[0058] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, verifying the identity of the air vehicle may include operations, features, apparatuses, or instructions for comparing the operational information with the second operational information and comparing the air identifier with the second air identifier, wherein the identity of the air vehicle may be authenticated based on the operational information matching the second operational information and the air identifier matching the second air identifier.

[0059] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, verifying the identity of the air vehicle may include operations, features, apparatus, or instructions for sending the air identifier and the operational information to a flight control system, and receiving a second response from the flight control system, the second response including an affirmative authentication of the air vehicle and received before sending the response.

[0060] A method for wireless communication at a wireless device coupled to an air vehicle is described. The method may include: transmitting a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; wherein the first message is configured to establish a data session with the network, and wherein a request to verify the air vehicle based on the first message is sent to an air functional management system; receiving a second message from the network based on transmitting the first message, the second message including a positive authentication of the air vehicle and an approval of a flight path of the air vehicle and configured to trigger establishment of the data session; and establishing the data session with the network based on receiving the second message.

[0061] An apparatus for wireless communication at a wireless device coupled to an air vehicle is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: transmit a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; wherein the first message is configured to establish a data session with the network, and wherein a request to verify the air vehicle based on the first message is sent to an air functional management system; receive a second message from the network based on transmitting the first message, the second message including a positive authentication of the air vehicle and an approval of the flight path of the air vehicle and configured to trigger establishment of the data session; and establish the data session with the network based on receiving the second message.

[0062] Another apparatus for wireless communication at a wireless device coupled to an air vehicle is described. The apparatus may include means for: transmitting a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; wherein the first message is configured to establish a data session with the network, and wherein a request to verify the air vehicle based on the first message is sent to an air functional management system; receiving a second message from the network based on transmitting the first message, the second message including a positive authentication of the air vehicle and an approval of a flight path of the air vehicle and configured to trigger establishment of the data session; and establishing the data session with the network based on receiving the second message.

[0063] A non-transitory computer-readable medium storing code for wireless communication at a wireless device coupled to an air vehicle is described. The code may include instructions executable by a processor to perform the following operations: transmitting a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; wherein the first message is configured to establish a data session with the network, and wherein a request to verify the air vehicle based on the first message is sent to an air function management system; receiving a second message from the network based on transmitting the first message, the second message including a positive authentication of the air vehicle and an approval of the flight path of the air vehicle and configured to trigger the establishment of the data session; and establishing the data session with the network based on receiving the second message.

[0064] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the first message includes a first indication of an access point providing air service, the air identifier, the operational information about the air vehicle, and a second indication of a controller for the air vehicle.

[0065] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for encapsulating the first indication of the access point in an Evolved Packet System (EPS) Session Management (ESM) container, and encapsulating the air identifier, the operational information about the air vehicle, and the second indication of the controller for the air vehicle in a Protocol Configuration Option (PCO) field.

[0066] Some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatus, or instructions for the following actions: identifying an access point providing air service, wherein the data session may be released based on the access point, and a second data session may be established based on the access point, wherein an exclusive communication path is established between the wireless device and a controller for the air vehicle via the access point. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Figure 1 An example of a wireless communication system that supports authorization of unmanned vehicles to operate in a network in accordance with various aspects of the present disclosure is illustrated.

[0068] Figure 2 Various aspects of a wireless communication system that supports authorizing unmanned vehicles to operate in a network in accordance with various aspects of the present disclosure are illustrated.

[0069] Figure 3Various aspects of a process for authorizing an unmanned vehicle to operate in a network are illustrated in accordance with various aspects of the present disclosure.

[0070] Figure 4 Various aspects of a process for authorizing an unmanned vehicle to operate in a network are illustrated in accordance with various aspects of the present disclosure.

[0071] Figure 5 Various aspects of a process for authorizing an unmanned vehicle to operate in a network are illustrated in accordance with various aspects of the present disclosure.

[0072] Figure 6 Various aspects of a process for authorizing an unmanned vehicle to operate in a network are illustrated in accordance with various aspects of the present disclosure.

[0073] Figure 7 Various aspects of a process for authorizing an unmanned vehicle to operate in a network are illustrated in accordance with various aspects of the present disclosure.

[0074] Figure 8 and Fig. 9 A block diagram of a device that supports authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown.

[0075] Fig.10 A block diagram of a communications manager that supports authorization of unmanned vehicles to operate in a network in accordance with aspects of the present disclosure is shown.

[0076] Fig.11 A diagram of a system including devices that support authorization of unmanned vehicles to operate in a network is shown in accordance with aspects of the present disclosure.

[0077] Fig.12 and Fig.13 A block diagram of a device that supports authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown.

[0078] Fig.14 A block diagram of a communications manager that supports authorization of unmanned vehicles to operate in a network in accordance with aspects of the present disclosure is shown.

[0079] Fig.15 A diagram of a system including devices that support authorization of unmanned vehicles to operate in a network is shown in accordance with aspects of the present disclosure.

[0080] Fig.16 A block diagram of a device that supports authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown.

[0081] Figures 17 to 22A flow chart illustrating a method of supporting authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0082] A wireless network may be able to provide support for unmanned aerial vehicle (UAV) operations—for example, may be configured to provide UAV-specific services to a user equipment (UE) coupled to a UAV that supports UAV operations. However, an external entity (e.g., a government agency) may be responsible for determining the procedures that a UAV may follow to gain access to an airspace. In some cases, these procedures may be unknown to the wireless network, and / or the wireless network may not be able to interact with a regulatory agency to ensure that the UAV has complied with these procedures. Accordingly, in order to prevent violations of policies established by regulatory agencies, a wireless network may be unable or prohibited from providing aerial services to UAVs.

[0083] In order to support the deployment of UAVs within a wireless network, mechanisms and procedures may be established that allow for direct interaction between a regulatory body and the wireless network. In some examples, a flight management system may be established as an interface between a regulatory body and the wireless network and used to communicate control and / or data information between the regulatory body and the wireless network. In some cases, the flight management system may be coupled to the wireless network as a subsystem of the wireless network. In other cases, the flight management system may act as a stand-alone interface between the wireless network and the regulatory body.

[0084] In some examples, operations for entering an airspace in accordance with agency policy may be combined with procedures for accessing a wireless network (e.g., the access procedures may have built-in capabilities for supporting UAV functionality). In some examples, operations associated with agency procedures for authorizing and authenticating UAVs may be combined with network procedures for registering with a wireless network (e.g., a "registration procedure") and / or procedures for establishing a data session with a wireless network (e.g., a "protocol data unit (PDU) session establishment procedure") - for example, when the wireless network is an NR system. In some examples, operations associated with agency procedures for authorizing and authenticating UAVs may be combined with network procedures for registering with and establishing a data session with a wireless network (e.g., a "attachment procedure") - for example, when the wireless network is a legacy network (which does not have an access procedure with built-in capabilities for authenticating UAVs or authorizing UAV functionality).

[0085] By incorporating operations for entering airspace into procedures for accessing wireless networks, the time and complexity associated with obtaining authentication and authorization for a UAV and confirming that the UAV has obtained authentication and authorization can be reduced. Moreover, authentication and authorization for a UAV seeking to access a wireless network can be obtained in real time and on the fly. Additionally, security measures associated with authenticating and authorizing a UE can be simplified and made more secure.

[0086] Aspects of the present disclosure are initially described in the context of a wireless communication system. Examples of communication devices that perform operations for authorizing an unmanned vehicle to operate in a network are then described. Aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow charts related to authorizing an unmanned vehicle to operate in a network.

[0087] Figure 1 An example of a wireless communication system that supports authorization of unmanned vehicles to operate in a network according to various aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, or a new radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

[0088] The base stations 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may be different forms of devices or devices with different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base stations 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support communication of signals according to one or more radio access technologies.

[0089] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be different forms of devices or devices with different capabilities. Figure 1Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), such as Figure 1 as shown in .

[0090] Each base station 105 may communicate with the core network 130, or communicate with each other, or both. For example, the base station 105 may interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3 or other interfaces). The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105), or indirectly (e.g., via the core network 130), or directly and indirectly on the backhaul link 120 (e.g., via X2, Xn or other interfaces). In some examples, the backhaul link 120 may be or include one or more wireless links.

[0091] One or more of the base stations 105 described herein may include or may be referred to by a person of ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a B node, an evolved B node (eNB), a next generation B node or a gigabit B node (any of which may be referred to as a gNB), a home B node, a home evolved B node, or other suitable terminology.

[0092] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.

[0093] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as base stations 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 as shown in .

[0094] UE 115 and base station 105 may communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a collection of one or more radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-APro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0095] The signal waveform transmitted on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may include a code element period (e.g., the duration of a modulation code element) and a subcarrier, where the code element period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 can be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further improve the data rate or data integrity of communication with UE 115.

[0096] The time interval of the base station 105 or the UE 115 can be expressed as a multiple of a basic time unit, and the basic time unit can be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0097] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of code element periods (e.g., depending on the length of the cyclic prefix added before each code element period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-time slots containing one or more code elements. Excluding the cyclic prefix, each code element period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating band.

[0098] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0099] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured to include a set of one or more UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0100] In some examples, base stations 105 may be mobile and thus provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

[0101] The wireless communication system 100 may be configured to support ultra-reliable communication or low latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low latency communication (URLLC) or mission-critical communication. UE 115 may be designed to support ultra-reliable, low latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private communication or group communication, and may be supported by one or more mission-critical services (such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions may include prioritization of services, and mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low latency, critical mission, and ultra-reliable low latency may be used interchangeably herein.

[0102] In some examples, UE 115 may also be able to communicate directly with other UE 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within a geographic coverage area 110 of a base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105, or may not be able to receive transmissions from the base station 105 for other reasons. In some examples, each group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, wherein each UE 115 transmits to each other UE 115 in the group. In some examples, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between each UE 115 without involving the base station 105.

[0103] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a base station 105 associated with the core network 130. User IP packets may be delivered via a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to a network operator IP service 150. Operator IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0104] Some network devices (such as base stations 105) may include subcomponents, such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with each UE 115 through one or more other access network transport entities 145, which may be referred to as radio heads, smart radio heads, or transmission / reception points (TRPs). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or merged into a single network device (e.g., base station 105).

[0105] The wireless communication system 100 can operate using one or more frequency bands, in some examples, in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). In general, the 300 MHz to 3 GHz region is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about 1 decimeter to 1 meter long. UHF waves can be blocked or redirected by buildings and environmental features, but these waves can penetrate various structures sufficiently for macro cells to provide service to UEs 115 located indoors. Transmission of UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0106] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating in an unlicensed radio frequency spectrum band, devices (such as base stations 105 and UEs 115) may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in coordination with component carriers operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0107] The base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with the base station 105 may be located at different geographical locations. The base station 105 may have an antenna array having antenna ports of several rows and columns that the base station 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0108] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each antenna element may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0109] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the bearer or packet data convergence protocol (PDCP) layer may be IP-based. The radio link control (RLC) layer may perform packet segmentation and reassembly to communicate on a logical channel. The media access control (MAC) layer may perform priority handling and multiplex logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission of the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports radio bearers of user plane data between UE 115 and base station 105 or core network 130. In the physical layer, transport channels may be mapped to physical channels.

[0110] The wireless communication system 100 can provide support for the operation of an unmanned vehicle (e.g., a drone, UAV) (which can be autonomous and / or remotely controlled). For example, a wireless communication system 100 connected to an unmanned vehicle and a remote controller can act as an intermediary that relays commands between the remote controller and an unmanned vehicle that is out of sight of the remote controller. In some cases, in order to obtain access to the wireless communication system 100, the unmanned vehicle can be coupled to a UE 115 - for example, the UE 115 can be included in the unmanned vehicle or attached to the unmanned vehicle - and is used to access the wireless communication system 100 and communicate with it. In some examples, information for controlling the unmanned vehicle can be transmitted to the UE 115, and the UE 115 can relay the information to a controller within the unmanned vehicle.

[0111] Before a UE 115 (e.g., a UE 115 coupled to an unmanned vehicle) is allowed to access services provided by a wireless communication system 100, the UE 115 may be provided or assigned a unique “network identifier” by an operator of the wireless communication system. In some examples, a subscriber identity module (SIM) card located within the UE 115 may be used to store a unique network identity (e.g., an international mobile subscriber identity (IMSI)) of the UE 115, and the UE 115 may provide the unique network identity to the wireless communication system 100 during an access procedure. In some cases, the access procedure is referred to as a registration procedure—e.g., where the wireless communication system 100 is an NR system. In some cases, the access procedure is referred to as an attachment procedure—e.g., where the wireless communication system 100 is an old (or existing) radio system (such as an LTE or 4G system). Before allowing the UE 115 to access services provided by the wireless communication system 100 , the wireless communication system 100 may use the network identity provided by the UE 115 to confirm that the UE 115 has a subscription to access the wireless communication system 100 .

[0112] In some examples, the wireless communication system 100 may be configured to provide dedicated services to support the operation of the UAV. The dedicated services for the UAV may include: a subscription-based means for identifying and authorizing a UE 115 coupled to the UAV, a procedure for reporting the altitude of the UE 115, a dedicated interference detection procedure, a procedure for signaling flight path information, and / or position information reporting including horizontal and vertical speeds of the UE 115. In order to access these dedicated services, the UE 115 may be configured with a network identifier that identifies the UE 115 coupled to the UAV.

[0113] For confidentiality and safety reasons, the operation of some unmanned vehicles may comply with regulations established by regulatory agencies for the jurisdictions in which unmanned vehicles are planned to operate. For example, regulatory agencies that control airspace in a jurisdiction may specify that UAVs (e.g., all UAVs, or UAVs of a specific size and / or capability) must be verified before deployment. In some cases, regulatory agencies can use the unique "air identifier" of the UAV to verify the identity of the UAV. In some examples, regulatory agencies can use the unique serial number of the UAV as a way to identify the UAV-for example, a manufacturer can generate the serial number of the UAV according to a standardization process. In some examples, regulatory agencies can assign a unique air identification number to a UAV registered with the regulatory agency. And in some examples, an air traffic controller system can assign a unique air identification number to a UAV seeking to enter the airspace, which can be referred to as a UAV unique identifier (UUID). In some cases, the UUID can be generated based on the serial number of the UAV or the assigned air identification number. In some cases, regulatory agencies can issue a ban on the operation of UAVs that have not been assigned at least one type of air identifier.

[0114] After establishing the UAV's airborne identifier, the regulatory body may also require that the operator of the UAV submit a flight plan for the UAV before the UAV will be approved for operation. In some examples, the UAV operator may submit the flight plan to the regulatory body, which may reject or approve the flight plan based on an analysis of the flight path trajectory, available airspace, safety issues, etc. In some cases, the UAV may be pre-approved for a flight path, and the regulatory body may confirm that the indicated flight path matches the pre-approved flight path before approval. In some cases, the regulatory body may maintain one or more flight control servers that store information related to approved UAVs and / or approved flight plans.

[0115] In order to support the safe and smooth operation of UAVs in airspace shared with other aircraft, regulatory agencies may also establish standards that enable the identity of UAVs to be remotely and continuously identified during operation (e.g., by the regulatory agency, an authorized third party monitoring the airspace, other operating UAVs, and / or other operating aircraft). In some examples, the UAV may be configured to broadcast a unique identity (e.g., a serial number, an assigned identification number, and / or a UUID) in a remote identification (RID) message, where the broadcasted unique identity may be received by other aircraft and ground stations. In some cases, in addition to the unique identity, the UAV may also broadcast operational information, including but not limited to: latitude, longitude, altitude, trajectory of the UAV, identification of the type of UAV, timestamp, accuracy information about the latitude, longitude, and / or timestamp, the operational state of the UAV, a description of the operation being performed by the UAV, altitude above takeoff, pressure altitude of the location, speed in multiple directions, location of the operator, identity of the operator, and the like. Aircraft and ground stations may use the information received in the RID message to verify the identity of the UAV, avoid collisions, confirm that the UAV is within an authorized area, identify rogue UAVs, and the like.

[0116] In some examples, the UAV may be configured to broadcast the RID message using an out-of-band or non-networking technology (such as Bluetooth or Wi-Fi) and using security measures to ensure the integrity and security of the RID message. In other examples, the UAV may be configured to transmit the RID message using a wireless network that utilizes an authentication mechanism to ensure the integrity and security of the RID message.

[0117] As discussed above, the wireless communication system 100 may be able to provide support for UAV operations. However, there may not be an interface established to allow the wireless communication system 100 to interact directly with the regulatory body - for example, the wireless communication system 100 may not be able to access a flight control server that stores information related to approved UAVs and approved flight plans. Similarly, there may not be procedures established to enable the wireless communication system 100 to interact directly with the regulatory body. Thus, the wireless communication system 100 may not be able to ensure that UAV operations comply with regulations established by the regulatory body. Accordingly, in order to prevent violations of policies established by the regulatory body, the wireless communication system 100 may be unable or prohibited from providing airborne functions to the UAV.

[0118] To support the deployment of UAVs within the wireless communication system 100, mechanisms and procedures may be established that allow for direct interaction between regulatory agencies and the wireless communication system 100. In some examples, a flight management system may be established as an interface between the regulatory agency and the wireless communication system 100. In some cases, the flight management system may be incorporated as a subsystem into the wireless communication system 100. In other cases, the flight management system may act as an external intermediary between the wireless communication system 100 and the regulatory agency.

[0119] In some examples, operations for entering an airspace in accordance with an agency policy may be incorporated into a procedure for accessing the wireless communication system 100 (e.g., the access procedure may have a built-in capability to support UAV functionality). In some examples, operations associated with an agency procedure for authorizing and authenticating a UAV may be incorporated into a network procedure for registering with the wireless communication system 100 (e.g., a "registration procedure") and / or a procedure for establishing a data session with the wireless communication system 100 (e.g., a "PDU session establishment procedure") - for example, when the wireless communication system 100 is an NR system. In some examples, operations associated with an agency procedure for authorizing and authenticating a UAV (also referred to as a "UAV Service Provider (USS) Specific Authentication and Authorization (USAA) Procedure") may be incorporated into a network procedure for registering with a wireless communication system and establishing a data session with it (e.g., a "attachment procedure") - for example, when the wireless network is a legacy network (which does not have an access procedure with a built-in capability for authenticating a UAV or authorizing UAV functionality). In some examples, UUIDs may be used to facilitate the merging of network procedures and air traffic procedures.

[0120] By incorporating operations for entering airspace into procedures for accessing wireless networks, the time and complexity associated with obtaining authentication and authorization for a UAV and confirming that the UAV has obtained authentication and authorization can be reduced. Moreover, authentication and authorization of a UAV seeking to access a wireless network can be obtained in real time and on the fly - for example, rather than the UAV operator having to obtain authentication and authorization separately from a regulatory agency to obtain initial approval and / or modify operating parameters for the UAV each time before accessing a cellular network. Additionally, security measures associated with authenticating and authorizing a UE can be simplified and made more secure - for example, by building UAV-specific security measures directly into the network access procedures, rather than having the flight control system and the wireless network system establish additional security measures to be independently complied with, and / or by establishing a secure link (e.g., a wired link) between the wireless network and the flight control system.

[0121] Figure 2Various aspects of a wireless communication system that supports authorization of an unmanned vehicle to operate in a network according to various aspects of the present disclosure are illustrated. The wireless communication system 200 may include a UE 215, which may be coupled to a UAV 220 and is an example of a UE 115, as described with reference to FIG. Figure 1 The wireless communication system 200 may further include a UAV system (UAS) 230, which includes a UAV 220 and a UAV controller 225. The wireless communication system 200 may further include a third party authorized entity (TPAE) 235, a first public land mobile network (PLMN) 240, a second PLMN 245, a first flight management system 250, a second flight management system 255, and a traffic control system 260.

[0122] UAV 220 may be an autonomous or remotely operated aerial vehicle (e.g., without a pilot on board). In general, UAV 220 may be a drone that does not carry passengers, but some UAVs may be designed to carry passengers. UAV 220 may be coupled to UE 215, and may use UE 215 to communicate with a wireless (e.g., cellular) network. In some cases, UE 215 is configured with a unique network identity that is used to verify that UE 115 has a subscription to access a wireless network.

[0123] The UAV controller 225 may be configured to issue commands to the UAV 220 and receive data (eg, telemetry) from the UAV 220. The UAV controller may also be coupled to a UE that is used to communicate with the wireless network.

[0124] The TPAE 235 may be a privileged UAV controller that may be used to monitor the operation of various UAVs and to take control of one or more UAVs via a wireless network.

[0125] The first PLMN 240 may be a wireless network maintained and managed by a first operator. The first PLMN 240 may include a radio access network architecture (e.g., a cell tower and a backhaul network), network components supporting the operation of the radio access network (e.g., an MME entity, an AMF entity, etc.), and network components supporting access to a data network (e.g., a session management function (SMF) entity, a PDN GW (gateway) entity, etc.). Similarly, the second PLMN 245 may be a wireless network maintained and managed by a different second operator.

[0126] The first flight management system 250 may be configured to act as an interface between the first PLMN 240 and the traffic control system 260. In some cases, the first flight management system 250 is a subsystem of the first PLMN 240. In other cases, the first flight management system 250 is an external component of the first PLMN 240. In some cases, the first flight management system 250 may include a UAV flight management system (UFMS), a UAV flight control function (UFCF), and / or a UAV flight support function (UFSF). Similarly, the second flight management system 255 may be configured to act as an interface between the second PLMN 245 and the traffic control system 260.

[0127] The traffic control system 260 may be configured to manage traffic in the airspace - for example, by approving and scheduling UAV operations. The traffic control system 260 may be configured to identify UAVs, UAV operators, and / or UAV pilots flying in the airspace monitored by the traffic control system 260. The traffic control system 260 may also provide flight plan management services, issue flight permissions and instructions, and manage traffic in the airspace. Additionally, the traffic control system 260 may be configured to monitor and track UAVs, monitor to ensure that the UAVs are still complying with the published flight plans, provide weather information, provide information about obstacles, and provide conflict avoidance services. The traffic control system 260 may also be configured to notify UAVs of emergencies and record historical UAV flight information - for example, for subsequent accident investigations.

[0128] Traffic control system 260 may include UAV service provider (USS) entities configured to support safe and efficient use of a particular airspace by providing services to UAV operators in accordance with a broader traffic control plan developed by traffic control system 260. In some cases, each USS entity interfaces with other USS entities, each of which may obtain approval from a regulatory agency before being permitted to deploy. In some cases, traffic control system 260 may also be referred to as a UAV traffic management (UTM) system.

[0129] The wireless communication system 200 may also include one or more UAV-specific interfaces that may be used to relay UAV-specific information between the UAS 230, the TPAE 235, the first PLMN 240, the second PLMN 245, the first flight management system 250, the second flight management system 255, and the traffic control system 260. The wireless communication system 200 may include a first interface 265 (or UAV1), a second interface 270 (or UAV3), a third interface 275 (or UAV4), a fourth interface 280 (or UAV9), and a fifth interface 285 (or UAV6).

[0130] The first interface 265 may be configured to provide a connection between a UAV (e.g., UAV 220) and one or more PLMNs (e.g., first PLMN 240 and second PLMN 245). The first interface 265 may also be configured to provide a connection between a UAV controller (e.g., UAV controller 225) and one or more PLMNs (e.g., first PLMN 240 and second PLMN 245). In some cases, the first interface 265 may be configured to communicate control information for authorizing, authenticating, identifying, and / or tracking a UAV and / or a UAV controller.

[0131] The second interface 270 may be configured to provide a connection between the UAV and the UAV controller (eg, UAV 220 and UAV controller 225). In some cases, the second interface 270 may be configured to communicate data information (eg, command and control) between the UAV and the UAV controller.

[0132] The third interface 275 may be configured to provide a connection between a UAV and a TPAE (e.g., UAV 220 and TPAE 235). In some cases, the third interface 275 may be configured to communicate data information (e.g., command and control) and control information (e.g., RID messages and UAV tracking) between the UAV and the TPAE.

[0133] The fourth interface 280 may be configured to provide a connection between the UAV, the UAV controller, and the flight management system (e.g., UAV 220, UAV controller 225, first flight management system 250, second flight management system 255). In some cases, the fourth interface 280 may further provide a connection between the UAV, the UAV controller, the flight management system, and the traffic control system (e.g., traffic control system 260). In some cases, the fourth interface 280 may be configured to communicate control information for authorizing, authenticating, identifying, and / or tracking the UAV and / or UAV controller. In some cases, the fourth interface 280 may be configured to communicate data information (e.g., command and control) - for example, in the case where the traffic control system 260 takes control of the UAV 220.

[0134] The fifth interface 285 may be configured to provide connections between PLMNs, flight management systems, and traffic control systems (e.g., first PLMN 240, second PLMN 245, first flight management system 250, second flight management system 255, and traffic control system 260). In some cases, the fifth interface 285 may be configured to communicate control information for authorizing, authenticating, identifying, and / or tracking UAVs and / or UAV controllers. In some cases, the fifth interface 285 may be configured to communicate data information (e.g., command and control)—e.g., when the traffic control system 260 takes control of the UAV 220.

[0135] As discussed above, in order to support the safe and secure deployment of UAVs within wireless communication systems, mechanisms and procedures that allow direct interaction between regulatory agencies and wireless communication systems may be determined. In some examples, a flight management system (e.g., first flight management system 250 and / or second flight management system 255) may be established as an interface between a regulatory agency and a wireless network. In some examples, operations for authorizing and authenticating UAVs according to regulatory agency protocols (e.g., USAA procedures) may be incorporated into procedures for accessing wireless networks.

[0136] In some examples, the UAV 220 and / or the UAV controller 225 may seek to access a wireless network. In some examples, the UAV 220 and the UAV controller 225 use the UAV1 interface to access the wireless network. For example, the UAV controller 225 may use the first interface 265 to access the second PLMN 245. In some examples, the UAV 220 and the UAV controller 225 may seek to access the same PLMN (e.g., the first PLMN 240), and both may use the same UAV1 interface to access the same PLMN. In order to access the wireless network, the UAV 220 and / or the UAV controller 225 may transmit a message (e.g., a RID message) via the UAV1 or UAV9 interface, which includes a network identifier of the coupled UE (e.g., UE 215), an air identifier of the device itself (e.g., UAV 220 or UAV controller 225), and other flight information (which may include information such as an operator identifier, a flight path, etc.). Based on the radio access technology used by the PLMN, the UAV 220 and / or the UAV controller 225 may transmit the message during a specific network access procedure. For example, if the first PLMN 240 is configured to use an emerging radio access technology (e.g., 5G or NR), the message may be transmitted during a registration procedure and / or a PDU session establishment procedure. Alternatively, if the first PLMN 240 is configured to use an old radio access technology (e.g., 4G or LTE), the message may be transmitted during an attachment procedure. In some examples, before accessing the wireless network, the UAV 220 may obtain a UUID and a set of one or more credentials from the first flight management system 250 or the traffic control system 260. The UAV 220 may use the UUID and the set of credentials during the USAA procedure. In some cases, the set of credentials may enable the first flight management system 250 to verify that the UAV 220 is the actual UAV corresponding to the UUID.

[0137] After receiving the message from UE 215 requesting access to the wireless network, first PLMN 240 may determine that UE 215 is coupled to UAV 220 and may initiate authentication and authorization procedures involving access to traffic control system 260 via first flight management system 250 and using UAV6 interface. Procedures for accessing wireless networks, including operations for authorizing and authenticating UAVs via flight management systems, are described in more detail herein.

[0138] In some cases, the first flight management system 250 may determine that the UAV 220 is authenticated and authorized for flight operations, and the second flight management system 255 may determine that the UAV controller 225 is authenticated and authorized for flight operations. After determining that the authentication and authorization procedures for the UAV 220 and the UAV controller 225 have been successfully completed, the first PLMN 240 and / or the second PLMN 245 may establish a data session with the UAV 220 and / or the UAV controller 225, and the UAV controller 225 may exchange data (e.g., command and control) with the UAV 220 via the second interface 270.

[0139] In some examples, USAA procedures may be executed dynamically—e.g., each time the UAV 220 connects to a wireless network. In some examples, upon connecting to a wireless network, as long as the wireless network stores valid authorization for the UAV 220, USAA procedures using the first flight management system 250 and the traffic control system 260 may be executed. In some examples, USAA procedures may be executed a single time—e.g., when the UAV 220 obtains a UUID and a set of credentials—and the first flight management system 250 may store the UUID and the set of credentials. In such a case, the first flight management system 250 may authenticate and authorize the UAV 220 without interacting with the traffic control system 260.

[0140] Figure 3 Various aspects of a process for authorizing an unmanned vehicle to operate in a network according to various aspects of the present disclosure are illustrated. Process flow 300 may be performed by UAV 320 (which may be a UAV 320 as referred to herein). Figure 1 and Figure 2 The process flow 300 may also be performed by a radio access network (RAN) 321, an AMF 322, an SMF 323, a UFMS 324, and a USS 325. In some cases, a core network 390 of the PLMN is configured according to an NR system (e.g., a 5G system) and includes an AMF 322 and an SMF 323. In some cases, the core network 390 also includes a UFMS 324. In some cases, a flight management system (e.g., Figure 2 The first flight management system 250 of the present invention includes UFMS 324. In some cases, the traffic control system (e.g., Figure 2 The traffic control system 260) includes the USS 325. In some cases, the radio access system 391 includes the UAV 720 and the RAN 721.

[0141] In some examples, process flow 300 illustrates control plane operations for authenticating and authorizing UAV 320, which are incorporated into or performed as part of procedures for registering with a wireless network. In some cases, a UAV controller may perform similar procedures.

[0142] In block 331, a UE coupled to the UAV 320 may perform a procedure for obtaining a UUID and credentials used to protect communications between the UAV 320 and the UFMS 324. In some examples, the UE may obtain a UUID from the UFMS 324, where the UUID may be a temporary identity used by the UFMS 324 and the USS 325 to uniquely identify the UAV 320. In some cases, the set of credentials (e.g., security keys and certificates) may be used to protect the UUID when the UAV 320 broadcasts a RID message, and to enable other UAVs and monitoring entities to verify the validity of the flight information or tracking information broadcast by the UAV 320. In some cases, the UE is assigned multiple UUID and credential combinations—for example, the UE may be assigned a first UUID and a first credential for in-coverage operations, and a second UUID and a second credential for out-of-coverage operations. In some cases, the UUID and credential combination may be referred to simply as a UUID. In some examples, the UUID and credentials may be provided by the UFMS 324. In other examples, the UUID and credentials may be provided by the USS 325. At arrow 333, a UE coupled to the UAV 320 may transmit a registration request message via the RAN 321 to register with the wireless network. The registration request message may convey UE parameters such as a subscriber permanent identifier (SUPI) and credentials for authenticating the SUPI. The registration message may also convey UAV parameters such as the UUID and flight data. The flight data may include: latitude, longitude, altitude, trajectory of the UAV, identification of the type of UAV, timestamp, accuracy information about the latitude, longitude and / or timestamp, operational state of the UAV, description of the operation being performed by the UAV, altitude above takeoff, pressure altitude of the position, speed in latitude and longitude, location of the operator, identity of the operator, and the like. In some cases, the registration message may also include information about a controller for the UAV 320—for example, the registration message may include a UUID of the controller, a location of the controller, and / or identification information about the controller (such as a pilot identity). In some cases, the registration request may be configured to register the UE for a network slice for airborne operations.

[0143] At block 335, AMF 322 may retrieve a network profile for the UE (e.g., a subscriber profile associated with the UE's credentials) and authenticate the UE. In some cases, AMF 322 may also verify that the UE has a subscription to access common services provided by the wireless network (e.g., voice, data, messaging, etc.). And at block 337, AMF 322 may verify that the identified network profile for the UE also has a valid subscription that gives the UE access to over-the-air services provided by the wireless network.

[0144] At block 339, AMF 322 may determine whether USAA procedures are to be performed before the wireless network is permitted to provide over-the-air services to the UE based on verifying that the UE has a valid subscription for over-the-air services. In some cases, the subscription indicates that USAA procedures are to be performed for the UE before the UE is given access to the wireless network. In some cases, AMF 322 determines that USAA procedures may be bypassed for UAV 320—for example, where AMF 320 has stored an indication that a previous USAA procedure performed for UAV 320 was successfully completed and is still valid.

[0145] In box 341, AMF 322 may identify the identity of UFMS 324 based on identification information (e.g., UUID or SUPI) signaled by the UE. And in box 343, AMF 322 may complete the network registration procedure. In some cases, AMF 322 may select a network slice for over-the-air operation for the UE based on subscription information about the UE. In some examples, AMF 322 may register the UE to a "prohibited" area or mode that only enables control plane communications with AMF 322 (e.g., does not enable data communications or PDN connections or sessions via the PDN GW). For example, the UE may be assigned to a state in which user plane data is blocked.

[0146] At arrow 345, AMF 322 may transmit a registration accept message to the UE via RAN 321, indicating that the registration request is accepted and that the UE has registered with the wireless network. In some cases, the registration accept message may include information about whether USAA procedures are pending or to be performed before the UE can obtain access to over-the-air services. In some cases, if USAA procedures are being performed as part of the registration request, the registration accept message indicates that the USAA procedures are pending. In some cases, the UE may establish a control plane connection with the wireless network based on receiving the registration accept message.

[0147] At arrow 347, AMF 322 may transmit a USAA request message to the UE via RAN 321 to request the UE to provide the wireless network with information for authenticating and authorizing UAV 320 to perform flight operations.

[0148] At arrow 349, the UE may transmit a USAA response message including information for authenticating the UAV 320 based on the UUID and authorizing the UE to perform flight operations to the MAF 322 via the RAN 321. The USAA response message may include the UUID of the UAV 320 and flight data.

[0149] At arrow 351, AMF 322 may send a USAA request message to UFMS 324 to request that UFMS 324 authenticate and / or authorize UAV 320 for flight operations. In some cases, the USAA request may include the UUID and flight data of UAV 320. In some cases, AMF 322 obtains the UUID and flight data for inclusion in the USAA request from the registration request message transmitted at arrow 333—for example, when AMF 322 does not transmit the USAA request at arrow 347. In other cases, AMF 322 obtains the UUID and flight data from the USAA response message transmitted at arrow 349. In some cases, the USAA request message is transmitted using one or more security keys for protecting and verifying the USAA request message.

[0150] At block 353, UFMS 324 may verify that the USAA request message received from AMF 322 is valid—e.g., using the one or more security keys. In some cases, UFMS 324 may use stored information about UAV 320 (e.g., a stored UUID) to determine whether the received USAA message is valid.

[0151] At arrow 355, UFMS 324 and UAV 320 may exchange USAA information. In some examples, UFMS 324 may send a USAA request message to UAV 320, and UAV 320 may send a USAA response message to UFMS 324. In some cases—e.g., where UFMS 324 obtains information for performing USAA in a registration request message transmitted at arrow 333 or a USAA response message transmitted at arrow 349—UAV 320 and UFMS 324 may refrain from exchanging USAA information.

[0152] At block 357, the UFMS 324 may attempt to verify the flight data received from the UAV 320 based on flight data for the UAV 320 previously received from the USS 325 and stored at the UFMS 324. In some cases, the UFMS 324 may authenticate the identity of the UAV 320 based on the UUID and / or flight data stored for the UAV 320. For example, the UFMS 324 may authenticate the identity of the UAV 320 using information such as the operator identity, the UAV type, the operator location, and the flight path. In some cases, the UFMS 324 may confirm an authorized association between the UAV 320 and a controller for the UAV 320.

[0153] At arrow 359, UFMS 324 may send a USAA request message to USS 325. In some cases, the USAA request message includes the UUID and flight data of UAV 320 and requests that the USS perform USAA procedures. In some examples, UFMS 324 may send the USAA request message after determining that information about UAV 320 is not stored at UFMS 324. In some examples, UFMS 324 may send the USAA request message after a USAA procedure performed by UFMS 324 fails.

[0154] At arrow 361, UFMS 325 may send a USAA response message to USS 324. In some cases, the USAA response message may include an indication of whether the USAA procedure was successful and / or flight data of UAV 320 (if the procedure was successful). In some cases, the USAA response message may include an indication of the duration for which the authentication and authorization are valid - for example, the USAA response message may indicate that UAV 320 is authenticated and authorized for the lifetime of UAV 320. In some cases, USS 325 may revoke persistent authentication and authorization at any time. In some cases, before sending the USAA response message, USS 325 may determine whether to approve one or more aspects associated with the instructed flight of UAV 320 (e.g., flight parameters, flight path). In some cases, the one or more aspects include a UAV (e.g., UAV 320), a UAV type, a UAV category, a UAV service provider, a flight schedule, a mission type, a location associated with a flight path, a pilot identity, an operator identity, operating parameters associated with a flight path, conditional validity information, or any combination thereof.

[0155] In some cases, the UFMS 324 may not be able to approve the flight path without first receiving approval of the flight path from the USS 325 .

[0156] In some cases, the USS 325 may provide conditional validity information regarding authentication and authorization—e.g., the USS 325 may indicate information regarding the controller for the UAV 320, the UAV type and category, the mission type, the location, the pilot identity, the operator identity, the flight plan, etc. In such cases, if the wireless network determines that the flight / mission parameters for the UAV 320 do not meet the conditions (e.g., the UAV 320 deviates from the approved conditions), the wireless network may trigger the USAA procedure for the UAV 320. Having the wireless network initiate the USAA procedure based on conditional authentication and approval may reduce the processing load on the USS 325.

[0157] At block 363, UFMS 324 may store the USAA response message generated by UFMS 324 or received from USS 325. In some examples, UFMS 324 may store the flight data of UAV 320 received from USS 325.

[0158] At arrow 365, UFMS 324 may send a USAA response message to AMF 322. In some cases, the USAA response message may include an indication of whether the USAA procedure was successful and / or flight data of UAV 320 (if the procedure was successful). In some cases, the USAA response message includes configuration information for the UE—for example, the message may include information directing the UE to report location continuously or at intervals.

[0159] At arrow 367, AMF 322 may transmit a USAA confirmation message (in the case of a successful USAA procedure) or a USAA rejection message (in the case of an unsuccessful USAA procedure) to a UE coupled to UAV 320 via RAN 321. In some cases, the UE may establish a PDU session with the wireless network based on receiving the USAA confirmation message. And, a controller for a UAV 320 that has similarly performed a successful USAA procedure may use the wireless network to transmit command and control information to the UAV 320. In some examples, AMF 322 may provide information to RAN 321 after determining that the USAA procedure is successful to guide RAN 321 to enable services that support air operations. In some examples, after receiving an indication that the USAA procedure for UAV 320 has been successful, the UE and AMF 322 may establish a PDU session that is configured to convey information that varies from UAV to UAV.

[0160] Certain operations discussed above may be ignored, performed concurrently with other operations, and / or performed in an order different from the order provided above. In some examples, the operations described at arrows 351 to 367 may be performed during the UAV registration procedure—for example, the execution of these operations may be initiated after the operations described at block 341.

[0161] Figure 4 Various aspects of a process for authorizing an unmanned vehicle to operate in a network according to various aspects of the present disclosure are illustrated. Process flow 400 may be performed by a UAV 420 (which may be a UAV 420 as referred to herein). Figures 1 to 3 Process flow 400 may also be performed by RAN 421, AMF 422, SMF 423, UFMS 424, and USS 425 (which may be as described in reference Figure 3 The core network 490 may be an example of a RAN, AMF, SMF, UFMS, and USS described above. Figure 3 An example of a core network 390 of FIG. 490. The radio access system 491 may be Figure 3 An example of a radio access system 391.

[0162] In some examples, process flow 400 illustrates data plane operations for authenticating and authorizing UAV 420, which are incorporated into or performed as part of procedures for registering with a wireless network. In some cases, a UAV controller may perform similar procedures. By using the data plane to perform USAA procedures, a UE coupled to the UAV may communicate with a flight management system using a data session connection (e.g., via an access point providing a connection to UFMS 424) instead of using a proprietary or dedicated connection between the UE, AMF 422 or SMF 423 and UFMS 424. In some cases, using the data plane to perform USAA procedures may enable the USAA procedures to be performed without configuring a direct or dedicated link between the UFMS and the wireless network-for example, an access point may be used to connect a wireless network (or core network) to the UFMS and / or USS. In some cases, the access point providing a connection to the UFMS 424 may also be referred to as an access point name (APN).

[0163] At block 431, a UE coupled to UAV 420 may obtain a UUID and a set of one or more credentials, as described in reference to Figure 3 Block 331 is similarly described.

[0164] At block 433, the UE may perform procedures for registering with the wireless network. In some examples, when registering with the wireless network, the UE and AMF 422 perform the operations described at arrows 333 to 345, and AMF 422 determines to perform USAA procedures for the UE, as described with reference to Figure 3 In some cases, the AMF 422 may register the UE in a "forbidden area" (e.g., the UE may be registered for limited communications via a wireless network (such as communications terminated at an entity of a wireless network core network)), which, for example, enables the UE to communicate with the AMF 422 (e.g., only with the AMF 422). For example, the UE may be assigned to a state in which user plane data for the UE is blocked.

[0165] At block 435, AMF 422, SMF 423, UFMS 424, and USS may establish a correlation between the UE and the pending USAA procedure. In some cases, to correlate the UE with the USAA request, the UE provides a network-specific identifier that UFMS 424 and / or USS 425 may use to align signaling to the wireless network. In some cases, to correlate the UE with the USAA request, AMF 422 signals a correlation ID (e.g., a universal public subscription identifier (GPSI)) to UFMS 424. In some cases, UFMS 424 signals the correlation ID (e.g., GPSI) to USS 422.

[0166] At arrow 437, the UE may transmit a PDU session request message to the AMF 422. At box 439, the AMF 422 may identify an APN that is configured to support unique data signaling for the USAA procedure - for example, the PDU session may not support the transmission of other data types (such as command and control). At arrow 441, the AMF 422 may indicate to the SMF 423 that the USAA procedure is pending for the UE. At arrow 433, the AMF 422 may provide information about the UFMS 424 to the SMF 423. In a certain example, the AMF 422 may indicate to the SMF 423 that the UFMS 424 is configured to perform the USAA procedure for the UAV 420.

[0167] At arrow 445, SMF 423 may send a PDU session establishment response message to AMF 422, and AMF 422 may transmit the PDU session establishment response message to the UE via RAN 421. At block 447, the UE and SMF 423 may establish a limited connectivity PDU session that enables the UE to exchange data with UFMS 424 (e.g., only with UFMS 424).

[0168] At arrow 449, the UE may transmit a USAA request message to the UFMS 424 via the RAN 421 and the data network. In some cases, the USAA request message includes the UUID and flight data of the UAV 420. In some cases, to correlate the UE with the USAA request, the USAA request message includes a correlation ID received from the AMF 422 during the registration procedure. In some cases, the UFMS 424 may signal the correlation ID to the USS 425.

[0169] At block 451, UFMS 424 may verify the received USAA request message, such as by referring to Figure 3 In some cases, the UFMS may map the correlation ID received from the UE to the UUID. At arrow 453, the UE and UFMS 424 may exchange USAA request and USAA response messages, as described in reference to FIG. Figure 3 At block 455, UFMS 424 may attempt to verify the flight data of UAV 420 based on the stored flight data, such as reference Figure 3 At arrow 457, UFMS 424 may send a USAA request message to USS 425, as described in reference to block 357 of FIG. Figure 3 At arrow 459, UFMS 424 may receive a USAA response message from USS 425, as described with reference to FIG. Figure 3 At block 461, UFMS 424 may store the USAA response, as described with reference to Figure 3 Block 363 is similarly described.

[0170] At arrow 463, UFMS 424 may send a USAA confirm message or a USAA reject message via the data network and RAN 421. In some cases, USAA information exchanged between the UE and UFMS 424 may be conveyed via the limited connectivity PDU session established at block 447.

[0171] At block 465, UFMS 424 and / or USS 425 may communicate to the wireless network that the USAA procedure was successful.

[0172] At arrow 467, AMF 422 may modify the registration area of ​​the UE to enable the UE to perform control plane communications with an additional entity other than AMF 422.

[0173] At block 469, AMF 422 and SMF 423 may modify the established limited connectivity PDU session so that the UE may perform communications with entities other than UFMS 424. In some cases, the modified PDU session may enable the UE to perform communications with a controller for UAV 420 (e.g., only with a controller for UAV 420). In some examples, AMF 322 may provide information to RAN 421 to direct RAN 421 to enable services supporting over-the-air operations after determining that the USAA procedure is successful.

[0174] Certain operations discussed above may be ignored, performed concurrently with other operations, and / or performed in an order different from that presented above.

[0175] Figure 5 Various aspects of a process for authorizing an unmanned vehicle to operate in a network according to various aspects of the present disclosure are illustrated. Process flow 500 may be performed by UAV 520 (which may be a UAV 520 as referred to herein). Figures 1 to 4 The process flow 500 may also be performed by RAN 521, AMF 522, SMF 523, UFMS 524 and USS 525 (which may be as described in reference Figure 3 and Figure 4 The core network 590 may be an example of a RAN, AMF, SMF, UFMS, and USS described above. Figure 3 and Figure 4 An example of a core network 390 or a core network 490. The radio access system 591 may be Figure 3 and Figure 4 Examples of radio access system 391 and radio access system 491.

[0176] In some examples, process flow 500 illustrates operations for authenticating and authorizing UAV 520, which are incorporated into or performed as part of a procedure for establishing a data session with a wireless network. In some cases, a UAV controller may perform similar procedures.

[0177] At block 531, a UE coupled to UAV 520 may obtain a UUID and a set of one or more credentials, as described in reference to Figure 3 In block 533, the UE may perform a procedure for registering with the wireless network, as described in reference to Figure 4 Block 433 is similarly described.

[0178] At arrow 535, the UE may transmit a PDU session request message to AMF 522 via RAN 521 to request permission to establish a PDU session (eg, PDN connection) with the wireless network. In some cases, the PDU session request message may indicate a data network configured for USAA operation.

[0179] At arrow 537, AMF 522 may send a PDU session request message to SMF 523 to request SMF 523 to establish a PDU session for the UE. In some cases, the PDU session request message may indicate a data network configured for USAA operation.

[0180] At block 539, SMF 523 may determine that USAA procedures are to be performed for UAV 520 before SMF 523 establishes a PDU session for the UE. At arrow 541, SMF 523 may send a USAA request message to UFMS 524. In some cases, the USAA request message includes the UUID of UAV 520 and / or flight data.

[0181] At block 543, UFMS 524 may verify the received USAA request message, such as by referring to Figure 3 At arrow 545, the UE, SMF 523 and UFMS 524 may exchange USAA request and USAA response messages, as described in reference to FIG. Figure 3 At block 547, UFMS 524 may attempt to verify the flight data of UAV 520 based on the stored flight data, such as reference Figure 3 At arrow 549, UFMS 524 may send a USAA request message to USS 525, as described in reference to block 357 of FIG. Figure 3 At arrow 551, UFMS 524 may receive a USAA response message from USS 525, as described with reference to arrow 359. Figure 3 At block 553, UFMS 524 may store the USAA response, as described with reference to Figure 3 Block 363 is similarly described.

[0182] At arrow 555, UFMS 524 may send a USAA response message to SMF 523 indicating whether UAV 520 has been authenticated and authorized for flight operations.

[0183] At block 557, SMF 523 may establish a user plane connection that provides a data communication path between the UE, UFMS 524, and the controller for UAV 520. In some cases, SMF 523 establishes the user plane connection after (e.g., only after) receiving a USAA response message indicating that UAV 520 has been authenticated and authorized for flight operations. In some examples, the user plane connection may be established so that an exclusive communication path between the indicated controller and the UE is created. In some cases, the exclusive communication path may include UFMS 524 and / or USS 525.

[0184] In some examples, the exclusive communication path is established based on information about the controller provided in the PDU session request message transmitted by the UE at arrow 535. In some cases, the exclusive communication path is established based on address information (e.g., one or more IP addresses, domain names, port numbers, etc.) provided in the USAA response message sent by the UFMS 524 and / or USS 525 at arrow 555. The address information may enable user plane packets to be communicated between the UE and the controller for the UAV 520. In some cases, the UFMS 524 and / or USS 525 generate the address information based on information about the controller included in the PDU session request message transmitted at arrow 535. In some cases, the address information enables user plane packets sent between the UE and the controller to pass through the UFMS 524. In some cases, the SMF 523 establishes packet filters for user plane connections (e.g., based on address information) that ensure that the UE is able to (e.g., is configured to) communicate with the UFMS 524 and the controller (e.g., only with the UFMS 524 and the controller).

[0185] At arrow 559, SMF 523 may transmit a PDU session establishment response message to the UE via AMF 522 and RAN 521. And at block 561, the UE may establish a PDU session with the wireless network based on the user plane connection established by SMF 523. In some cases, the PDU session is released and a new PDU session is established to support the communication of command and control between the UAV 520 and the controller for the UAV 520. In other cases, the PDU session is modified to support the communication of command and control between the UAV 520 and the controller for the UAV 520.

[0186] Certain operations discussed above may be ignored, performed concurrently with other operations, and / or performed in an order different from that presented above.

[0187] Figure 6 Various aspects of a process for authorizing an unmanned vehicle to operate in a network according to various aspects of the present disclosure are illustrated. Process flow 600 may be performed by a UAV 620 (which may be a UAV 620 as referred to herein). Figures 1 to 5 Process flow 600 may also be performed by RAN 621, AMF 622, SMF 623, UFMS 624, and USS 625 (which may be as described in reference Figures 3 to 5 The core network 690 may be an example of a RAN, AMF, SMF, UFMS, and USS described above. Figures 3 to 5 The radio access system 691 may be an example of the core network 390, the core network 490 or the core network 590. Figures 3 to 5 An example of a radio access system 391, a radio access system 491 or a radio access system 591.

[0188] In some examples, process flow 600 illustrates operations for authenticating and authorizing UAV 620, which are incorporated into procedures for registering with a wireless network and procedures for establishing a data session with a wireless network. In some cases, a UAV controller may perform similar procedures.

[0189] At block 631, a UE coupled to UAV 620 may obtain a UUID and a set of one or more credentials, as described in reference to Figure 3 At block 633, the UE may perform a procedure for registering with the wireless network, as described with reference to Figure 4 Block 433 is similarly described.

[0190] At arrow 635, AMF 622 may transmit a USAA request message to the UE via RAN 621 to request the UE to provide the wireless network with information for authenticating and authorizing UAV 320 to perform flight operations.

[0191] At arrow 637, the UE may transmit a USAA response message including information for authenticating the UAV 620 based on the UUID and authorizing the UE to perform flight operations to the MAF 622 via the RAN 621. The USAA response message may include the UUID of the UAV 620 and flight data.

[0192] At arrow 639, AMF 622 may send a USAA request message to UFMS 624 to request that UFMS 624 authenticate and / or authorize UAV 620 for flight operations. In some cases, the USAA request may include the UUID and flight data of UAV 620. In some cases, AMF 622 obtains the UUID and flight data for inclusion in the USAA request from a registration request message transmitted during the UAV registration procedure—e.g., when AMF 322 does not transmit a USAA request at arrow 635. In other cases, AMF 322 obtains the UUID and flight data from a USAA response message transmitted at arrow 637. In some cases, the USAA request message is transmitted using one or more security keys for protecting and verifying the USAA request message.

[0193] At block 641, UFMS 624 may verify that the USAA request message received from AMF 622 is valid—e.g., using the one or more security keys. In some cases, UFMS 624 may use stored information about UAV 620 (e.g., a stored UUID) to determine whether the received USAA message is valid.

[0194] At arrow 643, the UE and UFMS 624 may exchange USAA information. In some examples, UFMS 624 may send a USAA request message to UAV 620, and UAV 620 may send a USAA response message to UFMS 624. In some cases—e.g., where information for performing USAA is obtained by UFMS 624 in a registration request message transmitted during a registration procedure or in a USAA response message transmitted at arrow 637—UAV 620 and UFMS 624 may refrain from exchanging USAA information.

[0195] At block 645, the UFMS 624 may attempt to verify the flight data received from the UAV 620. In some cases, the UFMS 624 may compare the received flight data to the flight data stored for the UAV 620. In some cases, the UFMS 624 may authenticate the identity of the UAV 620 based on the UUID and / or flight data stored for the UAV 620. For example, the UFMS 624 may authenticate the identity of the UAV 620 using information such as the operator identity, the UAV type, the operator location, and the flight path. In some cases, the UFMS 624 may confirm an authorized association between the UAV 620 and the controller for the UAV 620.

[0196] At arrow 647, UFMS 624 may send a USAA request message to USS 625. In some cases, the USAA request message includes the UUID and flight data of UAV 620 and requests that the USS perform USAA procedures. In some examples, UFMS 624 may send the USAA request message after determining that no information about UAV 620 is stored at UFMS 624. In some examples, UFMS 624 may send the USAA request message after an attempt to authenticate UAV 620 fails.

[0197] At arrow 649, UFMS 625 may send a USAA response message to USS 624. In some cases, the USAA response message may include an indication of whether UAV 620 is authentic. In some cases, the USAA response message may include an indication of the duration for which the authentication is valid—e.g., the USAA response message may indicate that UAV 620 is authenticated for the lifetime of UAV 320. In some cases, USS 625 may revoke a persistent authentication at any time.

[0198] In some cases, the USS 625 may provide conditional validity information about the authentication procedure—for example, the USS 625 may indicate information about the controller for the UAV 620, the UAV type and category, the mission type, the location, the pilot identity, the operator identity, the flight plan, etc. In such cases, if the wireless network determines that the flight / mission parameters for the UAV 620 do not meet the conditions (e.g., the UAV 620 deviates from the approved conditions), the wireless network may trigger the USAA procedure for the UAV 620. Having the wireless network initiate the USAA procedure based on conditional authentication may reduce the processing load on the USS 625.

[0199] At block 651, UFMS 624 may store a USAA response message generated by UFMS 624 or received from USS 625. In some examples, UFMS 624 may store flight data of UAV 620 received from USS 625.

[0200] At arrow 653, UFMS 624 may send a USAA response message to AMF 622. In some cases, the USAA response message may include an indication as to whether the authentication procedure was successful and / or flight data of UAV 620 if the procedure was successful.

[0201] At arrow 655, AMF 622 may transmit a USAA confirmation message (if the authentication procedure is successful) or a USAA rejection message (if the authentication procedure is unsuccessful) to the UE coupled to UAV 620 via RAN 621. In some cases, the UE may establish a PDU session with the wireless network based on receiving the USAA confirmation message.

[0202] In some cases, the operations performed from arrow 635 to arrow 655 may be used to authenticate the identity of UAV 620. For example, UFMS 624 and / or USS 625 may use the received UUID and flight data (such as operator identity, operator location, advertised UAV type, flight plan, etc.) to verify that UAV 620 is indeed the UAV associated with the received UUID. In some cases, the operations performed from arrow 635 to arrow 655 may be performed as part of the UAV registration procedure performed at block 633.

[0203] After receiving confirmation that the USAA procedure successfully authenticated the identity of UAV 620 and at arrow 657, the UE may transmit a PDU Session Request message to AMF 622 via RAN 621, as described with reference to FIG. Figure 5 Arrow 535 is similarly described.

[0204] At arrow 659, AMF 622 may transmit a PDU session request message to SMF 623, as shown in FIG. Figure 5 The arrow 537 of is similarly described. In some cases, the AMF 622 may also transmit an indication to the SMF 623 that the USAA procedure is to be performed before establishing a PDU session for the UE.

[0205] At block 661, SMF 623 may determine that USAA procedures are to be performed for UAV 620, as described in reference Figure 5 Block 539 of is similarly described. In some cases, the USAA procedure is performed based on receiving an indication in a PDU session request message received from the AMF 622 that the USAA procedure is to be performed.

[0206] At arrow 663, SMF 623 may send a USAA request message to UFMS 624, as shown in FIG. Figure 5 At block 665, the UFMS may verify the received USAA request message, such as by referring to Figure 5 Block 543 is similarly described.

[0207] At arrow 667, the UE, SMF 623 and UFMS 624 may exchange USAA information, as shown in FIG. Figure 5Arrow 545 is similarly described.

[0208] At block 669, UFMS 624 may attempt to verify the flight data of UAV 520 based on the stored flight data, such as by referring to Figure 5 At arrow 671, UFMS 624 may send a USAA request message to USS 625, as described in reference to block 547 of FIG. Figure 5 At arrow 673, USS 625 may send a USAA response message to UFMS 624, as described with reference to arrow 549. Figure 5 At block 675, UFMS 624 may store the USAA response, as described with reference to Figure 5 At arrow 677, UFMS 624 may send a USAA response message to SMF 623, as described in reference to block 553 of FIG. Figure 5 Arrow 555 is similarly described.

[0209] At block 679, SMF 623 may establish aspects of the user plane connection, as described with reference to Figure 5 At arrow 681, SMF 623 may transmit a PDU session establishment response message to the UE via AMF 622 and RAN 621, as described in reference to FIG. Figure 5 And at block 683, the UE may establish a PDU session with the wireless network, as described with reference to Figure 5 Block 561 is similarly described.

[0210] In some cases, the operations performed from arrow 657 to arrow 681 may be used to authorize the flight plan of UAV 620 before establishing a PDU session for the UE.

[0211] Certain operations discussed above may be ignored, performed concurrently with other operations, and / or performed in an order different from that presented above.

[0212] Figure 7 Various aspects of a process for authorizing an unmanned vehicle to operate in a network according to various aspects of the present disclosure are illustrated. Process flow 700 may be performed by a UAV 720 (which may be a UAV 720 as referred to herein). Figures 1 to 6 Process flow 700 may also be performed by RAN 721 and USS 725 (which may be as described in reference Figures 3 to 6The process flow 700 may also be performed by an MME 726, a PDN GW 727, and a UFCF 728. In some cases, a core network 790 of the PLMN is configured according to a legacy radio system (e.g., a 4G or LTE system) and includes the MME 726 and the PDN GW 727. In some cases, the core network 790 also includes the UFCF 728. In some cases, a flight management system (e.g., Figure 2 The first flight management system 250 of the present invention includes a UFCF 728. In some cases, the UFCF 728 may be a Figures 3 to 6 An example of a UFMS is described. The radio access system 791 may be Figures 3 to 6 An example of a radio access system 391, a radio access system 491, a radio access system 591 or a radio access system 691.

[0213] In some examples, process flow 700 illustrates operations for authenticating and authorizing UAV 720, which are incorporated into the procedures for attaching to a wireless network. In some cases, a UAV controller may perform similar procedures.

[0214] At block 731, a UE coupled to UAV 720 may obtain a UUID and a set of one or more credentials, as described in reference to Figure 3 Block 331 is similarly described.

[0215] At arrow 733, the UE may transmit an attach request message to MME 726 via RAN 721. In some cases, the attach request message may request the wireless network to establish a PDN connection for the UE. In some examples, the attach request message may include an EPS system management (ESM) container and a protocol configuration option (PCO) container. In some cases, the PCO container is a flexible data structure that can be used to convey previously determined (or otherwise unsupported) information and / or information types. In some cases, the name of an access point configured to support UAV operation (e.g., UAV-APN) may be included in the ESM container. In some cases, the UAV-APN is associated with a default bearer that creates an exclusive communication path between the UE and the UFCF 728. Moreover, the UUID and / or flight data of the UAV 720 may be included in the PCO container. In some cases, the flight data includes a flight plan. In some cases, the flight data includes authorization information for and / or information about a controller for UAV 720, such as addresses of user plane data to and from the UAV controller (e.g., a fully qualified domain name (FQDN), one or more IP addresses, etc.).

[0216] At block 735, the MME 726 may authenticate the UE and verify that the UE has a subscription to access the wireless network. In some cases, the MME 726 may determine that the UE is associated with the UAV 720. In some cases, the MME 726 may be configured to decode the PCO information and obtain authorization information from the UFCF 728 if the USAA procedure is successful.

[0217] In block 737, the MME 726 may identify the access point indicated by the UE. In some cases, the access point is an access point configured to support UAV operations. In some cases, the MME 726 identifies a particular access point based on determining that the UE has a subscription to an over-the-air service.

[0218] At arrow 739, MME 726 may send a create session request message to PDN GW 727 to request PDN GW 727 to establish a PDN connection with the UE. In some cases, the create session request message may include a PCO container and encapsulated data.

[0219] At block 741, the PDN GW 727 may identify the UFCF 728 based on the information received in the create session request message. In some examples, the PDN GW 727 identifies the UFCF 728 based on the UUID of the UAV 720.

[0220] At arrow 743, the PDN GW may send a USAA request message to the UFCF 728. In some cases, the USAA request may include the UUID of the UAV 720 and / or flight data.

[0221] At block 745, the UFCF may verify the USAA request message, such as by referring to Figure 3 At arrow 747, the UE and UFCF 728 may exchange USAA information, as described in reference to FIG. Figure 3 At block 749, UFCF 728 may attempt to verify the flight data of UAV 720 based on the stored flight data, such as by referring to Figure 3 At arrow 751, UFCF 728 may send a USAA request message to USS 725, as described in reference to FIG. Figure 3 At arrow 753, UFCF 728 may receive a USAA response message from USS 725, as described with reference to arrow 359. Figure 3 At block 755, UFCF 728 may store the USAA response, as described with reference to Figure 3 Block 363 is similarly described.

[0222] In some cases, after the USAA procedure successfully authenticates the UAV 720 and authorizes the UAV 720 to conduct flight operations and at arrow 757, the UFCF 728 may send a USAA confirmation message to the PDN GW 727 indicating that the USAA procedure for the UAV 720 has been successfully completed. In some cases, the USAA confirmation message includes configuration information for the UE—for example, the message may include information directing the UE to report location continuously or at intervals. In some cases, the USAA confirmation message includes information for the MME 726, such as confirmation of the USAA, information about the validity of the USAA, and / or possible quality of service (QoS) and RAN related information.

[0223] At arrow 759, the PDN GW 727 may send a create session response message to the MME 726. In some cases, the create session response message includes a PCO container containing a USAA response confirming that the UAV 720 is successfully authenticated and authorized to perform flight operations. In some cases, before, simultaneously with, or after sending the create session response message, the PDN GW 727 may establish a user plane connection that provides a data communication path between the UE, the UFCF 728, and the controller for the UAV 720. In some cases, the PDN GW 727 establishes the user plane connection after receiving a USAA response message indicating that the UAV 720 has been authenticated and authorized to perform flight operations (e.g., only after receiving a USAA response message indicating that the UAV 720 has been authenticated and authorized to perform flight operations). In some examples, the user plane connection may be established so that an exclusive communication path between the indicated controller and the UE is created. In some cases, the exclusive communication path may include the UFCF 728 and / or the USS 725.

[0224] In some examples, the exclusive communication path is established based on information about the controller provided in the attach request message transmitted by the UE at arrow 733. In some cases, the exclusive communication path is established based on address information (e.g., one or more IP addresses, domain names, port numbers, etc.) provided in the USAA response message sent by the UFCF 728 and / or USS 725 at arrow 757. The address information may enable user plane packets to be communicated between the UE and the controller for the UAV 720. In some cases, the UFCF 728 and / or USS 725 generate the address information based on information about the controller included in the attach request message transmitted at arrow 733. In some cases, the address information enables user plane packets sent between the UE and the controller to pass through the UFCF 728. In some cases, the PDN GW 727 establishes packet filters for user plane connections (e.g., based on address information) that ensure that the UE is able (e.g., configured to) communicate with the UFMS 524 and the controller (e.g., only with the UFMS 524 and the controller).

[0225] In box 761, MME 726 can verify the USAA response and store the USAA response and configuration information for UAV 720.

[0226] At arrow 763, MME 726 may transmit an Attach Accept message to the UE via RAN 721. In some cases, the Attach Accept message includes a PCO container containing a USAA response confirming that authentication and authorization of UAV 720 has been successful.

[0227] At arrow 765, MME 726 may send an over-the-air service activation message to RAN 721, and RAN 721 may enable UAV-specific services to support a radio connection with the UE. In some cases, MME 726 sends an over-the-air service activation message based on determining that USAA procedures have been successfully executed.

[0228] At block 767, the UE may establish a PDN connection with the wireless network based on receiving the attach accept message. In some cases, establishing the PDN connection includes establishing a default bearer that enables communication between the UE and the UFCF 728.

[0229] At arrow 769, the UE, MME 726, and PDN GW 727 may release the established PDN connection, and at arrow 771, the UE, MME 726, and PDN GW 727 may establish a command and control (C2) PDN connection. In some cases, establishing a C2 PDN connection includes establishing a PDN connection between the UE and the access point named in the attach request. The C2 PDN connection may be a connection for communicating data (e.g., command and control) between the UAV 720 and the controller for the UAV 720. In some cases, establishing a C2 PDN connection includes establishing a dedicated radio bearer that enables communication of data between the UAV 720 and the controller for the UAV 720. In some examples, a first dedicated radio bearer is established for communicating command and control data from the controller to the UAV 720. In some examples, a second radio bearer is established for communicating telemetry and video data from the UAV 720 to the controller. In some cases, establishing the C2 PDN connection includes establishing a dedicated radio bearer that enables data to be communicated between the UAV 720 and the UFCF 728. In some cases, the MME 726 identifies an access point for the PDN connection that is known to the MME 726 (e.g., known only to the MME 726).

[0230] In block 773, instead of releasing and reestablishing the UAV-specific PDN connection, the MME 726 and / or the PDN GW 727 may modify the PDN connection to enable the communication of command and control data. In some examples, the MME 726 and / or the PDN GW 727 establish packet filters that ensure that data of the UAV 720 is communicated with authorized devices (e.g., only with authorized devices (e.g., a controller for the UAV 720)). In some examples, the PDN GW 727 establishes the packet filters based on an authorized association between the UAV 720 and the controller for the UAV 720 confirmed by the UFCF 728.

[0231] In some cases, after USAA procedures fail to authenticate UAV 720 and / or authorize UAV 720 to conduct flight operations and at arrow 775, UFCF 728 may send a USAA reject message to PDN GW 727 indicating that the USAA procedures for UAV 720 failed.

[0232] At arrow 777, the PDN GW 727 may send a create session reject message to the MME 726. In some cases, the create session reject message includes a PCO container including a USAA response indicating that authentication and authorization of the UAV 720 failed.

[0233] At arrow 779, MME 726 may transmit an attach accept message to the UE via RAN 721, wherein the attach accept message may include an error code for the PDN connection. In some cases, the attach accept message may include a PCO container containing a USAA response indicating that authentication and authorization of UAV 720 failed.

[0234] In block 781, the UE may attempt to establish a PDN connection with the MME 726 and the PDN GW 727. In some cases, a valid PDN connection may not be established—for example, because the PDN connection may not address a valid access point. In some examples, the UE may determine that the USAA procedure failed based on the failure to establish the PDN connection. In some cases, the UE may initiate another USAA procedure based on an indication included in the attach accept message directing the UE to initiate an additional USAA procedure. In some cases, the UE may initiate another USAA procedure to the UAV-APN that is used to configure the UUID and credentials. In other cases, the UE may initiate a procedure for establishing a PDN connection with the MME 726, and the MME 726 may use a default access point to perform a USAA procedure that allows connectivity between the UE and the UFCF 728 (e.g., only connectivity between the UE and the UFCF 728).

[0235] In some cases, MME 726 is modified to support the execution of certain operations. For example, MME 726 may be modified to support the ability to process UUID and flight data received in the PCO container. MME 726 may also be modified to support the ability to process USAA responses and perform operations (e.g., transmit air service activation messages) based on processed USAA responses. In some cases, a subset of MMEs in a wireless network is modified to support this functionality for UAVs connected to the wireless network. In some examples, a specific data control network identity is assigned to all UAVs in a wireless network, and an MME (e.g., only MME) with connections to these specific data control networks may be modified to support these additional functionalities. In some examples, an RRC message (e.g., RRC message 5) is modified to include an indication of a device type (e.g., UAV), and RAN 721 is configured to select an MME configured to support UAVs.

[0236] Certain operations discussed above may be ignored, performed concurrently with other operations, and / or performed in an order different from that presented above.

[0237] Figure 8A block diagram 800 of a device 805 that supports authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown. The device 805 can be an example of aspects of a UE 115 as described herein. The device 805 may include a receiver 810, a communication manager 815, and a transmitter 820. The device 805 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0238] The receiver 810 may receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to authorizing unmanned vehicles to operate in the network, etc.). The information may be passed to other components of the device 805. The receiver 810 may be a reference Fig.11 Examples of aspects of the described transceiver 1120. The receiver 810 may utilize a single antenna or a collection of one or more antennas.

[0239] The communication manager 815 can: transmit a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establish a control plane connection with the network based on the network identifier, wherein a request for verification of the air vehicle based on the air identifier is sent to an air function management system; receive a second message from the network in the control plane indicating approval of flight parameters (e.g., a flight path) of the air vehicle, the second message being configured to trigger establishment of a data session between the wireless device and the network; and establish the data session with the network based on the second message.

[0240] The communication manager 815 may also: transmit a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; wherein the first message is configured to establish a data session with the network, and wherein a request to verify the air vehicle based on the first message is sent to an air function management system; receive a second message from the network based on transmitting the first message, the second message including approval of the air vehicle (e.g., positive authentication of the air vehicle, approval of flight parameters of the air vehicle) and configured to trigger establishment of the data session; and establish the data session with the network based on receiving the second message. The communication manager 815 may be an example of aspects of the communication manager 1110 described herein.

[0241] The communication manager 815 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 815 or its subcomponents may be performed by a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device designed to perform the functions described in the present disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0242] The communication manager 815 or its subcomponents may be physically located at various locations, including being distributed such that portions of functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 815 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 815 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0243] The transmitter 820 may transmit signals generated by other components of the device 805. In some examples, the transmitter 820 may be co-located with the receiver 810 in a transceiver module. For example, the transmitter 820 may be a reference Fig.11 Examples of aspects of the described transceiver 1120. The transmitter 820 may utilize a single antenna or a collection of one or more antennas.

[0244] Fig. 9 A block diagram 900 of a device 905 that supports authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a communication manager 915, and a transmitter 965. The device 905 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0245] The receiver 910 may receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to authorizing unmanned vehicles to operate in the network, etc.). The information may be passed to other components of the device 905. The receiver 910 may be a reference Fig.11 Examples of aspects of the described transceiver 1120. Receiver 910 may utilize a single antenna or a collection of one or more antennas.

[0246] The communication manager 915 may be an example of aspects of the communication manager 815 as described herein. The communication manager 915 may include a UAV registration component 935, a UAV control surface component 940, a UAV flight management component 945, a UAV data surface component 950, and a UAV attachment component 960. The communication manager 915 may be an example of aspects of the communication manager 1110 described herein.

[0247] In a first example, the UAV registration component 935 can transmit a first message to the network that includes a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle.

[0248] The UAV control plane component 940 can establish a control plane connection with the network based on the network identifier, wherein a request to verify the air vehicle based on the air identifier is sent to the air capability management system.

[0249] The UAV flight management component 945 may receive (e.g., in a control plane) a second message from the network indicating approval of the air vehicle (e.g., indicating positive authentication of the air vehicle, approval of a flight path for the air vehicle), the second message being configured to trigger establishment of a data session between the wireless device and the network.

[0250] The UAV data plane component 950 can establish a data session with the network based on the second message.

[0251] In a second example, the UAV attachment component 960 may transmit a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the first message is configured to establish a data session with the network, and wherein a request to verify the air vehicle based on the first message is sent to an air functional management system.

[0252] The UAV flight management component 945 may (e.g., in response to the first message) receive a second message from the network indicating approval of the air vehicle (e.g., indicating positive authentication of the air vehicle, approval of a flight path for the air vehicle), the second message being configured to trigger establishment of a data session between the wireless device and the network.

[0253] The UAV data plane component 950 can establish a data session with the network based on receiving the second message.

[0254] The transmitter 965 can transmit signals generated by other components of the device 905. In some examples, the transmitter 965 can be co-located with the receiver 910 in a transceiver module. For example, the transmitter 965 can be a reference Fig.11Examples of aspects of the described transceiver 1120. The transmitter 965 may utilize a single antenna or a collection of one or more antennas.

[0255] Fig.10 A block diagram 1000 of a communication manager 1005 that supports authorization of unmanned vehicles to operate in a network in accordance with aspects of the present disclosure is shown. The communication manager 1005 can be an example of aspects of the communication manager 815, the communication manager 915, or the communication manager 1110 described herein. The communication manager 1005 can include a UAV registration component 1025, a UAV control plane component 1030, a UAV flight management component 1035, a UAV data plane component 1040, and a UAV attachment component 1050. Each of these modules can communicate with each other directly or indirectly (e.g., via one or more buses).

[0256] The UAV registration component 1025 can transmit a first message to the network that includes a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle.

[0257] The UAV control plane component 1030 can establish a control plane connection with the network based on the network identifier, wherein a request to verify the air vehicle based on the air identifier is sent to the air capability management system.

[0258] In some examples, the UAV control surface component 1030 may receive a second message from the network based on transmitting the first message, the second message including a positive authentication of the air vehicle and approval of the flight path of the air vehicle and configured to trigger establishment of the data session.

[0259] The UAV flight management component 1035 can receive in the control plane from the network a second message indicating approval of the flight path of the air vehicle, the second message configured to trigger establishment of a data session between the wireless device and the network.

[0260] In some examples, the UAV flight management component 1035 may receive a third message from the network in the control plane based on the request sent to the airborne functional management system, the third message indicating a positive authentication of the air vehicle and received before the second message.

[0261] In some examples, the UAV flight management component 1035 may identify an access point providing airborne services, wherein a data session is released based on the access point, and a second data session is established based on the access point, wherein an exclusive communication path is established between the wireless device and a controller for the air vehicle via the access point.

[0262] The UAV data plane component 1040 can establish a data session with the network based on the second message.

[0263] In some examples, the UAV data plane component 1040 may establish a data session with the network based on receiving the second message.

[0264] In some examples, the UAV data plane component 1040 transmits a fourth message to the network in the control plane based on receiving the third message, the fourth message being configured to request establishment of a data session and being transmitted prior to the second message.

[0265] The UAV attachment component 1050 may transmit a first message to a network, the first message comprising a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the first message is configured to establish a data session with the network, and wherein a request to verify the air vehicle based on the first message is sent to an air functional management system.

[0266] In some examples, a first indication to an access point is encapsulated in an Evolved Packet System (EPS) Session Management (ESM) container, and an air identifier, operational information about an air vehicle, and a second indication to a controller for the air vehicle are encapsulated in a Protocol Configuration Option (PCO) field.

[0267] In some cases, the first message includes a first indication of an access point providing the air service, an air identifier, operational information about the air vehicle, and a second indication of a controller for the air vehicle.

[0268] Fig.11 A diagram of a system 1100 including a device 1105 that supports authorization of unmanned vehicles to operate in a network according to aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a UE 115 as described herein or include a component of the device 805, a device 905, or a UE 115. The device 1105 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communication manager 1110, an I / O controller 1115, a transceiver 1120, an antenna 1125, a memory 1130, and a processor 1140. These components may be in electronic communication via one or more buses (e.g., a bus 1145).

[0269] The communication manager 815 can: transmit a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establish a control plane connection with the network based on the network identifier, wherein a request for verification of the air vehicle based on the air identifier is sent to an air function management system; receive a second message from the network in the control plane indicating approval of a flight path for the air vehicle, the second message being configured to trigger establishment of a data session between the wireless device and the network; and establish a data session with the network based on the second message.

[0270] The communication manager 815 can also: transmit a first message to the network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; wherein the first message is configured to establish a data session with the network, and wherein a request for verifying the air vehicle based on the first message is sent to the air function management system; receive a second message from the network based on transmitting the first message, the second message including a positive authentication of the air vehicle and approval of the flight path of the air vehicle and configured to trigger establishment of the data session; and establish the data session with the network based on receiving the second message.

[0271] I / O controller 1115 can manage input and output signals for device 1105. I / O controller 1115 can also manage peripheral devices that are not integrated into device 1105. In some cases, I / O controller 1115 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1115 can utilize an operating system, such as Or another known operating system. In other cases, I / O controller 1115 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1115 may be implemented as part of a processor. In some cases, a user may interact with device 1105 via I / O controller 1115 or via hardware components controlled by I / O controller 1115.

[0272] The transceiver 1120 may communicate bidirectionally via one or more antennas, wired or wireless links, as described herein. For example, the transceiver 1120 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1120 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0273] In some cases, a wireless device may include a single antenna 1125. However, in some cases, the device may have more than one antenna 1125, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.

[0274] Memory 1130 may include random access memory (RAM) and read-only memory (ROM). Memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1130 may include, among other things, a basic input / output system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0275] Processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1140 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks that support authorization of unmanned vehicles to operate in a network).

[0276] The code 1135 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1135 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the code 1135 may not be directly executed by the processor 1140, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0277] Fig.12 A block diagram 1200 of a device 1205 supporting authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the core network 130 as described herein. The device 1205 may include a receiver 1210, a communication manager 1215, and a transmitter 1220. The device 1205 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0278] Receiver 1210 may receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to authorizing unmanned vehicles to operate in the network, etc.). The information may be passed to other components of device 1205. Receiver 1210 may be a reference Fig.15 Examples of various aspects of the described transceiver 1520. The receiver 1210 may utilize a single antenna or a collection of one or more antennas.

[0279] The communication manager 1215 can: receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establish a control plane connection with the wireless device based at least in part on the network identifier; send a request to an air function management system in the control plane to verify the air vehicle based on the air identifier, wherein the request includes the air identifier and the operational information; receive a response from the air function management system in the control plane, the response including approval of a flight path for the air vehicle; and establish a data session for the wireless device based on the approval of the flight path.

[0280] The communication manager 1215 can also: receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the message is configured to establish a control plane connection and a data session with the network; determine that the wireless device is coupled to the air vehicle based on the network identifier being associated with an air subscription; send a request to verify the air vehicle to an air function management system based on the determination, wherein the request includes the air identifier and the operational information; receive a response from the air function management system, the response including an affirmative authentication of the air vehicle and an approval of a flight path for the air vehicle; and establish a data session for the wireless device based on the affirmative authentication of the air vehicle and the approval of the flight path. The communication manager 1215 can be an example of aspects of the communication manager 1510 described herein.

[0281] The communication manager 1215 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1215 or its subcomponents may be performed by a general purpose processor, a DSP, an application specific integrated circuit (ASIC), an FPGA or other programmable logic device designed to perform the functions described in the present disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0282] The communication manager 1215 or its subcomponents may be physically located at various locations, including being distributed such that portions of functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 1215 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 1215 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0283] The transmitter 1220 may transmit signals generated by other components of the device 1205. In some examples, the transmitter 1220 may be co-located with the receiver 1210 in a transceiver module. For example, the transmitter 1220 may be a reference Fig.15 Examples of various aspects of the described transceiver 1520. The transmitter 1220 may utilize a single antenna or a collection of one or more antennas.

[0284] Fig.13 A block diagram 1300 of a device 1305 supporting authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the device 1205 or the core network 130 as described herein. The device 1305 may include a receiver 1310, a communication manager 1315, and a transmitter 1345. The device 1305 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0285] Receiver 1310 may receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to authorizing unmanned vehicles to operate in the network, etc.). The information may be passed to other components of device 1305. Receiver 1310 may be a reference Fig.15 Examples of various aspects of the described transceiver 1520. The receiver 1310 may utilize a single antenna or a collection of one or more antennas.

[0286] Communications manager 1315 may be an example of aspects of communications manager 1215 as described herein. Communications manager 1315 may include network registration component 1320, network control plane component 1325, network flight management component 1330, network data plane component 1335, and network attachment component 1340. Communications manager 1315 may be an example of aspects of communications manager 1510 as described herein.

[0287] The network registration component 1320 can receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle.

[0288] The network control plane component 1325 can establish a control plane connection with the wireless device based on the network identifier.

[0289] The network flight management component 1330 can: send a request to the air function management system in the control plane to verify the air vehicle based on the air identifier, wherein the request includes the air identifier and the operation information; and receive a response from the air function management system in the control plane, wherein the response includes approval of the flight path of the air vehicle.

[0290] The network data plane component 1335 can establish a data session for the wireless device based on the approval of the flight path.

[0291] The network attachment component 1340 can receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the message is configured to establish a control plane connection and a data session with the network.

[0292] Network registration component 1320 can determine that the wireless device is coupled to the air vehicle based on the network identifier being associated with an over-the-air subscription.

[0293] The network flight management component 1330 can: based on the determination, send a request to the air functional management system to verify the air vehicle, wherein the request includes the air identifier and the operational information; and receive a response from the air functional management system, the response including a positive authentication of the air vehicle and approval of the flight path of the air vehicle.

[0294] The network data plane component 1335 can establish a data session for the wireless device based on the positive authentication of the air vehicle and the approval of the flight path.

[0295] Transmitter 1345 may transmit signals generated by other components of device 1305. In some examples, transmitter 1345 may be co-located with receiver 1310 in a transceiver module. Fig.15 Examples of various aspects of the described transceiver 1520. The transmitter 1345 may utilize a single antenna or a collection of one or more antennas.

[0296] Fig.14A block diagram 1400 of a communication manager 1405 that supports authorization of an unmanned vehicle to operate in a network in accordance with aspects of the present disclosure is shown. The communication manager 1405 can be an example of aspects of the communication manager 1215, the communication manager 1315, or the communication manager 1510 described herein. The communication manager 1405 can include a network registration component 1410, a network control plane component 1415, a network flight management component 1420, a network data plane component 1425, and a network attachment component 1430. Each of these modules can communicate directly or indirectly with each other (e.g., via one or more buses).

[0297] The network registration component 1410 can receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle.

[0298] In some examples, network registration component 1410 can determine that the wireless device is coupled to the air vehicle based on associating the network identifier with the air subscription.

[0299] In some examples, network registration component 1410 can match the airborne identifier with an entry in an airborne identifier list based on receiving the message.

[0300] In some examples, network registration component 1410 can verify based on the message that the wireless device has a subscription with the network.

[0301] In some examples, network registration component 1410 can determine that the wireless device is coupled to the air vehicle based on the subscription.

[0302] In some examples, the network registration component 1410 may transmit a second message to the wireless device indicating that a procedure for verifying the air vehicle is to be performed before the data session is established and configured to accept registration of the wireless device, wherein the control plane connection is established based on transmitting the second message.

[0303] In some cases, the operational information includes an identity of an operator, characteristics of an air vehicle, instructions to controllers for the air vehicle, a flight path, or any combination thereof.

[0304] The network control plane component 1415 can establish a control plane connection with the wireless device based on the network identifier.

[0305] In some examples, the network control plane component 1415 can assign a state in the control plane to the wireless device based on the over-the-air identifier, wherein user plane data addressed to the wireless device is blocked when the state is assigned to the wireless device.

[0306] In some examples, network control plane component 1415 can remove the state upon establishing the data session.

[0307] In some examples, the network control plane component 1415 may receive a third message from the wireless device based on transmitting the second message, the third message being configured to request establishment of the data session.

[0308] The network flight management component 1420 can send a request to verify the airborne vehicle based on the airborne identifier to the airborne functional management system in the control plane, wherein the request includes the airborne identifier and the operational information.

[0309] In some examples, the network flight management component 1420 receives a response from the airborne functional management system in the control plane, the response including approval of the flight path of the air vehicle.

[0310] In some examples, a request to verify the air vehicle is sent to an airborne functional management system based on the determination, where the request includes the airborne identifier and the operational information.

[0311] In some examples, the network flight management component 1420 can receive a response from the airborne functional management system that includes a positive certification of the air vehicle and approval of the flight path of the air vehicle.

[0312] In some examples, network flight management component 1420 can determine the identity of the airborne functional management system based on the airborne identifier.

[0313] In some examples, network flight management component 1420 can initiate procedures for verifying the air vehicle based on the match.

[0314] In some examples, network flight management component 1420 can determine, based on the air identifier, that a procedure for verifying the air vehicle is to be performed before a data session for the wireless device is established.

[0315] In some examples, network flight management component 1420 can transmit a second message to the wireless device based on establishing the control plane connection, the second message configured to request information for verifying the air vehicle.

[0316] In some examples, network flight management component 1420 can receive an airborne identifier of the airborne vehicle and operational information about the airborne vehicle based on the second message.

[0317] In some examples, network flight management component 1420 can receive a second response from the airborne functionality management system based on sending the request, the second response indicating a positive authentication of the air vehicle and received prior to the response.

[0318] In some examples, network flight management component 1420 may transmit a second message to the wireless device, the second message configured to indicate to the wireless device a positive authentication of the air vehicle based on receiving the second response.

[0319] In some examples, network flight management component 1420 can send a second request for an authorized flight path to the airborne functional management system based on the second message, wherein a response indicating approval of the flight path is received based on sending the second request.

[0320] In some examples, network flight management component 1420 can identify an airborne functional management system based on an airborne identifier.

[0321] In some examples, network flight management component 1420 may transmit a second message to the wireless device based on receiving the response from the airborne functional management system, the second message including affirmative authentication of the air vehicle and approval of the flight path and configured to trigger establishment of the data session.

[0322] In some examples, network flight management component 1420 can identify, based on the message, an access point for routing commands between the wireless device and a controller for the air vehicle.

[0323] In some examples, network flight management component 1420 can verify the authenticity of a response received from the airborne functional management system.

[0324] In some examples, network flight management component 1420 can store configuration information for an air vehicle based on verifying authenticity.

[0325] In some examples, network flight management component 1420 can transmit a second message to the wireless device based on verifying the authenticity of the response, the second message including affirmative authentication of the air vehicle and approval of the flight path and configured to trigger establishment of the data session.

[0326] In some examples, network flight management component 1420 can send a second message to the radio access network based on receiving the response from the airborne functionality management system, the second message including information for supporting a radio connection for the air vehicle.

[0327] In some cases, the second message includes an air identifier of the air vehicle, operational information about the air vehicle, or both.

[0328] The network data plane component 1425 can establish a data session for the wireless device based on the approval of the flight path.

[0329] In some examples, network data plane component 1425 can establish a data session for the wireless device based on positive authentication of the air vehicle and approval of the flight path.

[0330] In some examples, network data plane component 1425 may generate a traffic filter for communications with the wireless device based on receiving a response indicating approval of the flight path, wherein an exclusive communication path between the wireless device and a controller for the air vehicle is established based on the traffic filter.

[0331] In some examples, network data plane component 1425 can receive commands for the air vehicle in a control plane from a controller for the air vehicle based on establishing a data session.

[0332] In some examples, network data plane component 1425 may communicate the command to the air vehicle in the data plane.

[0333] In some examples, network data plane component 1425 may release the data session based on identifying the access point.

[0334] In some examples, the network data plane component 1425 can establish the second data session based on the access point via which the exclusive communication path is established between the wireless device and the controller.

[0335] In some examples, the network data plane component 1425 can generate a traffic filter for communications with the wireless device based on establishing the data session, wherein an exclusive communication path between the wireless device and a controller for the air vehicle is established based on the traffic filter.

[0336] The network attachment component 1430 can receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the message is configured to establish a control plane connection and a data session with the network.

[0337] In some cases, the message includes a first indication of an access point providing the air service and a set of configurable parameters including an air identifier, operational information about the air vehicle, and a second indication of a controller for the air vehicle.

[0338] In some cases, the first indication of the access point is included in an Evolved Packet System (EPS) Session Management (ESM) container and the set of configurable parameters is included in a Protocol Configuration Option (PCO) field.

[0339] Fig.15A diagram of a system 1500 including a device 1505 that supports authorization of unmanned vehicles to operate in a network according to aspects of the present disclosure is shown. The device 1505 may be an example of a device 1205, a device 1305, or a base station 105 as described herein or include components of the above devices. The device 1505 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a network communication manager 1515, a transceiver 1520, an antenna 1525, a memory 1530, a processor 1540, and an inter-station communication manager 1545. These components may be in electronic communication via one or more buses (e.g., bus 1550).

[0340] In some examples, the core network 130 may include a communication manager 1510. The communication manager 1510 may: receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; establish a control plane connection with the wireless device based at least in part on the network identifier; send a request to an air function management system in the control plane to verify the air vehicle based on the air identifier, wherein the request includes the air identifier and the operational information; receive a response from the air function management system in the control plane, the response including approval of a flight path for the air vehicle; and establish a data session for the wireless device based on the approval of the flight path.

[0341] The communication manager 1510 can also: receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the message is configured to establish a control plane connection and a data session with the network; determine that the wireless device is coupled to the air vehicle based on the network identifier being associated with an air subscription; send a request to verify the air vehicle to an air function management system based on the determination, wherein the request includes the air identifier and the operational information; receive a response from the air function management system, the response including an affirmative authentication of the air vehicle and an approval of a flight path for the air vehicle; and establish a data session for the wireless device based on the affirmative authentication of the air vehicle and the approval of the flight path.

[0342] The network communications manager 1515 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1515 may manage the delivery of data communications for client devices, such as one or more UEs 115.

[0343] The transceiver 1520 may communicate bidirectionally via one or more antennas, wired or wireless links, as described herein. For example, the transceiver 1520 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1520 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0344] In some cases, a wireless device may include a single antenna 1525. However, in some cases, the device may have more than one antenna 1525, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.

[0345] Memory 1530 may include RAM, ROM, or a combination thereof. Memory 1530 may store computer readable code 1535 including instructions that, when executed by a processor (e.g., processor 1540), cause the device to perform various functions described herein. In some cases, memory 1530 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0346] Processor 1540 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1540 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1540. Processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to cause device 1505 to perform various functions (e.g., functions or tasks that support authorization of unmanned vehicles to operate in a network).

[0347] The inter-site communication manager 1545 may manage communications with other base stations 105 and may include a controller or scheduler for controlling communications with UE 115 in cooperation with other base stations 105. For example, the inter-site communication manager 1545 may coordinate the scheduling of transmissions to UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, the inter-site communication manager 1545 may provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between base stations 105.

[0348] The code 1535 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1535 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the code 1535 may not be directly executed by the processor 1540, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0349] Fig.16 A block diagram 1600 of a device 1605 that supports authorizing an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown. The device 1605 can be an example of aspects of a flight management system as described herein. In some cases, the device 1605 can be incorporated into a system as described in reference to Fig.15 In some examples, the device 1605 may be incorporated into the core network 130. In other cases, the device 1605 may be in a system 1500 as described above. Fig.15 Described system 1500 is external. In some examples, device 1605 may act as an intermediary device between core network 130 and a flight control system.

[0350] The device 1605 may include a receiver 1610, a communication manager 1615, and a transmitter 1620. The device 1605 may also include a processor. Each of these components may be in communication with each other (eg, via one or more buses).

[0351] Receiver 1610 may receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to authorizing unmanned vehicles to operate in the network, etc.). The information may be passed to other components of device 1605. Receiver 1610 may utilize a single antenna or a collection of one or more antennas.

[0352] Communications manager 1615 may include UFMS flight management component 1625, UFMS authentication component 1630, UFMS authorization component 1635, and UFMS authentication and authorization component 1640. Each of these modules may communicate with each other directly or indirectly (eg, via one or more buses).

[0353] The UFMS flight management component 1625 can receive a request from the network to verify an air vehicle coupled to the wireless device, the request including an air identifier of the air vehicle and operational information about the air vehicle.

[0354] In some examples, the UFMS flight management component 1625 may receive a request from the network to verify an air vehicle coupled to the wireless device while a procedure for establishing a data session is being executed between the network and the wireless device, the request including an air identifier of the air vehicle and operational information about the air vehicle.

[0355] In some cases, the request includes a first set of credentials for the air vehicle, and wherein the authenticity of the request is verified based on the first set of credentials.

[0356] The UFMS authentication component 1630 can verify the identity of the air vehicle based on the air identifier and the operational information.

[0357] In some examples, UFMS authentication component 1630 can send a first response to the network including an affirmative authentication of the air vehicle, wherein procedures for establishing a data session are initiated between the network and the wireless device based on the first response.

[0358] In some examples, UFMS authentication component 1630 can verify the authenticity of the request to verify the air vehicle.

[0359] In some examples, UFMS authentication component 1630 can identify second operational information about the air vehicle and a second air identifier stored at the air functionality management system based on receiving the request to verify the air vehicle.

[0360] In some examples, UFMS authentication component 1630 may compare the operational information to the second operational information and compare the air identifier to the second air identifier, wherein the identity of the air vehicle is authenticated based on the operational information matching the second operational information and the air identifier matching the second air identifier.

[0361] In some examples, UFMS authentication component 1630 may send the air identifier and operational information to the flight control system.

[0362] In some examples, the UFMS certification component 1630 can receive a third response from the flight control system that includes a positive certification of the air vehicle and is received prior to sending the first response.

[0363] In some examples, UFMS authentication component 1630 can identify second operational information about the air vehicle and a second air identifier stored at the air functionality management system based on receiving the request to verify the air vehicle.

[0364] In some examples, UFMS authentication component 1630 may compare the operational information to the second operational information and compare the air identifier to the second air identifier, wherein the identity of the air vehicle is authenticated based on the operational information matching the second operational information and the air identifier matching the second air identifier.

[0365] In some examples, UFMS authentication component 1630 may send the air identifier and operational information to the flight control system.

[0366] In some examples, UFMS certification component 1630 can receive a second response from the flight control system that includes a positive certification of the air vehicle and is received prior to sending the response.

[0367] The UFMS authentication component 1635 can receive a second request for a flight path of an authorized air vehicle from the network based on sending the first response.

[0368] In some examples, UFMS certification component 1635 may send a second response to the network including approval of the flight path based on the second request.

[0369] The UFMS authentication and authorization component 1640 may verify the identity of the air vehicle and the flight path of the air vehicle based on the air identifier and operational information included in the request.

[0370] In some examples, UFMS authentication and authorization component 1640 can send a response to the network based on the verification, the response including affirmative authentication of the air vehicle and approval of the flight path.

[0371] In some examples, UFMS authentication and authorization component 1640 can verify the authenticity of the request to verify the air vehicle.

[0372] In some cases, the request includes a first set of credentials for the air vehicle, and wherein the authenticity of the request is verified based on the first set of credentials.

[0373] The communication manager 1615 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1615 or its subcomponents may be performed by a general purpose processor, a DSP, an application specific integrated circuit (ASIC), an FPGA or other programmable logic device designed to perform the functions described in this disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0374] The communication manager 1615 or its subcomponents may be physically located at various locations, including being distributed such that portions of functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 1615 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 1615 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0375] Transmitter 1620 may transmit signals generated by other components of device 1605. In some examples, transmitter 1620 may be co-located in a transceiver module with receiver 1610. Transmitter 1620 may utilize a single antenna or a collection of one or more antennas.

[0376] Fig.17 A flow chart illustrating a method 1700 for supporting authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by the base station 105 or components thereof as described herein. For example, the operations of the method 1700 may be implemented by the base station 105 or components thereof as described herein. Figures 12 to 15 In some examples, a base station may execute a set of one or more instructions to control functional elements of the base station to perform the functions described herein. Additionally or alternatively, a base station may use dedicated hardware to perform various aspects of the functions described herein.

[0377] At 1705, a base station may receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle. The operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Figures 12 to 15 The described network registration component is performed.

[0378] At 1710, the base station may establish a control plane connection with the wireless device based on the network identifier. The operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Figures 12 to 15 The described network control plane components are performed.

[0379] At 1715, the base station may send a request to the air function management system in the control plane to verify the air vehicle based on the air identifier, wherein the request includes the air identifier and the operation information. The operations of 1715 may be performed according to the methods described herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Figures 12 to 15 The described network flight management component is used to perform.

[0380] At 1720, the base station may receive a response from the airborne functional management system in the control plane, the response including approval of the flight path of the air vehicle. The operations of 1720 may be performed according to the methods described herein. In some examples, aspects of the operations of 1720 may be performed as described with reference to Figures 12 to 15 The described network flight management component is used to perform.

[0381] At 1725, the base station may establish a data session for the wireless device based on the approval of the flight path. The operations of 1725 may be performed according to the methods described herein. In some examples, aspects of the operations of 1725 may be performed as described with reference to Figures 12 to 15 The described network data plane components are performed.

[0382] Fig.18 1 is a flow chart illustrating a method 1800 for supporting authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure. The operations of the method 1800 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE 115 or a component thereof as described herein. Figures 8 to 11 In some examples, the UE may execute a set of one or more instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0383] At 1805, the UE may receive a request from the network to verify an air vehicle coupled to the wireless device, the request including an air identifier of the air vehicle and operational information about the air vehicle. The operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be performed as described with reference to Figures 8 to 11 The described UFMS flight management components are implemented.

[0384] At 1810, the UE may verify the identity of the air vehicle based on the air identifier and the operational information. The operations of 1810 may be performed according to the methods described herein. In some examples, aspects of the operations of 1810 may be performed as described with reference to Figures 8 to 11 The described UFMS certification components are implemented.

[0385] At 1815, the UE may send a first response to the network including a positive authentication of the air vehicle, wherein a procedure for establishing a data session is initiated between the network and the wireless device based on the first response. The operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Figures 8 to 11 The described UFMS certification components are implemented.

[0386] At 1820, the UE may receive from the network a second request to authorize a flight path for the air vehicle based on sending the first response. The operations of 1820 may be performed according to the methods described herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Figures 8 to 11 The UFMS authorization components described are executed.

[0387] At 1825, the UE sends a second response to the network including approval of the flight path based on the second request. The operations of 1825 may be performed according to the methods described herein. In some examples, aspects of the operations of 1825 may be performed as described with reference to Figures 8 to 11 The UFMS authorization components described are executed.

[0388] Fig.19 A flow chart illustrating a method 1900 for supporting authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE 115 or a component thereof as described herein. Figures 8 to 11 In some examples, the UE may execute a set of one or more instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0389] At 1905, the UE may transmit a first message to the network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle. The operations of 1905 may be performed according to the methods described herein. In some examples, aspects of the operations of 1905 may be performed as described with reference to Figures 8 to 11 The described UAV registration component is performed.

[0390] At 1910, the UE may establish a control plane connection with the network based on the network identifier, wherein a request to verify the air vehicle based on the air identifier is sent to an air function management system. The operations of 1910 may be performed according to the methods described herein. In some examples, aspects of the operations of 1910 may be performed as described with reference to Figures 8 to 11 The described UAV control surface assembly is implemented.

[0391] At 1915, the UE may receive, in the control plane, from the network a second message indicating approval of the flight path of the air vehicle, the second message being configured to trigger establishment of a data session between the wireless device and the network. The operations of 1915 may be performed according to the methods described herein. In some examples, aspects of the operations of 1915 may be performed as described with reference to Figures 8 to 11 The described UAV flight management component is performed.

[0392] At 1920, the UE may establish the data session with the network based on the second message. The operations of 1920 may be performed according to the methods described herein. In some examples, aspects of the operations of 1920 may be performed as described with reference to Figures 8 to 11 The described UAV data plane component is implemented.

[0393] Fig. 20 A flow chart illustrating a method 2000 for supporting authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 2000 may be implemented by a base station 105 or components thereof as described herein. Figures 12 to 15 In some examples, a base station may execute a set of one or more instructions to control functional elements of the base station to perform the functions described herein. Additionally or alternatively, a base station may use dedicated hardware to perform various aspects of the functions described herein.

[0394] At 2005, a base station may receive a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the message is configured to establish a control plane connection and a data session with the network. The operations of 2005 may be performed according to the methods described herein. In some examples, aspects of the operations of 2005 may be performed as described with reference to Figures 12 to 15 The described network attachment components are performed.

[0395] At 2010, the base station may determine that the wireless device is coupled to the air vehicle based on the network identifier being associated with the air subscription. The operations of 2010 may be performed according to the methods described herein. In some examples, aspects of the operations of 2010 may be performed as described with reference to Figures 12 to 15 The described network registration component is performed.

[0396] At 2015, the base station sends a request to verify the air vehicle to the air function management system based on the determination, wherein the request includes the air identifier and the operation information. The operations of 2015 may be performed according to the methods described herein. In some examples, various aspects of the operations of 2015 may be performed as described with reference to Figures 12 to 15 The described network flight management component is used to perform.

[0397] At 2020, the base station receives a response from the airborne functional management system, the response including a positive authentication of the air vehicle and approval of the flight path of the air vehicle. The operations of 2020 may be performed according to the methods described herein. In some examples, aspects of the operations of 2020 may be performed as described with reference to Figures 12 to 15 The described network flight management component is used to perform.

[0398] At 2025, the base station may establish a data session for the wireless device based on the positive authentication of the air vehicle and the approval of the flight path. The operations of 2025 may be performed according to the methods described herein. In some examples, aspects of the operations of 2025 may be performed as described with reference to Figures 12 to 15 The described network data plane components are performed.

[0399] Fig.21 1 is a flow chart illustrating a method 2100 for supporting authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure. The operations of the method 2100 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 2100 may be implemented by a UE 115 or a component thereof as described herein. Figures 8 to 11 In some examples, the UE may execute a set of one or more instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0400] At 2105, the UE receives a request from the network to verify an air vehicle coupled to the wireless device while a procedure for establishing a data session is being performed between the network and the wireless device, the request including an air identifier of the air vehicle and operational information about the air vehicle. The operations of 2105 may be performed according to the methods described herein. In some examples, aspects of the operations of 2105 may be performed as described with reference to Figures 8 to 11 The described UFMS flight management components are implemented.

[0401] At 2110, the UE may verify the identity of the air vehicle and the flight path of the air vehicle based on the air identifier and operational information included in the request. The operations of 2110 may be performed according to the methods described herein. In some examples, aspects of the operations of 2110 may be performed as described with reference to Figures 8 to 11 The described UFMS authentication and authorization components are implemented.

[0402] At 2115, the UE may send a response to the network based on the verification, the response including a positive authentication of the air vehicle and approval of the flight path. The operations of 2115 may be performed according to the methods described herein. In some examples, aspects of the operations of 2115 may be performed as described with reference to Figures 8 to 11 The described UFMS authentication and authorization components are implemented.

[0403] Fig. 22 A flow chart illustrating a method 2200 for supporting authorization of an unmanned vehicle to operate in a network according to aspects of the present disclosure is shown. The operations of the method 2200 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 2200 may be implemented by a UE 115 or a component thereof as described herein. Figures 8 to 11 In some examples, the UE may execute a set of one or more instructions to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0404] At 2205, the UE may transmit a first message to the network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein the first message is configured to establish a data session with the network, and wherein a request to verify the air vehicle based on the first message is sent to the air function management system. The operations of 2205 may be performed according to the methods described herein. In some examples, aspects of the operations of 2205 may be performed as described with reference to Figures 8 to 11 The described UAV attachment assembly is performed.

[0405] At 2210, the UE may receive a second message from the network based on transmitting the first message, the second message including a positive authentication of the air vehicle and an approval of the flight path of the air vehicle and configured to trigger establishment of the data session. The operations of 2210 may be performed according to the methods described herein. In some examples, aspects of the operations of 2210 may be performed as described with reference to Figures 8 to 11 The described UAV control surface assembly is implemented.

[0406] At 2215, the UE may establish the data session with the network based on the second message. The operations of 2215 may be performed according to the methods described herein. In some examples, aspects of the operations of 2215 may be performed as described with reference to Figures 8 to 11 The described UAV data plane component is implemented.

[0407] The following provides an overview of various aspects of the disclosure:

[0408] Aspect 1: A method for wireless communication at a network, comprising: receiving a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; determining that the wireless device is coupled to the air vehicle based at least in part on the network identifier being associated with an air subscription; sending a request to an air function management system to verify the air vehicle based at least in part on the determination, wherein the request includes the air identifier and the operational information; receiving a response from the air function management system, the response including approval of the air vehicle based at least in part on the air identifier and the operational information; and establishing a data session for the wireless device based at least in part on the approval of the air vehicle.

[0409] Aspect 2: The method of aspect 1 further comprises: identifying the air functionality management system based at least in part on the air identifier.

[0410] Aspect 3: The method of any one of Aspects 1 to 2 further comprises: transmitting a second message to the wireless device based at least in part on receiving the response from the air function management system, the second message comprising the approval of the air vehicle and configured to trigger establishment of the data session.

[0411] Aspect 4: The method of any one of Aspects 1 to 3 further includes: identifying an access point for routing commands between the wireless device and the controller for the air vehicle based at least in part on the message; releasing the data session based at least in part on identifying the access point; and establishing a second data session based at least in part on the access point, wherein an exclusive communication path is established between the wireless device and the controller via the access point.

[0412] Aspect 5: The method of any one of Aspects 1 to 4 further includes: generating a traffic filter for communicating with the wireless device based at least in part on establishing the data session or receiving the response indicating the approval of the air vehicle, or both, wherein an exclusive communication path between the wireless device and the controller for the air vehicle is established at least in part based on the traffic filter.

[0413] Aspect 6: The method of any one of Aspects 1 to 5 further includes: verifying the authenticity of the response received from the air functional management system; storing configuration information for the air vehicle based at least in part on verifying the authenticity; and transmitting a second message to the wireless device based at least in part on verifying the authenticity of the response, the second message including the approval of the air vehicle and configured to trigger establishment of the data session.

[0414] Aspect 7: The method of any one of Aspects 1 to 6, further comprising: sending a second message to the radio access network based at least in part on receiving the response from the air functionality management system, the second message comprising information for supporting a radio connection of the air vehicle.

[0415] Aspect 8: A method as in any one of Aspects 1 to 7, wherein the message comprises a first indication of an access point providing air service and a configurable parameter set, the configurable parameter set comprising the air identifier, the operational information about the air vehicle, and a second indication of a controller for the air vehicle.

[0416] Aspect 9: The method of aspect 8, wherein the first indication of the access point is included in an evolved packet system (EPS) session management (ESM) container, and the configurable parameter set is included in a protocol configuration option (PCO) field.

[0417] Aspect 10: The method of any one of Aspects 1 to 9, further comprising: determining the identity of the air function management system based at least in part on the air identifier; and establishing a control plane connection with the wireless device based at least in part on the network identifier.

[0418] Aspect 11: The method of Aspect 10 further includes: verifying that the wireless device has a subscription with the network based at least in part on the message; determining that the wireless device is coupled to the air vehicle based at least in part on the subscription; and determining, based at least in part on the air identifier, a procedure for verifying the air vehicle to be performed before the data session for the wireless device is established.

[0419] Aspect 12: A method as in Aspect 11, wherein the message is configured to request registration with the network, the method further comprising: transmitting a second message to the wireless device, the second message indicating that the procedure for verifying the air vehicle is to be performed before the data session is established and configured to accept registration of the wireless device, wherein the control plane connection is established at least in part based on transmitting the second message.

[0420] Aspect 13: The method of any one of Aspects 10 to 12 further comprises: assigning a state to the wireless device in a control plane based at least in part on the air identifier, wherein when the state is assigned to the wireless device, user plane data addressed to the wireless device is blocked; and removing the state when establishing the data session.

[0421] Aspect 14: The method of any one of Aspects 10 to 13 further includes: transmitting a second message to the wireless device based at least in part on establishing the control plane connection, the second message being configured to request information for verifying the air vehicle; and receiving the air identifier of the air vehicle and the operational information about the air vehicle based at least in part on the second message.

[0422] Aspect 15: The method of any one of Aspects 1 to 14, further comprising: matching the airborne identifier with an entry in an airborne identifier list based at least in part on receiving the message; and initiating a procedure for verifying the airborne vehicle based at least in part on the match.

[0423] Aspect 16: The method of any one of Aspects 1 to 15, wherein the operational information includes an identity of an operator, characteristics of the air vehicle, instructions for a controller for the air vehicle, a flight path, or any combination thereof.

[0424] Aspect 17: A method as described in any of Aspects 1 to 16, wherein receiving the response including the approval of the air vehicle includes: receiving a first response indicating an affirmative authentication of the air vehicle; and receiving a second response indicating approval of the flight path of the air vehicle, the second response being received after the first response, and wherein the method further includes: transmitting a second message to the wireless device, the second message being configured to indicate to the wireless device an affirmative authentication of the air vehicle based at least in part on receiving the first response.

[0425] Aspect 18: The method of aspect 17, further comprising: receiving a third message from the wireless device based at least in part on transmitting the second message, the third message being configured to request establishment of the data session.

[0426] Aspect 19: The method of Aspect 18 further includes: sending a second request to the airborne functional management system to authorize the flight path based at least in part on the second message, wherein the second response indicating approval of the flight path is received based at least in part on sending the second request.

[0427] Aspect 20: The method of any one of Aspects 1 to 19, further comprising: receiving a command for the air vehicle from a controller for the air vehicle in a data plane based at least in part on establishing the data session; and transmitting the command to the air vehicle in the data plane.

[0428] Aspect 21: A method for wireless communication at a wireless device coupled to an air vehicle, comprising: transmitting a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; receiving a second message from the network based at least in part on transmitting the first message, the second message including approval of the air vehicle by an air functional management system and configured to trigger establishment of a data session; and establishing the data session with the network based at least in part on receiving the second message.

[0429] Aspect 22: The method of aspect 21, wherein the first message includes a first indication of an access point providing air service, the air identifier, the operational information about the air vehicle, and a second indication of a controller for the air vehicle.

[0430] Aspect 23: The method of Aspect 22 further includes: encapsulating the first indication of the access point in an Evolved Packet System (EPS) Session Management (ESM) container, and encapsulating the air identifier, the operation information about the air vehicle, and the second indication of the controller for the air vehicle in a Protocol Configuration Option (PCO) field.

[0431] Aspect 24: The method of any one of Aspects 21 to 23 further includes: identifying an access point providing air service, wherein the data session is released at least in part based on the access point, and a second data session is established at least in part based on the access point, wherein an exclusive communication path is established between the wireless device and the controller for the air vehicle via the access point.

[0432] Aspect 25: The method of any one of Aspects 21 to 24, further comprising: establishing a control plane connection with the network based at least in part on the network identifier.

[0433] Aspect 26: The method of Aspect 25 further includes: receiving a third message from the network in the control plane based at least in part on the request sent to the air functional management system, the third message indicating a positive authentication of the air vehicle and being received before the second message; and transmitting a fourth message to the network in the control plane based at least in part on receiving the third message, the fourth message being configured to request establishment of the data session and being transmitted before the second message.

[0434] Aspect 27: An apparatus for wireless communication at a network, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any one of Aspects 1 to 20.

[0435] Aspect 28: An apparatus for wireless communication at a network, comprising at least one means for performing the method of any one of Aspects 1 to 20.

[0436] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication at a network, the code comprising instructions executable by a processor to perform the method of any one of aspects 1 to 20.

[0437] Aspect 30: An apparatus for wireless communication at a wireless device coupled to an aerial vehicle, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as described in any one of Aspects 21 to 26.

[0438] Aspect 31: An apparatus for wireless communication at a wireless device coupled to an air vehicle, comprising at least one means for performing the method of any one of Aspects 21 to 26.

[0439] Aspect 32: A non-transitory computer-readable medium storing code for wireless communication at a wireless device coupled to an air vehicle, the code comprising instructions executable by a processor to perform the method of any one of Aspects 21 to 26.

[0440] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0441] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applied to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0442] The information and signals described herein may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0443] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0444] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Other examples and implementations fall within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0445] Computer readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to transfer from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.As an example and not limitation, non-transient computer readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used to carry or store instruction or data structure form of desired program code means and can be accessed by general or special-purpose computer or general or special-purpose processor any other non-transient medium.Similarly, any connection is also properly referred to as computer readable medium.For example, if software is transmitted from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then the coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are just included in the definition of computer readable medium. Disk and disc as used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0446] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0447] In the accompanying drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number that distinguishes between similar components. If only the first reference number is used in the specification, the description may apply to any of the similar components having the same first reference number regardless of the second reference number, or other subsequent reference numbers.

[0448] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that can be implemented or fall within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration" and does not mean "better than" or "better than other examples." This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0449] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the universal principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a network, comprising: receiving a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information regarding the air vehicle; determining that the wireless device is coupled to the air vehicle based at least in part on associating the network identifier with an over-the-air subscription; sending a request to verify the air vehicle to an airborne functional management system based at least in part on the determination, wherein the request includes the airborne identifier and the operational information; as well as A response is received from the air functionality management system, the response including approval of the air vehicle based at least in part on the air identifier and the operational information.

2. The method of claim 1, further comprising: A data session is established for the wireless device based at least in part on the approval of the air vehicle.

3. The method of claim 1, further comprising: The over-the-air functionality management system is identified based at least in part on the over-the-air identifier.

4. The method of claim 2, further comprising: Based at least in part on receiving the response from the air functionality management system, a second message is transmitted to the wireless device, the second message including the approval of the air vehicle and configured to trigger establishment of the data session.

5. The method of claim 2, further comprising: identifying, based at least in part on the message, an access point for routing commands between the wireless device and a controller for the air vehicle; releasing the data session based at least in part on identifying the access point; as well as A second data session is established based at least in part on the access point, wherein an exclusive communication path is established between the wireless device and the controller via the access point.

6. The method of claim 2, further comprising: A traffic filter for communications with the wireless device is generated based at least in part on establishing the data session or receiving the response indicating the approval of the air vehicle, or both, wherein an exclusive communication path between the wireless device and a controller for the air vehicle is established based at least in part on the traffic filter.

7. The method of claim 2, further comprising: verifying the authenticity of said response received from said air functional management system; storing configuration information for the air vehicle based at least in part on verifying the authenticity; as well as Based at least in part on verifying the authenticity of the response, transmitting a second message to the wireless device, the second message including the approval of the air vehicle and configured to trigger establishment of the data session.

8. The method of claim 1, further comprising: A second message is sent to a radio access network based at least in part on receiving the response from the air functionality management system, the second message including information for supporting a radio connection of an air vehicle.

9. The method of claim 1 , wherein the message comprises a first indication of an access point providing air service and a configurable parameter set comprising the air identifier, the operational information about the air vehicle, and a second indication of a controller for the air vehicle.

10. The method of claim 9, wherein the first indication of the access point is included in an Evolved Packet System (EPS) Session Management (ESM) container and the set of configurable parameters is included in a Protocol Configuration Option (PCO) field.

11. The method of claim 2, further comprising: determining an identity of the air functionality management system based at least in part on the air identifier; as well as A control plane connection is established with the wireless device based at least in part on the network identifier.

12. The method of claim 11, further comprising: verifying, based at least in part on the message, that the wireless device has a subscription with the network; determining that the wireless device is coupled to the air vehicle based at least in part on the subscription; as well as A procedure for verifying the air vehicle is to be performed before the data session for the wireless device is established based at least in part on the air identifier.

13. The method of claim 12, wherein the message is configured to request registration with the network, the method further comprising: A second message is transmitted to the wireless device, the second message indicating that the procedure for verifying the air vehicle is to be performed before the data session is established and configured to accept registration of the wireless device, wherein the control plane connection is established based at least in part on transmitting the second message.

14. The method of claim 11, further comprising: assigning a state in a control plane to the wireless device based at least in part on the over-the-air identifier, wherein user plane data addressed to the wireless device is blocked when the state is assigned to the wireless device; as well as The state is removed upon establishment of the data session.

15. The method of claim 11, further comprising: transmitting, based at least in part on establishing the control plane connection, a second message to the wireless device, the second message configured to request information for verifying the air vehicle; as well as The airborne identifier of the airborne vehicle and the operational information regarding the airborne vehicle are received based at least in part on the second message.

16. The method of claim 1, further comprising: matching the airborne identifier to an entry in an airborne identifier list based at least in part on receiving the message; as well as A procedure for verifying the air vehicle is initiated based at least in part on the match.

17. The method of claim 1, wherein the operational information includes an identity of an operator, characteristics of the air vehicle, instructions to a controller for the air vehicle, a flight path, or any combination thereof.

18. The method of claim 2, wherein receiving the response including the approval of the air vehicle comprises: receiving a first response indicating a positive authentication of the air vehicle; as well as receiving a second response indicating approval of the flight path of the air vehicle, the second response being received after the first response, And wherein the method further comprises: A second message is transmitted to the wireless device, the second message configured to indicate to the wireless device a positive authentication of the air vehicle based at least in part on receiving the first response.

19. The method of claim 18, further comprising: Based at least in part on transmitting the second message, a third message is received from the wireless device, the third message configured to request establishment of the data session.

20. The method of claim 19, further comprising: A second request to authorize the flight path is sent to the airborne functional management system based at least in part on the second message, wherein the second response indicating approval of the flight path is received based at least in part on sending the second request.

21. The method of claim 2, further comprising: receiving, in a data plane, a command for the air vehicle from a controller for the air vehicle based at least in part on establishing the data session; as well as The command is transmitted to the air vehicle in the data plane.

22. A method for wireless communication at a wireless device coupled to an air vehicle, comprising: transmitting a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle; as well as A second message is received from the network based at least in part on transmitting the first message, the second message including approval of the air vehicle by an air capability management system and configured to trigger establishment of a data session.

23. The method of claim 22, further comprising: The data session is established with the network based at least in part on receiving the second message.

24. The method of claim 22, wherein the first message includes a first indication of an access point providing air service, the air identifier, the operational information about the air vehicle, and a second indication of a controller for the air vehicle.

25. The method of claim 24, further comprising: The first indication to the access point is encapsulated in an Evolved Packet System (EPS) Session Management (ESM) container, and the air identifier, the operational information about the air vehicle, and the second indication to the controller for the air vehicle are encapsulated in a Protocol Configuration Option (PCO) field.

26. The method of claim 22, further comprising: An access point providing an airborne service is identified, wherein the data session is released based at least in part on the access point, and a second data session is established based at least in part on the access point, wherein an exclusive communication path is established between the wireless device and a controller for the airborne vehicle via the access point.

27. The method of claim 22, further comprising: A control plane connection is established with the network based at least in part on the network identifier.

28. The method of claim 27, wherein a request to verify the air vehicle based at least in part on the first message is sent to an airborne functional management system, and the method further comprises: receiving, in a control plane, a third message from the network based at least in part on the request sent to the air functionality management system, the third message indicating a positive authentication of the air vehicle and received before the second message; as well as A fourth message is transmitted in the control plane to the network based at least in part on receiving the third message, the fourth message being configured to request establishment of the data session and being transmitted prior to the second message.

29. An apparatus for wireless communication at a network, comprising: processor, a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a message from a wireless device coupled to an air vehicle, the message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information regarding the air vehicle; determining that the wireless device is coupled to the air vehicle based at least in part on associating the network identifier with an over-the-air subscription; sending a request to verify the air vehicle to an airborne functional management system based at least in part on the determination, wherein the request includes the airborne identifier and the operational information; as well as A response is received from the air functionality management system, the response including approval of the air vehicle based at least in part on the air identifier and the operational information.

30. The apparatus of claim 29, wherein the instructions are further executable by the processor to cause the apparatus to: A data session is established for the wireless device based at least in part on the approval of the air vehicle.

31. The apparatus of claim 29, wherein the instructions are further executable by the processor to cause the apparatus to: The over-the-air functionality management system is identified based at least in part on the over-the-air identifier.

32. The apparatus of claim 30, wherein the instructions are further executable by the processor to cause the apparatus to: Based at least in part on receiving the response from the air functionality management system, a second message is transmitted to the wireless device, the second message including the approval of the air vehicle and configured to trigger establishment of the data session.

33. The apparatus of claim 30, wherein the instructions are further executable by the processor to cause the apparatus to: identifying, based at least in part on the message, an access point for routing commands between the wireless device and a controller for the air vehicle; releasing the data session based at least in part on identifying the access point; as well as A second data session is established based at least in part on the access point, wherein an exclusive communication path is established between the wireless device and the controller via the access point.

34. The apparatus of claim 30, wherein the instructions are further executable by the processor to cause the apparatus to: A traffic filter for communications with the wireless device is generated based at least in part on establishing the data session or receiving the response indicating the approval of the air vehicle, or both, wherein an exclusive communication path between the wireless device and a controller for the air vehicle is established based at least in part on the traffic filter.

35. The apparatus of claim 30, wherein the instructions are further executable by the processor to cause the apparatus to: verifying the authenticity of said response received from said air functional management system; storing configuration information for the air vehicle based at least in part on verifying the authenticity; and Based at least in part on verifying the authenticity of the response, transmitting a second message to the wireless device, the second message including the approval of the air vehicle and configured to trigger establishment of the data session.

36. The apparatus of claim 29, wherein the instructions are further executable by the processor to cause the apparatus to: A second message is sent to a radio access network based at least in part on receiving the response from the air functionality management system, the second message including information for supporting a radio connection of an air vehicle.

37. An apparatus as described in claim 29, wherein the message includes a first indication of an access point providing air service and a configurable parameter set, the configurable parameter set including the air identifier, the operational information about the air vehicle, and a second indication of a controller for the air vehicle.

38. The apparatus of claim 37, wherein the first indication of the access point is included in an Evolved Packet System (EPS) Session Management (ESM) container and the set of configurable parameters is included in a Protocol Configuration Options (PCO) field.

39. The apparatus of claim 30, wherein the instructions are further executable by the processor to cause the apparatus to: determining an identity of the air functionality management system based at least in part on the air identifier; and A control plane connection is established with the wireless device based at least in part on the network identifier.

40. The apparatus of claim 39, wherein the instructions are further executable by the processor to cause the apparatus to: verifying, based at least in part on the message, that the wireless device has a subscription with the network; determining that the wireless device is coupled to the air vehicle based at least in part on the subscription; as well as A procedure for verifying the air vehicle is to be performed before the data session for the wireless device is established based at least in part on the air identifier.

41. The apparatus of claim 40, wherein the message is configured to request registration with the network, wherein the instructions are further executable by the processor to cause the apparatus to: A second message is transmitted to the wireless device, the second message indicating that the procedure for verifying the air vehicle is to be performed before the data session is established and configured to accept registration of the wireless device, wherein the control plane connection is established based at least in part on transmitting the second message.

42. The apparatus of claim 39, wherein the instructions are further executable by the processor to cause the apparatus to: assigning a state in a control plane to the wireless device based at least in part on the over-the-air identifier, wherein user plane data addressed to the wireless device is blocked when the state is assigned to the wireless device; and The state is removed upon establishment of the data session.

43. The apparatus of claim 39, wherein the instructions are further executable by the processor to cause the apparatus to: transmitting, based at least in part on establishing the control plane connection, a second message to the wireless device, the second message configured to request information for verifying the air vehicle; and The airborne identifier of the airborne vehicle and the operational information regarding the airborne vehicle are received based at least in part on the second message.

44. The apparatus of claim 29, wherein the instructions are further executable by the processor to cause the apparatus to: matching the airborne identifier to an entry in an airborne identifier list based at least in part on receiving the message; and A procedure for verifying the air vehicle is initiated based at least in part on the match.

45. The apparatus of claim 29, wherein the operational information includes an identity of an operator, characteristics of the air vehicle, instructions for controls for the air vehicle, a flight path, or any combination thereof.

46. ​​The apparatus of claim 30, wherein the response comprises a first response and a second response, and wherein the instructions are further executable by the processor to cause the apparatus to: receiving the first response indicating positive authentication of the air vehicle; receiving a second response indicating approval of the flight path of the air vehicle, the second response being received after the first response; and A second message is transmitted to the wireless device, the second message configured to indicate to the wireless device a positive authentication of the air vehicle based at least in part on receiving the first response.

47. The apparatus of claim 46, wherein the instructions are further executable by the processor to cause the apparatus to: Based at least in part on transmitting the second message, a third message is received from the wireless device, the third message configured to request establishment of the data session.

48. The apparatus of claim 47, wherein the instructions are further executable by the processor to cause the apparatus to: A second request to authorize the flight path is sent to the airborne functional management system based at least in part on the second message, wherein the response indicating approval of the flight path is received based at least in part on sending the second request.

49. The apparatus of claim 47, wherein the second message includes the airborne identifier of the airborne vehicle, the operational information regarding the airborne vehicle, or both.

50. The apparatus of claim 30, wherein the instructions are further executable by the processor to cause the apparatus to: receiving, in a data plane, a command for the air vehicle from a controller for the air vehicle based at least in part on establishing the data session; and The command is transmitted to the air vehicle in the data plane.

51. An apparatus for wireless communication at a wireless device coupled to an aerial vehicle, comprising: processor, a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: transmitting a first message to a network, the first message including a network identifier of the wireless device, an air identifier of the air vehicle, and operational information about the air vehicle, wherein a request to verify the air vehicle based at least in part on the first message is sent to an air functionality management system; as well as A second message is received from the network based at least in part on transmitting the first message, the second message including approval of the air vehicle and configured to trigger establishment of a data session.

52. The apparatus of claim 51, wherein the instructions are further executable by the processor to cause the apparatus to: The data session is established with the network based at least in part on receiving the second message.

53. The apparatus of claim 51, wherein the first message includes a first indication of an access point providing air service, the air identifier, the operational information about the air vehicle, and a second indication of a controller for the air vehicle.

54. The apparatus of claim 53, wherein the instructions are further executable by the processor to cause the apparatus to: The first indication to the access point is encapsulated in an Evolved Packet System (EPS) Session Management (ESM) container, and the air identifier, the operational information about the air vehicle, and the second indication to the controller for the air vehicle are encapsulated in a Protocol Configuration Option (PCO) field.

55. The apparatus of claim 51, wherein the instructions are further executable by the processor to cause the apparatus to: An access point providing an airborne service is identified, wherein the data session is released based at least in part on the access point, and a second data session is established based at least in part on the access point, wherein an exclusive communication path is established between the wireless device and a controller for the airborne vehicle via the access point.

56. The apparatus of claim 51, wherein the instructions are further executable by the processor to cause the apparatus to: A control plane connection is established with the network based at least in part on the network identifier.

57. The apparatus of claim 56, wherein the instructions are further executable by the processor to cause the apparatus to: receiving, in a control plane, a third message from the network based at least in part on the request sent to the air functionality management system, the third message indicating a positive authentication of the air vehicle and received before the second message; and A fourth message is transmitted in the control plane to the network based at least in part on receiving the third message, the fourth message being configured to request establishment of the data session and being transmitted prior to the second message.

Images