Description
Multi-Connectivity (MC) is a mode of operation in which a multiple Rx/Tx UE in connected mode is configured to utilize radio resources among E-UTRA and/or NR provided by multiple distinct schedulers connected via non-ideal backhaul. The key architectural element is the presence of multiple distinct schedulers — typically located in different network nodes such as a master node and one or more secondary nodes — each independently managing its own radio resources. Because the schedulers are connected via non-ideal backhaul, coordination between them is subject to latency and capacity constraints, which distinguishes MC from tighter intra-node aggregation schemes.
In the NR and E-UTRA architecture described in 36.300 and 38.804, MC is realized through the dual connectivity and multi-radio dual connectivity (MR-DC) framework. A UE maintains connections to a Master Node (MN) and one or more Secondary Nodes (SN). The MN anchors the control plane toward the core network, while the SN provides additional user-plane capacity. Depending on the configuration, bearers may be split across nodes (split bearers), duplicated for reliability (packet duplication), or served independently by each node. The UE's multiple receivers and transmitters allow simultaneous reception and transmission on multiple links, which may operate on different frequencies, different radio access technologies, or both.
MC encompasses several specific configurations. NR-NR dual connectivity allows a UE to connect to two NR nodes, improving throughput and robustness in dense deployments. MR-DC covers EN-DC (E-UTRA-NR dual connectivity), NE-DC, NGEN-DC, and NR-DC variants, each differing in which node connects to which core network and which node provides the control plane. Beyond dual connectivity, the concept generalizes to multi-connectivity with more than two nodes, where a UE may aggregate resources from three or more schedulers. The common thread is that each scheduler independently allocates resources, and the UE combines them according to its capabilities.
The benefits of MC are substantial. Throughput is increased by aggregating bandwidth across nodes and bands. Reliability is improved through redundancy — for example, packet duplication over multiple links for ultra-reliable low-latency communication (URLLC). Mobility robustness is enhanced because a UE can maintain a connection to a secondary node while moving, reducing the risk of radio link failure during handover. Load balancing across nodes is also possible, as the network can steer traffic to less loaded schedulers. These benefits come at the cost of increased signaling, UE complexity, and backhaul coordination requirements.
MC relies on a set of procedures defined in 36.300 and 38.804: secondary node addition, modification, and release; bearer type change between MC and single connectivity; and measurement configuration to support node selection. The UE reports its multi-connectivity capabilities, including supported band combinations and the maximum number of connections. The network uses these capabilities together with measurements to decide when to add or remove secondary nodes. Because the schedulers are connected via non-ideal backhaul, the procedures are designed to tolerate backhaul latency, with the MN coordinating most control-plane decisions.
The term was introduced in Release 14 and has been carried forward through Release 19 with its definition unchanged. Its stability reflects the maturity of the dual connectivity framework and the continued importance of multi-node resource aggregation in 5G and beyond.
Purpose & Motivation
Multi-Connectivity exists to let a UE aggregate radio resources from multiple distinct schedulers, overcoming the throughput, reliability, and mobility limitations of single-node connectivity. In earlier single-connectivity deployments, a UE was served by one node at a time, so its peak throughput was bounded by that node's resources and its reliability was bounded by the quality of a single radio link. MC addresses these limits by allowing simultaneous use of resources from multiple nodes, even when those nodes are connected via non-ideal backhaul with limited coordination.
The concept was introduced in Release 14 to generalize dual connectivity beyond the original LTE-LTE configuration, enabling aggregation across E-UTRA and NR and across more than two nodes. This was motivated by the need for higher data rates, better mobility robustness in dense small-cell deployments, and support for ultra-reliable services through redundancy. By defining MC in terms of multiple distinct schedulers rather than a specific node count or RAT pairing, 3GPP created a flexible framework that accommodates EN-DC, NR-DC, and future multi-node configurations without redefining the core concept.
What changed in its specifications
The latest release-to-release comparison of specifications that define Multi-Connectivity. Each summary describes the whole specification, not only this term.
Rel-19 added NTN IoT Phase 3 for LTE, covering regenerative payload S1 removal, Msg3 early data transmission, and ETWS/CMAS for NB-IoT NTN. It also added inter-RAT mobility from E-UTRAN terrestrial network to NR NTN, plus NR NTN feeder link switchover via handover.
Full comparison in TS 36.300 →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.
Defining Specifications
3GPP specifications that define or reference Multi-Connectivity, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TR 38.804 ve00 | Study on New Radio Access Technology; Radio Interface Protocol Aspects | Rel-14 read |
| TR 38.912 vj00 | Study on New Radio Access Technology | Rel-19 read |