Command and control authorization for over-the-air devices

Abstract

Methods, systems, and devices for wireless communication are described. An application server may receive a remote pilot trigger message requesting establishment of a media connection and commanding and control connections between a remote pilot station and an air mobile device. The application server may send an authorization message associated with confirming whether the remote pilot station is authorized to control the air mobile device, and the application server may receive a response message responsive to the authorization message. The application server may communicate, based at least in part on receiving the response message, one or more control messages to initiate establishing a media connection and a command-to-control connection between the remote pilot station and the air mobile device.

Description

Technical Field

[0001] The following pertains to wireless communications, including command and control authorization for airborne equipment. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can 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, LTE-A Advanced (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 can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM).

[0003] A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as user equipment (UE). In some examples, a wireless multiple access communication system may support one or more airborne mobile devices, such as unmanned aerial vehicles (UAVs). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting command and control authorization for airborne devices. For example, the described technology provides a controller device sending an invitation message to initiate communication with a mobile airborne device (e.g., a UAV). In some examples, the invitation message may include: a description of data to be exchanged with the mobile airborne device (e.g., video data, audio data), an indication of a bootstrap data channel to be used for communication with the mobile airborne device, or both. In some examples, an application server may receive the invitation message and authorize the connection. For example, an IMS application server may send an authorization request to an authorization server, and the authorization request may include the identity of the airborne device, the identity of the controller device, or both. The authorization server may determine whether the controller device is authorized to control the mobile airborne device and may send a response message to the application server to authorize the connection. In some other examples, the IMS application server may request service data from another device to perform authorization. For example, the application server may receive service data indicating a list of approved controller devices (e.g., a whitelist), which may indicate whether the controller is authorized to control the mobile airborne device. Therefore, authorization processes can be used to authorize and establish connections between mobile air devices and controller devices, thereby enabling secure connections between them.

[0005] A method performed by an application server is described. This method may include: receiving a remote pilot trigger message requesting the establishment of a media connection and command and control connection between a remote pilot station (RPS) and an airborne mobile device; sending an authorization message associated with confirming whether the RPS is authorized to control the airborne mobile device; receiving a response message in response to the authorization message; and conveying one or more control messages based on the received response message to initiate the establishment of the media connection and command and control connection between the RPS and the airborne mobile device.

[0006] An application server is described. The application server may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may operate individually or collectively to execute code to enable the application server to: receive a remote pilot trigger message requesting the establishment of a media connection and command and control connection between the RPS and the airborne mobile device; send an authorization message associated with confirming whether the RPS is authorized to control the airborne mobile device; receive a response message in response to the authorization message; and, based on the received response message, convey one or more control messages to initiate the establishment of the media connection and command and control connection between the RPS and the airborne mobile device.

[0007] Another application server is described. This application server may include: components for receiving remote pilot trigger messages requesting the establishment of a media connection and command and control connection between the RPS and the airborne mobile device; components for sending an authorization message associated with confirming whether the RPS is authorized to control the airborne mobile device; components for receiving a response message in response to the authorization message; and components for conveying one or more control messages based on the received response message to initiate the establishment of a media connection and command and control connection between the RPS and the airborne mobile device.

[0008] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to: receive a remote pilot trigger message requesting the establishment of a media connection and command and control connection between the RPS and the airborne mobile equipment; send an authorization message associated with confirming whether the RPS is authorized to control the airborne mobile equipment; receive a response message in response to the authorization message; and, based on the received response message, convey one or more control messages to initiate the establishment of a media connection and command and control connection between the RPS and the airborne mobile equipment.

[0009] In some examples of the methods, application servers, and non-transitory computer-readable media described herein, sending an authorization message may include operations, features, components, or instructions for sending an authorization message to an authorization server indicating the identity of the RPS and the identity of the over-the-air mobile device.

[0010] In some examples of the methods, application servers, and nontransitory computer-readable media described herein, receiving a response message may include operations, features, components, or instructions for receiving a response message from an authorization server that indicates that the RPS can be authorized to control the airborne mobile device based on the identity of the RPS and the identity of the airborne mobile device.

[0011] In some examples of the methods, application servers, and non-transitory computer-readable media described herein, authorization messages may be sent to command and control network functions for forwarding to the authorization server.

[0012] In some examples of the methods, application servers, and nontransitory computer-readable media described herein, sending an authorization message may include operations, features, components, or instructions for: sending an authorization message requesting command and control service information to a Home Subscriber Server (HSS), and wherein receiving a response message further includes: receiving a response message from the Home Subscriber Server indicating command and control service information.

[0013] In some examples of the methods, application servers, and nontransitory computer-readable media described herein, command and control service information includes an indication of a list of one or more RPSs that can be authorized to control airborne mobile devices.

[0014] The methods described herein, application servers, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for conveying one or more control messages to initiate media connections and the establishment of command and control connections, which may be based on RPS and included in a list of one or more RPSs.

[0015] In some examples of the methods, application servers, and nontransitory computer-readable media described herein, the list of one or more RPSs includes a list of one or more identities, and the communication of one or more control messages to initiate media connections and the establishment of command and control connections may be based on the inclusion of the RPS's identity within the list of one or more identities.

[0016] The methods, application servers, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending a notification message to an authorization server that indicates that the RPS may be authorized to control airborne mobile devices based on a response message from a home subscriber server.

[0017] In some examples of the methods, application servers, and non-transitory computer-readable media described herein, remote pilot trigger messages include indications of the identity of the RPS, descriptions of the media to be transmitted via the media connection, indications of the boot data channel used for the media connection, or combinations thereof.

[0018] In some examples of the methods, application servers, and nontransitory computer-readable media described herein, conveying one or more control messages may include operations, features, components, or instructions for sending a trigger message for an airborne mobile device that indicates a boot data channel for media connection.

[0019] In some examples of the methods, application servers, and non-transitory computer-readable media described herein, remote pilot trigger messages may be received via call session control functions.

[0020] In some examples of the methods, application servers, and non-transitory computer-readable media described herein, airborne mobile devices include unmanned air vehicles.

[0021] In some examples of the methods, application servers, and nontransitory computer-readable media described herein, the media connection includes an Internet Protocol Multimedia Subsystem (IMS) audiovisual connection that supports the exchange of video and audio data between the RPS and over-the-air mobile devices.

[0022] In some examples of the methods, application servers, and nontransitory computer-readable media described herein, the command and control connection includes an IMS data communication connection that supports the exchange of command and control data and payload data between the RPS and the airborne mobile device.

[0023] In some examples of the methods, application servers, and nontransitory computer-readable media described herein, conveying one or more control messages may include operations, features, components, or instructions for: selecting data channel signaling functions associated with communication between the RPS and airborne mobile equipment; and selecting media functions for allocating one or more resources for a media connection.

[0024] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0025] While aspects and implementations have been described in this application by way of example, those skilled in the art will understand that additional implementations and use cases can arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, various implementations and / or devices can be produced via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically point to a use case or application, the applicability of various types of the described innovations is evident. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for the implementation and practice of the embodiments protected and described in the claims. For example, the transmission and reception of wireless signals necessarily involve multiple components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) for analog and digital purposes. The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., with different sizes, shapes, and constructions. Attached Figure Description

[0026] Figure 1 Examples of wireless communication systems supporting command and control authorization for airborne devices, according to one or more aspects of this disclosure, are shown.

[0027] Figure 2 Examples of wireless communication systems supporting command and control authorization for airborne devices, according to one or more aspects of this disclosure, are shown.

[0028] Figure 3 An example of a process flow supporting command and control authorization for airborne equipment, according to one or more aspects of this disclosure, is shown.

[0029] Figure 4 An example of a process flow supporting command and control authorization for airborne equipment, according to one or more aspects of this disclosure, is shown.

