Systems and methods for enforcing centralized privacy controls in de-centralized systems

• US 10,572,684 B2
• Filed: 04/26/2018
• Issued: 02/25/2020
• Est. Priority Date: 11/01/2013
• Status: Active Grant

• Current Assignee: Anonos IP LLC
• Original Assignee: Anonos, Inc.
• Inventors: LaFever, Malcolm Gary, Myerson, Ted N., Mason, Steven
• Primary Examiner(s): Jeudy, Josnel
• Application Number:
  US15/963,609
• Publication Number:
  US 20180307859A1
• Time in Patent Office: 670 Days
• CPC Class Codes: G06F 21/6254 by anonymising data, e.g. decorrelating personal data from the owner's identification
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: H04L 2209/42 Anonymization, e.g. involving pseudonyms
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00
• CPC Class Codes: H04L 63/0414 during transmission, i.e. party's identity is protected against eavesdropping, e.g. by using temporary identifiers, but is known to the other party or parties involved in the communication
• CPC Class Codes: H04L 63/068 using time-dependent keys, e.g. periodically changing keys cryptographic mechanisms or cryptographic arrangements for controlling usage of secret information H04L9/088
• 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/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 9/16 the keys or algorithms being changed during operation
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/3297 involving time stamps, e.g. generation of time stamps
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

Abstract

Systems, computer-readable media, and methods for improving both data privacy/anonymity and data value, wherein data related to a data subject can be used and stored, e.g., in a distributed ledger data structure, such as a blockchain, while minimizing re-identification risk by unauthorized parties and enabling data, including quasi-identifiers, related to the data subject to be disclosed to any authorized party by granting access only to the data relevant to that authorized party'"'"'s purpose, time period, place and/or other criterion via the obfuscation of specific data values, e.g., pursuant to the European Union'"'"'s General Data Protection Regulation (GDPR) or other similar regulatory schemes. The techniques described herein maintain this level of privacy/anonymity while still satisfying the immutability, auditability, and verification mandated by blockchain and other distributed ledger technologies (DLTs) for the decentralized storage of transactional data. Such systems, media, and methods may be implemented on both classical and quantum computing devices.

Claims

1. A system, comprising:

a communication interface for sending data over a network;

a memory having, stored therein, computer program code and one or more distributed ledgers capable of recording data records; and

one or more processing units operatively coupled to the memory and configured to execute instructions in the computer program code that cause the one or more processing units to;

obtain data from a first user pertaining to a first data subject;

generate a first dynamically-changing, temporally unique identifier (DDID) for the first data subject, wherein the first DDID is configured to replace a first value related to the first data subject;

store the first DDID in a first element of a first one of the one or more distributed ledgers;

receive, over the network, a first request from a first requesting party for the first value related to the first data subject;

send the first DDID to the first requesting party over the network in response to the first request when the first requesting party is not authorized to receive the first value; and

send the first value related to the first data subject to the first requesting party over the network in response to the first request when the first requesting party is authorized to receive the first value.

2. The system of claim 1, wherein the network is decentralized, wherein the network comprises a plurality of nodes, and wherein each node in the network stores a copy of the first one of the one or more distributed ledgers.

3. The system of claim 2, wherein the first one of the one or more distributed ledgers comprises a blockchain, and wherein the first element comprises a first block.

4. The system of claim 1, wherein the one or more processing units are further configured to execute instructions in the computer program code that further cause the one or more processing units to:

obtain a request from a first user for provision of a privacy policy; and

determine a first privacy policy based, at least in part, on the request,

wherein the first DDID is further configured to comply with the determined first privacy policy.

5. The system of claim 1, wherein the first DDID points to a storage location containing the first value related to the first data subject.

6. The system of claim 5, wherein the one or more processing units are further configured to execute instructions in the computer program code that further cause the one or more processing units to:

obtain a request from the first user to modify the first value related to the data subject to be a first modified value; and

store the first modified value in the storage location containing the first value related to the data subject.

7. The system of claim 1, wherein the first data subject comprises a first executable term of a smart contract.

8. A computer-implemented method comprising:

obtaining data from a first user pertaining to a first data subject;

generating a first dynamically-changing, temporally unique identifier (DDID) for the first data subject, wherein the first DDID is configured to replace a first value related to the first data subject;

storing the first DDID in a first element of a first one of one or more distributed ledgers;

receiving, over a network, a first request from a first requesting party for the first value related to the first data subject;

sending the first DDID to the first requesting party over the network in response to the first request when the first requesting party is not authorized to receive the first value; and

sending the first value related to the first data subject to the first requesting party over the network in response to the first request when the first requesting party is authorized to receive the first value.

9. The computer-implemented method of claim 8, wherein the network is decentralized, wherein the network comprises a plurality of nodes, wherein each node in the network stores a copy of the first one of the one or more distributed ledgers, wherein the first one of the one or more distributed ledgers comprises a blockchain, and wherein the first element comprises a first block.

10. The computer-implemented method of claim 8, further comprising:

obtaining a request from a first user for provision of a privacy policy; and

determining a first privacy policy based, at least in part, on the request,

wherein the first DDID is further configured to comply with the determined first privacy policy.

11. The computer-implemented method of claim 8, wherein the first DDID points to a storage location containing the first value related to the first data subject.

12. The computer-implemented method of claim 11, further comprising:

obtaining a request from the first user to modify the first value related to the data subject to be a first modified value; and

storing the first modified value in the storage location containing the first value related to the data subject.

13. The computer-implemented method of claim 8, wherein the first data subject comprises a first executable term of a smart contract.

14. A non-transitory program storage device, readable by a programmable control device, comprising instructions stored thereon that, when executed, cause the programmable control device to:

obtain data from a first user pertaining to a first data subject;

generate a first dynamically-changing, temporally unique identifier (DDID) for the first data subject, wherein the first DDID is configured to replace a first value related to the first data subject;

store the first DDID in a first element of a first one of one or more distributed ledgers;

receive, over a network, a first request from a first requesting party for the first value related to the first data subject;

send the first DDID to the first requesting party over the network in response to the first request when the first requesting party is not authorized to receive the first value; and

send the first value related to the first data subject to the first requesting party over the network in response to the first request when the first requesting party is authorized to receive the first value.

15. The non-transitory program storage device of claim 14, wherein the network is decentralized, wherein the network comprises a plurality of nodes, and wherein each node in the network stores a copy of the first one of the one or more distributed ledgers.

16. The non-transitory program storage device of claim 15, wherein the first one of the one or more distributed ledgers comprises a blockchain, and wherein the first element comprises a first block.

17. The non-transitory program storage device of claim 14, wherein the instructions further comprise instructions that, when executed, further cause the programmable control device to:

obtain a request from a first user for provision of a privacy policy; and

determine a first privacy policy based, at least in part, on the request,

wherein the first DDID is further configured to comply with the determined first privacy policy.

18. The non-transitory program storage device of claim 14, wherein the first DDID points to a storage location containing the first value related to the first data subject.

19. The non-transitory program storage device of claim 18, wherein the instructions further comprise instructions that, when executed, further cause the programmable control device to:

obtain a request from the first user to modify the first value related to the data subject to be a first modified value; and

store the first modified value in the storage location containing the first value related to the data subject.

20. The non-transitory program storage device of claim 14, wherein the first data subject comprises a first executable term of a smart contract.