Client Traffic Management Logic for Multipath Congestion Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current multipath traffic management systems face challenges in ensuring timely and efficient network traffic policy implementation at client devices, as they rely on periodic policy updates from service providers, which may not reflect current network conditions, leading to increased communication overhead and power consumption.

Innovation Solution

A system where client traffic management logic at the service provider server captures flow data to identify network traffic flows, selects appropriate traffic policies, and triggers their implementation by adjusting allowable throughput, allowing real-time congestion management without requiring client device cooperation or additional communication overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If periodic policy updates are sent from service provider to client device, then traffic policy implementation is achieved, but communication overhead and power consumption increase

Engineering Contradiction:
Improvetraffic policy implementationVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The client device is empowered to autonomously monitor network conditions and implement traffic policies locally without requiring periodic updates from the service provider. The device uses its own sensors and network interface to detect congestion levels and automatically adjusts traffic distribution, eliminating the need for continuous communication and reducing power consumption while maintaining reliable policy implementation

Inventive Principle:
Principle #25Self-service

2Reliability

If periodic policy updates are sent from service provider to client device, then traffic policy implementation is achieved, but communication overhead increases

Engineering Contradiction:
Improvetraffic policy implementationVSAvoidcommunication overhead
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts the traffic policy implementation function from the service provider's control domain and relocates it to the client device. By removing the need for periodic policy update communications and enabling local autonomous decision-making, the solution eliminates unnecessary data transmission while ensuring traffic policies are effectively implemented at the network edge

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If client device implements local traffic balancing, then traffic distribution is achieved, but response time to network condition changes is delayed

Engineering Contradiction:
Improvetraffic distributionVSAvoidresponse time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The client device continuously monitors network conditions through feedback from network interfaces and congestion indicators. This real-time feedback mechanism enables the device to detect changes in network status immediately and dynamically adjust traffic distribution without delay, achieving both ease of operation and rapid response time simultaneously

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11799689B2Multipath traffic management
Publication Date: 2023.10.24 INTEL CORP
  • US11799689B2 patent drawing
  • US11799689B2 patent drawing

AI summary

One embodiment provides an apparatus. The apparatus includes client traffic management (CTM) logic. The CTM logic is to trigger implementation of a selected network traffic flow related to the client device, the triggering based, at least in part, on a network traffic flow related to the client device. The network traffic flow is associated with a connection and includes at least one subflow. Each subflow is carried by a respective path associated with the connection. The triggering includes at least one of constraining and/or adjusting an allowable throughput at a service provider for one or more of the at least one subflow. The selected traffic policy is to be implemented in a transport layer.