Stream Classification Service Policy Validation via Cached Profiles
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Stream Classification Service (SCS) methods in Wi-Fi networks struggle to implement application-specific Quality of Service (QoS) management in enterprise settings, due to limitations in packet analysis techniques and computational resources, leading to inefficient resource allocation and potential service level agreement (SLA) violations.
Innovation Solution
The integration of policy pre-checks and on-demand packet analysis within the Stream Classification Service (SCS) feature, allowing for the validation of application-specific QoS policies by comparing SCS requests with cached application profiles and performing detailed packet analysis only when necessary.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If packet analysis is performed for every SCS request to ensure accurate application-specific QoS validation, then measurement precision and reliability are improved, but computational load and response time increase
Solution Approach 1:
The system performs preliminary actions by pre-defining and caching application profiles with their associated QoS parameters before actual SCS requests arrive. When a request comes in, the system first checks if the traffic characteristics match any cached profiles, avoiding the need for comprehensive packet analysis when the application type is already known, thus reducing computational load while maintaining validation accuracy.
Solution Approach 2:
The validation process is segmented into multiple stages: first checking against cached application profiles for quick matching, then performing targeted packet analysis only when necessary. This segmentation allows the system to handle common cases efficiently through profile matching while reserving computational resources for more complex, unknown traffic types that require deep packet inspection.
2Reliability
If comprehensive packet analysis is performed to validate application-specific QoS policies, then reliability and measurement precision are improved, but response time increases
Solution Approach 1:
Application profiles are pre-defined and cached before SCS requests arrive. The system uses these pre-prepared profiles to quickly validate common traffic types without performing time-consuming packet analysis, thereby reducing response time while maintaining reliable validation through targeted analysis only when profiles don't match.
Solution Approach 2:
The system applies partial packet analysis only when necessary (when traffic doesn't match cached profiles) rather than performing comprehensive analysis on all requests. This partial action approach maintains reliability for unknown traffic types while significantly improving response time for known applications that can be validated through profile matching alone.
3Productivity
If application profiles are cached to reduce computational load, then productivity is improved, but device complexity increases
Solution Approach 1:
The system performs preliminary action by pre-defining application profiles with their QoS characteristics and caching them in a database. This allows the system to leverage pre-processed information during runtime, reducing the need for complex real-time analysis and simplifying the validation process for known applications while maintaining high computational efficiency.
Data Source
AI summary
The present disclosure provides techniques for Stream Classification Service (SCS) policy validation for downlink and uplink traffic. A network device receives an SCS request from an associated STA, which specifies one or more sets of TCLAS information for a data flow transmitted between the network device and the STA, each set of TCLAS information being accompanied by associated QoS profile information for the data flow. The network device compares the sets of TCLAS information and associated QoS profile information with one or more cached application profiles, and determines that there is no match. In response to the determination, the network device performs packet analysis and confirms that the sets of TCLAS information and associated QoS profile information align with the type of service of the data flow under defined network polices. In response to the confirmation, the network device applies one or more treatments to the data flow.