Dual Connectivity

Description

Dual Connectivity (DC) is a fundamental radio resource management feature in 3GPP standards that allows a single User Equipment (UE) to maintain concurrent connections with two distinct network nodes, referred to as a Master Node (MN) and a Secondary Node (SN). These nodes can belong to the same or different radio access technologies (RATs), such as LTE (E-UTRA) and NR (New Radio). The UE is configured with two separate protocol stacks, one for each node, enabling the simultaneous transmission and reception of data over both radio links. The MN provides the control plane connection to the core network (e.g., via S1-MME or NG-C) and manages the overall UE context, including the establishment, modification, and release of the secondary connection. The SN provides additional radio resources for the user plane, boosting capacity. Data can be split at various protocol layers (e.g., PDCP, RLC) depending on the DC architecture variant (e.g., MCG bearer, SCG bearer, split bearer).

The architecture is defined by the roles of the involved nodes. In LTE DC (introduced as LTE-NR Dual Connectivity or EN-DC), the eNB typically acts as the MN (MeNB), and a gNB acts as the SN (SgNB). In 5G NR DC (NR-NR DC or NE-DC), the roles are defined as MN (e.g., a gNB) and SN (another gNB). The nodes are interconnected via standardized interfaces: the X2 interface for LTE-based nodes and the Xn interface for NR-based nodes. These interfaces carry control plane signaling (e.g., SN Addition/Modification/Release procedures) and user plane data for bearers terminated at the SN. The UE maintains two Cell Groups: the Master Cell Group (MCG) associated with the MN and the Secondary Cell Group (SCG) associated with the SN. Each group comprises a Primary Cell (PCell or PSCell) and optionally one or more Secondary Cells (SCells).

Operationally, DC involves complex coordination. The MN makes the decision to add an SN based on measurement reports from the UE and its own load conditions. It initiates the SN addition procedure via the X2/Xn interface, transferring necessary UE context. The SN then performs its own admission control and, if successful, configures resources for the UE. The MN provides the final configuration to the UE via RRC signaling, which may include a secondary RRC configuration from the SN (in the case of NR DC). For user plane, data can be routed in different ways. In a split bearer configuration, the PDCP layer at the MN handles packet duplication, sequencing, and can route packets to either its own RLC layer (for the MCG leg) or to the SN's RLC layer (for the SCG leg) via the X2/Xn-U interface. This requires tight synchronization and flow control between the nodes to minimize packet reordering delays at the receiver.

DC's role in the network is multi-faceted. Primarily, it is a capacity-boosting tool, aggregating spectrum and radio resources from two transmission points to achieve peak data rates beyond what a single node can provide. It is also a critical mobility enhancement; by keeping an anchor connection (the MCG) stable, it allows for smoother handovers of the SCG, reducing the risk of radio link failure during inter-cell mobility. Furthermore, it enables efficient load balancing between different network layers (e.g., macro and small cells) or different frequency bands. In 5G, DC is the foundation for more advanced multi-connectivity schemes and is essential for leveraging non-standalone (NSA) architectures where the LTE anchor provides robust coverage and control, while the NR link delivers high throughput.

Purpose & Motivation

Dual Connectivity was created to address the growing demand for higher user data rates and more robust mobile experiences, which could not be met by a single connection to one network cell. Prior to DC, Carrier Aggregation (CA) allowed a UE to aggregate component carriers from a single base station, but this was limited by the geographical coverage and capacity of that one node. DC overcomes this limitation by allowing aggregation across geographically separated nodes, effectively pooling the resources of a macro cell and a small cell. This was particularly important for heterogeneous network (HetNet) deployments, where small cells are deployed to boost capacity in hotspots but require a stable macro cell layer for control and coverage.

Historically, the concept evolved from earlier multi-point coordination techniques. Its formal introduction in 3GPP Release 12 (for LTE-LTE DC) was driven by the need for improved per-user throughput and mobility performance in dense networks. A key problem it solved was the 'ping-pong' effect in small cell deployments, where frequent handovers could degrade performance. By anchoring the control plane at the macro cell (MN) and adding a small cell as an SN for data, DC provided a stable connection while dynamically adding and removing capacity. This also improved network energy efficiency by allowing the SN to be activated only when needed for high data traffic.

The motivation intensified with the advent of 5G. The initial 5G deployments used the Non-Standalone (NSA) architecture, which relied fundamentally on LTE-NR Dual Connectivity (EN-DC) to provide a 5G data pipe (via the NR gNB as SN) while maintaining the LTE eNB as the control anchor. This allowed for rapid 5G service rollout using existing LTE core networks. Furthermore, as 5G networks evolved to standalone (SA) mode, NR-NR DC (and later multi-RAT DC) became essential for aggregating diverse NR frequency ranges (e.g., FR1 and FR2/mmWave) to combine coverage and capacity, ensuring consistent high performance even when one link (like mmWave) is susceptible to blockages.

Key Features

• Simultaneous connectivity to a Master Node and a Secondary Node
• User plane aggregation for increased peak data rates
• Control plane anchoring at the Master Node for robustness
• Support for multiple RAT combinations (e.g., LTE-LTE, LTE-NR, NR-NR)
• Flexible bearer types (MCG, SCG, and Split Bearer) for data routing optimization
• Enhanced mobility and load balancing across network layers

Evolution Across Releases

Defining Specifications