Description
Uncrewed Aerial System Traffic Management (UTM) is a comprehensive service framework that leverages mobile networks to support the safe and efficient operation of drones, or Uncrewed Aerial Systems (UAS). The architecture involves multiple entities: the UAS (drone and its controller), the UTM service provider, the 3GPP network (including UE, RAN, and core network), and regulatory authorities. The 3GPP network provides reliable connectivity for Command and Control (C2) communication between the drone and its pilot or automated system, as well as for UTM service messages. Key network functions include the Network Exposure Function (NEF) to expose network capabilities to UTM service providers, the Unified Data Management (UDM) for authentication, and location services for tracking.
The system works by establishing secure data sessions over the cellular network. The drone, equipped with a 3GPP User Equipment (UE) module, connects to the network for C2 links and transmits telemetry data (position, altitude, speed). The UTM service provider, which could be a third-party or network operator, uses 3GPP-defined service enablers (like UAV-related APIs exposed via NEF) to access network information such as real-time location, identity, and flight authorization status. This data is used for traffic management functions like flight planning, dynamic geofencing, conflict detection, and coordination with air traffic control (ATC) for higher-altitude operations. Specifications such as TS 23.255 (UAV control and command via 3GPP network) and TS 23.256 (support of UAS connectivity, identification, and tracking) define the protocol details and architecture.
UTM's role is to create a managed airspace for drones, analogous to air traffic management for manned aircraft but adapted for low-altitude, high-density operations. It integrates with regulatory frameworks (like the US FAA or EU EASA) to ensure compliance. The 3GPP network provides the ubiquitous, secure, and low-latency communication backbone required for real-time UTM services. This enables beyond visual line of sight (BVLOS) operations, multiple drone fleet management, and integration into urban air mobility ecosystems.
Purpose & Motivation
UTM was created to address the growing need for managing drone traffic as commercial and recreational drone usage surged, posing risks of mid-air collisions, interference with manned aviation, and security concerns. Traditional air traffic management systems are designed for high-altitude, structured routes and cannot scale to handle numerous low-altitude drones. The motivation for 3GPP's involvement, starting in Release 16, was to leverage existing cellular infrastructure—with its wide coverage, high reliability, and built-in security—to provide a communication and service platform for UTM.
The problems UTM solves include the lack of a standardized system for drone identification, tracking, and command/control communication. Prior to 3GPP standardization, proprietary solutions and limited-range direct radio links (like Wi-Fi) were used, which were insufficient for wide-area, BVLOS operations. 3GPP UTM provides a globally scalable framework that enables service providers to offer traffic management using network capabilities like precise location, QoS differentiation for C2 links, and secure authentication. It addresses regulatory requirements for remote identification and geofencing.
Historical context includes industry and regulatory bodies pushing for standardization. 3GPP initiated work in Rel-16 as part of broader vertical expansion, recognizing cellular networks' potential to support new industries. UTM enables economic opportunities in drone delivery, infrastructure inspection, and emergency response by making drone operations safer and more manageable. It represents a convergence of telecommunications and aviation, creating a new service domain for network operators.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- Additional Requirements for Remote Identification of UAS and UTM assistance requirements TS 22.125CR0049
- Simultaneous link support for UTM-Navigated C2 and clarifications TS 23.255CR0053
- Removal of Editor's Notes in TR 22.843 on 5GS to UTM exposure of location TS 22.843CR0001
- Corrections to the Dual UTM-Navigated C2 communication mode TS 29.257CR0071
Explore further
Broader topics and technologies where UTM plays a role.
Defining Specifications
3GPP specifications that define or reference UTM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.125 vj20 | Uncrewed Aerial Systems Requirements | Rel-19 |
| TS 22.825 vg00 | UAS Remote Identification and Tracking over 3GPP | Rel-16 |
| TR 22.829 vh10 | Enhancement for UAVs; Stage 1 | Rel-17 |
| TR 22.843 vj20 | Study on Uncrewed Aerial Vehicle (UAV) Phase 3 | Rel-19 |
| TS 23.255 vk00 | UAS Application Enabler Architecture | Rel-20 |
| TS 23.256 vj50 | UAS Support Architecture Enhancements | Rel-19 |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | 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 vk00 | UAS-NF Nnef Service Based Interface Stage 3 | Rel-20 |
| TS 29.257 vk00 | UAS Application Enabler Server Services | Rel-20 |
| TS 33.256 vj20 | Security for Uncrewed Aerial Systems (UAS) | Rel-19 |
| TS 33.759 vj00 | UAS Security Enhancements Phase 3 Study | Rel-19 |
| TR 33.854 vh10 | Security aspects of Uncrewed Aerial Systems | Rel-17 |