Beacon Hardware Identifier Rotation for Background Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems fail to enable repeat detection of a beacon device at a location by a user computing device operating in the background, as they rely on static beacon device identifiers, which prevents continuous check-in status logging.
Innovation Solution
The system periodically changes the beacon device's hardware identifier, allowing the user computing device to detect and log the check-in status by generating new identifiers using a random number generator, enabling continuous communication even when the application operates in the background.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the beacon device uses a static hardware identifier, then the initial detection by the service application is reliable, but the repeat detection fails when the application operates in the background
Solution Approach 1:
The beacon device dynamically changes its hardware identifier from static to rotating at predetermined time intervals. This allows the system to adapt to different operational states of the user computing device, enabling background applications to detect the beacon by receiving updated identifiers that differ from the initial static identifier.
Solution Approach 2:
The beacon device periodically rotates its hardware identifier at predetermined time intervals while maintaining continuous operation at the same location. This periodic change in identifier allows the service application to detect the beacon device multiple times even when running in the background, as each rotation creates a new detectable signal.
2Reliability
If the service application operates in the foreground continuously, then repeat detection of the beacon device is enabled, but power consumption increases and user experience deteriorates
Solution Approach 1:
Instead of requiring continuous foreground operation, the system uses periodic identifier rotation by the beacon device. The service application can operate in the background with lower power consumption, detecting the beacon through periodic signals containing rotated identifiers, thus reducing energy usage while maintaining detection capability.
3Adaptability or versatility
If the beacon device broadcasts a rotating hardware identifier, then repeat detection by background applications is enabled, but the complexity of the beacon device increases
Solution Approach 1:
The beacon device incorporates a rotating identifier mechanism that dynamically changes the hardware identifier at predetermined intervals. This dynamic feature adds complexity to the beacon device, enabling it to provide updated identifiers that allow background applications to detect and re-detect the beacon without requiring continuous user interaction or foreground application operation.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A user enters a location with a user device. A beacon device broadcasts a first beacon device code comprising a hardware identifier via a local wireless network at the location. A service application of the user device receives the first beacon device hardware identifier, logs a check-in status of the user, and transmits the check-in status to a service provider system. The beacon device generates, after a predetermined period of time, a subsequent beacon device code comprising a random number to broadcast at the location via the local wireless network. In response to receiving the subsequent beacon device code broadcast by the beacon device, the user device logs and transmits a subsequent check in status to the service provider system via the network. The service provider system provides services to the user device or another device at the location in accordance with the check-in status of the user device.