Unified Congestion Notification via Recipient-Set ACK Flags

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network communication protocols, such as TCP/IP, rely on Explicit Congestion Notification (ECN) mechanisms that are ineffective if not all devices along a communication path are ECN-compliant, leading to packet loss without proper congestion indication, forcing devices to manage transmission rates based on different scenarios.

Innovation Solution

A unified congestion notification mechanism where the recipient sets a congestion flag in acknowledgement packets without explicit indication from network devices, allowing for implicit congestion detection and notification, even in non-ECN compliant networks, and applicable to various communication protocols including TCP.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If ECN mechanisms are implemented in TCP/IP protocols, then congestion notification capability is improved, but device compatibility and network-wide effectiveness deteriorate because not all devices are ECN-compliant

Engineering Contradiction:
Improvecongestion notification capabilityVSAvoiddevice compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

Instead of having routers actively signal congestion to senders (top-down approach), the patent inverts the mechanism by having senders infer congestion from packet loss patterns and adjust their behavior accordingly (bottom-up approach). This allows congestion notification to work even when intermediate devices are not ECN-compliant.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent introduces an intermediary inference mechanism where the sender device acts as a mediator that detects congestion indirectly through packet loss patterns rather than requiring direct signaling from routers. This intermediary detection layer bridges the gap between non-ECN-compliant network infrastructure and ECN-capable endpoints.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If devices must manage transmission rates based on different scenarios (ECN-compliant vs non-compliant networks), then protocol adaptability is improved, but device complexity and operational burden increase

Engineering Contradiction:
Improveprotocol adaptabilityVSAvoidtransmission rate management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal congestion control mechanism that functions across both ECN-compliant and non-compliant networks using the same packet loss detection logic. This multi-functional approach eliminates the need for separate management strategies for different network types, reducing device complexity while maintaining adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent applies homogeneous congestion detection logic (inferring congestion from packet loss) that works uniformly across different network configurations. By using the same detection and response mechanism regardless of whether the network is ECN-compliant or not, the patent simplifies device operation while maintaining broad adaptability.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS7596091B2Unified congestion notification mechanism for reliable and unreliable protocols by augmenting ECN
Publication Date: 2009.09.29 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7596091B2 patent drawing
  • US7596091B2 patent drawing
  • US7596091B2 patent drawing

AI summary

A unified congestion notification mechanism can detect congestion at a recipient device either directly, such as via an explicit indicator, or indirectly, such as via dropped packets. Such congestion can then be indicated to the sending device either by leveraging an existing congestion notification mechanism, including by spoofing expected communications, or by creating a new congestion notification mechanism. Additionally, modifications to lossless protocols, such as TCP/IP can adapt them for use with streaming data while still implementing the unified congestion notification mechanism by eliminating retransmissions either as a result of the retransmission timeout or as a result of information conveyed as part of the acknowledgement packets.