# US 2026/0310553 A1 · Methods and systems for offloading memory data reconstruction

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

- Number: US 2026/0310553 A1
- Document ID: US20260310553A1
- Status: Published application
- Kind: A1
- Application number: 19/173,655
- Filed: 2025-04-08
- Published: 2026-10-08
- Earliest claimed: 2025-04-08
- Assignees: SK Hynix NAND Product Solutions Corp. (dba Solidigm)
- Applicants: SK Hynix NAND Product Solutions Corp. (dba Solidigm)
- Inventors: George KALWITZ
- Web page: https://patentgrep.com/patent/US20260310553A1

## CPC

- G06F 11/1088: {Reconstruction on already foreseen single or plurality of spare disks}
- G06F 11/108: {Parity data distribution in semiconductor storages, e.g. in SSD}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

This application is directed to managing data construction in a memory system having a plurality of memory drives that further include a set of member drives and a target drive. The memory system obtains a structured data command and extracts the identifications of the member drives from the structured data command. Based on the identifications of the member drives, the memory system generates at least one data request sent to each member drive. In response to the at least one data request to each member drive, the memory system obtains a respective data chunk extracted from the respective member drive, generates a target data chunk based on respective data chunks extracted from the set of member drives, and stores the target data chunk on a target drive. The structured data command may be obtained and processed by the target drive to generate the data requests and the target data chunk.

## Claims

### Claim 1

A method for memory data reconstruction, comprising:
at a memory system including a plurality of memory drives, wherein the plurality of memory drives further include a set of member drives and a target drive distinct from each of the set of member drives:
obtaining a structured data command including identifications of the set of member drives;
extracting the identifications of the set of member drives from the structured data command;
based on the identifications of the set of member drives, generating at least one data request sent to each of the set of member drives ;
in response to the at least one data request sent to each member drive, obtaining a respective data chunk extracted from the respective member drive; and
generating a target data chunk based on respective data chunks extracted from the set of member drives; and
storing the target data chunk on the target drive.

### Claim 2 (depends on 1)

The method of claim 1, wherein the structured data command further includes an identification of the target drive and a target chunk address on the target drive, and the method further comprises:
identifying the target drive based on the identification of the target drive, wherein the target data chunk is stored on the target drive based on the target chunk address.

### Claim 3 (depends on 1)

The method of claim 1, wherein:
the structured data command further includes a set of member chunk addresses on the set of member drives; and
for each of the set of member drives, the at least one data request includes a respective member chunk address of the respective member drive, and the respective data chunk is extracted from the respective member drive based at the respective member chunk address.

### Claim 4 (depends on 1)

The method of claim 1, wherein the target data chunk corresponds to a parity data chunk, and the respective data chunks extracted from the set of member drives correspond to a plurality of user data chunks, the plurality of user data chunks and the parity data chunk forming a data stripe.

### Claim 5 (depends on 4)

The method of claim 4, wherein the memory system is coupled to a host device, further comprising, at the host device:
generating data write commands to store the respective data chunks in the set of member drives;
generating the structured data command requesting generation of the parity data chunk locally at the target drive; and
sending the data write commands and the structured data command to the memory system.

### Claim 6 (depends on 1)

The method of claim 1, wherein the memory system is coupled to a host device, further comprising, at the host device:
determining that data stored on a first drive need to be reconstructed, wherein the data stored on the first drive includes the target data chunk and an alternative data chunk; and
generating the structured data command for reconstructing the target data chunk and an alternative data command for reconstructing the alternative data chunk.

### Claim 7 (depends on 6)

The method of claim 6, further comprising, at the target drive:
obtaining the alternative data command including identifications of a set of alternative drives; generating an alternative data chunk based on respective data chunks extracted from the set of alternative drives; and
storing the alternative data chunk on the target drive.

### Claim 8 (depends on 6)

The method of claim 6, further comprising, at a second drive distinct from the target drive:
obtaining the alternative data command including identifications of a set of alternative drives;
generating an alternative data chunk based on respective data chunks extracted from the set of alternative drives; and
storing the alternative data chunk on the second drive.

### Claim 9 (depends on 1)

The method of claim 1, wherein the structured data command includes one or more of: a data length of the target data chunk, a reconstruction algorithm indicator for generating the target data chunk, and a number of member drives associated with the target data chunk.

