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

Glossary term · Core Network

DNN based congestion control

Data Network Name based congestion control

Core Network →

DNN based congestion control is a session management level congestion control mechanism that rejects or releases PDU sessions associated with a congested Data Network Name, activated at an SMF or AMF to protect network resources.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
2 specs
DNN based congestion control Description Purpose What changed Neighbours Detected Changes Specifications

Description

DNN based congestion control is a type of congestion control at the session management (SM) level in the 5G core network. It is applied to reject session management requests from UEs or to release PDU sessions when the associated Data Network Name (DNN) is congested. The DNN identifies the data network to which a PDU session connects, such as the Internet or an enterprise network. When a DNN becomes congested, the network can selectively control sessions for that DNN without affecting other DNNs. This mechanism is defined in 3GPP TS 24.501 (Non-Access-Stratum (NAS) protocol for 5G System) and TS 24.890 (5G System Phase 1).

The congestion control can be activated at the Session Management Function (SMF) over the session management level, and also at the Access and Mobility Management Function (AMF) over the mobility management level. When activated at the SMF, the SMF rejects PDU session establishment requests or releases existing PDU sessions for the congested DNN. The SMF may include a back-off timer in the rejection message to instruct the UE to avoid re-attempting for a certain period. When activated at the AMF, the AMF can reject registration requests or service requests that are associated with the congested DNN, or it can indicate congestion to the UE during mobility management procedures. The AMF may also provide a back-off timer.

The mechanism works by the SMF or AMF monitoring the load or resource availability for a specific DNN. When congestion is detected, the network element activates congestion control for that DNN. The UE receives a rejection cause indicating DNN based congestion control, along with a back-off timer. The UE must then refrain from sending new session management requests for that DNN until the timer expires. For existing sessions, the network may release the PDU session with a cause indicating congestion, and the UE may attempt to re-establish after the back-off timer. The back-off timer can be set to a random value within a range to avoid synchronized re-attempts from many UEs.

The DNN based congestion control is part of a broader set of congestion control mechanisms in 5G, including DNN based, S-NSSAI based, and group specific congestion control. It allows the network to manage overload in a granular manner, protecting specific data networks while allowing other traffic to proceed. This is particularly important in networks that host multiple data networks with different QoS requirements and traffic patterns. For example, a massive IoT DNN might experience congestion due to a surge in devices, and the network can apply DNN based congestion control to protect the core network while allowing enhanced mobile broadband users on other DNNs to continue unaffected.

The parameter has been defined since Release 15 and its definition has remained essentially unchanged through Release 20. The only notable variation is in Release 19, where the definition text includes line breaks but the content is identical. This indicates that the mechanism has been stable and widely implemented in 5G networks. The DNN based congestion control is a key tool for network operators to maintain service quality and prevent overload in the 5G core.

Purpose & Motivation

DNN based congestion control exists to provide a targeted overload control mechanism in the 5G core network. In earlier generations, congestion control was often applied at a coarse level, such as entire access point names (APNs) or global level, which could unnecessarily affect users of non-congested services. With the introduction of 5G and network slicing, the need for finer granularity became apparent. DNN based congestion control allows the network to protect a specific data network without impacting others, improving overall user experience and network efficiency.

The motivation for introducing this in Release 15 was to support the diverse service requirements of 5G, including enhanced mobile broadband, massive machine type communication, and ultra-reliable low latency communication. Each of these services may use different DNNs, and congestion in one DNN should not degrade the others. By activating congestion control per DNN, the network can isolate the congested data network and apply back-off timers only to the affected UEs. This prevents a congested DNN from consuming excessive core network resources and ensures that other DNNs continue to operate normally.

The mechanism also addresses the limitations of previous congestion control methods that were based on APN but lacked the flexibility to be activated at both SMF and AMF. The dual activation points allow the network to respond to congestion at different levels: the SMF can control session management signaling, while the AMF can control mobility management signaling. This layered approach provides comprehensive protection against overload. The inclusion of back-off timers helps to avoid signaling storms and ensures that UEs retry after a randomized delay, which is essential for maintaining stability during congestion.

What changed in its specifications

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

TS 24.501Rel-18 → Rel-19

Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.

Full comparison in TS 24.501 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-15, normative work from Rel-16.

Rel-16 2 changes
  • Correction on LADN DNN based congestion control TS 24.501CR2216
  • DNN based congestion control for PDU session for LADN TS 24.501CR1195

Defining Specifications

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

SpecificationTitleRelease
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 Rel-16 read