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

Glossary term · Protocol

BMC

Broadcast/Multicast Control

Protocol →

BMC is the UMTS protocol sublayer that manages broadcast and multicast data delivery over the air interface, handling scheduling, segmentation, and reassembly for efficient point-to-multipoint transmission.

Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Specifications
5 specs
BMC Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 25.301Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 25.301: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.301 →

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

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 4 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.

R99 introduced

The BMC sublayer is specified for the first time: a user-plane L2 sublayer above RLC, one entity per cell, using RLC unacknowledged mode and a CTCH, with scheduling and transmission of BMC messages.

  • “Broadcast/Multicast Control (BMC) is a sublayer of L2 that exists in the User-Plane only. It is located above RLC.” TS 25.324 v3.9.0
  • “At the UTRAN side, the BMC sublayer shall consist of one BMC protocol entity per cell.” TS 25.324 v3.9.0
  • “The present document provides the description of the Broadcast/Multicast Control Protocol (BMC). This protocol adapts broadcast and multicast services on the radio interface.” TS 25.324 v3.9.0
Rel-5 2 CRs

BMC specification (25.324) revised: bit order and message encoding clarified, maximum BMC PDU size addressed, and a 100ms UE schedule-reception timing rule reworded, with CBS message terminology refined.

  • “The UE is not required to receive a CBS Schedule Period starting earlier than 100ms after UE has received the complete BMC Schedule message.” TS 25.324 v5.6.0
  • Bit order in BMC messages TS 25.324CR013
  • Maximum size of BMC PDU TS 25.324CR016
Rel-6 1 CR

BMC message and schedule handling was changed: a new Schedule Message Extension IE and serial number were added, UEs must ignore unrecognised trailing bits, and bit order and IE coding were corrected.

  • “The UE shall ignore any unrecognised bits at the end of a BMC message.” TS 25.324 v6.6.0
  • “The IE "BMC Schedule Message Extension" is optional.” TS 25.324 v6.6.0
  • Introduction of Serial Number in BMC Schedule Message TS 25.324CR0028
Rel-7 1 CR

A Rel-7 correction clarifies how the "Offset to CTCH BS index of first transmission" field in the BMC Schedule message is interpreted.

  • Interpretation of "Offset to CTCH BS index of first transmission" in BMC Schedule message TS 25.324CR0030

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 25.324 vj00 Broadcast/Multicast Control Protocol Rel-19 read
TS 25.401 vj00 UTRAN Overall Architecture Rel-19 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19 read