[0030] Figure 5 and Figure 6 A block diagram of an apparatus for command and control authorization for airborne equipment, according to one or more aspects of this disclosure, is shown.

[0031] Figure 7 A block diagram is shown of a communications manager that supports command and control authorization for airborne equipment, according to one or more aspects of this disclosure.

[0032] Figure 8 A diagram is shown of a system including equipment supporting command and control authorization for airborne equipment, according to one or more aspects of this disclosure.

[0033] Figures 9 to 11 A flowchart illustrating a method for command and control authorization for airborne equipment, illustrative of one or more aspects of this disclosure, is shown. Detailed Implementation

[0034] In some communication systems, mobile devices (e.g., airborne mobile devices such as UAVs, ground mobile devices such as off-road vehicles) can be remotely controlled by controller devices (e.g., via RPS, remote controllers, UEs). To facilitate control of mobile devices, they can also send media, such as audio or video, to the controller device via a media connection. However, in some cases, establishing a connection between the mobile device and the controller device may be difficult. For example, the controller device may lack mechanisms for discovering or establishing a connection with the mobile device. Furthermore, some mechanisms for establishing a connection between the controller device and the mobile device may allow unauthorized devices to gain control of the mobile device, potentially leading to security issues. Therefore, a mechanism to support the establishment of a secure connection between the controller device and the mobile device is desirable.

[0035] According to the examples described herein, a controller device (e.g., RPS) may send an invitation message (e.g., Session Initiation Protocol (SIP) invitation) to initiate communication with a mobile air device (e.g., UAV). In some examples, the invitation message may include: a description of the data to be exchanged with the mobile air device (e.g., video data, audio data), an indication of a bootstrap data channel to be used for communication with the mobile air device, or both. In some examples, an application server (e.g., an IMS application server) may receive the invitation message, and the application server may authorize the connection. For example, the IMS application server may send an authorization request (e.g., a Command and Control (C2) authorization request) to an authorization server (e.g., a C2 authorization server), and the authorization request may include the identity of the air device (e.g., IMS Public User (IMPU) identity), the identity of the controller device, or both. The authorization server may determine whether the controller device is authorized to control the mobile air device and may send a response message to the application server to authorize the connection. In some other examples, the IMS application server may request service data (e.g., C2 service data) from the HSS to perform authorization. For example, the application server may receive service data indicating a list of approved controller devices (e.g., a whitelist), which may indicate whether a controller is authorized to control a mobile air device. Therefore, authorization and connection establishment between the mobile air device and the controller device can be based on an authorization process, thereby allowing secure connections between the mobile air device and the controller device.

[0036] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further described in the context of a process flow. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to command and control authorization for airborne equipment.

[0037] Figure 1 An example of a wireless communication system 100 supporting command and control authorization for airborne devices according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 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, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0038] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0039] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices, such as... Figure 1 The other UE 115 or network entity 105 shown communicates.

[0040] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0041] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0042] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0043] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0044] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0045] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0046] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support command and control authorization for over-the-air devices as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

[0048] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0049] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF 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 the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0050] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be 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 decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0051] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0052] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, 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 symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

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

[0054] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount 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 set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0055] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

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

[0057] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0058] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0059] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), 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), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP IMS, or packet-switched streaming services.

[0060] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0061] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0062] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation 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 network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0063] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific direction (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other direction).

[0064] In some communication systems, mobile devices (e.g., airborne mobile devices such as unmanned aerial vehicles (UAVs) or ground-based mobile devices such as off-road vehicles) can be remotely controlled by controller devices (e.g., via a remote pilot station (RPS), remote pilot station, remote controller, UE 115). To facilitate control of mobile devices, they may also transmit media, such as audio or video, to the controller device via a media connection. However, in some cases, establishing a connection between the mobile device and the controller device may be difficult (e.g., a C2 connection). For example, the controller device may lack mechanisms for discovering or establishing a connection with the mobile device. Furthermore, some mechanisms for establishing a connection between the controller device and the mobile device may allow unauthorized devices to gain control of the mobile device, potentially leading to security issues. Additionally, mechanisms for controlling (e.g., authorizing and verifying) the connection (e.g., a C2 connection) after it has been established (even if established by an authorized party) can be beneficial. Furthermore, when the system involves airborne equipment, mechanisms for controlling quality of service and regulating operations (e.g., allowing or disallowing actions) can be beneficial. Finally, the ability for mobile devices (e.g., mobile airborne equipment) to change between controller devices or be controlled via multiple controller devices can be useful.

[0065] According to the examples described herein, a controller device (e.g., RPS, UE 115) can use IMS services to send an invitation message (e.g., Session Initiation Protocol (SIP) invitation) to initiate communication with a mobile air device (e.g., UAV). In some examples, the invitation message may include: a description of the data to be exchanged with the mobile air device (e.g., video data, audio data), an indication of a bootstrapping data channel to be used for communication with the mobile air device, or both. In some examples, an application server (e.g., an IMS application server) may receive the invitation message, and the application server may authorize the connection. For example, the application server may send an authorization request (e.g., a Command and Control (C2) authorization request) to an authorization server (e.g., a C2 authorization server), and the authorization request may include the identity of the air device (e.g., IMS Public User (IMPU) identity), the identity of the controller device, or both. The authorization server may determine whether the controller device is authorized to control the mobile air device and may send a response message to the application server to authorize the connection. In some other examples, the application server may request service data (e.g., C2 service data) from the HSS to perform authorization. For example, the application server may receive service data indicating a list of approved controller devices (e.g., a whitelist), which may indicate whether a controller is authorized to control a mobile air device. Therefore, authorization and connection establishment between the mobile air device and the controller device can be based on an authorization process, thereby allowing secure connections between the mobile air device and the controller device.

[0066] By incorporating an IMS data channel solution, mobile air devices and controller devices can experience various advantages. For example, mobile air devices and controller devices can each be assigned aliases, and discovery operations can be performed using IMS call establishment (e.g., based on aliases). Furthermore, IMS enhances security because each connection point can be authenticated (e.g., authorized) by the IMS provider (e.g., service provider). The IMS service can additionally provide functionality for controlling the establishment of C2 connections between mobile air devices and controller devices. In some examples, the IMS solution may also support the ability for mobile air devices to add third parties (e.g., additional controller devices) using call redirection procedures to change or connect to multiple controller devices. (References provided in this document) Figures 2 to 4 Let me describe these and other advantages in more detail.

[0067] Figure 2 An example of a wireless communication system 200 supporting command and control authorization for airborne equipment, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 includes a UAV 205 (e.g., an airborne remotely operated vehicle) and a remote pilot station 210 (e.g., an RPS 210). In some examples, the UAV 205, RPS 210, or both may be as referenced herein. Figure 1 The example of UE 115 described. Wireless communication system 200 supports establishing a connection between UAV 205 and RPS 210 via IMS capability. Although Figure 2 UAV 205 describes various aspects, but the described technologies can be implemented with respect to other equipment. For example, non-aerial equipment, such as ground equipment (e.g., cars, off-road vehicles) or submersible vehicles can be used.

[0068] Wireless communication system 200 may include network entity 105-a, which may be part of a cellular radio access network (RAN) such as a 5G system. In some examples, network entity 105-a may support an aviation subscription for UAV 205. For example, UAV 205 may have an aviation subscription in the cellular RAN, thereby allowing UAV 205 to participate in communications via network entity 105-b (e.g., communications with RPS 210). Network entity 105-a may include an access network and one or more core networks that may support communications with UAV 205 via communication link 265. In some examples, network entity 105-a may be or part of a mobile network operator (MNO) that manages operations associated with UAV 205 and other devices and may interface with an IMS core network.

