Mobile Call State Tracking for Device-Side Drop Diagnosis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network monitoring systems fail to detect device-side issues causing call failures and drops, leading to undetected root causes and inefficient resource allocation.
Innovation Solution
Implementing a method on mobile devices to track call states and reasons for disconnection or failure by utilizing operating system APIs, such as PreciseCallState and ImsReasonInfo, to identify device-side issues like modem failures and software problems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional network monitoring systems are used, then network performance can be monitored at a basic level, but device-side issues causing call failures and drops remain undetected
Solution Approach 1:
Instead of only monitoring network-side parameters, the patent inverts the approach by implementing monitoring on the device side (mobile device) to capture call state transitions and disconnection reasons. This inversion enables detection of device-side issues such as modem failures and software problems that conventional network-side monitoring cannot detect.
Solution Approach 2:
The patent introduces an intermediary monitoring application layer on the mobile device that bridges the gap between device operations and network monitoring. This intermediary captures detailed call state information and disconnection reasons through operating system APIs, enabling comprehensive monitoring of both network and device-side factors.
2Measurement precision
If device-side monitoring is implemented, then root causes of call failures can be identified, but system complexity increases
Solution Approach 1:
The monitoring application leverages existing multi-functional operating system APIs (such as telephony frameworks and IMS components) that already handle call management. By utilizing these universal APIs, the patent achieves precise measurement of call failure reasons without building separate complex monitoring infrastructure, thus reducing overall system complexity.
Solution Approach 2:
The patent implements self-service monitoring where the mobile device's own operating system and telephony frameworks provide the monitoring capabilities through their existing APIs. The device monitors its own call states and disconnection reasons internally, eliminating the need for external complex monitoring systems and reducing overall system complexity.
3Reliability
If comprehensive call state tracking is performed, then device-side issues can be detected, but data processing requirements increase
Solution Approach 1:
The patent extracts only the essential information needed for reliability analysis - specifically call state transitions and disconnection reasons - from the comprehensive device state space. By focusing monitoring on these critical parameters through targeted API calls, the system achieves high detection accuracy while minimizing data processing energy consumption compared to comprehensive state tracking.
Data Source
AI summary
A computer-implemented method for tracking calls attempted or established between a mobile device and a radio access network includes: receiving, using a first function registered with an operating system of a mobile device, information indicative of a transition of a call state associated with a voice call associated with the mobile device from a first state to a second state, determining, based on the information, that the first state is an active state and the second state is a disconnected state, responsive to determining that the first state is an active state and the second state is a disconnected state, receiving, using a second function registered with the operating system, information indicative of a reason for disconnection of the voice call, and identify, based on the information indicative of the reason for the disconnection of the voice call, a device-side issue responsible for the disconnection of the voice call.