Description
The Networked UAV Controller is a functional entity defined in 3GPP's UAV (aerial) study and normative work, primarily documented in TR 23.754 (architecture enhancements for UAV) and TS 23.256 (support of Uncrewed Aerial Systems). It represents the ground-side or remote-side control endpoint that pilots or operates an Unmanned Aerial Vehicle (UAV), but with a crucial distinction: instead of communicating with the UAV over a direct point-to-point radio link (such as a proprietary ISM-band remote control), the controller is attached to the 3GPP network, and the command-and-control (C2) traffic traverses the 3GPP network to reach the UAV, which is also connected to the 3GPP network.
Architecturally, the Networked UAV Controller is treated as a UE (User Equipment) or as an application client served through a UE. The UAV itself is also a 3GPP-connected device (a UAV UE). The C2 link between them is carried over the mobile network, potentially through a UAV application server or via a direct UE-to-UE path. 3GPP defines several C2 communication patterns: direct C2 over the user plane using a UAV-to-UAV or controller-to-UAV path, indirect C2 through an application server (e.g., a USS/UTM-connected server), and network-assisted C2 where the operator's core network provides routing, QoS, and policy support. The Networked UAV Controller is the endpoint that initiates or terminates this C2 communication.
The concept matters because regulatory frameworks (such as those from ICAO, EASA, and FAA) increasingly require reliable, authenticated, and traceable command-and-control links for drones flying beyond visual line of sight (BVLOS). A direct radio link has limited range and no inherent identity or authorization mechanism. By making the controller a 3GPP network subscriber, the network can authenticate it, authorize flight operations, enforce geofencing policies, apply QoS to the C2 link, and provide location and tracking information to UAS Traffic Management (UTM) systems.
Key network functions involved include the NEF (Network Exposure Function), which exposes UAV-related capabilities such as location reporting and C2 authorization to authorized third parties; the UDM, which stores UAV and controller subscription data; the PCF, which applies policy and QoS for C2 traffic; and the SMF/UPF, which establish the PDU sessions carrying C2. 3GPP also defines UAV-specific identifiers and authorization procedures so that a UAV can only accept C2 from an authorized controller, and so that the network can detect and report unauthorized UAV operation.
The Networked UAV Controller also participates in the broader UAS ecosystem. It may interact with a UAS Service Supplier (USS) or UTM system through APIs exposed by the mobile operator. The controller's identity, the UAV's identity, and the pairing between them are validated by the network. This enables services such as remote identification, flight authorization, and dynamic re-routing.
Purpose & Motivation
The Networked UAV Controller exists to solve a fundamental limitation of traditional drone remote controls: short range and no network-level trust. Legacy RC links operate on unlicensed spectrum with limited range and no authentication by any infrastructure, making beyond-visual-line-of-sight operations difficult to authorize and monitor. By defining the controller as a 3GPP-connected entity, the network becomes an active participant in the C2 path, able to authenticate both ends, enforce policy, and provide location and identity to regulators.
It also addresses the need for standardized interfaces between the mobile network and the UAS ecosystem. Aviation authorities require remote identification and traffic management (UTM). A controller that is a network subscriber can be identified, located, and authorized through standardized 3GPP procedures, enabling operators to offer drone connectivity as a service with SLAs.
Finally, it enables new business models for mobile operators — providing C2 connectivity, UAV tracking, and geofencing as network services — while giving drone operators reliable, wide-area command links that leverage existing cellular coverage rather than bespoke radio infrastructure.
What changed in its specifications
The latest release-to-release comparison of specifications that define Networked 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 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced in TR 23.754 and TS 23.256: a UAV Controller connected to the 3GPP network and connected to the UAV via a 3GPP network. This established the architectural split between networked and direct-link controllers and enabled C2 authorization, UAV identification, and UTM exposure.
Defining Specifications
3GPP specifications that define or reference Networked 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 |
| TR 23.754 vh10 | Study on UAS Connectivity, ID & Tracking | Rel-17 read |