[0069] Wireless communication system 200 may include a C2 communication service provider (CSP) 215, which may include an application server 220 (e.g., a C2 application server), an IMS core 225 (e.g., a C2 CSP IMS core), and C2 network functions 230. The IMS core 225 may form part of an IMS core network that may have data channel capabilities and support C2 communication between devices within the IMS core network. In some examples, the IMS core 225 may be provided by or interfaced with an MNO (e.g., network entity 105-a) to support a dedicated IMS network (e.g., a dedicated single network slice selection auxiliary information (S-NSSAI) data network). Alternatively, the IMS core 225 may be coordinated as a public IMS core 225 to enhance C2 services. The IMS core 225 may provide IMS subscription data and service profiles that support C2 communication services. For example, the IMS core 225 may provide IMS services 270 to various devices of wireless communication system 200, such as… Figure 2 As illustrated. In some examples, the RPS210 may be connected to the IMS core 225 via wireless communication (e.g., communication link 255) (such as a 5G system).

[0070] Wireless communication system 200 may include C2 service provider 235 (e.g., an unmanned aerial system (UAS) operator) that can host one or more devices (e.g., servers). C2 service provider 235 may include an enterprise IMS plane 240 that can interface with IMS core 225, and an authorization server 245 (e.g., a C2 authorization server). In some examples, C2 service provider 235 may include one or more wired RPS 250s, such as wired RPS 250-a and wired RPS 250-b, which may interface with C2 service provider 235 via enterprise IMS plane 240 or via Internet Protocol Private Branch Exchange (IP-PBX) system (e.g., via wired connection).

[0071] According to the examples described herein, C2 network function 230 can support the authorization of C2 connections between RPS 210 and UAV 205. In some examples, C2 network function 230 may be deployed by an MNO (e.g., as part of network entity 105-a or another device), and C2 network function 230 may be combined with a Network Open Function (NEF) or may be a standalone network function. In some examples, C2 network function may interact with application server 220 or HSS to support the authorization of connection requests. C2 network function 230 may expose C2 IMS capabilities to authorization server 245 via one or more application programming interfaces (APIs), enabling authorization server 245 to perform authorization and management of C2 pairing information. For example, C2 network function 230 may provide NEF service access 275 to IMS core 225 and authorization server 245 (e.g., if C2 network function is combined with NEF), such as... Figure 2 exemplified.

[0072] Authorization server 245 may be deployed by C2 service provider 235 to support the authorization of RPSs allowed to connect to each UAV 205 within the IMS core network. For example, authorization server 245 stores C2 configuration information that may include a dynamic list of allowed RPSs for each UAV 205 within wireless communication system 200. Additionally or alternatively, authorization server 245 may support real-time authorization of C2 connection requests (e.g., from RPS 210). For example, authorization server may store a list (e.g., a whitelist) of RPSs authorized to control and communicate with the UAV 205 (e.g., forming a media connection and C2 connection with the UAV), and this list may be dynamically updated. This may allow the addition of additional RPSs for controlling the UAV 205, or allow the revocation of access to an existing RPS communicating with the UAV 205 (e.g., preemption of access, network-triggered release of an existing IMS session). In some examples, this may allow the wired RPS 250-a, wired RPS 250-b, or both to be used to control the UAV 205 or to receive media (e.g., audiovisual data) from the UAV 205 (e.g., a multi-party session with a single control point such as RPS 210).

[0073] In some examples, RPS 210 may (e.g., via C2 network function 230 to C2 CSP 215) send a remote pilot trigger message 260 to trigger an IMS session with UAV 205, which may involve establishing a media connection and a C2 connection between RPS 210 and UAV 205. In some examples, the remote pilot trigger message 260 may be a SIP INVITE. The media connection may support the transmission of audio data, video data, or both (e.g., audiovisual data) from UAV 205 to RPS 210, which may facilitate control of UAV 205. The C2 connection may support control operations performed by RPS 210, such as controlling (e.g., piloting, flying, or otherwise controlling) UAV 205, and the C2 connection may be used to exchange other information between UAV 205 and RPS 210.

[0074] In some cases, the remote pilot trigger message 260 may include a description of the media to be exchanged via the media connection, an indication of a bootstrap data channel for connecting to UAV 205, or both. In some examples, the remote pilot trigger message 260 may include a called party identity (ID) associated with UAV 205, and the called party ID may indicate that the called party is a mobile air device (e.g., a UAV). To establish a media connection and C2 connection between UAV 205 and RPS 210, C2 network function 230 may perform an authorization process based on the remote pilot trigger message 260. For example, the authorization process may begin if C2 network function 230 (e.g., or C2 CSP 215, or application server 220) determines that the remote pilot trigger message 260 is for establishing a connection with the UAV (e.g., based on the called party ID, indicating that the called party is a UAV).

[0075] In some examples, application server 220 may receive a remote pilot trigger message 260, which may be forwarded to application server 220 from the call session control function (CSCF) of C2 CSP 215 or C2 service provider 235. Application server 220 may support an authorization process for RPS 210. In some examples, the authorization process may be performed after UAV 205 and RPS 210 have performed Packet Data Unit (PDU) session establishment for IMS services associated with IMS core 225 and IMS registration from UAV 205. Application server 220 may support an authorization process in dynamic mode, in which authorization is performed dynamically when RPS 210 calls UAV 205. Additionally or alternatively, application server 220 may support an authorization process in static mode, in which application server 220 may (e.g., via application functions) request configuration from HSS to verify RPS 210. In some cases, application server 220 may send a trigger message to UAV 205 (e.g., the trigger message will be forwarded to UAV 205 by another device), the trigger message may indicate the boot data channel for media connection (e.g., indicated by RPS 210).

[0076] In dynamic mode, application server 220 may send authorization requests to authorization server 245 (e.g., using...). Nnef_Authentication or Naf_Authentication The authorization server 245 determines whether RPS 210 is authorized to connect to UAV 205. In response to an authorization request, the authorization server 245 may consult stored information, such as a dynamic list of RPSs corresponding to 205, to determine whether RPS 210 is authorized to connect to UAV 205. The authorization server 245 may send a response message to the application server 220 indicating the result of the authorization (e.g., whether RPS 210 is allowed to connect to UAV 205). (This document references...) Figure 3 The process in dynamic mode is described in further detail.

[0077] In static mode, application server 220 may send a request (e.g., an authorization request, a data request) to the HSS to determine whether the caller ID associated with RPS 210 is authorized to connect to UAV 205. In some examples, the HSS may respond to the request by sending a response message indicating a list of RPSs associated with UAV 205 (e.g., a static whitelist). In some cases, the list may be a list of IDs (such as caller ID or IMPU ID) or a list including IDs. Application server 220 may check whether RPS 210 is in the list (e.g., whether the ID of RPS 210 is in the list) to determine whether RPS 210 is authorized to connect to UAV 205. In some examples, a signature-based disposal (SHAKEN) framework using token-to-assertional information may be used to verify the caller ID of RPS 210. (References) Figure 4 The process in static mode is described in further detail.

[0078] If authorization of RPS 210 is successful, an IMS session can be established between UAV 205 and RPS 210. This may include establishing a media connection supporting audio and video, and establishing one or more data channels (e.g., C2 connection) between UAV 205 and RPS 210. In some examples, application server 220 may communicate one or more control messages to initiate the establishment of the media connection and one or more data channels. For example, application server 220 may select data channel signaling functions for communication between UAV 205 and RPS 210. Additionally or alternatively, application server 220 may select media functions for allocating one or more resources for the media connection between UAV 205 and RPS 210.

