Secure Vehicle Interface with Interrupt for Diagnostic Safety
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing interfaces for motor vehicle communication lack the necessary safety features to meet higher safety requirements, particularly ASIL-A standards, and are limited to reading diagnostic data without ensuring secure and authorized data transmission.
Innovation Solution
A secure interface for motor vehicle communication that includes a first interface for control electronics, a second interface for external diagnostic devices, and processing units for data transfer, error detection, and plausibility checking, with a watchdog module and switching matrix to ensure safe and authorized data exchange, implemented as an OBD dongle for easy integration with existing systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a standard OBD2 interface is used for diagnostic communication, then ease of operation and compatibility are improved, but functional safety and security are insufficient
Solution Approach 1:
The patent introduces an intermediary device (interface according to the invention) that sits between the OBD2 interface and the diagnostic device. This intermediary includes a first processing unit that communicates with the motor vehicle and a second processing unit that communicates with the external diagnostic device, thereby mediating the communication and enabling safety monitoring without compromising ease of operation
Solution Approach 2:
The communication interface is segmented into functionally independent processing units: a first processing unit for vehicle communication, a second processing unit for diagnostic device communication, and a monitoring unit for safety oversight. This segmentation allows each unit to perform its specific function while maintaining overall system safety
2Adaptability or versatility
If diagnostic functions are expanded to include write access and control commands, then functionality is improved, but risk of unauthorized activation and safety hazards increase
Solution Approach 1:
The monitoring unit performs preliminary checks on all data transmissions before they reach the motor vehicle control electronics. It verifies plausibility, checks for unauthorized commands, and validates diagnostic routines in advance, preventing harmful actions before they can occur
Solution Approach 2:
The monitoring unit continuously monitors data transmissions and provides feedback by interrupting unauthorized communications. When a suspicious command or implausible data pattern is detected, the monitoring unit actively intervenes to block the transmission, creating a closed-loop safety mechanism
3Reliability
If safety monitoring and data verification functions are added to the interface, then functional safety is improved, but device complexity increases
Solution Approach 1:
The patent combines multiple safety functions into a single integrated interface device. The first processing unit, second processing unit, and monitoring unit are merged into one cohesive system that handles both communication tasks and safety monitoring simultaneously, rather than requiring separate systems
4Ease of operation
If the interface is designed to work with existing OBD2 sockets, then ease of operation and compatibility are improved, but security and authorization control are weakened
Solution Approach 1:
The interface acts as a security intermediary between the public OBD2 socket and the vehicle's control electronics. While the OBD2 socket remains accessible for easy connection, all communications passing through the intermediary are subject to security checks, authorization validation, and plausibility verification by the monitoring unit
Data Source
Figure 1
Figure 2
AI summary
An interface (2) for providing a secure interface to a motor vehicle, particularly for communication with control electronics of the motor vehicle, comprises: a first interface (4) having multiple connections that is configured for communication with control electronics of the motor vehicle; a second interface (6) that is configured for communication with an external diagnosis device; a first computation unit (12a) that is configured to transmit data between the first and the second interface (6); a second computation unit (12b) that is configured to monitor the data transmission between the first interface (4) and the second interface (6), in order to identify an unsafe state, and to interrupt the data transmission when an unsafe state has been identified; and a circuit (20) that allows connections of the first interface to be selectively connected to input and/or outputs of the first computation unit (12a) and/or the second computation unit (12b).