# US 2019/0171616 A1 · Metadata access in a dispersed storage network

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

- Number: US 2019/0171616 A1
- Document ID: US20190171616A1
- Status: Published application
- Kind: A1
- Application number: 16/262,577
- Filed: 2019-01-30
- Published: 2019-06-06
- Earliest claimed: 2010-06-22
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Jason K. Resch; Greg Dhuse; Andrew Baptist; Wesley Leggette
- Web page: https://patentgrep.com/patent/US20190171616A1

## CPC

- G06F 11/1092: {Rebuilding, e.g. when physically replacing a failing disk}
- G06F 11/0727: {in a storage system, e.g. in a DASD or network based storage system (drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097)}
- G06F 11/141: {for bus or memory accesses}
- G06F 11/167: {Error detection by comparing the memory output}
- G06F 16/13: File access structures, e.g. distributed indices (arrangements of input from, or output to, record carriers G06F3/06)
- H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 9/3271: {using challenge-response}
- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- H04L 63/12: {Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32)}
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04W 12/041: Key generation or derivation
- H04W 12/0431: Key distribution or pre-distribution; Key agreement
- H04W 12/35: {Protecting application or service provisioning, e.g. securing SIM application provisioning}
- G06F 16/137: {Hash-based (content-based indexing of textual data G06F16/31)}
- G06F 21/31: User authentication
- G06F 21/6209: {to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself}
- G06F 2211/1028: Distributed, i.e. distributed RAID systems with parity
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 2209/043: of tables, e.g. lookup, substitution or mapping
- H04L 2209/30: Compression, e.g. Merkle-Damgard construction
- H04L 2209/34: Encoding or coding, e.g. Huffman coding or error correction
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- H04L 2209/80: Wireless
- H04W 12/10: Integrity
- 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)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A method begins by a processing module dispersed storage error encoding a data segment to produce a set of encoded data slices and dispersed storage error encoding metadata associated with the data segment to produce a set of encoded metadata slices. The method continues with the processing module creating a set of data slice names for the set of encoded data slices and creating a set of metadata slice names based on the set of data slice names. The method continues with the processing module sending the set of encoded data slices and the set of data slice names to a dispersed storage network (DSN) memory for storage therein. The method continues with the processing module sending the set of encoded metadata slices and the set of metadata slice names to the DSN memory for storage therein.

## Claims

### Claim 1

A method comprises:
dispersed storage error encoding a data segment to produce a set of encoded data slices;
dispersed storage error encoding metadata associated with the data segment to produce a set of encoded metadata slices;
creating a set of data slice names for the set of encoded data slices;
creating a set of metadata slice names based on the set of data slice names;
sending the set of encoded data slices and the set of data slice names to a dispersed storage network (DSN) memory, wherein the DSN memory stores an encoded data slice of the set of encoded data slices based on a corresponding one of the set of data slice names using a first level of memory allocation; and
sending the set of encoded metadata slices and the set of metadata slice names to the DSN memory, wherein the DSN memory stores an encoded metadata slice of the set of encoded metadata slices based on a corresponding one of the set of metadata slice names using a second level of memory allocation, and wherein the second level of memory allocation is smaller than the first level of memory allocation.

### Claim 2 (depends on 1)

The method of claim 1 further comprises:
sending the encoded data slice and the corresponding one of the set of data slice names to a first dispersed storage (DS) unit of the DSN memory, wherein memory space of the first DS unit is partitioned in accordance with the first level of memory allocation.

### Claim 3 (depends on 2)

The method of claim 2 further comprises:
sending the encoded metadata slice and the corresponding one of the set of metadata slice names to a second DS unit of the DSN memory, wherein memory space of the second DS unit is partitioned in accordance with the second level of memory allocation.

### Claim 4 (depends on 1)

The method of claim 1 further comprises:
sending the encoded data slice and the corresponding one of the set of data slice names to a dispersed storage (DS) unit of the DSN memory, wherein a first portion of memory space of the DS unit is partitioned in accordance with the first level of memory allocation.

### Claim 5 (depends on 4)

The method of claim 4 further comprises:
sending the encoded metadata slice and the corresponding one of the set of metadata slice names to the DS unit, wherein a second portion of the memory space of the DS unit is partitioned in accordance with the second level of memory allocation.

### Claim 6 (depends on 1)

The method of claim 1, wherein the creating the set of data slice names is based on at least one of:
a data identifier (ID) associated with the data segment;
a vault ID lookup;
a directory lookup;
a source name; or
a vault source name.

### Claim 7 (depends on 1)

The method of claim 1, wherein the creating the set of data slice names is based on at least one of:
the set of encoded data slices;
a hash of the data segment; or
an object number associated with a data ID.

### Claim 8 (depends on 1)

The method of claim 1, wherein the creating the set of metadata slice names comprises at least one of:
toggling a data/metadata flag of a data slice name of the set of data slice names to produce a corresponding metadata slice name of the set of metadata slice names;
performing an exclusive OR (XOR) logical function on the data slice name with a naming mask to produce the corresponding metadata slice name;
adding a constant value to the data slice name to produce the corresponding metadata slice name; or
subtracting the constant value from the data slice name to produce the corresponding metadata slice name.

