US 12,487,286 B2
Diagnostic tool for traffic capture with known signature database
Linden Hsu, San Jose, CA (US); Boilam Phan, San Jose, CA (US); and Rotem Nahum, San Jose, CA (US)
Assigned to Advantest Corporation, Tokyo (JP)
Filed by Advantest Corporation, Tokyo (JP)
Filed on Feb. 19, 2021, as Appl. No. 17/180,618.
Application 17/180,618 is a continuation in part of application No. 17/127,596, filed on Dec. 18, 2020.
Application 17/127,596 is a continuation in part of application No. 15/981,634, filed on May 16, 2018, granted, now 10,929,260.
Prior Publication US 2021/0173010 A1, Jun. 10, 2021
This patent is subject to a terminal disclaimer.
Int. Cl. G01R 31/319 (2006.01); G01R 31/3183 (2006.01); G01R 31/3193 (2006.01)
CPC G01R 31/31917 (2013.01) [G01R 31/318307 (2013.01); G01R 31/318314 (2013.01); G01R 31/31901 (2013.01); G01R 31/3193 (2013.01)] 19 Claims
OG exemplary drawing
 
1. A method of identifying error patterns during automated device testing, the method comprising:
receiving a data pattern from a plurality of capture modules programmed on a programmable logic device, wherein the programmable logic device is operable to generate commands and data to test a plurality of devices under test (DUTs), wherein the plurality of capture modules are programmable and operable to selectively capture data traffic to be monitored, wherein the data traffic comprises a flow of traffic between the plurality of DUTs and the programmable logic device, wherein the plurality of capture modules each include acquisition logic and capture memory, wherein the programmable logic device includes a transfer interface coupled to the plurality of capture modules, and wherein each programmed capture module is operable to analyze the data pattern and identify an error condition, wherein analyzing and identifying comprises:
comparing the data pattern of the data traffic between a DUT and the programmable logic device captured by the plurality of capture modules with known signatures in a database, wherein the database further includes metadata that associates an error signature of each error with a type of capture module, a method of identification, a cause of error and a suggested action to take in response to the error;
correlating the data pattern with one or more matching known signatures stored in the database;
assigning a score to each of the one or more matching known signatures in the database based a level of correlation thereof; and
taking a predetermined action based on the score of the one or more matching known signatures and the associated action to take in response to the error associated with the one or more matching known signatures in the database.