### Claim 10 (depends on 1)

The method of claim 1, further comprising, at the target drive:
after storing the target data chunk, sending a confirmation message to a host device to which the memory system is coupled, the confirmation message indicating a completion status of the target drive.

### Claim 11 (depends on 1)

The method of claim 1, wherein the memory system is coupled to a host device, and the structured data command includes identifications of a set of alternative drives, the method further comprising:
at the host device:
determining that data stored on a first drive need to be reconstructed, the data stored on the first drive including the target data chunk and an alternative data chunk; and
generating the structured data command for reconstructing the target data chunk and an alternative data command for the alternative data chunk; and
at the target drive or a second drive distinct from the target drive:
generating an alternative data chunk based on respective data chunks extracted from the set of alternative drives; and
storing the alternative data chunk on the target drive or the second drive.

### Claim 12

A memory system, comprising:
a plurality of memory drives including set of member drives and a target drive distinct from each of the set of member drives;
one or more processors; and
memory having instructions stored thereon, which when executed by the one or more processors cause the processors to perform:
obtaining a structured data command including identifications of the set of member drives;
extracting the identifications of the set of member drives from the structured data command;
based on the identifications of the set of member drives, generating at least one data request sent to each of the set of member drives ;
in response to the at least one data request sent to each member drive, obtaining a respective data chunk extracted from the respective member drive; and
generating a target data chunk based on respective data chunks extracted from the set of member drives; and
storing the target data chunk on the target drive.

### Claim 13 (depends on 12)

The memory system of claim 12, wherein the memory system is coupled to a host device and configured to communicate with the host device via a PCIe bus, and the structured data command is received from the host device via the PCIe bus in compliance with a Non-Volatile Memory Express (NVMe) or NVMe over fabrics (NVMeOF) protocol.

### Claim 14 (depends on 12)

The memory system of claim 12, wherein each of the plurality of memory drives has an interface selected from Small Computer System Interface (SCSI), a Serial Storage Architecture (SSA) interface, a Fibre Channel interface, an Internet SCSI (iSCSI) interface, and a Serial-Attached SCSI (SAS) interface.

### Claim 15 (depends on 12)

The memory system of claim 12, wherein respective data chunks of the set of member drives and the target data chunk of the target drive are arranged according to a redundant array of independent disks (RAID) scheme selected from RAID1, RAID3, RAID5, RAID6, RAID-N, RAID10, RAID50, and RAID60, and each memory drive includes a respective solid-state drive (SSD), and the respective SSD includes a plurality of NAND flash memory cells.

### Claim 16

A non-transitory computer-readable storage medium, having instructions stored thereon, which when executed by one or more processors cause the processors to perform:
at a memory system including a plurality of memory drives, wherein the plurality of memory drives further include a set of member drives and a target drive distinct from each of the set of member drives:
obtaining a structured data command including identifications of the set of member drives;
extracting the identifications of the set of member drives from the structured data command;
based on the identifications of the set of member drives, generating at least one data request sent to each of the set of member drives ;
in response to the at least one data request sent to each member drive, obtaining a respective data chunk extracted from the respective member drive; and
generating a target data chunk based on respective data chunks extracted from the set of member drives; and
storing the target data chunk on the target drive.

### Claim 17 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, further comprising instructions for, at the target drive:
determining that an error has occurred during receiving the respective data chunks extracted from the set of member drives or generating the target data chunk;
generating an error alert message based on the error; and
sending the error alert message to a host device that issues the structured data command;
wherein the host device is configured to fetch the respective data chunks from the set of member drives, generate the target data chunk based on the respective data chunks, and send a write request to the target drive to store the target data chunk.

### Claim 18 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, wherein the target data chunk is selected from Reed-Solomon error codes, Hamming error codes, Low-density parity-check (LDPC) codes, and XOR-based error codes.

### Claim 19 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, wherein the respective data chunk of one of the set of member drives is selected from Reed-Solomon error codes, Hamming error codes, LDPC codes, and XOR-based error codes, and the target data chunk includes a subset of user data applied to generate the respective data chunk of the one of the set of member drives.

### Claim 20 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, wherein the plurality of memory drives are communicatively coupled to one another via a Peripheral Component Interconnect Express (PCIe) bus, and the target drive receives the respective data chunk extracted from each respective member drive via the PCIe bus without involving a host device.
