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.
What changed in its specifications
The latest release-to-release comparison of specifications that define MCE. Each summary describes the whole specification, not only this term.
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 →Rel-19 brings only minor changes to TS 23.246: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.246 →Technology family
Broadcast and multicast · Services
- Phase 1 CBC, CBCH, CBS, SMS-CB
- Phase 2 CBE
- R99 BMC, SABP
- Rel-6 ALC, BM-SC, FDT, FLUTE, LCT, MBMS, MBMS Bearer Service, MBMS download delivery method, MBMS streaming delivery method, MBMS User Service, TMGI
- Rel-7 MBSFN
- Rel-8 ETWS, MCE, PWS
- Rel-9 CBSP, CMAS, eMBMS, MBMS-GW
- Rel-10 KPAS
- Rel-11 EU-Alert
- Rel-12 MooD
- Rel-13 MBMS group communication delivery method, SC-PTM
- Rel-14 MBMS transparent delivery method, Receive Only Mode
- Rel-15 CBCF, PWS-IWF
- Rel-16 5G Broadcast
- 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 sourcesDocumented changes in 10 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.
Introduced in Rel-8 (release dating of the term; no individual change cited).
The MCE is defined for the first time as a logical entity doing admission control and radio resource allocation for MBSFN, with M3 session procedures to the MME and M2 signalling to eNBs.
- “The MCE is a logical entity” TS 36.300 v9.10.0
- “The MCE manages the E-MBMS Service Multiplex e.g. deciding which services are to be multiplexed on which MCH.” TS 36.300 v9.10.0
- “The MCE shall report to the MME, in the MBMS SESSION START RESPONSE message the result of the requested MBMS E-RAB.” TS 36.444 v9.4.0
MCE gains pre-emption by ARP in admission control, a split into distributed and centralized MCE architectures, and new session start, counting, and suspension/resumption functions.
- “The MCE decides not to establish the radio bearer(s) of the new MBMS service(s) if the radio resources are not sufficient” TS 36.300 v10.12.0
- “the MCE is a logical entity which means it can be deployed as a stand-alone physical entity or collocated in another physical entity” TS 36.300 v10.12.0
- “The MBMS Service Counting Function enables the MCE to perform counting and to receive counting results per MBMS service(s) within MBSFN area(s).” TS 36.300 v10.12.0
MCE behaviour changed: it now takes absolute 'Time of MBMS Data Transfer/Stop' into account for MCCH update synchronisation, and gains M3 Setup and MCE Configuration Update procedures, including a distributed MCE architecture.
- “the MCE shall, if supported, take it into account for the synchronization of the corresponding MCCH Update instead of the “Minimum Time to MBMS Data Transfer”” TS 36.444 v11.6.0
- “The MCE initiates the procedure by sending an MCE CONFIGURATION UPDATE message to the MME including an appropriate set of updated configuration data” TS 36.444 v11.6.0
- MCE and MBSFN role for distributed MCE architecture TS 36.300CR0465
MCE behaviour changed: it accepts MBMS Session Start with a Re-establishment IE for ongoing services, handles ARP updates in Session Update, and gains MCE restoration/failure handling procedures.
- “If the MCE receives the MBMS SESSION START REQUEST message including the Re-establishment IE for a service which is already ongoing, it shall, if supported, accept this message” TS 36.444 v12.2.0
- “If the ARP parameter is updated, the corresponding update of resources shall follow the principles described for the MBMS Session Start procedure.” TS 36.444 v12.2.0
- “When an MCE fails, the MCE shall release all the MBMS services affected by the failure locally and towards E-UTRAN” TS 23.007 v12.9.0
MCE behaviour was extended for SC-PTM operation: it decides between SC-PTM and MBSFN per session, forwards SC-PTM information and cell lists to eNBs, and handles new failure cases.
- “The MCE makes the decision on whether to use SC-PTM or MBSFN for each MBMS session.” TS 36.300 v13.14.0
- “In SC-PTM operation, the MCE shall forward the information in the MBMS E-RAB QoS parameters IE to the relevant eNBs.” TS 36.444 v13.2.0
- “In SC-PTM operation, the MCE includes the SC-PTM information” TS 36.300 v13.14.0
A note was added to TS 36.300 clarifying that the MCE does not need to check the PLMN ID included in the TMGI.
- “NOTE: The MCE does not need to check the PLMN ID included in the TMGI.” TS 36.300 v14.13.0
In MBSFN operation, the MCE may now send the MBMS Session Start Response after receiving at least one eNB confirmation, whereas OLD stated this only for SC-PTM operation.
- “In MBSFN operation, the MCE may send the MBMS SESSION START RESPONSE message after it receives at least one confirmation from the eNB(s)” TS 36.300 v15.14.0
The gNB is specified to send the QoE measurement collection (QMC) report to the MCE associated with the qoEReference and SliceScope, adding a new MCE-related step.
- “The gNB sends the QMC report to the MCE associated to the qoEReference and SliceScope.” TS 28.405 v17.4.0
The configuration information that the MCE indicates in advance to all eNBs for synchronized MCH scheduling now also includes time interleaving and frequency interleaving.
- “transmission order/priority information/time interleaving/frequency interleaving) such that synchronized MCH scheduling in the eNBs is ensured” TS 36.300 v19.2.0
Defining Specifications
3GPP specifications that define or reference MCE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.246 vj00 | MBMS Bearer Service Stage 2 Description | Rel-19 read |
| TR 23.780 ve00 | MBMS for Mission Critical Communication Services | Rel-14 read |
| TS 23.795 vg10 | V2X Application Architecture Study | Rel-16 read |
| TS 28.405 vj40 | QoE Measurement Control & Configuration | Rel-19 read |
| TS 32.425 vj00 | E-UTRAN Performance Measurements | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.440 vj00 | E-UTRAN MBMS Architecture Description | Rel-19 read |
| TS 36.444 vj00 | M3AP Protocol Specification for M3 Interface | Rel-19 read |
| TS 36.896 ve00 | Study on Flexible eNB-ID and Cell-ID in E-UTRAN | Rel-14 read |
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TR 38.890 vh00 | NR QoE Management and Optimization | Rel-17 read |