P2P Traffic SCS Authorization Through Flow Identification and QoS Checks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless networks struggle to identify and manage Quality of Service (QoS) resources for Peer-to-Peer (P2P) traffic flows due to the lack of support for Stream Classification Service (SCS) requests, particularly in enterprise environments with applications like Augmented Reality/Virtual Reality/Extended Reality (AR/VR/XR), leading to inefficiencies in network policy enforcement.
Innovation Solution
Enhancements to the SCS request process enable Stations (STAs) to provide flow identifiers and QoS resource information for P2P traffic flows, allowing Access Points (APs) to apply network policies and manage QoS resources effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional wireless network protocols are used for P2P traffic, then device compatibility is maintained, but QoS resource identification and management capability is lost
Solution Approach 1:
The patent segments the SCS request into distinct components: a P2P information element containing flow identifiers (such as TCLAS or IP tuple) and a QoS characteristics element. This segmentation allows the system to handle P2P traffic identification and QoS resource management as separate but integrated functions, enabling reliable QoS management while maintaining support for diverse P2P applications.
Solution Approach 2:
The patent adds a new dimensional layer to the SCS request by incorporating a P2P information element that carries flow identifier information. This additional dimension enables the Access Point to simultaneously process traditional QoS requirements and new P2P traffic identification needs without compromising either function.
2Measurement precision
If flow identifiers are added to SCS requests, then P2P traffic identification accuracy is improved, but request complexity increases
Solution Approach 1:
The P2P information element is designed with multi-functionality, supporting multiple types of flow identifiers (TCLAS, IP tuple, or other formats) within a single unified structure. This universality improves P2P traffic identification accuracy across different application types while avoiding the need for multiple separate request structures, thereby limiting the increase in complexity.
Solution Approach 2:
The patent introduces the P2P information element as an intermediary component between the station's QoS requirements and the Access Point's policy enforcement mechanisms. This intermediary structure organizes flow identifier information in a standardized format that simplifies processing at the Access Point, preventing request complexity from escalating despite enhanced identification capabilities.
3Reliability
If network policy enforcement is implemented for P2P flows, then network security is enhanced, but processing overhead at the Access Point increases
Solution Approach 1:
The patent implements preliminary action by requiring stations to include flow identifier information in the SCS request before traffic flow establishment. This allows the Access Point to perform network policy checks on already-identified P2P flows rather than having to monitor and identify flows in real-time, reducing processing overhead while maintaining security enforcement.
Solution Approach 2:
The station performs preliminary work by populating the P2P information element with flow identifier information before submitting the SCS request to the Access Point. This self-service approach shifts some processing burden from the Access Point to the station, enabling the Access Point to focus its processing power on policy enforcement decisions rather than flow identification, thus reducing overall processing overhead.
Data Source
AI summary
Authorization for stream classification service requests for Peer-to-Peer (P2P) traffic flows may be provided. An Access Point (AP) may receive a Stream Classification Service (SCS) request from a station for a P2P traffic flow. The SCS request may include a flow identifier for the P2P traffic flow and Quality of Service (QOS) resource requested for the P2P traffic flow. The AP may determine whether to grant the SCS request. Determining whether to grant the SCS request may include determining that a network policy allows the P2P traffic flow based on the flow identifier and determining that the AP can support the QoS resource requested for the P2P traffic flow.