Infrastructure Data Validation for Secure Automated Driving
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for ascertaining infrastructure data for partially automated vehicle driving lack assurance of data safety and security, particularly in ensuring that infrastructure data are not manipulated, which poses risks to road users and vehicle control systems.
Innovation Solution
A method that involves receiving data signals from infrastructure sensors and motor vehicles, checking safety conditions, and generating infrastructure data signals only if these conditions are met, ensuring secure data transmission and processing through redundancy and diversity in components and algorithms, and documenting results in a blockchain for integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If infrastructure data are used for automated vehicle driving without additional safety checks, then the complexity of the system is reduced, but the reliability and safety of the driving system deteriorates due to potential data manipulation
Solution Approach 1:
The patent implements preliminary safety checks before infrastructure data are used for automated driving decisions. The system performs validation of data integrity, authentication of data sources, and verification of safety conditions prior to utilizing the data, thereby ensuring reliability while maintaining a structured approach to complexity management
Solution Approach 2:
The patent introduces intermediary components including a communication interface for secure data transmission, a blockchain system for immutable data recording and verification, and intermediate validation layers that act as mediators between infrastructure data sources and the automated driving system, enhancing trust without requiring complete system redesign
2Reliability
If safety checks and validation mechanisms are implemented for infrastructure data, then the reliability and security of automated driving improve, but the device complexity and processing time increase
Solution Approach 1:
The patent divides the safety verification system into segmented functional modules: data reception module, validation module, blockchain interaction module, and execution module. Each module performs a specific function in the data verification chain, making the overall complex system manageable through functional decomposition and allowing independent optimization of each segment
Solution Approach 2:
The patent implements a universal blockchain-based verification mechanism that can handle multiple types of infrastructure data (sensor data, traffic signal data, road condition data) through a single standardized interface and validation protocol, reducing the need for separate verification systems for different data types and thereby controlling complexity growth
3Reliability
If blockchain documentation is implemented for infrastructure data, then the security and integrity of data transmission improve, but the processing time and computational requirements increase
Solution Approach 1:
The patent implements partial blockchain documentation where only critical infrastructure data and safety-relevant information are recorded on the blockchain, while non-critical data are processed through lighter validation mechanisms. This selective approach ensures data integrity for essential information without incurring the full computational overhead of blockchain processing for all data types
Solution Approach 2:
The system performs preliminary filtering and prioritization of infrastructure data to identify which data require blockchain documentation. By pre-identifying critical data that demand immutable recording, the system avoids unnecessary blockchain operations for non-critical data, thereby reducing overall processing time while maintaining integrity where most needed
Data Source
AI summary
A method for safely ascertaining infrastructure data for driving a motor vehicle in at least partially automated fashion. The method includes receiving data signals, which represent infrastructure sensor data generated by at least one infrastructure sensor and/or motor vehicle data generated by at least one source motor vehicle, receiving safety condition signals, which represent at least one safety condition for safely ascertaining infrastructure data based on the data, checking whether the at least one safety condition is fulfilled, ascertaining infrastructure data, on the basis of which it is possible to drive a destination motor vehicle in at least partially automated fashion, based on the data as a function of a result of the check as to whether the at least one safety condition is fulfilled, generating infrastructure data signals, which represent the ascertained infrastructure data, outputting the generated infrastructure data signals.