Glossary term · Services

BRID

Broadcast Remote Identification

Services →

BRID is a 3GPP service enabling drones (UAS) to broadcast their identification and location for safety, regulatory compliance, and remote identification by authorized entities.

Introduced
Rel-17
Where
Services › IMS
Specifications
13 specs
Also in
Radio Access Network
Category
Services
Introduced
Rel-17
Where
Services › IMS
Also touches
1 segments
Specifications
13 specs
BRID Description Purpose Related Classification Detected Changes Specifications

Description

Broadcast Remote Identification (BRID) is a standardized service within 3GPP networks designed to provide real-time identification and tracking of Uncrewed Aerial Systems (UAS), commonly known as drones. The service operates by having the UAS broadcast a set of identification and location parameters, which can be received by authorized observers, network entities, or other UAS within proximity. This broadcast mechanism is distinct from network-based identification, as it does not rely on an active connection to the cellular network for the information to be received by nearby parties, though it may utilize the network for other UAS services.

Architecturally, BRID leverages existing 3GPP user equipment (UE) capabilities, with the UAS itself acting as a UE. The key functional components involve the UAS, which generates and broadcasts the BRID message, and the observer, which receives and processes it. The UAS application layer formats the BRID message containing mandatory and optional elements. This message is then passed down through the protocol stack for broadcast. The specific radio technology used for the broadcast (e.g., LTE sidelink, NR sidelink, or other direct communication methods) is defined in the relevant Radio Access Network (RAN) specifications (e.g., 36.331, 38.331). The broadcast is typically performed on designated frequencies or resources to avoid interference with other cellular communications.

The BRID message itself is a structured data set defined in core network specifications (e.g., 24.577, 24.578). Mandatory information includes the UAS ID (which could be a serial number or a session ID), the location/altitude of the UAS, and a timestamp. Optional information can include the location of the UAS operator (Remote Pilot), the UAS's velocity, emergency status, and route information. Security is a paramount concern, addressed in specifications like 33.256, which define mechanisms to ensure the authenticity and integrity of the broadcast messages to prevent spoofing.

BRID's role in the network is as an enabler for UAS Traffic Management (UTM) and regulatory compliance. It provides a foundational layer for 'electronic identification plates' for drones. While it operates via a broadcast mechanism, it is integrated into the broader 3GPP UAS framework defined in specifications like 23.256 and 23.754. This framework includes network-based identification, command and control (C2) communications, and UAS service authorization. BRID specifically addresses the line-of-sight and immediate vicinity identification requirement mandated by aviation authorities worldwide, complementing network-based tracking which is used for beyond visual line of sight (BVLOS) operations and fleet management by service providers.

Purpose & Motivation

BRID was created to address a critical regulatory and safety gap in the rapidly expanding domain of commercial and recreational drone operations. Aviation authorities, such as the FAA in the United States and EASA in Europe, mandated that drones must be remotely identifiable in flight to ensure accountability, enhance security, and enable the safe integration of UAS into national airspace. Prior to 3GPP standardization, proprietary or non-cellular solutions existed, but they lacked global interoperability, scalability, and integration with mobile network operators' infrastructure.

The primary problem BRID solves is providing a standardized, secure, and reliable method for drones to announce their identity and basic telemetry to anyone in the vicinity with a suitable receiver. This enables law enforcement, security personnel, other airspace users, and concerned citizens to identify a drone and its operator without needing to establish a network connection with it. It addresses limitations of previous approaches which were often siloed, used non-standard protocols, or lacked robust security features, making them vulnerable to spoofing or jamming.

Historically, the motivation for its creation in 3GPP Release 17 stemmed from strong industry and regulatory demand to leverage ubiquitous cellular technology for UAS services. Cellular networks offer wide coverage, high reliability, built-in security, and management capabilities. By defining BRID within the 3GPP ecosystem, it ensures that drones can use the same device hardware and spectrum (where applicable) for identification as they do for command and control and payload communications, simplifying device design and certification. It positions cellular networks as a key enabler for the digital infrastructure required for large-scale UAS operations.

Classification

Part ofUTM
Related approachesV2X

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-18 2 changes
  • Generalisation of BRID TS 24.578CR0004
  • Correction for SL resource pool usage for BRID/DAA transmission TS 38.321CR1743

Explore further

Broader topics and technologies where BRID plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 22.843 vj20 Study on Uncrewed Aerial Vehicle (UAV) Phase 3 Rel-19
TS 23.256 vj50 UAS Support Architecture Enhancements Rel-19
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20
TR 23.754 vh10 Study on UAS Connectivity, ID & Tracking Rel-17
TS 24.577 vj30 A2X Services in 5G System Rel-19
TS 24.578 vj00 UE policies for A2X services in 5GS Rel-19
TS 29.256 vk00 UAS-NF Nnef Service Based Interface Stage 3 Rel-20
TS 33.256 vj20 Security for Uncrewed Aerial Systems (UAS) Rel-19
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19
TS 36.331 vj30 E-UTRA RRC Protocol Specification Rel-19
TS 38.300 vj30 NR and NG-RAN Overall Description Rel-19
TS 38.321 vj30 NR MAC Protocol Specification Rel-19
TS 38.331 vj30 NR Radio Resource Control Protocol Specification Rel-19