Vehicle Control Program Matching Across Multiple Calculation Units

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing multiprocessor system disclosed in PTL 1 cannot be applied to a vehicle control device with multiple calculation units having two different versions of programs, as it only supports a unified program version for all units, limiting its applicability.

Innovation Solution

A vehicle control device with multiple calculation units, each having a main program and sub-program storage area, where the main calculation unit activates and executes one main program and the sub-calculation unit selects and activates a corresponding sub-program based on the activation result of the main program, allowing independent program versions across units.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a multiprocessor system with a single unified program version is used (as in PTL 1), then the system configuration is simplified and hardware is reduced, but the system cannot support multiple calculation units with different program versions

Engineering Contradiction:
Improveability to support multiple program versionsVSAvoidprogram storage and selection mechanism
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The program storage area is segmented into main program storage area and sub-program storage area. Each calculation unit has its own program storage area that can store multiple program versions. The main program storage area stores the primary program while the sub-program storage area stores alternative versions, allowing different calculation units to run different versions without requiring a unified program across the entire system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each calculation unit is equipped with its own program storage area that can independently store and select program versions. This local program storage capability allows each calculation unit to have customized program versions according to its specific requirements, while maintaining the ability to communicate and coordinate with other calculation units through the communication interface.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If each calculation unit stores multiple program versions locally, then different versions can be activated independently, but the system complexity and hardware requirements increase

Engineering Contradiction:
Improveindependent program version selectionVSAvoidprogram storage capacity
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The program storage areas of multiple calculation units are logically merged through the communication interface. Instead of each calculation unit requiring complete independent storage of all program versions, the system allows shared access to program versions across calculation units. This reduces redundant storage while maintaining the capability for independent program selection and activation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The program storage area is designed with multi-functionality to serve both as local storage for the host calculation unit and as a shared resource for other calculation units through the communication interface. The same program version can be stored once and accessed by multiple calculation units, reducing overall storage requirements while maintaining universal access capability.

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

3Reliability

If program versions are synchronized across all calculation units, then consistency is maintained, but the ability to run different versions simultaneously is lost

Engineering Contradiction:
Improveprogram execution consistencyVSAvoidversion diversity support
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The program version configuration is made dynamic rather than static. Calculation units can dynamically select and switch between different program versions based on operational requirements. The system supports both synchronized operation (when consistency is needed) and asynchronous operation (when version diversity is needed), allowing flexible adaptation to different operational scenarios without compromising reliability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The communication interface enables feedback mechanisms where calculation units can exchange information about their program versions and operational status. This allows the system to maintain consistency when needed by synchronizing versions across units, or to allow version diversity when different operational modes are required, with each unit providing feedback about its state to the overall system.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12050902B2Vehicle control device and program management method
Publication Date: 2024.07.30 ASTEMO LTD
  • US12050902B2 patent drawing
  • US12050902B2 patent drawing
  • US12050902B2 patent drawing

AI summary

Matching programs are activated by a plurality of calculation units. A vehicle control device that controls a vehicle includes a plurality of calculation units that execute calculation processing for vehicle control; and a plurality of program storage areas that store a plurality of programs in which a procedure of the calculation processing is defined, wherein a main calculation unit includes a main program activation unit that activates one main program from the plurality of main programs, and a sub-calculation unit includes a sub-program selection unit that selects a sub-program to be activated by the sub-calculation unit based on an activation result of the main program activation unit, and a sub-program activation unit that activates one sub-program based on a selection result of the sub-program selection unit.