Map Data Management Predicting Mesh Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Map data management systems often fail to provide the latest data to in-vehicle applications due to delayed updates, leading to the mixing of old and new data, which can cause operational issues, especially with high-definition map data that requires longer download times.

Innovation Solution

A map data management apparatus that predicts which mesh data will be requested by the application, identifies outdated data, and performs immediate or deferred updates based on the application's operational conditions to ensure timely and accurate data provision.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If map data is updated immediately when requested, then the latest map data is provided to the application, but old and new map data may be mixed when updates take too long

Engineering Contradiction:
Improvedata consistencyVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by predicting which mesh data will be requested by the application before the actual request occurs. The map update controller identifies update-necessary meshes in advance and prepares updates for these predicted meshes, ensuring that when the application requests the data, the latest version is already available or will be ready without causing data mixing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts the update timing based on real-time conditions. The map update controller determines whether to perform immediate updates or deferred updates by evaluating whether the predicted mesh update can be completed before the application's actual request. This dynamic decision-making ensures data consistency while optimizing update timing based on current system state and predicted usage patterns.

Inventive Principle:
Principle #15Dynamics

2Manufacturing precision

If high-definition map data is downloaded, then detailed road information is provided, but the download time increases significantly

Engineering Contradiction:
Improvemap data detailVSAvoiddownload time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system performs preliminary downloads of high-definition map data for predicted meshes before the application actually needs them. By predicting which meshes will be requested and downloading their high-definition data in advance, the system ensures detailed map information is available when needed without causing delays in application operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies different quality levels of map data to different regions based on predicted usage. Instead of uniformly downloading high-definition data for all meshes, the system selectively downloads detailed map data only for predicted meshes that are likely to be requested, maintaining high data quality where needed while reducing overall download time and resource consumption.

Inventive Principle:
Principle #3Local quality

3Reliability

If mesh identification for updates is performed thoroughly, then all outdated data is found, but the identification time increases

Engineering Contradiction:
Improveupdate completenessVSAvoidupdate speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary identification of update-necessary meshes by comparing stored map data versions with the latest available versions for predicted meshes. This preliminary identification is done efficiently by focusing only on predicted meshes rather than all meshes, ensuring that when updates are performed, they are complete for the relevant data while maintaining fast identification speeds.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system performs identification and update preparation for a slightly larger set of predicted meshes than strictly necessary, ensuring that all potentially needed data is updated. This approach may identify a few more meshes than minimum required, but ensures complete update coverage for all actually requested data without significantly increasing identification time.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20230358560A1Map data management apparatus and map data management method
Publication Date: 2023.11.09 MITSUBISHI ELECTRIC CORP
  • US20230358560A1 patent drawing
  • US20230358560A1 patent drawing
  • US20230358560A1 patent drawing

AI summary

A map update controller of a map data management apparatus predicts meshes whose pieces of map data will be requested from a map application, and identifies meshes whose pieces of map data stored in the map database are not latest as update-necessary meshes, from among the predicted meshes whose pieces of map data will be requested. The map update controller performs a first map update process of immediately updating pieces of map data of the update-necessary meshes when the pieces of map data of the update-necessary meshes can be updated before the map application requests the pieces of map data of the update-necessary meshes, and performs a second map update process of updating the pieces of map data of the update-necessary meshes at the timing that an operation of the map application satisfies a predefined condition when the pieces of map data cannot be updated.