QoS-Enabled VoIP Traffic Segmentation in Open Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In open networks, traditional QoS policing methods such as three-tuple and five-tuple policing are ineffective due to net neutrality rules, making it challenging to ensure latency-advantaged QoS for latency-sensitive applications like VoIP and video telephony without intrusive and costly deep packet inspection.
Innovation Solution
Implementing a system that defines two buckets for traffic - one for general IP traffic and another for QoS-based traffic, with distinct billing rates and flow rate limits, allowing for metered or flat billing and applying bandwidth constraints to QoS-based traffic, thereby eliminating the need for policing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional three-tuple and five-tuple QoS policing methods are used, then QoS can be enforced in closed networks, but these methods become ineffective in open networks due to net neutrality rules
Solution Approach 1:
The patent segments traffic into different categories (voice traffic, video traffic, data traffic) and applies different billing models to each category. Voice and video traffic receive guaranteed QoS through real-time billing, while data traffic receives best-effort service through flat-rate billing, allowing QoS enforcement in open networks without violating net neutrality
Solution Approach 2:
The patent changes the billing parameter from traditional per-minute or per-byte charging to real-time QoS-based billing. By implementing real-time monitoring and charging based on actual QoS parameters (latency, jitter, bandwidth), the system can enforce QoS in open networks while maintaining compatibility with net neutrality rules
2Reliability
If deep packet inspection is used for intrusive policing in open networks, then QoS can be ensured for latency-sensitive applications, but the method becomes time consuming and expensive to implement
Solution Approach 1:
The patent performs preliminary classification of traffic into categories (voice, video, data) at the network edge before entering the core network. This preliminary action allows subsequent QoS handling to be based on traffic category rather than requiring deep packet inspection of every packet, reducing complexity while maintaining QoS guarantees
Solution Approach 2:
The patent introduces an intermediary billing system that acts as a mediator between traffic sources and network resources. This billing intermediary classifies traffic and applies appropriate billing models (real-time for voice/video, flat-rate for data), enabling QoS enforcement without requiring complex deep packet inspection at every network node
3Ease of operation
If QoS policing is applied to every user and application, then QoS can be negotiated for call setup, but every user receives best effort treatment and high bandwidth applications are served equally regardless of QoS needs
Solution Approach 1:
The patent applies different billing and QoS treatment to different traffic categories rather than treating all traffic uniformly. Voice and video traffic receive real-time billing with guaranteed QoS, while data traffic receives flat-rate billing with best-effort service, achieving QoS differentiation without complex per-user negotiation
Solution Approach 2:
The patent creates a universal billing framework that handles multiple traffic types (voice, video, data) through a single real-time billing system. This multi-functional approach allows the same infrastructure to provide both guaranteed QoS for real-time applications and best-effort service for data applications, eliminating the need for separate QoS negotiation for each user
Data Source
AI summary
A device defines a first bucket for general Internet protocol (IP) traffic provided to and from a user device associated with an open network, and defines a second bucket for quality of service (QoS)-based traffic provided to and from the user device. The device also assigns a first billing rate for the general IP traffic associated with the first bucket, and assigns a second billing rate to the QoS-based traffic associated with the second bucket, where the second billing rate is greater than the first billing rate. The device further associates the first billing rate and the second billing rate with a subscriber associated with the user device.