UAE

UAS Application Enabler

Services →
Introduced in Rel-17

UAE is the 3GPP framework enabling Unmanned Aircraft System services over cellular networks, providing standardized interfaces for drone identification, authorization, flight path management, and connectivity to support safe BVLOS operations.

Category
Services
Introduced
Rel-17
Where
Services › IMS
Specifications
5 specs
UAE Description Purpose Related Classification Detected Changes Specifications

Description

The UAS Application Enabler (UAE) is a service capability defined within the 3GPP architecture to support Unmanned Aircraft Systems (UAS), commonly known as drones, using 3GPP networks. It acts as an intermediary layer between UAS Service Suppliers (USS) and the 3GPP core network, translating application-level service requests into network-specific commands and procedures. The UAE framework is primarily realized through the Network Exposure Function (NEF) in the 5G Core (5GC) or the Service Capability Exposure Function (SCEF) in the Evolved Packet Core (EPC), which securely exposes network capabilities to authorized third-party UAS applications.

Architecturally, UAE defines a set of Application Programming Interfaces (APIs) and reference points, such as Nudm, Nnef, and N5g-eir, allowing a USS to interact with the network for critical UAS functions. Key procedures include UAS identification and authentication, where the UAE can query the network to verify a drone's subscription and credentials. It also supports authorization for flight operations by checking policies and no-fly zones, and facilitates the establishment and management of Quality of Service (QoS) for command-and-control (C2) links and payload data streams, ensuring reliable, low-latency connectivity essential for safe drone operation.

Furthermore, UAE enables location and tracking services by exposing network-based or UE-assisted location information of the UAS to the USS for air traffic management. It also supports network slicing, allowing the creation of dedicated logical networks with specific performance characteristics for UAS traffic, isolating it from other mobile broadband services. The UAE's role is crucial for integrating drones into the national airspace system, providing the necessary network-assisted automation, security, and regulatory compliance for scalable commercial and governmental UAS deployments.

Purpose & Motivation

The UAE was created to address the growing need for a standardized, secure, and reliable method to integrate Unmanned Aircraft Systems into controlled airspace using ubiquitous cellular networks. Prior to its specification, drone operations, especially BVLOS, relied on non-standardized, proprietary communication links (like direct radio) which lacked scalability, inherent mobility support, and integration with broader air traffic management systems. This posed significant challenges for safety, security, and regulatory oversight, limiting the commercial potential of drone delivery, surveillance, and inspection services.

The primary motivation for UAE within 3GPP was to leverage existing and future cellular infrastructure—4G LTE and 5G—to provide a unified connectivity solution for UAS. Cellular networks offer wide-area coverage, high reliability, built-in security, and advanced features like mobility management and QoS, which are ideal for supporting drones. The UAE framework solves the problem of how to securely expose these network capabilities to external UAS service providers and regulators, enabling automated flight authorization, real-time tracking, and guaranteed communication performance. Its creation in Release 17 was driven by global regulatory pushes, such as those by the FAA and EASA, for remote identification and tracking of drones, positioning 3GPP technology as a key enabler for the digital transformation of aviation.

Classification

Part ofSCS
Related approachesNEFQoS

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 2 changes

In Release 17, the specification introduced AT commands for configuring the UAE layer and corrected the standard by adding the previously missing UAE layer registration procedure. These additions provide concrete mechanisms for device configuration and ensure a complete foundational procedure for the UAS application enabler.

  • Introduction of AT commands for UAE layer configuration clause TS 27.007CR0770
  • Correction to add the missing UAE layer registration procedure TS 23.255CR0016
Rel-18 20 changes

In Release 18, the UAS Application Enabler (UAE) function introduced new capabilities for multi-USS operations and Detect and Avoid (DAA) assistance, enabling a UAV to report these capabilities to the UAE Server for dynamic USS changes and DAA policy configuration during flight. This release also defined and completed several key service APIs, including the UAE_ChangeUSSManagement API for USS handover procedures and the UAE_DAASupport API for DAA-related event handling. Furthermore, it added the new UAE_UAVDynamicInfo API and provided essential corrections to these and existing APIs like UAE_RealtimeUAVStatus to solidify the application layer framework.

  • Addition of multi-USS capabilities to UAE layer registration TS 23.255CR0030
  • Addition of DAA assist capability to UAE layer registration TS 23.255CR0038
  • Definition of the service description clauses of the UAE_ChangeUSSManagement API TS 29.257CR0008
  • Definition of the API resources and notifications of the UAE_ChangeUSSManagement API TS 29.257CR0010
  • Definition of the API data model clause of the UAE_ChangeUSSManagement API TS 29.257CR0011
  • Definition of the OpenAPI description of the UAE_ChangeUSSManagement API TS 29.257CR0012

+ 14 more changes

Rel-19 20 changes

In Release 19, the UAS Application Enabler (UAE) function introduced new, specific API definitions and procedures to enhance support for Unmanned Aerial Systems. Key additions include the formal definition of the UAE_FlightPathMonitoring, UAE_FlightRouteSupport, and UAE_NTZManagement APIs, which provide structured service descriptions and OpenAPI specifications. Furthermore, the release specified detailed procedures for No-Trespass Zone (NTZ) support—including configuration, activation, and enforcement—and introduced ground-based Detect and Avoid (DAA) assistance via the LDGS capability.

  • Support for DAA ground-based UAE layer assistance TS 23.255CR0055
  • UAE procedure for support of flight route TS 24.257CR0038
  • Update general procedure for NTZ support over UAE layer TS 24.257CR0049
  • NTZ configuration procedure for NTZ support over UAE layer TS 24.257CR0050
  • NTZ activation procedure for NTZ support over UAE layer TS 24.257CR0051
  • UAE-layer/SEAL/LMS assisted NTZ enforcement TS 24.257CR0054

+ 14 more changes

Explore further

Broader topics and technologies where UAE plays a role.

Defining Specifications

3GPP specifications that define or reference UAE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.255 vj50 UAS Application Layer Support Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 24.257 vj40 UAS Application Enabler (UAE) Layer Rel-19
TS 27.007 vj40 AT Command Set for UE Rel-19
TS 29.257 vj40 Application layer support for Uncrewed Aerial System (UAS) Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.