# US 2024/0403326 A1 · Self-organization of data storage

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

- Number: US 2024/0403326 A1
- Document ID: US20240403326A1
- Status: Published application
- Kind: A1
- Application number: 18/205,646
- Filed: 2023-06-05
- Published: 2024-12-05
- Earliest claimed: 2023-06-05
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: Harinath Meedinti Bhaskara Reddy; Manu Kurian; Jayachandra Varma; Erica Perkins; Aeric Solow
- Web page: https://patentgrep.com/patent/US20240403326A1

## CPC

- G06F 16/285: {Clustering or classification}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Provided herein is a method of storing an incoming dataset in a data mesh. The method may include a plurality of steps. The steps may include associating a metadata tag with a classifying feature and a storage instruction in a (first) relational database. The steps may include scanning incoming datasets to identify datasets characterized by the classifying feature. The steps may include tagging an incoming dataset to generate a tagged dataset. The steps may include storing the tagged dataset in the data mesh, according to the storage instruction. The steps may include associating, in a second relational database, the metadata tag with the initial storage location. The steps may include modifying the storage instruction. The steps may include storing the incoming dataset an additional time in the data mesh, according to the modified storage instruction.

## Claims

### Claim 1

A method of storing incoming datasets in a data mesh, said method using a processor, said method comprising the steps of:
associating in a first relational database, a metadata tag with:
a classifying feature; and
a first storage instruction;
identifying an initial storage location for an incoming dataset within the data mesh, the initial storage location included in the first storage instruction, the identifying being tuned using a machine learning system, the machine learning system executing on the processor;
upon receipt of said incoming dataset by said data mesh, ascertaining whether said incoming dataset comprises said classifying feature;
when said incoming dataset comprises said classifying feature:
automatically obtaining said metadata tag and said first storage instruction from said first relational database;
automatically annotating said incoming dataset with said metadata tag, thereby generating a tagged dataset;
automatically storing said tagged dataset in the initial storage location, according to said first storage instruction; and
automatically associating, in a second relational database, said metadata tag with said initial storage location;
subsequently modifying said first storage instruction to generate a modified storage instruction, the modifying comprising using the machine learning system to tune the modified storage instruction; and
upon generation of said modified storage instruction, automatically further storing said incoming dataset in said data mesh, according to said modified storage instruction.

### Claim 2 (depends on 1)

The method of claim 1, wherein said modified storage instruction comprises an instruction to store said incoming dataset in said data mesh in a second storage location that differs from said initial storage location.

### Claim 3 (depends on 2)

The method of claim 2, further comprising the step of automatically associating, in said second relational database, said metadata tag with said second storage location.

### Claim 4 (depends on 2)

The method of claim 2, wherein said initial storage location and said second storage location have different requirements for data storage.

### Claim 5 (depends on 2)

The method of claim 2, wherein said modified storage instruction reflects constraints of said second storage location that do not exist for said initial storage location.

### Claim 6 (depends on 2)

The method of claim 2, wherein said modified storage instruction reflects said second storage location not being subject to constraints that exist for said initial storage location.

### Claim 7 (depends on 6)

The method of claim 6, wherein said constraints comprise a limited storage lifespan for at least some data fields in said initial storage location.

### Claim 8 (depends on 7)

The method of claim 7, wherein said modified storage instruction is automatically triggered by an indication of said limited storage lifespan.

### Claim 9 (depends on 2)

The method of claim 2, wherein said modified storage instruction comprises denying user accessibility of at least one data field in said second storage location, wherein said at least one data field is accessible in said initial storage location.

### Claim 10 (depends on 2)

The method of claim 2, wherein said modified storage instruction comprises making accessible at least one data field in said second storage location, wherein said at least one data field is not accessible in said initial storage location.

### Claim 11 (depends on 2)

The method of claim 2, wherein said step of further storing said incoming dataset utilizes a data link between said first initial storage location and said second storage location.

### Claim 12 (depends on 11)

The method of claim 11, said method further comprising the step of automatically gatekeeping data transfers along said data link.

### Claim 13 (depends on 1)

The method of claim 1, wherein the steps of
(i) subsequently modifying said storage instruction; and
(ii) automatically further storing said incoming dataset;
are repeated a plurality of times.

### Claim 14 (depends on 2)

The method of claim 2, wherein said incoming dataset originated in a first jurisdiction, wherein said initial storage location is housed in said first jurisdiction; and wherein receipt of said dataset in a (sub) network housed in second jurisdiction automatically triggers said step of subsequently modifying said storage instruction.

### Claim 15 (depends on 14)

The method of claim 14, wherein said second storage location is housed in said second jurisdiction.

### Claim 16 (depends on 1)

The method of claim 1, wherein said storage instruction is derived from a storage instruction associated with a prior dataset annotated with said metadata tag.

### Claim 17 (depends on 16)

The method of claim 16, wherein said storage instruction is produced by a tunable storage rule engine.

### Claim 18 (depends on 1)

The method of claim 1, wherein said metadata tag is in binary format.

### Claim 19 (depends on 1)

The method of claim 1, said method further comprising the step of identifying redundant copies of said dataset in said data mesh.

### Claim 20 (depends on 19)

The method of claim 19, said method further comprising the step of deleting said redundant copies of said dataset.
