Address-Based Waveform Database Architecture for Simulation Tools

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing waveform simulation tools face challenges in storing and retrieving data due to differences in hardware definition languages (HDLs) and data formats, leading to compatibility issues and inefficient data processing.

Innovation Solution

A waveform database architecture that maps design objects to memory addresses, allowing simulation data to be translated into a format independent of implementation details, enabling storage and retrieval of event data in a unified format for various simulation tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If different simulation tools use different hardware definition languages and data formats, then each tool can process waveforms in its own way, but compatibility issues arise and data processing efficiency decreases

Engineering Contradiction:

Improvecompatibility across simulation toolsVSAvoiddata processing efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent introduces a database schema that acts as an intermediary layer between different simulation tools. This schema provides a standardized format for storing waveform data, allowing tools with different HDLs and data formats to exchange information efficiently. The database schema translates various tool-specific formats into a common structure, resolving compatibility issues while maintaining processing efficiency.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The database schema is designed to be universal, accommodating multiple hardware definition languages and data formats through a single standardized structure. This multi-functional schema can handle time-based, sample-based, and clock-based waveform data from different tools, enabling broad compatibility without sacrificing processing efficiency for any specific tool.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Productivity

If waveform data is stored in tool-specific formats, then each tool can process its own data efficiently, but data exchange between tools becomes problematic

Engineering Contradiction:

Improvedata processing efficiencyVSAvoiddata exchange capability

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The standardized database schema serves as a mediator that receives data from various simulation tools in their native formats and stores them in a unified structure. This intermediary layer enables efficient data exchange between tools while maintaining the processing efficiency benefits of tool-specific formats during the import phase.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If a unified data format is implemented across all simulation tools, then data exchange becomes easier, but tools lose flexibility in processing their own specific formats

Engineering Contradiction:

Improvedata exchange capabilityVSAvoidtool-specific processing flexibility

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system segments the data handling process into two distinct phases: data import and data processing. During import, tool-specific formats are preserved and translated into the standardized database schema. During processing, tools can access data in their preferred formats through the standardized interface, maintaining flexibility while enabling unified data exchange.

Inventive Principle:

Principle #1Segmentation

4Reliability

If simulation data is stored with implementation details, then the data accurately represents the design object, but the database becomes complex and harder to retrieve data from

Engineering Contradiction:

Improvedata accuracyVSAvoiddatabase structure complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The standardized database schema acts as an intermediary that preserves implementation details through structured fields while maintaining a consistent, simplified retrieval interface. The schema organizes HDL-specific information, timing information, and waveform data in a systematic way that retains data accuracy without increasing operational complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10642811B1Address-based waveform database architecture

Publication Date: 2020.05.05 XILINX INC

AI summary

A waveform simulation system with a waveform database architecture satisfies different requirements of different waveform simulation tools. The waveform simulation system includes a waveform database configured to store one or more mappings that map one or more design objects to one or more memory addresses. The waveform simulation system also includes a packet processing module configured to receive simulation data from a simulation tool. The packet processing module is configured to translate the simulation data into translated simulation data that is independent of implementation details of the one or more design objects, based at least in part on the one or more mappings. In some cases, the translated simulation data may include event data stored in the waveform database.