Packet Flow Optimization for Encapsulated QoS Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In wireless communication networks, especially in LTE and LTE Advanced, there is a challenge in effectively managing encapsulated data flows for quality of service (QoS) and policy and charging control (PCC), as existing systems struggle to accurately detect and manage encapsulated packet flows, leading to inefficiencies in resource allocation and service delivery.

Innovation Solution

The implementation of a method and system that uses predefined policy and charging control (PCC) rules to detect encapsulated packet flows through packet flow optimization, involving deep packet inspection and event trigger mechanisms, allowing for the derivation and enforcement of QoS rules based on detected flows, thereby optimizing resource allocation and service management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If deep packet inspection is performed to detect encapsulated packet flows, then measurement precision of packet flow detection is improved, but device complexity and processing overhead increase

Engineering Contradiction:
Improvepacket flow detection accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system segments the packet flow detection task by creating separate PFO applications for different encapsulation types (e.g., PMIP, DSMIPv6). Each PFO application is responsible for detecting specific encapsulation types using tailored detection rules, rather than one monolithic inspection system handling all types. This segmentation improves detection precision for each protocol while managing complexity through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by pre-configuring detection rules and PFO applications for known encapsulation types before actual packet flow detection begins. The network entity is pre-provisioned with multiple PFO applications that can be activated based on the detected flow type, avoiding the need for complex real-time analysis of every packet structure.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple PCC rules are configured for different encapsulation types, then adaptability of the system to various packet flows is improved, but device complexity increases

Engineering Contradiction:
Improveencapsulation detection capabilityVSAvoidrule management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The network entity is designed with multi-functionality to handle multiple encapsulation types (PMIP, DSMIPv6, and future types) through a unified architecture. The system can dynamically activate appropriate PFO applications based on the flow type detected, providing universal adaptability without requiring separate dedicated systems for each encapsulation protocol.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system implements dynamic rule selection where PFO applications are activated or deactivated based on the specific encapsulation type detected in the packet flows. This dynamic approach allows the system to adapt to different protocol requirements without permanently configuring all possible rules, thereby managing complexity while maintaining versatility.

Inventive Principle:
Principle #15Dynamics

3Productivity

If event trigger mechanisms are implemented for flow detection reporting, then productivity of QoS enforcement is improved, but device complexity increases

Engineering Contradiction:
ImproveQoS enforcement efficiencyVSAvoidevent trigger mechanism complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements feedback mechanisms where PFO applications continuously monitor packet flows and trigger events when specific detection criteria are met. This feedback loop enables the network entity to automatically respond to detected encapsulated flows by activating appropriate PCC rules and QoS policies, improving enforcement efficiency through automated closed-loop control.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP2356835B1Performing packet flow optimization with policy and charging control
Publication Date: 2016.08.17 QUALCOMM INC
  • EP2356835B1 patent drawingFigure 1
  • EP2356835B1 patent drawingFigure 2
  • EP2356835B1 patent drawingFigure 3

AI summary

Policy and charging control (PCC) is a framework within a Third or Fourth Generation (3G/4G) network that allows operators to authorize and enforce policy, Quality of Service (QoS), and charging control over communication sessions by mobile devices. PCC mechanism is used to determine the type QoS based on a request received from a User Equipment (UE) or network. PCC is one important element within System Architecture Evolution (SAE) architecture to allow the network to perform policy and charging control. A mechanism is provided so that PCC can allow packet flow optimization. Thereby, the network can detect Internet Protocol (IP) flows based on operator defined criteria and can perform policy and QoS control.