Vehicle Driving Mode Authentication for Accident Accountability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current automatic driving systems lack the ability to objectively determine whether an accident occurred in manual or automatic driving mode, hindering the verification and improvement of automatic driving functions, which is essential for constructing a safer system.
Innovation Solution
A driving management system that includes authentication servers and vehicles equipped with electronic control processors to manage switching between manual and automatic driving modes by generating and verifying transaction data, utilizing blockchain technology to record and verify mode switching history, ensuring accurate accountability and system improvement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If automatic driving mode is implemented without mode switching management, then automation capability is improved, but ability to objectively determine driving mode during accidents deteriorates
Solution Approach 1:
The patent introduces an authentication server as an intermediary between the vehicle's electronic control processors and the external environment. This server receives transaction data from multiple ECUs, verifies their authenticity, and records the driving mode switching information in a blockchain ledger, providing an objective third-party verification mechanism for determining driving mode during accidents
Solution Approach 2:
The system performs preliminary actions by continuously monitoring and recording driving mode switching information in real-time through transaction data before accidents occur. The authentication server pre- verifies and stores mode switching transactions in the blockchain, ensuring that accurate driving mode information is already available when accidents happen, eliminating the need for post-accident determination
2Extent of automation
If multiple electronic control processors are used for automatic driving control, then automation functionality is improved, but difficulty in verifying transaction data authenticity increases
Solution Approach 1:
The authentication server provides feedback by verifying transaction data from multiple electronic control processors and recording only authenticated information in the blockchain. This feedback mechanism ensures that despite multiple ECUs generating data, the system maintains verification capability through centralized authentication and transparent recording of mode switching transactions
Solution Approach 2:
The authentication server performs multiple functions: it receives transaction data from various ECUs, verifies the authenticity of each transaction, determines driving mode switching based on verified transactions, and records information in the blockchain. This multi-functional approach simplifies the verification process by consolidating authentication tasks in a single universal component
Data Source
AI summary
A vehicle in a driving management system including one or more authentication servers and one or more vehicles capable of switching between a manual driving mode and an automatic driving mode is provided. The vehicle includes a communication unit that communicate with at least one authentication server of the one or more authentication servers, and a detecting unit that detects switching between the manual driving mode where manual driving is performed, and an automatic driving mode where automatic driving is performed, based on a message issued by at least one of the plurality of electronic control processors. The vehicle also includes a generating unit that generates transaction data including information indicating the detected switching, and an identifier indicating the vehicle, and transmits, to the at least one authentication server, the transaction data.