Application-Based Queue Management Using Trigger Templates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Communication networks face challenges in effectively managing congestion due to oversubscription, leading to delayed packet transmission and disrupted application performance, as existing congestion control methods lack application-specific differentiation and dynamic queue management.

Innovation Solution

The implementation of application-based congestion control using trigger templates, which identify and apply specific congestion control actions based on packet headers and flow queue conditions, allowing for dynamic adjustment of queue management policies to match varying application needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If application-based congestion control with trigger templates is implemented, then network efficiency and quality of service are improved, but device complexity increases

Engineering Contradiction:

Improvenetwork efficiencyVSAvoidcongestion control mechanism complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The congestion control mechanism is segmented into multiple trigger templates, each dedicated to specific application types or protocols. This segmentation allows the system to handle different applications with specialized control rules rather than using a single complex monolithic controller, improving network efficiency while organizing complexity into manageable modular units.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of creating entirely new congestion control logic for each application, the patent uses trigger templates that copy and adapt generic congestion control patterns. Each template captures the essential control behavior for a class of applications, allowing the system to reuse proven control strategies across multiple applications without reinventing the wheel for each case.

Inventive Principle:

Principle #26Copying

2Reliability

If application-specific congestion control is implemented, then packet delivery performance is improved, but implementation complexity increases

Engineering Contradiction:

Improvepacket delivery performanceVSAvoidimplementation complexity

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The trigger template mechanism serves multiple functions simultaneously: it identifies applications based on packet headers, selects appropriate congestion control policies, and executes the corresponding control actions. This multi-functionality reduces implementation complexity by consolidating what could be separate complex systems into a unified template-based framework that handles application recognition and control execution together.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent implements application-specific control by changing parameters within a unified framework rather than creating fundamentally different control mechanisms. Each trigger template modifies congestion control parameters (such as queue management thresholds, drop probabilities, or scheduling priorities) based on the matched application type, allowing flexible adaptation while maintaining a consistent implementation structure.

Inventive Principle:

Principle #35Parameter changes

3Measurement precision

If dynamic queue management based on packet headers is implemented, then congestion control accuracy is improved, but processing overhead increases

Engineering Contradiction:

Improvecongestion control accuracyVSAvoidprocessing overhead

Core Design Contradiction:

Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by examining only specific header fields that are sufficient for application identification rather than performing complete deep packet inspection. The trigger templates are configured to match on essential header parameters (such as protocol type, port numbers, or traffic class markers), achieving adequate congestion control accuracy without the excessive processing overhead of analyzing entire packet contents.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS11677666B2Application-based queue management

Publication Date: 2023.06.13 NOKIA SOLUTIONS & NETWORKS OY

AI summary

Various example embodiments for supporting queue management in communication systems are presented. Various example embodiments for supporting queue management in communication systems may be configured to support application-based queue management. Various example embodiments for supporting application-based queue management may be configured to support application-based congestion control. Various example embodiments for supporting application-based congestion control may be configured to support application-based congestion control based on use of trigger templates.