Vehicle Identification Key for Multi-Application Diagnostics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing motor vehicle diagnostic systems require repetitive entry of vehicle information when switching between multiple test applications, making the process inconvenient and time-consuming.

Innovation Solution

A diagnostic system that generates a vehicle identification key containing essential vehicle information, allowing seamless access to multiple applications without the need for re-entering data, by storing this key in local storage and providing it to each application as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If vehicle information is re-entered for each application, then data accuracy is maintained, but time consumption increases

Engineering Contradiction:
Improvetime consumptionVSAvoiddata accuracy
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system performs preliminary action by storing the vehicle identification key after the first application retrieves it. This pre-stored key is then automatically provided to subsequent applications, eliminating the need for re-entry while maintaining data consistency through the standardized key structure defined in the first application.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The vehicle identification key is copied from the first application's data structure and stored in a format that can be reused by multiple applications. This copying mechanism allows the same identification data to be efficiently reused across different applications without re-entry, reducing time consumption while preserving data accuracy.

Inventive Principle:
Principle #26Copying

2Productivity

If a vehicle identification key is stored for reuse, then operational efficiency improves, but system complexity increases

Engineering Contradiction:
Improveoperational efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system extracts the essential vehicle identification information from the complete application data structure and stores only the necessary identification key. This extraction approach improves operational efficiency by storing and reusing only the critical identification data, while minimizing system complexity by avoiding storage of redundant information.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The vehicle identification key serves as an intermediary between multiple applications and the vehicle identification data. This intermediary simplifies the system architecture by providing a standardized interface that applications can use to access vehicle identification information without direct complex interactions, thereby improving efficiency while managing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If multiple applications share the same identification key, then user convenience improves, but data security risks increase

Engineering Contradiction:
Improveuser convenienceVSAvoiddata security risks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system applies local quality by providing the vehicle identification key to each application based on its specific needs and authorization level. Rather than universally sharing the key with all applications, the system selectively provides the key to authorized applications, thereby improving user convenience through automated identification while mitigating security risks through controlled access.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS7684908B1Vehicle identification key for use between multiple computer applications
Publication Date: 2010.03.23 SNAP ON INC
  • US7684908B1 patent drawing
  • US7684908B1 patent drawing
  • US7684908B1 patent drawing

AI summary

A vehicle diagnostic system including a processor, a user interface including a display device and an input device both coupled to the processor for interactive control thereof and thereby, and a local storage library connected to the processor for storing at least one application to be performed on a vehicle. The processor is programmed to request vehicle identification information from a user through the display device, create a particular configuration identifier containing the vehicle identification information entered by the user through the input device, store the particular configuration identifier in the local storage library, retrieve at least one application from the library as the application is selected by the user through the input device, and provide the particular configuration identifier to the application.