Model Adaptation Layer for Cross-Style Component Reuse

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing modeling technologies face challenges in seamlessly converting models between different modeling styles, such as rate-based multitasking and function-call-based styles, which can lead to delays in product design due to the need for extensive verification and testing when changes are made.

Innovation Solution

The introduction of an adaptation layer that allows model components to be utilized across different modeling styles by identifying executable entities, their relationships, and constraints, and providing a platform-independent interface for scheduling and service invocation, enabling user-controlled execution and reuse of model components without altering their functional behavior.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If model components are converted between different modeling styles, then adaptability and versatility are improved, but device complexity and verification requirements increase

Engineering Contradiction:
Improvemodel component compatibilityVSAvoidverification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an adaptation layer as an intermediary component that sits between model components and different modeling style interfaces. This adaptation layer handles the complexity of style conversion internally, allowing model components to work with multiple modeling styles without requiring extensive verification for each style conversion. The adaptation layer absorbs the complexity burden, enabling seamless interoperability while maintaining verification efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If model components are modified to work across different modeling styles, then adaptability is improved, but manufacturing precision and functional behavior stability deteriorate

Engineering Contradiction:
Improvemodel component reusabilityVSAvoidfunctional behavior consistency
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent segments the model component system into distinct layers: the core model component layer that maintains original functional behavior, and the adaptation layer that handles style-specific interactions. This segmentation allows model components to be reused across different modeling styles without modification, preserving functional behavior consistency while achieving adaptability through the separate adaptation layer that manages style conversions.

Inventive Principle:
Principle #1Segmentation

3Reliability

If extensive verification and testing are performed when changing modeling styles, then reliability is improved, but loss of time and productivity deteriorate

Engineering Contradiction:
Improvemodel conversion reliabilityVSAvoidproduct design time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-defining adaptation layers for different modeling styles and pre-establishing the conversion mechanisms. When model components need to work across styles, the pre-configured adaptation layers are automatically applied, eliminating the need for extensive verification and testing during each conversion. This preliminary preparation of adaptation infrastructure significantly reduces design time while maintaining reliability through proven conversion patterns.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3465424B1Systems and methods for creating model adaptors
Publication Date: 2023.11.15 MATHWORKS INC
  • EP3465424B1 patent drawingFigure 1
  • EP3465424B1 patent drawingFigure 2
  • EP3465424B1 patent drawingFigure 3

AI summary

Systems and methods decouple model components from a model execution style for which the model components are created, and the model components may be utilized in parent models having different execution styles. A model component may be partitioned into executable entities, and the entry points of the executable entities and their call styles may be identified. An adaptation layer that includes access points for the entry points may be constructed. The model component, including the adaptation layer, may be included in the model, and connection elements of the parent model may be connected to the access points of the adaptation layer. The execution call styles associated with the connection elements of the parent model may be bound to the execution call styles of the entry points as originally designed. The adaptation layer may manage translation of call styles and may coordinate scheduling of data communication with the model component.