MRB

MBMS Point to Multipoint Radio Bearer

Radio Access Network →
Introduced in Rel-8 Also in: Core Network, Services, User Equipment

MRB is the point-to-multipoint radio bearer used in LTE and 5G NR to efficiently deliver MBMS content, such as mobile TV, from a single network point to multiple user devices simultaneously.

Category
Radio Access Network
Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Also touches
3 segments
Specifications
16 specs
MRB Description Purpose Related Classification Detected Changes Specifications

Description

The MBMS Point to Multipoint Radio Bearer (MRB) is a fundamental transport mechanism within the 3GPP Radio Access Network (RAN) architecture, specifically designed for broadcast and multicast traffic. It operates as a unidirectional bearer established between the network's radio access nodes, such as the eNodeB in LTE or gNB in 5G NR, and a group of User Equipments (UEs) within a specific Multicast/Broadcast Service Area (MBSA). Unlike unicast bearers which establish individual logical connections for each UE, the MRB utilizes a single shared radio resource to transmit identical data streams to all subscribed UEs in its coverage area. This shared nature is the core of its efficiency, preventing the network from being overwhelmed by redundant data transmissions when many users request the same content simultaneously.

From an architectural perspective, the MRB is established and managed by the RAN in coordination with the core network's MBMS Gateway (MBMS-GW) and Broadcast Multicast Service Center (BM-SC). The bearer is characterized by specific radio configurations, including modulation and coding schemes, which are optimized for reliable reception at the cell edge where signal conditions may be poorer. The MRB supports both MBSFN (Multicast-Broadcast Single Frequency Network) and SC-PTM (Single Cell Point to Multipoint) transmission modes. MBSFN mode synchronizes transmissions from multiple cells to appear as a single transmission, improving spectral efficiency and reception quality through macro-diversity. SC-PTM mode is used for multicast delivery within a single cell, offering more flexibility for localized services.

At the protocol layer, the MRB is realized through specific configurations in the PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), and MAC (Medium Access Control) layers. Data for the MRB is scheduled using specific logical channels like the MTCH (Multicast Traffic Channel) and control information is provided via the MCCH (Multicast Control Channel). The UE's RRC (Radio Resource Control) layer manages subscription to these channels. The MRB's performance is tightly coupled with QoS parameters defined for the MBMS service, ensuring the broadcast stream meets required reliability and latency targets. Its role is critical in enabling scalable, network-efficient delivery of popular live media and critical information broadcasts.

Purpose & Motivation

The MRB was created to address the fundamental inefficiency of using unicast connections for delivering popular, real-time content to a mass audience. Prior to its introduction, if thousands of users in an area wanted to watch the same live sports event or news broadcast, the network would have to establish and maintain thousands of individual data pipes, each consuming dedicated radio resources. This approach does not scale and would quickly congest the radio interface, degrading service for all users. The MRB solves this by treating the content as a public good over the air interface, transmitting it once for all to receive, thereby conserving precious and limited radio spectrum and network capacity.

The development of MRB was driven by the commercial desire to offer mobile TV and multimedia broadcasting services, as well as regulatory requirements for efficient public warning systems. It enables business models for broadcast services that would be economically unviable using pure unicast. Technically, it allows operators to leverage their LTE and later 5G NR infrastructure for broadcast purposes, creating a converged network rather than needing separate broadcast networks like DVB-H. The MRB, as part of the broader MBMS/eMBMS (Evolved MBMS) framework, represents a core 3GPP innovation for point-to-multipoint communication, balancing the flexibility of IP-based delivery with the spectral efficiency of traditional broadcasting.

Classification

Part ofMBMS
Related approachesSC-PTM

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 3 changes

In Release 17, enhancements for the MRB function included the initialization of the Packet Data Convergence Protocol (PDCP) for MRB, corrections to the F1-U tunnel establishment procedures for multicast MRBs, and the introduction of a further multicast session flow mechanism for MRB type reconfiguration. These updates refined the bearer management and session control for point-to-multipoint services.

  • PDCP Initialisation of MRB TS 38.323CR0112
  • Correction on F1-U tunnels for multicast MRB TS 38.401CR0258
  • Introduction of further multicast session flow on MRB type reconfiguration TS 38.401CR0266
Rel-18 1 change

In Release 18, a specific correction was made to the Packet Data Convergence Protocol (PDCP) configuration used for multicast MRB (MBMS Point to Multipoint Radio Bearer) operation. This update ensured the proper configuration of PDCP, which is crucial for the reliable delivery of multicast and broadcast services over the radio interface. The change refined the bearer setup procedures to align with the overall MRB function for efficient multimedia resource brokerage and delivery.

  • Correction to PDCP configuration for multicast MRB TS 38.331CR4651

Explore further

Broader topics and technologies where MRB plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.218 vj00 IMS Call Model Specification Rel-19
TS 23.228 vj50 IMS Stage-2 Service Description Rel-19
TS 23.849 vb00 Study on IMS Roaming Media Optimization Rel-11
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TS 24.802 vc10 IMS II-NNI Traversal Scenario Determination Study Rel-12
TS 29.165 vj10 Inter-IMS Network to Network Interface (NNI) Rel-19
TS 32.281 vj00 Announcement Service for Online Charging Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.304 vj00 UE RRC_IDLE and RRC_INACTIVE Procedures Rel-19
TS 38.306 vj00 NR UE Radio Access Capability Parameters Rel-19
TS 38.323 vj00 Packet Data Convergence Protocol (PDCP) Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.401 vj10 NG-RAN Architecture Specification Rel-19
TS 38.425 vj10 NR User Plane Protocol Specification Rel-19
TS 38.523 vj20 5G NR UE Conformance Testing: Idle/Inactive Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.