Glossary term · Core Network

SMCC

Session Management Congestion Control

Core Network →

SMCC is a set of network mechanisms designed to prevent, detect, and mitigate congestion in the control plane procedures for PDU session management to protect the SMF and signaling interfaces from overload.

Introduced
Rel-17
Specifications
2 specs
Category
Core Network
Introduced
Rel-17
Specifications
2 specs
SMCC Description Purpose Detected Changes Specifications

Description

Session Management Congestion Control (SMCC) is a sophisticated framework introduced in 5G to safeguard the core network's control plane, particularly the Session Management Function (SMF), from congestion and overload. Unlike user plane congestion, SMCC focuses on the signaling storm that can occur when a massive number of UEs simultaneously attempt to establish, modify, or release PDU sessions. This congestion can be triggered by legitimate events (e.g., a stadium filling up) or malicious attacks (e.g., a Distributed Denial-of-Service attack targeting the N11/N7 interfaces). The SMCC architecture involves coordinated actions between the SMF, the Access and Mobility Management Function (AMF), and the Policy Control Function (PCF).

SMCC operates through a multi-stage process of monitoring, decision, and action. The SMF continuously monitors key performance indicators (KPIs) such as the rate of incoming session management requests, processing latency, and CPU/memory utilization. When predefined thresholds are crossed, the SMF enters a congestion state. It then applies congestion control policies, which are often pre-configured or dynamically provided by the PCF. A primary action is for the SMF to signal congestion information to the AMF using the N11 interface. The AMF, acting as a signaling aggregator from many UEs, can then apply back-pressure. This involves rejecting new session management requests from UEs with a wait timer or redirecting them, effectively throttling the load at the source.

The mechanisms within SMCC are granular. They can differentiate between types of session management procedures (e.g., prioritizing session establishment for emergency services over regular browsing) and can apply controls based on UE subscription, network slice (S-NSSAI), or Data Network Name (DNN). For instance, during congestion, the SMF might reject requests for a non-critical IoT slice while continuing to accept requests from a slice supporting public safety. The SMF may also implement local queuing and prioritization algorithms. By proactively managing the signaling load, SMCC ensures that the SMF remains responsive for essential sessions and that congestion does not cascade to cause a wider network control plane failure, thereby maintaining overall network stability and service availability.

Purpose & Motivation

SMCC was created to address a critical vulnerability in 5G and future networks: control plane signaling overload. Previous generations had congestion control, but 5G's service-based architecture, network slicing, and support for massive IoT exponentially increase the scale and complexity of session management signaling. A single SMF instance could be responsible for millions of sessions. Without SMCC, a surge in signaling—whether from a legitimate mass event or a coordinated attack—could overwhelm the SMF, leading to service denial for all users, including those with high-priority services.

The technology solves the problem of ensuring service reliability and fairness in a hyper-connected environment. It allows the network to gracefully degrade under load rather than catastrophically fail. The motivation for its standardization in Release 17 stemmed from operator experiences and the foresight that as networks become more software-defined and sliced, a standardized, interoperable approach to session management congestion was necessary. SMCC provides the tools to implement "smart" congestion control that can distinguish between different services and slices, which is a fundamental requirement for delivering on 5G's promises of guaranteed service level agreements (SLAs) for diverse use cases, from enhanced mobile broadband to ultra-reliable low-latency communications.

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-17 1 change
  • Correction of SMCC and other abbreviations TS 29.508CR0165

Explore further

Broader topics and technologies where SMCC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 29.508 vk00 Session Management Event Exposure Service Rel-20
TS 29.520 vk00 5G Network Data Analytics Function Services Rel-20