Vehicle Identifier Reuse Across Repair Software Activation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Vehicle technicians are required to repeatedly enter vehicle identification data for different software executables during a repair session, leading to inefficiencies in time and data entry errors.

Innovation Solution

A method and system that determines vehicle identification information (VII) once and uses it to generate specific vehicle identifiers for software executables, allowing these identifiers to be retrieved and provided automatically during activation, reducing the need for repeated data entry.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If vehicle technicians enter vehicle identification data for each software executable separately, then each software can be activated with the correct vehicle identifier, but the process becomes time-consuming and prone to data entry errors

Engineering Contradiction:
Improveaccuracy of vehicle identifier entryVSAvoidtime for data entry
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by determining and storing the vehicle identifier once at the beginning of the repair session. This pre-determined identifier is then automatically provided to multiple software executables, eliminating the need for repeated manual entry and reducing both time loss and errors.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies universality by making the vehicle identifier determination process serve multiple functions. A single vehicle identifier is generated and then reused across multiple different software executables (scan tool, DVOM, etc.), allowing one identification process to support multiple diagnostic and repair tools simultaneously.

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

2Ease of operation

If vehicle identification data is entered manually for each software executable, then each program can be properly activated, but the complexity of the repair process increases

Engineering Contradiction:
Improvesimplicity of software activationVSAvoidcomplexity of activation process
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system applies self-service by automatically providing the vehicle identifier to software executables without requiring manual re-entry. The computing device itself generates and manages the identifier, and the software executables automatically receive it during activation, making the process simpler and reducing operational complexity.

Inventive Principle:
Principle #25Self-service

3Stability of the object's composition

If the same vehicle identifier is used across multiple software executables, then data consistency is improved, but the ability to provide software-specific identifiers is reduced

Engineering Contradiction:
Improveconsistency of vehicle identifier dataVSAvoidflexibility of identifier assignment
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent applies segmentation by dividing the vehicle identifier into multiple distinct identifiers, each tailored for specific software executables. The system takes the base vehicle identification data and segments it into software-specific identifiers (e.g., different formats for scan tools versus DVOM), maintaining data consistency while providing the adaptability needed for different applications.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12585664B2System and method for accessing vehicle communication applications requiring vehicle identification without re-entering vehicle identification
Publication Date: 2026.03.24 SNAP ON INC
  • US12585664B2 patent drawing
  • US12585664B2 patent drawing
  • US12585664B2 patent drawing

AI summary

Methods and apparatus are provided for repairing vehicles. A computing device having first and second software executables can determine vehicle identification information (VII) that identifies a vehicle. The computing device can store first and second vehicle identifiers that are based on the VII and are respectively associated with the first and second software executables, where the first vehicle identifier differs from the second vehicle identifier. The computing device can be used to repair the vehicle by at least: receiving a request to activate the first software executable, and activating the first software executable at least by providing the stored first vehicle identifier to the first software executable.