Application-Layer Congestion Control Without Direct NIC Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network control systems are unable to perform traffic flow controls in closed environments where network interface cards (NICs) are inaccessible, leading to inefficiencies in network traffic management.

Innovation Solution

Implementing a controller that operates at the application layer to monitor and control network traffic using kernel-bypass transport mechanisms, enabling timestamping and network traffic control functions even in closed environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a controller operates at the control layer to manage network traffic, then network traffic control functions can be performed, but the controller cannot access closed environments where NICs are inaccessible

Engineering Contradiction:
Improvenetwork traffic control capabilityVSAvoidaccessibility to closed environments
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent moves the control function from the traditional control layer (layer 3.5) to the application layer (layer 7), enabling control capabilities in closed environments where NICs are inaccessible. This dimensional shift in the OSI model allows the controller to operate where previously it could not reach.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The patent introduces kernel-bypass transport mechanisms as an intermediary between the application layer and the network interface, allowing the controller to manage traffic flows without direct NIC access. This intermediary enables control in environments where the controller would otherwise be blocked.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If packets traverse through the OSI network stack, then network protocols are properly handled, but latency increases

Engineering Contradiction:
Improveprotocol handling correctnessVSAvoidnetwork latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the congestion control function from the deep kernel network stack and places it at the application layer with kernel-bypass mechanisms. This extraction removes unnecessary processing steps from the critical data path while maintaining protocol handling through selective engagement of network stack functions.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs congestion control actions at the application layer before packets enter the network stack, preventing congestion issues before they propagate through the system. This preliminary control reduces the need for corrective actions later in the transmission path.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250254128A1Application layer congestion control
Publication Date: 2025.08.07 CLOCKWORK SYSTEMS INC
  • US20250254128A1 patent drawing
  • US20250254128A1 patent drawing
  • US20250254128A1 patent drawing

AI summary

Systems and methods are disclosed herein method for controlling traffic of a network at an application layer. A controller detects that an application is initiating transmission of a message from a sender host to a receiver host. The controller records one or more application layer sender timestamps corresponding to the transmission of the message, and records one or more application layer receiver timestamps based on detecting receipt of at least a portion of the message at the receiver host. Responsive to detecting that the message has been completely received by the receiver host, the controller determines a message duration spanning a length of time between a first one of the application layer sender timestamps and a last one of the application layer receiver timestamps. The controller performs a network traffic control function based on the message duration.