Low Latency, Low Loss, and Scalable Throughput

Description

Low Latency, Low Loss, and Scalable Throughput (L4S) is a Quality of Service (QoS) framework standardized by 3GPP and IETF to enable extremely low queuing delays and near-zero packet loss in IP networks, particularly for 5G and beyond. It operates by modifying the behavior of both endpoints and network nodes to signal and manage latency-critical traffic. The core mechanism involves using the Explicit Congestion Notification (ECN) field in the IP header with a new L4S codepoint (ECT(1) or CE) to distinguish packets that require low-latency treatment. When a network node (like a router or UPF) experiences incipient congestion, it can mark these L4S packets with the CE codepoint at a very low queueing delay threshold, rather than dropping them or waiting for deep queues. This immediate feedback allows the sender (e.g., a UE or server) to react almost instantly using scalable congestion control algorithms like TCP Prague or equivalent real-time transport protocols, reducing its sending rate before significant queuing builds up.

Architecturally, L4S requires support in the end-to-end path: the sender must generate packets with the L4S ECN codepoint and use a scalable congestion control algorithm that reacts to single marked packets with a multiplicative decrease. The receiver must echo the ECN marks back to the sender via transport-layer acknowledgments. Critically, network nodes must implement a dual-queue coupled AQM (Active Queue Management) mechanism, such as Dual-Queue Coupled AQM (DQCA) or similar. This involves two queues: a Classic queue for standard traffic (e.g., traditional TCP) and an L4S queue for latency-sensitive traffic. The AQM applies very shallow thresholds (e.g., microseconds of queueing delay) to the L4S queue, marking packets at the first sign of congestion, while the Classic queue uses deeper thresholds. The queues are coupled so that L4S traffic does not starve Classic traffic, maintaining fairness.

In the 3GPP system, L4S is integrated into the 5G Core (5GC) and User Plane Function (UPF) to ensure low-latency treatment across the mobile network. Specifications define QoS flows and packet detection rules (PDRs) to identify and mark L4S traffic, often mapping to 5QI values designed for low latency. The UPF acts as a L4S network node, implementing the dual-queue AQM and marking packets accordingly. This enables applications like augmented reality (AR), virtual reality (VR), cloud gaming, and industrial control to achieve consistent sub-10ms latencies even under load, which is critical for immersive experiences and real-time automation. L4S thus transforms best-effort IP networks into predictable, low-latency platforms without requiring over-provisioning or dedicated physical resources.

Purpose & Motivation

L4S was created to address the fundamental limitations of traditional Internet congestion control and queue management in supporting ultra-low latency applications. Historically, TCP and standard Active Queue Management (e.g., RED, CoDel) were designed for throughput efficiency and fairness, but they induce latency due to bufferbloat—large queues in network buffers that cause delays. While solutions like DiffServ provided priority queuing, they required complex configuration, could starve background traffic, and did not scale well. The rise of 5G and demanding use cases like tactile internet, autonomous vehicles, and real-time holography necessitated a new approach that could deliver consistent microsecond-level latency without sacrificing throughput or fairness.

The motivation for L4S stems from the need for scalable low latency: as more applications require low delay, networks must handle many such flows simultaneously without performance degradation. Previous attempts, such as using separate high-priority queues, led to isolation issues and management overhead. L4S solves this by enabling low-latency and classic traffic to share the same link capacity efficiently through coupled congestion control. It leverages and extends Explicit Congestion Notification (ECN), which was underutilized, to provide immediate feedback. This allows congestion control algorithms to react within one round-trip time, minimizing queuing delays. By standardizing in 3GPP Release 18 and beyond, L4S ensures mobile networks can support the stringent requirements of future services, enabling economic scalability for operators while delivering superior user experiences.

Key Features

• Uses ECN with a dedicated L4S codepoint (ECT(1)/CE) for immediate congestion signaling
• Requires dual-queue coupled AQM in network nodes to separate L4S and Classic traffic with shallow thresholds
• Employs scalable congestion control algorithms (e.g., TCP Prague) that react to single marked packets
• Provides ultra-low queuing delay (sub-millisecond) and near-zero packet loss under congestion
• Maintains fairness between L4S and Classic traffic through coupled congestion control
• Integrates with 5G QoS framework via 5QI and UPF packet marking

Evolution Across Releases

Defining Specifications