Uncrewed Aerial Vehicle Controller

Description

The Uncrewed Aerial Vehicle Controller (UAV-C) is a functional entity introduced in 3GPP Release 19 to enable the command and control (C2) of Uncrewed Aerial Vehicles (UAVs), commonly known as drones, over cellular networks. The UAV-C represents the remote piloting or autonomous control function that communicates with the UAV through the 3GPP network. It is defined primarily in TS 23.256 (Architecture enhancements to support Uncrewed Aerial Systems) and TS 28.853 (Management aspects for UAS). The UAV-C may reside in the operator's network, be hosted by a third-party UAS Service Supplier (USS), or be deployed at the edge, depending on the deployment scenario and regulatory requirements.

Architecturally, the UAV-C interacts with the 5G Core network through standardized interfaces that support both the C2 link and the data link. The C2 link carries low-latency, high-reliability command messages between the UAV-C and the UAV, while the data link carries payload such as video or sensor data. In Release 19, the 3GPP architecture introduces UAS-specific network functions, including the UAS Network Function (UAS-NF) or enhancements to existing functions like the NEF (Network Exposure Function) and UDM (Unified Data Management), to handle UAV authentication, authorization, tracking, and C2 QoS enforcement. The UAV-C communicates with the network via application-layer protocols over user plane or through service-based interfaces for control operations.

The UAV-C plays a central role in UAV identification and authorization. Before flight, the UAV and UAV-C perform mutual authentication through the network, supported by the USS and the UAS-NF. The network verifies the UAV's identity (via a UAV ID and related credentials) and the UAV-C's authorization to operate a given UAV. Once authorized, the network establishes the C2 session with suitable QoS flows to guarantee the latency and reliability required for safe flight control. Throughout the flight, the network may enforce geofencing, detect unauthorized UAVs, and provide tracking information to authorized authorities.

QoS and mobility management are critical for UAV-C operation. The Command and Control QoS is characterized by low latency (typically tens of milliseconds) and high reliability (up to 99.999%). The network must support seamless mobility as UAVs traverse cells at altitude, where radio conditions differ significantly from terrestrial user equipment. Release 19 defines mechanisms for C2 link continuity, including session continuity across handovers and support for both direct UAV-to-network and UAV-to-UAV relay scenarios. The UAV-C also supports remote identification, allowing the network to broadcast or provide identity information as required by regulators.

Deployment models for UAV-C include fully operator-hosted controllers, third-party USS-hosted controllers, and hybrid models. The 3GPP architecture supports the exposure of UAV-related capabilities (for example, location, QoS control, and identity) through the NEF to authorized external applications such as traffic management systems. This openness is essential for integration with air traffic management (ATM) and U-space frameworks. Security is enforced end-to-end, with the UAV-C and UAS-NF authenticating each other and protecting the C2 link against tampering and eavesdropping. Overall, UAV-C is a foundational element enabling safe, scalable, and regulatory-compliant cellular-connected drone operations in 5G-Advanced and beyond.

Purpose & Motivation

UAV-C exists to provide a standardized, secure, and reliable control endpoint for cellular-connected drones within 3GPP networks. Before Release 19, drone operations over cellular networks were largely ad hoc, relying on generic mobile broadband connectivity without dedicated support for command-and-control (C2) links, UAV identification, or authorization. This created safety, security, and regulatory gaps: latency and reliability could not be guaranteed, unauthorized UAVs could not be reliably detected, and authorities lacked standardized means to enforce flight rules.

The rapid growth of commercial and public-safety drone use cases — package delivery, inspection, emergency response, and urban air mobility — drove the need for a dedicated architecture. Regulatory bodies worldwide (FAA, EASA, and others) require remote identification and controlled airspace management, which cellular networks can support through standardized functions. UAV-C, together with the UAS-NF and related enhancements, addresses these needs by defining how a controller authenticates with the network, how the C2 session is established with appropriate QoS, and how the network can assist in tracking and identifying UAVs.

UAV-C also solves the problem of fragmented, vendor-specific drone connectivity solutions. By integrating UAV control into the 3GPP service-based architecture and exposing capabilities via the NEF, operators can offer UAS connectivity as a managed service, interoperate with UAS Service Suppliers, and support emerging U-space airspace integration. This standardization benefits operators, drone manufacturers, service providers, and regulators simultaneously.