MCE

Multi-cell/multicast Coordination Entity

Radio Access Network →
Introduced in Rel-8 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-8
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

Detected Changes Across Releases

from 3GPP Change Requests

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

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

Rel-15 6 changes

In Release 15, the MCE function was enhanced to support RAN sharing with multiple Cell ID broadcast for E-UTRAN, allowing a single cell to broadcast identifiers for multiple operators. This release also introduced specifications for reference signals to support MBSFN operations with 1.25kHz and 7.5kHz sub-carrier spacing. Furthermore, the specifications included corrections and refinements for resource coordination procedures and Multi-Radio dual connectivity involving the MCE.

  • E-UTRA - NR Cell Resource Coordination TS 36.300CR1122
  • Corrections on resource coordination in stage-2 TS 36.300CR1190
  • RAN sharing with multiple Cell ID broadcast TS 36.300CR1239
  • Corrections on Multi-Radio dual connectivity TS 38.300CR0137
  • Reference Signals for MBSFN with 1.25kHz and 7.5khz sub-carrier spacing TS 36.300CR1113
  • Multiple Cell ID broadcast for E-UTRAN sharing TS 36.300CR1238
Rel-16 6 changes

In Release 16, the MCE function was updated with clarifications and new capabilities for multi-transmission and reception point (multi-TRP) operations, as detailed in the updated technical descriptions. The release also introduced specific configurations for multicast broadcast single frequency network (MBSFN) transmissions, including new sub-carrier spacing options of 0.375 kHz and 2.5 kHz. Furthermore, it clarified the non-support of carrier aggregation (CA), dual connectivity (DC), or multi-TRP operation concurrently with DAPS handover.

  • Add measurement on RRC connection usage per UE multi RAT capability TS 32.425CR0188
  • NRIIOT Higher Layer Multi-Connectivity TS 38.300CR0253
  • CP length and reference signal for MBSFN with sub-carrier spacing of 0.375 kHz and 2.5 kHz TS 36.300CR1322
  • Description of Multi-TRP operation TS 38.300CR0300
  • Clarification on no support of CA, DC or multi-TRP with DAPS TS 38.300CR0307
  • Updated description of multi-TRP TS 38.300CR0359
Rel-17 4 changes

In Release 17, specific enhancements were introduced for the MCE function, including corrections for multicast configuration and service continuity within MBS (Multicast/Broadcast Service). Furthermore, a new "Resource Coordination Only" attribute was introduced in the context of Automatic Neighbour Relations (ANR) to refine coordination procedures. These updates aimed to improve the reliability and configuration of multicast distribution services across multiple cells.

  • Running CR to 36300 for Multi-USIM devices support TS 36.300CR1355
  • Running CR to 38300 for Multi-USIM devices support TS 38.300CR0422
  • Introduction of new attributes "Resource Coordination Only" in ANR TS 36.300CR1390
  • MBS corrections for multicast configuration and service continuity TS 38.300CR0613
Rel-18 4 changes

In Release 18, the MCE function was updated with the introduction of a unique MCE ID for identification and management, alongside enhancements for multi-carrier operation. The release also introduced a mechanism to consider UE preference for multi-receiver operation and included corrections to multi-cell scheduling procedures. These changes aimed to improve the coordination and efficiency of multicast and multi-cell transmissions.

  • Introduction on UE preference for multi-Rx operation in UAI TS 38.300CR0731
  • Introduction of Multi-carier enhancements TS 38.300CR0769
  • Correction to 38.300 for multi-cell scheduling TS 38.300CR0832
  • Rel-18 CR TS28.405 Adding MCE ID TS 28.405CR0027
Rel-19 4 changes

In Release 19, the MCE function was enhanced to support improved reliability for multicast sessions, specifically introducing procedures for the recovery from N3mb path failures during unicast transport of a multicast session. Furthermore, the release introduced new multi-path and multi-hop relay capabilities, including Multi-path Relay Enhancement and NR sidelink multi-hop U2N Relay, expanding the coordination of multicast delivery across more complex network topologies. These additions aimed to increase the robustness and flexibility of multicast service distribution within the 5G system.

  • Introduction of Multi-path Relay Enhancement [N3C_M_Relay] TS 38.300CR0991
  • Stage 2 CR for Rel-19 Multi-carrier enhancements TS 38.300CR1005
  • Introduction of NR sidelink multi-hop U2N Relay TS 38.300CR1028
  • Recovery of N3mb path failure for unicast transport of multicast session TS 38.300CR1032

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