Description
MBMS bearer availability is a concept in the Multimedia Broadcast Multicast Service (MBMS) architecture, defined in 3GPP specifications 23.479 and 23.792. It refers to the presence of the Temporary Mobile Group Identity (TMGI) that identifies an MBMS bearer within the radio control channels. In other words, a bearer is considered available when the network advertises its TMGI on the radio interface control channels, allowing user equipment to discover and receive the associated broadcast or multicast service.
The TMGI is the identifier that ties together the service, the bearer, and the radio resources. When an MBMS bearer is established to deliver a service, the network assigns a TMGI and signals it in the radio control channels, such as the MCCH (Multicast Control Channel) in LTE or the corresponding NR multicast control channel. The presence of the TMGI in these channels tells UEs that the bearer exists and provides the information needed to receive it. If the TMGI is absent, the bearer is not available, even if the underlying service session is active elsewhere in the network.
Availability is distinct from reception quality. A bearer can be available (TMGI present) but have poor reception quality, or it can be unavailable (TMGI absent) and therefore not receivable at all. MBMS bearer quality monitoring, a related concept, evaluates the reception quality of an available bearer. Together, availability and quality monitoring allow the UE and network to manage service continuity, bearer selection, and fallback to unicast delivery.
The concept is used in MBMS and related broadcast/multicast architectures, including the 5G multicast-broadcast services (5MBS) framework. It supports procedures such as service announcement, bearer establishment and release, and mobility. When a UE moves between cells, it checks whether the TMGI is present in the target cell's control channels to determine whether the bearer remains available. This enables seamless continuation of broadcast/multicast reception and informs decisions about switching to unicast if the bearer is not available.
The definition of MBMS bearer availability remained unchanged across Releases 15 through 19, indicating a stable concept that carried forward as the architecture evolved from LTE MBMS toward 5G multicast-broadcast services.
Purpose & Motivation
MBMS bearer availability exists to provide a simple, unambiguous indicator of whether a broadcast/multicast bearer is currently offered in a given radio environment. Broadcast and multicast services are delivered over shared radio resources, and a UE must know whether a bearer is present before it can attempt reception. The presence of the TMGI in the radio control channels serves as that indicator.
The concept solves the problem of service discovery and continuity in multicast/broadcast networks. Without a defined notion of availability, a UE would have no reliable way to determine whether a service is being broadcast in its current cell, whether it should continue monitoring a bearer after cell reselection, or whether it should fall back to unicast. By tying availability to TMGI presence in control channels, 3GPP provides a mechanism that is simple to implement and robust across mobility scenarios.
The concept also supports network efficiency. Operators can make a bearer available only where there is demand, and UEs can avoid unnecessary monitoring when the bearer is not available. This complements quality monitoring and enables coordinated decisions about bearer selection, handover, and unicast fallback. The definition's stability from Release 15 onward reflects its foundational role in MBMS and its continued relevance in 5G multicast-broadcast services.
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 bearer availability, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.479 vj00 | MBMS API for Mission Critical Services | Rel-19 read |
| TS 23.792 vg00 | MBMS API for Mission Critical Services | Rel-16 read |