Vehicle Telematics Compatibility Workflow for Accurate OBD Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern vehicles face challenges with incompatibility issues between telematics devices and on-board electronic systems, leading to inaccurate telematics data, which can result in unreliable user experiences and potential damage to vehicles or devices.

Innovation Solution

A telematics platform performs a compatibility workflow that assesses telematics data for compatibility using pre-established data from vehicle-telematics device interactions, user-reported data, and vehicle-specific information, activating or deactivating interactions based on compatibility, and informs users of incompatibilities, thereby ensuring data accuracy and reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a telematics device interfaces with an on-board electronic system using OBD link, then telematics data can be obtained, but incompatibility issues may arise leading to inaccurate telematics data

Engineering Contradiction:
Improvetelematics data accuracyVSAvoidvehicle-telematics device compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs compatibility assessment before fully activating the telematics device interaction. The telematics service evaluates compatibility data from vehicle profiles, previously reported telematics data, and user reports to determine if the device-vehicle pairing is compatible before allowing data collection, thereby preventing inaccurate data generation

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors telematics data quality and compatibility status, providing feedback to activate or deactivate interactions. When incompatibility is detected through data validation or user reports, the system deactivates the interaction to prevent further inaccurate data collection, and can reactivate it when compatibility is confirmed

Inventive Principle:
Principle #23Feedback

2Measurement precision

If compatibility assessment is performed using pre-established data from vehicle populations, then data accuracy is improved, but system complexity increases

Engineering Contradiction:
Improvecompatibility assessment accuracyVSAvoidcompatibility workflow complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system combines multiple data sources including pre-established compatibility data from vehicle profiles, previously reported telematics data from population of vehicles, and user-reported compatibility issues into a unified compatibility assessment process. This integrated approach improves assessment accuracy while managing complexity through centralized processing at the telematics service

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The telematics service acts as an intermediary between the telematics device and the on-board electronic system, performing compatibility assessments and managing activation/deactivation based on multiple data sources. This intermediary layer handles the complexity of evaluating vehicle profiles, population data, and user reports without burdening the device or vehicle system

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If real-time compatibility monitoring is implemented, then data reliability is enhanced, but loss of time in processing increases

Engineering Contradiction:
Improvetelematics data reliabilityVSAvoidcompatibility workflow time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs initial compatibility assessment using pre-established data from vehicle profiles and population statistics before runtime operations begin. This preliminary evaluation prepares compatibility status in advance, reducing processing time during actual telematics operations while maintaining reliable data quality monitoring

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements periodic compatibility monitoring rather than continuous real-time assessment. Compatibility is evaluated at scheduled intervals and triggered events (such as when incompatibility is detected), balancing data reliability with processing time efficiency by not constantly monitoring when no issues are present

Inventive Principle:
Principle #19Periodic action

4Measurement precision

If incompatibility detection leads to deactivation of interactions, then data accuracy is maintained, but loss of information occurs

Engineering Contradiction:
Improvetelematics data accuracyVSAvoidtelematics data availability
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The system dynamically adjusts interaction activation status based on detected compatibility issues. When incompatibility is detected, the interaction is temporarily deactivated to prevent inaccurate data collection, but can be reactivated when compatibility is confirmed through further assessment or user verification, allowing flexible information management

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system converts the potential harm of incompatibility (inaccurate data) into a benefit by using detected incompatibilities to improve the overall compatibility model. User-reported compatibility issues and detected problems are fed back to update vehicle profiles and population data, improving future compatibility assessments and data accuracy

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

Data Source

PatentEP3632141B1Vehicle telematics compatibility
Publication Date: 2023.11.15 MOJ IO INC
  • EP3632141B1 patent drawingFigure 1
  • EP3632141B1 patent drawingFigure 2
  • EP3632141B1 patent drawingFigure 3

AI summary

A telematics platform including a telematics service and a telematics device interfacing with an on-board electronic system of a vehicle, performs a compatibility workflow with respect to the vehicle-telematics device compatibility and data accuracy. The compatibility workflow may include multiple phases in which telematics data is assessed for compatibility or inaccuracies based on pre-established compatibility data obtained from a population of other vehicle-telematic device interactions, user-reported compatibility data, and vehicle-specific compatibility data. Incompatibility or inaccuracies in telematics data may be used to activate/deactivate or continue/discontinue interactions between the vehicle and the telematics device, and to inform users of the incompatibility of the vehicle-telematics device pair, or inaccuracies in the telematics data.