# US 2025/0094268 A1 · Performance And Power Efficient Link Error Recovery In Inter-chiplet Communication

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

- Number: US 2025/0094268 A1
- Document ID: US20250094268A1
- Status: Published application
- Kind: A1
- Application number: 18/468,479
- Filed: 2023-09-15
- Published: 2025-03-20
- Earliest claimed: 2023-09-15
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Santhosh Reddy AKAVARAM; Prakhar SRIVASTAVA; Sridhar ANUMALA; Chintalapati BHARATH SAI VARMA
- Web page: https://patentgrep.com/patent/US20250094268A1

## CPC

- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- G06F 13/4265: {on a point to point bus (G06F13/4247, G06F13/4282 take precedence)}
- G06F 11/0745: {in an input/output transactions management context (input/output processing in general G06F13/00)}
- G06F 11/0772: {Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers}
- G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)}
- G06F 11/1443: {Transmit or communication errors}
- G06F 11/3041: {where the computing system component is an input/output interface (interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units G06F13/00)}
- G06F 13/42: Bus transfer protocol, e.g. handshake; Synchronisation
- G06F 13/4282: {on a serial bus, e.g. I2C bus, SPI bus (on daisy chain buses G06F13/4247)}
- H04L 41/0659: by isolating or reconfiguring faulty entities
- H04L 41/0663: Performing the actions predefined by failover planning, e.g. switching to standby network elements
- H04L 41/0677: Localisation of faults
- H04L 43/0823: Errors, e.g. transmission errors
- G06F 2213/0026: PCI express
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Various embodiments include methods and devices for efficiently recovering from errors that occur in part but not all of a universal chiplet interconnect express (UCIe) link for chiplets of a computing device. Various embodiments may include identifying a first part of a UCIe link in which an error has occurred, and training the first part of the UCIe link in which the error has occurred while maintaining active a second part of the UCIe link in which no error has occurred.

## Claims

### Claim 1

A method for managing errors occurring in parts of a universal chiplet interconnect express (UCIe) link for chiplets of a computing device, comprising:
identifying a first part of a UCIe link in which an error has occurred;
training the first part of the UCIe link in which the error has occurred; and
maintaining active a second part of the UCIe link in which no error has occurred while training the first part of the UCIe link in which the error has occurred.

### Claim 2 (depends on 1)

The method of claim 1, wherein:
the first part of the UCIe link is a sideband;
the second part of the UCIe link is a mainband; and
identifying the first part of a UCIe link in which the error has occurred includes:
identifying a timeout for a sideband message;
setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the sideband in response to identifying the timeout for the sideband message; and
reading the value configured to indicate to the computing device the occurrence of the error in the sideband from the error recovery structure.

### Claim 3 (depends on 1)

The method of claim 1, wherein:
the first part of the UCIe link is a sideband;
the second part of the UCIe link is a mainband;
training the first part of the UCIe link in which the error has occurred includes:
toggling power to the sideband; and
transitioning from a sideband initialization state directly to a link initialization state; and
maintaining active the second part of the UCIe link in which no error has occurred while training the first part of the UCIe link in which the error has occurred includes maintaining power to the mainband while training the sideband.

### Claim 4 (depends on 1)

The method of claim 1, wherein:
the first part of the UCIe link is a mainband;
the second part of the UCIe link is a sideband; and
identifying the first part of a UCIe link in which the error has occurred includes:
identifying a handshake request for entering an error state;
setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the mainband in response to identifying the handshake request for entering the error state; and
reading the value configured to indicate to the computing device the occurrence of the error in the mainband from the error recovery structure.

### Claim 5 (depends on 1)

The method of claim 1, wherein:
the first part of the UCIe link is a mainband;
the second part of the UCIe link is a sideband;
training the first part of the UCIe link in which the error has occurred includes:
toggling power to the mainband; and
transitioning from a reset state directly to a mainband initialization state; and
maintaining active the second part of the UCIe link in which no error has occurred while training the first part of the UCIe link in which the error has occurred includes maintaining power to the sideband while training the mainband.

### Claim 6 (depends on 1)

The method of claim 1, wherein:
the first part of the UCIe link is a mainband and a sideband;
the second part of the UCIe link is no part of the UCIe link; and
identifying the first part of a UCIe link in which the error has occurred includes:
identifying a handshake request for entering an error state;
identifying a timeout for a handshake response for entering the error state;
setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the mainband and the sideband in response to identifying the handshake request and identifying the timeout for the handshake response for entering the error state; and
reading the value configured to indicate to the computing device the occurrence of the error in the mainband and the sideband from the error recovery structure.

### Claim 7 (depends on 1)

The method of claim 1, wherein:
the first part of the UCIe link is a mainband and a sideband;
the second part of the UCIe link is no part of the UCIe link; and
training the first part of the UCIe link in which the error has occurred includes:
toggling power to the mainband and to the sideband; and
transitioning from a sideband initialization to a mainband initialization state.

