Description
The Master Node (MN) is a central concept in 3GPP's dual connectivity and multi-radio dual connectivity (MR-DC) frameworks, such as EN-DC (E-UTRA-NR Dual Connectivity), NE-DC, NGEN-DC, and NR-DC. It refers to the radio access node (e.g., an eNB in LTE or a gNB in 5G NR) that acts as the control anchor for a User Equipment (UE) operating with a simultaneous connection to two different nodes. The MN terminates the control plane connection to the core network (e.g., the S1-C or N2 interface) and hosts the master cell group (MCG). It manages the primary cell (PCell) for the UE and is responsible for key radio resource control (RRC) functions, including connection establishment, reconfiguration, handover, and the addition/release of the secondary node.
Architecturally, the MN connects to the core network's control plane entity (MME in EPC or AMF in 5GC) and establishes a user plane connection (e.g., S1-U or N3). When configured for dual connectivity, the MN coordinates with a Secondary Node (SN) via the Xn or X2 interface. The MN sends the SN Addition Request message to prepare the secondary cell group (SCG) and manages the split of data radio bearers (DRBs) between the MCG and SCG. Bearers can be MCG bearers (anchored solely at the MN), SCG bearers (anchored solely at the SN), or split bearers where the PDCP layer is located in the MN (MN-terminated) or the SN (SN-terminated).
The MN's role is critical for seamless mobility and radio resource aggregation. It makes central decisions on handovers and connection reconfigurations, ensuring service continuity. In MR-DC scenarios involving different radio access technologies (e.g., LTE and NR), the MN provides the inter-RAT coordination, managing the security, QoS, and mobility procedures. The specifications detail MN procedures for bearer management, measurement configuration, and failure handling, making it a lynchpin for achieving the high data rates and reliability targets of advanced 4G and 5G networks.
Purpose & Motivation
The Master Node concept was introduced to address the need for aggregating radio resources from multiple transmission points or different radio access technologies to boost user data rates and enhance connection reliability. Prior to dual connectivity, a UE was connected to a single cell, limiting peak throughput to the capabilities of one link and one technology. Carrier aggregation improved this within the same technology, but dual connectivity, anchored by the MN, enabled simultaneous utilization of resources from geographically separate nodes, even across different RATs (e.g., LTE and 5G NR).
This architecture solves problems of capacity bottlenecks and coverage holes. By allowing a UE to maintain a primary, control-anchored connection (the MN) while adding a secondary, capacity-boosting connection (the SN), networks can deliver higher aggregate bandwidth and better load balancing. It also facilitates smooth migration and interworking between 4G and 5G, as seen in EN-DC where an LTE eNB acts as the MN and a 5G gNB acts as the SN. The MN provides the stable control plane needed for mobility management while the SN provides additional user plane capacity.
Historically, the concept evolved from simpler coordination between base stations. The creation of the MN/SN split formalized the roles and interfaces (Xn/X2), enabling standardized, vendor-interoperable deployments. It addresses the limitation of single-node dependency, improving resilience against node failure and enabling advanced features like uplink/downlink decoupling and ultra-reliable low-latency communication (URLLC) through redundant paths.
What changed in its specifications
The latest release-to-release comparison of specifications that define MN. Each summary describes the whole specification, not only this term.
Rel-19 added external management data IOCs, discovery, notification retrieval, and single notifications. It added network slice lists in Area Scope, measurement conditions, and new data types for selecting instances via DNs, GeoAreas, or TAIs.
Full comparison in TS 28.622 →Rel-19 adds management aspects of RedCap features to TS 29.273. It also edits trusted non-3GPP access (TWAN) behaviour and authorization text around UE access priority.
Full comparison in TS 29.273 →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.
The Master Node concept was not explicitly defined in Rel-8; dual connectivity was not yet standardized. The foundational LTE architecture with eNB as the sole node was established.
Introduced dual connectivity for LTE (DC-LTE), defining the Master eNB (MeNB) and Secondary eNB (SeNB) roles. The MeNB acted as the MN, terminating the S1-MME and managing the MCG, enabling data aggregation from two LTE eNBs.
Formalized the term 'Master Node' (MN) within the 5G NR multi-radio dual connectivity (MR-DC) framework. Expanded scenarios to include EN-DC (LTE MN, NR SN), NE-DC (NR MN, LTE SN), and NR-DC (NR MN, NR SN), with the MN connecting to 5GC via N2/N3.
Defining Specifications
3GPP specifications that define or reference MN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.327 vd10 | 3GPP-WLAN Mobility Stage 2 Description | Rel-13 read |
| TS 28.622 vk40 | Generic Network Resource Information Service | Rel-20 read |
| TS 29.273 vj20 | EPS AAA Reference Points and Procedures | Rel-19 read |
| TS 32.422 vk30 | Trace, MDT and UE Measurement Control | Rel-20 read |
| TS 32.425 vj00 | E-UTRAN Performance Measurements | Rel-19 read |
| TS 32.856 vf00 | Energy Efficiency Assessment for RAN OAM | Rel-15 read |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 read |
| TS 33.501 vk30 | 5G Security Architecture | Rel-20 read |
| TS 33.822 v800 | Inter-Access Mobility Security Architecture | Rel-8 read |
| TS 33.825 vg01 | Security for 5G URLLC Services | Rel-16 read |
| TS 37.340 vj30 | Overview of Multi-Connectivity Operation using E-UTRA and NR | Rel-19 read |
| TS 38.133 vk10 | NR Radio Resource Management Requirements | Rel-20 read |
| TS 38.306 vj40 | NR UE Radio Access Capability Parameters | Rel-19 read |
| TS 38.401 vj30 | NG-RAN Architecture Description | Rel-19 read |
| TS 38.523 vj40 | UE Conformance Specification for 5G NR | Rel-19 read |
| TR 38.804 ve00 | Study on New Radio Access Technology; Radio Interface Protocol Aspects | Rel-14 read |