# US 8,751,870 B2 · Method and system for providing a random sequence coverage

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,751,870 B2
- Document ID: US8751870B2
- Status: Granted
- Kind: B2
- Application number: 13/231,945
- Filed: 2011-09-13
- Published: 2013-03-14
- Granted: 2014-06-10
- Earliest claimed: 2011-09-13
- Assignees: Whizchip Design Technologies Pvt. Ltd.
- Applicants: Ravishankar Rajarao; Chinthana Ednad; Deepthi Gopalakrishna Kavalur
- Inventors: Ravishankar Rajarao; Chinthana Ednad; Deepthi Gopalakrishna Kavalur
- Web page: https://patentgrep.com/patent/US8751870B2

## CPC

- G06F 11/3676: {for coverage analysis}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The various embodiments of the present invention provide a method and system for providing random sequence coverage. The method comprising receiving a plurality of data packet packets carrying transaction data from a transaction database, specifying transactions in a configuration file along with the transaction data, identifying one or more fields in the packets received from the transaction database, generating an automatic random sequence based on the identification of at least one of a field among the one or more fields in the data packets, generating a coverage report for the random sequence generated automatically and determining uncovered sequences based on the coverage report generated. The system comprises a transaction database for storing transaction data during simulation, a transaction viewer for providing transactions data packets, an auto sequence generator module for generating an automatic random sequence and a report generator module for generating a coverage report for the random sequence generated.

## Claims

### Claim 1

A method for providing a random sequence coverage, the method comprising steps of:
receiving a plurality of data packets carrying transaction data from a transaction database;
specifying transactions in a configuration file along with the transaction data;
identifying one or more fields in the packets received from the transaction database;
generating an automatic random sequence based on the identification of at least one of a field among the one or more fields in the data packets;
generating a coverage report for the random sequence generated automatically, and wherein generating the coverage report comprises providing a user defined configuration file to the auto sequence generation module to generate a first set of sequences, disabling detailed sequence track to perform a coverage summary track, analyzing values obtained from the transaction database and obtaining the missed sequences; and
determining uncovered sequences based on the coverage report generated.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the transaction data is specified by a user during a post process simulation stage.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the transaction data is based on the post processing simulation history.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the configuration file and the transaction data provides for generating a plurality of automated random sequences.

### Claim 5 (depends on 1)

The method according to claim 1, wherein the configuration file comprises an autoseq section including at least one of:
a base name to generate an auto sequence;
a sequence length count; and
a list of transactions.

### Claim 6 (depends on 1)

The method according to claim 1, wherein the configuration file comprises one or more coverage goals and variable transaction relationships.

### Claim 7 (depends on 1)

The method according to claim 1, wherein the generating of the automatic random sequence comprising steps of:
retrieving each of the transaction data by separation of values in one or more fields of a coverage tracker configuration file;
mapping the transaction data with a simformat section of the configuration file; and obtaining a simlog data based on mapping of the transaction data.

### Claim 8 (depends on 1)

The method according to claim 1, wherein generating the coverage report comprises further comprising steps of:
providing a user defined configuration file to the autosequence generation module;
optimizing a coverage tracker data structure by removing the sequences not present in a coverage summary track of the first set of sequences; and
enabling detailed tracking of sequences and log values to generate a report.

### Claim 9 (depends on 1)

The method according to claim 1, wherein disabling detailed sequence track comprises steps of:
checking for uncovered sequences in the automatic random sequence generated;
providing zero hit sequences on a first part of the coverage report; and
providing the hit sequences on a second part of the coverage report.

### Claim 10 (depends on 1)

The method according to claim 1, wherein at least one of the uncovered and covered sequences in the report are determined using a computing algorithm.

### Claim 11 (depends on 1)

The method according to claim 1, wherein the tracking of the automated random sequences and log values provides for generating the coverage report.

### Claim 12 (depends on 1)

The method according to claim 1, wherein the transaction data is extracted and passed to an auto sequence generator module for coverage tracking.

### Claim 13

A system for automatically generating a random sequence, the system comprising:
a transaction database for storing transaction data during simulation;
a transaction viewer for providing transaction data packets;
an auto sequence generator module for generating an automatic random sequence based on the transaction data in the configuration file, and wherein the auto sequence generator module comprises a coverage tracker module and an auto sequence generator core, and wherein the coverage tracker module comprises a coverage tracker core and a coverage tracker parser, and wherein the coverage tracker module is configured to load and parse an user written configuration file, and wherein the auto sequence generator core is configured to generate the automatic random sequences, and wherein the coverage tracker core is configured to perform at least one of a summary tracking of the coverage and a detailed tracking of the coverage, and wherein the coverage tracker parser is configured to load the user written configuration file to the autosequence generator core;
and
a report generator module for generating a coverage report for the random sequence generated automatically.

### Claim 14 (depends on 13)

The system according to claim 13, wherein the auto sequence generator module identifies at least one of a field among the one or more fields in the transaction data packets to generate random sequences.

### Claim 15 (depends on 13)

The system according to claim 13, wherein the transaction data packets includes at least one of a transaction data and the configuration file.
