QoS Engine TCP Controller Network Traffic Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Middleboxes experience transmission latency due to resource constraints, leading to poor quality of service for users, especially during sudden increases in network traffic, as they struggle to process packets efficiently with limited CPU capacity and memory.

Innovation Solution

A system that includes a Quality of Service (QoS) engine to determine flow priorities and TCP characteristics, and a TCP controller to adjust the receive window size based on queue information, optimizing network traffic by prioritizing high-priority traffic and managing resource constraints.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the middlebox processes all network traffic packets with limited CPU capacity and memory, then packet processing queue builds up causing transmission latency, but reducing processing capacity further degrades quality of service

Engineering Contradiction:
Improvepacket processing throughputVSAvoidtransmission latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments network traffic into different priority queues (high priority and low priority) based on flow classification. High priority traffic is processed first through a dedicated queue, while low priority traffic is processed separately. This segmentation allows the middlebox to handle critical traffic efficiently even when resources are constrained, reducing transmission latency for important packets while maintaining overall processing throughput.

Inventive Principle:
Principle #1Segmentation

2Reliability

If the middlebox increases resource allocation to handle traffic bursts, then transmission latency is reduced, but device complexity and resource requirements increase

Engineering Contradiction:
Improvequality of service consistencyVSAvoidappliance resource requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic resource allocation where the middlebox adjusts processing priorities and queue management in real-time based on current traffic conditions and resource availability. The system dynamically switches between processing modes, allocating more resources to high priority traffic when needed while maintaining flexibility to handle varying traffic patterns. This dynamic approach ensures consistent quality of service without requiring permanently over-provisioned resources.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes operational parameters such as queue thresholds, processing priorities, and flow classification rules based on system state. When resource constraints are detected, the system adjusts parameters like the maximum queue length for high priority traffic or modifies flow priority assignments to optimize performance. These parameter changes allow the middlebox to adapt to varying conditions without increasing hardware complexity.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the middlebox prioritizes high-priority traffic during resource constraints, then quality of service for critical traffic is maintained, but low-priority traffic experiences increased latency

Engineering Contradiction:
Improvequality of service for high-priority trafficVSAvoidlatency for low-priority traffic
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies different quality standards to different traffic flows based on their priority classification. High priority traffic receives preferential treatment with dedicated queue space, faster processing, and protected bandwidth, while low priority traffic is allowed to experience more variable performance. This local quality differentiation ensures that critical applications maintain reliable quality of service even during resource constraints, while non-critical traffic can tolerate increased latency.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11582163B2System for early system resource constraint detection and recovery
Publication Date: 2023.02.14 CITRIX SYSTEMS INC
  • US11582163B2 patent drawing
  • US11582163B2 patent drawing
  • US11582163B2 patent drawing

AI summary

A system for optimizing network traffic is described. The system includes a quality of service (QoS) engine configured to acquire information regarding a plurality of data packets comprising a plurality of data packet flows operating over a plurality of links. The QoS engine can be further configured to determine a flow priority to the plurality of data packets flows, and to determine TCP characteristics for the plurality of data packet flows. The system further includes a TCP controller configured to acquire the flow priority to the plurality of data packets from the QoS engine. The TCP controller can be configured to obtain queue information associated with the plurality of data packets, and adjust a receive window size based on the flow priority and the queue information.