Vehicle Bus Block Access for ECU Updates and Debug Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The management and updating of low-cost electronic components with limited capabilities in vehicles are challenging due to the need for simple communication protocols and the complexity of interconnecting these components with other electronic systems via vehicle buses.

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 data reading and writing, and enabling debugging information and software updates to be transmitted securely.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If simple protocols are implemented for low-cost electronic components to communicate via vehicle bus, then communication capability is improved, but maintenance and updating become technically challenging

Engineering Contradiction:
Improvecommunication capabilityVSAvoidmaintenance and updating
Core Design Contradiction:
Adaptability or versatilityVSEase of repair

Solution Approach 1:

The patent introduces a gateway device as an intermediary between low-cost electronic components and the update system. The gateway translates simple communication protocols from ECUs into standard protocols, enabling maintenance and updating operations without requiring the ECUs themselves to support complex protocols directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into different functional layers: the ECU layer using simple protocols, the gateway layer handling protocol translation, and the update management layer handling maintenance operations. This segmentation allows each component to operate within its capability while achieving overall system maintainability.

Inventive Principle:
Principle #1Segmentation

2Ease of manufacture

If low-cost components with limited capabilities are used, then cost is reduced, but interconnecting and networking becomes a particular challenge

Engineering Contradiction:
ImprovecostVSAvoidinterconnecting and networking
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The gateway acts as a mediator that shields low-cost ECUs from the complexity of networking and interconnection management. The gateway handles protocol conversion, address management, and network coordination, allowing ECUs to remain simple while achieving complex networking capabilities at the system level.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway device serves multiple functions: protocol translation, address assignment, network management, and update coordination. This multi-functionality consolidates complexity into a single component rather than distributing it across all ECUs.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If existing vehicle bus infrastructure is used for communication, then compatibility is improved, but data transmission speed and reliability may be limited

Engineering Contradiction:
ImprovecompatibilityVSAvoiddata transmission
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The gateway serves as an intermediary that can implement error correction, data validation, and reliable transmission protocols. It receives simple data from ECUs, validates and corrects errors, then transmits through the vehicle bus using appropriate protocols, thereby enhancing reliability while maintaining compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250028665A1Network Block Device Protocol
Publication Date: 2025.01.23 APTIV TECHNOLOGIES AG
  • US20250028665A1 patent drawing
  • US20250028665A1 patent drawing
  • US20250028665A1 patent drawing

AI summary

An electronic device in a vehicle includes at least one interface to a vehicle bus, at least one processor, and at least one memory including program code. The program code causes the electronic device to configure the interface to communicate with a controller in the vehicle over a transport protocol. The program code causes the electronic device to be accessible to the controller over the interface as a block device. The program code causes the electronic device to, 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.