Call Detail Record Data Refinement for Routing Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current telecommunications networks lack efficient systems to quickly and easily view how calls are being routed, making it difficult for network service providers to determine if calls are being routed optimally according to business objectives, vendor agreements, and cost considerations, due to the complexity and volume of call detail records (CDRs).
Innovation Solution
A computer-implemented method and system that refines CDR data by summing selected amounts such as minutes of use and costs associated with common call setup characteristics, generating refined call entries that summarize data across network elements, allowing for easier analysis and reporting of call routing metrics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If CDR data is collected and stored in detailed call-by-call format, then complete routing information is captured, but the data becomes difficult to view and analyze quickly
Solution Approach 1:
The patent extracts and displays only the most relevant CDR data elements for analysis, separating critical routing information from the complete detailed dataset. This allows executives to quickly view essential routing patterns without being overwhelmed by all available data points.
Solution Approach 2:
The patent combines multiple CDR records with similar routing characteristics into aggregated views, merging data at different hierarchical levels (call-by-call, route-by-route, vendor-by-vendor) to provide both detailed and summary perspectives simultaneously.
2Loss of information
If CDR data is presented at individual call level with all data items, then complete information is available, but network administrators cannot quickly determine if network service objectives are being met
Solution Approach 1:
The patent segments CDR data into hierarchical levels of aggregation, allowing users to navigate from individual call details to summarized routing patterns. This segmentation enables quick assessment of network objectives by presenting aggregated data at appropriate levels without losing access to detailed call information when needed.
Solution Approach 2:
The patent implements partial action by displaying only the most relevant aggregated metrics needed for quick assessment of network service objectives, rather than presenting all possible CDR data elements. This selective presentation reduces analysis time while maintaining sufficient information for decision-making.
3Loss of information
If detailed CDR data is gathered from all network elements, then comprehensive routing data is captured, but the volume and complexity make it difficult to understand call routing patterns
Solution Approach 1:
The patent adds dimensional aggregation to CDR data presentation, organizing data along multiple dimensions (time, route, vendor, network element) simultaneously. This multi-dimensional organization transforms complex detailed data into structured summaries that reveal routing patterns without reducing data completeness.
4Loss of information
If all CDR attributes are displayed for each call, then complete call information is available, but important routing analysis becomes difficult due to large numbers of non-important data items
Solution Approach 1:
The patent extracts and prioritizes display of CDR attributes most relevant to routing analysis, separating critical routing information from less important call details. This extraction allows network administrators to quickly detect routing patterns and assess service objectives without being obscured by numerous non-essential data items.
Data Source
AI summary
An embodiment of a method includes selecting call detail report (CDR) call setup attributes from captured CDR data, refining the CDR data, and summing CDR amount attribute values for each set of CDR call entries having common values for the selected CDR call setup attributes. Each set of one or more CDR call entries having common values for the CDR call setup attributes are combined into a single refined CDR call entry having the common CDR call setup attribute values and the summed CDR amount attribute values. The summing process is repeated for each set of CDR data associated with each of a plurality of network elements. After summing the CDR attribute amount values for call entries having common CDR setup call attribute values for each switch, CDR attribute amount values associated with common CDR setup attribute values in call entries associated with all switches are summed to generate a final set of refined CDR data.