Description
The Single Cell Multicast Radio Bearer (SC-MRB) is a core concept in the LTE user plane for multicast services. It represents a unidirectional point-to-multipoint radio bearer established between the eNodeB and a group of User Equipment (UEs) within a single cell to deliver multicast or broadcast content. An SC-MRB is associated with a specific SC-PTM service, such as a public safety message stream or a mobile TV channel. It is the logical pipe through which the actual service data flows, contrasting with the control information carried on the SC-MCCH. At the Packet Data Convergence Protocol (PDCP) layer, data for an SC-MRB is processed and assigned a specific Group-RNTI (G-RNTI) which identifies the bearer and the service to all receiving UEs.
Architecturally, an SC-MRB utilizes a shared channel structure for efficiency. It is mapped to a specific Single Cell Multicast Traffic Channel (SC-MTCH) at the logical channel level. The SC-MTCH is then mapped to the Downlink Shared Channel (DL-SCH) transport channel, which is ultimately transmitted on the Physical Downlink Shared Channel (PDSCH). This shared channel mapping is fundamental; instead of dedicating separate resources to each UE, the eNodeB transmits the data once, and all UEs interested in that service monitor the same time-frequency resources using the common G-RNTI to identify the packets intended for them. The Radio Link Control (RLC) layer for an SC-MRB operates in Unacknowledged Mode (UM), as there is no mechanism for hybrid ARQ feedback from the multitude of receivers, which aligns with the broadcast nature of the service.
The operation involves coordination between control and user planes. The eNodeB first configures the SC-MRB and its associated parameters (like the G-RNTI). It then advertises this configuration, including the G-RNTI and scheduling details, on the SC-MCCH control channel. A UE wishing to receive the service reads the SC-MCCH, learns the G-RNTI and how the SC-MRB is scheduled, and then configures its physical layer to monitor the PDSCH for that G-RNTI. When the eNodeB schedules data for that SC-MRB, it transmits it on the PDSCH with the corresponding G-RNTI in the downlink control information (DCI). All UEs monitoring for that G-RNTI will receive the data, pass it up through their RLC and PDCP layers associated with that SC-MRB, and deliver it to the upper-layer application. This mechanism allows a single transmission to serve an unlimited number of UEs within the cell's coverage, providing optimal spectral efficiency for group communication.
Purpose & Motivation
The SC-MRB was created to provide a standardized, efficient mechanism for user plane data delivery in Single Cell Point-to-Multipoint (SC-PTM) services. Before SC-PTM, delivering the same content to multiple users in an LTE cell typically required establishing individual unicast bearers (DRBs) for each user, duplicating the data stream for each connection. This approach is highly inefficient in terms of radio resource usage, especially as the number of recipients grows, and it creates significant load on the network.
The SC-MRB solves this resource inefficiency problem for localized group communications. It enables true multicast at the radio level: a single transmission of data packets that can be received by an entire group. This is critical for use cases where timely, simultaneous delivery to many devices is required, such as dispatching instructions to a fleet of vehicles, broadcasting emergency alerts to all phones in an area, or streaming live video to spectators in a stadium. The purpose is to leverage the broadcast nature of the radio medium for optimal spectral efficiency.
Motivated by the need for lightweight multicast solutions complementary to the more complex eMBMS/MBSFN, SC-PTM and its SC-MRB were designed for dynamic, cell-specific services. The SC-MRB provides the essential user plane bearer model that integrates with LTE's shared channel architecture. It allows operators to offer multicast services without the overhead of managing a synchronized multi-cell MBSFN area, making multicast economically viable for a wider range of applications, including emerging IoT and V2X scenarios where group messaging is a fundamental requirement.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (14 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-15.
In Release 15, the SC-MRB (Single Cell Multicast Radio Bearer) function was enhanced by introducing a short value for the sc-mcch repetition period and sc-mcch modification period, which were taken out of the 'br-BCCH-Config-r14' configuration. This change provides more flexible configuration options for the Single Cell Multicast Control Channel to improve efficiency.
- Introduction of increased number of E-UTRAN data bearers TS 36.331CR3446
- Correction to FDD/TDD Diff for NR PDCP Capabilities TS 36.331CR3674
- Introducing PDCP suspend procedure TS 36.331CR3794
- Supporting bearer type change with LCID change TS 36.331CR3892
- Correction for the establishment of LTE RLC bearers for (NG)EN-DC and NE-DC TS 36.331CR4185
- Introduce the short value of sc-mcch repetition period and sc-mcch modification period out of 'br-BCCH-Config-r14'. TS 36.331CR3468
+ 1 more changes
In Release 16, the SC-MRB function was enhanced to allow a PDCP version change without requiring a handover and to remove an incorrect restriction that previously applied to RLC Unacknowledged Mode radio bearers. These changes, along with clarifications on PDCP queuing delay measurement and security procedures during termination point changes, improved the flexibility and robustness of the multicast bearer management.
- Allowing PDCP version change without handover TS 36.331CR4262
- Incorrect restriction for RLC UM radio bearers TS 36.331CR4385
- Note to clarify UE handling of non-DAPS bearer TS 36.331CR4604
- On PDCP queuing delay value measurement TS 36.331CR4711
- Avoiding security risk for RLC AM and RLC UM bearers during termination point change TS 36.331CR4293
In Release 17, the SC-MRB function was enhanced by introducing support for User Plane IP for EPC-connected architectures using NR PDCP. This was complemented by the introduction of a single-bit approach for MINT (Multicast/Broadcast Service Interest Indication).
Explore further
Broader topics and technologies where SC-MRB plays a role.
Defining Specifications
3GPP specifications that define or reference SC-MRB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |