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

Glossary term · Core Network

SCM

Single-Connection Mode

Core Network →

SCM is an operational mode where a UE maintains a single, simultaneous PDN connection to either a 3GPP or non-3GPP network for fundamental network-based mobility management.

Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
12 specs
Also in
Radio Access Network, Testing
SCM Description Purpose What changed Neighbours Detected Changes Specifications

Description

Single-Connection Mode (SCM) is a core concept in 3GPP network-based mobility management, formally defined in TS 23.402 for the System Architecture Evolution (SAE). It describes the state of a User Equipment (UE) when it is simultaneously connected to the core network via exactly one access network. This single connection is the active point of attachment for the UE's IP traffic. In the context of Evolved Packet Core (EPC), this typically means the UE has one active PDN connection established through a single Packet Data Network Gateway (PGW). The access network for this connection can be a 3GPP access like E-UTRAN, UTRAN, or GERAN, or a trusted/untrusted non-3GPP access like Wi-Fi.

The technical operation of SCM is governed by the mobility management protocols. For a UE in SCM, all of its IP traffic flows over this single bearer path. The mobility management entity (e.g., MME for 3GPP, ePDG for untrusted non-3GPP) tracks the UE's location and manages the handover procedures for this sole connection. The UE's IP address(es) are anchored at the single PGW serving this PDN connection. Key procedures like Attach, PDN Connectivity, and Bearer Management are executed with the understanding that the UE is in this singular connectivity state. The network's policy and charging rules (PCRF) are applied to this single data path.

SCM is often discussed in contrast to Multi-Access PDN Connectivity (MAPCON) or IP Flow Mobility (IFOM), where a UE can maintain multiple simultaneous PDN connections over different accesses. In SCM, the network handles mobility events (e.g., handover from LTE to Wi-Fi) by transferring the entire PDN connection and its associated bearers from one access to another, potentially involving an inter-access handover procedure. The concept is foundational for understanding how a UE registers, connects, and is managed in its most basic and common operational state within EPS and 5GS architectures, where simplicity and single-path routing are required.

Purpose & Motivation

SCM was defined to establish a clear and fundamental baseline for UE connectivity behavior within the new, access-agnostic Evolved Packet System (EPS) introduced in 3GPP Rel-8. Prior to EPS, connectivity was more siloed (e.g., GPRS attach for 2G/3G). EPS aimed to provide seamless mobility and service continuity across heterogeneous access technologies (LTE, 3G, 2G, Wi-Fi) under a unified core. A formal definition of the state where a UE uses only one of these accesses at a time was necessary for specifying standard procedures.

It solves the problem of ambiguity in mobility management specifications. By defining SCM as the default and simplest mode, 3GPP could precisely specify attach, detach, handover, and bearer management procedures for this case. This created a stable reference model. More advanced features like simultaneous multi-access connectivity (e.g., MAPCON) were then defined as extensions to or deviations from this baseline SCM behavior. The concept is crucial for network implementations to correctly handle resource allocation, routing, charging, and policy enforcement for the vast majority of UEs that are not using advanced multi-connectivity features, ensuring predictable and efficient network operation.

What changed in its specifications

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

TS 24.302Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 24.302: 7 clauses changed, with no change attributed to a release feature.

Full comparison in TS 24.302 →
TR 25.996Rel-6 → Rel-7

Rel-7 brings only minor changes to TS 25.996: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 25.996 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change
  • Corrections of errors in emergency PDU session establishment by UE without valid UICC using SCM in TWAN TS 24.302CR0659

Defining Specifications

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

SpecificationTitleRelease
TS 23.161 vj00 Network-based IP Flow Mobility (NBIFOM) Rel-19 read
TS 23.861 vd00 Network-Based IP Flow Mobility (NBIFOM) Rel-13 read
TS 24.161 vj00 Network-Based IP Flow Mobility (NBIFOM) Rel-19 read
TS 24.302 vj00 Access to EPC via non-3GPP networks; Stage 3 Rel-19 read
TR 25.996 vj00 3GPP-3GPP2 Spatial Channel Model Specification Rel-19 read
TR 26.955 vj00 Video Codec Analysis for 5G Services Rel-19 read
TS 29.826 vd10 P-CSCF Restoration Enhancements for WLAN Rel-13 read
TS 36.840 vc10 LTE 450 MHz Band Technical Requirements for Brazil Rel-12 read
TR 37.976 vj00 MIMO OTA Test Methodology Study Rel-19 read
TR 37.977 vj00 MIMO OTA Test Methodology Rel-19 read
TR 38.900 vf00 Channel Model Study for >6 GHz Rel-15 read
TS 38.901 vj50 5G NR Channel Model Rel-19 read