Description
E-UTRA NR Dual Connectivity (EN-DC) is a specific dual connectivity configuration defined by 3GPP where the User Equipment (UE) is concurrently connected to two different radio access technologies: LTE (E-UTRA) and 5G New Radio (NR). In this architecture, the LTE base station (eNodeB) acts as the Master Node (MN), forming the Master Cell Group (MCG). The 5G NR base station (gNB) acts as the Secondary Node (SN), forming the Secondary Cell Group (SCG). The UE maintains a single control plane connection to the LTE Master Node via the MCG. The core network connection is anchored in the Evolved Packet Core (EPC), not the 5G Core (5GC), which classifies EN-DC as a Non-Standalone (NSA) 5G deployment mode.
How it works involves coordinated operation between the eNodeB (MN) and the gNB (SN). The LTE eNodeB is the control plane anchor, handling all Radio Resource Control (RRC) signaling, mobility management, and connection to the EPC (specifically the MME and S-GW). The NR gNB is primarily responsible for providing additional user plane capacity. Data can be split at the PDCP layer (located at the MN) or at the core network (S-GW). The MN's PDCP layer can route data packets to its own RLC layer (for transmission over LTE) or to the SN's RLC layer (for transmission over NR) via the X2 interface (enhanced as X2-C and X2-U). This requires tight synchronization and coordination between the two nodes.
Key components include the UE supporting both LTE and NR radios, the LTE eNodeB (Master eNB or MeNB), the NR gNB (Secondary gNB or SgNB), and the EPC. The critical interfaces are the LTE-Uu interface between UE and eNodeB, the NR-Uu interface between UE and gNB, and the X2 interface between the eNodeB and gNB for control (X2-C) and user plane (X2-U) coordination. The role of EN-DC in the network was to serve as the primary early deployment path for 5G, allowing operators to leverage their dense LTE infrastructure to provide wide-area 5G coverage and high data rates without requiring immediate investment in a full 5G core network, accelerating time-to-market for 5G services.
Purpose & Motivation
EN-DC was created to solve the problem of how to introduce and deploy 5G New Radio technology rapidly and cost-effectively before the 5G Core network was fully standardized and deployed. The primary motivation was to enable operators to offer enhanced mobile broadband (eMBB) services with very high data rates using 5G NR spectrum, while relying on the mature, ubiquitous, and stable LTE network for control plane functions and coverage anchoring.
Historically, it addressed the limitations of a pure "greenfield" 5G Standalone (SA) deployment, which would have required simultaneous rollout of new radio and a new core network, a massive and slow capital investment. EN-DC, as a Non-Standalone architecture, allowed a phased approach. It leveraged the existing LTE infrastructure as a reliable control plane and coverage layer, overlaying 5G NR capacity only in targeted areas (e.g., dense urban hotspots, stadiums) where the high throughput was most needed.
It solved key technical and business challenges: It provided a clear migration path, reduced initial deployment risk and cost, and allowed for early device ecosystem development focused on data-centric use cases. By anchoring to the EPC, it also ensured backward compatibility and service continuity for voice (VoLTE) and other LTE services. EN-DC was the cornerstone of the first wave of commercial 5G deployments globally, bridging the gap between 4G and full 5G Standalone systems.
Key Features
- Non-Standalone (NSA) 5G architecture anchored to LTE EPC
- LTE eNodeB as Master Node for control plane (RRC) and coverage
- NR gNB as Secondary Node for high-capacity user plane boost
- Data split/aggregation at the Master Node's PDCP layer or S-GW
- Utilizes enhanced X2 interface (Xn for NR is not used) for inter-node coordination
- Enables early 5G deployment without a 5G Core network
Evolution Across Releases
Introduced EN-DC as the foundational Non-Standalone 5G architecture. Defined the complete protocol stack, with LTE eNodeB as Master Node connected to EPC and NR gNB as Secondary Node. Specified the user plane architecture options (MCG, SCG, or split bearers), the control plane procedures via LTE RRC, and the enhancements to the X2 interface (X2-C and X2-U) for inter-RAT coordination.
Defining Specifications
| Specification | Title |
|---|---|
| TS 28.540 | 3GPP TS 28.540 |
| TS 28.552 | 3GPP TS 28.552 |
| TS 28.554 | 3GPP TS 28.554 |
| TS 28.558 | 3GPP TS 28.558 |
| TS 28.657 | 3GPP TS 28.657 |
| TS 28.707 | 3GPP TS 28.707 |
| TS 29.281 | 3GPP TS 29.281 |
| TS 32.425 | 3GPP TR 32.425 |
| TS 33.501 | 3GPP TR 33.501 |
| TS 36.212 | 3GPP TR 36.212 |
| TS 36.331 | 3GPP TR 36.331 |
| TS 36.413 | 3GPP TR 36.413 |
| TS 36.423 | 3GPP TR 36.423 |
| TS 36.424 | 3GPP TR 36.424 |
| TS 37.340 | 3GPP TR 37.340 |
| TS 37.473 | 3GPP TR 37.473 |
| TS 37.483 | 3GPP TR 37.483 |
| TS 37.571 | 3GPP TR 37.571 |
| TS 37.717 | 3GPP TR 37.717 |
| TS 37.718 | 3GPP TR 37.718 |
| TS 37.719 | 3GPP TR 37.719 |
| TS 37.825 | 3GPP TR 37.825 |
| TS 38.101 | 3GPP TR 38.101 |
| TS 38.133 | 3GPP TR 38.133 |
| TS 38.171 | 3GPP TR 38.171 |
| TS 38.213 | 3GPP TR 38.213 |
| TS 38.307 | 3GPP TR 38.307 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.401 | 3GPP TR 38.401 |
| TS 38.423 | 3GPP TR 38.423 |
| TS 38.425 | 3GPP TR 38.425 |
| TS 38.463 | 3GPP TR 38.463 |
| TS 38.473 | 3GPP TR 38.473 |
| TS 38.508 | 3GPP TR 38.508 |
| TS 38.521 | 3GPP TR 38.521 |
| TS 38.522 | 3GPP TR 38.522 |
| TS 38.523 | 3GPP TR 38.523 |
| TS 38.755 | 3GPP TR 38.755 |
| TS 38.793 | 3GPP TR 38.793 |
| TS 38.839 | 3GPP TR 38.839 |
| TS 38.846 | 3GPP TR 38.846 |
| TS 38.881 | 3GPP TR 38.881 |
| TS 38.894 | 3GPP TR 38.894 |