IP Telephony CDR Matching via Transfer ID Calculation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
IP telephony systems face challenges in matching multiple Call Detail Records (CDRs) generated by different elements for the same communication, especially in complex call flows where call identification number information is not available, making it difficult to determine the flow path and aggregate information for billing, troubleshooting, and quality monitoring.
Innovation Solution
A method is developed to match CDRs using a transfer ID number calculated from information such as calling party identifier, called party identifier, and counter number, and timestamp values, allowing for the identification of all CDRs related to a communication, even in call flows where call ID numbers are not consistently linked.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If call identification number information is used to link CDRs, then CDR matching is straightforward and reliable, but this method fails in complex call flows where call ID numbers are not consistently available or linked across different legs
Solution Approach 1:
The patent introduces an intermediary matching process that uses multiple parameters (calling party identifier, called party identifier, timestamp, counter number) as mediators to connect CDRs when direct call ID linking is unavailable. This intermediary approach allows CDRs from different call flow legs to be matched through common identifying characteristics rather than relying solely on call ID numbers.
Solution Approach 2:
The patent changes the parameters used for CDR matching from relying exclusively on call identification numbers to using a combination of parameters including calling party identifier, called party identifier, timestamp, and counter number. This parameter transformation enables matching across diverse call flow types where call ID consistency cannot be guaranteed.
2Loss of information
If multiple CDRs are generated by different elements for the same communication, then comprehensive information is collected for billing and troubleshooting, but it becomes difficult to determine which CDRs belong to the same communication and reconstruct the flow path
Solution Approach 1:
The patent segments the CDR matching process into distinct stages: identifying matching parameters, comparing CDRs based on those parameters, grouping matched CDRs into communication sets, and reconstructing flow paths. This segmentation makes the complex task of matching multiple CDRs manageable and systematic.
Solution Approach 2:
The patent creates a universal matching mechanism that works across different call flow types (direct routing, hairpinning, transiting, etc.) by using common parameters that exist in all CDRs. This multi-functional approach allows the same matching logic to handle diverse scenarios without requiring separate specialized processes.
3Measurement precision
If call flow type information is recorded in the final CDR, then billing and quality monitoring become more accurate, but determining the actual flow path followed by each communication becomes difficult
Solution Approach 1:
The patent performs preliminary action by recording the flow path type in the final CDR after the communication has been routed through the network. By determining and recording the flow path classification (direct, hairpin, transit, etc.) as part of the CDR aggregation process, the system captures this information before it is needed for billing and analysis, making it readily available without requiring real-time detection during call setup.
Data Source
AI summary
Call detail records (CDRs) that are generated by different elements of an IP telephony system in connection with the same communication can be matched to one another using timing information contained in the CDRs. Other information in addition to timing information, and which is present in two CDRs relating to the same communication may be used in conjunction with timing information to match CDRs from the same communication. Also, information relating to the type of flow path that a communication follows through the elements of an IP telephony system may also be recorded in a final CDR that is created for each communication.