Type Configuration Ledger for Traceable Vehicle Software Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods fail to provide secure, transparent, and traceable documentation for software updates in motor vehicles, particularly in the context of over-the-air updates, which is essential for future regulatory compliance and intellectual property protection.
Innovation Solution
A method utilizing a distributed ledger technology, such as a blockchain, to create and manage type configurations for computing devices, ensuring secure and tamper-proof documentation of software updates by using identification values like hash values, allowing for transparent and traceable updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional documentation methods are used for software updates, then the process is simple and fast, but the security and integrity of the documentation cannot be ensured
Solution Approach 1:
A distributed ledger is introduced as an intermediary system between the software update generation process and the documentation storage. The distributed ledger acts as a mediator that receives type configurations, validates them using identification values, and stores them in a tamper-proof manner, thereby ensuring security and integrity without requiring complex centralized security systems
Solution Approach 2:
Instead of storing the actual type configuration data in the distributed ledger, the system stores identification values (such as hash values) that uniquely identify the type configurations. This copying approach ensures that the documentation cannot be altered while maintaining simplicity, as the identification values serve as digital fingerprints that verify the integrity of the original documents
2Loss of information
If manual documentation processes are used, then the system is easier to operate, but traceability and transparency for long-term verification are compromised
Solution Approach 1:
The system performs preliminary actions by automatically generating identification values for type configurations before they are stored in the distributed ledger. This preliminary creation of unique identifiers ensures that traceability is established from the outset, allowing any future verification to quickly trace back to the original configuration without requiring complex manual tracking processes
Solution Approach 2:
The distributed ledger provides automatic feedback mechanisms that verify the integrity and uniqueness of stored type configurations. When a type configuration is added, the system automatically checks its identification value and confirms its successful storage with immutable records, providing transparent feedback that enhances traceability without requiring manual verification processes
3Reliability
If centralized documentation systems are used, then data management is simpler, but security and tamper-proof documentation are compromised
Solution Approach 1:
The documentation system is segmented into distributed components across multiple nodes in the distributed ledger network. Instead of a single centralized database that could be targeted for tampering, the system divides documentation storage across many independent nodes, making it tamper-proof while maintaining relatively simple data management through automated consensus mechanisms
Data Source
AI summary
The invention relates to a method for documenting A type configuration generated using a provided type library for at least one computing device is documented by providing a first version of the type library by a first computing device and storing an identification value of the first version of the type library in a distributed database. A first at least partial type configuration and/or complete type configuration is generated using the first version the type library by the first computing device and/or at least one further computing device and an identification value of the first type configuration is stored in the distributed database.