QoS Traffic Segmentation for Application Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current networking systems lack the ability to provide multiple quality of service (QoS) levels to different classes of traffic within a single network-based application, leading to suboptimal user experience and inefficient resource utilization.

Innovation Solution

A system and method that utilize an application programming interface (API) to differentiate between control and other traffic within an application, allowing for the provision of low-latency QoS to control commands and higher latency to other data, managed by network components such as Public Data Network Gateways and Policy Charging and Rules Functions, to conserve network resources while maintaining responsiveness.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single QoS level is provided to all traffic within an application, then network resource utilization is simplified, but user experience deteriorates due to inability to prioritize control commands

Engineering Contradiction:
ImproveQoS management complexityVSAvoiduser experience quality
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments traffic within an application into multiple classes (e.g., control traffic and data traffic) and assigns different QoS levels to each class. This is achieved through traffic classification mechanisms that identify and separate control commands from other application traffic, allowing differentiated QoS treatment while maintaining manageable complexity through systematic classification rules

Inventive Principle:
Principle #1Segmentation

2Speed

If low-latency QoS is provided to all application traffic, then responsiveness is improved, but network resource efficiency deteriorates due to over-provisioning

Engineering Contradiction:
Improvetraffic responsivenessVSAvoidnetwork resource efficiency
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The patent applies local quality by providing high QoS treatment (low latency) only to specific local portions of traffic that require it (control commands), while allowing standard QoS treatment for other traffic portions (data transfer). This localized differentiation ensures responsiveness where needed while conserving network resources for non-critical traffic

Inventive Principle:
Principle #3Local quality

3Reliability

If multiple QoS levels are provided to different traffic classes, then user experience is improved through prioritized control commands, but system complexity increases

Engineering Contradiction:
Improveuser experience qualityVSAvoidQoS management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by establishing traffic classification rules and QoS mapping configurations in advance, before actual traffic flow occurs. Network components are pre-configured with classification criteria (e.g., port numbers, protocol types, packet markers) that automatically direct traffic to appropriate QoS levels without real-time complex decision-making

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9007899B2Quality of service treatement for applications with multiple traffic classes
Publication Date: 2015.04.14 VERIZON PATENT & LICENSING INC
  • US9007899B2 patent drawing
  • US9007899B2 patent drawing
  • US9007899B2 patent drawing

AI summary

A system may receive a connection request, from a user device, that includes information identifying a particular application; identify that the particular application is associated with a group of classes of traffic; establish a group of bearer channels that are associated with the group of classes of traffic, the group of bearer channels being associated with a group of different levels of quality of service (“QoS”); process, via a first bearer channel and according to a first level of QoS, first traffic associated with the user device and the particular application; and process, via a second bearer channel of the group of bearer channels, according to a second level of QoS, second traffic associated with the user device and the particular application, the second bearer channel being different from the first bearer channel, and the second level of QoS being different from the first level of QoS.