IMS Mute Event Tracking via SIP BYE for Network Root-Cause Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional mobile devices terminate voice communications automatically upon detecting network-related mutes without providing the core network with information about mute events that do not reach a predetermined threshold duration, leading to incomplete data on user-initiated terminations and poor network performance.
Innovation Solution
Mobile devices are configured to track mute-related information, such as RTP packet loss, and report this information to the IMS stack, which includes it in SIP BYE messages, allowing the core network to receive crowd-sourced data on mute events, enabling pattern recognition and potential root-cause identification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If mobile devices automatically terminate voice communications upon detecting network-related mutes without reporting, then device operation is simplified and termination speed is improved, but network data completeness deteriorates and network performance worsens
Solution Approach 1:
The patent implements a feedback mechanism where mobile devices report mute event information to the core network via SIP BYE messages. The disruption tracker monitors RTP packet loss and communicates this data back to the network, allowing the network to learn from device-side observations and improve overall service quality based on aggregated feedback from multiple devices.
Solution Approach 2:
The patent performs preliminary tracking of mute-related information (RTP packet loss) before session termination occurs. The disruption tracker continuously monitors network conditions and prepares disruption reports in advance, so that when a session is terminated—whether automatically or by user action—the network already has the necessary data to analyze patterns and identify root causes.
2Loss of information
If mobile devices track and report all mute-related information to the IMS stack, then network data completeness is improved and network performance is enhanced, but device complexity increases
Solution Approach 1:
The patent leverages existing device components to perform tracking functions, reducing the need for entirely new hardware or software subsystems. The disruption tracker utilizes the device's existing RTP processing capabilities and session management infrastructure to monitor and report disruptions, allowing the device to serve its own monitoring needs using resources already allocated for communication functions.
Solution Approach 2:
The disruption tracker and reporting mechanism are designed to work within the existing IMS protocol stack, which already handles session management, signaling, and communication protocols. By integrating the tracking functionality into the multi-functional IMS architecture rather than creating a separate system, the patent achieves data collection without proportionally increasing device complexity.
Data Source
AI summary
Systems and methods for tracking and logging mute events that occur during communication sessions are disclosed. The method includes generating a disruption report that includes one or more aspects of a mute event detected during a communication session. The disruption report is communicated to a network for further analysis.