PCRN Session Revalidation Timeout Extension
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP standards for LTE networks lack guidance on how the Policy and Charging Rules Function (PCRF) should respond to events such as revalidation timeouts, limiting the flexibility in managing subscriber sessions and charging.
Innovation Solution
A Policy and Charging Rules Node (PCRN) is implemented to respond to network events by receiving event messages, retrieving incremental values for subscribers, determining updated values based on these and reference values, and sending update messages, allowing for flexible session management and charging practices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If fixed absolute values are used to respond to revalidation timeout events, then the response is simple and consistent, but the flexibility and variety of options available are limited
Solution Approach 1:
The patent implements dynamic event response by allowing the PCRN to select between different response types (terminate session, extend timeout, or no action) based on subscriber-specific policies. The revalidation timeout value becomes dynamic rather than fixed, adapting to individual subscriber needs and service requirements.
Solution Approach 2:
The patent changes the parameter of revalidation timeout from a fixed absolute value to a configurable value that can be extended by an incremental amount. This allows the timeout parameter to be adjusted based on subscriber profile, service type, and policy rules, providing flexibility without requiring complete redesign of the event response mechanism.
2Ease of operation
If subscriber-specific incremental values are used to extend sessions, then flexibility and fairness in resource allocation are enhanced, but the complexity of managing and retrieving subscriber information increases
Solution Approach 1:
The patent implements self-service by having the PCRN automatically retrieve subscriber-specific incremental values from the subscriber profile repository and apply them to extend sessions. The system autonomously manages the complexity of storing, retrieving, and applying subscriber information without requiring manual intervention, making session management easier while handling the complexity internally.
Solution Approach 2:
The patent introduces the subscriber profile repository as an intermediary component that stores and manages subscriber-specific incremental values. This mediator separates the complexity of subscriber information management from the session management logic in the PCRN, allowing the PCRN to focus on session control while the repository handles data storage and retrieval.
3Reliability
If the PCRN terminates sessions when no incremental value is defined, then resource allocation is controlled, but the ability to accommodate diverse subscriber needs is reduced
Solution Approach 1:
The patent applies partial action by allowing session extension only for subscribers who have defined incremental values in their profiles. For subscribers without such values, the session terminates as specified. This partial application of extension logic maintains reliability for standard cases while providing versatility for subscribers with special requirements.
Solution Approach 2:
The patent implements local quality by applying different session management behaviors to different subscribers based on their individual profiles. Subscribers with defined incremental values receive extended sessions, while others receive standard termination. This allows the system to accommodate subscriber variations locally without compromising overall system reliability.
Data Source
AI summary
Various exemplary embodiments relate to a method performed by a Policy Charging and Control Node (PCRN) for updating a session associated with a subscriber in response to an event. The method may include receiving at the PCRN an event message indicating that an event has occurred within the session; retrieving subscriber information including at least one incremental value associated with the event for the subscriber; determining an updated value based on the at least one retrieved incremental value and at least one reference value; and responding to the event message with an update message including the updated value. Various exemplary embodiments may further include configuring a subscriber profile repository to include at least one incremental value and terminating the session if the subscriber is not allowed to use incremental updates or no incremental value is defined for the subscriber.