SC-MCCH

Single Cell Multicast Control Channel

Radio Access Network →
Introduced in Rel-13

SC-MCCH is the logical channel in LTE that carries control information for Single Cell Point-to-Multipoint (SC-PTM), informing UEs about the configuration and scheduling of the associated multicast traffic channels.

Category
Radio Access Network
Introduced
Rel-13
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
3 specs
SC-MCCH Description Purpose Related Classification Detected Changes Specifications

Description

The Single Cell Multicast Control Channel (SC-MCCH) is a downlink logical channel defined within the LTE Radio Access Network for the Single Cell Point-to-Multipoint (SC-PTM) feature. It operates as the control plane component for SC-PTM, analogous to how the BCCH (Broadcast Control Channel) operates for cell-wide system information. The SC-MCCH is used by the eNodeB to broadcast essential configuration and scheduling information to all User Equipment (UEs) within a cell that are interested in receiving SC-PTM services. This information is crucial for UEs to successfully locate, demodulate, and decode the actual multicast data being transmitted on the associated Single Cell Multicast Traffic Channels (SC-MTCHs).

From an architectural perspective, the SC-MCCH is a logical channel mapped to the Downlink Shared Channel (DL-SCH) transport channel, which in turn is carried on the Physical Downlink Shared Channel (PDSCH). It is dynamically scheduled by the eNodeB, but its scheduling follows a specific repetition pattern defined by system information to ensure UEs can find it efficiently without continuous monitoring. The content of the SC-MCCH is defined in RRC (Radio Resource Control) messages, specifically the SC-MCCH message. This message contains a list of the SC-PTM services (identified by Group Radio Network Temporary Identifiers - G-RNTIs) currently active in the cell, along with the detailed configuration for each corresponding SC-MTCH, such as the modulation and coding scheme, periodicity, and scheduling information.

How it works involves a UE first acquiring the cell's standard system information (SIB). A specific System Information Block (SIB 20) provides the necessary parameters to receive the SC-MCCH, including its scheduling period, repetition period, and the PDSCH resource allocation. The UE then monitors the PDSCH at the indicated times to receive the SC-MCCH message. Upon decoding it, the UE can identify if the multicast service it wants (e.g., a public safety alert, a mobile TV stream) is being broadcast. If present, the UE extracts the SC-MTCH configuration for that service and begins monitoring the scheduled PDSCH resources to receive the multicast data. The SC-MCCH may be updated when services start or stop, and UEs re-acquire it periodically based on a modification period to stay synchronized.

Purpose & Motivation

SC-MCCH was created to support efficient multicast service delivery within a single LTE cell, a feature known as Single Cell Point-to-Multipoint (SC-PTM). Prior to SC-PTM, LTE primarily offered broadcast/multicast through eMBMS (evolved Multimedia Broadcast Multicast Service), which required a synchronized multi-cell MBSFN (Multicast Broadcast Single Frequency Network) architecture. MBSFN is complex to deploy and manage, suitable for large-scale content distribution but overkill for localized or dynamic multicast needs, such as public safety communications in a specific area or targeted advertising in a stadium.

The purpose of SC-MCCH is to provide a lightweight, cell-localized control mechanism for these simpler multicast scenarios. It solves the problem of how to dynamically inform a potentially large group of UEs within one cell about the availability and configuration of multicast services without establishing individual unicast connections for control signaling. This is essential for scalability and network efficiency when serving many users with the same content.

Motivated by use cases like IoT group messaging, public safety, and localized media, SC-PTM and its SC-MCCH control channel fill a gap between pure unicast (inefficient for group data) and full eMBMS (complex for single-cell deployment). It allows an operator or service provider to rapidly deploy a multicast service in a specific geographic area (a single cell) with minimal network configuration, using the existing shared channel (PDSCH) infrastructure. The SC-MCCH is the key enabler that makes this dynamic, cell-specific multicast service discovery and configuration possible.

Classification

Part ofSC-PTM
Related approachesSC-MTCHMBSFN

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-13, normative work from Rel-15.

Rel-15 4 changes

In Release 15, the SC-MCCH function was enhanced to support bearer availability monitoring, where the UE is notified if a TMGI becomes present or is removed from the SC-MCCH. This enables the UE to monitor for MBMS bearer suspension indications via the MSI. Furthermore, the release introduced mechanisms for the MC MBMS API to query multicast location information, such as MBMS SAI or ECGI, decoded from the local cell's broadcast information.

  • Missing description of RRC Connection Re-establishment for the Control plane TS 36.300CR1094
  • Reference Signals for MBSFN with 1.25kHz and 7.5khz sub-carrier spacing TS 36.300CR1113
  • Introduction of support for MAC PDU containing UE contention resolution identity MAC control element without RRC response message in NB-IoT TS 36.300CR1102
  • Introduction of DL channel quality reporting TS 36.300CR1245
Rel-16 1 change

In Release 16, the SC-MCCH function was enhanced to support new sub-carrier spacing configurations for MBSFN, specifically 0.375 kHz and 2.5 kHz, which involved defining the corresponding CP length and reference signal structures. Furthermore, the release introduced mechanisms for the MC MBMS API to notify applications about the presence or suspension of a TMGI specifically on the SC-MCCH, integrating it with procedures for MBMS bearer availability monitoring. These updates were part of broader work to apply the MC MBMS API solutions for mission critical services using SC-PTM mode.

  • CP length and reference signal for MBSFN with sub-carrier spacing of 0.375 kHz and 2.5 kHz TS 36.300CR1322

Explore further

Broader topics and technologies where SC-MCCH plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.792 vg00 MBMS API for Mission Critical Services Rel-16
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.322 vj00 E-UTRA Radio Link Control Protocol Specification Rel-19