Web Browser Call Completion Detection via Timing Interval

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for detecting the outcome of a telephone call initiated from a mobile communication device, especially from an internet browser, lead to high resource consumption and compromise user privacy due to the need for active event listening and knowledge of phone numbers.

Innovation Solution

A method that uses a time counter initialized upon a click event, detects a predetermined event to stop the counter, and determines call success based on duration within a predetermined interval, all done without APIs, ensuring low resource usage and protecting user data confidentiality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If API-based solutions are used to detect call completion, then call outcome detection capability is provided, but processor and memory resource consumption increases significantly

Engineering Contradiction:
Improvecall outcome detection capabilityVSAvoidprocessor and memory resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The invention extracts only the essential timing information needed for call outcome detection (call start time and call end time) from the complex API-based solution. By using a simple timer that records only these two time points, the system eliminates the need for continuous event listening and complex API implementations, thereby dramatically reducing processor and memory resource consumption while maintaining reliable call outcome detection.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The invention uses a simple, lightweight timer object that creates minimal overhead compared to persistent API listeners and broadcast receivers. This disposable timing mechanism is created only when needed for call detection and discarded afterward, avoiding the continuous resource consumption associated with always-active API-based detection systems.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

2Reliability

If active event listening functions are implemented, then call completion detection is enabled, but CPU and memory consumption increases

Engineering Contradiction:
Improvecall completion detectionVSAvoidevent listening implementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The invention extracts only the essential timing information needed for call outcome detection (call start time and call end time) from the complex API-based solution. By using a simple timer that records only these two time points, the system eliminates the need for continuous event listening and complex API implementations, thereby dramatically reducing processor and memory resource consumption while maintaining reliable call outcome detection.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If APIs with access to phone numbers are used, then call detection functionality is provided, but user privacy and data confidentiality are compromised

Engineering Contradiction:
Improvecall detection functionalityVSAvoiduser privacy and data confidentiality risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The invention extracts only the essential timing information needed for call outcome detection (call start time and call end time) from the complex API-based solution. By using a simple timer that records only these two time points, the system eliminates the need for continuous event listening and complex API implementations, thereby dramatically reducing processor and memory resource consumption while maintaining reliable call outcome detection.

Inventive Principle:
Principle #2Taking out (Extraction)

4Adaptability or versatility

If broadcast receivers are constantly active to listen for incoming calls, then call detection is comprehensive, but CPU and memory consumption remains high even when calls are not initiated

Engineering Contradiction:
Improvecall detection coverageVSAvoidCPU and memory consumption during idle periods
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

Instead of continuous monitoring, the invention uses periodic timing checks. The timer is activated only when needed (when a call is initiated) and remains inactive during idle periods. This periodic approach maintains comprehensive call detection coverage while eliminating the continuous resource consumption associated with always-active broadcast receivers.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentEP3931691B1Method for detecting the completion of a telephone call initiated from a web browser of a mobile communication device
Publication Date: 2023.08.30 GNI MEDIA
  • EP3931691B1 patent drawingFigure 1
  • EP3931691B1 patent drawingFigure 2

AI summary

The invention concerns a method for detecting the completion of a telephone call initiated from a web browser of a mobile communication device, comprising an initial step (20) of detecting a click event on display data of a predetermined web page displayed via the web browser, the display data being relative to a telephone number; and a step (28) of establishing a telephone call between the mobile communication device and a terminal corresponding to the telephone number. The method further comprises the following steps - initialising a time counter upon detection (20) of the click event; detecting (30) a predetermined event; - stopping the time counter upon detection (30) of the predetermined event; - if the time period recorded by the time counter is within a predetermined time interval, determining (36) that the telephone call has been completed.