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

Glossary term · IoT

Networked Remote ID

Networked Remote Identification and Tracking

IoT →

Networked Remote ID is a Rel-17 capability enabling 3GPP networks to provide Remote Identification and Tracking of UAVs (drones) to a USS, supporting regulatory and safety requirements for unmanned aviation.

Introduced
Rel-17
Where
Services › IMS
Specifications
2 specs
Networked Remote ID Description Purpose What changed Neighbours Specifications

Description

Networked Remote ID is a 3GPP Release 17 feature, specified in TS 23.256 with study material in TR 23.754, that enables the 3GPP network to provide Remote Identification and Tracking (RID) information for Unmanned Aerial Vehicles (UAVs) to a UAS Service Supplier (USS). Remote ID is a regulatory concept requiring drones to broadcast or otherwise make available their identity, position, and related telemetry so that authorities and other airspace users can identify and track them. Networked Remote ID uses the cellular network — rather than direct radio broadcast — as the transport and enabler for delivering this information to the USS.

The architecture builds on the broader 3GPP UAV/UAS support framework. Key network functions include the UAS NF (UAV Service Function), which acts as the entry point for UAS-related services; the NEF, which exposes capabilities to external application functions such as the USS; the UDM for subscription and authorization data; the AMF for UE reachability and mobility; and the GMLC for location information. The UAV (or its paired controller) is a UE that registers with the network and is authorized for UAS services.

In operation, the UAV's UE establishes connectivity and, through the UAS NF and NEF, the USS can request Remote ID information. The network collects and provides identification and tracking data — such as the UAV identity, location, and status — derived from network capabilities (e.g., location services, subscription data, and network-assisted information). The USS uses this to satisfy regulatory Remote ID obligations, perform airspace management, and coordinate with other stakeholders such as UTM (UAS Traffic Management) systems.

The feature distinguishes between different Remote ID service levels and supports both direct and networked delivery models. Networked Remote ID is particularly valuable where direct broadcast (e.g., Wi-Fi/Bluetooth-based Remote ID) is insufficient or unavailable, or where the operator can provide more reliable, authenticated tracking through the cellular infrastructure. Security and privacy are handled through 3GPP authentication, authorization, and exposure controls at the NEF.

Networked Remote ID matters because aviation regulators worldwide mandate Remote ID for drones, and cellular networks are well positioned to provide it reliably over wide areas. It integrates drone identification with the same 5G core that provides connectivity, enabling operators to offer value-added UAS services. The definition text is identical across Rel-17, Rel-18, and Rel-19, indicating the concept remained stable through these releases.

Purpose & Motivation

The rapid growth of unmanned aviation created a regulatory need for Remote Identification: authorities must be able to identify and track drones in flight to ensure safety, security, and accountability. Traditional direct-broadcast Remote ID (e.g., over Wi-Fi or Bluetooth) has limited range and can be spoofed or unavailable, especially beyond visual line of sight or in areas without receiver coverage.

Networked Remote ID was created to leverage the ubiquitous coverage, authentication, and management capabilities of 3GPP networks to deliver Remote ID and tracking information to USS/UTM systems. By using the cellular network as the transport and source of trusted identity and location data, it provides a more reliable and scalable alternative or complement to direct broadcast.

The feature also fits into the broader 3GPP UAS support work (Rel-17 onward), which addresses UAV identification, tracking, authorization, and command-and-control connectivity. Networked Remote ID gives operators a standards-based way to support regulatory compliance and to offer UAS service providers a trusted interface via the NEF, opening new business opportunities in the drone ecosystem.

What changed in its specifications

The latest release-to-release comparison of specifications that define Networked Remote ID. 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 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-17 Initial

Initial definition: the capability of providing Remote Identification and Tracking to a USS over 3GPP network. Introduces the UAS NF, NEF-based exposure, and integration with location and subscription data in TS 23.256.

Definition text unchanged from Rel-17; the term carried over without modification.

Definition text unchanged from Rel-17; the term carried over without modification.

Defining Specifications

3GPP specifications that define or reference Networked Remote ID, 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
TR 23.754 vh10 Study on UAS Connectivity, ID & Tracking Rel-17 read