NGEN-DC

E-UTRA NR Dual Connectivity with E-UTRAN connected to 5GC

Radio Access Network →
Introduced in Rel-15 Also in: Management, Testing

NGEN-DC is a dual connectivity mode where a UE connects simultaneously to an LTE eNodeB and a 5G NR gNB, with the LTE node as the master node connected to the 5G Core for migration.

Category
Radio Access Network
Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Also touches
2 segments
Specifications
11 specs
NGEN-DC Description Purpose Related Classification Detected Changes Specifications

Description

NGEN-DC, which stands for E-UTRA NR Dual Connectivity with E-UTRAN connected to 5GC, is a specific dual connectivity (DC) architecture defined by 3GPP. In this configuration, a User Equipment (UE) maintains simultaneous connections with two different radio access nodes: a Master Node (MN) which is an LTE eNodeB (E-UTRA), and a Secondary Node (SN) which is a 5G NR gNB. The critical architectural aspect of NGEN-DC is that the Master eNodeB is connected to the 5G Core Network (5GC) via the NG interface, not the legacy Evolved Packet Core (EPC). This distinguishes it from EN-DC, where the eNodeB connects to the EPC. The LTE node provides the control plane anchor (via the NR RRC connection is conveyed via the LTE node), while both nodes can deliver user plane data to the UE, aggregating radio resources for higher throughput and reliability.

How NGEN-DC works involves sophisticated coordination between the Master eNodeB and the Secondary gNB. The UE initially connects to the LTE network, which is configured to support connectivity to the 5GC (this is known as an LTE anchor in 5GC). When conditions are favorable (e.g., strong NR signal available), the Master eNodeB can initiate the addition of a Secondary gNB for the UE. This process involves signaling between the eNodeB and gNB over the Xn interface (the inter-base station interface in 5G). The Master Node retains control of the UE's Radio Resource Control (RRC) connection and manages the connection to the 5GC's Access and Mobility Management Function (AMF). The Secondary Node provides additional radio resources (a secondary cell group, SCG) for data transmission. Data can be split at the PDCP layer (option 3 or 3a/3x architectures), where the Master Node's PDCP layer handles routing of packets to either its own RLC layer (for transmission over LTE) or to the Secondary Node's RLC layer (for transmission over NR).

Key components of NGEN-DC include the UE supporting both E-UTRA and NR radios, the LTE eNodeB acting as the Master Node (MN), the NR gNB acting as the Secondary Node (SN), and the 5G Core Network. The interfaces involved are the NG interface between the MN and the 5GC, the Xn interface between the MN and SN for coordination, and the Uu radio interface for both LTE and NR. The UE must support the necessary protocol stack, including dual PDCP entities for split bearer operation. The role of NGEN-DC in the network is to provide a crucial migration path for operators deploying 5G. It allows them to introduce 5G NR coverage in hotspots or new spectrum bands while relying on the ubiquitous LTE network for wide-area coverage and control plane reliability. This provides users with an early 5G data rate boost in supported areas while ensuring seamless mobility and service continuity on the LTE layer.

Purpose & Motivation

NGEN-DC was created to facilitate a flexible and efficient migration from 4G LTE networks to full 5G standalone (SA) networks. Before 5G SA, the initial 5G deployments used Non-Standalone (NSA) architecture, specifically EN-DC, where the NR gNB was an add-on to an LTE network connected to the EPC. While EN-DC provided a 5G speed boost, it did not allow access to new 5GC capabilities like network slicing or advanced QoS. NGEN-DC solves this by allowing the LTE network itself to connect to the new 5GC, enabling operators to deploy and trial the 5G core while still using their extensive LTE radio assets as the primary coverage layer.

The problem it addresses is the 'chicken and egg' scenario of 5G deployment: building a nationwide 5G NR coverage layer is time-consuming and expensive. NGEN-DC allows operators to launch 5G services (via the 5GC) much faster by leveraging their existing LTE radio access network (RAN) as the master and coverage layer. It provides a middle ground between pure NSA (EN-DC with EPC) and pure SA (NR connected to 5GC). This enables subscribers to benefit from new 5G core services and potentially higher data rates via NR secondary cells, even in areas where 5G NR coverage is sparse or non-existent.

Historically, it addresses the limitation of EN-DC, which tied 5G radio innovation to the legacy EPC. NGEN-DC decouples this by connecting the LTE RAN to the 5GC, making the LTE network '5GC-aware'. This was a strategic step in 3GPP Release 15, allowing for a more gradual transition where the core network could be modernized independently of achieving full NR coverage. It motivated operators to begin deploying 5GC infrastructure and testing new services without waiting for NR build-out to be complete, thereby accelerating the overall 5G ecosystem development.

Classification

Part ofMR-DC
Related approachesEN-DC

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change

In Release 15, the NGEN-DC (E-UTRA-NR Dual Connectivity with E-UTRAN connected to 5GC) function was newly introduced. This was part of a broader introduction that also included NE-DC and NR-DC, with this specific release incorporating these features as a late drop.

  • Introduction of late drop NGEN-DC, NE-DC and NR-DC TS 38.331CR0916

Explore further

Broader topics and technologies where NGEN-DC plays a role.

Defining Specifications

3GPP specifications that define or reference NGEN-DC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 28.552 vk10 5G Performance Management Measurements Rel-20
TS 28.657 vj00 E-UTRAN NRM IRP Requirements Rel-19
TS 32.425 vj00 E-UTRAN Performance Measurements Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 37.340 vj00 Multi-Connectivity Operation Overview Rel-19
TS 37.473 vj00 W1 Application Protocol (W1AP) Specification Rel-19
TS 37.571 vj00 UE Conformance for Positioning Rel-19
TS 38.133 vj20 5G UE Radio Requirements for RRC_IDLE Mobility Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.508 vj11 5G NR UE Radio Transmission & Reception Rel-19
TS 38.521 vj20 NR Physical Layer UE Conformance Testing Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.