Description
In 3GPP standards, an Uncrewed Aerial Vehicle (UAV) refers not only to the physical aircraft but also to its integration as a User Equipment (UE) within the cellular network. This integration enables UAVs to use 3GPP networks for Command and Control (C2) communication, tracking, and payload data links. The 3GPP system provides the connectivity infrastructure, requiring enhancements to support UAV-specific requirements such as altitude-based service, mobility, identification, and security.
Architecturally, a UAV connects to the network like any other UE, but it is associated with additional network functions and external systems. Key network entities involved include the Access and Mobility Management Function (AMF) for registration and mobility, the Session Management Function (SMF) for PDU session handling, and the Network Exposure Function (NEF) for exposing network capabilities to external UAS Service Suppliers (USS) or UAS Traffic Management (UTM). The UAV's subscription and authorization are managed by the Unified Data Management (UDM). The UAV itself may have specific capabilities, such as reporting its 3D location (latitude, longitude, altitude) and UAV identity, which are communicated to the network via the Control Plane or User Plane.
How it works: A UAV, equipped with a 3GPP modem, attaches to the network. During registration, it may indicate its UAV capabilities. The network can then apply specific policies, such as restricting service to certain geographical zones (geo-fencing) or prioritizing its C2 traffic. For tracking, the network can provide location services (e.g., via LTE Positioning Protocol or 5G NR positioning) to authorized external entities (like a UASS) upon subscription. The UAV's C2 communication typically uses a dedicated PDU session with guaranteed QoS (low latency, high reliability). The network interfaces with UTM systems to exchange flight authorization, telemetry, and traffic management information, creating a cohesive ecosystem for safe UAV operations.
Purpose & Motivation
The standardization of UAV support in 3GPP addresses the critical need for a reliable, wide-area, and secure communication network for drones, particularly for Beyond Visual Line of Sight (BVLOS) operations. Traditional drone communication relied on direct radio links (e.g., Wi-Fi, proprietary C2) with limited range and lack of seamless mobility, hindering scalable commercial applications. Cellular networks offer ubiquitous coverage, high reliability, security, and advanced features like network slicing.
Initiated in Release 14 as a study item, the work was motivated by the rapid growth of the drone industry and regulatory pushes for UAS Traffic Management (UTM). 3GPP networks solve the limitations of previous approaches by providing a managed, QoS-aware infrastructure. This enables diverse applications like aerial delivery, surveillance, and inspection. The evolution through subsequent releases has continuously enhanced support, adding features like UAV identification, altitude reporting, interference mitigation with terrestrial users, and direct UAV-to-network and UAV-to-UAV communication, positioning cellular technology as a foundational enabler for the future of autonomous aerial systems.
What changed in its specifications
The latest release-to-release comparison of specifications that define UAV. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 adds UAV Phase 3 requirements to TS 22.125 covering safety, flight path and zones management, and UTM assistance. It also changes general, exposure, restriction, UxNB and security requirements.
Full comparison in TS 22.125 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (64 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- CR to 22.125 Network exposure requirements for UAV TS 22.125CR0018
- Service restriction requirements for UAV TS 22.125CR0020
- KPIs for UAV services TS 22.125CR0026
- Definition of UAV for purpose of UE NAS TS 24.501CR3218
- UAV registered as normal UE TS 24.501CR3563
- Added reference to UAV procedures TS 29.274CR2044
+ 25 more changes
- Unsubscribe UAV dynamic information TS 23.255CR0047
- UAV dynamic information API TS 23.255CR0048
- N2 and Xn based HO for UAV TS 23.256CR0098
- XML schema for tracking dynamic UAVs in an application defined area relative to a host UAV procedure TS 24.257CR0028
- Structure and Data semantics for tracking dynamic UAVs in an application defined area relative to a host UAV procedure TS 24.257CR0027
- Clarification on ProSe capability support for UAV UEs TS 23.256CR0082
+ 6 more changes
- Support for real time UAV flight path monitoring assistance TS 23.255CR0050
- Require QoS along UAV planned flight path TS 23.255CR0052
- Assist selecting UAV flight path based on QoS TS 23.255CR0054
- Support new functionalities of UAV NF TS 23.256CR0125
- Support of UAV flight planning and monitoring TS 23.256CR0131
- Instructing a UAV to perform its altitude reporting TS 23.256CR0150
+ 13 more changes
Defining Specifications
3GPP specifications that define or reference UAV, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.125 vj20 | Uncrewed Aerial Systems Requirements | Rel-19 read |
| TS 22.261 vk81 | 5G Service and Operational Requirements | Rel-20 read |
| TS 22.825 vg00 | UAS Remote Identification and Tracking over 3GPP | Rel-16 read |
| TR 22.862 ve10 | Critical Communications Feasibility Study | Rel-14 read |
| TS 23.255 vk10 | UAS Application Enabler Architecture | Rel-20 read |
| TS 23.256 vj50 | UAS Support Architecture Enhancements | Rel-19 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TR 23.755 vh00 | Study on app layer support for UAS | Rel-17 read |
| TS 24.257 vj40 | UAS Application Enabler (UAE) Layer | Rel-19 read |
| TS 24.301 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 27.007 vk00 | AT Command Interface for Mobile Terminals | Rel-20 read |
| TS 28.853 vj10 | Charging for Uncrewed Aerial Systems | Rel-19 read |
| TS 29.255 vk00 | UAS-specific NAF Service Based Interface | Rel-20 read |
| TS 29.256 vk10 | UAS-NF NEF Service Protocols | Rel-20 read |
| TS 29.257 vk10 | UAS Application Enabler Server APIs | Rel-20 read |
| TS 29.274 vk00 | GTPv2-C Control Plane Protocol | Rel-20 read |
| TS 29.502 vk10 | 5G SMF Service Based Interface Stage 3 | Rel-20 read |
| TS 29.571 vk10 | 5G Common Data Types | Rel-20 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.255 vk30 | 5G Data Connectivity Converged Charging | Rel-20 read |
| TS 32.256 vk10 | 5G Connection and Mobility Charging | Rel-20 read |
| TS 33.256 vj20 | Security for Uncrewed Aerial Systems (UAS) | Rel-19 read |
| TS 33.759 vj00 | UAS Security Enhancements Phase 3 Study | Rel-19 read |
| TR 33.854 vh10 | Security aspects of Uncrewed Aerial Systems | Rel-17 read |
| TR 33.891 vi00 | Security and Privacy Threats for UAVs and UAM | Rel-18 read |
| TS 36.101 vk10 | E-UTRA UE RF Requirements | Rel-20 read |
| TS 36.777 vf00 | Enhanced Support for Aerial Vehicles | Rel-15 read |
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TR 38.825 vg00 | Study on NR Industrial IoT | Rel-16 read |
| TS 38.901 vj50 | 5G NR Channel Model | Rel-19 read |