Control Plane Charging Coordination in Separated Network Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In existing network architectures where network control and data flow forwarding are separated, online credit control cannot be performed effectively, leading to inefficient charging mechanisms and increased transmission delays due to the distributed nature of trigger conditions across control and user planes.
Innovation Solution
A method and apparatus that enable online credit control by having the control plane execute charging rules, generate user plane reporting policies, request quotas from the online charging system, and establish associations between reporting policies and quota information, allowing for centralized quota management and reporting across separated network planes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data gateways are centrally deployed at a relatively long distance from access network to cooperate in charging, then charging coordination is improved, but transmission delays increase
Solution Approach 1:
The patent segments the gateway into control plane (CP) and user plane (UP) entities. The CP entity remains centrally deployed for charging coordination while the UP entity is distributed closer to access networks for local data forwarding. This segmentation allows charging functions to be separated from data traffic paths, resolving the contradiction between centralized charging management and reduced transmission delays.
2Loss of time
If network control and data flow forwarding are separated with distributed user plane entities, then transmission delays are reduced, but charging enforcement cannot be performed at one point
Solution Approach 1:
The patent introduces an intermediary mechanism where the CP entity acts as a mediator between the OCS and distributed UP entities. The CP entity receives quota information from OCS, generates reporting policies, and coordinates with UP entities for quota enforcement. This intermediary approach enables centralized charging enforcement while maintaining distributed data forwarding architecture.
Solution Approach 2:
The patent implements a feedback mechanism where UP entities report quota usage information back to the CP entity, which then communicates with the OCS. This feedback loop enables the system to maintain charging enforcement capability despite the distributed architecture, as usage information is continuously collected and reported through the CP intermediary.
3Productivity
If user plane gateways are moved downwards close to Radio Access Network, then local service transmission is optimized, but online credit control cannot be performed
Solution Approach 1:
The patent segments the gateway into control plane (CP) and user plane (UP) entities. The CP entity remains centrally deployed for charging coordination while the UP entity is distributed closer to access networks for local data forwarding. This segmentation allows charging functions to be separated from data traffic paths, resolving the contradiction between centralized charging management and reduced transmission delays.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention discloses a charging method. The charging method is applied to a network architecture in which network control and data flow forwarding are separated, and includes: receiving, by a control plane CP entity, a charging rule delivered by a policy control and charging rules function PCRF entity; generating, by the CP, a user plane UP entity reporting policy based on the charging rule; requesting, by the CP from an online charging system OCS, a quota required by a rating group in the charging rule; receiving, by the CP, a quota delivered by the OCS, and generating UP quota information based on the quota; and delivering, by the CP, the generated UP reporting policy and the generated UP quota information to the UP. In the solutions provided in the embodiments of the present invention, online credit control and charging can be implemented in the architecture in which network control and data flow forwarding are separated.