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.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (65 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, 3GPP introduced new capabilities for UAV support, specifically focusing on security and identification. The release added a function to detect and report a problematic UAV controller to the Unmanned Traffic Management (UTM) system. It also provided clarifications for the identity data pertaining to the UAV controller.
In Release 17, 3GPP introduced new capabilities for Uncrewed Aerial Vehicle (UAV) integration, including network exposure requirements, service restriction requirements, and KPIs for UAV services. It defined the UAV for NAS purposes and established procedures for authentication, authorization, and real-time UAV status subscription, while also introducing a CAA-level UAV ID and its association with a 3GPP UAV ID. Furthermore, the release clarified UAV tracking modes and addressed UAV replacement procedures for EPS.
- 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
- General description for UAV aspects TS 22.261CR0382
- Definition of UAV for purpose of UE NAS TS 24.501CR3218
- UAV registered as normal UE TS 24.501CR3563
+ 26 more changes
In Release 18, new work included defining an API for UAV dynamic information and establishing procedures for tracking dynamic UAVs in an application-defined area relative to a host UAV, complete with specified XML schema, structure, and data semantics. The release also introduced N2 and Xn-based handover for UAVs and clarified authorization for UAV flights, including USS involvement during PDN connectivity procedures. Furthermore, it provided clarifications and corrections on ProSe capability support, A2X capability for UAV UEs, and various other UAV-related stage-2 aspects.
- 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
In Release 19, the UAV function introduced significant enhancements for real-time flight path monitoring assistance and QoS-aware flight planning. Key new capabilities include procedures for instructing a UAV to start or stop its altitude reporting, along with updates to the XML schema and configuration procedures to support these monitoring functions. The release also specifically added UAV mobility enhancements and refined procedures for UAV-triggered network-assisted Detect and Avoid (DAA) and location reporting.
- 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
Explore further
Broader topics and technologies where UAV plays a role.
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 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.125 vj20 | UAS Requirements via 3GPP System | Rel-19 |
| TS 22.261 vk30 | 5G System Service Requirements | Rel-20 |
| TS 22.825 vg00 | UAS Remote Identification and Tracking over 3GPP | Rel-16 |
| TR 22.862 ve10 | Critical Communications Feasibility Study | Rel-14 |
| 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 24.301 vj60 | NAS protocol for Evolved Packet System | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 27.007 vj40 | AT Command Set for UE | Rel-19 |
| TS 28.853 vj10 | Charging for Uncrewed Aerial Systems | Rel-19 |
| TS 29.255 vj20 | USS Services for UAS in 5G | 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 29.274 vj50 | GTPv2-C Control Plane Protocol Specification | Rel-19 |
| TS 29.502 vj50 | 5G System; Nsmf Service Based Interface; Stage 3 | Rel-19 |
| TS 29.571 vj50 | Common Data Types for 5G Service Based Interfaces | Rel-19 |
| TS 32.240 vj40 | Charging Management Architecture & Principles | Rel-19 |
| TS 32.255 vk10 | Telecom Management; Charging for 5G Data Connectivity | Rel-20 |
| TS 32.256 vj40 | 5G Connection & Mobility Charging Spec | 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 |
| TR 33.891 vi00 | Security and Privacy Threats for UAVs and UAM | Rel-18 |
| TS 36.101 vj30 | LTE UE Radio Transmission & Reception Requirements | Rel-19 |
| TS 36.777 vf00 | Enhanced Support for Aerial Vehicles | Rel-15 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TR 38.825 vg00 | Study on NR Industrial IoT | Rel-16 |
| TR 38.901 vj10 | Channel Model for 0.5-100 GHz | Rel-19 |