# US 2026/0064548 A1 · Redundancy for multiple failure types in distributed data storage

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

- Number: US 2026/0064548 A1
- Document ID: US20260064548A1
- Status: Published application
- Kind: A1
- Application number: 19/308,516
- Filed: 2025-08-25
- Published: 2026-03-05
- Earliest claimed: 2024-08-30
- Assignees: Cubbit SRL
- Applicants: Cubbit SRL
- Inventors: Marco Moschettini; Alessio Paccoia; Lorenzo Posani
- Web page: https://patentgrep.com/patent/US20260064548A1

## CPC

- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 2201/80: Database-specific techniques
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present disclosure presents systems and methods for distributed data storage with enhanced redundancy to ensure high fault tolerance and data availability. A multi-layer scheme can be leveraged that combines local redundancy within datacenters and geographic redundancy across multiple locations. Data objects to be stored can be divided into shards and encrypted using error-correcting codes, such as Reed-Solomon codes, and distributed across a swarm of nodes. These nodes can be organized into nexuses and rings to attempt to optimize for factors such as redundancy and fault recovery. A centralized coordinator can oversee tasks such as shard placement, system health monitoring, and failure recovery. Such approaches can help to ensure seamless data restoration during device, node, or regional failures while providing a scalable and efficient framework for robust distributed storage.

## Claims

### Claim 1

A computer-implemented method, comprising:
receiving a data object to be stored;
segmenting the data object into two or more data shards;
storing metadata for the data object in a centralized database;
storing at least one of the data object or the two or more shards in a local storage location; and
distributing the data shards redundantly across storage resources in at least two geographically distinct storage locations.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein redundancy and distribution of the data object across the storage resources is provided in a single upstream operation and without delegation to one or more other components.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the local storage location is within a datacenter, and wherein the at least two geographically distinct storage locations include the datacenter and a remote datacenter.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, further comprising:
encrypting the data object using an encryption algorithm; and
applying Reed-Solomon error correction coding to create the two or more data shards.

### Claim 5 (depends on 2)

The computer-implemented method of claim 2, wherein the encryption algorithm ensures that no single storage node has access to complete or decrypted data objects.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein the data shards are to be distributed based in part on one or more configurable parameters, including at least one of:
a. a number of storage locations;
b. a number of storage locations that are accepted to be lost;
c. a number of nodes within a single location; or
d. a number of nodes that are accepted to be lost.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, further comprising:
allowing user configuration of one or more redundancy levels through a graphical user interface (GUI).

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, wherein the storage resources in the at least one geographically distinct storage location are selected based on at least one of:
a. uptime criteria for nodes;
b. geographic diversity to mitigate correlated failures;
c. node bandwidth capacity; or
d. historical reliability metrics for nodes.

### Claim 9 (depends on 1)

The computer-implemented method of claim 1, further comprising:
detecting a failure impacting a data object stored to a multiple storage resources in a first storage location; and
retrieving two or more data shards stored to two or more other storage resources in the first storage location to reconstruct the data object.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, further comprising:
detecting a failure impacting a data object stored to a first storage resource in a first storage location; and
retrieving two or more data shards stored to two or more storage resources in at least a second storage location to reconstruct the data object.

### Claim 11

A system, comprising:
at least one processor;
a memory device, the memory device storing instructions that, when executed by the at least one processor, cause the system to:
receive a data object to be stored;
segment the data object into two or more data shards;
store the data object to a primary storage resource in a first storage location; and
store the data shards redundantly across multiple storage resources within the first storage location and at least one second storage location.

### Claim 12 (depends on 11)

The system of claim 11, wherein the instructions when executed further cause the at least one processor to:
detect one or more failures impacting the data object in one of the storage resources in one or more of the first and second storage locations; and
reconstruct the data object using the data shards stored in other resources in one or more of the first and second storage locations.

### Claim 13 (depends on 11)

The system of claim 11, further comprising:
a coordinator module to dynamically select storage nodes based at least on operational criteria, the operational criteria including at least node availability, geographic diversity, or load balancing.

### Claim 14 (depends on 11)

The system of claim 11, wherein the instructions when executed further cause the at least one processor to:
encrypt the data object using an encryption algorithm; and
apply Reed-Solomon error correction coding to create the two or more data shards.

### Claim 15 (depends on 14)

The system of claim 14, wherein the encryption algorithm ensures that no single storage node has access to complete or decrypted data objects.

### Claim 16

A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to:
receive a data object to be stored;
segment the data object into two or more data shards;
store the data object to a primary storage resource in a first storage location; and
store the data shards redundantly across multiple storage resources within the first storage location and at least one second storage location.

### Claim 17 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the instructions when executed further cause the at least one processor to:
restore lost shards within a single storage location, when possible, to reduce bandwidth usage; and
perform inter-location recovery operations only when an entire storage location is unavailable.

### Claim 18 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the instructions when executed further cause the at least one processor to:
encrypt the data object using an encryption algorithm; and
apply Reed-Solomon error correction coding to create the two or more data shards.

### Claim 19 (depends on 18)

The non-transitory computer-readable medium of claim 18, wherein the encryption algorithm ensures that no single storage node has access to complete or decrypted data objects.

### Claim 20 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the instructions when executed further cause the at least one processor to:
allow user configuration of one or more redundancy levels through a graphical user interface (GUI).
