# US 2020/0026785 A1 · Data Manifest as a Blockchain Service

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

- Number: US 2020/0026785 A1
- Document ID: US20200026785A1
- Status: Published application
- Kind: A1
- Application number: 16/038,923
- Filed: 2018-07-18
- Published: 2020-01-23
- Earliest claimed: 2018-07-18
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: Vishal Patangia; Mark Standring; Vasudevan Atteeri; Matthew Steed
- Web page: https://patentgrep.com/patent/US20200026785A1

## CPC

- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- H04L 63/123: {received data contents, e.g. message integrity}
- G06F 16/1834: {implemented based on peer-to-peer networks, e.g. gnutella (p2p communication protocols H04L67/104)}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2209/80: Wireless
- 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)

## Abstract

Methods and systems for providing data manifests as a service (DMAAS) are described herein. a first computing system, may generate a first data manifest comprising a first count parameter and a first hash parameter associated with a first data exchange transaction between the first computing system and a second computing system, store the first data manifest to a blockchain data store and transfer a data payload of the first data exchange transaction. The second computing system may analyze the data payload received via the transport mechanism, generate a second data manifest including a second count parameter and a second hash parameter and store the second data manifest to the blockchain data store. A DMAAS computing system facilitates access to the blockchain data store, identifies transmission errors, and triggers acceptance of data at the second computing system upon a successful data exchange transaction.

## Claims

### Claim 1

A method comprising:
generating, by a first computing system, a first data manifest comprising a first count parameter and a first hash parameter associated with a first data exchange transaction between the first computing system and a second computing system;
storing, by the first computing system, the first data manifest to a blockchain data store;
transferring, by the first computing system to the second computing system via a transport mechanism, a data payload of the first data exchange transaction;
analyzing, by the second computing system, the data payload received via the transport mechanism;
generating, by the second computing system, a second data manifest including a second count parameter and a second hash parameter;
storing, by the second computing system, the second data manifest to the blockchain data store;
analyzing, by a data manifest as a service (DMAAS) computing system, the first data manifest and the second data manifest retrieved from the blockchain; and
triggering, by the DMAAS computing system, the second computing system to release the data payload to a data consuming application when analysis by the DMAAS computing system indicates a successful transfer.

### Claim 2 (depends on 1)

The method of claim 1 comprising:
creating, by the first computing system, a first hash value using a hashing algorithm; and
creating, by the second computing system, a second hash value using the hashing algorithm.

### Claim 3 (depends on 1)

The method of claim 1 wherein:
storing, by the first computing system, the first data manifest to a blockchain data store comprises using a first application programming interface (API) function; and
storing, by the second computing system, the second data manifest to the blockchain data store comprises using a second API function.

### Claim 4 (depends on 1)

The method of claim 1, wherein analyzing, by the DMAAS computing system, the first data manifest and the second data manifest retrieved from the blockchain comprises:
retrieving, via one or more application programming interface (API) functions, the first manifest and the second data manifest from the blockchain;
comparing the first count parameter to the second count parameter; and
comparing the first hash parameter to the second hash parameter.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
storing, by the first computing system, a first data exchange contract to the blockchain data store, the first data exchange contract defining one or more characteristics of data exchange transactions between the first computing system and the second computing system, wherein the first data manifest is generated based on the data exchange contract.

### Claim 6 (depends on 5)

The method of claim 5, wherein storing, by the first computing system, the first data exchange contract to the blockchain data store comprises using a third API function.

### Claim 7 (depends on 5)

The method of claim 5, further comprising:
retrieving, by the DMAAS computing system, the first data contract from the blockchain;
determining, by the DMAAS computing system, a comparison of a data exchange timing parameter to a measured duration of the transfer of the data payload via the transport mechanism; and
storing, to the blockchain by the DMAAS computing system, an indication that the transfer of the data payload completed within a defined time limit when the comparison meets the data exchange timing parameter; and
storing, to the blockchain by the DMAAS computing system, an indication that the transfer of the data payload exceeded the defined time limit when the comparison exceeds the data exchange timing parameter.

### Claim 8 (depends on 7)

The method of claim 7, further comprising:
adjusing, by the DMAAS computing system, at least one of the data exchange timing parameter or a transport mechanism parameter as defined in a first version of the first data contract if the transfer of the data payload exceeded the defined time limit; and
storing, by the DMAAS computing system, a second version of the first data contract to the blockchain, the second version of the first data contract including an adjusted at least one of the data exchange timing parameter or the transport mechanism parameter.

