Data sharing via distributed ledgers

Patent metadata

Field	Value
Publication number	US-11200334-B2
Application number	US-201916591132-A
Country	US
Kind code	B2
Filing date	Oct 2, 2019
Priority date	Jun 4, 2019
Publication date	Dec 14, 2021
Grant date	Dec 14, 2021

Abstract

Systems as described herein may include authorizing the sharing of data and sharing data between a variety of systems. A request to share data may be provided to a first system. The system may create sharing session data on a distributed ledger accessible by a number of systems. Sharing session data may be stored using a transaction stored on a distributed ledger. A second system may obtain the sharing session account and verify the sharing session. On verification of the sharing session, a variety of data may be shared between the systems identified in the sharing session data. The sharing session data may be established between two or more systems. The distributed ledger may be maintained by the systems themselves and/or a distributed network system. In a variety of embodiments, encrypted data may be stored and/or obtained using the distributed ledger.

First claim

What is claimed is:

1. A method, comprising:
obtaining, by a server system and from a requesting system, request data comprising a user account identifier associated with an account maintained by the server system and an indication of desired data;
identifying, by the server system, an alias token associated with the user account identifier;
determining, by the server system, at least one related server system based on a distributed ledger,
wherein:
the distributed ledger comprises a mapping of each of the at least one related server system to the server system; and
the distributed ledger indicates a start date and an end date for each mapping of the server system to each of the at least one related server system;

transmitting, by the server system and to each of the at least one related server system, a message comprising the alias token identified in the distributed ledger and the indication of desired data;
obtaining, by the server system and from each of the at least one related server system, at least one response component comprising data corresponding to the indication of desired data and associated with the alias token;
generating, by the server system, account data based on the indication of desired data;
generating, by the server system, response data based on the indication of desired data, wherein the response data comprises the at least one response component and the account data; and
transmitting, by the server system, the response data.

2. The method of claim 1 , further comprising:
obtaining, by the server system and from a third-party server system, a request for account information, wherein the request for account information comprises a second alias token;
generating, by the server system, a second distributed ledger comprising a mapping of the third-party server system to the server system; and
transmitting, by the server system and to the third-party server system, the account information.

3. The method of claim 1 , further comprising:
transmitting, by the server system and to a computing device, a verification request comprising an identification of a third-party server system;
obtaining, by the server system and from the computing device, response data; and
when the response data indicates that account information should be shared, transmitting the account information.

4. The method of claim 1 , wherein the distributed ledger comprises a start date and an end date for each mapping of the server system to each of the at least one related server system.

5. The method of claim 1 , wherein:
the distributed ledger comprises permission data associated with the user account identifier; and
generating the account data is further based on the permission data.

6. The method of claim 1 , further comprising transmitting the response data to a computing device, wherein the response data is usable to generate output data comprising the account data and the at least one response component.

7. The method of claim 1 , wherein the distributed ledger is stored using the server system.

8. The method of claim 1 , wherein the distributed ledger is stored using at least one of the at least one related server system.

9. The method of claim 1 , wherein the distributed ledger is stored using a distributed network system.

10. The method of claim 1 , further comprising:
obtaining, by the server system, a sharing request comprising an account identifier, a start date, an end date, a set of permissions, and an indication of a related server system;
generating, by the server system, the alias token;
generating, by the server system, a transaction block comprising the account identifier, the start date, the end date, the set of permissions, the indication of the related server system, and the alias token; and
recording, by the server system, the transaction block on the distributed ledger.

11. A computing device, comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the computing device to:
obtain, from a third-party server system, a request for account information, wherein the request for account information comprises an alias token;
transmit, to a computing device, a verification request comprising an identification of the third-party server system;
obtain response data comprising an account identifier; and
when the response data indicates that account information should be shared:
generate a distributed ledger;
generate a transaction block comprising a mapping of the third-party server system to the system, the alias token, and the account identifier;

record the transaction block on the distributed ledger, wherein the distributed ledger indicates a start date and an end date for the mapping of the third-party server system to the system; and
transmit, to the third-party server system, the account information.

12. The computing device of claim 11 , wherein:
the response data further comprises the start date and an end date; and
the transaction block further comprises the start date and the end date.

13. The computing device of claim 11 , wherein:
the response data further comprises permission data associated with the account information; and
the transaction block further comprises the permission data.

14. The computing device of claim 11 wherein the distributed ledger is stored using the system.

15. The computing device of claim 11 , wherein the distributed ledger is stored using the third-party server system.

16. The computing device of claim 11 , wherein the distributed ledger is stored using a distributed network system.

17. A non-transitory machine-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform steps comprising:
obtaining request data comprising an account identifier and an indication of desired data;
identifying an alias token associated with the account identifier;
determining a transaction block of a distributed ledger, wherein the transaction block indicates a mapping to a related server system that is based on the alias token, and
wherein the transaction block comprises a start date and an end date for the mapping;
determining a current date when the request data was obtained; and
when the current date is after the start date and before the end date:
transmitting, to the related server system, a message comprising the alias token and the indication of desired data; and
obtaining, from the related server system, a response component comprising data corresponding to the indication of desired data and associated with the alias token; and

generating response data based on the request data, wherein the response data comprises the response component when the current date is after the start date and before the end date.

18. The non-transitory machine-readable medium of claim 17 , wherein the instructions further cause the one or more processors to transmit the response data to a computing device, wherein the response data is usable to generate output data comprising the response data.

19. The non-transitory machine-readable medium of claim 17 , wherein the instructions further cause the one or more processors to determine the transaction block by querying a distributed ledger to identify the transaction block based on the related server system.

20. The non-transitory machine-readable medium of claim 17 , wherein:
the transaction block further comprises permission data; and
the instructions furt

Assignees

• Capital One Services Llc

Inventors

• Kuzin Taras
• Tang Qiaochu
• Frensch Steve
• Santoro John

Classifications

• H04L9/50 Primary

  using hash chains, e.g. blockchains or hash trees · CPC title

• G06F21/645

  using a third party · CPC title

• H04L9/3213

  using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807) · CPC title

• G06F21/6218 Primary

  to a system of files or objects, e.g. local or distributed file system or database · CPC title

• H04L63/102

  Entity profiles · CPC title