PCRF Node Session Management for Multi-Version 3GPP Standards

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current telecommunications systems face challenges in seamlessly operating with different minor versions of 3GPP standards, particularly at the PCRF node, leading to compatibility issues and the need for multiple product versions, which is inefficient and costly during network upgrades and live deployments.

Innovation Solution

A device and method that enable the PCRF node to operate with various major and minor release combinations of the 3GPP standards by using attribute value pairs (AVPs) to determine and select the appropriate release combinations for new and existing sessions, allowing for flexible session management and support of multiple standard versions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single PCRF product version is used to support multiple minor versions of 3GPP standards, then device complexity and maintenance costs are reduced, but the system must implement mechanisms to distinguish and determine which minor version is being used in network components

Engineering Contradiction:

ImprovePCRF product version managementVSAvoidMinor version identification

Core Design Contradiction:

Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent uses AVP (Attribute Value Pair) indicators as 'signifiers' embedded in Diameter protocol messages to indicate the minor version of 3GPP standards being used by network components. These AVPs act like visual indicators that allow the PCRF to quickly identify and adapt to different standard versions without complex detection mechanisms

Inventive Principle:

Principle #32Color changes

Solution Approach 2:

Network components automatically include AVP indicators in their Diameter messages that self-identify their 3GPP minor version. This eliminates the need for separate version detection queries, as each component provides its version information proactively in its own signaling messages

Inventive Principle:

Principle #25Self-service

2Reliability

If multiple product versions are maintained to support different minor versions of 3GPP standards, then compatibility with specific network components is ensured, but maintenance burden and cost increase

Engineering Contradiction:

ImproveStandard version compatibilityVSAvoidProduct version maintenance

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The PCRF is designed with multi-functionality to support multiple 3GPP minor versions within a single product. The system can dynamically adapt its behavior based on the AVP indicators received from network components, allowing one PCRF instance to serve multiple standard versions without requiring separate product versions for each minor release

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The PCRF implements dynamic version adaptation where the supported 3GPP minor version is not fixed but changes based on the AVP indicators received in incoming Diameter messages. This allows the system to flexibly adjust its operational mode to match the version required by the communicating network component

Inventive Principle:

Principle #15Dynamics

3Adaptability or versatility

If the system determines and selects different minor versions for new sessions, then network compatibility and scalability are enhanced, but additional processing steps are required to determine the appropriate release combination

Engineering Contradiction:

ImproveSession compatibilityVSAvoidSession management process

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary determination of the appropriate 3GPP minor version during the session establishment phase by examining AVP indicators in incoming requests. This early determination allows the PCRF to configure session parameters correctly from the start, avoiding later compatibility issues and reducing the need for complex runtime version negotiation

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The AVP indicator acts as an intermediary that carries version information from network components to the PCRF. This intermediary mechanism simplifies the interaction between components of different versions by providing a standardized way to communicate version requirements without direct complex version negotiation

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8788677B2Session based support of multiple 3GPP standards versions

Publication Date: 2014.07.22 ALCATEL LUCENT SA

AI summary

Embodiments are disclosed that enable a device such as a policy and charging rules function (PCRF) node to operate with other nodes in a long term evolution (LTE) network that are operating at different respective major-minor release combinations of the 3rd Generation Partnership Project (3GPP) standards. Some embodiments enable such a device to operate with another network node at a given major-minor release combination of the 3GPP standards with respect to one session being managed by the device and at another major-minor release combination of the 3GPP standards with respect to another session. Some embodiments enable the major-minor release combination to be specified by first and second attribute value pairs (AVPs) respectively indicating the major and minor release identifiers of the major-minor release combination when a new session is requested, thereby providing greater flexibility for establishing sessions.