# US 2024/0005013 A1 · Testing-and-Manufacturing Keys for a System-on-Chip

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

- Number: US 2024/0005013 A1
- Document ID: US20240005013A1
- Status: Published application
- Kind: A1
- Application number: 18/249,698
- Filed: 2020-10-27
- Published: 2024-01-04
- Earliest claimed: 2020-10-27
- Assignees: Google Inc.
- Applicants: Google LLC
- Inventors: Andrei Tudor Stratan; Randall R. Spangler
- Web page: https://patentgrep.com/patent/US20240005013A1

## CPC

- G06F 21/62: Protecting access to data via a platform, e.g. using keys or access control rules
- G06F 21/74: operating in dual or compartmented mode, i.e. at least one secure mode
- G06F 11/2273: {Test methods}
- G06F 21/44: Program or device authentication
- G06F 21/85: interconnection devices, e.g. bus-connected or in-line devices
- G06F 2221/034: Test or assess a computer or a system
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and techniques are described for implementing testing-and-manufacturing keys for a system-on-chip (SoC). A hardware test portion of the SoC is configured to exercise features of domains that process data being communicated across the fabrics during an externally initiated test. In response to receiving a testing-and-manufacturing token from an external test system, a testing-and-manufacturing key support component of the SoC generates a testing-and-manufacturing key. The hardware test portion is configured to execute a test function to promote security of the SoC, however, only in response to the testing-and-manufacturing security component authenticating the testing-and-manufacturing key. Through implementing testing-and-manufacturing keys this way, the system-on-chip secures access to potentially sensitive functions and secrets, while allowing their unencumbered and authorized access for testing the system-on-chip during various life cycle states.

## Claims

### Claim 1

A method comprising:
receiving, by a system-on-chip, from an external test system, a testing-and-manufacturing token for the external test system;
generating, by the system-on-chip and based on the testing-and-manufacturing token, a testing-and-manufacturing key for authorizing access to test functions of the system-on-chip;
attempting authentication of the testing-and-manufacturing key based on a secret key maintained by the system-on-chip; and
responsive to authenticating the testing-and-manufacturing key based on the secret key, outputting, to the external test system, an indication of whether one or more domains or one or more fabrics of the system-on-chip passed or failed a test involving the test functions of the system-on-chip.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
causing the one or more domains to execute instructions that check whether the one or more domains of the system-on-chip pass or fail the test functions of the system-on-chip.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
causing the one or more fabrics to carry data during a check of whether the one or more fabrics of the system-on-chip pass or fail the test functions of the system-on-chip.

### Claim 4 (depends on 1)

The method of claim 1, wherein receiving the testing-and-manufacturing token for the external test system comprises receiving the testing-and-manufacturing token using a testing-and-manufacturing security component of the system-on-chip that is physically coupled to the external test system.

### Claim 5 (depends on 4)

The method of claim 4, wherein generating the testing-and-manufacturing key comprises generating the testing-and-manufacturing key using the testing-and-manufacturing security component of the system-on-chip.

### Claim 6 (depends on 5)

The method of claim 5, wherein the testing-and-manufacturing token comprises an authorization payload and an identification segment that is indicative of the one or more domains and the one or more fabrics intended for a test, and generating the testing-and-manufacturing key comprises generating, based in part on the authorization payload and the identification segment, the testing-and-manufacturing key.

### Claim 7 (depends on 4)

The method of claim 4, further comprising:
transitioning the testing-and-manufacturing security component from a dormant state to a wake state in response detecting the external test system that is physically coupled to the system-on-chip.

### Claim 8 (depends on 4)

The method of claim 4, wherein attempting authentication of the testing-and-manufacturing key based on the secret key comprises:
maintaining, by the testing-and-manufacturing security component, the secret key; and
responsive to the testing-and-manufacturing security component authenticating the testing-and-manufacturing key, executing the test using a hardware test portion that is separate from the testing-and-manufacturing security component.

### Claim 9 (depends on 8)

