PCRF PCC Deployment Detection for Roaming Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the 3GPP EPS system, the Policy and Charging Control (PCC) function faces challenges in determining whether a visited network supports PCC, leading to difficulties in reporting events and managing policy and charging rules, especially in roaming scenarios where configuration information is complex and hard to update, and third-party services struggle to decide on event subscriptions based on the visited network's support for PCC.
Innovation Solution
A method where the Policy and Charging Rules Function (PCRF) determines if a visited network supports PCC by analyzing IP-CAN session messages, mobility protocol types, and local configuration information, including IP addresses, to notify the Application Function (AF) if PCC is not supported, allowing the AF to cancel or not initiate event subscriptions, thereby ensuring accurate reporting and resource management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the PCRF determines PCC support status by analyzing IP-CAN session messages and mobility protocol types, then the accuracy of PCC deployment status detection is improved, but the complexity of the detection mechanism increases
Solution Approach 1:
The PCRF utilizes existing IP-CAN session establishment/modification indication messages and mobility protocol type identifiers for multiple purposes: both for normal session management and for detecting PCC deployment status. This eliminates the need for separate detection mechanisms while maintaining accurate status identification.
Solution Approach 2:
The PCRF leverages its own existing message processing capabilities and local configuration information to perform PCC status detection. The system uses self-contained resources (local configuration, existing message handling) rather than requiring external detection systems or additional complex infrastructure.
2Ease of manufacture
If the AF subscribes to events without knowing the visited network's PCC support status, then the system operates with simpler configuration, but resource waste occurs due to unsuccessful event reporting
Solution Approach 1:
The PCRF performs preliminary determination of PCC support status in the visited network before the AF subscribes to events. This advance information allows the AF to make informed subscription decisions, avoiding wasted resources on event reporting that cannot be successfully delivered.
Solution Approach 2:
The PCRF provides feedback information about PCC deployment status to the AF through the event subscription process. This feedback mechanism enables the AF to adjust its behavior accordingly, subscribing to events only when PCC is supported, thus avoiding resource waste while maintaining configuration simplicity.
3Adaptability or versatility
If third-party AFs rely on their own configuration information to determine PCC support, then the system maintains operational independence, but the configuration becomes complex and hard to update
Solution Approach 1:
The PCRF acts as an intermediary that provides standardized feedback about PCC deployment status to third-party AFs. This intermediary mechanism eliminates the need for AFs to maintain complex configuration information about visited networks, while preserving operational independence through standardized interfaces.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
The present invention provides a method and system for implementing limited policy and charging control. The method comprises a PCRF determining whether a visited network where a UE roams supports PCC, and sending a message containing an identifier indicating the limited policy and charging control deployment to an AF. After receiving the message containing the identifier, the AF performs no subscription of the event trigger and/or cancels the subscription of the event trigger based on the identifier. Using the method and system in accordance with the present invention, the AF can be notified more conveniently and accurately of the current policy and charging control deployment situation when the limited policy and charging control is implemented (i.e., when the visited network does not support the PCC). Moreover, the AF may perform the corresponding operations according to the current policy and charging control deployment situation, thereby saving system resources.