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

Glossary term · Services

MBMS User Services

Multimedia Broadcast/Multicast Service User Services

Services →

MBMS User Services is the application-level service consumed by users, which may use more than one underlying MBMS bearer service and broadcast/multicast session for transport.

Introduced
Rel-6
Where
Services › Codecs
Specifications
5 specs
MBMS User Services Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

MBMS User Services are the top-level services offered to end users over the MBMS framework. According to 3GPP TS 22.246 and TS 26.346, an MBMS User Service is an application-level service that may be delivered using one or more MBMS bearer services and one or more broadcast and/or multicast sessions. This layered architecture separates the user service (what the user consumes) from the bearer service (how the data is transported) and the session (the actual radio transmission).

The concept of a user service is central to the MBMS architecture because it allows a single logical service — such as a mobile TV channel, a software update feed, or a live sports event — to be composed of multiple media streams and delivered over multiple bearers. For example, a streaming video service might use one bearer for the video component and another for the audio component, or it might use multiple sessions to provide different quality levels or to cover different geographic areas. The user service abstraction hides this complexity from the end user and from the application layer.

Each MBMS User Service is described by a User Service Description (USD), which is part of the Service Announcement metadata. The USD contains information about the service, including the service identifier, the delivery method (download or streaming), the media presentation description, the session descriptions, and the associated delivery procedures. The USD is typically delivered via HTTP or via MBMS itself, and it enables the UE to discover and initiate the service.

The relationship between user services and bearer services is many-to-many. A single user service may use multiple bearer services, and a single bearer service may carry data for multiple user services. This flexibility allows network operators to optimize resource usage by multiplexing different services onto the same bearer when appropriate. The mapping is defined in the USD and is used by the UE during the initiation procedure.

MBMS User Services can be categorized into two main delivery methods: download delivery and streaming delivery. Download delivery uses the FLUTE protocol to deliver files, with optional file repair and reception reporting. Streaming delivery uses RTP/RTCP for continuous media, with support for synchronization and error resilience. Both methods can be protected using MBMS security mechanisms.

In the context of 5G, the MBMS User Service concept has been extended to support the 5G MBS architecture, where user services can be delivered via 5G multicast/broadcast sessions. The fundamental principle of separating user services from bearer services remains, but the underlying transport and session management are adapted to the 5G core network and NR radio interface.

Purpose & Motivation

The MBMS User Service concept was created to provide a clear separation between the services that users consume and the underlying transport mechanisms. Before this abstraction, MBMS services were more tightly coupled to specific bearers, making it difficult to compose complex services from multiple media components or to adapt delivery to different network conditions.

The introduction of user services in Rel-8 (aligned with the EPS MBMS enhancements) allowed operators to offer rich multimedia services that could span multiple bearers and sessions, while keeping the user experience seamless. It also enabled the reuse of existing IETF protocols and web technologies for service announcement and delivery, reducing the need for proprietary solutions.

Furthermore, the user service abstraction supports service continuity and mobility, as the UE can maintain the user service context even when the underlying bearer changes (e.g., due to cell reselection or handover). This is essential for delivering broadcast/multicast services to mobile users without interruption. The concept also facilitates charging and policy control, as the user service can be associated with a particular QoS profile and charging model, independent of the bearer details.

What changed in its specifications

The latest release-to-release comparison of specifications that define MBMS User Services. Each summary describes the whole specification, not only this term.

TS 26.237Rel-10 → Rel-11

Added a suggested presentation offset for synchronized playout and updated the nBookmark XML schema to version 2.

Full comparison in TS 26.237 →
TS 26.346Rel-16 → Rel-17

Added a profiled FLUTE FDT schema with semantics and versioning, plus 5GMS references and requirements, removing old schema clauses. Updated User Service Bundle Description schema versions and added a new unicast announcement FQDN format.

Full comparison in TS 26.346 →

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 User Services counterpart in another generation: MBS User Service
    “MBS User Services are provisioned in the MBSF via reference point Nmb10 per the present document. eMBMS User Services are separately provisioned in the MBSF at reference point xMB-C per TS 26.348 [6]” TS 26.502

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 9 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

TS 26.346 first appears in Rel-6, specifying MBMS User Services: UE decoder requirements, functional entities, receiver function behaviour and deregistration.

  • “4.4 Functional Entities to support MBMS User Services” TS 26.346 v6.14.0
  • “The MBMS UE hosts the MBMS User Services receiver function.” TS 26.346 v6.14.0
  • “A UE that supports MBMS User Services shall support a decoder for the “MBMS FEC scheme”.” TS 26.346 v6.14.0