### Claim 8

A computing device, comprising:
at least two chiplets; and
a universal chiplet interconnect express (UCIe) link configuration device coupled to the at least two chiplets and configured to:
identify a first part of a UCIe link between the at least two chiplets in which an error has occurred;
train the first part of the UCIe link in which the error has occurred; and
maintain active a second part of the UCIe link in which no error has occurred while training the first part of the UCIe link in which the error has occurred.

### Claim 9 (depends on 8)

The computing device of claim 8, wherein:
the first part of the UCIe link is a sideband;
the second part of the UCIe link is a mainband; and
the UCIe link configuration device is further configured to identify the first part of a UCIe link in which the error has occurred by:
identifying a timeout for a sideband message;
setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the sideband in response to identifying the timeout for the sideband message; and
reading the value configured to indicate to the computing device the occurrence of the error in the sideband from the error recovery structure.

### Claim 10 (depends on 8)

The computing device of claim 8, wherein:
the first part of the UCIe link is a sideband;
the second part of the UCIe link is a mainband;
the UCIe link configuration device is further configured to train the first part of the UCIe link in which the error has occurred by:
toggling power to the sideband; and
transitioning from a sideband initialization state directly to a link initialization state; and
the UCIe link configuration device is further configured to maintain power to the mainband while training the sideband.

### Claim 11 (depends on 8)

The computing device of claim 8, wherein:
the first part of the UCIe link is a mainband;
the second part of the UCIe link is a sideband; and
the UCIe link configuration device is further configured to identify the first part of the UCIe link in which the error has occurred by:
identifying a handshake request for entering an error state;
setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the mainband in response to identifying the handshake request for entering the error state; and
reading the value configured to indicate to the computing device the occurrence of the error in the mainband from the error recovery structure.

### Claim 12 (depends on 8)

The computing device of claim 8, wherein:
the first part of the UCIe link is a mainband;
the second part of the UCIe link is a sideband; and
the UCIe link configuration device is further configured to train the first part of the UCIe link in which the error has occurred includes:
toggling power to the mainband; and
transitioning from a reset state directly to a mainband initialization state; and
the UCIe link configuration device is further configured to maintain power to the sideband while training the mainband.

### Claim 13 (depends on 8)

The computing device of claim 8, wherein:
the first part of the UCIe link is a mainband and a sideband;
the second part of the UCIe link is no part of the UCIe link; and
the UCIe link configuration device is further configured to identify the first part of a UCIe link in which the error has occurred by:
identifying a handshake request for entering an error state;
identifying a timeout for a handshake response for entering the error state;
setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the mainband and the sideband in response to identifying the handshake request and identifying the timeout for the handshake response for entering the error state; and
reading the value configured to indicate to the computing device the occurrence of the error in the mainband and the sideband from the error recovery structure.

### Claim 14 (depends on 8)

The computing device of claim 8, wherein:
the first part of the UCIe link is a mainband and a sideband,
the second part of the UCIe link is no part of the UCIe link, and
the UCIe link configuration device is further configured to train the first part of the UCIe link in which the error has occurred by:
toggling power to the mainband and to the sideband; and
transitioning from a sideband initialization to a mainband initialization state.

### Claim 15

A computing device, comprising:
means for identifying a first part of a chiplet interconnect express (UCIe) link in which an error has occurred;
means for training the first part of the UCIe link in which the error has occurred; and
means for maintaining active a second part of the UCIe link in which no error has occurred while training the first part of the UCIe link in which the error has occurred.

### Claim 16 (depends on 15)

The computing device of claim 15, wherein:
the first part of the UCIe link is a sideband;
the second part of the UCIe link is a mainband; and
means for identifying the first part of a UCIe link in which the error has occurred comprises: identifying a timeout for a sideband message;
means for setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the sideband in response to identifying the timeout for the sideband message; and
means for reading the value configured to indicate to the computing device the occurrence of the error in the sideband from the error recovery structure.

### Claim 17 (depends on 15)

The computing device of claim 15, wherein:
the first part of the UCIe link is a sideband;
the second part of the UCIe link is a mainband;
means for training the first part of the UCIe link in which the error has occurred comprises:
means for toggling power to the sideband; and
means for transitioning from a sideband initialization state directly to a link initialization state; and
means for maintaining active the second part of the UCIe link in which no error has occurred while training the first part of the UCIe link in which the error has occurred includes means for maintaining power to the mainband while training the sideband.

### Claim 18 (depends on 15)

The computing device of claim 15, wherein:
the first part of the UCIe link is a mainband;
the second part of the UCIe link is a sideband; and
means for identifying the first part of a UCIe link in which the error has occurred comprises:
means for identifying a handshake request for entering an error state;
means for setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the mainband in response to identifying the handshake request for entering the error state; and
means for reading the value configured to indicate to the computing device the occurrence of the error in the mainband from the error recovery structure.