[0079] The media channel, data channel, or both can be a bootstrap data channel indicated by RPS 210. Application server 220 can provide and update IMS data communication (DC) applications specific to each UAV 205 in the IMS network to IMS core 225. For example, after establishing an IMS session between UAV 205 and RPS 210, application server 220 can download the corresponding IMS DC application to support C2 communication and provide these IMS DC applications to IMS core 225. The DC application can support the exchange of control data and payload data between UAV 205 and RPS 210.

[0080] These technologies can also prioritize emergency services, including preemption, network-triggered release of existing IMS sessions, and multi-party sessions with only a single control point. These technologies can further provide verification of caller identification (e.g., verifying the caller ID of the RPS) and a framework for signature-based disposal (SHAKEN) of assertion information using tokens. These technologies enable IMS DC application providers and IMS DC web servers to support the disposal of control and payload data.

[0081] Therefore, the wireless communication system 200 can support the formation of a connection between UAV 205 and RPS 210 during the authorization process of a request for connection to UAV 205 from RPS 210, thereby improving the security associated with UAV 205.

[0082] Figure 3 An example of a process flow 300 supporting command and control authorization for airborne equipment, according to one or more aspects of this disclosure, is shown. Process flow 300 illustrates operations for supporting the establishment of a connection between UAV 305 and RPS 310, as referenced herein. Figure 2 As described herein. Process flow 300 may exemplify authorization processes in dynamic mode, which may involve communication between UAV 305, RPS 310, CSCF 315, IMS Application Server (AS) 320, HSS 325, C2 Network Function (NF) 330, and C2 Authorization Server 335, which may be examples of corresponding devices and components as described herein. Process flow 300 may exemplify signaling flows for C2 IMS with dynamic authorization per IMS session. In some examples, some steps may be added to process flow 300, performed in a different order than shown, or omitted.

[0083] At 340, UAV 305 can be configured for C2 services. For example, a subscription to UAV 305 can be configured for an IMS-based C2 service. Service profiles and service data associated with the C2 service can be stored in HSS 325, which may include the address of IMS AS 320. In some examples, when UAV 305 performs IMS registration (e.g., for an IMS service), the service profile of UAV 305 can be downloaded to CSCF 315 (e.g., service CSCG 315). In some cases, UAV 305 can register to a 5G service with an Arial subscription and can also register to an IMS with a subscription to the C2 service.

[0084] At 345, RPS 310 may send a remote pilot trigger message (e.g., an RPS trigger for establishing an IMS session to UAV 305) requesting the establishment of a media connection (e.g., an IMS session for transmitting audio, video, or both) and a command and control connection (e.g., an IMS data communication session) between RPS 310 and UAV 305. In some examples, the remote pilot trigger message may be a SIP invitation for initiating an IMS session to UAV 305 and may include the IMPU ID of RPS 310, a media description of video, audio, or both to be received from UAV 305, an indication of a bootstrap data channel for communication with UAV 305, or any combination thereof. In some cases, CSCF 315 may receive the remote pilot trigger message, which may be forwarded from the network from which RPS 310 originates to CSCF 315 serving UAV 305.

[0085] At 350, CSCF 315 can forward remote pilot trigger messages to IMS AS 320 (e.g., to the appropriate IMS AS) based on the UAV's subscription and service profile. CSCF 315 may include the IMPU ID of RPS 310, a media description of the video and audio to be received from UAV 305, an indication of the boot data channel used for communication with UAV 305, or any combination thereof. In response to receiving a remote pilot trigger message, IMS AS 320 can retrieve service profiles and service data from HSS 325, such as the address of C2 NF 330 and the address of C2 authorization server 335.

[0086] At 355, IMS AS 320 may send an authorization message (e.g., a C2 authorization request) associated with confirming whether RPS 310 is authorized to control UAV 305. For example, IMS AS 320 may initiate C2 authorization processes that may include sending an authorization message to C2 authorization server 335. In some examples, the authorization message may be sent to C2 authorization server 335 via C2 NF 330. The authorization message may include the identity of UAV 305 and the identity of RPS 310 (e.g., the IMPU IDs of UAV 305 and RPS 310). In some cases, the authorization message may be sent via one or more services specified for C2 authorization in the IMS. Additionally or alternatively, Nnef_Authentication and Naf_Authentication It can be extended to support licensing of C2 connections in IMS.

[0087] At 360, IMS AS 320 can receive a response message (e.g., a C2 authorization response) from C2 authorization server 335 in response to the authorization message. For example, if RPS 310 is included in a whitelist (e.g., a dynamic whitelist) of RPSs authorized to connect to UAV 305, C2 authorization server 335 can determine that RPS 310 is authorized to connect to UAV 305 and control that UAV. In some other examples, if RPS 310 is not authorized (e.g., if RPS 310 is not in a whitelist), the requested IMS session is rejected, and no connection is established.

[0088] At point 365, an IMS session can be established based on successful authorization of RPS 310. The IMS session enables the establishment of a bootstrap data channel that supports media (e.g., audiovisual) connections between UAV 305 and RPS 310. In some examples, one or more control messages can be exchanged between one or more devices described herein to support the establishment of the IMS session. For example, IMS AS 320 can select data channel signaling functions for communication between UAV 305 and RPS 310. Additionally or alternatively, IMS AS 320 can select media functions for allocating one or more resources for the media connection between UAV 305 and RPS 310. IMS AS 320 or another component can send an indication of a bootstrap data channel for the media connection to UAV 305.

[0089] In some examples, the IMS AS 320 can maintain a list of C2 data channel applications associated with each UAV 305 associated with the IMS network and upload these C2 data channel applications to the Data Channel Signaling Function (DCSF). When a media connection is established, the IMS AS 320 can select one or more C2 data channel applications corresponding to the UAV 305, and the UAV 305 and RPS 310 can download the C2 data channel applications via a bootstrap data channel. For example, the DCSF can create a list of UAV 305-specific data channel applications to be downloaded and presented in the RPS 310 (e.g., for user selection). Therefore, UAV 305-compatible C2 data channel applications can be included in the list of data channel applications.

[0090] At 370, a C2 data channel can be established between UAV 305 and RPS 310. For example, one or more C2 data channels can be established by downloading one or more C2 data channel applications via a bootstrap data channel based on UAV 305 and RPS 310. In some examples, a C2 data channel can be established using a Person-to-Person (P2P) application data channel establishment process or a Person-to-Application and Application-to-Person (P2A2P) process.

[0091] At 375, UAV 305 and RPS 310 can communicate via a media connection. For example, the media connection can be used by UAV 305 to transmit audiovisual data (e.g., audio stream, video stream, or both) to RPS 310, which can be used for monitoring by UAV 305.

[0092] At 380, UAV 305 and RPS 310 can communicate via a C2 data connection (e.g., an IMS data communication session). For example, RPS 310 can use the C2 data connection to remotely control (e.g., fly) UAV 305. In some examples, RPS 310 can retrieve payload data (e.g., information about UAV 305 or information collected by UAV 305) from UAV 305 via the C2 data connection.

[0093] Figure 4 An example of a process flow 400 supporting command and control authorization for airborne equipment according to one or more aspects of this disclosure is shown. Process flow 400 illustrates operations for supporting the establishment of a connection between UAV 405 and RPS 410, as referenced herein. Figure 2 As described herein. Process flow 400 may exemplify authorization processes in static mode, which may involve communication between UAV 405, RPS 410, CSCF 415, IMS AS 420, HSS 425, C2 NF 440, and C2 authorization server 445, which may be examples of corresponding devices and components as described herein. Process flow 400 may exemplify signaling flows for each UAV with a statically configured C2 IMS. In some examples, some steps may be added to process flow 400, performed in a different order than shown, or omitted.

