Policy Node Identifier Routing in Packet Core Networks

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional LTE networks rely on a large binding database for routing application requests, which can lead to service outages and significant revenue loss due to database unavailability, especially when handling millions of records for user equipment (UE) sessions.

Innovation Solution

The system introduces node identifiers assigned to packet core nodes, which are routed within the call flow to enable the Diameter Routing Agent (DRA) to determine the correct Policy and Charging Rules Function (PCRF) without relying on the binding database, using a global mapping table and node identifiers to facilitate efficient routing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If a large binding database is used to store PCRF routing information per IP-CAN session, then routing accuracy is improved, but system reliability deteriorates due to database unavailability impacting application services

Engineering Contradiction:

Improverouting accuracyVSAvoidservice availability

Core Design Contradiction:

Measurement precisionVSReliability

Solution Approach 1:

The patent segments the routing information by including the PCRF identifier directly in the Rx message from the AF, rather than storing all routing information in a centralized binding database. This allows the DRA to determine the host PCRF using the identifier embedded in the message, eliminating the need to query the binding database for routing decisions.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The PCRF identifier is determined and included in the Rx message during the initial service request phase, before any database queries are needed. This preliminary inclusion of routing information in the message itself enables the DRA to perform routing decisions without relying on the availability of the binding database.

Inventive Principle:

Principle #10Preliminary action

2Quantity of substance

If a binding database with millions of records is maintained, then routing information completeness is improved, but device complexity and maintenance difficulty increase

Engineering Contradiction:

Improverouting information completenessVSAvoiddatabase management complexity

Core Design Contradiction:

Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent extracts the essential routing information (PCRF identifier) from the binding database and embeds it directly in the Rx message. This extraction eliminates the need to maintain and query a large binding database, as the routing information is now self-contained in the message itself, significantly reducing database management complexity.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of querying the binding database for routing information, the system uses a copy of the PCRF identifier that is already embedded in the Rx message. This copying approach eliminates the need to access and query the large binding database, simplifying the DRA's routing decision process.

Inventive Principle:

Principle #26Copying

3Ease of repair

If the binding database is made unavailable for maintenance or updates, then ease of repair is improved, but service continuity deteriorates due to direct impact on application services

Engineering Contradiction:

Improvedatabase maintenance easeVSAvoidservice continuity

Core Design Contradiction:

Ease of repairVSDuration of action of stationary object

Solution Approach 1:

The PCRF identifier is preliminarily embedded in the Rx message during service request setup, before any database operations are needed. This allows the DRA to perform routing decisions using the embedded identifier without needing to access the binding database, enabling database maintenance without service disruption.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The Rx message acts as an intermediary carrier that transports the PCRF identifier from the AF to the DRA. This intermediary mechanism eliminates the direct dependency between the DRA and the binding database, allowing the database to be taken offline for maintenance while services continue to function using the identifier in the message.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11039291B2Policy node identifier for application services in a packet core network

Publication Date: 2021.06.15 AT&T INTELLECTUAL PROPERTY I L P

AI summary

Node identifiers can be assigned to packet core policy nodes and directly routed to a diameter routing agent (DRA) and application functions (AFs) within a call processing message that is employed to establish an application service. Such a policy node identity will be received by Application Functions, UEs and/or intermediate message routers during the initial establishment of a packet data session so that they can refer to the policy node entity directly in the sub-sequent call processing flows related the established session, instead of querying a relational database which can be complex to maintain with multi-million correlation records. As an example, the policy node identifiers can be configurable and can comprise a hostname of the policy nodes, address data associated with the policy nodes, or a defined numerical value that maps to the hostname of the policy nodes.