Brake Control Hardware Type Detection via Memory Registers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing brake systems in motor vehicles, particularly electromechanical brake boosters, face challenges in accurately identifying and adapting to different types of computing devices, such as ASICs, which can lead to incorrect function activation or deactivation, especially in mixed platforms with varying hardware configurations, potentially affecting safety and efficiency.

Innovation Solution

A method and device that access registers of a memory device to ascertain the type of computing device, allowing for correct identification and adaptation of software functions based on the detected hardware configuration, enabling timely activation or deactivation of functions like autonomous driving and preventing faulty brake system control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple different hardware configurations are used in mixed platforms, then versatility and adaptability are improved, but device complexity and difficulty of detecting and measuring increase

Engineering Contradiction:
Improvesupport for different hardware configurationsVSAvoidcomplexity of controlling multiple hardware configurations
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The computing device automatically identifies its own hardware configuration type by accessing register information during initialization, without requiring external detection or manual configuration. This self-identification mechanism allows the system to adapt to different hardware configurations while maintaining simple control architecture.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses register parameters to encode hardware configuration information, allowing different hardware configurations to be represented through different parameter values. This enables the same software to adapt to multiple hardware types by reading and responding to parameter differences rather than requiring separate control paths.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If hardware configuration information is stored in registers, then ease of operation and initialization are improved, but reliability decreases due to potential transmission errors

Engineering Contradiction:
Improveinitialization processVSAvoidaccuracy of type identification
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system implements a feedback mechanism where the read access result is evaluated to determine if a transmission error occurred. Based on this evaluation, the system can request retransmission or take corrective action, ensuring reliable hardware configuration identification while maintaining simple initialization procedures.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The hardware configuration information is prepared and stored in registers during manufacturing or initialization before the device enters service. This preliminary action allows the information to be readily available for quick identification without requiring complex real-time detection, while error checking ensures reliability.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If software is designed to support multiple hardware configurations, then adaptability is improved, but manufacturing precision and testing requirements increase

Engineering Contradiction:
Improvesoftware compatibility with different hardwareVSAvoidsoftware development and testing accuracy
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The software is designed with universal functionality that can operate across multiple hardware configurations through a unified interface. The computing device reads hardware-specific register information and adapts its operation accordingly, allowing a single software version to serve multiple hardware types without requiring separate development or extensive customization for each configuration.

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

Data Source

PatentUS20240001946A1Method and device for ascertaining a type of a computing device of an apparatus
Publication Date: 2024.01.04 ROBERT BOSCH GMBH
  • US20240001946A1 patent drawing
  • US20240001946A1 patent drawing

AI summary

A method for ascertaining a type of a computing device of an apparatus of a motor vehicle. The computing device is designed to at least partially control at least one function of the apparatus. Access to at least one register of a memory device of the apparatus takes place. A type of the computing device is ascertained based on a result of the access.