Application specific Congestion control for Data Communication

Description

Application specific Congestion control for Data Communication (ACDC) is a standardized 3GPP feature designed to provide granular, application-aware congestion management at the network access level. Unlike traditional congestion control methods that apply blanket restrictions to all traffic, ACDC operates by categorizing applications into distinct ACDC categories and applying selective access control barring (ACB) mechanisms based on these categories during periods of network congestion. The core principle is to allow the network to prioritize access attempts for critical or operator-designated applications while temporarily restricting or delaying access attempts from less critical applications, thereby alleviating signaling and data plane congestion and preserving service availability for high-priority use cases.

The architecture of ACDC involves coordination between the core network (CN) and the user equipment (UE). The network, specifically the Access and Mobility Management Function (AMF) in 5GC or the Mobility Management Entity (MME) in EPS, is responsible for defining and broadcasting ACDC-specific barring parameters via system information blocks (SIBs). These parameters, defined per ACDC category, include a barring factor and a barring time. The UE, which is provisioned with an ACDC category for each of its applications (typically via the USIM or device management), reads these broadcast parameters. When an application triggers a service request (e.g., for a mobile-originated data session or signaling connection establishment), the UE evaluates the request against the barring parameters for that application's assigned ACDC category. This evaluation involves drawing a random number and comparing it to the broadcast barring factor; if access is barred, the UE enters a timer-based wait state before retrying, effectively throttling access attempts from applications in congested categories.

Key components of the ACDC system include the ACDC category, a numeric identifier (e.g., 1-16) assigned to an application; the network-defined barring parameters for each category; and the UE's ACDC capability and rule enforcement logic. The UE's behavior is specified in protocols such as TS 24.301 (NAS) and TS 36.331 (RRC), ensuring standardized interaction with the radio access network (E-UTRAN, NG-RAN). ACDC does not directly manage data flow or quality of service (QoS) once a session is established; its role is exclusively focused on the initial access control phase. It acts as a preventive, signaling-layer filter to mitigate congestion storms that can be caused by a massive number of UEs simultaneously attempting to access the network for non-urgent services, such as social media updates or background syncs, during events that strain network capacity.

Purpose & Motivation

ACDC was created to address the critical problem of signaling and access congestion in cellular networks, particularly during mass events, emergencies, or network failures. Prior to ACDC, congestion control mechanisms like Access Class Barring (ACB) and Extended Access Barring (EAB) were relatively blunt instruments. ACB could bar entire classes of UEs (e.g., based on subscriber type), and EAB could target UEs configured for low access priority, but neither could distinguish between different *applications* running on the same device. This limitation became acute with the proliferation of smartphones and background applications, where a single UE could generate numerous access attempts for non-essential services, contributing to network overload and potentially blocking access for critical communications like emergency alerts or mission-critical operator services.

The historical context for ACDC's introduction in 3GPP Release 13 was the growing need for smarter, more application-aware network management. Operators required a tool to ensure network resilience and service continuity for high-value applications (e.g., voice, IoT alarm systems, public safety communications) even under extreme load. ACDC solves this by shifting the congestion management paradigm from a device-centric or subscriber-class-centric model to an application-centric model. It allows an operator to define policies that, for instance, permit a banking application or a smart meter reporting service to access the network while temporarily barring a video streaming app during a congestion event. This targeted approach improves overall network efficiency, enhances the user experience for priority services, and provides operators with a powerful policy tool for traffic steering and congestion mitigation, forming a foundational element for service differentiation and network slicing preparations.

Key Features

• Application-aware access control based on configured ACDC categories
• Network-configurable barring parameters (barring factor, barring time) broadcast per ACDC category
• UE-based enforcement where the device applies barring rules per application request
• Backward compatibility and coexistence with legacy barring mechanisms like ACB and EAB
• Support for both EPS and 5GS network architectures
• Provisioning of ACDC categories via USIM (EF_ACDC) or device management

Evolution Across Releases

Defining Specifications