# US 2026/0093604 A1 · Device data access via a management controller

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

- Number: US 2026/0093604 A1
- Document ID: US20260093604A1
- Status: Published application
- Kind: A1
- Application number: 19/412,086
- Filed: 2025-12-08
- Published: 2026-04-02
- Earliest claimed: 2025-12-08
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: Patrick G. KUTCH; Brian P. JOHNSON
- Web page: https://patentgrep.com/patent/US20260093604A1

## CPC

- G06F 11/0784: {Routing of error reports, e.g. with a specific transmission path or data flow}
- G06F 11/366: {using diagnostics (G06F11/0703 takes precedence)}
- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Examples described herein relate to a first interface to a device; a second interface to the device; and a circuitry to: based on inoperability of the first interface or inoperability of the device, utilize the second interface to communicate with the device and to retrieve debug data from the device and provide the debug data to a requester, wherein the first and second interfaces utilize different protocols. In some examples, the debug data comprises three or more of: timestamped events, error messages, informational messages generated by the device's firmware or software, connectivity errors, hardware errors, or system events.

## Claims

### Claim 1

An apparatus comprising:
a first interface to a device;
a second interface to the device; and
a circuitry to:
based on inoperability of the first interface or inoperability of the device, utilize the second interface to communicate with the device and to retrieve debug data from the device and provide the debug data to a requester, wherein the first and second interfaces utilize different protocols.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the debug data comprises three or more of: timestamped events, error messages, informational messages generated by the device's firmware or software, connectivity errors, hardware errors, or system events.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein:
the circuitry comprises a management controller to manage and monitor operation the device.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein:
the circuitry is to permit or deny accesses to the device through the second interface based on a configuration.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein:
the first interface comprises a device interface,
the second interface comprises a management controller interface to the device, and
the management controller interface is to remain operative despite inoperability of the device and inoperability of the first interface.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein:
the first interface is to operate in a manner consistent with a Peripheral Component Interface express (PCIe) protocol and
the second interface is to communicate with the device based on a Distributed Management Task Force (DMTF) protocol.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the device comprises one or more of: an accelerator, graphics processing unit (GPU), storage device, memory device, or network interface device.

### Claim 8

At least one non-transitory computer-readable medium comprising instructions stored thereon, that when executed by one or more processors, cause the one or more processors to:
configure circuitry to:
based on inoperability of a first interface to a device or inoperability of the device, utilize a second interface to communicate with the device and to retrieve data from the device and provide the data to a requester, wherein the first and second interfaces utilize different protocols.

### Claim 9 (depends on 8)

The computer-readable medium of claim 8, wherein the data comprises three or more of: timestamped events, error messages, informational messages generated by the device's firmware or software, connectivity errors, hardware errors, or system events.

### Claim 10 (depends on 8)

The computer-readable medium of claim 8, wherein the circuitry comprises a management controller to manage and monitor operation the device.

### Claim 11 (depends on 8)

The computer-readable medium of claim 8, wherein the circuitry is to permit or deny accesses to the device through the second interface based on a configuration.

### Claim 12 (depends on 8)

The computer-readable medium of claim 8, wherein
the first interface comprises a device interface,
the second interface comprises a management controller interface to the device, and
the management controller interface is to remain operative despite inoperability of the device.

### Claim 13 (depends on 8)

The computer-readable medium of claim 8, wherein:
the first interface is to operate in a manner consistent with a Peripheral Component Interface express (PCIe) protocol and
the second interface is to communicate with the device based on a Distributed Management Task Force (DMTF) protocol comprising one or more of: Network Controller Sideband Interface (NC-SI), Management Component Transport Protocol (MCTP), Platform Level Data Model (PLDM).

### Claim 14

A method comprising:
based on inoperability of a first interface to a device or inoperability of the device, utilizing a second interface to communicate with the device for retrieving data from the device and
providing the data to a requester, wherein the first and second interfaces utilize different protocols.

### Claim 15 (depends on 14)

The method of claim 14, wherein the data comprises three or more of: timestamped events, error messages, informational messages generated by the device's firmware or software, connectivity errors, hardware errors, or system events.

### Claim 16 (depends on 14)

The method of claim 14, comprising a management controller performing the utilizing the second interface to communicate with the device for retrieving data from the device.

### Claim 17 (depends on 14)

The method of claim 14, comprising a management controller permitting or denying a request to access the device via the second interface.

### Claim 18 (depends on 14)

The method of claim 14, wherein:
the first interface comprises a device interface,
the second interface comprises a management controller interface to the device, and
the management controller interface is to remain operative despite inoperability of the device.

### Claim 19 (depends on 14)

The method of claim 14, wherein the first interface is to operate in a manner consistent with a Peripheral Component Interface express (PCIe) protocol.

### Claim 20 (depends on 14)

The method of claim 14, wherein the second interface is to communicate with the device based on a Distributed Management Task Force (DMTF) protocol.
