Automatic Application-Rule Checker for IC Design

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for integrated circuit design, such as U.S. Pat. Nos. 6,078,737, 5,903,469, and 6,735,749, fail to guarantee first silicon success by not checking the application and usage correctness of libraries and intellectual properties (IPs), which is crucial for ensuring the correct interaction between library and library, library and IP, and IP and IP, leading to increased design costs and time-to-market due to manual and complex application-rule checks.

Innovation Solution

An automatic application-rule checking system that extracts instance-level information from the integrated circuit design database using an abstract file containing physical and electrical information, and performs application-rule checks using a command file with logic operations, ensuring compliance with application rules without requiring detailed device-level information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual inspection of application notes is performed, then application rules can be checked, but the complexity and time consumption increase significantly

Engineering Contradiction:
Improveapplication rule check correctnessVSAvoidchecking process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces manual mechanical inspection with an automated electronic checking system. The application-rule checker automatically extracts instance-level information from GDS files and compares it against application rules stored in databases, eliminating the need for manual review of lengthy application notes while maintaining check completeness.

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

Solution Approach 2:

The patent introduces an intermediary automated checking system that mediates between the design data (GDS files) and application rules. This intermediary system extracts instance-level information, matches it against library/IP instances, and automatically verifies compliance with application rules, reducing direct human involvement.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual inspection of application notes is performed, then application rules can be checked, but the time consumption increases significantly

Engineering Contradiction:
Improveapplication rule check correctnessVSAvoidchecking time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces time-consuming manual inspection with automated electronic processing. The system rapidly extracts instance-level information from GDS files, compares it against application rules in databases, and generates compliance reports automatically, reducing checking time from hours or days to minutes or seconds.

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

Solution Approach 2:

The patent performs preliminary extraction of instance-level information from design data before the actual compliance checking. This pre-processing step organizes and structures the data in advance, enabling faster and more efficient application rule verification during the checking phase.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If detailed device-level information is used for checking, then checking accuracy improves, but data processing complexity increases

Engineering Contradiction:
Improvechecking accuracyVSAvoiddata processing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts only the necessary instance-level information from GDS files, such as instance types, locations, and connections, rather than processing all detailed device-level data. This selective extraction maintains checking accuracy by focusing on relevant parameters while significantly reducing data processing complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the checking process into distinct phases: extracting instance-level information, matching against library/IP instances, and verifying application rules. This segmentation allows the system to process data in manageable chunks, improving efficiency without sacrificing accuracy.

Inventive Principle:
Principle #1Segmentation

4Reliability

If application rules are specified in lengthy application notes, then comprehensive rules can be documented, but user comprehension becomes extremely difficult

Engineering Contradiction:
Improveapplication rule completenessVSAvoiduser comprehension
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent replaces manual reading and comprehension of lengthy application notes with automated electronic checking. The system directly interprets application rules from structured databases and automatically applies them to design data, eliminating the need for users to comprehend complex documentation while maintaining rule completeness.

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

Solution Approach 2:

The patent introduces an intermediary automated system that mediates between the comprehensive application rules and the user. This system handles the complexity of rule interpretation and application internally, presenting users with simplified compliance results rather than requiring them to navigate complex documentation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8943453B2Automatic application-rule checker
Publication Date: 2015.01.27 TAIWAN SEMICONDUCTOR MANUFACTURING CO LTD
  • US8943453B2 patent drawing
  • US8943453B2 patent drawing
  • US8943453B2 patent drawing

AI summary

A method of checking an integrated circuit design database includes providing the integrated circuit design stored in a storage media; providing application rules; and providing an instance abstract of instances of libraries and IP(s). Instance-level information is extracted from the integrated circuit design database. An application-rule check is performed against the instance-level information using the information provided in an abstract file.