Vehicle Feature Safety Updates With Distributed Ledger Effectiveness Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
It is difficult to determine the effectiveness of vehicle safety features and updates in preventing vehicle accidents due to variability in OEM-specific terminology and the lack of data on feature usage and accident records.
Innovation Solution
A system that translates OEM-specific terminology into a common language using an ontology model, analyzes vehicle build information and accident records to calculate effectiveness scores for safety features, and tracks updates using a distributed ledger.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If OEM-specific terminology is used for vehicle safety features, then each OEM can describe its features with precise proprietary language, but it becomes difficult to compare effectiveness across different manufacturers and track updates consistently
Solution Approach 1:
The patent introduces a distributed ledger as an intermediary data structure that stores standardized vehicle feature information independent of OEM-specific terminology. The ledger contains canonical feature identifiers and descriptions that serve as a common reference frame, allowing effectiveness scores to be calculated and compared across different manufacturers without being confounded by proprietary language differences.
Solution Approach 2:
The distributed ledger serves multiple functions simultaneously: it stores vehicle build information, tracks feature updates, provides a common terminology reference, and enables effectiveness score calculation. By creating a universal data structure that works across all OEMs, the system eliminates the need for separate tracking systems for each manufacturer while maintaining precise effectiveness measurements.
2Productivity
If vehicle feature updates are deployed across multiple OEMs, then safety improvements can be rapidly implemented, but tracking the effectiveness of these updates becomes difficult without a centralized system
Solution Approach 1:
The distributed ledger implements a feedback mechanism where effectiveness scores are continuously calculated and stored based on accident data and feature performance. This feedback loop allows the system to track whether updates are achieving their intended safety improvements, and the information is permanently recorded in the ledger for future reference and analysis.
Solution Approach 2:
The system performs preliminary actions by pre-defining the data structure and calculation methods in the distributed ledger before updates are deployed. Effectiveness tracking is built into the system architecture from the beginning, so data is captured and standardized automatically as updates are implemented, rather than attempting to retroactively track effectiveness.
3Ease of operation
If centralized databases are used to store vehicle safety data, then data access and analysis is simplified, but data security and manufacturer privacy concerns increase
Solution Approach 1:
The patent segments the data storage architecture into a distributed ledger that contains only standardized feature identifiers and effectiveness metrics, while keeping detailed OEM-specific vehicle data separate. This segmentation allows the system to access and analyze safety effectiveness information centrally through the ledger without requiring access to sensitive proprietary data, thereby maintaining both ease of operation and data security.
Solution Approach 2:
The distributed ledger acts as an intermediary layer between data sources and analysis systems. It contains standardized information that can be freely accessed and analyzed for effectiveness tracking, while the actual detailed vehicle data remains with the respective OEMs. This intermediary structure enables simplified data access for safety analysis without compromising manufacturer data security or privacy.
Data Source
AI summary
The following relates generally to tracking effectiveness of an update to a vehicle feature using a distributed ledger. In some embodiments, a distributed ledger including a vehicle feature is added to or constructed. Information indicating an update to the vehicle feature, and accident record information may then be received. A first dataset from before the update was implemented in the vehicle, and a second dataset from after the update was implemented in the vehicle may then be constructed. An effectiveness score may then be calculated based upon the first and second datasets, and added to the distributed ledger.