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

Glossary term · Radio Access Network

NR-DC

NR-NR Dual Connectivity

Radio Access Network →

NR-DC is a 5G feature where a device connects simultaneously to two NR cell groups via different bands to aggregate their radio resources for higher data rates, reliability, and mobility.

Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
10 specs
Also in
Security, User Equipment
NR-DC Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

NR-NR Dual Connectivity (NR-DC) is an advanced multi-connectivity scheme in 5G where a user equipment (UE) is concurrently connected to two distinct NR cell groups: a Master Node (MN) and a Secondary Node (SN). These nodes can be gNBs (Next Generation NodeBs) operating in different frequency bands (e.g., mid-band and mmWave), and they are coordinated to serve the UE simultaneously. The architecture involves split bearer configurations where data radio bearers (DRBs) can be terminated at either the MN or SN, or split across both using the Packet Data Convergence Protocol (PDCP) duplication or splitting. The MN manages the control plane connection via Radio Resource Control (RRC), while the SN provides additional user plane resources, with coordination over the Xn interface between the nodes.

How NR-DC works involves several key procedures. During setup, the MN decides to add an SN based on measurement reports from the UE, triggering an SN Addition procedure via Xn signaling. The UE then establishes a secondary cell group (SCG) with the SN, configuring secondary cells (SCells) for data transmission. Data flow can be managed through MCG (Master Cell Group) bearers, SCG bearers, or split bearers, depending on the deployment. For split bearers, the PDCP layer at the MN or SN handles packet duplication or distribution to the RLC layers in both nodes, enhancing throughput and reliability. Synchronization and coordination between MN and SN are critical to avoid interference and ensure seamless handovers, with mechanisms like power control and scheduling coordination.

NR-DC's role in the network is to maximize resource utilization and service quality. It enables higher peak data rates by aggregating bandwidth from multiple carriers, often across different bands, which is especially useful in 5G where spectrum is fragmented. It improves reliability through packet duplication, meeting URLLC requirements for critical applications. Additionally, NR-DC enhances mobility by allowing the UE to maintain connectivity with one node while transitioning to another, reducing interruption times. This is vital in dense or heterogeneous networks with mixed macro and small cell deployments, ensuring consistent performance as users move.

Purpose & Motivation

NR-DC was developed to address the challenges of achieving ultra-high data rates, reliable connectivity, and efficient spectrum use in 5G networks. Previous technologies like LTE-NR Dual Connectivity (EN-DC) allowed aggregation between 4G and 5G but were limited by LTE's capabilities. As networks evolved to standalone 5G, there was a need for a native NR solution to fully exploit 5G's advanced features across multiple frequency bands. The purpose of NR-DC is to enable operators to leverage their diverse spectrum portfolios (e.g., combining low-band for coverage with high-band for capacity) without being constrained by legacy systems.

Historically, dual connectivity was introduced in LTE-Advanced to aggregate resources from multiple base stations, but it was primarily intra-LTE. With 5G's broader spectrum range and new use cases, NR-DC solves problems like fragmented spectrum utilization by allowing simultaneous use of non-contiguous bands. It also addresses mobility issues in dense networks by providing anchor points for seamless handovers. The motivation stems from the demand for enhanced mobile broadband (eMBB) and ultra-reliable communications, where single-node connectivity may be insufficient. NR-DC facilitates network densification and carrier aggregation in a pure 5G environment, driving performance improvements and supporting innovative services like augmented reality and industrial automation.

What changed in its specifications

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

TS 33.501Rel-18 → Rel-19

Rel-19 TS 33.501 adds roaming and inter-PLMN indirect communication authorization, fast re-authentication for non-3GPP mobility, and AI/ML security clauses for positioning and federated learning. It also adds NPN security, NRF access token key retrieval, LTM security, and monitoring-of-signalling-traffic protection.

Full comparison in TS 33.501 →
TS 37.340Rel-18 → Rel-19

Rel-19 adds to TS 37.340 data collection for SON/MDT in NR standalone and MR-DC Phase 4. It covers conditional PSCell addition or change (CPAC/S-CPAC) failure detection and root cause analysis in MN and SN nodes.

