3GPP Unmanned Aerial Vehicle Identifier

Description

The 3GPP UAV ID is an identifier assigned by the 3GPP system and used by external Application Functions (AFs) — most notably the UAS Service Supplier (USS) — to identify an Unmanned Aerial Vehicle (UAV) within the 3GPP ecosystem. It is defined in 3GPP TS 23.256, which specifies the architecture enhancements for supporting Unmanned Aerial System (UAS) connectivity, identification, and tracking. The identifier is not a new standalone numbering scheme: rather, the existing Generic Public Subscription Identifier (GPSI) is used as the 3GPP UAV ID. This design choice means that the UAV is identified in the same way as any other 3GPP subscription, leveraging the mature identity framework already deployed for mobile networks.

Architecturally, the 3GPP UAV ID sits at the boundary between the 3GPP core network and the external UAS ecosystem. The UAV itself is typically a UE (or contains a UE) that registers with the 5G core network. During UAS service authorization, the UAS NF (UAS Network Function) interacts with the UDM to retrieve subscription data, and the GPSI associated with the UAV's subscription becomes the 3GPP UAV ID that is exposed to the USS via the NEF or directly through the UAS NF. This allows the USS to correlate the UAV's aviation identity (such as its civil registration number) with its cellular subscription, enabling services like remote identification, flight authorization, and traffic management.

The use of GPSI as the 3GPP UAV ID has several important implications. First, it ensures global uniqueness, since GPSIs are constructed in a way that guarantees uniqueness across PLMNs (typically in the form of an MSISDN or an external identifier in the format username@realm). Second, it enables the network to apply subscription-specific policies, such as UAS-specific QoS, aerial UE authorization, and location reporting, based on the same identity. Third, it simplifies interworking: the USS does not need to understand internal 3GPP identifiers like SUPI or 5G-GUTI; it only needs the GPSI, which is already the standard external identifier used in 3GPP service exposure.

The 3GPP UAV ID is used in several procedures defined in TS 23.256. During UAS service authorization, the UAV's GPSI is used to check whether the subscription is authorized for aerial services. During UAV tracking, the UAS NF uses the 3GPP UAV ID to report the UAV's location to the USS. During C2 (Command and Control) communication establishment, the identifier helps bind the UAV's application-layer session to its 3GPP subscription. Security aspects are covered in TS 33.256, which defines how the UAV identity is protected and authenticated, and TS 28.853 covers management aspects for UAS.

In summary, the 3GPP UAV ID is a pragmatic identity solution that reuses the GPSI to give external UAS stakeholders a stable, globally unique handle on a UAV's cellular subscription. It is a foundational element for integrating drones into cellular networks, enabling regulatory compliance (such as remote identification requirements), service authorization, and location-based UAS traffic management.

Purpose & Motivation

The 3GPP UAV ID exists to solve a fundamental interoperability problem: how can external aviation-domain entities, such as a UAS Service Supplier, reliably identify a specific drone within the cellular network? Before Rel-19, 3GPP had no standardized way to expose a UAV's identity to external AFs for UAS-specific services. The USS operates in the aviation domain and needs a stable identifier to associate flight plans, remote identification data, and traffic management information with a specific UAV. Without a standardized identifier, each implementation would invent its own mapping, leading to fragmentation and hindering regulatory compliance.

By reusing the GPSI as the 3GPP UAV ID, 3GPP avoided creating yet another identifier namespace. The GPSI was already defined as the external identifier for a 3GPP subscription, already supported by the UDM, NEF, and service exposure framework, and already understood by external partners. This reuse dramatically lowers implementation cost and accelerates deployment. It also ensures that the same identity used for UAS services can be used for other 3GPP services, providing a unified subscription view.

The identifier also addresses regulatory drivers. Aviation authorities worldwide require remote identification of drones, and cellular connectivity is a key enabler. By providing a standardized 3GPP UAV ID, the specification allows the network to serve as a trusted source of identity for regulatory purposes, bridging the gap between telecommunications and aviation governance.