Charging Information Parameter Segmentation for Roaming Network Accounting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current charging systems in network deployments, particularly in IMS communication scenarios, fail to accurately differentiate between various traffic cases handled by Interconnect Border Control Functions (IBCFs), leading to inaccurate inter-operator accounting and potential revenue losses due to insufficient charging information.
Innovation Solution
The introduction of additional connection state parameters such as roaming indication, connection direction, trust state, and address parameters in charging information messages allows for the generation of detailed charging records that distinguish between different traffic cases, enabling precise accounting across multiple network segments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If standardized CDR parameters are used for charging, then inter-operator accounting can be performed, but the charging information is insufficient to differentiate between various traffic cases handled by IBCFs
Solution Approach 1:
The patent segments the charging information into multiple distinct parameters including roaming indication parameter, connection direction parameter, trust parameter, and address parameter. Each parameter captures a specific aspect of the traffic case, enabling precise differentiation between various IBCF-handled scenarios while maintaining comprehensive accounting capability.
Solution Approach 2:
The patent adds multiple new dimensions to the charging information by introducing parameters that describe different aspects of the connection state (roaming status, direction, trust relationship, address). This multi-dimensional approach transforms the flat standardized CDR parameters into a rich parameter set that can differentiate traffic cases across multiple dimensions simultaneously.
2Productivity
If multiple logical IBCF instances are involved in a single IMS communication scenario, then multiple ACRs and CDRs are generated, but the standardized CDR parameters fail to carry enough charging information to allow traffic classification
Solution Approach 1:
The patent creates a universal parameter set that can be applied across multiple logical IBCF instances and different IMS communication scenarios. The connection state parameters (roaming indication, connection direction, trust parameter, address parameter) serve multiple functions: they differentiate traffic cases, enable accurate accounting, and work consistently across single and multiple IBCF instance scenarios.
Solution Approach 2:
The patent changes the parameter structure by introducing new connection state parameters with specific values that encode traffic case information. For example, the roaming indication parameter can take values indicating whether roaming is used, and the connection direction parameter indicates the direction of connection, allowing systematic differentiation of traffic cases across multiple IBCF instances.
3Measurement precision
If dedicated physical IBCF nodes are assigned to each logical IBCF instance, then traffic case differentiation is possible, but network resource utilization efficiency considerably decreases
Solution Approach 1:
The patent merges multiple logical IBCF instances onto shared physical infrastructure while maintaining the ability to differentiate traffic cases through parameter information. By using connection state parameters to encode traffic case details, the system eliminates the need for dedicated physical nodes for each logical instance, thereby improving network resource utilization while preserving precise traffic case identification.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
There are provided measures for network interface utilization dependent charging determination. Such measures exemplarily comprise establishing a connection between a network and a neighboring network for transiting a transmission session, obtaining connection state parameters based on at least one of said connection, said network, and said neighboring network, and generating a charging information message based on said connection state parameters at a network interface side, and receiving a charging information message related to a connection between a network and a neighboring network for transiting a transmission session, storing connection state parameters based on said charging information message, and generating an account for said transmission session based on said connection state parameters at a charging evaluation side.