[0094] At 440, UAV 405 can be configured for C2 services. For example, a subscription to UAV 405 can be configured for an IMS-based C2 service. Service profiles and service data associated with the C2 service can be stored in HSS 425, which may include the address of the IMS application server 420 and a list of authorized RSPs that can access UAV 405. In some examples, service data may also be provided, or alternatively, by the C2 authorization server 435, for example, via a process for external parameter tuning. In some examples, when UAV 405 performs IMS registration (e.g., for an IMS service), the service profile of UAV 405 can be downloaded to CSCF 415 (e.g., service CSCG 415). In some cases, UAV 405 can register to a 5G service with an Arial subscription and can also register to an IMS with a subscription to the C2 service.

[0095] At 445, RPS 410 may send a remote pilot trigger message (e.g., an RPS trigger for establishing an IMS session to UAV 405) requesting the establishment of a media connection (e.g., an IMS session for transmitting audio, video, or both) and a command and control connection (e.g., an IMS data connection) between RPS 410 and UAV 405. In some examples, the remote pilot trigger message may be a SIP invitation for initiating an IMS session to UAV 405 and may include the IMPU ID of RPS 410, a media description of the video and audio to be received from UAV 405, an indication of a bootstrap data channel for communication with UAV 405, or any combination thereof. In some cases, CSCF 415 may receive the remote pilot trigger message, which may be forwarded from the network from which RPS 410 originates to CSCF 415 serving UAV 405.

[0096] At 450, CSCF 315 can forward remote pilot trigger messages to IMS AS 420 (e.g., to the appropriate IMS AS) based on the UAV 405's subscription and service profile. CSCF 415 may include the IMPU ID of RPS 410, a media description of the video and audio to be received from UAV 405, an indication of the bootstrap data channel used for communication with UAV 405, or any combination thereof. In response to receiving a remote pilot trigger message, IMS AS 420 can retrieve service profiles and service data from HSS 425, such as the address of C2 NF 440 and the address of C2 authorization server 445. IMS AS 420 can process the service profiles and service data to determine whether RPS 410 is authorized to access the UAV for C2 communication.

[0097] At 455, IMS AS 420 may send a request (e.g., an authorization request, a data request) to HSS 425, which may request service data associated with UAV 405 stored by HSS 425. For example, IMS AS 420 may request a list of authorized RSPs that can access UAV 405.

[0098] At 460, HSS 425 may send a response message in response to a request. In some examples, the response message may include an indication of a list of authorized RPSs that can access UAV 405. IMS AS 420 may determine whether RPS 410 is authorized to access UAV 405 based on this list. For example, IMS AS 420 may check whether the ID of RPS 410 is included in the list. If RPS 410 is not authorized, IMS AS 420 rejects the requested IMS session.

[0099] At 465, if RPS 410 is successfully authorized (e.g., RPS 410 is included in the list), an IMS session can be established based on the successful authorization of RPS 410. The IMS session enables the establishment of a bootstrap data channel that supports a media (e.g., audiovisual) connection between UAV 405 and RPS 410. In some examples, one or more control messages can be exchanged between one or more devices described herein to support the establishment of the IMS session. For example, IMS AS 420 can select data channel signaling functions for communication between UAV 405 and RPS 410. Additionally or alternatively, IMS AS 420 can select media functions for allocating one or more resources for the media connection between UAV 405 and RPS 410. IMS AS 420 or another component can send an indication of a bootstrap data channel for the media connection to UAV 405.

[0100] In some examples, the IMS AS 420 can maintain a C2 data channel application associated with each UAV 405 associated with the IMS network and upload the C2 data channel applications to the Data Channel Signaling Function (DCSF). When a media connection is established, the IMS AS 420 can select one or more C2 data channel applications corresponding to the UAV 405, and the UAV 405 and RPS 410 can download the C2 data channel applications via a bootstrap data channel. For example, the DCSF can create a list of UAV 405-specific data channel applications to be downloaded and presented in the RPS 410 (e.g., for user selection). Therefore, UAV 405-compatible C2 data channel applications can be included in the list of data channel applications.

[0101] At 470, IMS AS 420 may send C2 event notifications (e.g., notification messages) to the authorization server 435 based on successful authorization of RPS 410. In some examples, sending C2 event notifications may be based on event subscriptions or local network policies. In some cases, C2 event notifications from IMS AS 420 may be forwarded (e.g., relayed) to the C2 authorization server 435 via C2 NF 430.

[0102] At 475, a C2 data channel can be established between UAV 405 and RPS 410. For example, one or more C2 data channels can be established by downloading one or more C2 data channel applications via a bootstrap data channel based on UAV 405 and RPS 410. In some examples, a C2 data channel can be established using a Person-to-Person (P2P) application data channel establishment process or a Person-to-Application and Application-to-Person (P2A2P) process.

[0103] At 480, UAV 405 and RPS 410 can communicate via a media connection. For example, the media connection can be used by UAV 405 to transmit audiovisual data (e.g., audio and video streams) to RPS 410, which can then be used for monitoring by UAV 405. The media connection can be an IMS audio stream, an IMS video stream, or an IMS audiovisual stream, and RPS 410 can apply the IMS video stream to the monitoring performed by UAV 405.

[0104] At 490, UAV 405 and RPS 410 can communicate via a C2 data connection (e.g., an IMS data communication session). For example, RPS 410 can use the C2 data connection to remotely control (e.g., fly) UAV 405. In some examples, RPS 410 can retrieve payload data (e.g., information about UAV 405 or information collected by UAV 405) from UAV 405 via the C2 data connection. RPS 410 can use the C2 data connection to remotely control UAV 405 and retrieve payload data from UAV 405.

[0105] Figure 5 A block diagram 500 is shown of a device 505 supporting command and control authorization for airborne equipment according to one or more aspects of this disclosure. Device 505 may be an example of aspects of network entity 105 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communications manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0106] Receiver 510 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 505. In some examples, receiver 510 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 510 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0107] Transmitter 515 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 505. For example, transmitter 515 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 515 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 515 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 515 and receiver 510 may be co-located in a transceiver, which may include or be coupled to a modem.

[0108] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of command and control authorization for airborne devices as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0109] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0110] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0111] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0112] For example, the communication manager 520 can be configured or operable to support components for receiving remote pilot-triggered messages requesting the establishment of a media connection and command and control connection between a remote pilot station and an airborne mobile device. The communication manager 520 can be configured or operable to support components for sending authorization messages associated with confirming whether the remote pilot station is authorized to control the airborne mobile device. The communication manager 520 can be configured or operable to support components for receiving response messages in response to authorization messages. The communication manager 520 can be configured or operable to support components for transmitting one or more control messages based on the received response messages to initiate the establishment of a media connection and command and control connection between the remote pilot station and the airborne mobile device.

[0113] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof or at least one processor otherwise coupled to them) can support technologies for establishing media connections and C2 data channel connections between UAV and RPS with enhanced authentication processes and connectivity flexibility.

[0114] Figure 6A block diagram 600 is shown of a device 605 supporting command and control authorization for an airborne device according to one or more aspects of this disclosure. Device 605 may be an example of aspects of device 505 or network entity 105 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communications manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0115] Receiver 610 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 605. In some examples, receiver 610 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 610 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0116] Transmitter 615 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 605. For example, transmitter 615 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 615 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 615 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 615 and receiver 610 may be co-located in a transceiver, which may include or be coupled to a modem.

[0117] Device 605 or its various components may be examples of parts used to perform various aspects of command and control authorization for airborne devices as described herein. For example, communication manager 620 may include triggering component 625, authorization component 630, response manager 635, connection establishment component 640, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0118] Triggering component 625 is capable of, configured to, or operable to support components for receiving remote pilot trigger messages requesting the establishment of a media connection and command and control connection between a remote pilot station and an airborne mobile device. Authorization component 630 is capable of, configured to, or operable to support components for sending authorization messages associated with confirming whether the remote pilot station is authorized to control the airborne mobile device. Response manager 635 is capable of, configured to, or operable to support components for receiving response messages in response to authorization messages. Connection establishment component 640 is capable of, configured to, or operable to support components for transmitting one or more control messages based on received response messages to initiate the establishment of a media connection and command and control connection between the remote pilot station and the airborne mobile device.

