Message-Based Modeling for Hybrid Execution Domain Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current modeling systems lack efficient mechanisms for executing message-based models that integrate time-based and state-based execution domains, leading to complexity in simulating dynamic systems and analyzing their behavior.
Innovation Solution
A message-based modeling system that includes a library of pre-defined object types for generating and processing messages, with a graphical editor for constructing models, and an execution engine that controls message-based objects, cooperating with time-based and state-based execution entities to implement hybrid execution models, and a verification engine for evaluating message-based block operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If message-based modeling systems integrate multiple execution domains (time-based and state-based), then the system's ability to simulate dynamic systems improves, but the device complexity increases
Solution Approach 1:
The system is divided into separate execution entities, each responsible for a specific execution domain (time-based, state-based, message-based). These entities operate independently but cooperate through defined interfaces, allowing the system to handle multiple execution domains without monolithic complexity.
Solution Approach 2:
The execution entities are designed to be multi-functional, capable of handling different types of model operations within their respective domains. The message-based execution entity, for example, can both send and receive messages, and coordinate with other execution entities to provide comprehensive simulation capabilities.
2Ease of operation
If the system uses pre-defined object types and graphical editors for model construction, then ease of operation improves, but device complexity increases
Solution Approach 1:
The system provides pre-defined object types and graphical editor templates that are prepared in advance. Users can construct models by selecting and configuring these pre-defined elements rather than creating everything from scratch, significantly easing operation while the complexity is managed in the background preparation.
Solution Approach 2:
The graphical editor serves as an intermediary layer between the user and the complex execution engine. It provides a simplified interface for model construction while handling the complexity of translating graphical models into executable configurations for the multiple execution entities.
3Measurement precision
If the system persists messages for defined time intervals, then measurement precision improves, but loss of time increases
Solution Approach 1:
The message-based execution entity operates with periodic message persistence at defined time intervals. Messages are held for specific durations and then processed or discarded according to the model's timing requirements, providing precise timing control while limiting the time messages remain in the system.
Data Source
AI summary
A system and method may generate executable models having message sending objects and message receiving objects. A message may include a fixed data payload, and the message may persist for only a determined time interval of a total execution or simulation time of model. Message queues may be established for the messages, and the queues may have attributes. The model may include a state-based portion having states and transitions. States may be configured to generate and send messages, and to receive and process messages. In addition, transitions may be guarded by particular messages. The system and method also may generate standalone code, such as source code, for the model. The standalone code may include code that establishes a message passing service to support the sending and receiving of messages.