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.
Key Features
- Standardized broadcast of UAS ID and location/altitude
- Support for both mandatory and optional data elements (e.g., pilot location, velocity)
- Utilization of 3GPP sidelink technologies (LTE-V2X, NR sidelink) for direct device-to-device broadcast
- Integrated security mechanisms for message authentication and integrity protection
- Defined message structure and protocols across application, core network, and radio layers
- Complements network-based UAS identification and tracking services
Evolution Across Releases
Introduced the foundational BRID service architecture. Defined the core BRID message set, including UAS ID, location, timestamp, and remote pilot location. Specified the service requirements (22.843), stage 2 architecture (23.256), and detailed protocol details for non-access stratum (24.577, 24.578) and security (33.256). Integrated the broadcast mechanism into the LTE and NR RAN frameworks, specifying how BRID messages are transported over PC5 sidelink interfaces.
Enhanced BRID capabilities based on implementation experience and new regulatory needs. Introduced support for additional optional parameters in the BRID message to convey more detailed operational intent or status. Potential optimizations to the broadcast procedures for improved reliability and reduced interference in dense UAS environments. Further alignment with updated aviation regulations and UTM interfaces.
Continued evolution focusing on performance enhancements, coexistence with other sidelink services (e.g., V2X), and support for advanced UAS operational scenarios. May include refinements to the security framework, support for new spectrum bands for UAS communications, and tighter integration with network-assisted UAS traffic management (UTM) functions for dynamic airspace management.
Defining Specifications
| Specification | Title |
|---|---|
| TS 22.843 | 3GPP TS 22.843 |
| TS 23.256 | 3GPP TS 23.256 |
| TS 23.700 | 3GPP TS 23.700 |
| TS 23.754 | 3GPP TS 23.754 |
| TS 24.577 | 3GPP TS 24.577 |
| TS 24.578 | 3GPP TS 24.578 |
| TS 29.256 | 3GPP TS 29.256 |
| TS 33.256 | 3GPP TR 33.256 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.321 | 3GPP TR 38.321 |
| TS 38.331 | 3GPP TR 38.331 |