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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (37 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the newly introduced BRID (Broadcast Remote Identification) function provided the capability for unambiguous identification of UAVs to support reliable tracking. This was achieved by enabling a UAV to broadcast its identification information, which a ground station in the 5G network could then receive and use to inform a UTM (Unmanned Traffic Management) system. The function specifically supported the tracking of UAVs that have a subscription with the 5G operator.
In Release 16, the new BRID (Broadcast Remote Identification) function introduced the capability for a 5G network to broadcast specific assistance data, including barometric pressure and TBS (Trajectory Based Services) information, to support unambiguous identification and tracking of UAVs. This allowed a subscribed UAV to broadcast its BRID information, enabling a ground station in the network to inform a UTM (Unmanned Traffic Management) system that the UAV was following its planned route. These enhancements provided foundational support for reliable remote identification and tracking within the operator's network coverage.
- Introduction of LTE-based 5G terrestrial broadcast TS 36.331CR4190
- CR TS 38.300 Remote Interference Management TS 38.300CR0184
- Addition of broadcast of barometric pressure assistance data TS 36.331CR4026
- Broadcast of TBS assistance data TS 36.331CR4134
- Correction on posSIB broadcastStatus TS 38.331CR2199
In Release 17, the BRID function introduced UE capabilities and network configurations for new bands and bandwidth allocations to support LTE-based 5G terrestrial broadcast. The release also provided clarifications and corrections for key procedures, including power control parameters (dl-P0-PSBCH, dl-P0-PSSCH-PSCCH, dl-P0-PSFCH) for out-of-coverage remote UEs and the reception of system information. These enhancements aimed to improve the reliability of broadcast remote identification and tracking for subscribed UAVs within the 5G network.
- Introduction of new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast TS 36.300CR1360
- Introduction of new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast TS 36.331CR4750
- UE capabilities for new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast TS 36.331CR4780
- Correction in Remote UE synchronization TS 38.331CR3854
- Clarification on dl-P0-PSBCH, dl-P0-PSSCH-PSCCH and dl-P0-PSFCH for OoC Remote UE TS 38.331CR3874
- Corrections on MBS Broadcast Configuration TS 38.331CR3946
+ 1 more changes
In Release 18, the BRID function was enhanced to support the tracking of UAVs with a 5G network subscription, while tracking for non-subscribed UAVs was not covered. The release introduced architectural enhancements and specific support for MBS (Multicast/Broadcast Services) to deliver BRID information. Furthermore, it generalized the BRID function and provided corrections and clarifications for its broadcast reception, including for RedCap and eRedCap UEs.
- Architectural enhancements for support of Broadcast Remote ID TS 23.256CR0077
- MBS support for Broadcast Remote ID TS 23.256CR0089
- GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] TS 36.331CR4931
- Introduction of RedCap UE MBS Broadcast reception [RedcapMBS] TS 38.300CR0753
- GNSS LOS/NLOS posSIB broadcast assistance information [GNSS LOS/NLOS] TS 38.331CR4109
- RedCap CFR for MBS broadcast [RedCapMBS_Bcast] TS 38.331CR4123
+ 8 more changes
In Release 19, the BRID (Broadcast Remote Identification) function was enhanced to support the unambiguous identification and tracking of UAVs that do not have a subscription with the 5G operator, a capability not covered in Release 18. This allows the 5G network's ground station to inform the UTM that a UAV is following its planned route by receiving BRID information from the target UAV. The release also introduced technical features such as LTE-based 5G Broadcast Phase 2 and CAS muting to support these broadcast-related functionalities.
- Introduction of LTE-based 5G Broadcast Phase 2 TS 36.300CR1428
- Introduction of CAS muting in LTE-based 5G broadcast [5GB_CASMuting] TS 36.331CR5139
- Introduction of LTE-based 5G Broadcast Phase 2 TS 36.331CR5143
- Rapporteur correction on CAS muting for LTE based 5G broadcast [5GB_CASMuting] TS 36.331CR5162
- Corrections to LTE-based 5G Broadcast Phase 2 after ASN.1 review TS 36.331CR5168
- U2U Relays, Peer Remote UE Control Plane Procedures TS 38.300CR1048
+ 1 more changes
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.
| Specification | Title | Release |
|---|---|---|
| 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 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TR 23.754 vh10 | Study on UAS Connectivity, ID & Tracking | Rel-17 |
| TS 24.577 vj10 | A2X Services in 5GS | Rel-19 |
| TS 24.578 vj00 | UE policies for A2X services in 5GS | Rel-19 |
| TS 29.256 vj30 | UAS-NF Stage 3 Protocol Specification | Rel-19 |
| TS 33.256 vj10 | Security for Uncrewed Aerial Systems (UAS) | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.321 vj00 | NR MAC Protocol Specification | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |