FMU Integrity Check Using Embedded Hash Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The integrity of Functional Mock-up Units (FMUs) is vulnerable to manipulation during distribution and usage, as they are not controlled by the original manufacturer, leading to potential unauthorized modifications and compromised test results.

Innovation Solution

Integrate an integrity check code into the FMU that performs a version and authenticity check on startup, using a hash value calculated from the binary file's memory segments and optionally includes a validity period and user ID verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If FMU is distributed and used across different simulators and users, then model reusability and collaboration are improved, but integrity and security of the model deteriorate due to potential unauthorized modifications

Engineering Contradiction:
Improvemodel reusabilityVSAvoidintegrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

An integrity check code is generated and embedded into the FMU during the export process from the V-ECU. This preliminary action ensures that the integrity verification mechanism is already in place before the FMU is distributed, allowing automatic detection of any unauthorized modifications when the FMU is later used in different simulation environments.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The FMI simulator performs an integrity check on the FMU using the embedded integrity check code. This feedback mechanism automatically verifies whether the FMU has been modified, providing immediate detection of integrity violations and preventing the use of compromised models in simulation processes.

Inventive Principle:
Principle #23Feedback

2Productivity

If FMU is made accessible to multiple users and simulators, then productivity and testing efficiency are improved, but vulnerability to manipulation and unauthorized changes increases

Engineering Contradiction:
Improvetesting efficiencyVSAvoidunauthorized modifications
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The integrity check code is pre-configured in the FMU to counteract potential manipulation attempts. This preliminary anti-action establishes a defensive mechanism that automatically detects and prevents unauthorized modifications, allowing the FMU to be freely shared across multiple users and simulators without compromising security.

Inventive Principle:
Principle #9Preliminary anti-action

3Ease of operation

If the V-ECU is exported as a standardized FMU, then ease of exchange and collaboration between different companies and teams is improved, but control over the model's lifecycle and integrity is lost

Engineering Contradiction:
Improvemodel exchangeVSAvoidintegrity control
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The integrity check code acts as an intermediary element embedded within the FMU. It carries the original manufacturer's verification mechanism through the distribution process, enabling automatic integrity verification without requiring the original manufacturer to be directly involved in each usage instance. This mediator preserves integrity control while maintaining the benefits of standardized exchange.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4654010A1Computer-implemented method for creating a residual model for a simulation system
Publication Date: 2025.11.26 DSPACE SE & CO KG
  • EP4654010A1 patent drawingFigure 1~2
  • EP4654010A1 patent drawing
  • EP4654010A1 patent drawing

AI summary

According to the invention, a computer-implemented method for creating a Functional Mock-up Unit (FMU) according to the FMI standard is provided, comprising the following process steps: creating a virtual electronic control unit (V-ECU), creating integrity check code, and exporting the V-ECU to an FMU with the addition of the integrity check code, so that the generated FMU performs an integrity check on every startup on an FMI simulator based on the integrity check code. This check verifies whether the version of the FMU is unchanged compared to the version of the FMU generated by exporting the V-ECU. In this way, a simple method is provided to verify the integrity of an FMU.