Call Flow Analysis Using Comparison Level Indicators
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional testing platforms for LTE networks and equipment fail to provide informative and useful diagnostics for software or hardware issues, as they generate large amounts of test data that are difficult to analyze, especially when emulating multiple user devices, making it hard to identify problems in call flows.
Innovation Solution
The implementation of call flow analysis using comparison level indicators (CLIs) that allow for the emulation of user devices, transmission of test traffic, and analysis of received traffic using defined templates and indicators to compare actual and expected call flows, providing detailed feedback on discrepancies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If conventional testing platforms generate and collect test data from multiple emulated user devices, then the quantity of test data increases, but the difficulty of analyzing call flow information increases exponentially
Solution Approach 1:
The patent segments the large volume of test data into individual call flow records, each representing a specific user device's communication sequence. By dividing the monolithic data set into discrete, manageable call flow units, the system enables targeted analysis of individual device behaviors rather than being overwhelmed by aggregate data from multiple emulated devices.
Solution Approach 2:
The patent introduces comparison level indicators (CLIs) as an intermediary layer between the raw test data and the analysis process. These CLIs serve as reference templates that mediate the comparison between actual call flows and expected behaviors, transforming the complex task of analyzing raw test data into a structured pattern-matching process that identifies deviations systematically.
2Loss of information
If conventional testing platforms provide statistics on communication success or failure, then the amount of information provided increases, but the usefulness of the information for diagnosing problems decreases
Solution Approach 1:
The patent extracts specific diagnostic information from the overall test results by identifying and isolating call flows that deviate from expected patterns defined by comparison level indicators. Instead of presenting all statistics equally, the system extracts only the relevant deviations that indicate actual problems, separating signal from noise in the test data.
Solution Approach 2:
The patent applies local quality by providing detailed analysis specifically for call flows that exhibit problems, rather than uniformly analyzing all call flows. The comparison level indicators enable the system to focus diagnostic resources on specific problematic areas, providing deep insight into individual failure cases while maintaining overview of overall test results.
3Adaptability or versatility
If the number of emulated user devices increases, then the comprehensiveness of testing improves, but the time required to analyze test data increases linearly or exponentially
Solution Approach 1:
The patent performs preliminary action by establishing comparison level indicators (expected call flow patterns) before analyzing the actual test data. These pre-defined templates prepare the analysis framework in advance, allowing the system to quickly match actual call flows against expected patterns without performing complex analysis during the data processing phase, thus reducing analysis time as the number of emulated devices increases.
Data Source
AI summary
Methods, systems, and computer readable media for call flow analysis using comparison level indicators (CLIs) are disclosed. One exemplary method includes emulating a plurality of user devices, transmitting test traffic to at least one device under test (DUT) using the emulated user devices, receiving traffic from the at least one DUT in response to the traffic transmitted by the emulated user devices, and analyzing the traffic received from the at least one DUT using one or more CLIs, wherein each CLI indicates particular information associated with the traffic to analyze or compare.