Message-Based Model Verification for Hybrid Execution Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current modeling systems lack efficient mechanisms for managing message-based execution and verification in high-level modeling environments, particularly in integrating message-based and time-based execution domains, leading to compatibility issues and errors during model execution.
Innovation Solution
A message-based modeling system with a propagation engine, execution engine, and verification engine that organizes blocks into class hierarchies, checks message types, and supports hybrid execution models, enabling message-based and time-based domains to cooperate, and includes verification blocks for validating message traces and constraints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If message-based and time-based execution domains are integrated in modeling systems, then the system's adaptability and functionality are improved, but compatibility issues and execution errors increase
Solution Approach 1:
The patent introduces message-based components as intermediaries between time-based execution domains. These message components act as mediators that translate and coordinate interactions between different execution paradigms, enabling seamless integration while maintaining system reliability through standardized communication protocols and type checking mechanisms.
Solution Approach 2:
The system segments the execution model into distinct message-based and time-based domains, each operating with its own rules and semantics. This segmentation allows independent optimization and verification of each domain while reducing integration complexity through well-defined interface boundaries and message passing protocols.
2Reliability
If verification mechanisms are added to validate message traces and constraints, then model verification capability is improved, but system complexity increases
Solution Approach 1:
The verification system performs self-service by automatically checking message traces against constraints during execution. The verification engine monitors message flows, validates type compatibility, and detects constraint violations without requiring external intervention, thereby improving verification capability while keeping the added complexity manageable through automation.
Solution Approach 2:
The system performs preliminary verification actions by checking message types and constraints before execution errors can occur. This proactive verification approach prevents many potential errors upfront, reducing the need for complex post-execution analysis and simplifying the overall verification system architecture.
3Manufacturing precision
If message type checking and propagation engine are implemented, then execution accuracy is improved, but processing overhead increases
Solution Approach 1:
The propagation engine performs message type checking and validation in advance during model compilation and setup phases. By pre-verifying message compatibility and establishing type relationships beforehand, the system ensures execution accuracy while minimizing processing overhead during actual runtime execution.
Solution Approach 2:
The system merges type checking, message propagation, and verification functions into a unified engine that operates efficiently during execution. This consolidation reduces redundant processing steps and optimizes the balance between execution accuracy and processing overhead through integrated algorithms.
Data Source
AI summary
A system and method may generate executable block diagrams having blocks that run in accordance with message-based execution semantics. A message may include an input data payload that does not change over time, and the message may persist for only a determined time interval during execution of block diagram. A verification engine may provide one or more tools for evaluating and verifying operation of message-based blocks. The verification engine may support one or more verification blocks that may be added to the block diagram and associated with the diagram's message-based blocks. The verification blocks may capture and present messages exchanged among the message-based blocks. The verification blocks may also specify an expected interaction of messages, and determine whether the actual messages are equivalent to the expected interaction.