MCE

Multi-cell/multicast Coordination Entity

Radio Access Network →
Introduced in Rel-9 Also in: Radio Access Network, Management

MCE is a logical LTE RAN function that coordinates radio configuration and resource allocation for eMBMS across multiple cells to enable synchronized MBSFN broadcast/multicast transmission.

Category
Radio Access Network
Introduced
Rel-9
Where
Services › IMS
Also touches
2 segments
Specifications
12 specs
MCE Description Purpose Related Classification Detected Changes Specifications

Description

The Multi-cell/multicast Coordination Entity (MCE) is a critical control plane function within the LTE Evolved Universal Terrestrial Radio Access Network (E-UTRAN) architecture for evolved Multimedia Broadcast Multicast Service (eMBMS). It is not a standalone physical node but a logical entity that can be implemented as part of the eNodeB (base station) or as a separate network element. Its primary role is to manage and coordinate all radio-related aspects of eMBMS delivery within a defined MBSFN (MBMS Single Frequency Network) area. An MBSFN area consists of a group of cells that are time-synchronized to transmit identical waveforms for an MBMS service, creating a seamless broadcast zone where signals from multiple cells combine constructively at the UE receiver.

Architecturally, the MCE sits between the MBMS Gateway (MBMS-GW) in the core network and the eNodeBs in the RAN. It communicates with the MBMS-GW via the M3 interface (based on IP) and with the eNodeBs via the M2 interface (also IP-based, using the M2AP protocol). When an MBMS session starts, the MBMS-GW sends a session start request to the MCE. The MCE is then responsible for the radio resource allocation decision. It calculates and decides on the common radio configuration parameters that all eNodeBs in the MBSFN area must use. These parameters include the MCS (Modulation and Coding Scheme) level, the allocation of subframes for MBSFN transmission (the MBSFN subframe pattern), the MCH (Multicast Channel) scheduling period, and the allocation of resources between different MBMS services (MTCHs) multiplexed on the same MCH.

After making these decisions, the MCE uses the M2 interface to send MBMS Scheduling Information (MSI) and the radio configuration to each participating eNodeB. This ensures absolute consistency across the MBSFN area, which is vital for successful SFN operation. A UE moving within the area receives identical physical layer parameters from every cell, allowing it to treat the combined transmissions as a single, powerful signal with multi-path diversity, rather than as interfering signals. The MCE also manages the admission control for new MBMS sessions, checking if sufficient radio resources are available in the MBSFN area before accepting a session start request from the core network.

In terms of operation, the MCE's coordination is ongoing. It can modify parameters during a session if needed, and it handles session stop procedures. For each MBSFN area, there is one MCE responsible. In deployments, a single MCE can control multiple MBSFN areas. Its functions are purely control-plane; user plane data for MBMS flows directly from the MBMS-GW to the eNodeBs via the M1 interface, bypassing the MCE. This separation ensures that the high-bandwidth multimedia traffic does not burden the coordination entity. The MCE is a cornerstone of eMBMS efficiency, transforming a collection of individual cells into a unified, synchronized broadcast network.

Purpose & Motivation

The MCE was created to solve the fundamental coordination problem inherent in implementing a Single Frequency Network (SFN) for broadcast within a cellular architecture. In a traditional unicast cellular network, each cell operates independently, scheduling resources for its connected UEs. For broadcast, where the same content must be delivered from many cells simultaneously, this independent operation would lead to chaos: cells would use different radio parameters (MCS, timing), causing destructive interference at cell edges and making it impossible for a UE to combine signals. The MCE provides the necessary centralized radio resource control to overcome this.

Before the standardized MCE in LTE Release 9, MBMS in UMTS (Release 6) had limited multicast capabilities and did not support true SFN operation on a wide scale, leading to lower spectral efficiency and coverage gaps. The introduction of eMBMS with MBSFN in LTE promised significant gains in spectral efficiency and coverage for broadcast services, but it required a new architectural element to realize this promise. The MCE was that element, designed to centrally manage the 'synchronized' aspect of MBSFN.

Its purpose extends beyond mere synchronization. It also optimizes the use of scarce radio resources for MBMS. By making a centralized decision on MCS and resource allocation, the MCE can choose the most robust parameters that satisfy the worst-case UE at the edge of the MBSFN area, ensuring service continuity for all subscribers. It also enables efficient statistical multiplexing of multiple MBMS services onto shared radio resources (the MCH). Without the MCE, achieving consistent, efficient, and reliable broadcast across a multi-vendor RAN would be extremely difficult, as each eNodeB would require complex peer-to-peer coordination protocols. The MCE abstracts this complexity, providing a single point of control and enabling the scalable deployment of broadcast services like mobile TV and public safety announcements over LTE networks.

Classification

Part ofMBSFN
Related approachesMBMS-GWMCH

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-18 1 change

In Release 18, a specific identifier for the Multi-cell/multicast Coordination Entity (MCE) was formally introduced into the management specifications. This change involved adding the "MCE ID" parameter to the relevant technical standard.

  • Rel-18 CR TS28.405 Adding MCE ID TS 28.405CR0027

Explore further

Broader topics and technologies where MCE plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.246 vj00 MBMS Bearer Service Stage 2 Description Rel-19
TR 23.780 ve00 MBMS for Mission Critical Communication Services Rel-14
TS 23.795 vg10 V2X Application Architecture Study Rel-16
TS 28.405 vj40 QoE Measurement Control & Configuration Rel-19
TS 32.425 vj00 E-UTRAN Performance Measurements Rel-19
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.440 vj00 E-UTRAN MBMS Architecture Description Rel-19
TS 36.444 vj00 M3AP Protocol Specification for M3 Interface Rel-19
TS 36.896 ve00 Study on Flexible eNB-ID and Cell-ID in E-UTRAN Rel-14
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TR 38.890 vh00 NR QoE Management and Optimization Rel-17
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.