Multimedia Broadcast/Multicast Service User Service Initiation

Description

MBMS user service initiation is the second phase of the MBMS user service consumption lifecycle, following discovery and preceding actual data reception. Once a UE has discovered an MBMS user service — typically via the Service Announcement function described in 3GPP TS 26.346 — it must initiate the reception of that service by activating the necessary bearers, joining the relevant multicast group, and configuring its protocol stack for the specific delivery method (download or streaming). The initiation procedure is defined in TS 26.346 and its implementation guidance in TS 26.946.

The initiation procedure operates across several layers. At the application layer, the UE processes the user service description (USD) obtained during discovery, which contains the media presentation description, session description, and associated delivery procedures. The UE then determines which MBMS bearer services and which broadcast or multicast sessions must be activated. At the bearer level, the UE interacts with the network to join the multicast group (for multicast mode) or to tune to the broadcast frequency (for broadcast mode). In E-UTRAN, this involves the MCE and eNB configuring the MBSFN subframes carrying the service, while in UTRAN the UE performs the appropriate RRC procedures.

A key aspect of initiation is the mapping between the user service and the underlying bearer services. A single MBMS user service may be delivered over multiple bearer services and multiple sessions, so the UE must correlate the session descriptions with the transport parameters. The initiation procedure handles the selection of the appropriate bearer, the setup of the file repair and reception reporting mechanisms (for download delivery), and the configuration of the streaming client (for streaming delivery).

For download delivery, initiation includes setting up the FLUTE (File Delivery over Unidirectional Transport) receiver, configuring the file repair procedure parameters, and preparing the reception reporting function. For streaming delivery, initiation configures the RTP/RTCP stack, buffering parameters, and synchronization mechanisms. The procedure also handles security aspects such as the acquisition of MBMS security keys (MSK, MTK) when service protection is applied.

In later releases, the initiation procedure has been adapted to support the 5G multicast/broadcast framework (MBS) introduced in Rel-17, where the interaction with the 5G core network and the MBS session management functions replaces some of the EPS-based procedures. However, the fundamental concept — that a UE must explicitly set up reception after discovering a service — remains unchanged. The initiation procedure is critical for efficient resource usage, as it allows the network to know which UEs are interested in a service and to optimize the radio resource allocation accordingly.

Purpose & Motivation

The MBMS user service initiation procedure exists to bridge the gap between a UE learning about an available MBMS service (discovery) and actually receiving its content. Without a defined initiation mechanism, UEs would have no standardized way to activate the correct bearers, join multicast groups, or configure their protocol stacks for the specific delivery method. This would lead to interoperability failures and inefficient use of radio resources.

The procedure was introduced in Rel-8 alongside the broader MBMS enhancements in EPS, which aimed to make MBMS more efficient and scalable. Prior to this, MBMS in UTRAN (Rel-6) had a more monolithic approach where service setup and bearer activation were less clearly separated. The Rel-8 architecture decomposed the process into discovery, initiation, and reception, allowing for greater flexibility and enabling features such as service announcement over HTTP and the reuse of existing IETF protocols (FLUTE, RTP).

By standardizing initiation, 3GPP ensured that UEs from different vendors could reliably join MBMS services, and that network operators could manage multicast/broadcast resources dynamically based on actual UE participation. The procedure also provides hooks for security (key acquisition) and for reception reporting, which are essential for commercial deployment of broadcast/multicast services.