Coverage Data Interchange via Binary Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Unified Coverage Interoperability Standard (UCIS) faces challenges in efficiently exchanging coverage data between non-binary compatible coverage databases due to inconsistencies between internal data representations and XML exchange formats, leading to large and resource-intensive XML files.
Innovation Solution
A computing system is implemented to extract coverage data from a source database using API routines specific to the source database, classify it into a UCIS-compliant format, and transfer it to a target database using corresponding API routines, facilitating data interchange between different coverage databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If XML format is used for coverage data exchange according to UCIS, then interoperability between different vendor databases is improved, but file size increases hundreds of times and processing resources are consumed
Solution Approach 1:
The patent introduces an intermediary binary format that sits between the internal database representations and the XML exchange format. This intermediary format enables data exchange between different vendor databases while avoiding the excessive size and processing overhead of direct XML conversion. The binary format acts as a mediator that preserves interoperability benefits without incurring the full cost of XML serialization.
Solution Approach 2:
The patent changes the parameter of data representation from text-based XML to binary format for the exchange mechanism. This parameter change maintains the standardization and interoperability goals of UCIS while dramatically reducing file size and processing requirements. The binary format uses different encoding parameters (binary vs. text) to achieve the same interoperability function more efficiently.
2Quantity of substance
If XML compression is applied to reduce file size, then storage space is improved, but processing time increases and compressed files remain multiple times larger than binary representation
Solution Approach 1:
The patent applies preliminary action by converting data to binary format before exchange operations rather than compressing XML after generation. This preliminary conversion to an efficient format prevents the need for subsequent compression and decompression operations, eliminating the associated processing time overhead while achieving even smaller file sizes than compressed XML.
3Adaptability or versatility
If coverage data is exchanged between non-binary compatible databases, then vendor interoperability is enabled, but data inconsistency and loss occur due to representation differences
Solution Approach 1:
The patent uses copying by creating a standardized binary representation of coverage data that can be replicated across different vendor databases. Instead of directly transforming data between incompatible formats (which risks inconsistency), the system copies data into a standardized binary format that preserves integrity while enabling exchange. This copying approach maintains data consistency across vendor boundaries.
Data Source
AI summary
This application discloses a computing system implementing a source application to extract coverage data from a source database with application program interface (API) routines specific to the source database, and classify the coverage data according to a Unified Coverage Interoperability Standard (UCIS)-compliant format. The coverage data can include at least one of data from verification operations performed on a circuit design, test information utilized during the verification operations, or at least one test plan. The computing system implementing the source application can, based on the classification, select exchange routines to transfer the coverage data towards a target database. The computing system can implement a target application to utilize the classification of the coverage data to identify corresponding API routines specific to the target database, and write the coverage data to the target database with the identified API routines.