Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Security

UUAA

UAV USS Authentication and Authorization

Security →

UUAA is a procedure that authenticates and authorizes an unmanned aerial vehicle with its UAS service supplier via the 3GPP network to enable safe UAS connectivity.

Introduced
Rel-17
Where
Services › IMS
Specifications
9 specs
Also in
Core Network
UUAA Description Purpose What changed Neighbours Detected Changes Specifications

Description

UUAA (UAV USS Authentication and Authorization) is a security procedure introduced in 3GPP Release 17 to support Unmanned Aerial Systems (UAS) connectivity over 3GPP networks. The procedure ensures that an Unmanned Aerial Vehicle (UAV) is authenticated and authorized by its associated USS (UAS Service Supplier) before it is allowed to use 3GPP network connectivity for UAS services. The USS is an entity that provides services to UAVs, such as flight planning, traffic management, and authorization. The UUAA procedure is performed with the support of the 3GPP system, which acts as an intermediary between the UAV and the USS.

The UUAA procedure involves several steps. First, the UAV registers with the 3GPP network (e.g., 5G system) and establishes connectivity. Then, the UAV initiates the UUAA procedure by sending a request to the USS via the 3GPP network. The 3GPP system, specifically the UAS NF (Network Function) or similar entity, facilitates the communication between the UAV and the USS. The USS authenticates the UAV based on credentials provided by the UAV, and if successful, authorizes the UAV for UAS operations. The authorization may include specific permissions, such as allowed flight areas, time restrictions, or service levels. Once the UUAA procedure is successfully completed, the 3GPP system enables connectivity for UAS services, allowing the UAV to exchange data with the USS and other UAS entities.

The UUAA procedure is defined in several 3GPP specifications, including 23.256 (Architecture enhancements to support UAS), 24.301 (NAS protocol for EPS), 24.501 (NAS protocol for 5GS), 27.007 (AT commands), 28.853 (UAS management), 29.255 (UAS NF services), 29.256 (UAS NF services), 29.502 (5G system procedures), and 33.256 (Security aspects of UAS). These specifications detail the protocol messages, security mechanisms, and procedures for UUAA. The procedure uses the 3GPP system's authentication and authorization framework, which may involve the AUSF (Authentication Server Function) and UDM (Unified Data Management) in 5G core networks.

The UUAA procedure is critical for ensuring that only authorized UAVs are allowed to operate using 3GPP connectivity. This is important for safety and regulatory compliance, as UAV operations must be coordinated with air traffic management systems. The USS is responsible for authorizing UAVs based on their registration and operational requirements. The 3GPP system provides the secure communication channel and may also assist in the authentication process. The UUAA procedure is part of the broader UAS architecture defined in 3GPP, which includes entities such as the UAV, UAV Controller (UAVC), USS, and 3GPP network functions.

In Release 17, the UUAA procedure was introduced with the initial definition. In Release 18, the definition text was slightly reformatted but the content remained the same. In Release 19, the definition was carried over unchanged. The UUAA procedure continues to be a key enabler for integrating UAVs into 3GPP networks, supporting the growing market for commercial and civil UAV applications.

Purpose & Motivation

The UUAA procedure was created to address the security and authorization requirements for UAVs operating over 3GPP networks. As UAVs become increasingly common for commercial, civil, and government applications, there is a need to ensure that they are properly authenticated and authorized before they can use cellular connectivity. Without such a procedure, unauthorized UAVs could potentially access network resources, posing security risks and interfering with legitimate operations.

Before UUAA, UAVs might have used generic 3GPP connectivity without specific authorization from a USS. This was insufficient because UAV operations require coordination with airspace management and must comply with regulations. The USS is the entity responsible for authorizing UAV flights, and it needs to verify the identity and credentials of the UAV. The UUAA procedure provides a standardized way for the UAV to authenticate with the USS via the 3GPP network, leveraging the network's security features.

The UUAA procedure also solves the problem of integrating UAVs into the 3GPP ecosystem. By defining a clear procedure, 3GPP enables interoperability between different USS providers and network operators. This allows UAVs to operate seamlessly across different networks and regions, as long as they are authorized by their USS. The procedure is part of the broader UAS architecture that 3GPP has developed to support UAV communications, including command and control (C2) links, telemetry, and payload data. The UUAA procedure ensures that these communications are secure and authorized, which is essential for safe and reliable UAV operations.

What changed in its specifications

The latest release-to-release comparison of specifications that define UUAA. Each summary describes the whole specification, not only this term.

TS 23.256Rel-18 → Rel-19

Rel-19 adds NEF-assisted pre-flight planning, USS changeover, and network-assisted detect-and-avoid to TS 23.256. It also adds no-transmit zone enforcement for UAV UEs and altitude reporting.

Full comparison in TS 23.256 →
TS 24.301Rel-18 → Rel-19

Rel-19 adds store-and-forward satellite operation for NTN, control plane CIoT data overhead reduction via EMM TRANSPORT and Data container IE, and RAT utilization control. It also adds disaster roaming indications and MINT-EPS support, plus MPS priority for messaging paging.

Full comparison in TS 24.301 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 48 changes
  • UUAA failure TS 24.301CR3557
  • UUAA completion after default EPS bearer context activation TS 24.301CR3593
  • UUAA: multiple round trips TS 24.301CR3594
  • Uplink control during EPS UUAA-SM TS 24.301CR3615
  • UUAA re-authentication, re-authorization, and revocation TS 24.301CR3628
  • UUAA and C2 pairing authorization at attach - UE procedure on receiving side TS 24.301CR3636

+ 42 more changes

Rel-18 15 changes
  • Corrections to Direct C2 authorization via UUAA procedure TS 23.256CR0084
  • Fixing reference towards UUAA-SM procedure for Direct C2 TS 23.256CR0108
  • Reference correction in UUAA Revocation TS 23.256CR0117
  • Added DNN and S-NSSAI as indication for UUAA-SM and C2 authorization TS 24.501CR5037
  • NF name correction for UUAA-MM TS 24.501CR5218
  • Security and privacy for Direct C2 communications for UUAA-SM procedure TS 24.501CR5732

+ 9 more changes

Rel-19 3 changes
  • Correction to UUAA-MM TS 24.501CR6679
  • Removal of Editor’s Note regarding the support for UAV triggered UUAA from UAS3 TS 33.256 TS 33.256CR0054
  • Unsubscribing from the UUAA-related notifications TS 23.256CR0184

Defining Specifications

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

SpecificationTitleRelease
TS 23.256 vj50 UAS Support Architecture Enhancements 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.502 vk10 5G SMF Service Based Interface Stage 3 Rel-20 read
TS 33.256 vj20 Security for Uncrewed Aerial Systems (UAS) Rel-19 read