MCCH

MBMS point-to-multipoint Control Channel

Radio Access Network
Introduced in Rel-2
A logical channel in 3GPP networks used exclusively for broadcasting control information related to Multimedia Broadcast Multicast Services (MBMS). It carries critical configuration and scheduling details for MTCH channels, enabling efficient point-to-multipoint content delivery to multiple UEs simultaneously.

Description

The MBMS point-to-multipoint Control Channel (MCCH) is a downlink logical channel defined within the 3GPP radio access network architecture. It operates as a critical component of the MBMS framework, which is designed for efficient broadcast and multicast service delivery. As a logical channel, the MCCH is mapped onto transport channels and eventually physical channels for transmission over the air interface. Its primary function is to carry control plane information necessary for UEs to receive MBMS services on the Multicast Traffic Channel (MTCH). This information includes MBMS service announcements, session start notifications, and most importantly, the Radio Resource Control (RRC) configuration messages that specify how the associated MTCH is scheduled and transmitted. The MCCH is transmitted in a point-to-multipoint fashion within an MBMS Single Frequency Network (MBSFN) area, meaning a single transmission is received by all subscribed UEs within that geographic zone.

Architecturally, the MCCH is defined per MBSFN area. An MBSFN area is a collection of cells that are synchronized to transmit identical waveforms for MBMS content, creating a seamless broadcast region. Within each MBSFN area, there is one unique MCCH. The network uses System Information Blocks (SIBs), specifically SIB13 in LTE and SIB20 in NR, to inform UEs about the scheduling and configuration of the MCCH itself. This includes parameters like the modification period, repetition period, and subframe allocation. The UE, after acquiring this SIB, knows when and where to listen for the MCCH to obtain the necessary RRC configuration (an MBSFNAreaConfiguration message) for the MTCHs it is interested in.

The operation of the MCCH is characterized by its periodic and change-driven notification mechanism. It is transmitted at predefined intervals. To save UE battery, a change notification mechanism is employed. Short notifications are sent on a related physical channel (e.g., MICH in UMTS, PDCCH with G-RNTI/MCS-RNTI in LTE/NR) to alert UEs only when the MCCH information is about to change in the next modification period. If no notification is detected, the UE can assume the previous MCCH configuration remains valid and does not need to decode the MCCH repeatedly. The content on the MCCH includes a list of MBMS services (identified by Temporary Mobile Group Identities - TMGIs) active in the area and, for each, the associated logical channel configuration for the MTCH. This tells the UE the specific radio bearer configuration, scheduling, and MCS (Modulation and Coding Scheme) to use for decoding the multimedia content.

In the overall protocol stack, the MCCH exists at the RRC layer. The information is generated by the RRC entity in the base station (eNodeB/gNB) based on instructions from the core network's MBMS coordination entity (MCE). It is then passed down through the Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC) layers, where it is assigned specific transport and physical resources. Its role is foundational to MBMS because without the control information it provides, UEs would be unable to discover, synchronize with, and correctly decode the broadcast multimedia streams, rendering the point-to-multipoint service delivery impossible.

Purpose & Motivation

The MCCH was created to solve the fundamental control signaling challenge for broadcast/multicast services in cellular networks. Traditional unicast services use dedicated signaling channels per UE, which is massively inefficient for services delivering identical content to thousands of devices, such as mobile TV or live event streaming. Without a shared control channel, the network would need to send individual RRC configuration messages to each UE, consuming excessive downlink radio resources and core network signaling capacity.

The introduction of MBMS in 3GPP Release 6 necessitated a complementary control mechanism that matched the efficiency of the point-to-multipoint data channel (MTCH). The MCCH provides this by broadcasting control information once for all UEs in an area. This design is intrinsically linked to the concept of MBSFN operation, where multiple cells transmit in synchrony. The MCCH carries the unified configuration that allows all UEs to tune into this synchronized transmission correctly. Its purpose extends beyond mere efficiency; it enables service scalability, allowing an unlimited number of UEs to join a broadcast session without impacting the control channel load. It also facilitates essential MBMS functions like service announcement (telling UEs what broadcasts are available) and session control (signaling the start and stop of a broadcast stream).

Historically, before dedicated broadcast systems like MBMS, delivering popular content required massive unicast duplication, which could congest the network. The MCCH, as part of the MBMS architecture, provided the standardized, cellular-integrated control plane that made network-based broadcast a viable and efficient service for operators. It addressed the limitations of previous non-cellular broadcast technologies (like DVB-H) by enabling tight integration with cellular mobility management and bi-directional capabilities, using the MCCH as the one-way broadcast conduit for all necessary reception parameters.

Key Features

  • Broadcasts MBMS control information point-to-multipoint within an MBSFN area.
  • Carries RRC configuration messages (MBSFNAreaConfiguration) for MTCH decoding.
  • Utilizes a change notification mechanism (e.g., via PDCCH) to minimize UE power consumption.
  • Configured and scheduled via system information (SIB13 in LTE, SIB20 in NR).
  • Transmitted periodically with defined modification and repetition periods.
  • Contains a list of active MBMS services and their associated radio bearer configurations.

Evolution Across Releases

Rel-6 Initial

Initially introduced in UMTS as part of the first MBMS feature set. Defined as a logical channel for carrying control information for MBMS services in UTRAN, including service announcement and RB configuration for point-to-multipoint transmission.

Re-defined and enhanced for LTE as part of evolved MBMS (eMBMS). Integrated with the new MBSFN architecture. MCCH scheduling and configuration details were specified via SIB13, and its mapping to the transport channel MCH (Multicast Channel) was established.

Enhanced for LTE-Advanced. Further optimizations and clarifications on MCCH procedures and its interaction with the MCE (Multi-cell/multicast Coordination Entity) for consistent configuration across an MBSFN area.

Introduced enhancements for LTE-based FeMBMS (Further evolved MBMS), including support for longer cyclic prefix and new subcarrier spacing, impacting the physical layer configuration carried by the MCCH.

Re-defined for 5G NR as part of the new MBS (Multicast and Broadcast Services) architecture. The MCCH concept was adapted for NR, with scheduling and configuration now provided via SIB20. A new RNTI (MCCH-RNTI) was introduced for scrambling the PDCCH carrying MCCH scheduling information.

Defining Specifications

SpecificationTitle
TS 21.905 3GPP TS 21.905
TS 23.468 3GPP TS 23.468
TS 23.479 3GPP TS 23.479
TS 23.792 3GPP TS 23.792
TS 25.102 3GPP TS 25.102
TS 25.301 3GPP TS 25.301
TS 25.302 3GPP TS 25.302
TS 25.304 3GPP TS 25.304
TS 25.321 3GPP TS 25.321
TS 25.322 3GPP TS 25.322
TS 25.331 3GPP TS 25.331
TS 25.346 3GPP TS 25.346
TS 25.401 3GPP TS 25.401
TS 25.402 3GPP TS 25.402
TS 25.912 3GPP TS 25.912
TS 25.931 3GPP TS 25.931
TS 36.300 3GPP TR 36.300
TS 36.302 3GPP TR 36.302
TS 36.304 3GPP TR 36.304
TS 36.322 3GPP TR 36.322
TS 36.443 3GPP TR 36.443
TS 36.976 3GPP TR 36.976
TS 38.300 3GPP TR 38.300
TS 38.304 3GPP TR 38.304
TS 38.321 3GPP TR 38.321
TS 38.322 3GPP TR 38.322
TS 38.331 3GPP TR 38.331
TS 38.523 3GPP TR 38.523