UTM

Uncrewed Aerial System Traffic Management

Services →
Introduced in Rel-16 Also in: Security

UTM is a 3GPP service framework that uses cellular networks to manage uncrewed aerial system traffic by providing communication, identification, tracking, and coordination for safe, low-altitude operations.

Category
Services
Introduced
Rel-16
Where
Services › IMS
Also touches
1 segments
Specifications
15 specs
UTM Description Purpose Detected Changes Specifications

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 Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (22 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 5 changes

In Release 16, 3GPP formally defined the Uncrewed Aerial System Traffic Management (UTM) function and clarified its roles, including centralized and decentralized architectures for services like collision avoidance. The release specified UTM's capability to manage UAS identification, tracking, and authorization, and introduced the "UTM-Navigated C2 communication" mode for autonomous flight plan management and monitoring. Furthermore, it defined mechanisms for the 3GPP system to report problematic UAV controllers to the UTM and to provide UTM with UAS data, live locations, and authorization outcomes.

  • Definition and Clarification for UTM TS 22.125CR0006
  • Detect and report the problematic UAV controller to UTM TS 22.125CR0005
  • Clarification of Centralized UTM TS 22.125CR0003
  • Clarification of Decentralized UTM for Collision Avoidance TS 22.125CR0004
  • Clarification of UTM Definition TS 22.125CR0002
Rel-17 6 changes

In Release 17, key refinements were made to the Uncrewed Aerial System Traffic Management (UTM) function, including enhanced context management for the "UUAA" (UAS UTM Authentication and Authorization) procedure and improved mechanisms for updating aerial service availability using a UAV Control Unit (UCU). The release also focused on cleaning up procedures for managing lists of aerial UEs in a geographic area and ensuring terminology alignment to consistently use "uncrewed" and "USS/UTM" throughout the specifications.

  • Alignment of the term "USS/UTM" throughout TS 23.255 TS 23.255CR0019
  • Clean up for List of Aerial UEs in a geographic area TS 23.256CR0008
  • Correction of UUAA when aerial subscription is missing TS 23.256CR0032
  • UUAA context management TS 23.256CR0049
  • Aerial Service Availability Update using UCU TS 23.256CR0072
  • Terminology alignment to use uncrewed TS 23.255CR0004
Rel-18 2 changes

In Release 18, the UTM (Uncrewed Aerial System Traffic Management) function introduced new procedures for Multi-USS management, enhancing the coordination between the network and multiple UAS Service Suppliers. It also addressed the delivery management of SEAL data, which is part of the UAS data sent to the UTM, ensuring the system can support evolving UTM applications and extended data sets as required.

  • Multi-USS management procedures TS 24.257CR0010
  • Undefined reference to SEAL data delivery management TS 24.257CR0034
Rel-19 9 changes

In Release 19, the UTM function introduced enhanced redundancy and simultaneous link support for Command and Control (C2) traffic, specifically improving the procedures for UTM-Navigated C2 communication mode management. It also added requirements for remote identification of UAS, enabling the UTM to associate the UAV and its controller and receive detailed UAS data. Furthermore, the release included updates to flight path management and clarified altitude reporting thresholds and periodicity for aerial UEs.

  • Additional Requirements for Remote Identification of UAS and UTM assistance requirements TS 22.125CR0049
  • Improved redundancy for command and control (C2) traffic TS 23.255CR0049
  • Simultaneous link support for UTM-Navigated C2 and clarifications TS 23.255CR0053
  • Improved redundanncy for command and control (C2) traffic related procedure TS 24.257CR0035
  • Necessary updates and corrections to C2 Communication Mode management procedures TS 29.257CR0046
  • Removal of Editor's Notes in TR 22.843 on 5GS to UTM exposure of location TS 22.843CR0001

+ 3 more changes

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.

SpecificationTitleRelease
TS 22.125 vj20 UAS Requirements via 3GPP System 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 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
TS 33.256 vj10 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