Synchronized Changing Beacons for Continuous Mobile App Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices face challenges in maintaining continuous application execution due to operating system restrictions, which can lead to unauthorized access and inefficient user experience in scenarios like entry access, where beacons are used to trigger applications but may result in unwanted access or application closure.
Innovation Solution
Implementing a system of synchronized changing beacons that trick the operating system into thinking the mobile device has moved between different transmitters, allowing continuous application execution without user interaction and overcoming OS restrictions on beacon usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Duration of action of moving object
If the OS allows an application to execute continuously in response to beacon triggers, then the application can maintain continuous operation for seamless user experience, but the OS restrictions prevent the application from running indefinitely to manage power usage and resources
Solution Approach 1:
The system uses periodic beacon transmissions at defined intervals to trigger application execution. The beacon transmitter sends beacons continuously at set intervals, and the mobile device wakes the application periodically based on these beacons, allowing the application to execute in periodic bursts rather than continuously, thus maintaining functionality while managing power consumption.
Solution Approach 2:
The application is pre-configured with beacon identifiers and execution parameters before runtime. When a beacon is received, the application is already prepared to execute immediately, eliminating the need for lengthy initialization processes and allowing quick start-stop cycles that conserve power while maintaining operational readiness.
2Ease of operation
If the OS prevents an application from restarting within a defined interval after being closed, then power consumption is reduced, but the application cannot respond to subsequent beacons until the interval expires
Solution Approach 1:
The system dynamically adjusts application execution based on beacon reception. Instead of a fixed restart interval, the application can be restarted immediately when new beacons are received, making the execution pattern adaptive rather than static. This allows the application to remain responsive to beacon triggers while still managing resources efficiently.
3Device complexity
If a single beacon transmitter is used to trigger application execution, then the system is simple to implement, but the application may be closed by the OS after one execution cycle
Solution Approach 1:
The system segments the beacon transmission function across multiple beacon transmitters distributed in different locations. Each transmitter independently sends beacons that can trigger the same application, providing redundancy and ensuring continuous execution capability even if one transmitter is unavailable or the device moves between locations.
4Productivity
If the OS restricts beacon usage to once per interval, then power consumption is controlled, but seamless continuous operation for entry access scenarios cannot be achieved
Solution Approach 1:
The beacon system is designed to support multiple functions: it can trigger application execution for entry access, provide location-based services, and enable various other beacon-driven functionalities. The same beacon infrastructure serves multiple purposes, maximizing the utility of the power consumption and enabling seamless operation across different use cases.
Data Source
AI summary
One or more beaconing devices transmit synchronized changing beacons. The changing beacons trigger execution of an application that is installed but closed or not running on a mobile device, that is in wireless beaconing range of a beaconing device, and that has registered the changing beacons with the mobile device operating system (“OS”) to trigger execution of the application upon receipt of the changing beacons. The changing beacons also keep the executing application running by resetting OS policies for closing the application when it is running with the mobile device in a locked or standby state. The application may perform different procedures and different times with the beaconing device or other devices including authorizing access to a secured resource when the mobile device is far away from the beaconing device, and confirming intent to access the secured resource when the mobile device is close to the beaconing device.