Rel-7 specification text

MBMS User Services may now use unicast/other UMTS bearer services for delivery, and the receiver function may receive data from unicast bearers as well as MBMS bearers.

  • “the MBMS User Services may use other UMTS bearer services to deliver data” TS 26.346 v7.11.0
  • “The MBMS receiver function may receive data from MBMS bearer services or from unicast bearer services.” TS 26.346 v7.11.0
Rel-8 specification text

TS 26.346 adds MBMS User Service deregistration procedure text and Raptor FEC decoder requirements for UEs supporting MBMS User Services; TS 26.237 first specifies MBMS User Services over IMS, including registration.

  • “The MBMS UE deregisters, when registration was required for the MBMS User Service.” TS 26.346 v8.7.0
  • “A UE that supports MBMS User Services shall support a decoder for the Raptor FEC scheme.” TS 26.346 v8.7.0
  • “This procedure is used to register a UE with one or more MBMS User Services.” TS 26.237 v8.7.0
Rel-9 specification text

The Raptor decoder requirement for UEs supporting MBMS User Services now refers to the RFC5053 section 5.3 encoder instead of Annex B, and a clause on UGC provision and distribution for IMS based PSS and MBMS User Services was added.

  • “generated according to the encoder specification in RFC5053 [91], section 5.3, for reconstruction of a source block, then the decoder shall recover the entire source block” TS 26.346 v9.15.0
  • “This clause defines the provision and distribution procedures of user generated content (UGC) for IMS based PSS and MBMS User Services.” TS 26.237 v9.11.0
Rel-11 specification text

A Filter Description metadata fragment was added to the USD, enabling selective or targeted UE reception of MBMS User Services or contents via filter data referenced from the Schedule Description.

  • “The Filter Description metadata fragment contains filter data to enable selective/targeted UE reception of MBMS User Services or contents.” TS 26.346 v11.14.0
Rel-12 specification text

User Service descriptions for MBMS User Services may now be fetched over HTTP via a unicast USD URL (pre-stored, OMA PUSH, or resolved from the Service Announcement FQDN).

  • “User Service descriptions may be transported to the UE using HTTP and other interactive transport methods.” TS 26.346 v12.12.0
  • “‘unicastUSD’ references a file that contains USD information for all MBMS User Services offered by the MBMS operator.” TS 26.346 v12.12.0
Rel-13 specification text

TS 26.346 gained text on MBMS User Services covering service discovery, a Service Announcement Channel profile, and a rule of one userServiceDescription per USBD, with separate USBD instances for multiple services.

  • “There shall be one userServiceDescription element per USBD.” TS 26.346 v13.7.0
  • “This section profiles Service Announcement over MBMS bearers as described in clause 5.2.3 by defining a Service Announcement Channel (SACH).” TS 26.346 v13.7.0
Rel-14 specification text

MBMS User Services gained new delivery methods (GC and Transparent) and Receive-Only-Mode service signalling via the r14:romService attribute in the user service description.

  • “The present document specifies four delivery methods for the MBMS user services: download, streaming, GC, and Transparent.” TS 26.346 v14.8.0
  • “The userServiceDescription element may include the r14:romService attribute which when set to "true" is an indication that the corresponding MBMS User Service is a Receive-Only-Mode (ROM) service.” TS 26.346 v14.8.0
Rel-16 specification text

The Service Announcement Channel profile now covers MBMS User Services for Live HLS and hybrid DASH/HLS services, and new definitions relate application services and MBMS applications to MBMS User Services.

  • “enable UEs to receive MBMS User Services for Live DASH, Live HLS, Live hybrid DASH/HLS service or Non-Real-Time file delivery” TS 26.346 v16.11.1
  • “all associated content components are delivered through one or more MBMS User Services via broadcast and/or unicast bearers” TS 26.346 v16.11.1

Defining Specifications

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

SpecificationTitleRelease
TS 26.237 vj00 IMS for PSS and MBMS Control Rel-19 read
TS 26.346 vj30 MBMS User Services Specification Rel-19 read
TS 26.852 ve20 MBMS user service profiles, APIs and transport enabler study Rel-14 read
TR 26.946 vj00 MBMS User Services Overview Rel-19 read
TR 26.947 vj00 FEC Evaluation for MBMS Enhancement Rel-19 read