[0119] Figure 7A block diagram 700 is shown of a communication manager 720 supporting command and control authorization for an airborne device according to one or more aspects of this disclosure. The communication manager 720 may be an example of a communication manager 520, a communication manager 620, or aspects thereof as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of command and control authorization for an airborne device as described herein. For example, the communication manager 720 may include a triggering component 725, an authorization component 730, a response manager 735, a connection establishment component 740, a functional component 745, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0120] Triggering component 725 is capable of, configured to, or operable to support components for receiving remote pilot trigger messages requesting the establishment of a media connection and command and control connection between a remote pilot station and an airborne mobile device. Authorization component 730 is capable of, configured to, or operable to support components for sending authorization messages associated with confirming whether the remote pilot station is authorized to control the airborne mobile device. Response manager 735 is capable of, configured to, or operable to support components for receiving response messages in response to authorization messages. Connection establishment component 740 is capable of, configured to, or operable to support components for transmitting one or more control messages based on received response messages to initiate the establishment of a media connection and command and control connection between the remote pilot station and the airborne mobile device.

[0121] In some examples, in order to support the sending of authorization messages, the authorization component 730 is capable of, configured to, or operable to support components for sending authorization messages to the authorization server that indicate the identity of the remote pilot station and the identity of the airborne mobile device.

[0122] In some examples, in order to support receiving response messages, the response manager 735 is capable of, configured to, or operable to support components for receiving response messages from an authorization server, which instruct the remote pilot station to be authorized to control the airborne mobile device based on the identity of the remote pilot station and the identity of the airborne mobile device.

[0123] In some examples, to support the sending of authorization messages, the authorization component 730 is capable of, configured to, or operable to support components for sending authorization messages requesting command and control service information to the home subscriber server. In some examples, to support the sending of authorization messages, the response manager 735 is capable of, configured to, or operable to support components for receiving response messages indicative of command and control service information from the home subscriber server. In some examples, the authorization message is sent to the command and control network function for forwarding to the authorization server.

[0124] In some examples, command and control service information includes an indication of a list of one or more remote pilot stations authorized to control airborne mobile equipment.

[0125] In some examples, one or more control messages are communicated to initiate media connections and command and control connections based on a remote pilot station included in a list of one or more remote pilot stations.

[0126] In some examples, the list of one or more remote pilot stations includes a list of one or more identities. In some examples, the communication of one or more control messages to initiate a media connection and the establishment of a command and control connection are based on the remote pilot station's identity being included in a list of one or more identities.

[0127] In some examples, the authorization component 730 is capable of, configured to, or operable to support components for sending notification messages to the authorization server, which instruct the remote pilot station to be authorized to control airborne mobile equipment based on a response message from the home subscriber server.

[0128] In some examples, remote pilot trigger messages include indications of the identity of the remote pilot station, descriptions of the media to be transmitted via the media connection, indications of the boot data channel used for the media connection, or combinations thereof.

[0129] In some examples, in order to support the transmission of one or more control messages, the triggering component 725 is capable of, configured to, or operable to support components for sending trigger messages for airborne mobile devices, which indicate a boot data channel for media connection.

[0130] In some examples, the remote pilot trigger message is received via a call session control function. In some examples, the airborne mobile device includes unmanned aerial vehicles. In some examples, the media connection includes an IMS audiovisual connection that supports the exchange of video and audio data between the remote pilot station and the airborne mobile device.

[0131] In some examples, the command and control connection includes an IMS data communication connection that supports the exchange of command and control data and payload data between remote pilot stations and airborne mobile equipment.

[0132] In some examples, to support the transmission of one or more control messages, functional component 745 is capable of, configured, or operable to support components for selecting data channel signaling functions associated with communication between a remote pilot station and an airborne mobile device. In some examples, to support the transmission of one or more control messages, functional component 745 is capable of, configured, or operable to support components for selecting media functions for allocating one or more resources for a media connection.

[0133] Figure 8 A diagram is shown of a system 800 including device 805 supporting command and control authorization for air-to-air devices, according to one or more aspects of this disclosure. Device 805 may be an example of device 505, device 605, or network entity 105 as described herein, or may include components thereof. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 805 may include components supporting output and acquisition of communication, such as a communication manager 820, a transceiver 810, an antenna 815, at least one memory 825, code 830, and at least one processor 835. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 840).

[0134] Transceiver 810 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 810 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 810 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 805 may include one or more antennas 815 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 810 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 815, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 815, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 810 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 815 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 815 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 810 may include one or more processors or one or more memory components, or be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 810, or transceiver 810 and one or more antennas 815, or transceiver 810 and one or more antennas 815 and one or more processors or one or more memory components (e.g., at least one processor 835, at least one memory 825, or both), may be included in a chip or chip assembly mounted in device 805. In some examples, transceiver 810 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0135] At least one memory 825 may include RAM, ROM, or any combination thereof. At least one memory 825 may store computer-readable, computer-executable (e.g., processor-executable) code 830, including instructions that, when executed by one or more of the at least one processor 835, cause device 805 to perform the various functions described herein. Code 830 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 830 may not be directly executable by one of the at least one processor 835, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, among other things, at least one memory 825 may also contain a BIOS that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 835 may include multiple processors, and at least one memory 825 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0136] At least one processor 835 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, at least one processor 835 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 835. At least one processor 835 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 825) to cause device 805 to perform various functions (e.g., functions or tasks supporting command and control authorization for over-the-air devices). For example, device 805 or components of device 805 may include at least one processor 835 and at least one memory 825 coupled to one or more processors in at least one processor 835, wherein at least one processor 835 and at least one memory 825 are configured to perform the various functions described herein. At least one processor 835 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions for performing the functions of device 805 (e.g., by executing code 830). At least one processor 835 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 805 (such as within one or more memories in at least one memory 825). In some examples, at least one processor 835 may include multiple processors, and at least one memory 825 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 835 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 835) and memory circuitry (which may include at least one memory 825)) or components that receive or obtain input and process such input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 835 or a processing system including at least one processor 835 may be configured, configurable, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configurable,” “configurable to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 825 or otherwise.

[0137] In some examples, bus 840 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 840 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 805, or communication performed between different components of device 805 that are co-addressable or may be located in different locations (e.g., where device 805 may refer to a system in which one or more of communication manager 820, transceiver 810, at least one memory 825, code 830 and at least one processor 835 may be located in one of the different components or partitioned between the different components).

[0138] In some examples, the communication manager 820 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 820 can manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 820 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating other network entities 105 to control communication with UE 115. In some examples, the communication manager 820 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0139] For example, the communication manager 820 can be configured or operable to support components for receiving remote pilot-triggered messages requesting the establishment of a media connection and command and control connection between a remote pilot station and an airborne mobile device. The communication manager 820 can be configured or operable to support components for sending authorization messages associated with confirming whether the remote pilot station is authorized to control the airborne mobile device. The communication manager 820 can be configured or operable to support components for receiving response messages in response to authorization messages. The communication manager 820 can be configured or operable to support components for transmitting one or more control messages based on the received response messages to initiate the establishment of a media connection and command and control connection between the remote pilot station and the airborne mobile device.

[0140] By including or configuring a communication manager 820 according to examples as described herein, device 805 can support technologies used. In some examples, authorization messages are sent to command and control network functions for forwarding to an authorization server.

