TLM2.0 Model Protocol Engine Attachment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of simulating computer systems with varying bus communication protocols requires creating multiple simulation models for each protocol, which is time-consuming and adds complexity, necessitating a solution for protocol conversion.
Innovation Solution
Attaching different protocol engines associated with each bus communication protocol to a TLM2.0 model, allowing the model to be independent of specific protocols and reducing the need for multiple models.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple simulation models are created for each bus communication protocol, then protocol simulation capability is improved, but model complexity and development time increase
Solution Approach 1:
The simulation model is segmented into distinct functional components: a protocol-independent TLM2.0 model core and separate protocol-specific protocol engines. This allows the core model to remain simple while protocol-specific functionality is isolated in modular protocol engines that can be attached as needed, resolving the contradiction between versatility and complexity.
Solution Approach 2:
A single TLM2.0 model is designed to be universal by implementing a standardized model interface that can work with multiple different bus communication protocols through protocol engines. The model core remains protocol-agnostic while gaining the ability to simulate various protocols through attachment of appropriate protocol engines, eliminating the need to create separate models for each protocol.
2Adaptability or versatility
If multiple simulation models are created for each bus communication protocol, then protocol simulation capability is improved, but development time increases
Solution Approach 1:
Protocol engines are pre-configured with protocol-specific logic and behavior before simulation execution. The TLM2.0 model core is pre-designed with a universal interface structure that anticipates multiple protocol types. This preliminary preparation allows rapid protocol switching during simulation without requiring time-consuming model recreation, resolving the contradiction between versatility and development time.
Solution Approach 2:
Instead of creating entirely new simulation models for each protocol, the invention uses a template approach where a single TLM2.0 model serves as a reusable template. Protocol-specific behaviors are implemented as separate protocol engine components that can be attached to the template, dramatically reducing development time while maintaining full protocol simulation capability.
3Reliability
If protocol-specific actions are implemented in the model algorithm, then protocol accuracy is improved, but model complexity increases
Solution Approach 1:
Protocol-specific actions and logic are extracted from the core TLM2.0 model algorithm and placed into separate protocol engine components. This extraction allows the core model to maintain high protocol accuracy through proper protocol engine attachment while keeping the core algorithm simple and protocol-agnostic, resolving the contradiction between reliability and complexity.
Solution Approach 2:
Protocol engines serve as intermediary components between the protocol-independent TLM2.0 model core and the specific bus communication protocols. These intermediaries translate protocol-specific requirements into standardized interface calls that the core model can handle, ensuring protocol accuracy without embedding protocol-specific complexity in the core model algorithm.
Data Source
AI summary
A system and a method are disclosed for simulating a target system. The target system may include a plurality of components coupled via a communication bus. Each component of the target system may include a model algorithm representing the internal behavior of the component, and a model interface configured to transfer and/or receive communication payloads to/from a peer component in the target system. During simulation initialization, a simulation model of a component of the target system is accessed and a protocol engine, associated with a bus communication protocol is selected to be attached to the simulation model of the accessed component. Then, during the simulation of the target system, the model interface receives an incoming payload and informs the protocol engine of the received payload. The protocol engine may instruct the model algorithm of the component to perform a protocol specific action based on the received payload.