Vehicle Block Device Protocol for ECU Updates Over CAN/LIN
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic systems in vehicles face challenges in managing and updating low-cost components with limited capabilities, due to the complexity of interconnecting and networking such components using simple protocols over vehicle buses like CAN and LIN.
Innovation Solution
An electronic device in a vehicle is configured with a processor and memory that executes program code to communicate with a controller over a transport protocol, allowing the device to be accessed as a block device for reading and writing data, including software updates, while performing encryption and handshake procedures for secure communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If simple protocols are implemented for communication via vehicle bus to support low-cost components with limited capabilities, then hardware requirements are reduced, but maintenance and updating of such components become technically challenging
Solution Approach 1:
The patent introduces a gateway device as an intermediary between the controller and low-cost electronic components. The gateway translates complex update commands from the controller into simple protocols that the low-cost components can understand, enabling maintenance and updating capabilities without requiring the components themselves to have advanced processing capabilities.
Solution Approach 2:
The system enables self-service updating by allowing the controller to directly update electronic components through the vehicle bus using standardized block device protocols. The components can receive and apply updates autonomously without requiring manual intervention or complex external update mechanisms.
2Adaptability or versatility
If electronic systems are interconnected to achieve advanced functions and technologies, then system capabilities are improved, but device complexity increases
Solution Approach 1:
The patent segments the system into distinct functional layers: a control layer with the controller, a gateway layer for protocol translation, and an execution layer with electronic components. This segmentation allows advanced functions to be implemented at the controller and gateway levels while keeping individual component complexity low.
Solution Approach 2:
The patent implements a universal interface using standard block device protocols that allow different types of electronic components (ECUs, sensors, actuators) to be interconnected and managed through a common communication framework. This universality enables system expansion without proportionally increasing complexity.
3Ease of manufacture
If low-cost components with limited capabilities are used, then manufacturing cost is reduced, but manageability of electronic components deteriorates
Solution Approach 1:
The gateway acts as a mediator that handles complex management tasks such as protocol translation, data formatting, and command interpretation. This allows low-cost components to maintain simple hardware while the gateway manages the complexity of communication and updates.
Solution Approach 2:
The system changes the communication parameters by implementing a standardized block device protocol interface. This standardization transforms how data is exchanged, allowing simple components to be managed through uniform commands and procedures, improving manageability without increasing component complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The subject disclosure pertains to communication between electronic devices (ECUs, ECMs, central control units) in a vehicle. For example, the subject disclosure provides an electronic device in the vehicle, comprising at least one processor and at least one memory including program code. The program code causes the electronic device, when executed with the at least one processor, to: configure the interface to communicate with a controller in the vehicle over a transport protocol; configure the electronic device to be accessible to the controller over the interface as a block device; upon receiving, from the controller, a request to access the block device over the transport protocol: read data from the block device; and transmit, to the controller, the data over the transport protocol.