Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

MBMS Bearer Service

Multimedia Broadcast Multicast Service Bearer Service

Services →

MBMS Bearer Service is a network service that delivers a single multicast data stream to one or more users with a specific QoS profile, serving as a fundamental building block for MBMS.

Introduced
Rel-6
Where
Radio Access Network › UTRAN (3G)
Specifications
3 specs
MBMS Bearer Service Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The MBMS Bearer Service is a core concept in the 3GPP Multimedia Broadcast Multicast Service (MBMS) architecture, defined as the network service used to deliver a single multicast data stream to one or more users. It is a point-to-multipoint bearer service that provides a unidirectional data path from a source to multiple destinations, with an associated Quality of Service (QoS) profile. Each MBMS Bearer Service is identified by a Temporary Mobile Group Identity (TMGI) and a Flow Identifier (FID), and it is established across the core network and radio access network to transport multicast content. The MBMS Bearer Service is a fundamental enabler for MBMS user services, which may require one or more bearer services to deliver their content.

Architecturally, the MBMS Bearer Service is realized through a set of network elements and interfaces. The Broadcast Multicast Service Center (BM-SC) is the source of the multicast data and manages the service. The MBMS Gateway (MBMS-GW) acts as the entry point to the core network and distributes the data to the relevant eNodeBs (or gNodeBs in 5G) 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 Service is established through session start procedures, which are initiated by the BM-SC and propagated through the core network. The bearer service can be modified during its lifetime to adapt to changing conditions, and it is released when the session ends.

The operation of an MBMS Bearer Service involves several key procedures. First, the BM-SC initiates a session start request, which is sent to the MBMS-GW. The MBMS-GW 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 service 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 Service 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 Service 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 Service is a point-to-multipoint transport service within the 3GPP network that delivers a single multicast data stream to multiple receivers with an associated QoS profile. It is defined in specifications such as 23.846, 25.413, and 25.423, 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 Service was created to provide a standardized mechanism for delivering multicast data streams efficiently to multiple users in mobile networks. Before its introduction, delivering the same content to many users required individual unicast connections, which consumed significant network resources and could lead to congestion. The MBMS Bearer Service solves this problem by allowing the network to establish a single bearer that can be shared by many users, thereby conserving bandwidth and reducing the processing load on the core network and radio access network.

Historically, the need for efficient multicast in mobile networks became apparent with the rise of mobile TV and multimedia services. The MBMS Bearer Service was first introduced in 3GPP Release 6 for UMTS networks, providing a way to deliver multicast content over the air interface. With the evolution to LTE, the concept was adapted and enhanced in later releases, such as Release 8 and beyond, to support higher data rates and new features. The MBMS Bearer Service is a key enabler for services like mobile TV, live streaming, and public safety communications, where the same information needs to be delivered to many users simultaneously.

The MBMS Bearer Service 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 Service ensures that this is done reliably and efficiently. Furthermore, the MBMS Bearer Service 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 Service 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 Service. Each summary describes the whole specification, not only this term.

TS 25.413Rel-11 → Rel-12

Release 12 adds LIPA and SIPTO procedural handling with new IEs, an MBMS Session Re-establishment Indicator IE, and BDS support including GANSS ID coding value 101.

Full comparison in TS 25.413 →
TS 25.423Rel-10 → Rel-11

Four Branch MIMO for HSDPA, uplink transmit diversity for HSPA, CELL_FACH enhancements, HSUPA MIMO with 64QAM, multiflow data transmission, and SON enhancements.

Full comparison in TS 25.423 →

Technology family

Broadcast and multicast · Services

  1. Phase 1 CBC, CBCH, CBS, SMS-CB
  2. Phase 2 CBE
  3. R99 BMC, SABP
  4. Rel-6 ALC, BM-SC, FDT, FLUTE, LCT, MBMS, MBMS Bearer Service, MBMS download delivery method, MBMS streaming delivery method, MBMS User Service, TMGI
  5. Rel-7 MBSFN
  6. Rel-8 ETWS, MCE, PWS
  7. Rel-9 CBSP, CMAS, eMBMS, MBMS-GW
  8. Rel-10 KPAS
  9. Rel-11 EU-Alert
  10. Rel-12 MooD
  11. Rel-13 MBMS group communication delivery method, SC-PTM
  12. Rel-14 MBMS transparent delivery method, Receive Only Mode
  13. Rel-15 CBCF, PWS-IWF
  14. Rel-16 5G Broadcast
  15. Rel-17 5MBS, Broadcast MBS session, MB-SMF, MB-UPF, MBS, MBS Distribution Session, MBS User Service, MBSF, MBSSF, MBSTF, Multicast MBS session, Object Distribution Method, Packet Distribution Method
  • MBMS Bearer Service used together with TMGI
    “The TMGI is a radio resource efficient MBMS bearer service identification, which is equivalent to the MBMS bearer service identification consisting of IP multicast address and APN.” TS 23.246

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 3 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-6 introduced

MBMS Bearer Service is first specified in RANAP and RNSAP in Rel-6, with session start, MBMS Bearer Service Type, linking and active service list handling.

  • “The purpose of the MBMS Session Start procedure is to request the UTRAN to notify UEs about an upcoming MBMS Session of a given MBMS Bearer Service” TS 25.413 v6.16.0
  • “The TMGI IE contains the TMGI identifier which uniquely identifies the MBMS Bearer Service.” TS 25.413 v6.16.0
  • “the DRNC shall include for each of these active MBMS bearer services in the Active MBMS Bearer Service List IE the Transmission Mode IE” TS 25.423 v6.17.0
Rel-8 specification text

In RNSAP, the DRNC performs UE Linking for the MBMS Bearer Service List IE only 'if supported', and new information exchange types report MBMS counting, transmission mode and RLC sequence number per MBMS bearer service.

  • “the DRNC shall, if supported, perform the UE Linking as specified in [50], section 5.1.6.” TS 25.423 v8.14.0
  • “Correction for procedural text for MBMS Bearer Service List IE” TS 25.423 v8.14.0
  • “the RNC2 shall report for each TMGI included in the received MBMS Bearer Service Identifiers List IE” TS 25.423 v8.14.0
Rel-12 specification text

RNC handling of MBMS SESSION START from several CN nodes for an MBMS Bearer Service now applies only when the Session Re-establishment Indicator IE is absent.

  • “all the MBMS SESSION START messages include the RA List of Idle Mode UEs IE and does not include the Session Re-establishment Indicator IE” TS 25.413 v12.4.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.846 v610 MBMS Architecture and Functionality Rel-6 read
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19 read