Middleware Location Data Adaptation for Mobile Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing location-based services require users to manually configure their devices to convert location data into standard formats, which is inconvenient and prone to errors, especially when the device's location precision does not match the application's requirements, leading to irrelevant data being provided.
Innovation Solution
A network-based system that identifies the device's capabilities and generates requests for location reports in appropriate formats, processes the data to select relevant information, and transmits it to the user without prior registration or configuration, allowing for real-time updates and dynamic data adaptation based on location changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the device converts position data to standard format using manual configuration, then the location data can be recognized by mapping applications, but the process becomes inconvenient and error-prone, requiring software downloads and precise precision matching
Solution Approach 1:
The system enables self-service by allowing the device to automatically determine its position using built-in position finding capabilities without requiring manual configuration or conversion of coordinates. The device independently queries the central database and receives location-related information without user intervention in the data format conversion process.
Solution Approach 2:
A central database acts as an intermediary between the device and the mapping application. The database receives position data from the device in any format, performs the necessary coordinate conversions and precision adjustments, and returns location-related information without requiring the device to have conversion capabilities.
2Productivity
If the device reports location at regular intervals to a central database, then real-time tracking information can be provided, but the system requires dedicated configuration and specific data formats
Solution Approach 1:
The central database provides universal functionality by accepting position data from devices regardless of their specific capabilities or data formats. The database can serve multiple functions: tracking valuable cargoes, monitoring public transport vehicles, and providing location-based information services, all through a single standardized interface.
Solution Approach 2:
The device leverages its existing position finding system to automatically report location without requiring dedicated configuration for tracking services. The device independently determines its position and transmits it to the central database, which processes the data and provides relevant information without requiring the device to understand the application context.
3Duration of action of stationary object
If in-vehicle navigation systems use on-board mapping databases, then location information can be accessed without communication connection, but the database cannot be updated dynamically to reflect infrastructure changes
Solution Approach 1:
The system pre-loads location-related information into the central database based on position data from devices. This allows the database to proactively prepare and store relevant information about services, facilities, and infrastructure in advance, making it available when devices query their current location without requiring real-time communication connections.
Solution Approach 2:
The system continuously receives position data from devices and uses this feedback to update and refine the location-related information in the central database. This allows the database to adapt to infrastructure changes, new services, and evolving user needs by incorporating real-world position data and updating its information accordingly.
Data Source
AI summary
Requests (94) for location-dependant information, received from a mobile device (1) having a location-finding capability (10), are processed by middleware (4, 40) which identifies the handset type and generates instructions (93, 95) specific to the handset type to provide the data (94, 97) required to generate the required data (99) in a format compatible with the handset (1).