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

Glossary term · Services

Application Service

MBMS Application Service

Services →

Application Service is an end-user service whose entry point document is defined in the User Service Description, with all content components delivered via one or more MBMS User Services over broadcast and/or unicast bearers.

Introduced
Rel-11
Where
Security
Specifications
2 specs
Application Service Description Purpose What changed Neighbours Specifications

Description

The Application Service is a concept defined within the 3GPP Multimedia Broadcast/Multicast Service (MBMS) framework, primarily specified in TS 22.895 (service aspects) and TS 26.346 (codecs and media formats for MBMS). It represents a complete, user-facing service that is delivered to the end user through the MBMS bearer capabilities of a mobile network. Unlike a raw MBMS User Service, which is a transport-level construct for delivering content, an Application Service is the top-level service that the user actually consumes—for example, a live TV channel, a software update feed, or a group communication service. The entry point to the service is an XML document called the User Service Description (USD), which contains metadata that allows the UE to discover and access the service.

Architecturally, the Application Service sits above the MBMS User Service layer. The USD provides the entry point document that describes the service, including the list of associated MBMS User Services and their delivery parameters. Each MBMS User Service may be delivered via broadcast (using MBMS bearers) or unicast (using unicast bearers), and the Application Service can use a combination of both. This allows for flexible delivery: popular content can be broadcast to many users simultaneously, while less popular or personalized content can be delivered via unicast. The Application Service concept enables service providers to define a service once and have it delivered efficiently across different radio access technologies and network conditions.

The key components of an Application Service include the entry point document (USD), the set of MBMS User Services that carry the content components, and the delivery methods (broadcast and/or unicast). The USD is typically delivered to the UE via an interaction with the MBMS service discovery mechanisms, such as the Service Announcement function. The UE uses the USD to learn how to access the service, including the session description, scheduling information, and security parameters. The Application Service may also include associated delivery procedures, such as file repair and reception reporting, which are handled by the MBMS download delivery method.

In the network, the Application Service is managed by the MBMS service layer, which includes the Broadcast Multicast Service Center (BM-SC) and the MBMS Gateway (MBMS-GW). The BM-SC is responsible for service provisioning, announcement, and security, while the MBMS-GW handles the user plane delivery of MBMS packets to the eNodeB/gNodeB. The Application Service is thus an end-to-end service that spans from the content provider through the 3GPP network to the UE. It is a crucial concept for enabling efficient delivery of popular content, such as live streaming, emergency alerts, and software updates, over cellular networks.

The Application Service concept has evolved over releases, with the definition being refined to better reflect the multi-user-service and multi-bearer nature of modern MBMS deployments. It is a foundational term for understanding how 3GPP networks support broadcast and multicast services, and it is closely related to other MBMS concepts such as User Service Description, MBMS User Service, and Broadcast Multicast Service Center.

Purpose & Motivation

The Application Service concept was created to provide a clear separation between the user-facing service and the underlying delivery mechanisms in MBMS. Before this concept, MBMS specifications focused on the transport of multicast/broadcast data, but there was no standardized way to describe a complete service that could be discovered and accessed by users. The Application Service solves this by defining a structured entry point (the USD) that contains all necessary information for a UE to access the service, including the list of associated MBMS User Services and their delivery parameters.

This abstraction allows service providers to define a service once and have it delivered over multiple bearers (broadcast and unicast) and potentially across different access networks. It also enables the network to efficiently manage resources by using broadcast for popular content and unicast for individualized content. The Application Service concept is essential for enabling new business models, such as broadcast-based live TV, emergency alerts, and IoT software updates, where efficient delivery to many users is critical.

The evolution of the definition reflects the growing complexity of MBMS services, moving from a simple web-based service to a multi-component service delivered through multiple MBMS User Services. This evolution addresses the limitations of earlier approaches that lacked a standardized service description and delivery framework.

What changed in its specifications

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

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 →

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-11 Initial

Initial definition: 'A network-based service delivered to the user through an application that resides on the UE. The Application Service may be web-based or non-web-based.' This established the concept of an application-level service delivered over MBMS.

Wording changed to: 'A service for which the entry point document is contained in the User Service Description and all associated resources are delivered through an MBMS User Service including broadcast and unicast fallback.' This clarified the role of the USD and the use of MBMS User Services with unicast fallback.

Definition carried over unchanged from Rel-12.

Definition carried over unchanged from Rel-12.

Definition carried over unchanged from Rel-12.

Wording changed to: 'An end-user service for which the entry point document is contained in the User Service Description and whereby all associated content components are delivered through one or more MBMS User Services via broadcast and/or unicast bearers.' This emphasized the end-user nature and the possibility of multiple MBMS User Services and mixed bearers.

Definition carried over unchanged from Rel-16.

Definition carried over unchanged from Rel-16.

Definition carried over unchanged from Rel-16.

Defining Specifications

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

SpecificationTitleRelease
TS 22.895 vc00 3GPP Single Sign-On Framework Rel-12 read
TS 26.346 vj30 MBMS User Services Specification Rel-19 read