Missed Call Rate Determination in OTT Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Determining a missed call rate for over-the-top (OTT) applications is challenging due to their operation in foreground or background modes and convoluted call routing paths, making it difficult to track key performance indicators (KPIs) effectively.
Innovation Solution
A method and system that involve a telephony application server (TAS) receiving a call invitation, forwarding it to a WebRTC node, and activating a response timer. The system logs response codes and reason headers in a call data record, regardless of the response type, and labels calls as 'not reachable' if no response is received within a predetermined time, allowing for the calculation of a missed call rate.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional cellular network KPI tracking methods are used for OTT applications, then network parameters can be monitored, but accurate missed call rate determination is impossible due to foreground/background operation modes and convoluted routing paths
Solution Approach 1:
The patent introduces a response timer as an intermediary mechanism between the call invitation sending and the missed call determination. This timer mediates the tracking process by providing a standardized time threshold for determining missed calls, simplifying the complex routing path analysis while maintaining accurate measurement.
Solution Approach 2:
The patent segments the call tracking process into distinct phases: call invitation sending, response timer activation, response reception/checking, and missed call determination. This segmentation allows each phase to be handled independently, reducing overall system complexity while improving measurement precision.
2Measurement precision
If response timing is not tracked, then the system is simpler to operate, but missed calls cannot be distinguished from other call states in OTT applications
Solution Approach 1:
The response timer is activated preliminarily immediately after the call invitation is sent, before the actual call response occurs. This preliminary action establishes a predetermined time threshold that automatically differentiates missed calls from other call states, improving measurement precision without requiring complex real-time analysis.
Solution Approach 2:
The system implements feedback by checking whether a response is received before the response timer expires. This feedback mechanism provides clear binary outcomes (response received/not received) that automatically differentiate call states, maintaining operational simplicity while achieving precise measurement.
3Measurement precision
If all call responses are logged without categorization, then data completeness is maintained, but missed call rate calculation becomes inaccurate
Solution Approach 1:
The patent applies local quality by categorizing call responses based on their specific characteristics: responses received before timer expiration are classified as successful calls, while responses received after expiration or no responses are classified as missed calls. This localized categorization ensures accurate missed call rate calculation while preserving necessary call response information.
Data Source
AI summary
Methods and systems for determining a missed call rate in an OTT application are provided. The method begins with receiving, at a telephony application server (TAS), a call invitation. The TAS then forwards the call invitation to a web real-time communications (WebRTC) node which sends the call to an OTT application. The TAS activates a response timer after forwarding the call invitation. Next, it is determined if a response to the call invitation is received before the expiration of the response timer. A response code and a reason header are logged in a call data record whether the response to the call invitation is an acceptance or a decline. If a response is not received by the TAS within a predetermined period of time, the TAS labels the call as “not reachable.” The information in the call data record allows determining a missed call rate for an OTT application.