Odometer Monitoring with Redundant Storage for Rollback Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mileage rollback techniques, which falsify vehicle odometer readings, pose challenges for industries by affecting warranty claims, over-mileage fees, and residual vehicle value, necessitating a method to accurately monitor and detect such activities.

Innovation Solution

A system utilizing a computer processor to compare odometer values from a first and second storage system, calculating a reduction value to identify mileage rollback events, and storing relevant data, including date and location, to ensure accurate mileage tracking and prevent fraud.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single storage system is used for odometer data, then the system is simple and easy to operate, but the reliability is reduced due to potential data tampering or loss

Engineering Contradiction:
Improveodometer data integrityVSAvoidstorage system structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by creating different types of storage systems with different functions: a first storage system for primary odometer data and a second storage system for backup and comparison data. Each storage system has specialized characteristics optimized for its specific role in detecting mileage rollbacks.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements preliminary action by pre-storing odometer data in the second storage system before potential rollback events occur. This historical data is prepared in advance to enable comparison and detection of any future mileage manipulations.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If odometer data is monitored and compared between storage systems, then mileage rollback detection capability is improved, but the device complexity increases due to additional comparison and processing logic

Engineering Contradiction:
Improvemileage rollback detection accuracyVSAvoiddata processing system
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent implements feedback by continuously comparing odometer data from the first storage system against historical data from the second storage system. This comparison creates a feedback mechanism that automatically detects and flags any discrepancies indicating mileage rollback events.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent uses the second storage system as an intermediary element between the odometer and the detection logic. This intermediary stores historical data that mediates the comparison process, allowing the system to detect rollbacks without direct complex interaction between the odometer and analysis components.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If redundant storage systems are implemented for odometer monitoring, then data reliability and fraud detection improve, but the loss of energy increases due to additional reading, comparing, and storing operations

Engineering Contradiction:
Improveodometer value verificationVSAvoidprocessing energy consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies partial action by performing comparison operations only when necessary - specifically when odometer data is read from the first storage system. The system does not continuously compare all data points, but rather performs targeted comparisons to detect rollbacks while minimizing unnecessary energy consumption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9361739B2Odometer monitoring and redundant storage system
Publication Date: 2016.06.07 GM GLOBAL TECHNOLOGY OPERATIONS LLC

AI summary

A vehicle control system includes a computer and logic executable by the computer. The logic is configured to read an odometer value from a storage system. The odometer value corresponds to an accrued mileage obtained from an odometer. The accrued mileage is determined at a beginning of a current driving event. The logic is also configured to read an odometer value for the vehicle from another storage system. The odometer value from the other storage system corresponds to an accrued mileage obtained from the storage system at the beginning of a driving event that precedes the current driving event. The logic is further configured to compare the odometer value from the storage system to the odometer value from the other storage system and calculate a reduction value from the difference, upon determining the odometer value from the other storage system is greater than the odometer value from the storage system.