Server-Based Traffic Data Extraction for Mobile Navigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing navigation systems face challenges in providing real-time and relevant traffic information to drivers due to bandwidth limitations and the need for local storage and processing of large volumes of data, leading to latency and reduced information relevance.
Innovation Solution
A two-way communication system between a mobile device and a server that minimizes bandwidth usage by performing complex computations on the server, allowing for real-time traffic information retrieval and alternative route suggestions based on current conditions, preferences, and historical/predictive data, while enabling transactional billing for usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If traffic information is made available through traditional mechanisms (TV, radio, subscription services), then drivers can access traffic information, but the information is not personalized and requires significant bandwidth for comprehensive data
Solution Approach 1:
The patent extracts only the essential traffic information needed for route optimization from comprehensive traffic databases. The server retrieves and transmits only specific traffic data relevant to the requested route, rather than broadcasting all available traffic information, thereby reducing bandwidth consumption while maintaining information relevance.
Solution Approach 2:
The system provides traffic information customized to the specific route requested by the driver. Instead of providing generic traffic updates, the server analyzes the requested route and returns only the traffic information relevant to that path, making the information both personalized and bandwidth-efficient.
2Productivity
If navigation systems store and process large volumes of traffic data locally, then real-time route optimization is possible, but device complexity and processing requirements increase
Solution Approach 1:
The patent introduces a server as an intermediary between the mobile navigation device and the traffic database. The server performs complex data retrieval, analysis, and route optimization calculations, while the mobile device only handles simpler tasks like displaying results and receiving user inputs, thereby reducing device complexity.
Solution Approach 2:
The system divides functionality between server and mobile device. The server handles data-intensive operations (retrieving traffic information from databases, calculating alternative routes), while the mobile device handles user interaction and display. This segmentation reduces the processing burden on the mobile device.
3Loss of information
If comprehensive traffic information is transmitted to mobile devices, then drivers receive detailed traffic updates, but bandwidth requirements and data transmission time increase
Solution Approach 1:
The server extracts only the specific traffic information relevant to the requested route before transmission. Instead of transmitting comprehensive traffic databases, the system retrieves and sends only the necessary data segments, reducing transmission time while maintaining information completeness for the specific route.
Solution Approach 2:
The system performs preliminary route analysis and traffic data selection on the server before transmission to the mobile device. This preliminary processing ensures that only relevant data is transmitted, optimizing the balance between information completeness and transmission efficiency.
Data Source
AI summary
Two-way communication between a mobile device and a server is used to provide increased relevance of traffic information at lower bandwidth. The complexity, amount of storage and processing power required of the mobile navigation device are minimized, since the server performs much of the required computing. A transactional billing model can be used to bill the driver based on usage or consumption of traffic information. A driver selects a destination and routing preferences on a mobile device, and the local system generates a routing. The mobile device sends the planned route and preferences to a server. The server uses real-time traffic flow and incident information to determine an estimated driving time for the planned route. The server may also generate alternative routes, with an estimated time for each alternative route. The traffic and time information for the planned and alternative routes are then transmitted back to the mobile device.