Wi-Fi Stream Classification for QoS-Aware Flow Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Wi-Fi standards struggle to differentiate and manage diverse application flows with varying quality of service (QoS) requirements, leading to inefficiencies in bandwidth allocation and user experience.
Innovation Solution
Implementing a stream classification service (SCS) that classifies data streams based on QoS characteristics, allowing network devices to prioritize and manage flows using scheduling behaviors and queue configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If Wi-Fi networks use traditional flow management without stream classification, then device complexity remains low, but quality of service differentiation and bandwidth allocation efficiency deteriorate
Solution Approach 1:
The patent segments network flows into different classes based on QoS characteristics (e.g., latency-sensitive, bandwidth-intensive, best-effort). This segmentation enables differentiated service treatment for each flow class, improving bandwidth allocation efficiency while managing complexity through standardized classification categories rather than custom per-flow management.
Solution Approach 2:
The system performs preliminary flow classification and QoS parameter extraction at the network edge before traffic enters the core network. By pre-processing flow identification and scheduling behavior determination upstream, the patent reduces real-time processing complexity at network nodes while maintaining efficient bandwidth allocation.
2Reliability
If the network implements comprehensive flow classification and scheduling, then quality of service for critical applications improves, but network device processing overhead increases
Solution Approach 1:
The patent applies different quality treatment locally at each network node based on flow classification results. Each node independently determines scheduling behavior for classified flows, allowing QoS guarantees for critical applications without requiring centralized processing of all traffic. This distributed local quality approach reduces overall processing energy consumption.
Solution Approach 2:
The system applies comprehensive flow classification only to traffic matching predefined QoS criteria (partial action), rather than processing all flows uniformly. Flows that do not match specific QoS requirements are handled with simpler best-effort processing, reducing total device processing energy while maintaining reliable QoS for critical applications that need it.
3Ease of operation
If the network manages diverse application flows with varying QoS requirements, then user experience improves, but ease of operation and configuration deteriorates
Solution Approach 1:
The patent implements a universal flow classification framework that handles multiple application types and QoS requirements through a single integrated mechanism. The same classification and scheduling infrastructure serves diverse flows (video conferencing, AR/VR, file transfer, etc.), improving user experience across applications while avoiding the need for separate configuration systems for each application type.
Solution Approach 2:
The system manages diverse flows by changing key parameters (scheduling behavior, queue selection, bandwidth allocation) based on flow classification results rather than requiring complex configuration changes. The network dynamically adjusts QoS parameters for different application flows using standardized parameter sets, simplifying operation while maintaining differentiated service quality.
Data Source
AI summary
In embodiments described herein, one or more stream classifications are incorporated into a plurality of flows within a network. These flows can have a number of characteristics associated with it, such as, but not limited to quality of service requirements that can dictate how the flow should be processed. A device associated with the flow can transmit a stream classification service (SCS) request. This SCS request can be received and processed to determine a scheduling behavior that should be adopted by various network device/nodes associated with the flow. The scheduling behavior can be transmitted to those network devices which can then modify the processing of the flow(s). In some cases, the network device can classify the packets associated with the flow(s) and prioritize them. In additional cases, the network device can generate one or more new queues that can be configured to best serve the requirements of the flow.