Description
The Master eNB (MeNB) is a central concept of Dual Connectivity (DC) in E-UTRAN, introduced in Release 12. Dual Connectivity allows a UE to be served simultaneously by two or more eNBs — typically a macro cell and a small cell — to boost user throughput and improve mobility robustness. In this architecture, one of the participating eNBs is designated the Master eNB and the other(s) the Secondary eNB (SeNB). The MeNB is defined as the eNB that terminates at least the S1-MME interface towards the Mobility Management Entity (MME), and therefore acts as the mobility anchor towards the core network for the UE.
Architecturally, the MeNB holds the RRC connection with the UE and is responsible for the control-plane relationship with the core network. It terminates S1-MME towards the MME, and it coordinates radio resource configuration across the DC group by exchanging messages with the SeNB over the X2-C interface (X2AP). User-plane traffic can be split in different ways: in the SCG bearer option, the SeNB terminates S1-U directly towards the Serving Gateway; in the split bearer option, the MeNB terminates S1-U and forwards part of the traffic to the SeNB over X2-U. The MeNB decides when to add, modify, or release secondary cell groups, and it remains the node that handles RRC reconfiguration, measurement configuration, and mobility decisions.
Because the MeNB is the mobility anchor, all handovers and tracking-area updates are coordinated through it. When the UE moves, the MeNB may decide to change the SeNB (SeNB change procedure) or to release dual connectivity entirely, without the core network necessarily being aware of the secondary node. This separation of control and data anchoring is what allows dense small-cell deployments to scale without multiplying S1 signalling towards the core.
The MeNB concept is defined and used across a wide set of specifications: TS 36.300 (overall E-UTRAN description and DC architecture), TS 36.423 (X2AP, including SeNB Addition/Modification/Release procedures), TS 36.425 (X2-U data forwarding for split bearers), TS 36.133 (radio resource management requirements, including measurement and mobility requirements in DC), TS 36.521 (UE conformance), TS 36.842 (the original DC study), TS 36.875 (further DC enhancements study), and TS 28.802 (management aspects). This breadth reflects how deeply DC touches both the radio and the management planes.
In later releases, the same master/secondary role model was extended to NR with the Master Node (MN) and Secondary Node (SN) in Multi-RAT Dual Connectivity (EN-DC, NE-DC, NGEN-DC), where the MeNB concept generalizes to the master node. The MeNB remains the canonical example of the anchor-node pattern that underpins all subsequent dual-connectivity architectures.
Purpose & Motivation
Before Release 12, a UE was connected to exactly one eNB at a time. Operators deploying heterogeneous networks — macro cells overlaid with small cells — found that the small cells could not deliver their full capacity benefit because the UE's control plane and data plane were both tied to a single node, and frequent handovers between macro and small cells caused signalling overhead and interruptions. The desire to aggregate radio resources from multiple eNBs simultaneously, without multiplying core-network interfaces, motivated Dual Connectivity.
The Master eNB concept solves the anchoring problem: by designating one node as the S1-MME terminator and mobility anchor, the architecture keeps a single, stable control-plane relationship with the core network while allowing additional radio resources to be added and removed dynamically. The SeNB can be changed without touching S1, which keeps core signalling proportional to UE mobility rather than to the number of radio nodes involved.
This design also enabled practical split-bearer operation, where the MeNB's robust macro link carries signalling and can carry a portion of user data, while the SeNB provides a throughput boost. The pattern proved so successful that it became the template for EN-DC and all later multi-connectivity architectures in 5G, where the master node remains the control-plane anchor.
What changed in its specifications
The latest release-to-release comparison of specifications that define Master eNB. Each summary describes the whole specification, not only this term.
Rel-19 adds enhanced NR NTN and IoT NTN requirements and test methods to TS 36.133. It also removes many clauses, mainly SCell delay, RSRP accuracy, NB-IoT and LTE-M measurement and test sections, plus multi-layer gap monitoring and CGI identification clauses.
Full comparison in TS 36.133 →Rel-19 added NTN IoT Phase 3 for LTE, covering regenerative payload S1 removal, Msg3 early data transmission, and ETWS/CMAS for NB-IoT NTN. It also added inter-RAT mobility from E-UTRAN terrestrial network to NR NTN, plus NR NTN feeder link switchover via handover.
Full comparison in TS 36.300 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Wording changed: the definition text was revised to reference TS 36.300 and to introduce the adjacent MBSFN ABS definition ('ABS configured in MBSFN-configurable subframe'), reflecting editorial restructuring of the DC-related definitions rather than a change to the MeNB role itself.
Defining Specifications
3GPP specifications that define or reference Master eNB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 28.802 vf00 | Management Study for 5G Network Architecture | Rel-15 read |
| TS 36.133 vj60 | LTE Radio Resource Management Requirements | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.423 vj10 | X2 Application Protocol (X2AP) Specification | Rel-19 read |
| TS 36.425 vj00 | X2 User Plane Protocol for Dual Connectivity | Rel-19 read |
| TS 36.521 vj11 | E-UTRA UE Conformance Testing for Satellite Access | Rel-19 read |
| TS 36.842 vc00 | Small Cell Enhancements for LTE Higher Layers | Rel-12 read |
| TS 36.875 vd10 | Dual Connectivity Extension Requirements | Rel-13 read |