Wireless Carrier Fee Re-Rating Through Selective CDR Reprocessing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless carrier networks face challenges in efficiently recalculating service fees due to initial errors, configuration issues, or anomalous events, leading to inaccurate billing and customer complaints.
Innovation Solution
A re-rating engine with a lookup tool and CDR reprocessing tool allows administrators to identify and modify large batches of call detail records (CDRs) using query criteria, update business logic, and generate reprocessed CDRs to recalibrate fees accurately.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual recalculation of service fees is performed for affected subscribers, then billing accuracy can be improved, but the time and resources required increase significantly
Solution Approach 1:
The system performs preliminary identification of affected subscribers and CDRs using event detection and lookup tools before recalculation begins. This pre-processing organizes data and determines re-rating parameters in advance, enabling faster execution of the actual recalculation process while maintaining accuracy.
Solution Approach 2:
The system creates copies of affected CDRs and generates reprocessed CDRs with corrected rating parameters. Instead of modifying original records, the system works with replicated data structures, allowing efficient recalculation without compromising data integrity or requiring time-consuming original record modifications.
2Productivity
If automated re-rating systems are implemented, then processing speed improves, but system complexity increases
Solution Approach 1:
The re-rating system is divided into distinct functional modules: event detection engine, lookup tool for identifying affected CDRs, CDR reprocessing tool for generating corrected records, and billing system integration components. This segmentation allows each module to be developed, maintained, and scaled independently, managing overall system complexity while enabling high-throughput automated processing.
Solution Approach 2:
The system introduces intermediary components including the lookup tool that bridges event detection and CDR reprocessing, and the CDR reprocessing tool that mediates between original CDR data and the billing system. These intermediaries simplify the overall architecture by handling data transformation and coordination tasks, reducing the complexity burden on individual components.
3Measurement precision
If comprehensive event monitoring is performed across all network nodes, then detection accuracy improves, but computational resources consumed increase
Solution Approach 1:
The event detection engine is deployed at specific network nodes where anomalous events are most likely to occur or where their impact would be greatest. Rather than uniform monitoring across all nodes, the system concentrates detection capabilities at strategic locations, improving detection accuracy for critical events while reducing overall computational resource consumption.
Solution Approach 2:
The system implements selective monitoring that focuses computational resources on detecting specific types of anomalous events that affect billing accuracy, rather than attempting to detect all possible events. The lookup tool then efficiently identifies only the CDRs affected by detected events, avoiding unnecessary processing of unrelated records and reducing overall computational load.
Data Source
AI summary
A business logic used to generate call details records (CDRs) for a plurality of subscribers by a wireless carrier network is imported. A selection of one or more data collector applications that are listed in the business logic is received and one or more configuration parameters in the business logic are updated based on one or more inputted parameter updates. A selection of one or more CDR distributor applications listed in the business logic is also received. A particular set of CDRs in the specific group of CDRs is further selected based on one or more inputted selection parameters. Reprocessed CDRs that correspond to the particular set of CDRs are generated according to at least the one or more updated configuration parameters in the business logic and sent to the one or more billing systems via the one or more CDR distributor applications to trigger recalculation of service fees.