Simulation Method for Accurate ECU Timing on Distributed Hardware

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing simulation methods fail to accurately reproduce the execution timing of a target ECU environment on a host PC simulation due to insufficient consideration of hardware features like cache, bus, and microcomputer characteristics, and do not account for distributed hardware configurations, leading to inaccuracies in simulating software execution on different hardware platforms.

Innovation Solution

A simulation method that extracts host feature values, calculates performance differences between host and target environments, and estimates execution times on the target environment based on these values, allowing for high-accuracy simulation of software execution on distributed hardware configurations without actual porting to the target environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If time adjustment process is performed based on speed ratio between simulation device and calculator, then execution timing can be simulated close to actual ECU, but accuracy of adjustment is insufficient due to not considering cache, bus, and microcomputer features

Engineering Contradiction:
Improveexecution timing accuracyVSAvoidsimulation model complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent changes the parameters used for timing adjustment from simple speed ratio to multiple hardware feature parameters including cache size, bus speed, and microcomputer characteristics. This allows the simulation to account for actual hardware variations and achieve more accurate execution timing predictions.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent performs preliminary measurements of hardware features on both the simulation device and target calculator before executing the software. These pre-collected hardware parameters are then used to calculate timing adjustments, avoiding the need for complex real-time measurements during software execution.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If distributed hardware configuration is not considered, then simulation is simpler, but latency due to communication timing difference between functions on different hardware cannot be reproduced

Engineering Contradiction:
Improvecommunication timing accuracyVSAvoidhardware configuration complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the distributed hardware system into individual components (different calculators, communication buses, memory devices) and measures the timing characteristics of each segment separately. This allows the simulation to account for communication latencies between different hardware components while maintaining manageable complexity through modular measurement and calculation.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20240394168A1Simulation method
Publication Date: 2024.11.28 ASTEMO LTD
  • US20240394168A1 patent drawing
  • US20240394168A1 patent drawing
  • US20240394168A1 patent drawing

AI summary

To reproduce, in consideration of the distributed hardware configuration, a software execution timing in a target environment on a host environment with high accuracy. A simulation method includes: extracting a first host feature value 11 obtained by executing first software 10 on a host environment 100; executing the first software 10 on a target environment 110 to calculate a target execution time 20 taken to execute the first software 10 on the target environment 110; calculating a performance difference between the host environment 100 and the target environment 110 based on the first host feature value 11 and the target execution time 20; extracting a second host feature value 13 obtained by executing second software 12 on the host environment 100; and estimating a time 40 taken to execute the second software 12 on the target environment 110 based on the second host feature value 13 and the performance difference.