REAL-TIME PROCESSING DISTRIBUTED LEDGER SYSTEM

• US 20190034922A1
• Filed: 07/25/2017
• Published: 01/31/2019
• Est. Priority Date: 07/25/2017
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Castinado, Joseph Benjamin, Kendall, Charles Russell, McClellan, Martha Sain, Proud, Lee Ann, Sachedina, Ayeesha, Tackett, JR., Calvin William
• Granted Patent: US 10,643,202 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/1815 Journaling file systems
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06Q 20/065 using e-cash
• CPC Class Codes: G06Q 20/223 based on the use of peer-to-peer networks
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/389 Keeping log of transactions for guaranteeing non-repudiation of a transaction
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

A system, computer program product, and method for executing real-time processing of resource transfers using distributed ledger technology is provided. In particular, the system utilizes a private or semi-private blockchain to create a distributed ledger which comprises a record of all resource transfers between a number of entities. The real-time processing system addresses a number of computer technology-centric challenges associated with executing resource transfers. In particular, executing resource transfers on a real-time basis allows the nodes of the blockchain to more evenly distribute computing workload over time when compared to more traditional resource transfer systems that use batch processing to execute transfers.

Claims

1. A system for processing a real-time resource transfer using distributed ledger technology, the system comprising:

a first entity node comprising;

a processor;

a communication interface; and

a memory having a blockchain application stored therein, wherein the blockchain application comprises a blockchain comprising a plurality of data records, wherein the blockchain application, when executed by the processor, causes the processor to;

receive a resource transfer request from a user device;

generate a pending data record on the blockchain;

validate the pending data record for a first entity;

detect that the pending data record has been validated by a second entity;

convert the pending data record to a permanent data record; and

append the permanent data record to the blockchain.

2. The system according to claim 1, wherein the blockchain application further comprises smart code portions configured to:

read the data within the permanent data record;

detect that data within the permanent data record references an amount of resources over a threshold; and

selectively authorize a third party computing system to access the permanent data record.

3. The system according to claim 1, wherein validating the pending data record for the first entity comprises verifying that a threshold number of first entity nodes have validated the pending data record.

4. The system according to claim 1, wherein detecting that the pending data record has been validated by the second entity comprises verifying that a threshold number of second entity nodes have validated the pending data record.

5. The system according to claim 1, wherein the pending data record comprises identifier data, the identifier data comprising a unique identifier associated with a user and a unique identifier associated with a recipient.

6. The system according to claim 5, wherein the unique identifier associated with a user is associated with an account of the user with the first entity, wherein the unique identifier associated with the recipient is associated with an account of the recipient with the second entity.

7. A computer program product for processing a real-time resource transfer using distributed ledger technology, the computer program product comprising at least one non-transitory computer readable medium having computer-readable program code portions embodied therein, the computer-readable program code portions comprising:

an executable portion for receiving a resource transfer request from a user device;

an executable portion for generating a pending data record on the blockchain;

an executable portion for validating the pending data record for a first entity;

an executable portion for detecting that the pending data record has been validated by a second entity;

an executable portion for converting the pending data record to a permanent data record; and

an executable portion for appending the permanent data record to the blockchain.

8. The computer program product according to claim 7, the computer-readable program code portions further comprising:

an executable portion for reading the data within the permanent data record;

an executable portion for detecting that data within the permanent data record references an amount of resources over a threshold; and

an executable portion for selectively authorizing a third party computing system to access the permanent data record.

9. The computer program product according to claim 7, wherein validating the pending data record for the first entity comprises verifying that a threshold number of first entity nodes have validated the pending data record.

10. The computer program product according to claim 7, wherein detecting that the pending data record has been validated by the second entity comprises verifying that a threshold number of second entity nodes have validated the pending data record.

11. The computer program product according to claim 7, wherein the pending data record comprises identifier data, the identifier data comprising a unique identifier associated with a user and a unique identifier associated with a recipient.

12. The computer program product according to claim 11, wherein the unique identifier associated with a user is associated with an account of the user with the first entity, wherein the unique identifier associated with the recipient is associated with an account of the recipient with the second entity.

13. A computer-implemented method for processing a real-time resource transfer using distributed ledger technology, said method comprising:

receiving a resource transfer request from a user device;

generating a pending data record on the blockchain;

validating the pending data record for a first entity;

detecting that the pending data record has been validated by a second entity;

converting the pending data record to a permanent data record; and

appending the permanent data record to the blockchain.

14. The computer-implemented method according to claim 13, the method further comprising:

reading the data within the permanent data record;

detecting that data within the permanent data record references an amount of resources over a threshold; and

selectively authorizing a third party computing system to access the permanent data record.

15. The computer-implemented method according to claim 13, wherein validating the pending data record for the first entity comprises verifying that a threshold number of first entity nodes have validated the pending data record.

16. The computer-implemented method according to claim 13, wherein detecting that the pending data record has been validated by the second entity comprises verifying that a threshold number of second entity nodes have validated the pending data record.

17. The computer-implemented method according to claim 13, wherein the pending data record comprises identifier data, the identifier data comprising a unique identifier associated with a user and a unique identifier associated with a recipient.

18. The computer-implemented method according to claim 17, wherein the unique identifier associated with a user is associated with an account of the user with the first entity, wherein the unique identifier associated with the recipient is associated with an account of the recipient with the second entity.