COMPUTING DEVICES AND METHODS FOR PROPAGATING UPDATES TO USER PROFILE DATA

• US 20200137058A1
• Filed: 10/25/2018
• Published: 04/30/2020
• Est. Priority Date: 10/25/2018
• Status: Active Grant

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Original Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Inventors: Allen, John, Hosny, Ahmed, Groarke, Peter J.
• Granted Patent: US 11,057,382 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/0478 applying multiple layers of encryption, e.g. nested tunnels or encrypting the content with a first key and then with at least a second key cryptographic mechanisms or cryptographic arrangements using a plurality of keys or algorithms H04L9/14
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources

Abstract

A data update computing device is provided. The data update computing device receives, from one of a user computing device and a first relying party computing device, a first access authorization message, wherein the first access authorization message identifies (i) a first relying party and (ii) a first user data element of the user to be shared with the first relying party. The data update computing device generates a first globally unique identifier (GUID), wherein the first GUID is uniquely associated in a first record in a GUID database table with the first user data element and the first relying party; receives an updated value of the first user data element of the user; stores the updated value of the first user data element in the first record, and flag the first record as updated in the GUID database table; and transmits the first GUID to the first relying party.

Claims

1. A data update computing device comprising at least one processor in communication with a database, the database configured to store a plurality of user data elements of a user, the data update computing device configured to:

receive, from one of a user computing device and a first relying party computing device, a first access authorization message, wherein the first access authorization message identifies (i) a first relying party and (ii) a first of the user data elements of the user to be shared with the first relying party;

create, in response to the first access authorization message, a first record in a GUID database table, wherein the first record associates a first globally unique identifier (GUID), the first user data element, and the first relying party;

receive, and store in the database, an updated value of the first user data element of the user;

flag the first record as updated in the GUID database table; and

transmit the first GUID to the first relying party.

2. The data update computing device of claim 1, further configured to transmit the first GUID in response to:

receiving, from the first relying party computing device, an update status request identifying the first relying party;

parsing the GUID database table to identify flagged records associated with the first relying party, including the first record; and

extracting the first GUID from the first record for transmission to the first relying party.

3. The data update computing device of claim 1, further configured to transmit the first GUID in response to:

retrieving, from the database, a watch list comprising a plurality of subscribed relying parties, each of the subscribed relying parties having authorization to receive updates associated with at least one of a plurality of users;

identifying the first relying party in the watch list;

parsing the GUID database table to identify flagged records associated with the first relying party, including the first record; and

extracting the first GUID from the first record for transmission to the first relying party.

4. The data update computing device of claim 1, further configured to, prior to transmitting the GUID to the first relying party:

encrypt the first GUID in a first encryption layer using a private key A associated with the data update computing device to generate an A-encrypted first GUID; and

encrypt the A-encrypted first GUID in a second encryption layer using a public key B associated with the first relying party to generate a double-encrypted first GUID, wherein transmitting the first GUID comprises transmitting the double-encrypted first GUID to the first relying party.

5. The data update computing device of claim 1, further configured to:

transmit the first GUID by transmitting an update list including the first GUID to the first relying party;

receive, in response to transmitting the update list, an update pull request from the first relying party, the update pull request including the first GUID; and

transmit, in response to the update pull request, the updated value to the first relying party.

6. The data update computing device of claim 1, further configured to transmit the updated value to the first relying party simultaneously with the transmission of the first GUID.

7. The data update computing device of claim 1, further configured to transmit the updated value to a representational state transfer (REST)-compliant endpoint maintained by the first relying party.

8. The data update computing device of claim 1, further configured to:

encrypt the updated value in a first encryption layer using a private key A associated with the data update computing device to generate an A-encrypted updated value;

encrypt the A-encrypted updated value in a second encryption layer using a public key B associated with the first relying party to generate a double-encrypted updated value; and

transmit the double-encrypted updated value to the first relying party.

9. The data update computing device of claim 1, wherein the first access authorization message further includes an authentication key, the data update computing device further configured to validate that the user authorizes the first relying party to access the first user data element based on the authentication key.

10. The data update computing device of claim 1, further configured to:

receive, from one of the user computing device and a second relying party computing device, a second access authorization message, wherein the second access authorization message identifies (i) a second relying party and (ii) the first user data element;

create, in response to the second access authorization message, a second record in the GUID database table, wherein the second record associates a second globally unique identifier (GUID), the first user data element, and the second relying party;

