Multimedia Broadcast Multicast Service Subchannel

Description

The MBMS subchannel is a concept introduced in 3GPP Release 13 to support group communication services (such as Mission Critical Push-to-Talk, MCPTT) over MBMS. It is defined as a logical channel that uses the resources of an activated and announced MBMS bearer, identified by the TMGI of that bearer, along with additional parameters like UDP port. These additional parameters allow multiple logical channels to be multiplexed over a single MBMS bearer, each serving a different purpose or group. For example, in a group call, one subchannel might carry the media (voice), while another subchannel carries floor control messages (e.g., to indicate when a user is talking).

Architecturally, the MBMS subchannel is not a separate radio bearer; it is a logical construct that leverages the underlying MBMS bearer's transport capabilities. The MBMS bearer provides the physical and transport resources (e.g., radio resources, IP multicast address, TMGI), while the subchannel adds a layer of differentiation using parameters such as UDP port numbers. This allows the network to send different types of data (e.g., media, signaling) to the same group of UEs without setting up multiple MBMS bearers, which would be resource-intensive. The subchannel concept is particularly important for group communication, where multiple streams (e.g., audio from different talkers, control messages) need to be delivered to the same set of users.

The operation of an MBMS subchannel involves the BM-SC and the group communication service enabler (e.g., MCPTT server). When a group call is established, the server activates an MBMS bearer and assigns subchannels for different purposes. The subchannel information (e.g., UDP port) is announced to the UEs via the MBMS user service discovery/announcement mechanisms. UEs that join the group call receive the bearer and then filter the incoming packets based on the subchannel parameters to extract the relevant streams. This filtering is typically done at the IP layer using the UDP port number.

Key components include the TMGI, which identifies the MBMS bearer, and the additional parameters (e.g., UDP port) that identify the subchannel. The subchannel may also be used for other purposes, such as informing when a conversation in a group call is started or ended. This is crucial for synchronizing the group communication state across all participants. The subchannel concept thus provides a flexible and efficient way to deliver multiple logical streams over a single MBMS bearer, reducing the overhead of managing multiple bearers.

The MBMS subchannel is defined in specifications such as 23.479 (Mission Critical Services over MBMS), 24.380 (MCPTT media plane), and 24.581 (MCPTT media plane). Its introduction in Release 13 coincided with the development of mission-critical services, which require robust and efficient group communication. The subchannel mechanism allows these services to leverage MBMS for scalability while maintaining the necessary control and media separation. It has been carried forward in subsequent releases without changes to its definition, indicating its stability and continued relevance.

Purpose & Motivation

The MBMS subchannel was created to address the need for efficient group communication over MBMS, particularly for mission-critical services like MCPTT. In group calls, multiple types of data (e.g., voice media, floor control signaling) must be delivered to all group members. Using separate MBMS bearers for each data type would be inefficient, as each bearer consumes radio and core network resources. The subchannel concept solves this by allowing multiple logical channels to share a single MBMS bearer, differentiated by parameters like UDP port. This reduces resource consumption and simplifies session management.

Before the subchannel, group communication over MBMS would have required either multiplexing all data into a single stream (which complicates processing) or using multiple bearers (which is wasteful). The subchannel provides a middle ground: it allows logical separation without the overhead of multiple bearers. This is especially important in mission-critical scenarios where resources may be scarce and reliability is paramount. The subchannel also enables the network to inform UEs about the state of the group call (e.g., when someone starts or stops talking) through a dedicated control subchannel, ensuring that all participants have a consistent view of the call.

The introduction of the subchannel in Release 13 was driven by the 3GPP's work on mission-critical services, which required a robust and scalable group communication enabler. The subchannel concept has since become a key part of the MBMS-based group communication architecture, allowing operators to deploy MCPTT and similar services efficiently. It also aligns with the broader trend of using MBMS for specialized services beyond traditional mobile TV, demonstrating the flexibility of the MBMS framework.