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

Glossary term · Services

MC MBMS API

Mission Critical MBMS Application Programming Interface

Services →

MC MBMS API is a UE-side API that lets mission critical applications use MBMS bearer services for efficient point-to-multipoint delivery of MCPTT, MCVideo, and MCData traffic over broadcast bearers.

Introduced
Rel-15
Where
User Equipment
Specifications
2 specs
MC MBMS API Description Purpose Neighbours Specifications

Description

The MC MBMS API is an application programming interface exposed on the User Equipment (UE) that allows mission critical (MC) client applications to make use of the Multimedia Broadcast Multicast Service (MBMS) bearer service. MBMS, defined in 3GPP TS 23.246, provides point-to-multipoint delivery of IP data over a broadcast/multicast bearer, which is far more spectrum-efficient than unicast when the same content must reach many users simultaneously. In mission critical communications, group calls and group video are inherently one-to-many, so MBMS is a natural transport. The MC MBMS API is the abstraction layer that hides the complexity of MBMS bearer activation, deactivation, and monitoring from the MC application itself.

Architecturally, the API sits between the MC client (the application implementing MCPTT, MCVideo or MCData service logic) and the UE's MBMS client, which handles the broadcast/multicast bearer procedures. The MC client uses the API to request that a particular MBMS bearer be activated for a given group or service, to receive notifications about bearer availability and reception quality, and to release the bearer when the group session ends. The API is specified in 3GPP TS 23.479 (Mission Critical Services (MCS) MBMS bearer usage) and referenced in TS 23.792 (MBMS for mission critical services). It defines the primitives, parameters, and state model that the MC client and MBMS client exchange.

The API supports both broadcast and multicast modes of MBMS. In broadcast mode, the network transmits the bearer regardless of whether any UE is listening, which is useful for wide-area group communication. In multicast mode, the bearer is only activated when at least one UE has joined the multicast group, saving resources. The MC MBMS API allows the MC client to indicate which mode is required and to receive feedback on the actual bearer status. It also handles the mapping between MC service group identities and MBMS bearer identifiers (TMGIs and source/destination IP addresses), so the MC client does not need to manage transport-level identifiers directly.

A key function of the API is to provide the MC client with information about the reception quality of the MBMS bearer, such as whether the bearer is being received successfully, the current reception level, and any error conditions. This allows the MC client to decide whether to fall back to unicast if the broadcast reception degrades. The API also supports the concept of MBMS bearer announcement, where the network informs the UE about available bearers via the MBMS user service discovery/announcement procedures. The MC MBMS API translates these announcements into events that the MC client can subscribe to.

The MC MBMS API is used across all mission critical services. For MCPTT, it enables group voice calls to be delivered over MBMS, reducing the load on the unicast core network during large incidents. For MCVideo, it supports group video streaming to many responders. For MCData, it enables group messaging and file distribution. The API is designed to be independent of the underlying radio access technology, so it works over LTE (eMBMS) and 5G (5G MBS) as those broadcast technologies evolve. It is a critical enabler for scalable mission critical communications, especially in scenarios with hundreds or thousands of users in a small area.

Purpose & Motivation

The MC MBMS API exists to solve the scalability problem of mission critical group communications. Without it, each group call or video stream would require a separate unicast bearer to every user, consuming enormous radio and core network resources. MBMS provides an efficient point-to-multipoint alternative, but the complexity of managing MBMS bearers, mapping group identities to transport identifiers, and handling reception quality would otherwise fall on every MC application developer. The API standardizes this interface, allowing MC clients to use MBMS without deep knowledge of the underlying broadcast technology.

Historically, mission critical services were built on narrowband technologies like TETRA and P25, which had native group call capabilities but limited data throughput. When 3GPP began standardizing MCPTT over LTE in Release 13/14, the initial focus was on unicast delivery. However, it became clear that large-scale incidents (e.g., a stadium event or natural disaster) would overwhelm unicast resources. MBMS had been standardized since Release 6, but integrating it with mission critical services required a standardized API so that MC clients from different vendors could interoperate with MBMS clients from different vendors. The MC MBMS API was introduced in Release 15 to fill this gap.

The API also addresses the need for dynamic fallback. If MBMS coverage is poor, the MC client can switch to unicast seamlessly. The API provides the reception quality information needed for this decision. This hybrid approach ensures reliability while maximizing efficiency. The API has been maintained through Releases 16, 17, 18 and 19, with the definition text remaining unchanged, indicating a stable and mature interface that continues to serve its purpose as broadcast technologies evolve from LTE eMBMS to 5G MBS.

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.

Rel-15 Initial

Initial introduction of the MC MBMS API as an application programming interface on the UE to enable the use of MBMS bearer service for mission critical applications. Defined in TS 23.479 and TS 23.792, it established the primitives for bearer activation, monitoring and release.

The definition text carried over unchanged from Release 15. The API continued to provide the same interface for MC applications to use MBMS bearers.

The definition text carried over unchanged from Release 16. The API remained stable, with no change to its core definition.

The definition text carried over unchanged from Release 17. The API continued to be specified in TS 23.479 and TS 23.792 without definitional changes.

The definition text carried over unchanged from Release 18. The API remains a stable interface for mission critical MBMS usage.

Defining Specifications

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

SpecificationTitleRelease
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