Gx Rule Detection of Service Data Flow Initiation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Gx rules are limited in detecting the initiation of a service data flow, as they require specifying actions at the time of service flow definition, making it difficult for network operators to monitor and manage unknown applications and their resource consumption.

Innovation Solution

A Gx rule with a traffic classifier and a monitoring or notification directive is sent from the PCRF to the PCEF, allowing the PCEF to detect and report the initiation of a service data flow directly to an AF node, enabling network operators to monitor service flows without pre-defined actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If current Gx rules are used for post-service-initiation events, then charging and subscriber bandwidth usage management can be performed, but detection of service data flow initiation is not possible

Engineering Contradiction:
Improvedetection capabilityVSAvoidrule functionality
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The Gx rule is transformed from a static post-service-initiation notification mechanism to a dynamic service data flow initiation detection mechanism. The rule now actively monitors and detects the start of service data flows, enabling real-time detection capabilities while maintaining the existing rule structure and deployment framework.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If actions are specified at the time of service flow definition, then policy control can be enforced, but monitoring of unknown applications becomes difficult

Engineering Contradiction:
Improvemonitoring capabilityVSAvoidrule configuration
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary configuration of Gx rules with monitoring directives before service data flows are initiated. This allows the PCEF to be pre-equipped with the capability to detect and report unknown applications, enabling flexible monitoring without requiring complex runtime rule configuration or pre-definition of all possible service flows.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If PCEF reports service data flow initiation directly to AF node, then network operators can monitor unknown applications, but additional reporting infrastructure is required

Engineering Contradiction:
Improveinformation availabilityVSAvoidsystem architecture
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The PCEF acts as an intermediary that receives Gx rules from the PCRF and directly reports service data flow initiation events to the AF node. This intermediary role enables information flow from detection to application function without requiring complex additional infrastructure, leveraging existing Gx interface components to bridge the reporting gap.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2522103B1Methods, systems, and computer readable media for detecting initiation of a service data flow using a gx rule
Publication Date: 2020.10.21 TEKELEC INC
  • EP2522103B1 patent drawingFigure 1
  • EP2522103B1 patent drawingFigure 2
  • EP2522103B1 patent drawingFigure 3

AI summary

Methods, systems, and computer readable media for detecting a service data flow using a Gx rule are disclosed. According to one method, a policy and charging rules function (PCRF) node sends to a policy and charging enforcement function (PCEF) node, a Gx rule for triggering the PCEF node to generate a notification message upon initiation of a service data flow. The PCEF node receives and installs the Gx rule and uses the Gx rule to detect and report initiation of a service data flow.