Description
The Broadcast Multicast Radio Bearer (Broadcast MRB) is a fundamental radio access network concept introduced in 3GPP Release 17 as part of the Multicast/Broadcast Services (MBS) framework for 5G NR. It defines a radio bearer specifically configured for the delivery of broadcast MBS traffic from the gNB to multiple UEs over the Uu interface. Unlike unicast data radio bearers that are dedicated to a single UE, a Broadcast MRB is a point-to-multipoint bearer that allows the same broadcast content to be transmitted once and received by all interested UEs within the coverage area, thereby significantly improving spectral efficiency for popular content distribution.
Architecturally, the Broadcast MRB operates between the gNB and the UE at the Access Stratum (AS) level. It is configured via RRC signaling using the MBS Broadcast Configuration, which is carried in SIB20 and SIB21 for broadcast and groupcast respectively, or through dedicated RRC signaling. The Broadcast MRB is associated with an MBS session that is delivered in broadcast mode, and it maps to a specific MBS QoS flow and MBS session. The gNB establishes the Broadcast MRB based on the MBS session context received from the core network (via the MB-SMF and MB-UPF) and configures the corresponding PDCP, RLC, and MAC entities to support the broadcast transmission. The PDCP layer handles header compression and ciphering (if applicable), the RLC layer operates in UM mode for broadcast, and the MAC layer uses the MBS Radio Network Temporary Identifier (M-RNTI) to schedule the broadcast transmissions on the Physical Downlink Shared Channel (PDSCH).
The Broadcast MRB supports both single-cell and multi-cell transmission modes. In single-cell mode, the broadcast transmission is confined to a single gNB coverage area, while in multi-cell mode, the same broadcast content is synchronized and transmitted across multiple gNBs using MBS Synchronization protocols (e.g., SYNC protocol over the M1 interface) to enable combining gains at the UE. The Broadcast MRB is identified by an MBS Radio Bearer Identity (MRB ID) which is unique within the MBS session scope. The UE acquires the Broadcast MRB configuration from the broadcast system information and can receive the broadcast service without prior registration or session establishment, making it suitable for public safety, emergency alerts, and popular media streaming.
Key technical aspects of the Broadcast MRB include the use of a common PDCP entity for all UEs receiving the broadcast service, which eliminates the need for per-UE PDCP contexts and reduces signaling overhead. The RLC layer uses unacknowledged mode (UM) since broadcast traffic does not support retransmissions at RLC. The MAC layer employs a common M-RNTI for scheduling the broadcast transmissions, allowing all UEs to monitor the same PDCCH candidates. The Broadcast MRB also supports flexible numerology and slot aggregation to accommodate different broadcast service requirements. Furthermore, the Broadcast MRB can be configured with different QoS profiles to support varying levels of reliability and latency for different broadcast applications.
In the overall 5G MBS architecture, the Broadcast MRB plays a critical role in enabling efficient delivery of broadcast services such as live sports, emergency alerts, software updates, and IoT firmware distribution. It complements the unicast bearers by providing a scalable solution for content that is intended for a large audience. The Broadcast MRB is managed by the gNB based on the MBS session context and can be dynamically activated or deactivated depending on the service demand. The 3GPP specifications 38.300, 38.323, and 38.331 define the overall NR and NG-RAN architecture, the PDCP protocol, and the RRC protocol aspects of the Broadcast MRB, respectively, ensuring interoperability and consistent implementation across vendors.
Purpose & Motivation
The Broadcast MRB was created to address the need for efficient point-to-multipoint delivery of broadcast content in 5G networks. Traditional unicast bearers require separate radio resources for each UE, which becomes highly inefficient when the same content needs to be delivered to many users simultaneously. The Broadcast MRB solves this by allowing a single transmission to be received by multiple UEs, thereby conserving spectrum and reducing network load. This is particularly important for applications like live media streaming, emergency alerts, and public safety communications where the same information is relevant to a large population.
Prior to Release 17, 5G NR did not have a native broadcast/multicast framework; broadcast services were primarily supported in LTE via eMBMS (Evolved Multimedia Broadcast Multicast Service). The 3GPP community recognized the need for a more flexible and efficient MBS solution in 5G that could leverage the advanced capabilities of NR, such as beamforming, flexible numerology, and massive MIMO. The Broadcast MRB was introduced as part of the MBS work item in Release 17 to provide a unified radio bearer design for broadcast and multicast services, enabling operators to deliver high-quality broadcast content over 5G networks without relying on LTE-based eMBMS.
The Broadcast MRB also addresses the limitations of application-layer broadcast solutions, which often result in redundant transmissions and inefficient use of radio resources. By defining a standardized radio bearer for broadcast delivery, the Broadcast MRB enables network operators to optimize resource allocation, improve spectral efficiency, and provide a better user experience for broadcast services. It also facilitates interoperability between different vendors and ensures consistent service delivery across multi-vendor networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define Broadcast MRB. Each summary describes the whole specification, not only this term.
Rel-19 adds multi-hop L2 UE-to-Network relay for NR sidelink as the largest item. It also adds low-power wake-up signal and receiver (LP-WUS/WUR) text, on-demand SSB and SIB1 for network energy savings, and sub-band full duplex for TDD carriers.
Full comparison in TS 38.300 →Rel-18 adds multi-path operation for remote UEs over sidelink or non-3GPP indirect paths, with related relay PDCP definitions. It also adds XR enhancements, including data volume calculation for delay status reporting and transmit/receive operations. Sidelink PDCP duplication is added, covering control PDU transmission and duplicate PDU discard.
Full comparison in TS 38.323 →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.
Defining Specifications
3GPP specifications that define or reference Broadcast MRB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 38.323 vj10 | PDCP Protocol Specification | Rel-19 read |
| TS 38.331 vj40 | NR Radio Resource Control (RRC) | Rel-19 read |