Mobile Device Location API with Backup Source Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices with resource limitations, such as reduced memory capacity, face inefficiencies in determining location due to the need for multiple processing threads, which consume unnecessary power and shorten battery life.
Innovation Solution
A method that interfaces a mobile device and an application virtual machine to provide location information from a secondary source efficiently, using a primary location component, verification component, and backup location component to validate and retrieve location data in a single request, reducing the need for new processing threads and power consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple processing threads are used to retrieve location information from secondary sources, then location information can be obtained from multiple sources, but power consumption increases and battery life decreases
Solution Approach 1:
The system pre-loads and caches configuration parameters for secondary location sources during device initialization or idle periods. When location information is needed, the cached parameters are used directly without spawning new threads, thus maintaining reliable multi-source location retrieval while avoiding the power consumption penalty of thread creation and parameter loading at runtime.
2Adaptability or versatility
If multiple processing threads are spawned to collect configuration parameters, then location information from secondary sources can be retrieved, but device complexity and processing overhead increase
Solution Approach 1:
The system combines the retrieval of location information and configuration parameters into a single integrated process. Instead of spawning separate threads for parameter collection and location data retrieval, the system uses a unified thread that accesses pre-cached parameters, thereby maintaining adaptability to multiple location sources while significantly reducing processing complexity and thread management overhead.
3Measurement precision
If configuration parameters are loaded each time secondary location method is used, then accurate location information can be obtained, but unnecessary processing consumes power and shortens battery life
Solution Approach 1:
Configuration parameters for secondary location sources are loaded and cached in advance during device initialization or idle periods. When location information is required, the system uses these pre-loaded parameters without reloading them, thus maintaining measurement precision for accurate location determination while eliminating the unnecessary power consumption associated with repeated parameter loading.
Data Source
AI summary
Media, methods and interfaces are provided for interfacing a mobile device and an application virtual machine to provide location information of the mobile device from a secondary source. When location information supplied by a first source to the application virtual machine contains invalid values for device location, a secondary source is utilized to provide the location information. No new processing thread is spawned for collection of back-up source configurations. Thus, interfaces initiate the first and second location determination methods in a single request. The power consumed by the mobile device to retrieve the device location information from a secondary source is reduced by the absence of additional configuration collection threads. Interfaces include a primary location component, a verification component, a backup location component, and a location update component.


