# US 2018/0024193 A1 · Core testing machine

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

- Number: US 2018/0024193 A1
- Document ID: US20180024193A1
- Status: Published application
- Kind: A1
- Application number: 15/722,235
- Filed: 2017-10-02
- Published: 2018-01-25
- Earliest claimed: 2015-09-25
- Assignees: Contec, LLC
- Applicants: Contec, LLC
- Inventors: Samant Kumar; Dinesh Kumar; Shivashankar Diddimani; Gunjan Samaiya
- Web page: https://patentgrep.com/patent/US20180024193A1

## CPC

- G01R 31/31715: {Testing of input or output circuits; test of circuitry between the I/C pins and the functional core, e.g. testing of input or output driver, receiver, buffer}
- G01R 31/3177: Testing of logic operation, e.g. by logic analysers
- G06F 11/273: Tester hardware, i.e. output processing circuits {(G06F11/263 takes precedence)}
- G01R: MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES (indicating correct tuning of resonant circuits H03J3/12)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A testing system includes a slot configured to receive a device-under-test (DUT), and a core testing processor configured to communicate with a user interface and with the slot, wherein the core testing processor is associated with communication that is independent of any other communications transmitted within the system, and wherein the core testing processor executes a set of tests associated with the DUT.

## Claims

### Claim 1

A testing system, comprising:
a slot configured to receive a device-under-test (DUT); and
a core testing processor configured to communicate with a user interface and with the slot, wherein the core testing processor is associated with communication that is independent of other communications transmitted within the system;
wherein the core testing processor executes a set of tests associated with the DUT.

### Claim 2 (depends on 1)

The system of claim 1, wherein the slot communicates with a lightweight virtualization container configured for association with an interface of a DUT receivable in the slot, the lightweight virtualization container enabling isolation of testing processes and testing resources associated with the DUT receivable in the slot

### Claim 3 (depends on 2)

The system of claim 2, wherein the lightweight virtualization container comprises a testing probe for testing an interface of the DUT receivable in the slot.

### Claim 4 (depends on 1)

The system of claim 1, wherein prior to executing the set of tests associated with the DUT, the core testing processor retrieves at run time a test configuration corresponding to the DUT receivable in the slot, and loads the set of tests associated with the DUT.

### Claim 5 (depends on 1)

The system of claim 1, wherein the core testing processor is associated with a web socket for communication that is independent of other communications transmitted within the system.

### Claim 6 (depends on 2)

The system of claim 2, wherein the lightweight virtualization container is configured to test one or more DUT interfaces at the DUT, each of the DUT interfaces comprising one of:
an Ethernet Local Area Network (LAN) interface;
an Ethernet Wide Area Network (WAN) interface;
a Multimedia over Coax Alliance (MoCA) LAN interface;
a Multimedia over Coax Alliance (MoCA) WAN interface;
a Wireless 2.4 GHz interface;
a Wireless 5.0 GHz interface;
a Foreign eXchange Subscriber ports (FXS) interface;
a Universal Serial Bus (USB) interface;
a video interface; and
an audio interface.

### Claim 7 (depends on 1)

The system of claim 1, wherein the core testing processor communicates using asynchronous feedback and interaction.

### Claim 8 (depends on 1)

The system of claim 1, wherein the core testing processor communicates using Java script object notation (JSON) messages.

### Claim 9 (depends on 1)

The system of claim 1, wherein the core testing processor communicates using TCP/IP protocol.

### Claim 10

A core testing processor configured to
receive serial number information for a plurality of devices under test (DUTs);
retrieve, from a source selected from a database and a web service, type information comprising a make or model of each DUT, retrieval of the type information based upon the serial number information;
load test configuration information specific to each type of DUT;
read a test step of the test configuration information loaded for each DUT;
execute the test step read for each DUT;
determine whether each DUT passed or failed the executed test step;
responsive to a determination that a DUT passed the executed test step, determine whether, for each DUT that passed the executed test step, the loaded test configuration information contains a next test step to be executed;
responsive to a determination that the loaded test configuration contains a next test step to be executed, perform repeated tasks for each DUT for which a next test step exists, the repeated tasks comprising reading the test step, executing the test step read for each DUT, determining whether each DUT passed the executed test step, and determining whether, for each DUT that passed the executed test step, the loaded test configuration information contains a next step to be executed; and
responsive to a determination that the loaded test configuration does not contain a next test step to be executed, terminate the repeating step for each DUT for which a next test step does not exist.

### Claim 11 (depends on 10)

The core testing processor of claim 10, further configured to
responsive to a determination that a DUT failed the executed test step, determine whether to abort testing for each DUT that failed the executed test step; and
responsive to a determination to not abort testing, perform the repeated tasks until reaching the determination that the loaded test configuration does not contain a next test step to be executed.

### Claim 12 (depends on 11)

The core testing processor of claim 11, further configured to, responsive to a determination to abort testing, indicate testing failure for each DUT for which a determination to abort testing has been made.

### Claim 13 (depends on 11)

The core testing processor of claim 11, further configured to communicate, upon completion of each test step, results of the completed test step to a user.

### Claim 14 (depends on 13)

The core testing processor of claim 13, wherein communicating the results of the completed test step to the user comprises sending a message to a browser of the user via web-sockets.

### Claim 15 (depends on 10)

A system for testing devices, comprising:
the core testing processor of claim 10; and
a slot configured to receive a device-under-test (DUT), the slot communicating with the core testing processor and with a lightweight virtualization container configured for association with an interface of a DUT receivable in the slot, the lightweight virtualization container enabling isolation of testing processes and testing resources associated with the DUT receivable in the slot.

### Claim 16 (depends on 15)

The system for testing devises of claim 15, where in the core testing processor is configured to communicate with a user interface and with the slot, wherein the core testing processor is associated with communication that is independent of other communications transmitted within the system.

### Claim 17 (depends on 16)

The system for testing devices of claim 16, wherein the core testing processor is associated with a web socket for communication that is independent of other communications transmitted within the system.