in response to receiving and storing the updated value of the first user data element, flag the second record as updated in the GUID database table; and

transmit the second GUID to the second relying party.

11. A computer-implemented method for propagating updates to user profile data, the user profile data comprising user data elements of a user, the method implemented using a data update computing device in communication with a database, the method comprising:

receiving, from one of a user computing device and a first relying party computing device, a first access authorization message, wherein the first access authorization message identifies (i) a first relying party and (ii) a first of the user data elements of the user to be shared with the first relying party;

creating, in response to the first access authorization message, a first record in a GUID database table in the database, wherein the first record associates a first globally unique identifier (GUID), the first user data element, and the first relying party;

receiving, and storing in the database, an updated value of the first user data element of the user;

flagging the first record as updated in the GUID database table; and

transmitting the first GUID to the first relying party.

12. The method of claim 11, wherein transmitting the first GUID further comprises:

receiving, from the first relying party computing device, an update status request identifying the first relying party;

parsing the GUID database table to identify flagged records associated with the first relying party, including the first record; and

extracting the first GUID from the first record for transmission to the first relying party.

13. The method of claim 11, wherein transmitting the first GUID further comprises:

retrieving, from the database, a watch list comprising a plurality of subscribed relying parties, each of the subscribed relying parties having authorization to receive updates associated with at least one of a plurality of users;

identifying the first relying party in the watch list;

parsing the GUID database table to identify flagged records associated with the first relying party, including the first record; and

extracting the first GUID from the first record for transmission to the first relying party.

14. The method of claim 11, further comprising, prior to transmitting the GUID to the first relying party:

encrypting the first GUID in a first encryption layer using a private key A associated with the data update computing device to generate an A-encrypted first GUID; and

encrypting the A-encrypted first GUID in a second encryption layer using a public key B associated with the first relying party to generate a double-encrypted first GUID, wherein transmitting the first GUID comprises transmitting the double-encrypted first GUID to the first relying party.

15. The method of claim 11, further comprising:

encrypting the updated value in a first encryption layer using a private key A associated with the data update computing device to generate an A-encrypted updated value; and

encrypting the A-encrypted updated value in a second encryption layer using a public key B associated with the first relying party to generate a double-encrypted updated value; and

transmitting the double-encrypted updated value to the first relying party.

16. A non-transitory computer readable medium that includes computer-executable instructions for propagating updates to user profile data comprising user data elements of a user, wherein when executed by at least one processor of a data update computing device, the computer-executable instructions cause the at least one processor to:

receive, from one of a user computing device and a first relying party computing device, a first access authorization message, wherein the first access authorization message identifies (i) a first relying party and (ii) a first of the user data elements of the user to be shared with the first relying party;

create, in response to the first access authorization message, a first record in a GUID database table, wherein the first record associates a first globally unique identifier (GUID), the first user data element, and the first relying party;

receive and store in the database an updated value of the first user data element of the user;

flag the first record as updated in the GUID database table; and

transmit the first GUID to the first relying party.

17. The non-transitory computer readable medium of claim 16, wherein the computer-executable instructions further cause the at least one processor to:

transmit the first GUID by transmitting an update list including the first GUID to the first relying party;

receive, in response to transmitting the update list, an update pull request from the first relying party, the update request including the first GUID; and

transmit, in response to the update pull request, the updated value to the first relying party.

18. The non-transitory computer readable medium of claim 16, wherein the computer-executable instructions further cause the at least one processor to transmit the updated value to the first relying party simultaneously with the transmission of the first GUID.

19. The non-transitory computer readable medium of claim 16, wherein the first access authorization message further includes an authentication key, wherein the computer-executable instructions further cause the at least one processor to validate that the user authorizes the first relying party to access the first user data element based on the authentication key.

20. The non-transitory computer readable medium of claim 16, wherein the computer-executable instructions further cause the at least one processor to:

receive, from one of the user computing device and a second relying party computing device, a second access authorization message, wherein the second access authorization message identifies (i) a second relying party and (ii) the first user data element;

create, in response to the second access authorization message, a second record in the GUID database table, wherein the second record associates a second globally unique identifier (GUID), the first user data element, and the second relying party;

in response to receiving and storing the updated value of the first user data element, flag the second record as updated in the GUID database table; and

transmit the second GUID to the second relying party.