Scheduled ECN Signaling for Transport Node Congestion Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Congestion control in Next Generation (NG) wireless networks, such as 5G NR networks, is inefficient due to packet dropping and misinterpretation of congestion states by transport nodes, leading to inefficient bandwidth utilization and increased latency, particularly with Low Latency Low Loss Scalable Throughput (L4S) traffic.

Innovation Solution

Implementing a transport congestion control notification service in network devices, utilizing AI/ML and time-based scheduling to accurately indicate congestion states by altering ECN bits in packets, ensuring correct congestion signaling and efficient traffic delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If transport nodes drop packets to signal congestion, then congestion notification is provided, but bandwidth utilization decreases and latency increases

Engineering Contradiction:
Improvecongestion notification accuracyVSAvoidbandwidth utilization
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces ECN (Explicit Congestion Notification) bits as an intermediary mechanism. Instead of dropping packets to signal congestion, transport nodes set ECN bits in packet headers to notify senders of congestion conditions. This intermediary signaling mechanism allows congestion notification without packet loss, thereby maintaining bandwidth utilization while providing reliable congestion information.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If transport nodes continuously monitor and signal congestion, then congestion control accuracy improves, but network overhead and processing complexity increase

Engineering Contradiction:
Improvecongestion state detection accuracyVSAvoidcongestion control mechanism complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent utilizes ECN bit parameters in packet headers to encode congestion state information. By changing the state of these standardized parameters (ECN bits) rather than introducing new complex signaling mechanisms, the system achieves precise congestion detection with minimal added complexity. The approach leverages existing protocol parameters for their intended purpose.

Inventive Principle:
Principle #35Parameter changes

3Loss of time

If L4S traffic uses ECN bits for congestion signaling, then latency is reduced through better congestion control, but transport nodes cannot properly remap ECN bits due to encapsulation by outer IP protocols

Engineering Contradiction:
ImprovelatencyVSAvoidECN bit remapping capability
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The patent segments the congestion control function into separate network elements. Transport nodes that encounter encapsulated L4S traffic cannot remap ECN bits, but this is acceptable because other transport nodes in the path that are not encapsulating the traffic can perform ECN bit remapping. The congestion control functionality is distributed across multiple network elements rather than requiring every node to perform all functions.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12568395B2Method and system for congestion notification in transport nodes
Publication Date: 2026.03.03 VERIZON PATENT & LICENSING INC
  • US12568395B2 patent drawing
  • US12568395B2 patent drawing
  • US12568395B2 patent drawing

AI summary

A method, a network device, and a non-transitory computer-readable storage medium are described in relation to a transport congestion control notification service. The transport congestion control notification service may include providing congestion notification by a network device according to a schedule. The congestion notification may be implemented as explicit congestion notification bits included in packets. The schedule may govern the starting and stopping of the congestion notification. The schedule may be generated based on historical congestion states of relevance to the network device. The schedule may be generated by the network device or by an external device and provisioned at the network device.