Mobile Third-Party Callbacks Using Proximity and Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to provide convenient and accurate methods for users to request third-party services on mobile devices, particularly when the precise timing of service need is uncertain, and there is a risk of accidental service requests.
Innovation Solution
A computer-implemented method for performing third-party callbacks on a mobile device after a triggering event is detected by a remote device, with proximity determination and authentication to ensure accurate service requests, including biometric authentication, geographical location, and input commands.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the mobile device performs third-party callbacks automatically after detecting a triggering event, then service request convenience is improved, but the risk of accidental service requests increases
Solution Approach 1:
The system performs preliminary actions by detecting triggering events (such as geo-fence entry, biometric authentication, or specific input commands) before automatically initiating the third-party callback. This ensures that the service request is triggered only by predetermined, intentional user actions rather than accidental device interactions.
Solution Approach 2:
The patent introduces an intermediary authentication mechanism between the triggering event detection and the callback execution. The system verifies whether the triggering event was intentional by checking for associated authentication events (biometric data, passcode entry) or specific input patterns, acting as a mediator to filter out accidental triggers.
2Productivity
If the user configures service requests in advance on the mobile device, then service request speed is improved, but the precision of service timing control deteriorates
Solution Approach 1:
The system dynamically adjusts the triggering conditions based on multiple factors including geographic location, time of day, device orientation, and recent user behavior patterns. This allows the pre-configured service request to be triggered at the precise moment when the user actually needs the service, rather than at a fixed predetermined time.
Solution Approach 2:
The patent changes multiple parameters simultaneously to determine the optimal trigger moment: geographic coordinates (geo-fence detection), temporal parameters (time of day, day of week), device state parameters (orientation, motion detection), and user behavior parameters (recent app usage patterns). This multi-parameter approach achieves both speed and precision in service timing control.
3Measurement precision
If the system implements proximity determination and authentication before performing callbacks, then service request accuracy is improved, but device complexity increases
Solution Approach 1:
The patent leverages existing multi-functional components already present in modern mobile devices: the camera and image processing algorithms serve both photography and biometric authentication functions; the accelerometer and gyroscope serve both gaming and geo-fence detection functions. This universal reuse of components improves service request accuracy without significantly increasing device complexity.
Solution Approach 2:
The system uses copies of authentication data (biometric templates, device fingerprints) stored securely in the device for rapid verification without requiring repeated physical authentication. The proximity determination uses copied location data from GPS/geo-fence systems already integrated into the device, enabling accurate service triggering with minimal additional complexity.
Data Source
AI summary
Aspects described herein may allow for deploying third-party callback to be performed on a mobile device. For example, the mobile device may configure a third-party callback to be performed after a triggering event is detected by a remote device. The triggering event may relate to a remote device associated with the mobile device. A determination may be made as to whether the mobile device is within a pre-determined proximity of the remote device. If the two devices are in proximity and if the mobile device receives a message that indicates the triggering event has been detected, the mobile device may perform the third-party callback. In this way, a user's need to request services conveniently and accurately is facilitated.