Excess Active Queue Management for TCP Slow-Start Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern Active Queue Management (AQM) techniques are complex and do not adequately address performance reductions during the Slow-Start phase of TCP connections, leading to inefficiencies and increased latency.

Innovation Solution

The introduction of 'excess-AQM' techniques, which include 'excess-AQM-tail', 'excess-AQM-head', and 'excess-AQM-both', that simplify AQM by using explicit congestion notification (ECN) or Data Center TCP (DCTCP)/Low Latency, Low Loss, and Scalable Throughput (L4S) signaling, allowing for efficient handling of excess packets and reduced resource consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If modern AQM techniques are used to manage queue congestion, then congestion signaling to TCP endpoints is improved, but device complexity increases and Slow-Start performance is not adequately addressed

Engineering Contradiction:
Improvecongestion signalingVSAvoidAQM complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the AQM functionality into two distinct parts: (1) a simple threshold-based excess packet detection mechanism that operates independently of complex AQM algorithms, and (2) the existing AQM logic. This segmentation allows the system to maintain simple, effective Slow-Start handling while preserving modern AQM capabilities for established connections, thereby reducing overall device complexity while maintaining reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different AQM strategies to different phases of TCP connection lifecycle. For Slow-Start phase, it uses a simple threshold-based excess packet marking approach. For established connections, it relies on the configured modern AQM technique. This local quality approach ensures optimal performance for each phase without requiring the system to be complex enough to handle all scenarios uniformly.

Inventive Principle:
Principle #3Local quality

2Reliability

If modern AQM techniques are used to optimize traffic flow, then congestion management is improved, but latency during Slow-Start phase increases

Engineering Contradiction:
Improvetraffic flow managementVSAvoidSlow-Start latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by proactively marking excess packets before they cause congestion during the Slow-Start phase. The threshold-based mechanism identifies and marks packets that would contribute to queue buildup before actual congestion occurs, allowing TCP endpoints to adjust their sending rates in advance. This prevents the latency that would otherwise occur when congestion is detected too late in the Slow-Start phase.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If complex AQM techniques are implemented to handle congestion, then congestion signaling is optimized, but resource consumption increases

Engineering Contradiction:
Improvecongestion notificationVSAvoidprocessing resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts the Slow-Start handling functionality from the complex modern AQM techniques. By separating the threshold-based excess packet detection and marking logic from the main AQM processing chain, the system can handle Slow-Start packets with minimal resource consumption while reserving the more resource-intensive modern AQM techniques for established connections where they are more effective.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12301473B2Excess active queue management (AQM): a simple AQM to handle slow-start
Publication Date: 2025.05.13 HEWLETT PACKARD ENTERPRISE DEV LP
  • US12301473B2 patent drawing
  • US12301473B2 patent drawing
  • US12301473B2 patent drawing

AI summary

A system maintains a queue for storing packets, which are enqueued at a tail of the queue and dequeued at a head of the queue. The system computes a queue utilization value, based on the packets stored in the queue. The system computes an excess amount value, based on the packets stored in the queue and previously tagged as excess packets. The system receives a first packet at the tail of the queue and determines whether a difference between the queue utilization value and the excess amount value exceeds a predetermined threshold. Responsive to determining that the difference exceeds the predetermined threshold, the system tags the first packet as an excess packet. Responsive to tagging the first packet as an excess packet, the system performs an operation associated with the first packet or a second packet at the head of the queue to reduce congestion.