UAS

NF Uncrewed Aerial System Network Function

Services →
Introduced in Rel-15 Also in: Core Network, Security

UAS is a 3GPP network function that provides service exposure, authorization, and traffic management to enable secure cellular connectivity for uncrewed aerial systems like drones.

Category
Services
Introduced
Rel-15
Where
Services › IMS
Also touches
2 segments
Specifications
36 specs
UAS Description Purpose Related Classification Detected Changes Specifications

Description

The NF Uncrewed Aerial System Network Function (UAS NF) is a core network element introduced by 3GPP to support Uncrewed Aerial Systems (UAS), commonly known as drones, over 3GPP networks (4G LTE and 5G). It is part of the service-based architecture (SBA) in the 5G Core network, operating as a specialized Network Function (NF) that interacts with other core NFs like the Unified Data Management (UDM), Network Exposure Function (NEF), and Policy Control Function (PCF). The primary role of the UAS NF is to authorize UAS operations, manage UAS service subscriptions, and facilitate communication between the UAS Service Supplier (USS), the UAS operator, and the 3GPP network.

Architecturally, the UAS NF acts as a central control point. It authenticates and authorizes a UAS (comprising the Uncrewed Aerial Vehicle - UAV - and its Remote Controller) before allowing it to access network services for command & control (C2) and payload data links. It interfaces with the USS/UTM (UAS Traffic Management) system, which is the external service provider managing airspace and flight approvals. The UAS NF relays flight authorization requests from the UAS operator (via the UE) to the USS and enforces the authorization decisions received. It also supports location reporting of UAVs to the USS for airspace awareness and can apply specific QoS policies for UAS traffic through the PCF.

Key components of the UAS service framework include the UAS NF itself, the UAS service subscription profile stored in the UDM, and the service interfaces (e.g., Nuu, Nudm, Nnef). The UAS NF works by first validating the UAS identity and subscription. For a flight operation, it receives a UAS flight authorization request, potentially including the planned flight path. It forwards this to the authorized USS. Upon receiving approval, the UAS NF may instruct the network to establish dedicated QoS flows for the C2 link with high reliability and low latency guarantees. It also supports continuous or triggered location reporting during the flight. This end-to-end management enables beyond visual line-of-sight (BVLOS) operations by providing a secure, tracked, and network-managed communication link.

Purpose & Motivation

The UAS NF was created to address the growing need for safe, scalable, and regulated integration of drones into national airspace using ubiquitous cellular networks. Prior to its specification, drones used direct point-to-point radio links (e.g., Wi-Fi) with limited range, no inherent network-based authorization, and no integration with air traffic management systems. This posed safety, security, and scalability challenges for commercial drone applications. The 3GPP network provides wide-area coverage, robust security, mobility support, and high capacity, making it an ideal candidate for UAS connectivity.

The motivation for standardizing the UAS NF stemmed from regulatory pushes worldwide (e.g., by FAA, EASA) requiring remote identification, geofencing, and traffic management for drones. 3GPP initiated work to define network support for UAS to enable compliant commercial services. The UAS NF solves the problem of how a mobile network can authenticate a drone as a legitimate user, authorize its specific flight, and provide the necessary quality of service and location tracking services demanded by regulators and UAS service providers.

It addresses the limitations of ad-hoc connectivity by providing a standardized, secure framework. This framework allows a single drone operator to manage a fleet across wide geographic areas using existing cellular infrastructure, enables seamless handover between cells during flight, and ensures that critical C2 links are protected and prioritized. The creation of the UAS NF in 3GPP Release 15 and its enhancements in later releases represent a pivotal step in enabling advanced drone services like package delivery, infrastructure inspection, and aerial surveillance at scale.

Classification

Part ofNEF
Specific typesIMUUAV-CUASSUAV

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific 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.

Rel-16 1 change

In Release 16, the foundational requirements for the Uncrewed Aerial System (UAS) Network Function were introduced, focusing on enabling remote identification, tracking, and secure communication with UAS Traffic Management (UTM). This included specific capabilities for the 3GPP system to provide UTM with UAS identities and live location data, to support secure command and control (C2) communication, and to differentiate UAS-capable user equipment. The release also provided clarifications on core UAS terminology and the system model, defining the relationship between the UAV, its controller, and the supporting network.

  • Clarifications on UAS terminology and model TS 22.125CR0021
Rel-17 36 changes

In Release 17, the UAS (Uncrewed Aerial System) Network Function enhancements introduced support for EPS networks, including mechanisms for UAS service indication and rejection in EPS NAS messages and ePCO. The release also specified procedures for PDU session establishment for UAS services, including handling for scenarios with valid aerial subscriptions but failed authentication, and defined new 5GSM cause values for session rejection. Furthermore, it provided clarifications and corrections on UAS NF discovery, selection, architecture, and the usage of services like Nnef_AFsessionWithQoS for Command and Control (C2) authorization.

  • 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

Rel-18 14 changes

In Release 18, the UAS (NF) function was enhanced with architectural updates to support USS (UAS Service Supplier) re-mapping and refined registration procedures for the UAS. It introduced explicit network rejection mechanisms for C2 communication PDN connections or PDU sessions when the UAS service is not allowed, including clarifications for transmitting this indication to the UE. Furthermore, the release added specific security aspects for these UAS features and updated the handling of UAS service data and EAS (External Application Server) types.

  • 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

Rel-19 14 changes

In Release 19, the UAS (NF Uncrewed Aerial System Network Function) was enhanced with new capabilities for operational management and charging. Key additions include the configuration of no-transmit zones, support for provisioning UAS-provided flight routes, and the introduction of specific charging principles and requirements for UAS services. The release also focused on fulfilling additional requirements for remote identification and UTM assistance, while performing permanent alignment between the different specification stages.

  • 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

+ 8 more changes

Explore further

Broader topics and technologies where UAS plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 22.125 vj20 UAS Requirements via 3GPP System Rel-19
TS 22.825 vg00 UAS Remote Identification and Tracking over 3GPP Rel-16
TR 22.843 vj20 Study on Uncrewed Aerial Vehicle (UAV) Phase 3 Rel-19
TS 23.255 vj50 UAS Application Layer Support Rel-19
TS 23.256 vj50 UAS Support Architecture Enhancements Rel-19
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TR 23.754 vh10 Study on UAS Connectivity, ID & Tracking Rel-17
TR 23.755 vh00 Study on app layer support for UAS Rel-17
TS 24.228 v1500 IP Multimedia Call Control Signaling Flows Rel-5
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
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 28.879 vj10 OAM for Service Management Exposure Study Rel-19
TS 29.162 vj00 IMS-IP Network Interworking 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.558 vj40 Enabling Edge Applications Rel-19
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures 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 32.808 v1800 Common User Profile Storage Framework Rel-8
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14
TS 33.256 vj10 Security for Uncrewed Aerial Systems (UAS) 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
TR 36.763 vh00 NB-IoT/eMTC Support for Non-Terrestrial Networks Rel-17
TS 38.811 vf40 Study on NR Support for Non-Terrestrial Networks Rel-15
TS 38.821 vg20 NR Support for Non-Terrestrial Networks Rel-16
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.