Map-Agnostic Navigation Routing via Midpoint Encoding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing navigation systems face challenges in providing accurate routing instructions when the end-user's map version differs from the server's version, leading to performance issues and the need for multiple map versions to be stored, which consumes server space and complicates maintenance.
Innovation Solution
Implementing a midpoint-based or decision-based map-agnostic navigation routing system that encodes routes using geographic data such as latitude and longitude values at midpoints or decision points, allowing for compatibility with different map versions and enabling frequent updates without storing older versions on the server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple map versions are stored on the server to support different end-user map versions, then routing compatibility with various end-users is improved, but server storage space is consumed and maintenance complexity increases
Solution Approach 1:
The patent extracts the map version dependency from the routing instructions by using map-agnostic IDs that reference road segments in a version-independent manner. This allows the server to store only the current map version while maintaining compatibility with older versions through the version-agnostic routing identifiers.
Solution Approach 2:
The routing instructions use universal map-agnostic IDs that can be interpreted by both current and historical map versions. These IDs serve multiple purposes: they work with the current server map version, are compatible with older end-user map versions, and enable future-proof routing without requiring version-specific identifiers.
2Adaptability or versatility
If multiple map versions are stored on the server to support different end-user map versions, then routing compatibility with various end-users is improved, but maintenance complexity increases
Solution Approach 1:
The patent extracts the version compatibility burden from the routing instruction management by using version-agnostic identifiers. This eliminates the need to maintain and synchronize multiple map versions on the server, significantly reducing maintenance complexity while preserving routing compatibility.
Solution Approach 2:
Instead of adapting routing instructions to match different end-user map versions (which requires maintaining multiple versions), the patent inverts the approach by creating routing instructions that adapt to work with any map version through version-independent identifiers.
3Reliability
If map versions are stored for four years with quarterly updates to support historical routing, then routing accuracy for historical routes is improved, but server storage space is consumed
Solution Approach 1:
The patent extracts the historical map data requirement by using map-agnostic IDs that can resolve to road segments in any map version. This enables the server to store only the current map version while maintaining the ability to provide accurate routing for historical routes through version-independent references.
Solution Approach 2:
The routing system uses dynamic resolution of map-agnostic IDs that can adapt to different map versions at runtime. This allows the same routing instruction to work whether the end-user has an old or new map version, eliminating the need to store historical map data.
Data Source
AI summary
Systems, apparatuses, and methods are provided for determining a navigation route. A route is requested by a navigation device between a starting location and a destination location. The route request is received by an external processor for analysis. A navigation route is determined by the external processor and its associated map version. The determined navigation route is then encoded with geographic data for each path segment along the route. The encoded navigation route is transmitted to the navigation device.