Hierarchical Entity Model for Multi-Level Simulation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current simulation methodologies face challenges in efficiently modeling and simulating systems with components specified at different levels of abstraction, such as Register Transfer Level (RTL) and higher levels, due to the lack of native high-level features in languages like C++ and VHDL, leading to complex and error-prone manual translations and time-consuming testing processes.

Innovation Solution

A method for simulating behavior across different abstraction levels by using a hierarchical entity model, where entities are instantiated based on their relationships, and a novel programming language CY is used to generate recognition and generation algorithms, allowing for multi-level simulation and automatic data conversion between levels, along with an event-based simulation system that processes events categorized by time and category.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual translation between different abstraction levels is used, then system behavior can be verified across levels, but the process becomes complex and error-prone

Engineering Contradiction:
Improvevalidation accuracyVSAvoidtranslation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary translation system that automatically converts between behavioral level models and RTL models. This intermediary translator serves as a mediator that handles the complex translation process, reducing manual intervention and minimizing errors while maintaining validation accuracy across different abstraction levels.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the manual mechanical translation process with an automated computational system. The translation between abstraction levels is performed algorithmically rather than manually, substituting human effort with an automated mechanism that reduces complexity and error-proneness in the translation process.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Measurement precision

If testing is carried out at RTL level only, then detailed verification is possible, but testing cannot begin until all components are completed at RTL

Engineering Contradiction:
Improveverification detailVSAvoidtesting delay
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent enables preliminary testing at the behavioral level before RTL implementation is complete. By allowing validation to occur at higher abstraction levels in advance, the system can perform preliminary verification of system behavior, reducing the overall testing timeline while maintaining the option for detailed RTL-level verification later.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the verification process into multiple levels: behavioral level verification can be performed independently on individual components before they are integrated at RTL level. This segmentation allows parallel testing activities, reducing total testing time while maintaining comprehensive verification through multi-level validation.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If behavioral level modeling is used, then higher level features are available, but true system level modeling is still difficult to achieve

Engineering Contradiction:
Improvemodeling flexibilityVSAvoidsystem level modeling difficulty
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal modeling framework that works across multiple abstraction levels. The system can handle behavioral level models, RTL models, and their translations uniformly through a common architecture, enabling true system-level modeling while maintaining the flexibility of behavioral level features. This multi-functional approach allows the same framework to serve different modeling needs.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If VHDL+ language is used for high level modeling, then abstraction level is increased, but automatic conversion between levels has not been successfully implemented

Engineering Contradiction:
Improveabstraction levelVSAvoidautomatic conversion
Core Design Contradiction:
Adaptability or versatilityVSExtent of automation

Solution Approach 1:

The patent replaces the unsuccessful manual conversion approach with an automated translation system. The system uses algorithmic methods to automatically convert between VHDL+ behavioral level models and RTL models, achieving the automation that was previously unattainable with manual processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces an intermediary translation layer that mediates between VHDL+ and RTL. This intermediary system handles the complexity of automatic conversion, enabling high-level modeling with VHDL+ while providing automated translation to RTL for implementation, thus achieving both high abstraction and automation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8082141B2Modelling and simulation method
Publication Date: 2011.12.20 SIEMENS INDUSTRY SOFTWARE INC
  • US8082141B2 patent drawing
  • US8082141B2 patent drawing
  • US8082141B2 patent drawing

AI summary

A method for simulating behavior of first and second interrelated components within a system. The method comprises modelling behavior of said first and second components using first and second functional specifications; simulating behavior of said first and second components in predetermined circumstances by instantiating at least one first entity within a hierarchy of interrelated entities; and instantiating at least one further entity in response to the or each instantiated first entity. The or each further entity is selected by a simulation system on the basis of its hierarchical relationship with the at least one first entity.