Description
Intra-band non-contiguous dual connectivity (DC) is a multi-connectivity feature in which a UE maintains simultaneous connections to two NG-RAN nodes (or two distinct cells) using carriers that belong to the same operating band but are not adjacent in frequency. Unlike intra-band contiguous DC, where the two component carriers form a single continuous block, non-contiguous operation requires the UE to support two separate RF chains tuned to different portions of the same band, with a frequency gap between them. This gap may be occupied by other operators' spectrum, by legacy systems, or simply be unused.
Architecturally, the feature builds on the dual connectivity framework defined for NR: a Master Node (MN) and a Secondary Node (SN) each provide one of the carriers, connected via the Xn interface. The MN terminates the RRC connection and handles mobility, while the SN provides additional user-plane capacity. In the intra-band non-contiguous case, both nodes operate in the same band, which simplifies some aspects of RF coexistence and antenna sharing but complicates UE implementation because two independent local oscillators or a wideband synthesizer with sufficient linearity are needed. The UE reports its capability to support specific non-contiguous carrier combinations, and the network configures the secondary cell group (SCG) only if the combination is signalled as supported.
From the physical layer perspective, the two carriers can use different numerologies, bandwidths, and even different duplex arrangements within the band (subject to band-specific rules). Each carrier performs its own link adaptation, HARQ, and scheduling. The MAC layer in each cell group operates independently, and PDCP duplication or split bearers can be used to improve reliability. Because the carriers are non-adjacent, inter-carrier interference and spectral leakage are less of a concern than in contiguous aggregation, but receiver blocking and in-device coexistence (IDC) with other radios (e.g., Wi-Fi, GNSS) become more significant design constraints.
The feature was studied and specified in 3GPP Release 17 through the RF and performance specifications 37.717, 37.718, and 37.719, which define the band combinations, RF requirements, and UE conformance test cases. These documents specify the allowed gaps between carriers, the maximum supported bandwidth per carrier, and the coexistence requirements with other systems. Operators benefit because they can combine fragmented spectrum holdings within a single band—common in markets where spectrum was auctioned in non-contiguous blocks—without waiting for refarming or new band acquisitions.
In the network, intra-band non-contiguous DC is configured by the RAN based on UE capability, traffic demand, and radio conditions. It is particularly useful in dense urban deployments where a single band has been split into multiple blocks and where high throughput is needed at the cell edge. The feature complements other DC variants such as inter-band DC and intra-band contiguous DC, giving operators a fuller toolbox for spectrum aggregation.
Purpose & Motivation
Operators frequently hold spectrum in a given band as multiple non-adjacent blocks, either because of how auctions were structured or because parts of the band are occupied by legacy systems. Before Release 17, dual connectivity and carrier aggregation combinations were largely limited to contiguous intra-band or inter-band scenarios, leaving fragmented intra-band holdings underutilized. Intra-band non-contiguous DC exists to unlock that fragmented spectrum, allowing a single UE to aggregate two separated carriers in the same band and thereby increase peak throughput and robustness without requiring new spectrum or refarming.
The feature also addresses the practical constraint that contiguous aggregation requires a single wideband RF chain, which increases UE cost and power consumption. By allowing non-contiguous operation, the standard gives vendors flexibility to implement dual RF chains that can be tuned independently, potentially reusing components across band combinations. This is especially valuable for mid-band spectrum (e.g., 3.5 GHz) where regulators often assign non-contiguous blocks.
Finally, the feature improves mobility and reliability: because both carriers are in the same band, they tend to have similar propagation characteristics, so the network can use the secondary carrier to boost throughput while the primary carrier maintains coverage. This makes it attractive for cell-edge users and for services that require consistent user experience.
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.
Initial specification of intra-band non-contiguous dual connectivity, including RF requirements, band combinations, and UE conformance tests in 37.717, 37.718, and 37.719. The definition establishes the concept of aggregating non-contiguous carriers of dual connectivity in the same operating band.
Defining Specifications
3GPP specifications that define or reference Intra-band non-contiguous dual connectivity, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 37.717 | 3GPP TR 37.717 | Rel-17 read |
| TS 37.718 | 3GPP TR 37.718 | Rel-17 read |
| TS 37.719 vj00 | Rel-19 Dual Connectivity Band Combinations | Rel-19 read |