The method of claim 8, wherein the hardware test portion is communicatively isolated from the external test system.

### Claim 10 (depends on 9)

The method of claim 9, wherein the testing-and-manufacturing token further comprises a test command and one or more parameters, the method further comprising:
further responsive to authenticating the testing-and-manufacturing key based on the secret key, executing, based on the test command and the one or more parameters, the test involving the test functions of the system-on-chip.

### Claim 11 (depends on 4)

The method of claim 4, further comprising:
receiving, by the hardware test portion and from the testing-and-manufacturing security component of the system-on-chip, a signal indicative of the testing-and-manufacturing key.

### Claim 12 (depends on 11)

The method of claim 11, wherein the signal is further indicative of one or more parameters for the test functions.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
receiving, by the system-on-chip, from the external test system, another testing-and-manufacturing token for the external test system;
generating, by the system-on-chip, based on the other testing-and-manufacturing token, another testing-and-manufacturing key for authorizing access to the test functions of the system-on-chip;
attempting authentication of the other testing-and-manufacturing key based on the secret key maintained by the system-on-chip; and
responsive to failing to authenticate the other testing-and-manufacturing key based on the secret key, refraining, by the system-on-chip, from executing the test involving the test functions of the system-on-chip to protect the test functions and other secrets maintained by the system-on-chip.

### Claim 14

(canceled)

### Claim 15

(canceled)

### Claim 16

A system-on-chip comprising:
one or more processors; and
memory storing one or more programs to be executed by the one or more processors, the one or more programs comprising instructions for:
receiving, by a system-on-chip, from an external test system, a testing-and-manufacturing token for the external test system;
generating, by the system-on-chip and based on the testing-and-manufacturing token, a testing-and-manufacturing key for authorizing access to test functions of the system-on-chip;
attempting authentication of the testing-and-manufacturing key based on a secret key maintained by the system-on-chip; and
responsive to authenticating the testing-and-manufacturing key based on the secret key, outputting, to the external test system, an indication of whether one or more domains or one or more fabrics of the system-on-chip passed or failed a test involving the test functions of the system-on-chip.

### Claim 17 (depends on 16)

The system-on-chip of claim 16, wherein the one or more programs further comprise instructions for at least one of:
causing the one or more domains to execute instructions that check whether the one or more domains of the system-on-chip pass or fail the test functions of the system-on-chip; or
causing the one or more fabrics to carry data during a check of whether the one or more fabrics of the system-on-chip pass or fail the test functions of the system-on-chip.

### Claim 18 (depends on 16)

The system-on-chip of claim 16, wherein receiving the testing-and-manufacturing token for the external test system comprises receiving the testing-and-manufacturing token using a testing-and-manufacturing security component of the system-on-chip that is physically coupled to the external test system.

### Claim 19 (depends on 18)

The system-on-chip of claim 18, wherein generating the testing-and-manufacturing key comprises generating the testing-and-manufacturing key using the testing-and-manufacturing security component of the system-on-chip.

### Claim 20 (depends on 19)

The system-on-chip of claim 19, wherein the testing-and-manufacturing token comprises an authorization payload and an identification segment that is indicative of the one or more domains and the one or more fabrics intended for a test, and generating the testing-and-manufacturing key comprises generating, based in part on the authorization payload and the identification segment, the testing-and-manufacturing key.

### Claim 21 (depends on 18)

The system-on-chip of claim 18, wherein the one or more programs further comprise instructions for:
transitioning the testing-and-manufacturing security component from a dormant state to a wake state in response detecting the external test system that is physically coupled to the system-on-chip.

### Claim 22 (depends on 18)

The system-on-chip of claim 18, wherein attempting authentication of the testing-and-manufacturing key based on the secret key comprises:
maintaining, by the testing-and-manufacturing security component, the secret key; and
responsive to the testing-and-manufacturing security component authenticating the testing-and-manufacturing key, executing the test using a hardware test portion that is separate from the testing-and-manufacturing security component.
