Node Impedance State Analysis with Reasoning Engine

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional EDA software systems cannot provide reasons for the impedance state of nodes in a circuit design, making it difficult to debug and resolve impedance-related issues such as high-impedance nodes.

Innovation Solution

The system analyzes impedance states of nodes in a circuit design and provides reasons for these states through textual descriptions or graphical annotations on circuit schematics, including conductive paths and component parameters, during transient analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If traditional EDA software performs transient analysis to determine node impedance states, then the impedance state (highz or lowz) can be identified, but the system cannot provide reasons or explanations for why nodes are in high-impedance state

Engineering Contradiction:
Improveinformation about impedance state reasonsVSAvoidcomplexity of analysis system
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary component (reasoning engine or analysis module) that acts as a mediator between the transient analysis results and the final output. This intermediary analyzes the circuit netlist, identifies conducting paths, and generates human-readable explanations for impedance states without requiring changes to the core simulation engine, thus adding functionality while maintaining modular system architecture

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The analysis system is segmented into distinct functional modules: one module performs transient analysis to determine impedance states, while another separate module analyzes the circuit netlist to generate reasons for those states. This segmentation allows each module to specialize in its specific task and enables independent optimization and maintenance of each component

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If the system provides detailed reasons and annotations for node impedance states, then debugging effectiveness is improved, but the complexity of the analysis process increases

Engineering Contradiction:
Improveease of debuggingVSAvoidcomplexity of analysis process
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically analyzing its own analysis results and generating explanations without requiring external intervention. The reasoning engine autonomously traces conducting paths through the circuit netlist and formulates reasons for impedance states, eliminating the need for manual circuit analysis by engineers while providing comprehensive debugging information

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback by taking the impedance state results from transient analysis and using them to guide the reasoning process. The generated reasons are fed back to the user in a comprehensible format, and the system can iteratively refine its analysis based on user interactions or additional circuit parameters, creating a closed-loop debugging assistance system

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10318682B1Systems and methods for analyzing node impedance state
Publication Date: 2019.06.11 CADENCE DESIGN SYST INC
  • US10318682B1 patent drawing
  • US10318682B1 patent drawing
  • US10318682B1 patent drawing

AI summary

Various embodiments provide for analyzing impedance states of a set of nodes in a circuit design and providing a set of reasons for those impedance states. The set of reasons can include a reason regarding why a particular node is reported as being in high-impedance (highz) state or in low-impedance (lowz) state, and the reason may be for a specific time point during transient analysis of the circuit design. Some embodiments are implemented within a debugging utility of an electronic design automation (EDA) software system.