Invoice Correction Pipeline Using Batch Processing and Indexing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current telecommunications processing systems face challenges in automating the correction of invoices without disrupting the automated processing of Usage Detail Records (UDRs), as manual corrections can compromise the automated processing sequence.
Innovation Solution
A pipeline batch processing system is implemented to perform parallel and batch processing of Call Detail Records (CDRs) using a specialized indexing scheme with primary, secondary, and foreign keys, allowing for efficient generation and correction of invoices by reducing data volume and storing redundant data in auxiliary records.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual correction procedures are used for invoice corrections, then correction flexibility is improved, but automated processing of UDRs is compromised and processing time increases
Solution Approach 1:
The system enables self-service correction by allowing the automated processing pipeline to perform its own corrections through the same correction procedures it uses for generation. The correction mechanisms are integrated into the automated flow, eliminating the need for separate manual intervention while maintaining correction flexibility through the same procedural pathways.
Solution Approach 2:
The same processing procedures are used for both generating new invoices and correcting existing ones. The pipeline batch processing system handles both operations through unified correction procedures, allowing a single automated system to perform multiple functions (generation and correction) without requiring separate manual processes.
2Measurement precision
If complete usage data is retained in records for correction purposes, then correction accuracy is improved, but data volume increases and processing speed decreases
Solution Approach 1:
Redundant data is extracted from the main usage records and stored separately in auxiliary records. The main records retain only the essential data needed for primary processing, while auxiliary records store additional correction-related information. This separation allows fast processing of main records while preserving correction capabilities through the extracted auxiliary data.
Solution Approach 2:
The data storage is segmented into main usage records and auxiliary correction records. This segmentation allows the system to process only the essential data in the main records for speed, while the auxiliary records provide supplementary information when correction is needed, thus balancing processing speed with correction accuracy.
3Productivity
If data volume is reduced in processed records, then processing efficiency is improved, but correction capability is compromised
Solution Approach 1:
Auxiliary records serve as intermediaries between the reduced main records and the correction requirements. When correction is needed, the system retrieves supplementary information from the auxiliary records, which act as a mediator providing the necessary data without requiring the main records to retain complete original data volumes.
Solution Approach 2:
Data that may be needed for future corrections is preliminarily stored in auxiliary records during the initial processing phase. This preliminary action ensures that correction capability is maintained without requiring the main records to carry complete data volumes throughout processing, thus preserving processing efficiency while enabling future corrections.
Data Source
AI summary
A mobile digital telecommunication system, a computer-implemented method, and a computer readable medium having stored thereon a computer executable program code for processing of usage detail records (UDRs) is disclosed herein. The mobile digital cellular telecommunication system comprises a network component configured to generate the UDRs, a rating system and a billing system.