Wireless Call Failure Tracking via On-Device Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Telecommunication carriers are unable to accurately track call failures on wireless phones, specifically the inability to connect with their network, as existing methods only monitor calls after connection, not before.
Innovation Solution
A software application on the wireless phone monitors outbound calls for failure, storing information such as time, location, and phone ID, and sends this data to the carrier, allowing for assessment of network quality and connection success rates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If carriers track calls only after connection, then network monitoring is simple, but call failure tracking is inaccurate
Solution Approach 1:
The patent introduces a software application as an intermediary component on the wireless phone that bridges the gap between the phone and carrier network. This software monitors call connection status locally and reports failures to the carrier, enabling accurate call failure tracking without requiring complex changes to the carrier's core network infrastructure.
Solution Approach 2:
The software application performs preliminary monitoring of call connection status before the call is fully established. By detecting call failures during the initial connection phase and reporting them proactively, the system enables carriers to track call failures accurately without waiting for post-connection analysis.
2Loss of information
If software monitors all outbound calls, then call failure data is complete, but phone battery consumption increases
Solution Approach 1:
The software extracts and monitors only the specific parameter needed for call failure detection (connection status during initial call setup) rather than continuously monitoring all call parameters. This selective monitoring approach provides complete call failure data while minimizing battery consumption by avoiding unnecessary continuous monitoring of other call characteristics.
3Loss of time
If call information is sent after each call, then real-time feedback is provided, but network traffic increases
Solution Approach 1:
The software implements periodic reporting where call failure information is accumulated and sent to the carrier at scheduled intervals rather than after every single call. This periodic action reduces network traffic volume by batching multiple reports together, while still providing timely feedback for network quality assessment and maintenance operations.
Data Source
AI summary
A system, method and software application track call failures on a wireless phone. A software application on the phone monitors outbound calls made on the phone to determine whether or not a call fails. In one embodiment, such monitoring is done only for a select period of time (e.g., the initial few seconds when the phone is attempting to connect to a call to the wireless communication carrier's network), and, in an alternate embodiment, such monitoring is done for the duration of the call. If a call fails, the software application stores information related to the call. Examples of such types of information include the time the call failed, the location of the phone at call failure, and identification information for the phone. The stored call information is then sent to the wireless communication carrier to enable the carrier to assess network quality.