Unified Mobile Call Interface for VoIP and Native Calls
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Smartphone users experience a fragmented user experience when handling VoIP calls, as existing systems do not provide a unified interface for VoIP calls and traditional mobile calls, leading to inconsistencies and limitations in call management, especially when the device is locked or password-protected.
Innovation Solution
Implementing a unified user experience for mobile calls by invoking the native incoming call user interface for VoIP calls, allowing multiple calls to be hosted and switched between while the device is locked, and providing a full in-call experience when unlocked, with the VoIP application taking control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If VoIP applications manage their own in-call user experience independently, then VoIP call functionality is provided, but user experience consistency between VoIP calls and traditional mobile calls deteriorates
Solution Approach 1:
The patent merges the VoIP call management interface with the native mobile phone interface by allowing the native interface to remain visible and functional during VoIP calls. The VoIP application runs in the background while the native incoming call and in-call interfaces are displayed in the foreground, creating a unified user experience that combines both VoIP and traditional mobile call capabilities through a single consistent interface.
2Reliability
If the device locks during a VoIP call, then device security is maintained, but call management capability deteriorates
Solution Approach 1:
The system prepares and displays the native incoming call interface in advance when a VoIP call is incoming, even before the device is unlocked. This preliminary display of call information and controls allows the user to see and manage the call state immediately upon waking the device, rather than requiring full unlocking first, thus maintaining call management capability while preserving security.
Solution Approach 2:
The native mobile phone interface acts as an intermediary between the locked device state and the VoIP application. It provides a bridge that allows call management functionality to be accessed through the secure lock screen interface without requiring the VoIP application to be fully accessible, thus maintaining both security and call management capability.
3Duration of action of stationary object
If multiple calls are hosted while locked, then call continuity is maintained, but interface complexity increases
Solution Approach 1:
The native mobile phone interface is designed to be universal and multi-functional, handling both traditional mobile calls and VoIP calls through the same interface paradigm. This allows multiple calls from different sources (mobile network and VoIP applications) to be managed consistently through a single unified interface that the user already understands, avoiding the need for separate interfaces for different call types.
Data Source
AI summary
VoIP calls associated with VoIP applications installed on a mobile computing device are treated similar to calls not associated with installed VoIP applications. VoIP applications invoke the same native incoming call user interface that is invoked when a mobile device detects an incoming call that is not associated with an installed VoIP application. Mobile devices can simultaneously host a VoIP call and a call not associated with an installed VoIP application while a mobile device is locked. A reduced call user interface is displayed while a mobile device is simultaneously hosting multiple calls. Selection of the reduced call user interface causes the mobile device to make the active call the inactive call and vice versa. The reduced call user interface is managed by the mobile device operating system.