Description
The UAV controller (Unmanned Aerial Vehicle Controller) is a fundamental component of an Unmanned Aircraft System (UAS). As defined in 3GPP Release 19 (TS 23.256 and TS 28.853), it is the device or software that enables a drone pilot (human operator) to control an Unmanned Aerial Vehicle (UAV). The UAV controller may be a dedicated hardware remote control, a smartphone, a tablet, or a software application running on a general-purpose device. In the context of 3GPP networks, the UAV controller is a communication endpoint that establishes a Command and Control (C2) link with the UAV, often over a cellular connection.
In the 3GPP UAS architecture, the UAV controller is treated as a distinct entity that may be authenticated and authorized separately from the UAV. The UAS NF (Network Function) is responsible for authenticating both the UAV and the UAV controller, and for authorizing the establishment of the C2 link between them. The UAV controller may connect to the network via a UE (User Equipment) such as a smartphone or a dedicated device, and it may have its own subscription or be associated with the UAV's subscription.
The C2 link between the UAV controller and the UAV can be established in several ways: direct radio link (e.g., Wi-Fi, proprietary radio), or via the mobile network (indirect). When using the mobile network, the UAV controller and the UAV each establish PDU sessions, and the C2 traffic is routed through the UPF. The UAS NF ensures that the C2 link is authorized and that QoS requirements (e.g., low latency, high reliability) are met. The UAV controller may also be involved in Remote Identification (RID) procedures, providing its identity and location.
From a management perspective (TS 28.853), the UAV controller may be managed as part of the UAS, with its configuration, software updates, and performance monitored. Security is paramount: the UAV controller must be authenticated to prevent unauthorized control of the UAV. The 3GPP security architecture (TS 33.256) defines procedures for mutual authentication between the UAV controller, the UAV, and the network.
The UAV controller is not a network function but a UE-side entity. However, its interactions with the network are standardized to ensure interoperability. For example, the UAV controller may need to register with the network, establish a PDU session for C2, and participate in authentication procedures. The UAS NF coordinates these activities, ensuring that only authorized controllers can control a given UAV. This is critical for safety and security, as unauthorized control could lead to accidents or malicious use.
In summary, the UAV controller is the human-machine interface for drone operation, and its integration with 3GPP networks enables reliable, secure, and regulatory-compliant drone flights over cellular connectivity. It is a key element in the UAS ecosystem, bridging the pilot and the UAV through the mobile network.
Purpose & Motivation
The UAV controller exists to provide a means for a human pilot to control an Unmanned Aerial Vehicle. In traditional drone operations, the controller is a dedicated remote control using proprietary radio links. However, as drones become more advanced and operate beyond visual line of sight (BVLOS), there is a need for more reliable and ubiquitous connectivity, which cellular networks can provide. The 3GPP standardization of the UAV controller in Release 19 addresses the need to integrate the controller into the mobile network architecture, ensuring that C2 links are secure, authorized, and meet QoS requirements.
Previously, cellular-connected drones used generic mobile broadband connections without specific support for C2 link authorization or controller authentication. This posed security risks and made it difficult to ensure regulatory compliance. The 3GPP definition of the UAV controller as a distinct entity enables the network to authenticate both the UAV and the controller, and to authorize their association. This prevents unauthorized control and enhances safety.
The UAV controller also plays a role in Remote Identification, as its identity and location may be part of the RID data. By standardizing the UAV controller's interactions with the network, 3GPP enables interoperability between different drone manufacturers, operators, and mobile networks. This is essential for the growth of the drone industry and for the safe integration of drones into airspace. The UAV controller concept also supports future autonomous operations, where the controller may be an automated system rather than a human pilot.
What changed in its specifications
The latest release-to-release comparison of specifications that define UAV controller. Each summary describes the whole specification, not only this term.
Rel-19 adds NEF-assisted pre-flight planning, USS changeover, and network-assisted detect-and-avoid to TS 23.256. It also adds no-transmit zone enforcement for UAV UEs and altitude reporting.
Full comparison in TS 23.256 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference UAV controller, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.256 vj50 | UAS Support Architecture Enhancements | Rel-19 read |
| TS 28.853 vj10 | Charging for Uncrewed Aerial Systems | Rel-19 read |