Event Trigger Provisioning in Evolved Packet Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the 3GPP EPS system, event triggers provisioned based on IP-CAN session level lead to incorrect reporting by the BBERF, as it cannot determine which IP-CAN session the policy information is associated with due to shared gateway control sessions, resulting in event misreporting.

Innovation Solution

Provisioning event triggers based on the gateway control session level, where the PCRF sends all event triggers related to a user equipment's IP-CAN sessions to the BBERF, allowing correct installation and reporting of trigger events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If event triggers are provisioned at IP-CAN session level, then each session can have specific event triggers, but the BBERF cannot determine which IP-CAN session the policy information is associated with due to shared gateway control sessions, leading to event misreporting

Engineering Contradiction:
Improveevent reporting accuracyVSAvoidsession management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the event trigger management by introducing a specific identifier (such as IP-CAN session identifier or bearer identifier) that uniquely associates event triggers with individual IP-CAN sessions. This segmentation allows the BBERF to distinguish between multiple sessions sharing the same gateway control session, thereby resolving the ambiguity and improving event reporting accuracy without significantly increasing overall system complexity.

Inventive Principle:
Principle #1Segmentation

2Productivity

If multiple IP-CAN sessions share a gateway control session, then resource utilization is improved, but the BBERF loses the ability to correctly identify which session policy information belongs to

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidsession association information
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary identifier mechanism that acts as a mediator between the shared gateway control session and multiple IP-CAN sessions. This identifier is included in the policy information messages, allowing the BBERF to correctly associate policy information with the specific IP-CAN session even when multiple sessions share the same gateway control session, thus preventing loss of session association information while maintaining resource utilization efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If event triggers are sent individually for each IP-CAN session, then session-specific control is achieved, but the BBERF installs incorrect triggers due to inability to distinguish sessions

Engineering Contradiction:
Improvesession-specific policy controlVSAvoidtrigger installation accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by pre-configuring unique identifiers for each IP-CAN session that are embedded in the event trigger messages. This preliminary identification mechanism is established before the BBERF installs the event triggers, ensuring that even when multiple sessions share a gateway control session, the BBERF can correctly identify and install the appropriate event triggers for each specific session, thereby maintaining both session-specific adaptability and trigger installation accuracy.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2302842B1Method for sending down and installing event trigger
Publication Date: 2014.04.09 ZTE CORP
  • EP2302842B1 patent drawingFigure 1
  • EP2302842B1 patent drawingFigure 2
  • EP2302842B1 patent drawingFigure 3

AI summary

The present invention provides a method for provisioning and installing event triggers, which is applied to an evolved packet system. The method comprises: a policy and charging rules function entity provisions event triggers to a bearer binding and event reporting function entity based on gateway control session level; after receiving the provisioned event triggers, the BBERF installs or updates the event triggers. An evolved packet system is further provided.