Polymorphic Blocks for Hybrid Domain Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques fail to automatically integrate or reuse graphical building blocks across different execution domains in hybrid Discrete Event System models, requiring manual reconfiguration and lacking support for using blocks from one domain in another.
Innovation Solution
The development of polymorphic blocks that can execute in multiple domains, identified during the compilation stage through signal connectivity, allowing time-driven blocks to adapt to event-driven execution rules and vice versa, with visual cues indicating domain execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual reconfiguration is used to integrate blocks across domains, then domain-specific functionality is maintained, but integration complexity and time consumption increase
Solution Approach 1:
The patent implements polymorphic blocks that can execute in multiple domains (time-driven and event-driven) without requiring separate copies for each domain. A single block definition can adapt to different execution domains through automatic domain detection and adaptation mechanisms, eliminating the need for manual reconfiguration while maintaining domain-specific functionality.
Solution Approach 2:
The system automatically determines the execution domain of polymorphic blocks based on signal connectivity during compilation, without requiring manual intervention. The blocks self-adapt to the appropriate domain execution rules through automatic domain detection and configuration, reducing manual reconfiguration efforts.
2Reliability
If separate copies of blocks are created for each domain, then domain-specific execution rules are ensured, but system complexity and maintenance burden increase
Solution Approach 1:
Instead of creating separate copies of blocks for each domain, the patent uses polymorphic blocks that can execute in multiple domains. A single block definition serves multiple domains through automatic adaptation, reducing the number of block copies while ensuring domain-specific execution rules are followed through runtime domain detection and adaptation.
3Productivity
If automatic domain integration is implemented, then integration time is reduced, but system complexity in managing multi-domain execution increases
Solution Approach 1:
The system performs domain determination and block adaptation during the compilation stage rather than at runtime. By pre-determining which blocks are polymorphic and which domains they should execute in based on signal connectivity analysis, the system reduces integration time while managing complexity through upfront configuration rather than runtime management.
Solution Approach 2:
The patent replaces manual mechanical reconfiguration processes with automatic computational methods. The compilation stage automatically analyzes signal connectivity to determine block domains, substituting manual configuration efforts with automated algorithms that reduce integration time while managing complexity through systematic analysis.
Data Source
AI summary
A time-driven block provided in a block diagram model may be executed in an event domain without user modification. The time-driven block is connected to one or more event-driven blocks using event domain signals. The time-driven block automatically adapts to the execution rules of the event domain modeling and simulation environment. The blocks that are configured to execute in more than one modeling and simulation environments are called polymorphic blocks. The polymorphic blocks are indentified during the compilation stage of the block diagram model taking into consideration the port and line styles of the blocks. The execution rules of the polymorphic blocks are also determined during the compilation stage of the block diagram model.