Broadcast/Multicast Control

Description

Broadcast/Multicast Control (BMC) operates as a sublayer within the Radio Link Control (RLC) layer of the UMTS protocol architecture, specifically in the User Plane. Positioned above the RLC layer and below the Packet Data Convergence Protocol (PDCP) layer, BMC provides specialized functions for broadcast and multicast traffic that differ from conventional unicast data handling. The protocol resides in both the User Equipment (UE) and the UTRAN (UMTS Terrestrial Radio Access Network), with the network-side BMC entity typically located in the Radio Network Controller (RNC).

BMC's primary function is to store broadcast messages received from the core network, schedule their transmission over the air interface, and handle message segmentation and reassembly. When a broadcast message arrives from the Core Network via the Iu interface, the BMC entity in the RNC stores it in a broadcast message queue. The protocol then schedules these messages for transmission over the Cell Broadcast Channel (CTCH) logical channel, which is mapped to the Forward Access Channel (FACH) transport channel. This scheduling considers factors like message priority, transmission periodicity, and system load to optimize radio resource usage.

The protocol architecture includes several key components: the BMC entity itself, which manages message storage and scheduling; the BMC-SAP (Service Access Point) for communication with upper layers; and interfaces with RLC for actual data transmission. BMC supports two main operational modes: broadcast mode for messages sent to all UEs in a cell, and multicast mode for messages targeted to specific subscriber groups. For MBMS services, BMC works in conjunction with other protocol layers to provide efficient multimedia content distribution, including support for selective combining and counting procedures to optimize resource utilization.

BMC implements several important mechanisms to ensure reliable and efficient broadcast/multicast delivery. These include message segmentation for large broadcasts, scheduling algorithms to prevent radio interface congestion, and support for geographical area-based message distribution. The protocol also handles cell broadcast service (CBS) messages, which are short text messages broadcast to all UEs in specific geographical areas. BMC's design minimizes UE power consumption by allowing devices to receive broadcast messages without establishing dedicated connections, making it particularly suitable for emergency alerts, location-based services, and multimedia broadcasting.

Purpose & Motivation

BMC was created to address the fundamental challenge of efficiently delivering the same content to multiple users simultaneously in cellular networks. Before BMC, cellular systems primarily relied on point-to-point (unicast) connections, which became highly inefficient when the same content needed to be delivered to many users in the same geographical area. This inefficiency consumed excessive radio resources and core network bandwidth, particularly for popular content like news updates, emergency alerts, or multimedia streams.

The protocol was introduced in 3GPP Release 4 as part of the UMTS architecture evolution to support broadcast and multicast services natively within the cellular system. Previous approaches either used repeated unicast transmissions (wasteful of resources) or relied on external broadcast systems like Digital Audio Broadcasting (DAB) or Digital Video Broadcasting (DVB), which required separate infrastructure and devices. BMC enabled integrated broadcast/multicast capabilities within the existing UMTS infrastructure, allowing operators to offer new services without deploying completely separate networks.

BMC specifically solved several technical problems: it provided standardized scheduling mechanisms for broadcast traffic, enabled efficient use of radio resources through shared channels, and supported both cell broadcast services (for short messages) and multimedia broadcast/multicast services (for richer content). The protocol's design considered the unique requirements of broadcast transmission, including support for discontinuous reception to conserve UE battery life, geographical targeting capabilities, and integration with existing UMTS mobility management functions. This made possible services like emergency warning systems, location-based information distribution, and eventually multimedia content broadcasting through MBMS.

Key Features

• Broadcast message storage and scheduling in the RNC
• Support for Cell Broadcast Service (CBS) messages
• Efficient radio resource utilization through shared channel transmission
• Geographical area-based message distribution capabilities
• Integration with Multimedia Broadcast/Multicast Service (MBMS)
• Discontinuous reception support for UE power saving

Evolution Across Releases

Defining Specifications