Broadcast Service User

Description

The Broadcast Service User (BSU) is a fundamental logical entity within the 3GPP Multimedia Broadcast Multicast Service (MBMS) framework, standardized primarily in TS 22.947. It represents the consumer endpoint for broadcast and multicast content delivery services. Unlike a traditional unicast user, a BSU is defined by its subscription to and consumption of one or more MBMS services, which can include mobile TV, software updates, emergency alerts, or live event streaming. The BSU concept abstracts the physical user equipment (UE) to focus on the service consumption relationship, enabling the network to manage broadcast sessions, apply service-specific policies, and perform accurate charging based on service usage rather than individual packet flows.

Architecturally, the BSU exists within the service layer of the MBMS architecture. It interacts with the Broadcast-Multicast Service Center (BM-SC), which is the entry point for content providers and manages MBMS sessions. The BM-SC authenticates and authorizes BSUs for specific services, often leveraging the user's subscription profile stored in the Home Subscriber Server (HSS). When a BSU activates an MBMS service, the network establishes a bearer context that includes the BSU's identity, the requested service, and associated QoS parameters. This context is propagated through the core network (via the MBMS Gateway and Mobility Management Entity) and the radio access network (via the eNodeB in LTE or gNB in 5G NR) to ensure efficient delivery of content to all subscribed BSUs in a target area.

The BSU's role is critical for several network functions. For service management, the BSU identity allows the network to track which users are receiving which broadcast streams, enabling dynamic session management (like starting/stopping streams based on demand). For charging, the BSU provides a logical anchor for applying broadcast-specific charging models, which may differ from unicast (e.g., flat-rate, event-based, or time-based charging). From a QoS perspective, the BSU's service profile determines the priority, bandwidth, and error tolerance for the delivery of MBMS content, ensuring consistent user experience. In 5G, the concept evolves with enhanced Mobile Broadband (eMBB) and multicast-broadcast services, where BSUs can seamlessly switch between unicast and broadcast modes based on network conditions and service requirements.

Operationally, a BSU is typically associated with a temporary MBMS bearer context during an active service session. The BSU may be identified using a temporary identifier like the TMGI (Temporary Mobile Group Identity) combined with user-specific credentials. The network monitors BSU activity to optimize resource usage—for example, if no BSUs are subscribed in a certain cell, the network may suspend transmission there to save radio resources. The BSU concept also supports mobility: as a user moves, their BSU context is updated to ensure continuous service reception across different broadcast service areas, managed by procedures like MBMS service continuity.

Purpose & Motivation

The Broadcast Service User (BSU) concept was introduced to address the unique requirements of broadcast and multicast services in cellular networks, which differ fundamentally from traditional point-to-point unicast services. Prior to MBMS and the BSU abstraction, 3GPP networks primarily focused on unicast communication, where each user had a dedicated connection. This approach was inefficient for delivering popular content (like live sports or news) to many users simultaneously, as it duplicated data streams and consumed excessive network resources. The BSU provides a standardized way to model users as consumers of shared broadcast flows, enabling efficient one-to-many delivery and solving the scalability challenges of unicast for mass content distribution.

Historically, the motivation for BSU emerged with the development of MBMS in 3GPP Release 6, which aimed to support mobile TV and group communications. However, the formalization of BSU in Release 9 (as documented in TS 22.947) refined the architectural model by clearly separating the service user from the underlying transport mechanisms. This separation allowed operators to manage broadcast services independently of radio access technologies (e.g., transitioning from 3G to LTE and later 5G broadcast). The BSU abstraction also addressed business needs by enabling flexible service provisioning—operators could offer subscription-based broadcast packages, trial services, or free-to-air content, all tracked through BSU identities for charging and analytics.

Furthermore, the BSU concept solves technical limitations related to service awareness and network optimization. Without a defined BSU entity, the network would treat broadcast packets as anonymous datagrams, making it difficult to implement user-specific policies, such as parental controls for mobile TV or targeted emergency alerts. By modeling the BSU, 3GPP standards enable service-layer intelligence: the network can authenticate users for premium content, monitor service usage for quality assurance, and dynamically allocate resources based on the number and distribution of active BSUs. This purpose extends into 5G era applications like public safety communications, automotive updates, and immersive media, where efficient multicast delivery to identified user groups is essential.

Key Features

• Logical representation of a broadcast/multicast service consumer
• Enables service-specific authentication and authorization via BM-SC
• Supports flexible charging models for broadcast content delivery
• Facilitates QoS management and policy enforcement for MBMS flows
• Allows dynamic session management based on active user presence
• Enables mobility support for continuous broadcast service reception

Evolution Across Releases

Defining Specifications