Navigation Device Map Database Data Structure Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for generating map data in information terminal devices face challenges in data extensibility when adding or deleting attribute values, as they require updating the component data, leading to inefficiencies in data access and management.

Innovation Solution

The solution involves an information terminal device with a map database that stores feature information, attribute information, and relation information, where attribute holding type information indicates the presence or absence of attribute data, allowing flexible association and efficient data access by separating feature and attribute data lists and using relation information to manage attribute data presence and type.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If attribute information is embedded inside component information, then data structure is simple, but data extensibility deteriorates when adding or deleting attribute values

Engineering Contradiction:
Improvedata structure complexityVSAvoiddata extensibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent divides the data structure into three separate lists: a component information data list, an attribute information data list, and a relation information data list. This segmentation allows attribute information to be stored independently from component information, enabling flexible addition and deletion of attributes without requiring updates to component data structures. Each list can be managed and modified independently, resolving the contradiction between structural simplicity and data extensibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a relation information data list that acts as an intermediary between component information and attribute information. This intermediary contains association information that links components to their attributes through indices, allowing the system to maintain simple component data while enabling flexible attribute management. The relation list mediates the connection without requiring embedded structures, solving the extensibility problem.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If attribute information is stored separately from component information, then data extensibility is improved, but data access efficiency deteriorates

Engineering Contradiction:
Improvedata extensibilityVSAvoiddata access efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent performs preliminary organization of data by sorting both component information and attribute information in ascending order based on their respective indices. The relation information data list is also pre-configured with proper index associations. This preliminary sorting and organization enables efficient data access without requiring complex search algorithms, resolving the contradiction between separate storage and access efficiency.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If flag information is embedded inside each component to indicate attribute presence, then attribute presence can be tracked, but data structure complexity increases and extensibility decreases

Engineering Contradiction:
Improveattribute presence trackingVSAvoiddata structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the flag information from individual component records and consolidates it into a separate attribute information data list. The presence or absence of attributes is tracked through the structure of this separate list rather than through embedded flags within component data. This extraction eliminates the need for additional flag fields in component records, maintaining reliability while reducing data structure complexity and improving extensibility.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS9933267B2Navigation device and navigation method
Publication Date: 2018.04.03 MITSUBISHI ELECTRIC CORP
  • US9933267B2 patent drawing
  • US9933267B2 patent drawing
  • US9933267B2 patent drawing

AI summary

Map data is managed by being divided into a geometric information data list of pieces of geometric information or a phase information data list of pieces of phase information, an attribute information data list of pieces of attribute information, and a relation information data list of pieces of relation information each indicating a relation between the geometric information or the phase information and the attribute information. The pieces of attribute information in the attribute information data list are arranged in the order corresponding to the pieces of geometric information or phase information which are feature information, and the pieces of relation information are arranged in the order corresponding to the pieces of geometric information or phase information which are feature information.