Description
C2 (Control and Command) is a standardized service defined by 3GPP to facilitate the remote operation of Unmanned Aerial Vehicles (UAVs), also known as drones, over cellular networks, primarily 5G. It establishes a dedicated communication link between a UAV Controller (often a ground-based pilot or automated system) and the UAV itself. This link is designed to carry the essential command signals for flight control (e.g., navigation, altitude, speed) and the reception of telemetry data from the UAV (e.g., position, status, sensor readings). The service is architected to meet the stringent requirements of aviation safety, demanding ultra-reliable low-latency communication (URLLC), high availability, and secure data transmission.
The C2 architecture integrates the UAV, the 3GPP network, and the UAV Service Supplier (USS) or UAS Traffic Management (UTM) system. The UAV connects to the 5G network via the User Equipment (UE) function, which could be an onboard modem. The C2 communication path is established between the UAV Controller's application server, which may reside in a data network, and the UAV UE. The 3GPP core network, specifically the 5G Core (5GC), provides the session management, policy control, and security functions for this connection. Key network functions involved include the Access and Mobility Management Function (AMF) for registration and mobility, the Session Management Function (SMF) for PDU session establishment, and the Policy Control Function (PCF) for applying QoS policies tailored for C2 traffic, such as guaranteed bit rate and priority handling.
The service works by establishing a PDU session with specific QoS characteristics for the C2 link. Network slicing is a fundamental enabler, allowing the creation of isolated logical networks dedicated to UAV C2 communications, ensuring performance and security isolation from other consumer traffic. The C2 link can operate in direct mode, where commands flow from the controller to the UAV, or in networked mode, where the link may traverse intermediary network elements for enhanced reliability and service continuity during mobility events like handovers. Security is paramount, leveraging 5G's native security features like mutual authentication and ciphering, with additional application-layer security as defined in the service specifications.
C2's role in the network is to transform the 5G system into a reliable control channel for beyond visual line of sight (BVLOS) UAV operations. It enables the UAV to be treated as a specialized network client with service requirements on par with critical IoT and industrial automation. The network actively manages the C2 session's lifecycle, monitors its performance against QoS targets, and can trigger corrective actions, such as session modification or handover to a cell with better signal strength, to maintain the integrity of the control link. This integration is a cornerstone for enabling scalable commercial and governmental drone services.
Purpose & Motivation
C2 was created to address the lack of a standardized, scalable, and secure cellular-based communication system for controlling unmanned aircraft. Prior to 3GPP standardization, UAV operations relied on proprietary radio links (e.g., in ISM bands) which had limited range, were susceptible to interference, and could not guarantee the quality of service required for safe BVLOS operations in complex environments. These limitations hindered the scalability and integration of drones into controlled airspace alongside manned aviation. The motivation for C2 stems from the rapid growth of the drone industry and regulatory pushes worldwide to establish UAS Traffic Management (UTM) systems, which require a reliable and ubiquitous communication backbone.
The primary problem C2 solves is providing a certified communication link for UAVs that meets aviation regulatory requirements for command and control. It leverages the existing and expanding footprint of 5G networks to offer wide-area coverage, high capacity, and inherent mobility support. This allows drone operators to conduct missions over long distances without the need for deploying and maintaining their own dedicated ground infrastructure. Furthermore, 5G's capabilities in network slicing, edge computing, and precise positioning complement the C2 service, enabling advanced scenarios like dynamic geofencing, real-time collision avoidance, and low-latency processing of sensor data at the network edge.
Historically, the integration of cellular technology for UAV control was ad-hoc. 3GPP's work, starting in Release 15, provided the necessary architectural framework and service definitions to ensure interoperability between UAVs, controllers, and mobile network operators globally. This standardization was crucial for network operators to offer C2 as a commercial service with well-defined performance SLAs and for aviation authorities to recognize cellular networks as a valid means of compliance for C2 link communications. It addresses the limitations of previous non-standardized approaches by providing a holistic solution encompassing connectivity, security, identification, and service management.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (40 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-15, normative work from Rel-16.
In Release 16, the C2 function was enhanced to enable the detection and reporting of a problematic UAV controller to the Uncrewed Arial System Traffic Management (UTM), thereby supporting UTM's role in oversight and regulation. Furthermore, specifications were clarified regarding the identity of the UAV controller data, which is essential for the UTM to correctly associate a UAV with its controller as a single UAS. These additions strengthen the network's support for reliable and accountable UAS operations managed by the UTM.
In Release 17, the C2 (Command and Control) function introduced formal definitions for C2 communication and its control modes (Steer to waypoints, Direct stick steering, Automatic flight by UTM, and Approaching autonomous navigation infrastructure), along with new procedures for authorizing, revoking, and switching these communication modes. It also added specific support for C2 authorization within EPS networks and defined mechanisms for the network to reject PDN connections when the UAS service is not permitted. These enhancements provided a more complete framework for managing Uncrewed Aerial System operations over 3GPP networks.
- Definition and introduction of C2 Communication TS 22.125CR0017
- Clarification of Control Modes in C2 communication TS 22.125CR0027
- Correction to the input and output of Notify C2 communication mode switching operation TS 23.255CR0011
- Correction to add the missing API operation for C2 operation mode configuration complete notification TS 23.255CR0012
- Correction to the C2 operation mode switching confirmation TS 23.255CR0015
- Corrections for operations of C2 communication mode switching TS 23.255CR0024
+ 11 more changes
In Release 18, the C2 function introduced new support for Direct C2 communication, including the specific capability for Direct C2 availability reporting. The release also provided clarifications and corrections to the authorization procedures for this direct mode, specifically refining the Direct C2 authorization and UUAA procedures.
- Support for C2 direct mode availability reporting TS 23.255CR0046
- Support for direct C2 communication TS 23.256CR0075
- Clarification on Direct C2 authorization procedure TS 29.256CR0017
- Corrections to Direct C2 authorization via UUAA procedure TS 23.256CR0084
- Direct C2 authorization exceptions TS 23.256CR0085
- Fixing reference towards UUAA-SM procedure for Direct C2 TS 23.256CR0108
+ 2 more changes
In Release 19, key enhancements for the C2 function introduced **Dual Network-Assisted C2 communications** and improved **UTM-Navigated C2** procedures to support simultaneous links. These updates focused on significantly increasing C2 communication reliability through mechanisms for redundant user plane paths and improved traffic redundancy. The release also included necessary corrections and completion of the definitions for these dual communication modes.
- Improved redundancy for command and control (C2) traffic TS 23.255CR0049
- Simultaneous link support for UTM-Navigated C2 and clarifications TS 23.255CR0053
- Support of C2 communication reliability TS 23.256CR0132
- Adding C2 Communication Reliability with Redundant User Plane Paths to Annex TS 23.256CR0144
- Improved redundanncy for command and control (C2) traffic related procedure TS 24.257CR0035
- Update structure and data semantics to support network assisted C2 TS 24.257CR0046
+ 7 more changes
Explore further
Broader topics and technologies where C2 plays a role.
Defining Specifications
3GPP specifications that define or reference C2, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.125 vj20 | UAS Requirements via 3GPP System | Rel-19 |
| TR 22.843 vj20 | Study on Uncrewed Aerial Vehicle (UAV) Phase 3 | Rel-19 |
| TS 23.255 vj50 | UAS Application Layer Support | Rel-19 |
| TS 23.256 vj50 | UAS Support Architecture Enhancements | Rel-19 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TR 23.755 vh00 | Study on app layer support for UAS | Rel-17 |
| TS 24.257 vj40 | UAS Application Enabler (UAE) Layer | Rel-19 |
| TS 28.853 vj10 | Charging for Uncrewed Aerial Systems | Rel-19 |
| TS 29.256 vj30 | UAS-NF Stage 3 Protocol Specification | Rel-19 |
| TS 29.257 vj40 | Application layer support for Uncrewed Aerial System (UAS) | Rel-19 |
| TR 33.891 vi00 | Security and Privacy Threats for UAVs and UAM | Rel-18 |
| TS 38.811 vf40 | Study on NR Support for Non-Terrestrial Networks | Rel-15 |