[0141] In some examples, the communication manager 820 may be configured to use or otherwise coordinate with the transceiver 810, one or more antennas 815 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the transceiver 810, one or more processors in at least one processor 835, one or more memories in at least one memory 825, code 830, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 835, at least one memory 825, code 830, or any combination thereof). For example, code 830 may include instructions that can be executed by one or more processors in at least one processor 835 to cause the device 805 to perform various aspects of command and control authorization for airborne devices as described herein, or at least one processor 835 and at least one memory 825 may be otherwise configured to perform or support such operations individually or jointly.

[0142] Figure 9 A flowchart illustrating a method 900 for supporting command and control authorization for over-the-air devices, as exemplified by an example as described herein, is shown. The operation of method 900 can be implemented by a network entity or its components as described herein. For example, the operation of method 900 can be implemented by, as referenced... Figures 1 to 8 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0143] At 905, the method may include: receiving a remote pilot-triggered message requesting the establishment of a media connection and command and control connection between a remote pilot station and an airborne mobile device. The operation of box 905 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 905 may be provided by reference to [reference needed]. Figure 7 The described triggering component 725 is executed.

[0144] At 910, the method may include: sending an authorization message associated with confirming whether a remote pilot station is authorized to control airborne mobile equipment. The operation of block 910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 910 may be provided by reference to [reference needed]. Figure 7 The described authorization component 730 is used to execute.

[0145] At 915, the method may include: receiving a response message in response to an authorization message. The operation of block 915 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 915 may be provided by reference to [reference needed]. Figure 7 The described response manager 735 is used to execute this.

[0146] At 920, the method may include: conveying one or more control messages based on a received response message to initiate the establishment of a media connection and a command and control connection between the remote pilot station and the airborne mobile device. The operation of block 920 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 920 may be provided by reference to [reference needed]. Figure 7 The described connection establishment component 740 is used to perform this.

[0147] Figure 10 A flowchart illustrating a method 1000 for supporting command and control authorization for over-the-air devices, as exemplified by an example as described herein, is shown. The operation of method 1000 can be implemented by a network entity or its components as described herein. For example, the operation of method 1000 can be implemented by, as referenced... Figures 1 to 8 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0148] At 1005, the method may include: receiving a remote pilot-triggered message requesting the establishment of a media connection and command and control connection between a remote pilot station and an airborne mobile device. The operation of block 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1005 may be provided by reference to [reference needed]. Figure 7 The described triggering component 725 is executed.

[0149] At 1010, the method may include: sending an authorization message to an authorization server associated with confirming whether a remote pilot station is authorized to control an airborne mobile device, the authorization message indicating the identity of the remote pilot station and the identity of the airborne mobile device. The operation of block 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1010 may be provided by reference to [reference needed]. Figure 7 The described authorization component 730 is used to execute.

[0150] At 1015, the method may include: receiving a response message from an authorization server, the response message indicating that the remote pilot station is authorized to control the airborne mobile device based on the identity of the remote pilot station and the identity of the airborne mobile device. The operation of box 1015 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1015 may be provided by reference to [reference]. Figure 7The described response manager 735 is used to execute this.

[0151] At 1020, the method may include: conveying one or more control messages based on a received response message to initiate the establishment of a media connection and a command and control connection between the remote pilot station and the airborne mobile device. The operation of block 1020 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1020 may be provided by reference to [reference needed]. Figure 7 The described connection establishment component 740 is used to perform this.

[0152] Figure 11 A flowchart illustrating a method 1100 for supporting command and control authorization for over-the-air devices, according to an example as described herein, is shown. The operation of method 1100 can be implemented by a network entity or its components as described herein. For example, the operation of method 1100 can be implemented by, as referenced... Figures 1 to 8 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0153] At 1105, the method may include: receiving a remote pilot-triggered message requesting the establishment of a media connection and command and control connection between a remote pilot station and an airborne mobile device. The operation of block 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1105 may be provided by reference to [reference needed]. Figure 7 The described triggering component 725 is executed.

[0154] At 1110, the method may include: sending an authorization message to the HSS associated with confirming whether a remote pilot station is authorized to control an airborne mobile device, the authorization message requesting command and control service information associated with confirming whether a remote pilot station is authorized to control an airborne mobile device. The operation of block 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1110 may be provided by reference to [reference needed]. Figure 7 The described authorization component 730 is used to execute.

[0155] At 1115, the method may include: receiving a response message from the HSS in response to an authorization message containing indication commands and control service information. The operation of block 1115 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1115 may be derived from references... Figure 7 The described response manager 735 is used to execute this.

[0156] At 1120, the method may include: conveying one or more control messages based on a received response message to initiate the establishment of a media connection and a command and control connection between the remote pilot station and the airborne mobile device. The operation of block 1120 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1120 may be provided by reference to [reference needed]. Figure 7 The described connection establishment component 740 is used to perform this.

[0157] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication, the method comprising: receiving a remote pilot-triggered message requesting the establishment of a media connection and a command and control connection between an RPS and an airborne mobile device; sending an authorization message associated with confirming whether the RPS is authorized to control the airborne mobile device; receiving a response message in response to the authorization message; and conveying one or more control messages, at least in part based on the receipt of the response message, to initiate the establishment of the media connection and the command and control connection between the RPS and the airborne mobile device.

[0158] Aspect 2: According to the method of aspect 1, sending the authorization message further includes: sending the authorization message to the authorization server indicating the identity of the RPS and the identity of the over-the-air mobile device.

[0159] Aspect 3: According to the method of aspect 2, receiving the response message further includes: receiving the response message from the authorization server, the response message indicating that the RPS is authorized to control the airborne mobile device at least in part based on the identity of the RPS and the identity of the airborne mobile device.

[0160] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the authorization message is sent to the command and control network function for forwarding to the authorization server.

[0161] Aspect 5: According to the method of aspect 1, sending the authorization message further includes: sending the authorization message requesting command and control service information to the HSS, and receiving the response message further includes: receiving the response message indicating the command and control service information from the HSS.

[0162] Aspect 6: According to the method of aspect 5, wherein the command and control service information includes an indication of a list of one or more RPSs authorized to control the airborne mobile device.

[0163] Aspect 7: The method according to aspect 6, wherein the communication of the one or more control messages to initiate the media connection and the establishment of the command and control connection are at least in part based on the RPS being included in the list of the one or more RPS.

[0164] Aspect 8: The method according to any one of Aspects 6 to 7, wherein the list of one or more RPSs includes a list of one or more identities, and the establishment of the communication of the one or more control messages to initiate the media connection and the command and control connection is based at least in part on the identity of the RPS being included in the list of one or more identities.

[0165] Aspect 9: The method according to any one of Aspects 5 to 8, the method further comprising: sending a notification message to an authorization server, the notification message indicating that the RPS is authorized to control the airborne mobile device at least in part based on the response message from the HSS.

[0166] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the remote pilot trigger message includes an indication of the identity of the RPS, a description of the media to be transmitted via the media connection, an indication of a boot data channel for the media connection, or a combination thereof.

[0167] Aspect 11: The method according to aspect 10, wherein conveying the one or more control messages further includes: sending a trigger message for the airborne mobile device, the trigger message indicating the boot data channel for the media connection.

[0168] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the remote pilot trigger message is received via a call session control function.

[0169] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the airborne mobile device includes unmanned air vehicles.

[0170] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the media connection includes an IMS audiovisual connection that supports the exchange of video and audio data between the RPS and the over-the-air mobile device.

[0171] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the command and control connection includes an IMS data communication connection that supports the exchange of command and control data and payload data between the RPS and the airborne mobile device.

[0172] Aspect 16: The method according to any one of Aspects 1 to 15, wherein conveying the one or more control messages further includes: selecting a data channel signaling function associated with communication between the RPS and the airborne mobile device; and selecting a media function for allocating one or more resources for the media connection.

