Description
The MBMS bearer is a fundamental concept in the 3GPP Multimedia Broadcast Multicast Service (MBMS) architecture, defined as the service provided by the Evolved Packet System (EPS) to deliver the same IP datagrams to multiple receivers in a designated location. It represents the network's capability to transport multicast or broadcast content over a shared radio and core network path, rather than establishing individual unicast connections for each user. This bearer is established between the Broadcast Multicast Service Center (BM-SC) and the User Equipment (UE), traversing the core network (via MBMS Gateways) and the radio access network (via eNodeBs or gNodeBs). The MBMS bearer is characterized by a set of QoS parameters, such as Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR), which ensure that the multicast stream meets the required quality for all receivers in the service area.
Architecturally, the MBMS bearer is realized through a combination of network elements and interfaces. The BM-SC acts as the entry point for content providers, managing service announcements, security, and session control. The MBMS Gateway (MBMS-GW) serves as the mobility anchor and distributes the multicast data to the relevant eNodeBs via the M1 interface. The eNodeBs then transmit the data over the air interface using either Multicast-Broadcast Single Frequency Network (MBSFN) or Single-Cell Point-to-Multipoint (SC-PTM) techniques. The MBMS bearer is identified by a Temporary Mobile Group Identity (TMGI) and a Flow Identifier (FID), which allow the UE to join the correct multicast session. The bearer is established and released through session start and stop procedures, which are triggered by the BM-SC and propagated through the core network.
The operation of an MBMS bearer involves several key procedures. First, the BM-SC initiates a session start request, which is sent to the MBMS-GW. The MBMS-GW then allocates resources and sends a session start request to the relevant eNodeBs. The eNodeBs configure the radio resources and begin transmitting the multicast data. UEs interested in the service join the multicast group by acquiring the TMGI and FID from the service announcement. The UE then monitors the Multicast Control Channel (MCCH) for session information and receives the data on the Multicast Traffic Channel (MTCH). The bearer can be modified during its lifetime to adapt to changing network conditions or service requirements, and it is released when the session ends.
The MBMS bearer provides significant benefits for delivering popular content to many users simultaneously. By sharing network resources, it reduces the load on the core network and radio access network, and it enables efficient use of spectrum. It also allows for the delivery of high-quality multimedia content, such as live TV, video streaming, and file downloads, to a large audience without overwhelming the network. The MBMS bearer is a key enabler for services like Public Warning Systems (PWS), where alert messages must be delivered to all users in a specific area, and for group communication in mission-critical applications.
In summary, the MBMS bearer is a point-to-multipoint transport service within the EPS that delivers identical IP datagrams to multiple receivers in a designated area. It is defined in 3GPP specifications such as 24.380, 24.581, and 29.468, and it has evolved across releases to support new features and capabilities. Its efficient use of network resources makes it ideal for broadcast and multicast services, and it continues to be a vital component of 3GPP networks.
Purpose & Motivation
The MBMS bearer was created to address the inefficiency of delivering the same content to multiple users via individual unicast connections. In traditional unicast, each user consumes dedicated network resources, which can lead to congestion and high costs when many users request the same popular content, such as a live sports event or a software update. The MBMS bearer solves this problem by allowing the network to deliver a single stream of data to multiple receivers simultaneously, using shared resources. This not only conserves bandwidth but also reduces the processing load on the core network and radio access network.
Historically, the need for efficient multicast and broadcast in mobile networks became apparent with the rise of mobile TV and multimedia services. Early attempts, such as the Multimedia Broadcast Multicast Service (MBMS) in 3GPP Release 6, introduced the concept of multicast bearers. However, these were limited to UMTS networks. With the advent of LTE, the MBMS bearer was redefined for the EPS in Release 12, leveraging the flat architecture and higher data rates of LTE. The MBMS bearer in EPS supports both broadcast and multicast modes, and it can be used for a variety of applications, including mobile TV, live streaming, and public safety communications.
The MBMS bearer also addresses the need for efficient group communication in mission-critical scenarios. In public safety networks, for example, first responders need to receive the same information simultaneously, and the MBMS bearer ensures that this is done reliably and efficiently. Furthermore, the MBMS bearer supports the delivery of emergency alerts to all users in a specific area, which is essential for public warning systems. By providing a standardized mechanism for point-to-multipoint delivery, the MBMS bearer enables operators to offer new services and generate additional revenue, while ensuring that network resources are used optimally.
What changed in its specifications
The latest release-to-release comparison of specifications that define MBMS bearer. Each summary describes the whole specification, not only this term.
Rel-18 adds media plane multiplexing via mc_floor_ssrc fmtp and Audio SSRC in floor control. It adds an MBS subchannel control protocol. It also adds invited user identity, group call setup, and floor control SSRC/SDP fields.
Full comparison in TS 24.380 →Rel-18 added SSRC-related fields, fmtp attributes, and procedures for MCVideo transmission control and multiplexing. It also introduced the MBS subchannel control protocol with messages, fields, timers, counters, and term mappings.
Full comparison in TS 24.581 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (7 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- MBMS bearer announcement over an MBMS bearer TS 24.380CR0197
- MBMS bearer announcement over an MBMS bearer TS 24.581CR0037
- Clarification for MBMS bearer activation procedure TS 29.468CR0043
- Correction for Radio-Frequency AVP in MBMS Bearer-Response AVP TS 29.468CR0036
- MBMS bearer activation correction TS 29.468CR0054
- Correction for MBMS Bearer Event-Notification AVP TS 29.468CR0039
+ 1 more changes
Defining Specifications
3GPP specifications that define or reference MBMS bearer, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.380 vk10 | MCPTT Media Plane Control Protocols | Rel-20 read |
| TS 24.581 vj30 | MCVideo Media Plane Control | Rel-19 read |
| TS 29.468 vj00 | MB2 Reference Point Protocol Definition | Rel-19 read |