Coordinated Map Versioning for Autonomous Navigation Continuity

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional map updating systems for autonomous vehicles face issues with batch processing and compatibility, leading to machine disengagements and errors when new map versions are published while previous versions are still in use.

Innovation Solution

A system that strategically publishes and stores compatibility information for different map versions, allowing simultaneous use of new and old versions to reduce disengagements by maintaining compatibility data across regions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If new map versions are published while previous versions are still in use, then map updates can be performed continuously, but machine disengagements and errors occur

Engineering Contradiction:

Improvemap update frequencyVSAvoidnavigation stability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system segments map data into multiple versions (current and previous) and maintains them separately in the map database. Each map version is independently stored with version identifiers, allowing the system to serve different versions to different vehicles based on their capabilities and update timing, thus preventing errors while maintaining high update frequency

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by publishing new map versions to the database before all vehicles have finished using previous versions. The compatibility data structure is prepared in advance to handle version mismatches, allowing continuous updates without waiting for complete version transitions across all vehicles

Inventive Principle:

Principle #10Preliminary action

2Device complexity

If batch processing is used for map updates, then system complexity is reduced, but update time increases

Engineering Contradiction:

Improveupdate system complexityVSAvoidmap update delay

Core Design Contradiction:

Device complexityVSLoss of time

Solution Approach 1:

The system transitions from static batch processing to dynamic incremental updates. Map portions are updated individually as changes are detected, with each update immediately reflected in the database. The compatibility data structure dynamically tracks which vehicles need which versions, enabling real-time updates without complex batch coordination

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system performs preliminary actions by pre-computing and storing compatibility data in the database that indicates whether map portions are compatible across versions. This preliminary preparation allows new map portions to be published immediately without waiting for batch processing completion, reducing update delay while maintaining manageable system complexity

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20250334424A1Coordinated map updating and versioning for autonomous systems and applications

Publication Date: 2025.10.30 NVIDIA CORP

AI summary

In various examples, updates may be published for maps used by machines to navigate an environment without restricting use of previous versions of the maps that remain valid. For example, a map for a region of an environment may be updated to a new version, and compatibility information for the new version of the map may be published. The compatibility information may indicate whether the new version of the map is compatible with other maps for other regions. Additional compatibility information for the other maps may also be updated to indicate whether those other maps are compatible with the new version of the map and/or the previous versions of the map. In some examples, an index may be updated to indicate the new version of the map is the most current version, and the new version of the map may be made available for use by the machines.