IP Flow Based Charging Control for Packet Data Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing GPRS charging system cannot perform separate charging for different services that share the same PDP Context, leading to an inability to accurately reflect resource usage and charge operators or service providers based on the specific services provided.
Innovation Solution
Implementing IP Flow Based Charging (FBC) by setting event triggers and sending charging rule requests from the Traffic Plane Function (TPF) to the Charging Rule Function (CRF) to selectively apply charging rules based on specific events, such as bearer establishment, modification, or deletion, thereby allowing for more granular and accurate charging.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If IP Flow Based Charging is implemented with event triggers and charging rule requests, then charging precision and flexibility are improved, but system complexity and information exchange overhead increase
Solution Approach 1:
The charging system is segmented into distinct functional components: Traffic Plane Function (TPF) for monitoring data flows, Charging Rule Function (CRF) for managing charging rules, and Online Charging System (OCS) for credit control. This segmentation allows each component to specialize in specific tasks, improving charging precision while managing complexity through modular design. The PDP context is also segmented into multiple service data flows that can be charged separately.
Solution Approach 2:
The patent introduces intermediate components and interfaces to manage complexity: the Gx interface between TPF and CRF, the Rx interface between AF and CRF, and the Gy interface between TPF and OCS. These intermediaries standardize communication protocols and information exchange formats, allowing the system to achieve high charging precision without proportionally increasing overall system complexity.
2Measurement precision
If separate charging is implemented for different services within the same PDP Context, then charging accuracy is improved, but device complexity and processing overhead increase
Solution Approach 1:
Service data flows within a PDP context are segmented into distinct IP flows that can be independently monitored and charged. Each service flow is assigned unique identifiers and characteristics that enable separate charging while sharing the same PDP context. This allows the system to achieve granular charging accuracy without requiring separate PDP contexts for each service.
Solution Approach 2:
The TPF is designed with multi-functionality to handle both PDP context-level operations and service data flow-level monitoring. The same TPF that manages PDP context activation and deactivation also performs detailed flow-based charging, eliminating the need for separate devices and reducing overall system complexity while maintaining high charging accuracy.
3Adaptability or versatility
If event triggers are used to send charging rule requests, then charging flexibility is improved, but information exchange overhead increases
Solution Approach 1:
The system uses periodic event triggers at key PDP context events (activation, deactivation, QoS modification) to request charging rules. Instead of continuous information exchange, charging rule requests are sent periodically at these specific event points, providing charging flexibility while reducing overall information exchange overhead compared to continuous monitoring and reporting.
Solution Approach 2:
The CRF provides feedback to the TPF with charging rule decisions based on received requests. This feedback mechanism allows the system to adapt charging rules dynamically based on network conditions, service types, and user profiles, achieving high charging flexibility. The feedback is efficiently managed through standardized interfaces that minimize information exchange overhead by only transmitting necessary charging parameters.
Data Source
AI summary
A method for controlling the charging of packet data service includes: monitoring a number of event triggers; and when one of the event triggers is met, a Traffic Plane Function (TPF) requesting charging rules from a Charging Rule Function (CRF). In the preferred embodiments, the event triggers, which the TPF is required for request charging rules from the CRF according to are set by the CRF and then are provided to the TPF. Charging-relevant input information is provided in the request, based on which the CRF determines proper charging rules and sends the determined charging rules to the TPF. In this way, the timing that the TPF requests charging rules from the CRF becomes controllable, and redundant information caused by the unnecessary charging rule from the TPF becomes avoidable, which enables effective interaction between the TPF and the CRF and reasonable charging control of packet data service.