### Claim 19 (depends on 15)

The computing device of claim 15, wherein:
the first part of the UCIe link is a mainband;
the second part of the UCIe link is a sideband; and
means for training the first part of the UCIe link in which the error has occurred comprises:
means for toggling power to the mainband; and
means for transitioning from a reset state directly to a mainband initialization state; and
means for maintaining active the second part of the UCIe link in which no error has occurred while training the first part of the UCIe link in which the error has occurred includes means for maintaining power to the sideband while training the mainband.

### Claim 20 (depends on 15)

The computing device of claim 15, wherein:
the first part of the UCIe link is a mainband and a sideband;
the second part of the UCIe link is no part of the UCIe link; and
means for identifying the first part of a UCIe link in which the error has occurred comprises:
means for identifying a handshake request for entering an error state;
means for identifying a timeout for a handshake response for entering the error state;
means for setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the mainband and the sideband in response to identifying the handshake request and identifying the timeout for the handshake response for entering the error state; and
means for reading the value configured to indicate to the computing device the occurrence of the error in the mainband and the sideband from the error recovery structure.

### Claim 21 (depends on 15)

The computing device of claim 15, wherein:
the first part of the UCIe link is a mainband and a sideband,
the second part of the UCIe link is no part of the UCIe link, and
means for training the first part of the UCIe link in which the error has occurred comprises:
means for toggling power to the mainband and to the sideband; and
means for transitioning from a sideband initialization to a mainband initialization state.

### Claim 22

A universal chiplet interconnect express (UCIe) link configuration device for use in a computing device including at least two chiplets, the UCIe link configuration device configured to:
identify a first part of a UCIe link between two chiplets in which an error has occurred;
train the first part of the UCIe link in which the error has occurred; and
maintain active a second part of the UCIe link in which no error has occurred while training the first part of the UCIe link in which the error has occurred.

### Claim 23 (depends on 22)

The UCIe link configuration device of claim 22, wherein:
the first part of the UCIe link is a sideband;
the second part of the UCIe link is a mainband; and
the UCIe link configuration device is further configured to identify the first part of a UCIe link in which the error has occurred by:
identifying a timeout for a sideband message;
setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the sideband in response to identifying the timeout for the sideband message; and
reading the value configured to indicate to the computing device the occurrence of the error in the sideband from the error recovery structure.

### Claim 24 (depends on 22)

The UCIe link configuration device of claim 22, wherein:
the first part of the UCIe link is a sideband;
the second part of the UCIe link is a mainband;
the UCIe link configuration device is further configured to train the first part of the UCIe link in which the error has occurred by:
toggling power to the sideband; and
transitioning from a sideband initialization state directly to a link initialization state; and
the UCIe link configuration device is further configured to maintain power to the mainband while training the sideband.

### Claim 25 (depends on 22)

The UCIe link configuration device of claim 22, wherein:
the first part of the UCIe link is a mainband;
the second part of the UCIe link is a sideband; and
the UCIe link configuration device is further configured to identify the first part of the UCIe link in which the error has occurred by:
identifying a handshake request for entering an error state;
setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the mainband in response to identifying the handshake request for entering the error state; and
reading the value configured to indicate to the computing device the occurrence of the error in the mainband from the error recovery structure.

### Claim 26 (depends on 22)

The UCIe link configuration device of claim 22, wherein:
the first part of the UCIe link is a mainband;
the second part of the UCIe link is a sideband; and
the UCIe link configuration device is further configured to train the first part of the UCIe link in which the error has occurred includes:
toggling power to the mainband; and
transitioning from a reset state directly to a mainband initialization state; and
the UCIe link configuration device is further configured to maintain power to the sideband while training the mainband.

### Claim 27 (depends on 22)

The UCIe link configuration device of claim 22, wherein:
the first part of the UCIe link is a mainband and a sideband;
the second part of the UCIe link is no part of the UCIe link; and
the UCIe link configuration device is further configured to identify the first part of a UCIe link in which the error has occurred by:
identifying a handshake request for entering an error state;
identifying a timeout for a handshake response for entering the error state;
setting a UCIe link error recovery structure with a value configured to indicate to the computing device an occurrence of the error in the mainband and the sideband in response to identifying the handshake request and identifying the timeout for the handshake response for entering the error state; and
reading the value configured to indicate to the computing device the occurrence of the error in the mainband and the sideband from the error recovery structure.

### Claim 28 (depends on 22)

The UCIe link configuration device of claim 22, wherein:
the first part of the UCIe link is a mainband and a sideband,
the second part of the UCIe link is no part of the UCIe link, and
the UCIe link configuration device is further configured to train the first part of the UCIe link in which the error has occurred by:
toggling power to the mainband and to the sideband; and
transitioning from a sideband initialization to a mainband initialization state.