### Claim 9

A method comprises:
determining a set of data slice names corresponding to a data segment previously stored in a dispersed storage network (DSN) memory as a set of encoded data slices;
determining a set of metadata slice names based on the set of data slice names, wherein the metadata slice names correspond to metadata previously stored in the DSN memory as a set of encoded metadata slices;
retrieving at least a decode threshold number of encoded data slices of the set of encoded data slices from the DSN memory to produce received encoded data slices utilizing the set of data slice names, wherein the DSN memory retrieves an encoded data slice of the set of encoded data slices based on a corresponding one of the set of data slice names using a first level of memory allocation;
retrieving at least a decode threshold number of encoded metadata slices of the set of encoded metadata slices from the DSN memory to produce received encoded metadata slices utilizing the set of metadata slice names, wherein the DSN memory retrieves an encoded metadata slice of the set of encoded metadata slices based on a corresponding one of the set of metadata slice names using a second level of memory allocation, and wherein the second level of memory allocation is smaller than the first level of memory allocation;
dispersed storage error decoding the received encoded data slices to reproduce the data segment; and
dispersed storage error decoding the received encoded metadata slices to reproduce the metadata.

### Claim 10 (depends on 9)

The method of claim 9 further comprises:
transforming the data segment utilizing a metadata function to produce transformed data in accordance with the metadata.

### Claim 11 (depends on 10)

The method of claim 10 further comprises:
sending the transformed data to a requesting entity.

### Claim 12 (depends on 9)

The method of claim 9, wherein the dispersed storage error decoding the received encoded data slices comprises:
dispersed storage error decoding the received encoded data slices based on the metadata to reproduce the data segment.

### Claim 13

A computer comprises:
an interface;
a non-transitory memory that stores operational instructions; and
at least one processing device that executes the operational instructions, which cause the at least one processing device to:
dispersed storage error encode a data segment to produce a set of encoded data slices;
dispersed storage error encode metadata associated with the data segment to produce a set of encoded metadata slices;
create a set of data slice names for the set of encoded data slices;
create a set of metadata slice names based on the set of data slice names;
send, via the interface, the set of encoded data slices and the set of data slice names to a dispersed storage network (DSN) memory, wherein the DSN memory stores an encoded data slice of the set of encoded data slices based on a corresponding one of the set of data slice names using a first level of memory allocation; and
send, via the interface, the set of encoded metadata slices and the set of metadata slice names to the DSN memory, wherein the DSN memory stores an encoded metadata slice of the set of encoded metadata slices based on a corresponding one of the set of metadata slice names using a second level of memory allocation, and wherein the second level of memory allocation is smaller than the first level of memory allocation.

### Claim 14 (depends on 13)

The computer of claim 13, wherein executing the operational instructions further cause the at least one processing device to:
send, via the interface, the encoded data slice and the corresponding one of the set of data slice names to a first dispersed storage (DS) unit of the DSN memory, wherein memory space of the first DS unit is partitioned in accordance with the first level of memory allocation.

### Claim 15 (depends on 14)

The computer of claim 14, wherein executing the operational instructions further cause the at least one processing device to:
send, via the interface, the encoded metadata slice and the corresponding one of the set of metadata slice names to a second DS unit of the DSN memory, wherein memory space of the second DS unit is partitioned in accordance with the second level of memory allocation.

### Claim 16 (depends on 13)

The computer of claim 13, wherein executing the operational instructions further cause the at least one processing device to:
send, via the interface, the encoded data slice and the corresponding one of the set of data slice names to a dispersed storage (DS) unit of the DSN memory, wherein a first portion of memory space of the DS unit is partitioned in accordance with the first level of memory allocation.

### Claim 17 (depends on 16)

The computer of claim 16, wherein executing the operational instructions further cause the at least one processing device to:
send, via the interface, the encoded metadata slice and the corresponding one of the set of metadata slice names to the DS unit, wherein a second portion of the memory space of the DS unit is partitioned in accordance with the second level of memory allocation.

### Claim 18 (depends on 13)

The computer of claim 13, wherein the at least one processing device functions to create the set of data slice names based on at least one of:
a data identifier (ID) associated with the data segment;
a vault ID lookup;
a directory lookup;
a source name; or
a vault source name.

### Claim 19 (depends on 13)

The computer of claim 13, wherein the at least one processing device functions to create the set of data slice names based on at least one of:
the set of encoded data slices;
a hash of the data segment; or
an object number associated with a data ID.

### Claim 20 (depends on 13)

The computer of claim 13, wherein the at least one processing device functions to create the set of metadata slice names by at least one of:
toggling a data/metadata flag of a data slice name of the set of data slice names to produce a corresponding metadata slice name of the set of metadata slice names;
performing an exclusive OR (XOR) logical function on the data slice name with a naming mask to produce the corresponding metadata slice name;
adding a constant value to the data slice name to produce the corresponding metadata slice name; or
subtracting the constant value from the data slice name to produce the corresponding metadata slice name.
