Residual Simulation Model for Secure Target Model Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex simulation systems in the automotive industry face challenges in integrating and verifying individual plant models due to lack of interoperability and inflexible application implementations, requiring secure and efficient methods for data exchange and model protection.

Innovation Solution

A method for creating a residual model that mimics the behavior of the original simulation system without the target model, focusing on essential interfaces and functions necessary for testing, using port and fieldbus controllers to replicate communication and data exchange, while ensuring intellectual property protection through encryption and secure data handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the complete simulation system with all submodels is shared for testing, then the target model can be fully validated, but intellectual property and confidential information are exposed

Engineering Contradiction:
Improvevalidation completenessVSAvoidintellectual property protection
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent extracts only the necessary components (ports and fieldbuses) from the complete simulation system to create a residual model. This residual model contains minimal information required for testing the target model while excluding proprietary submodels and implementation details, thus protecting intellectual property while enabling validation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The residual model acts as an intermediary between the target model and the original simulation system. It provides the necessary interface for testing without exposing the actual proprietary systems, serving as a secure mediator that enables validation while maintaining confidentiality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Manufacturing precision

If detailed documentation of all model interfaces is provided for integration, then integration accuracy improves, but system complexity and confidentiality requirements increase

Engineering Contradiction:
Improveintegration accuracyVSAvoidsystem integration complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent extracts only the essential interface elements (ports and fieldbuses) needed for integration rather than documenting complete model details. This reduces the complexity of integration documentation while maintaining sufficient accuracy for connecting the target model to the simulation system.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If multiple teams from different companies create models independently, then specialization and expertise are leveraged, but interoperability and integration become difficult

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidmodel interoperability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal interface structure (residual model with standardized ports and fieldbuses) that can accommodate models from different teams and companies. This universal structure enables interoperability while allowing each team to maintain their specialized model implementations independently.

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

Data Source

PatentEP4471650A1Method for creating a residual model for a simulation system
Publication Date: 2024.12.04 DSPACE SE & CO KG
  • EP4471650A1 patent drawingFigure 1~2
  • EP4471650A1 patent drawingFigure 3~4
  • EP4471650A1 patent drawingFigure 5

AI summary

According to the invention, a method for creating a residual model (3) for a simulation system (1) comprising a plurality of sub-models (11, 12, 13, 21, 22) is provided, comprising the following method steps: selecting at least one sub-model (11, 12, 13, 21, 22) as the target model (21, 22) that is not to be included in the residual model (3), identifying ports of the simulation system (1) that need to be connected to ports of the target model (21, 22), creating corresponding ports with identical properties in the residual model (3) from the identified ports, identifying fieldbuses of the simulation system (1) that need to be connected to the target model (21, 22), and creating fieldbus controllers suitable for the identified fieldbuses in the residual model (3).