Description
MBMS notification is a fundamental mechanism in 3GPP Multimedia Broadcast Multicast Service (MBMS) that informs User Equipment (UE) about upcoming, ongoing, or changing MBMS data transmissions. It serves as a control-plane signaling function that allows the network to coordinate the reception of broadcast/multicast content across multiple users without requiring individual dedicated connections. The notification can be transmitted via various channels depending on the radio access technology and release, such as the MBMS Control Channel (MCCH) in E-UTRAN or via paging and system information in UTRAN.
The primary purpose of MBMS notification is to alert UEs that a specific MBMS service is about to start, is currently active, or has changed its transmission parameters. This allows UEs to activate their receivers, configure the necessary radio bearers, and synchronize with the broadcast data. In UTRAN, the notification is provided by the RNC (Radio Network Controller) and can be sent on the MCCH, which carries control information for MBMS. The notification may include details such as the service identity, session start/stop, and scheduling information. UEs that have subscribed to or are interested in the service monitor these notifications to determine when to receive data.
The mechanism operates in both broadcast and multicast modes. In broadcast mode, the notification is sent to all UEs in a cell, while in multicast mode, it may be targeted to specific groups. The notification process is tightly coupled with the MBMS session start and stop procedures, which are initiated by the core network (e.g., BM-SC) and propagated to the radio access network. The RAN then schedules the notification messages according to the configured repetition periods and modification periods, ensuring that UEs have sufficient opportunity to receive them.
Key components involved in MBMS notification include the MBMS Coordination Entity (MCE) in E-UTRAN, which manages the allocation of radio resources and ensures synchronization across eNBs; the Mobility Management Entity (MME) in the core network, which handles session control; and the UE, which processes the notifications to manage its reception state. The notification can be delivered via RRC signaling, such as the MBMSNotification message in UTRAN or the MCCH notification in LTE. In 5G, MBMS evolved into MBS (Multicast/Broadcast Service), where similar notification mechanisms are used but adapted to the NR architecture.
Overall, MBMS notification is essential for efficient use of radio resources, as it avoids the need for always-on reception and allows UEs to sleep when no relevant service is active. It also supports service continuity during mobility by informing UEs about changes in service availability across cells. The mechanism has been refined over releases to improve reliability, reduce latency, and support new use cases such as public safety and IoT.
Purpose & Motivation
MBMS notification exists to solve the problem of coordinating broadcast/multicast reception across many UEs without wasting radio resources. Before its introduction, delivering broadcast content required either continuous transmission (which drains UE battery) or individual signaling to each UE (which is inefficient). The notification mechanism allows the network to inform UEs only when there is actual data to receive, enabling UEs to conserve power by entering sleep modes when no relevant service is active.
Historically, MBMS was introduced in 3GPP Release 6 to enable efficient point-to-multipoint delivery of multimedia content over cellular networks. The notification mechanism was a key enabler, as it allowed UEs to be aware of service availability and changes without constant monitoring. This was particularly important for services like mobile TV and radio, where continuous reception would quickly deplete battery life. The notification also supports dynamic service changes, such as when a service is added or removed from a cell, ensuring that UEs can adapt their reception accordingly.
Over time, the notification mechanism has evolved to support more advanced features, such as MBS in 5G, where it is integrated with the NR control plane. The fundamental purpose remains the same: to provide a lightweight, scalable signaling method that keeps UEs informed about MBMS service status while minimizing overhead and power consumption.
What changed in its specifications
The latest release-to-release comparison of specifications that define MBMS notification. Each summary describes the whole specification, not only this term.
Rel-16 added SR-VCC handover from NR to UTRAN, integrity protection activation, and key set storage. These were the largest feature overviews for TS 25.331.
Full comparison in TS 25.331 →Rel-8 brings only minor changes to TS 43.246: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 43.246 →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 MBMS notification, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.846 v610 | MBMS Architecture and Functionality | Rel-6 read |
| TS 25.331 vj01 | UTRAN Radio Resource Control Protocol | Rel-19 read |
| TS 43.246 vj00 | MBMS in GERAN Stage 2 Specification | Rel-19 read |