Full comparison in TS 37.340 →

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)

  • NR-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
  • NR-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

NR-DC is specified for the first time in Rel-15, with RRC procedures and RAN4 requirements, initially limited to MCG in FR1 and SCG in FR2.

  • “NR-DC in Rel-15 only includes the scenarios where all serving cells in MCG in FR1 and all serving cells in SCG in FR2.” TS 38.133 v15.35.0
  • “NR-DC, if and only if it is configured with mrdc-SecondaryCellGroup set to nr-SCG,” TS 38.331 v15.30.0
  • “3.6.2.4 Number of serving carriers for NR-DC” TS 38.133 v15.35.0
Rel-16 1 CR

Rel-16 extends NR-DC beyond Rel-15: it adds synchronous/asynchronous NR-DC operation, per-CG SCell activation and deactivation requirements, NR-DC power control, and SRB3 and SCG configuration changes.

  • “where the requriements for Sync apply for synchronous NR-DC, and for asynchronous NR-DC if the active serving cell is in the same CG” TS 38.133 v16.29.0
  • “The value async means that the UE only indicates NR-DC support for band combinations for which it supports asynchronous NR-DC” TS 38.331 v16.22.0
  • Introduction of NR-DC in same Frequency Range and of Cross-carrier Scheduling with Different Numerologies TS 38.213CR0077
Rel-17 specification text

Rel-17 adds NR-DC requirements and signalling: handover with PSCell from NR-DC to NR-DC interruption requirements, MN/SN-initiated inter-SN CPC in NR-DC, and NR-DC RF test coverage.

  • “When handover with PSCell from NR-DC to NR-DC is commanded, the interruption time shall be less than Tinterrupt” TS 38.133 v17.23.0
  • “the measId is within the SCG VarMeasConfig and is indicated in the condExecutionCondSCG associated to a condReconfigId in the MCG VarConditionalReconfig (for SN-initiated inter-SN CPC in NR-DC)” TS 38.331 v17.18.0
  • “In NR-DC without FR2-FR2 band combination, the network entity which is configured with FR2 serving cell(s) decides and configures the FR2 UL gap pattern.” TS 38.331 v17.18.0
Rel-18 1 CR

Rel-18 extends NR-DC requirements and signalling: handover and conditional handover requirements for FR1-FR1 and FR1-FR2 NR-DC, SRB3 uses and subsequent CPAC in NR-DC, plus new NR-DC performance measurements.

  • “The requirements in this clause are applicable to handover with PSCell from NR-DC to NR-DC.” TS 38.133 v18.15.0
  • “The requirements in this clause are applicable to conditional handover with target SCG from NR-DC to NR-DC.” TS 38.133 v18.15.0
  • New performance measurements for NR-NR Dual Connectivity TS 28.552CR0524
Rel-19 1 CR

NR-DC gained new RRC and performance requirements in Rel-19, including an LTM-ConfigNRDC IE for SCG LTM, enhanced CSSF scaling for NR-DC, and Power Class 1 for inter-band NR-DC uplink.

  • “The IE LTM-ConfigNRDC is used to provide LTM configurations in NR-DC.” TS 38.331 v19.4.0
  • “configured with NR-DC operation and none of SMTC occasions of outside gap measurement objects in one FR are overlapped” TS 38.133 v19.6.0
  • Introduction of Power Class 1 for uplink inter-band CA and NR-DC TS 38.331CR5689

Defining Specifications

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

SpecificationTitleRelease
TS 33.501 vk30 5G Security Architecture Rel-20 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 37.571 vj00 UE Conformance for Positioning Rel-19 read
TS 38.133 vk10 NR Radio Resource Management Requirements Rel-20 read
TS 38.171 vj10 5G A-GNSS UE Positioning Requirements Rel-19 read
TS 38.213 vj50 NR Physical Layer Control Procedures Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TS 38.523 vj40 UE Conformance Specification for 5G NR Rel-19 read
TR 38.846 vi10 Technical Report Rel-18 read