Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

NGEN-DC

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

Radio Access Network →

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.

Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
11 specs
Also in
User Equipment, Management
NGEN-DC Description Purpose What changed Family Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define NGEN-DC. Each summary describes the whole specification, not only this term.

TS 28.552Rel-18 → Rel-19

Rel-19 added 5G performance measurements for LTM mobility and NEF analytics, NWDAF data collection/efficiency metrics, NTN paging load distribution, and UE measurement relaxation reporting for energy efficiency.

Full comparison in TS 28.552 →
TS 28.657Rel-15 → Rel-16

Rel-16 brings only minor changes to TS 28.657: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 28.657 →

Technology family

Carrier aggregation and dual connectivity · Radio Access Network

  1. Rel-12 MCG bearer, SCG bearer, Split bearer
  2. Rel-15 CA duplication, DC duplication, EN-DC, MR-DC, NE-DC, NGEN-DC, NR-DC, Split SRB, Supplementary Uplink (SUL)

Also in this family (introduction release not pinned to a single defining specification): Dynamic Spectrum Sharing (DSS)

  • NGEN-DC builds on MR-DC
    “Network side protocol termination options are shown in Figure 4.2.2-3 for MR-DC with EPC (EN-DC) and in Figure 4.2.2-4 for MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC).” TS 37.340
  • NGEN-DC coexists with EN-DC
    “Figure 4.2.2-4: Network side protocol termination options for MCG, SCG and split bearers in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC).” TS 37.340
  • NGEN-DC coexists with NE-DC (not stated verbatim in the specifications)

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 sources

Documented changes in 5 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.

Rel-15 introduced

NGEN-DC is specified for the first time in Rel-15, with an ng-eNB as master node and a gNB as secondary node connected to 5GC, including bearer, SRB3 and protocol architecture.

  • “NG-RAN supports NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), in which a UE is connected to one ng-eNB that acts as a MN and one gNB that acts as a SN.” TS 37.340 v15.16.0
  • “In MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC), the involved core network entity is the AMF.” TS 37.340 v15.16.0
  • Introduction of late drop NGEN-DC, NE-DC and NR-DC TS 38.331CR0916
Rel-16 specification text

Rel-16 adds NGEN-DC-specific behaviour: CA duplication only for SCG bearer, CLI measurements configured only by the SN, CSI-RS based SN change supported, and conditional PSCell change not supported.

  • “In NGEN-DC, CA duplication can only be configured for SCG bearer.” TS 37.340 v16.13.0
  • “In NGEN-DC and NR-DC, CSI-RS based SN change between neighbour gNBs is supported” TS 37.340 v16.13.0
  • “Conditional PSCell Change is not supported for the MR-DC options NE-DC and NGEN-DC.” TS 37.340 v16.13.0
Rel-17 specification text

Rel-17 adds NGEN-DC-specific behaviour: RLM/BFD relaxation criteria configured in the NR PSCell, conditional PSCell addition not supported, and FR2 UL gap configuration decided by the SN.

  • “in the NR PSCell for the case of EN-DC, NGEN-DC and NR-DC.” TS 37.340 v17.8.0
  • “Conditional PSCell Change and conditional PSCell addition are not supported for the MR-DC options NE-DC and NGEN-DC.” TS 37.340 v17.8.0
  • “In EN-DC and NGEN-DC, the SN decides and configures the FR2 UL gap pattern.” TS 38.331 v17.18.0
Rel-18 specification text

Rel-18 adds NGEN-DC-specific behaviour: NR RA Report forwarding via Xn between ng-eNBs, and a statement that CHO with candidate SCG(s) is not supported in NGEN-DC.

  • “In case of NGEN-DC, in case there is no Xn connectivity between the ng-eNB retrieving the NR RA Report from the UE” TS 37.340 v18.7.0
  • “CHO with candidate SCG(s) is not supported for NE-DC and NGEN-DC.” TS 37.340 v18.7.0
  • “SRB5 is supported in NR-DC, but not in EN-DC, NGEN-DC and NE-DC.” TS 37.340 v18.7.0
Rel-19 specification text

In MR-DC including NGEN-DC, a UE supporting LP-WUS can be configured to monitor LP-WUS on the PSCell when the SN is a gNB, a feature not in OLD, which covers only DCP.

  • “the UE supporting LP-WUS can be configured with LP-WUS to be monitored on the PCell” TS 37.340 v19.3.0
  • “with LP-WUS to be monitored on the PSCell, if the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC)” TS 37.340 v19.3.0

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 vk40 5G Network Performance Measurements Rel-20 read
TS 28.657 vk00 E-UTRAN and ng-eNB NRM Requirements Rel-20 read
TS 32.425 vj00 E-UTRAN Performance Measurements Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 37.340 vj30 Overview of Multi-Connectivity Operation using E-UTRA and NR Rel-19 read
TS 37.473 vj00 W1 Application Protocol (W1AP) Specification Rel-19 read
TS 37.571 vj00 UE Conformance for Positioning Rel-19 read
TS 38.133 vk10 NR Radio Resource Management Requirements Rel-20 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TS 38.508 vj31 5G NR UE ICS Proforma Rel-19 read
TS 38.521 vj10 UE Conformance Spec for NR Satellite Access Rel-19 read