Description
An Uncrewed Aerial System (UAS) in the 3GPP context refers to the integrated system comprising an Uncrewed Aerial Vehicle (UAV), commonly known as a drone, its onboard avionics, the remote pilot ground control station (GCS), and the command and control (C2) and application data links facilitated by the 3GPP network. The 3GPP system provides the secure, reliable, and high-performance communication service that enables the UAS to operate, particularly for Beyond Visual Line of Sight (BVLOS) scenarios where direct radio control is impossible.
The architecture involves several key components. The UAV itself is equipped with a 3GPP User Equipment (UE) module, often with enhanced capabilities for aerial mobility. The UAS Service Supplier (USS) is a service layer entity that may provide flight planning, authorization, and traffic management services, interacting with the UAS Traffic Management (UTM) system. The 3GPP network—comprising the 5G Core Network (5GC) and Radio Access Network (RAN)—provides the connectivity. The network exposes specific service capabilities to the USS and UAS operators through Network Exposure Functions (NEF) and Application Functions (AF).
How it works: The UAV registers with the 3GPP network like any UE. For C2 communications, dedicated QoS flows with guaranteed low latency and high reliability are established between the UAV and its GCS. The network can apply specific policies for UAS traffic, including routing optimizations, mobility management tailored for aerial paths, and enhanced security measures like mutual authentication and integrity protection. The network also supports UAS identification and remote identification services, broadcasting the UAV's identity and location for safety and security.
Its role is to transform the 3GPP network into a trusted, ubiquitous communication infrastructure for drone operations. It moves beyond simple internet access to provide managed, mission-critical services. This includes supporting UAS application data (e.g., high-definition video streaming from the drone) alongside C2, enabling network-based detection and avoidance of other UAS, and facilitating regulatory compliance through integration with UTM systems. The network's slicing capability allows operators to dedicate virtual network slices with specific performance characteristics exclusively for UAS operations.
Purpose & Motivation
The purpose of standardizing UAS support in 3GPP is to unlock the vast commercial and societal potential of drone technology by solving the fundamental challenge of reliable, long-range, and secure communication. Prior to 3GPP involvement, commercial drone operations were largely limited to Visual Line of Sight (VLOS) using direct point-to-point radio links, which have limited range and are susceptible to interference. This severely constrained applications like long-distance delivery, large-scale infrastructure monitoring, and aerial surveying.
The motivation for 3GPP's work, beginning in Release 15 and intensifying in later releases, was to leverage the existing, pervasive cellular infrastructure to provide a managed communication service for UAS. This addresses the limitations of previous approaches by offering wide-area coverage, inherent mobility support, strong security inherited from cellular standards, and the ability to support both control and high-bandwidth application data on the same link. It also enables integration with air traffic management systems, which is essential for safe, scalable deployment of drones in shared airspace.
Historically, the aviation and telecommunications domains operated separately. 3GPP's standardization creates the technical bridge, defining how cellular networks can meet the stringent latency, reliability, and availability requirements for command and control, while also supporting new service models and regulatory needs like remote identification. This convergence is a key enabler for the drone economy, allowing operators to rely on a commercial, standards-based network rather than building isolated, proprietary communication systems.
What changed in its specifications
The latest release-to-release comparison of specifications that define UAS. Each summary describes the whole specification, not only this term.
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 →Rel-19 added real-time flight path reporting, QoS-based flight route selection, no-transmit zone management, and supporting APIs/procedures for UAS applications.
Full comparison in TS 23.255 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (67 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- General description for ID_UAS feature to EPS TS 24.301CR3578
- ePCO support for UAS TS 24.301CR3604
- UAS services not allowed indication in EPS NAS message TS 24.301CR3618
- General section for ID_UAS TS 24.501CR3135
- PDU session establishment request for UAS services TS 24.501CR3418
- 5GSM cause value of PDU session establishment reject for UAS services TS 24.501CR3629
+ 30 more changes
- Support the USS re-mapping for a UAS TS 23.255CR0041
- Architectural enhancements for Rel. 18 UAS features TS 23.256CR0076
- Additional architectural enhancements for Rel. 18 UAS features TS 23.256CR0081
- To update UAS UE registration procedure TS 24.257CR0009
- Adding the security aspects of Rel-18 UAS features TS 33.256CR0027
- Correction for UAS_Ph2 TS 23.256CR0114
+ 8 more changes
- Additional requirements for UAS TS 22.125CR0047
- Additional Requirements for Remote Identification of UAS and UTM assistance requirements TS 22.125CR0049
- No-transmit zones configuration and execution for UAS TS 23.255CR0059
- Addition of functionalities for UAS_Ph3 to General concept TS 23.256CR0122
- Update XML coding to support UAS provided flight routes TS 24.257CR0047
- Add charging principles for UAS TS 32.240CR0517
+ 9 more changes
Defining Specifications
3GPP specifications that define or reference UAS, 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 read |
| TS 22.825 vg00 | UAS Remote Identification and Tracking over 3GPP | Rel-16 read |
| TR 22.843 vj20 | Study on Uncrewed Aerial Vehicle (UAV) Phase 3 | Rel-19 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.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TR 23.754 vh10 | Study on UAS Connectivity, ID & Tracking | Rel-17 read |
| TR 23.755 vh00 | Study on app layer support for UAS | Rel-17 read |
| TS 24.228 v590 | IP Multimedia Call Control Signaling Flows | Rel-5 read |
| TS 24.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 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.552 vk40 | 5G Network Performance Measurements | Rel-20 read |
| TS 28.853 vj10 | Charging for Uncrewed Aerial Systems | Rel-19 read |
| TS 28.879 vj10 | OAM for Service Management Exposure Study | Rel-19 read |
| TS 29.162 vj00 | IMS-IP Network Interworking | 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.522 vk10 | NEF Northbound Interface | Rel-20 read |
| TS 29.558 vk00 | Edge Application Enablement APIs | Rel-20 read |
| TR 29.949 vj00 | VoLTE IMS Roaming Architecture & Procedures | Rel-19 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 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TS 33.256 vj20 | Security for Uncrewed Aerial Systems (UAS) | 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 |
| TR 36.763 vh00 | NB-IoT/eMTC Support for Non-Terrestrial Networks | Rel-17 read |
| TS 38.101 vj40 | UE Radio Transmission and Reception; Satellite Access | Rel-19 read |
| TS 38.521 vj10 | UE Conformance Spec for NR Satellite Access | Rel-19 read |
| TS 38.811 vf40 | Study on NR Support for Non-Terrestrial Networks | Rel-15 read |
| TS 38.821 vg20 | NR Support for Non-Terrestrial Networks | Rel-16 read |