Description
Multi-Connection Mode (MCM) is a network architecture and operational mode specified by 3GPP, primarily in the context of core network evolution towards seamless integration of multiple access technologies. Defined in TS 23.402, it allows user equipment (UE) to establish and maintain concurrent connections to different access networks, such as 3GPP networks (e.g., LTE, 5G NR) and non-3GPP networks (e.g., Wi-Fi, fixed broadband). MCM enables the network to manage these connections collectively, providing functionalities like traffic steering, aggregation, and mobility support without service interruption. It is a key enabler for heterogeneous network (HetNet) deployments and enhanced user experience.
Architecturally, MCM involves core network functions like the Access Network Discovery and Selection Function (ANDSF) for policy-based access selection, the Packet Data Network Gateway (PGW) in EPC or User Plane Function (UPF) in 5GC for anchoring user plane connections, and the Non-3GPP Interworking Function (N3IWF) for secure integration of non-3GPP accesses. The mode works by allowing the UE to register with multiple access points simultaneously, with the core network coordinating session management and data flow across these paths. Key components include dual-stack IP capabilities, authentication mechanisms for non-3GPP networks, and interfaces like S2a/b/c in EPC or N3 in 5GC.
In operation, MCM supports scenarios where a UE might use LTE for voice services and Wi-Fi for high-speed data downloads concurrently, with the network dynamically routing traffic based on policies, link quality, or user preferences. The core network maintains a unified context for the UE, enabling seamless handovers and session continuity when moving between accesses. MCM's role extends to enabling advanced services like LTE-WLAN aggregation (LWA) or 5G multi-access edge computing (MEC), where low latency and high bandwidth are achieved by leveraging multiple connections. It is foundational for realizing the 3GPP vision of converged access in evolved packet core and 5G system architectures.
Purpose & Motivation
MCM was introduced to address the growing heterogeneity of access networks and the need for seamless integration between 3GPP and non-3GPP technologies, such as Wi-Fi. Prior to its standardization, UEs typically operated in single-connection modes, switching between networks with interruptions, which limited the potential for traffic aggregation and always-best-connected experiences. MCM provides a standardized framework for concurrent multi-access operation, solving problems like inefficient resource utilization and poor mobility performance in mixed environments.
Historically, as mobile data demand surged with the proliferation of smartphones, operators sought to offload traffic to Wi-Fi and other complementary accesses, but lacked cohesive management capabilities. MCM, defined from 3GPP Release 12 onwards, was motivated by the desire to enhance core network architectures (e.g., EPC and later 5GC) for better access agnosticism. It enables operators to leverage multiple radios for improved capacity, coverage, and user satisfaction, particularly in dense urban areas or indoor settings.
The creation of MCM also supports the evolution towards 5G and network slicing, where flexible access selection is crucial for diverse service requirements. By allowing simultaneous connections, it facilitates innovations like multi-path TCP and edge computing, addressing limitations of previous single-path approaches. This has become increasingly important with the Internet of Things (IoT) and ultra-reliable low-latency communications (URLLC), where redundant connections can enhance reliability.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (6 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-12, normative work from Rel-15.
In Release 15, the MCM (Multi-Connection Mode) function was introduced to support NBIFOM (Network-Based IP Flow Mobility), enabling a PDN connection to be simultaneously established over both 3GPP and WLAN accesses via S2a or S2b interfaces. This allows for individual IP flows to be routed over either access based on exchanged Routing Rules, operating in either UE-initiated or Network-initiated NBIFOM modes. The release also defined the capability discovery and negotiation procedures between the UE and the network to determine NBIFOM support on a per-PDN connection basis.
In Release 16, enhancements were made to Multi-Connection Mode (MCM) for NBIFOM, specifically addressing UE handling when the network signals the error MAX_CONNECTION_REACHED and clarifying the applicability of the maximum PDN connection limit. Additionally, a gap was identified where the handover of an Ethernet PDN connection to an ePDG was not supported within the S2a/S2b framework for multi-access connections.
Explore further
Broader topics and technologies where MCM plays a role.
Defining Specifications
3GPP specifications that define or reference MCM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.161 vj00 | Network-based IP Flow Mobility (NBIFOM) | Rel-19 |
| TS 23.861 vd00 | Network-Based IP Flow Mobility (NBIFOM) | Rel-13 |
| TS 24.161 vj00 | Network-Based IP Flow Mobility (NBIFOM) | Rel-19 |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 |
| TS 29.826 vd10 | P-CSCF Restoration Enhancements for WLAN | Rel-13 |