QoS Polling via Traffic Threshold Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As networks grow, the sheer volume of network interfaces and traffic classes necessitates efficient Quality of Service (QoS) polling, but existing methods struggle to manage the vast amount of data, leading to challenges in making appropriate network decisions due to the overwhelming number of Key Performance Indicators (KPIs) generated.
Innovation Solution
The method involves determining if network interfaces exceed a traffic threshold, excluding those below the threshold from QoS polling, and for non-excluded interfaces, determining traffic classes and excluding those with priority levels below a cutoff threshold, while setting per-class QoS polling rates based on priority levels for higher-priority classes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If QoS polling is performed on all network interfaces to ensure comprehensive monitoring, then measurement precision is improved, but the quantity of data generated increases overwhelming the system
Solution Approach 1:
The patent extracts and excludes low-priority traffic classes from QoS polling based on priority thresholds. By identifying and removing non-critical traffic types from the polling process, the system generates fewer KPI data points while still monitoring essential services, directly resolving the contradiction between comprehensive monitoring and data volume management.
Solution Approach 2:
The patent applies different polling strategies to different traffic classes based on their priority levels. High-priority traffic classes receive frequent polling with detailed KPI collection, while low-priority classes are excluded or polled less frequently. This localized differentiation allows precise monitoring where needed while reducing overall data generation.
2Reliability
If QoS polling is performed on all network interfaces to ensure comprehensive monitoring, then reliability is improved, but loss of time increases due to processing vast data
Solution Approach 1:
The patent extracts and removes low-priority traffic classes from the QoS polling process using priority-based filtering. By excluding non-critical traffic types, the system maintains reliable monitoring of essential services while significantly reducing the time required to process and analyze KPI data across the network.
Solution Approach 2:
The patent applies partial action by performing QoS polling selectively on only the necessary subset of traffic classes rather than all interfaces uniformly. High-priority traffic receives full monitoring attention, while low-priority traffic is partially or completely excluded, optimizing the balance between monitoring reliability and processing time.
3Measurement precision
If comprehensive QoS polling is performed on all traffic classes to ensure thorough analysis, then measurement precision is improved, but device complexity increases
Solution Approach 1:
The patent extracts and removes low-priority traffic classes from the polling system using automated priority-based filtering. This extraction simplifies the polling system architecture by eliminating the need to configure, manage, and process numerous low-value KPI metrics, while maintaining precise measurement capabilities for critical traffic classes.
Solution Approach 2:
The patent implements local quality by applying differentiated polling configurations to different traffic classes based on priority levels. Critical traffic classes receive detailed multi-parameter monitoring, while non-critical classes are excluded or monitored with reduced parameters, thereby simplifying the overall system complexity while preserving measurement precision where it matters most.
4Productivity
If QoS polling is performed frequently on all interfaces to improve responsiveness, then productivity is improved, but use of energy increases
Solution Approach 1:
The patent extracts and excludes low-priority traffic classes from frequent QoS polling operations. By removing non-critical traffic types from the polling schedule, the system maintains high productivity for monitoring essential services while significantly reducing the computational energy required to perform repeated polling cycles across all interfaces.
Solution Approach 2:
The patent applies different polling frequencies to different traffic classes based on priority levels. High-priority traffic classes are polled frequently to ensure rapid detection of QoS issues and maintain high monitoring productivity, while low-priority classes are polled less frequently or excluded entirely, thereby reducing overall energy consumption of the polling system.
Data Source
AI summary
According to one aspect of the present disclosure, a computer-implemented method is disclosed, in which a determination is made for each of a plurality of network interfaces of whether an amount of traffic on the network interface exceeds a predefined traffic threshold. Each of the network interfaces whose amount of traffic is below the traffic threshold is excluded from Quality of Service (QoS) polling. For each of the non-excluded network interfaces whose traffic exceeds the traffic threshold, a determination is made of a set of traffic classes transported on the network interface, and any of the traffic classes with a priority level below a cutoff threshold are excluded from QoS polling. For each non-excluded traffic class that has a priority level above the cutoff threshold, a determination is made of a per-class QoS polling rate based on the respective priority level of the traffic class.