[0173] Aspect 17: An apparatus comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the apparatus to perform a method according to any one of Aspects 1 to 16.

[0174] Aspect 18: An apparatus comprising at least one component for performing the method according to any one of aspects 1 to 16.

[0175] Aspect 19: A non-transitory computer-readable medium storing code, said code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 16.

[0176] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0177] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0178] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0179] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0180] The functionality described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functionality can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.

[0181] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0182] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0183] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0184] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0185] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0186] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0187] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this 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. An application server, the application server comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, said one or more processors coupled to said one or more memories and capable of operating individually or jointly to execute said code to enable the application server: Receive remote pilot trigger messages requesting the establishment of media and command and control connections between the remote pilot station and airborne mobile equipment; Send an authorization message associated with confirming whether the remote pilot station is authorized to control the airborne mobile equipment; Receive a response message in response to the authorization message; as well as At least in part, based on receiving the response message, one or more control messages are conveyed to initiate the establishment of the media connection and the command and control connection between the remote pilot station and the airborne mobile device.

2. The application server of claim 1, wherein, in order to send the authorization message, the one or more processors are capable of further operating individually or jointly to execute the code to cause the application server to: Send the authorization message to the authorization server, indicating the identity of the remote pilot station and the identity of the airborne mobile device.

3. The application server of claim 2, wherein, in order to receive the response message, the one or more processors are capable of further operating individually or jointly to execute the code to cause the application server to: The remote pilot station receives a response message from the authorization server, the response message indicating that the remote pilot station is authorized to control the airborne mobile device at least in part based on the identity of the remote pilot station and the identity of the airborne mobile device.

4. The application server of claim 2, wherein the authorization message is sent to the command and control network function for forwarding to the authorization server.

5. The application server of claim 1, wherein, in order to send the authorization message, the one or more processors are capable of further operating individually or jointly to execute the code to cause the application server to: The authorization message that sends a request for command and control service information to the home subscriber server, and the receipt of the response message further includes: Receive the response message indicating the command and control service information from the home subscriber server.

6. The application server of claim 5, wherein the command and control service information includes an indication of a list of one or more remote pilot stations authorized to control the airborne mobile equipment.

7. The application server of claim 6, wherein the establishment of the one or more control messages to initiate the media connection and the command and control connection is at least in part based on the remote pilot station being included in the list of the one or more remote pilot stations.

8. The application server according to claim 6, wherein: The list of one or more remote pilot stations includes a list of one or more identities, and The establishment of the media connection and the command and control connection, which transmits the one or more control messages to initiate the connection, is based at least in part on the identity of the remote pilot station, which is included in the list of the one or more identities.

9. The application server of claim 5, wherein the one or more processors are individually or jointly further operable to execute the code to enable the application server to: A notification message is sent to the authorization server, the notification message instructing the remote pilot station to be authorized to control the airborne mobile equipment at least in part based on the response message from the home subscriber server.

10. The application server of claim 1, wherein the remote pilot trigger message includes an indication of the identity of the remote pilot station, a description of the media to be transmitted via the media connection, an indication of a boot data channel for the media connection, or a combination thereof.

11. The application server of claim 10, wherein, in order to convey the one or more control messages, the one or more processors are individually or jointly capable of further operating to execute the code to cause the application server to: A trigger message is sent for the airborne mobile device, the trigger message indicating the bootstrap data channel for the media connection.

12. The application server of claim 1, wherein the remote pilot trigger message is received via a call session control function.

13. The application server according to claim 1, wherein the airborne mobile device includes unmanned air vehicles.

14. The application server of claim 1, wherein the media connection includes an Internet Protocol Multimedia Subsystem (IMS) audiovisual connection that supports the exchange of video and audio data between the remote pilot station and the airborne mobile device.

15. The application server of claim 1, wherein the command and control connection includes an Internet Protocol Multimedia Subsystem (IMS) data communication connection that supports the exchange of command and control data and payload data between the remote pilot station and the airborne mobile equipment.

16. The application server of claim 1, wherein, in order to convey the one or more control messages, the one or more processors are capable of further operating individually or jointly to execute the code to cause the application server to: Select the data channel signaling function associated with communication between the remote pilot station and the airborne mobile equipment; and Select a media function to allocate one or more resources for the media connection.

17. A method for wireless communication, the method comprising: Receive remote pilot trigger messages requesting the establishment of media and command and control connections between the remote pilot station and airborne mobile equipment; Send an authorization message associated with confirming whether the remote pilot station is authorized to control the airborne mobile equipment; Receive a response message in response to the authorization message; as well as At least in part, based on receiving the response message, one or more control messages are conveyed to initiate the establishment of the media connection and the command and control connection between the remote pilot station and the airborne mobile device.

18. The method of claim 17, wherein sending the authorization message further comprises: Send the authorization message to the authorization server, indicating the identity of the remote pilot station and the identity of the airborne mobile device.

19. The method of claim 18, wherein receiving the response message further comprises: The remote pilot station receives a response message from the authorization server, the response message indicating that the remote pilot station is authorized to control the airborne mobile device at least in part based on the identity of the remote pilot station and the identity of the airborne mobile device.

20. The method of claim 18, wherein the authorization message is sent to a command and control network function for forwarding to the authorization server.

21. The method of claim 17, wherein sending the authorization message further comprises: The authorization message that sends a request for command and control service information to the home subscriber server, and the receipt of the response message further includes: Receive the response message indicating the command and control service information from the home subscriber server.

22. The method of claim 21, wherein the command and control service information includes an indication of a list of one or more remote pilot stations authorized to control the airborne mobile equipment.

23. The method of claim 22, wherein the establishment of the communication of the one or more control messages to initiate the media connection and the command and control connection is at least in part based on the remote pilot station being included in the list of the one or more remote pilot stations.

24. The method of claim 22, wherein the list of one or more remote pilot stations includes a list of one or more identities, and the establishment of the communication of the one or more control messages to initiate the media connection and the command and control connection is based at least in part on the remote pilot station's identity being included in the list of one or more identities.

25. The method according to claim 21, further comprising: A notification message is sent to the authorization server, the notification message instructing the remote pilot station to be authorized to control the airborne mobile equipment at least in part based on the response message from the home subscriber server.

26. The method of claim 17, wherein the remote pilot trigger message includes an indication of the identity of the remote pilot station, a description of the media to be transmitted via the media connection, an indication of a boot data channel for the media connection, or a combination thereof.

27. The method of claim 26, wherein conveying the one or more control messages further comprises: A trigger message is sent for the airborne mobile device, the trigger message indicating the bootstrap data channel for the media connection.

28. The method of claim 17, wherein the remote pilot trigger message is received via a call session control function.

29. An apparatus comprising: Components used to receive remote pilot-triggered messages requesting the establishment of media and command and control connections between remote pilot stations and airborne mobile devices; A component for sending an authorization message associated with confirming whether the remote pilot station is authorized to control the airborne mobile equipment; A component for receiving a response message in response to the authorization message; and Components for transmitting one or more control messages, at least in part, based on the receipt of the response message, to initiate the establishment of the media connection and the command and control connection between the remote pilot station and the airborne mobile equipment.

30. A non-transitory computer-readable medium storing code, the code comprising instructions executable by one or more processors to: Receive remote pilot trigger messages requesting the establishment of media and command and control connections between the remote pilot station and airborne mobile equipment; Send an authorization message associated with confirming whether the remote pilot station is authorized to control the airborne mobile equipment; Receive a response message in response to the authorization message; as well as At least in part, based on receiving the response message, one or more control messages are conveyed to initiate the establishment of the media connection and the command and control connection between the remote pilot station and the airborne mobile device.

Images