Runtime Vocabulary Engine for Vehicle Data Standardization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in compiling, integrating, and consistently accessing descriptive data for vehicles, particularly due to data availability and the need for multiple entities to access this data effectively.

Innovation Solution

A method and system utilizing a runtime vocabulary engine (RVE) that separates scripting language from the vocabulary engine, allowing dynamic generation of vehicle data outputs by using vehicle data from an enterprise vehicle database and data warehouse, with hash maps for efficient storage, enabling flexibility in network and web-based environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If descriptive data for vehicles is compiled and integrated, then data availability and consistency are improved, but system complexity and data management difficulty increase

Engineering Contradiction:
Improvedata availabilityVSAvoiddata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a vocabulary engine as an intermediary system between data sources and applications. This engine standardizes vehicle data by mapping various data formats to a common vocabulary structure, enabling consistent data access without requiring complex integration logic in each application. The vocabulary engine acts as a mediator that handles data heterogeneity centrally.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The vocabulary engine provides universal access to vehicle data through a standardized interface that can serve multiple applications and data sources. By creating a unified data representation layer, the system enables any application to access vehicle information consistently without needing application-specific data integration logic, thus reducing overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple entities access vehicle data, then data usability is improved, but data access consistency and control become more difficult

Engineering Contradiction:
Improvedata accessibilityVSAvoiddata access consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The vocabulary engine serves as a centralized intermediary that all entities must access through for obtaining vehicle data. This single entry point ensures consistent data access across all applications while maintaining data integrity and access control policies uniformly applied to all requests.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments data access into two independent parts: the vocabulary engine handles data retrieval and standardization, while applications handle interpretation and presentation. This segmentation allows multiple applications to access data consistently without interfering with each other, as each application interacts with the standardized vocabulary interface independently.

Inventive Principle:
Principle #1Segmentation

3Productivity

If scripting language is integrated with vocabulary engine, then functionality is improved, but system flexibility and adaptability decrease

Engineering Contradiction:
Improveoutput generation efficiencyVSAvoidsystem flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent extracts the scripting language from the vocabulary engine, separating the data standardization function from the output generation function. The vocabulary engine focuses solely on retrieving and standardizing data according to the vocabulary, while scripting languages can be independently selected and applied by different applications without affecting the core vocabulary engine functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

By separating the scripting language from the vocabulary engine, the system becomes dynamic and adaptable. Different applications can choose different scripting languages or output formats based on their specific needs while using the same vocabulary engine for data retrieval. This dynamic architecture allows the system to adapt to changing requirements without modifying the core vocabulary standardization logic.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8661032B2Vocabulary engine
Publication Date: 2014.02.25 AUTODATA SOLUTIONS
  • US8661032B2 patent drawing
  • US8661032B2 patent drawing
  • US8661032B2 patent drawing

AI summary

A system and method are provided for generating an output comprising data pertaining to a vehicle. A set of vehicle data pertaining to a selected vehicle is requested and the vehicle data is obtained from a database. The vehicle data is stored, e.g. using a hash map and a script generated outside of the system is obtained, which defines the structure of the output. The script is then run while using the vehicle data to generate the output and the output is provided to an application.