Description
Direct C2 Communication is a UAV (Unmanned Aerial Vehicle) connectivity mode defined in 3GPP specifications 23.256 and 23.755. In this mode, the UAV controller and the UAV establish a direct Command and Control (C2) link with each other, and both endpoints are registered to the 5G network. The 5G network provides the radio resource configuration and scheduling that enables this direct link, ensuring that the communication is under network control and can be managed for interference, QoS, and regulatory compliance.
The architecture relies on the 5G system acting as an enabler rather than a relay. Both the UAV and the UAV controller are UEs registered to the 5G network. The network configures and schedules the radio resources used for the direct C2 link, which in later releases is explicitly realized over the PC5 reference point (the sidelink interface). This means the C2 traffic flows directly between the two endpoints over the air interface without traversing the core network user plane, while the network retains control over resource allocation and policy.
In Rel-17, the definition emphasized that both endpoints are registered to the 5G network and that the network configures and schedules the radio resources for direct C2 communication. This reflects the initial design where the 5G network provides the necessary radio resource management for the direct link. In Rel-18, the definition was revised to state that the UAV controller and UAV establish a direct C2 link over the PC5 reference point, making the sidelink nature of the communication explicit and aligning the terminology with the broader 5G ProSe and sidelink framework.
The key components include the UAV (aerial UE), the UAV controller (a controller UE), the 5G RAN providing resource configuration and scheduling, and the core network functions responsible for UAV authorization, policy control, and C2 link management. The network can enforce UAV identification and tracking, C2 link monitoring, and QoS differentiation for C2 traffic. Because the C2 link is critical for flight safety, the network must ensure reliability and low latency for the control messages exchanged between the controller and the UAV.
Direct C2 Communication is one of several C2 connectivity modes in 3GPP, alongside network-assisted and Uu-based C2 communication. It is particularly relevant for scenarios where the UAV and controller are in proximity and can benefit from low-latency direct communication, while still relying on the 5G network for resource management, authorization, and regulatory compliance. This mode supports the integration of UAVs into 5G networks and enables use cases such as aerial inspection, delivery, and surveillance.
Purpose & Motivation
Direct C2 Communication exists to enable safe and reliable command and control of UAVs within 5G networks while allowing direct, low-latency communication between the UAV and its controller. Traditional cellular communication routes all traffic through the core network, which can introduce latency and overhead. By allowing a direct C2 link under network control, 3GPP provides a mechanism that balances low-latency direct communication with the network's need to manage resources, enforce policy, and ensure regulatory compliance.
The concept was motivated by the rapid growth of commercial UAV operations and the need for standardized connectivity that supports beyond-visual-line-of-sight (BVLOS) flights. Regulatory frameworks require reliable C2 links, and 5G networks can provide the coverage, reliability, and management capabilities needed. The direct mode addresses scenarios where the UAV and controller are close and can communicate directly, reducing latency and network load.
The evolution from Rel-17 to Rel-18 clarified that the direct C2 link is established over the PC5 reference point, aligning UAV communications with the 5G sidelink framework. This clarification helps implementers and regulators understand that the direct link uses standardized sidelink technology, which has well-defined security, resource allocation, and QoS mechanisms.
What changed in its specifications
The latest release-to-release comparison of specifications that define Direct C2 Communication. 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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-17, normative work from Rel-18.
Defining Specifications
3GPP specifications that define or reference Direct C2 Communication, 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.755 vh00 | Study on app layer support for UAS | Rel-17 read |