Description
Networked Remote Identification (NRID) is a 3GPP service defined to support the identification and tracking of Unmanned Aerial Systems (UAS), commonly known as drones, using the cellular network infrastructure. It operates as a network-based service where the drone, equipped with a 3GPP User Equipment (UE), transmits its identification and location information to a network entity known as the USS (UAS Service Supplier) or a UTM (UAS Traffic Management) system via the 5G core network. This transmission is authenticated and secured using standard 3GPP security mechanisms, ensuring the integrity and confidentiality of the data. The architecture involves the UE (drone), the 5G RAN and Core Network (including AMF, SMF), and external entities like the USS/UTM and the NRID Management Function, which orchestrates the identification sessions.
The service works by establishing a dedicated PDU session or utilizing an existing one for the NRID data transfer. The drone's UE periodically or on-demand sends Remote ID messages containing critical information such as the drone's unique identifier (e.g., Serial Number, CAA-assigned ID), its real-time geographical position, altitude, velocity, and the location of the control station. This data is packaged according to defined protocols (e.g., ASTM Remote ID standard) and transported over the user plane of the 3GPP network. The network can apply specific QoS policies to ensure timely delivery of this safety-critical information. The NRID Management Function, potentially collocated with a Network Exposure Function (NEF), authorizes the drone's service request and manages the association between the drone's 3GPP subscription and its remote ID credentials.
Key components include the NRID-enabled UE (the drone), the 5G Core Network functions (AMF for mobility, SMF for session management, UPF for data forwarding), and the NRID Management Function. The latter acts as the interface between the 3GPP network and the external UAS service providers. Its role is to authenticate NRID service requests, enforce policies (e.g., verifying the drone is authorized for flight in a certain area), and potentially trigger the establishment of the PDU session for NRID data. The service supports both periodic reporting and on-demand query modes, where authorized entities like air traffic control can request identification data for a specific drone.
NRID's role in the network is to leverage the ubiquitous coverage, reliability, and security of cellular networks to provide a scalable and standardized remote identification solution. It integrates UAS operations into the national airspace system by providing a digital identity and telemetry feed that is accessible to authorities and other airspace users. This network-based approach contrasts with direct RF broadcast methods, offering longer range, better security against spoofing, and the ability to integrate identification with other UAS communication services (like command and control) over the same network connection. It is a foundational enabler for advanced UAS operations like Beyond Visual Line of Sight (BVLOS) flights.
Purpose & Motivation
NRID was created to address the regulatory and safety requirements emerging from the rapid proliferation of commercial and recreational drones. Aviation authorities worldwide, such as the FAA and EASA, mandated remote identification for drones to ensure accountability, safety, and security in shared airspace. Prior to NRID, solutions were often proprietary, based on direct radio broadcast (like Wi-Fi or Bluetooth), which had limited range, were susceptible to interference and spoofing, and lacked integration with broader air traffic management systems.
The primary problem NRID solves is providing a standardized, secure, and reliable method for drones to broadcast their identity and location to authorities and other airspace users. The motivation for its development within 3GPP was to leverage existing and future cellular networks (4G, 5G) as a trusted, ubiquitous communication platform. This network-based approach solves the limitations of direct broadcast by offering extended coverage, leveraging network authentication and encryption for security, and enabling back-end integration with UAS Traffic Management (UTM) platforms. It allows for centralized monitoring and enforcement of flight rules.
Historically, the initial drone identification methods were fragmented. The creation of NRID in 3GPP Release 17 provided a globally standardized framework that aligns with aviation standards (like ASTM's Remote ID). This ensures interoperability between drone manufacturers, mobile network operators, and air traffic service providers. It addresses the limitation of previous non-network approaches by enabling identification even when the drone is far from the pilot or ground observer, which is critical for BVLOS operations that are essential for delivery, inspection, and other commercial applications.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-17, normative work from Rel-18.
In Release 18, architectural enhancements were introduced to support Broadcast Remote ID, and Multicast/Broadcast Service (MBS) support for Broadcast Remote ID was added. The release specifies that the radio link for Broadcast Remote ID utilizes technologies outside of 3GPP, while the network provides support for receiving these broadcasts via MBS announcements. Furthermore, the assignment and use of a CAA-level UAV Identity for Remote Identification functionality is defined, applying solely to the UAV and not its controller.
Explore further
Broader topics and technologies where NRID plays a role.
Defining Specifications
3GPP specifications that define or reference NRID, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.256 vj50 | UAS Support Architecture Enhancements | Rel-19 |
| TR 23.754 vh10 | Study on UAS Connectivity, ID & Tracking | Rel-17 |
| TS 29.256 vj30 | UAS-NF Stage 3 Protocol Specification | Rel-19 |