Description
The MBS Radio Bearer (MRB) is a fundamental architectural element introduced in 3GPP Release 17 for 5G New Radio (NR) to support Multicast/Broadcast Service (MBS). It represents a radio bearer that is specifically configured for the delivery of MBS data, which can be either multicast (intended for a specific group of UEs) or broadcast (intended for all UEs in a given area). The MRB operates at the Access Stratum (AS) level and is responsible for the transport of MBS user plane data between the gNB and the UE. It is defined in 3GPP TS 38.323 (PDCP specification) and TS 38.331 (RRC protocol specification), highlighting its role in both the packet data convergence protocol layer and radio resource control configuration.
Architecturally, the MBS Radio Bearer is established as part of an MBS session. When a UE joins an MBS session, the network configures one or more MRBs for that UE. These bearers can be configured in two modes: Point-to-Multipoint (PTM) and Point-to-Point (PTP). In PTM mode, a single MRB is used to deliver data to multiple UEs simultaneously, leveraging the broadcast nature of the radio interface for spectral efficiency. In PTP mode, a separate MRB is established for each UE, providing dedicated resources and potentially higher reliability. The network can dynamically switch between PTM and PTP modes based on factors such as UE distribution, channel conditions, and service requirements. This flexibility is a key feature of MBS in 5G, allowing operators to optimize resource usage while meeting diverse service demands.
The MRB is associated with a specific MBS session and is identified by an MBS Radio Bearer identity. At the PDCP layer, the MRB uses a common PDCP entity for PTM transmission, which handles ciphering, integrity protection (if applicable), and header compression for the MBS data. For PTP, a dedicated PDCP entity may be used. The RRC layer is responsible for configuring the MRB, including parameters such as the PDCP configuration, RLC configuration, and logical channel prioritization. The configuration is signaled to the UE via RRC messages, either through dedicated signaling or broadcast signaling (e.g., SIB). The UE must be aware of the MRB configuration to properly receive and process the MBS data.
In terms of protocol stack, the MRB spans multiple layers. At the top, the MBS data is encapsulated in PDCP PDUs, which are then passed to the RLC layer. The RLC layer can operate in Unacknowledged Mode (UM) for PTM transmission, as retransmissions are not feasible for multiple receivers, or in Acknowledged Mode (AM) for PTP transmission to ensure reliability. Below RLC, the MAC layer multiplexes the MRB data with other logical channels onto transport channels. For PTM, the MAC layer uses a specific MBS Radio Network Temporary Identifier (M-RNTI) to schedule the MBS data on the Physical Downlink Shared Channel (PDSCH). The physical layer then transmits the data using multicast/broadcast techniques, potentially with single-frequency network (SFN) operation to improve coverage and spectral efficiency.
The MBS Radio Bearer is a critical enabler for new services such as live streaming, group communications, and software updates. It allows the network to deliver the same content to many users efficiently, reducing the load on the core network and radio access network compared to unicast delivery. The design of the MRB in 5G NR builds upon the experience from LTE's eMBMS (Evolved Multimedia Broadcast Multicast Service) but introduces enhancements such as support for both multicast and broadcast, flexible PTM/PTP switching, and integration with the 5G core network architecture. As MBS continues to evolve in Releases 18 and 19, the MRB will likely see further optimizations for latency, reliability, and capacity.
Purpose & Motivation
The MBS Radio Bearer exists to provide an efficient means of delivering multicast and broadcast services over the 5G NR air interface. Traditional unicast delivery requires separate radio bearers for each user, which is spectrally inefficient when many users are interested in the same content. The MRB solves this by enabling point-to-multipoint transmission, where a single radio bearer can serve multiple UEs simultaneously. This is particularly important for services like live video streaming, emergency alerts, and group communications, where the same data needs to be delivered to a large audience.
Before the introduction of MBS in 5G, LTE had eMBMS, which provided broadcast/multicast services using MBSFN (Multicast-Broadcast Single-Frequency Network) operation. However, eMBMS had limitations: it was primarily designed for broadcast, did not support flexible switching between PTM and PTP, and had limited integration with the core network. The MBS Radio Bearer in 5G addresses these limitations by supporting both multicast and broadcast, allowing dynamic mode switching, and being tightly integrated with the 5G Service-Based Architecture (SBA). It also benefits from the higher bandwidth and lower latency of 5G NR, making it suitable for more demanding applications.
The MRB was motivated by the need for a unified mechanism to deliver group-oriented services in 5G. It provides a standardized way for the network to configure and manage radio resources for MBS, ensuring interoperability between different vendors and enabling global roaming. By defining the MRB in specifications like TS 38.323 and TS 38.331, 3GPP ensures that UEs and network equipment can support MBS consistently. The MRB also facilitates efficient use of network resources, as the network can choose the most appropriate transmission mode based on the number and location of interested UEs, thereby optimizing capacity and coverage.
What changed in its specifications
The latest release-to-release comparison of specifications that define MBS Radio Bearer. Each summary describes the whole specification, not only this term.
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 →Rel-19 adds LTM cell-switch and MIMO Phase 5 identifiers to TS 38.331, plus multi-hop sidelink U2N relay clauses and IEs. It also adds OD-SIB1 and adaptive SSB for RRM, SIB27 for NTN, and SBFD identifiers.
Full comparison in TS 38.331 →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 MBS Radio Bearer, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.323 vj10 | PDCP Protocol Specification | Rel-19 read |
| TS 38.331 vj40 | NR Radio Resource Control (RRC) | Rel-19 read |