### Claim 9

A system comprising:
a first computing system comprising a first processor and a first non-transitory memory device storing instructions that, when executed by the first processor, cause the first computing system to:
generate a first data manifest comprising a first count parameter and a first hash parameter associated with a first data exchange transaction between the first computing system and a second computing system;
store the first data manifest to a blockchain data store;
transfer, via a transport mechanism, a data payload of the first data exchange transaction to the second computing system;
a second computing system comprising a second processor and a second non-transitory memory device storing instructions that, when executed by the second processor, cause the second computing system to:
analyze the data payload received via the transport mechanism;
generate a second data manifest including a second count parameter and a second hash parameter;
store the second data manifest to the blockchain data store; and
a data manifest as a service (DMAAS) computing system comprising a third processor and a third non-transitory memory device storing instructions that, when executed by the second processor, cause the DMAAS computing system to:
analyze the first data manifest and the second data manifest retrieved from the blockchain; and
trigger the second computing system to release the data payload to a data consuming application when analysis by the DMAAS computing system indicates a successful transfer.

### Claim 10 (depends on 9)

The system of claim 9, wherein the instructions stored in the first non-transitory memory device that, when executed by the first processor, cause the first computing system to:
create a hash value using a hashing algorithm.

### Claim 11 (depends on 9)

The system of claim 9 wherein the instructions stored in the first non-transitory memory device that, when executed by the first processor, cause the first computing system to:
store the first data manifest to a blockchain data store using a first application programming interface (API) function; and
wherein the instructions stored in the first non-transitory memory device that, when executed by the first processor, cause the first computing system to:
store the second data manifest to the blockchain data store using a second API function.

### Claim 12 (depends on 9)

The system of claim 9, wherein the instructions stored in the third non-transitory memory device that, when executed by the third processor, cause the DMAAS computing system to:
retrieve, via one or more application programming interface (API) functions, the first manifest and the second data manifest from the blockchain;
compare the first count parameter to the second count parameter; and
compare the first hash parameter to the second hash parameter.

### Claim 13 (depends on 9)

The system of claim 9, wherein the instructions stored in the first non-transitory memory device that, when executed by the first processor, cause the first computing system to:
store a first data exchange contract to the blockchain data store, the first data exchange contract defining one or more characteristics of data exchange transactions between the first computing system and the second computing system, wherein the first data manifest is generated based on the data exchange contract.

### Claim 14 (depends on 13)

The system of claim 13, wherein storing, the first data exchange contract to the blockchain data store comprises using a third API function.

### Claim 15 (depends on 13)

The system of claim 13, wherein the instructions stored in the third non-transitory memory device that, when executed by the third processor, cause the DMAAS computing system to:
retrieve the first data contract from the blockchain;
determine a comparison of a data exchange timing parameter to a measured duration of the transfer of the data payload via the transport mechanism;
store to the blockchain data store, an indication that the transfer of the data payload completed within a defined time limit when the comparison meets the data exchange timing parameter; and
store, to the blockchain data store, an indication that the transfer of the data payload exceeded the defined time limit when the comparison exceeds the data exchange timing parameter.

### Claim 16 (depends on 15)

The system of claim 15, wherein the instructions stored in the third non-transitory memory device that, when executed by the third processor, cause the DMAAS computing system to:
adjust at least one of the data exchange timing parameter or a transport mechanism parameter as defined in a first version of the first data contract if the transfer of the data payload exceeded the defined time limit; and
store a second version of the first data contract to the blockchain data store, the second version of the first data contract including an adjusted at least one of the data exchange timing parameter or the transport mechanism parameter.

### Claim 17

A data manifest computing system (DMAAS) comprising:
a processor;
a non-transitory computing device storing instructions that, when executed by the processor, cause the DMAAS computing system to:
store, to a blockchain data store via a first application programming interface (API) function, a first data manifest received from a first computing system, the first data manifest corresponding to a data exchange transaction between the first computing system to a second computing system;
store, to the blockchain data store via a second API function, a second data manifest received from the second computing system;
compare, via a third API function, the first data manifest to the second data manifest; and
trigger, at the second computing system, import of a data payload received from the first computing system when comparison of the first data manifest to the second data manifest indicates a successful data transfer.
