IP Library Granted Patent US 12,093,426
Granted Patent B2
US 12,093,426 · App. 17/450,948 · Granted Sep 17, 2024

Systems and methods for functionally separating heterogeneous data for analytics, artificial intelligence, and machine learning in global data ecosystems

Inventors: Malcolm Gary LaFever (Lyons, CO); Ted N. Myerson (New York, NY); Mark Little (Matthews, NC); Steven Mason (Las Vegas, NV)
Assignee: Anonos IP LLC
G06F21/6254H04L63/0407G06F2221/2115H04L63/068
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,093,426
App. No.
17/450,948
Granted
Sep 17, 2024
Kind
B2
Abstract

Systems, program storage devices, and methods for improving data privacy/trust/anonymity/pseudonymity and data value, wherein data related to a Data Subject can be used and stored, while minimizing re-identification risk by unauthorized parties and enabling data related to the Data Subject to be disclosed to an authorized party by granting access only to the data relevant to that authorized party's purpose, time, place, and/or other criterion via the obfuscation of specific data values. The techniques described herein maintain this level of privacy/trust/anonymity/pseudonymity, while empowering Data Subjects, e.g., consumers or customers of such authorized parties, by enabling protection of data at the desired level of engagement with various business entities. The techniques described herein also allow Data Controllers to perform General Data Protection Regulation (GDPR) and Schrems II-compliant (and surveillance-proof) data processing, via the functional separation of heterogeneous data (e.g., via the use of “Variant Twins”) from embedded trust and privacy controls.

Claims (126)

1. A method of surveillance-proof data processing, comprising:

(a) receiving source data in protected form at a first cloud server;

(b) transmitting the received source data into a first Trusted Execution Environment (TEE) of the first cloud server;

(c) unprotecting the received source data into cleartext form in the first TEE;

(d) generating, in the first TEE, at least one dynamically-changing, temporally unique identifier (DDID) associated with the unprotected received source data, resulting in processed source data;

(e) re-protecting the processed source data in the first TEE; and

(f) transmitting, by the first cloud server, the re-protected processed source data to a second location.

2. The method of claim 1 , wherein the first cloud server is hosted by a United States (US)-based cloud service provider.

3. The method of claim 1 , wherein the second location comprises another location at the first cloud server.

4. The method of claim 1 , wherein the second location comprises a second cloud server.

5. The method of claim 1 , further comprising:

(g) receiving the re-protected processed source data at the first TEE;

(h) unprotecting, in the first TEE, the received re-protected processed source data, wherein the unprotected processed source data is converted back into at least the at least one DDID; and

(i) re-linking the at least one DDID with its associated cleartext form.

6. The method of claim 5 , further comprising:

(j) re-protecting, in the first TEE, the associated cleartext form of the at least one DDID; and

(k) transmitting the re-protected associated cleartext form of the at least one DDID to a second location.

7. The method of claim 6 , wherein the second location comprises another location at the first cloud server.

8. The method of claim 7 , further comprising performing, at the first cloud server, the following actions:

(l) unprotecting the re-protected associated cleartext form of the at least one DDID; and

(m) performing at least one of the following actions on the unprotected associated cleartext form of the at least one DDID: data analytics; artificial intelligence (AI) processing; or machine learning (ML) processing.

9. The method of claim 1 , further comprising performing, at the first cloud server, the following actions:

(n) unprotecting, in the first TEE, the re-protected processed source data, wherein the unprotected processed source data is converted back into at least the at least one DDID; and

(o) performing at least one of the following actions on the at least one DDID: data analytics; AI processing; or ML processing.

10. The method of claim 6 , wherein the second location comprises a second cloud server.

11. The method of claim 1 , wherein the unprotected received source data comprises two or more data fields in cleartext form, and wherein the two or more data fields are associated with a first data record.

12. The method of claim 11 , wherein the act of: (d) generating, in the first TEE, at least one dynamically-changing, temporally unique identifier (DDID) for the unprotected received source data further comprises:

generating, in the first TEE, a first record-level dynamically-changing, temporally unique identifier (Record-DDID) associated with the first data record.

13. The method of claim 12 , wherein the act of: (d) generating, in the first TEE, at least one dynamically-changing, temporally unique identifier (DDID) for the decrypted received source data further comprises:

generating, in the first TEE, a first association dynamically-changing, temporally unique identifier (A-DDID) or a first DDID for at least one of the two or more data fields.

14. The method of claim 13 , wherein the first data record, the associated first Record-DDID, and the generated first A-DDIDs or first DDIDs for at least one of the two or more data fields comprise a first Variant Twin.

15. The method of claim 14 , further comprising:

generating, in the first TEE, a second Record-DDID associated with the first data record;

generating, in the first TEE, a second A-DDID or a second DDID for at least one of the two or more data fields,

wherein the first data record, the associated second Record-DDID, and the generated second A-DDIDs or second DDIDs for at least one of the two or more data fields comprise a second Variant Twin.

16. The method of claim 12 , further comprising:

using the first Record-DDID to re-link the first data record with the two or more data fields associated with the first data record.

17. The method of claim 8 , wherein at least one of the at least one DDIDs generated in the first TEE comprises: a Non-Attributing Data Element Value (NADEV); or an A-DDID representing a microsegment (MSeg).

18. The method of claim 9 , wherein at least one of the at least one DDIDs generated in the first TEE comprises: a NADEV; or an A-DDID representing an MSeg.

19. The method of claim 1 , wherein the protected form comprises an encrypted form.

20. The method of claim 19 , wherein unprotecting the received source data into cleartext form comprises decrypting the received source data.

21. A system, comprising:

a first cloud server, wherein the first cloud server comprises a first Trusted Execution Environment (TEE);

a memory having, stored therein, computer program code; 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:

(a) receive source data in protected form at the first cloud server;

(b) transmit the received source data into the first TEE of the first cloud server;

(c) unprotect the received source data into cleartext form in the first TEE;

(d) generate, in the first TEE, at least one dynamically-changing, temporally unique identifier (DDID) associated with the unprotected received source data, resulting in processed source data;

(e) re-protect the processed source data in the first TEE; and

(f) transmit, by the first cloud server, the re-protected processed source data to a second location.

22. The system of claim 21 , wherein the first cloud server is hosted by a United States (US)-based cloud service provider.

23. The system of claim 21 , wherein the second location comprises another location at the first cloud server.

24. The system of claim 21 , wherein the second location comprises a second cloud server.

25. The system of claim 21 , wherein the computer program code further causes the one or more processing units to:

(g) receive the re-protected processed source data at the first TEE;

(h) unprotect, in the first TEE, the received re-protected processed source data, wherein the unprotected processed source data is converted back into at least the at least one DDID; and

(i) re-link the at least one DDID with its associated cleartext form.

26. The system of claim 25 , wherein the computer program code further causes the one or more processing units to:

(j) re-protect, in the first TEE, the associated cleartext form of the at least one DDID; and

(k) transmit the re-protected associated cleartext form of the at least one DDID to a second location.

27. The system of claim 26 , wherein the second location comprises another location at the first cloud server.

28. The system of claim 27 , wherein the computer program code further causes the one or more processing units to:

(l) unprotect the re-protected associated cleartext form of the at least one DDID; and

(m) perform at least one of the following actions on the unprotected associated cleartext form of the at least one DDID: data analytics; artificial intelligence (AI) processing; or machine learning (ML) processing.

29. The system of claim 21 , wherein the computer program code further causes the one or more processing units to:

(n) unprotect, in the first TEE, the re-protected processed source data, wherein the unprotected processed source data is converted back into at least the at least one DDID; and

(o) perform at least one of the following actions on the at least one DDID: data analytics; AI processing; or ML processing.

30. The system of claim 26 , wherein the second location comprises a second cloud server.

31. The system of claim 21 , wherein the unprotected received source data comprises two or more data fields in cleartext form, and wherein the two or more data fields are associated with a first data record.

32. The system of claim 31 , wherein the computer program code that causes the one or more processing units to: (d) generate, in the first TEE, at least one dynamically-changing, temporally unique identifier (DDID) for the unprotected received source data further comprises computer program code that causes the one or more processing units to:

generate, in the first TEE, a first record-level dynamically-changing, temporally unique identifier (Record-DDID) associated with the first data record.

33. The system of claim 32 , wherein the computer program code that causes the one or more processing units to: (d) generate, in the first TEE, at least one dynamically-changing, temporally unique identifier (DDID) for the unprotected received source data further comprises computer program code that causes the one or more processing units to:

generate, in the first TEE, a first association dynamically-changing, temporally unique identifier (A-DDID) or a first DDID for at least one of the two or more data fields.

34. The system of claim 33 , wherein the first data record, the associated first Record-DDID, and the generated first A-DDIDs or first DDIDs for at least one of the two or more data fields comprise a first Variant Twin.

35. The system of claim 34 , wherein the computer program code further causes the one or more processing units to:

generate, in the first TEE, a second Record-DDID associated with the first data record;

generate, in the first TEE, a second A-DDID or a second DDID for at least one of the two or more data fields,

wherein the first data record, the associated second Record-DDID, and the generated second A-DDIDs or second DDIDs for at least one of the two or more data fields comprise a second Variant Twin.

36. The system of claim 32 , wherein the computer program code further causes the one or more processing units to:

use the first Record-DDID to re-link the first data record with the two or more data fields associated with the first data record.

37. The system of claim 28 , wherein at least one of the at least one DDIDs generated in the first TEE comprises: a Non-Attributing Data Element Value (NADEV); or an A-DDID representing a microsegment (MSeg).

38. The system of claim 29 , wherein at least one of the at least one DDIDs generated in the first TEE comprises: a NADEV; or an A-DDID representing an MSeg.

39. The system of claim 21 , wherein the protected form comprises an encrypted form.

40. The system of claim 39 , wherein the computer program code that causes the one or more processing units to unprotect the received source data into cleartext form comprises computer program code that causes the one or more processing units to decrypt the received source data.

41. A non-transitory program storage device (NPSD), readable by one or more processing units, comprising computer program code stored thereon that, when executed, causes the one or more processing units to:

(a) receive source data in protected form at a first cloud server;

(b) cause the received source data to be transmitted into a first Trusted Execution Environment (TEE) of the first cloud server;

(c) unprotect the received source data into cleartext form in the first TEE;

(d) generate, in the first TEE, at least one dynamically-changing, temporally unique identifier (DDID) associated with the unprotected received source data, resulting in processed source data;

(e) re-protect the processed source data in the first TEE; and

(f) cause the re-protected processed source data to be transmitted, by the first cloud server, to a second location.

42. The NPSD of claim 41 , wherein the first cloud server is hosted by a United States (US)-based cloud service provider.

43. The NPSD of claim 41 , wherein the second location comprises another location at the first cloud server.

44. The NPSD of claim 41 , wherein the second location comprises a second cloud server.

45. The NPSD of claim 41 , wherein the computer program code further causes the one or more processing units to:

(g) receive the re-protected processed source data at the first TEE;

(h) unprotect, in the first TEE, the received re-protected processed source data, wherein the unprotected processed source data is converted back into at least the at least one DDID; and

(i) re-link the at least one DDID with its associated cleartext form.

46. The NPSD of claim 45 , wherein the computer program code further causes the one or more processing units to:

(j) re-protect, in the first TEE, the associated cleartext form of the at least one DDID; and

(k) transmit the re-protected associated cleartext form of the at least one DDID to a second location.

47. The NPSD of claim 46 , wherein the second location comprises another location at the first cloud server.

48. The NPSD of claim 47 , wherein the computer program code further causes the one or more processing units to:

(l) unprotect the re-protected associated cleartext form of the at least one DDID; and

(m) perform at least one of the following actions on the unprotected associated cleartext form of the at least one DDID: data analytics; artificial intelligence (AI) processing; or machine learning (ML) processing.

49. The NPSD of claim 41 , wherein the computer program code further causes the one or more processing units to:

(n) unprotect, in the first TEE, the re-protected processed source data, wherein the unprotected processed source data is converted back into at least the at least one DDID; and

(o) perform at least one of the following actions on the at least one DDID: data analytics; AI processing; or ML processing.

50. The NPSD of claim 46 , wherein the second location comprises a second cloud server.

51. The NPSD of claim 41 , wherein the unprotected received source data comprises two or more data fields in cleartext form, and wherein the two or more data fields are associated with a first data record.

52. The NPSD of claim 51 , wherein the computer program code that causes the one or more processing units to: (d) generate, in the first TEE, at least one dynamically-changing, temporally unique identifier (DDID) for the unprotected received source data further comprises computer program code that causes the one or more processing units to:

generate, in the first TEE, a first record-level dynamically-changing, temporally unique identifier (Record-DDID) associated with the first data record.

53. The NPSD of claim 52 , wherein the computer program code that causes the one or more processing units to: (d) generate, in the first TEE, at least one dynamically-changing, temporally unique identifier (DDID) for the unprotected received source data further comprises computer program code that causes the one or more processing units to:

generate, in the first TEE, a first association dynamically-changing, temporally unique identifier (A-DDID) or a first DDID for at least one of the two or more data fields.

54. The NPSD of claim 53 , wherein the first data record, the associated first Record-DDID, and the generated first A-DDIDs or first DDIDs for at least one of the two or more data fields comprise a first Variant Twin.

55. The NPSD of claim 54 , wherein the computer program code further causes the one or more processing units to:

generate, in the first TEE, a second Record-DDID associated with the first data record;

generate, in the first TEE, a second A-DDID or a second DDID for at least one of the two or more data fields,

wherein the first data record, the associated second Record-DDID, and the generated second A-DDIDs or second DDIDs for at least one of the two or more data fields comprise a second Variant Twin.

56. The NPSD of claim 52 , wherein the computer program code further causes the one or more processing units to:

use the first Record-DDID to re-link the first data record with the two or more data fields associated with the first data record.

57. The NPSD of claim 48 , wherein at least one of the at least one DDIDs generated in the first TEE comprises: a Non-Attributing Data Element Value (NADEV); or an A-DDID representing a microsegment (MSeg).

58. The NPSD of claim 49 , wherein at least one of the at least one DDIDs generated in the first TEE comprises: a NADEV; or an A-DDID representing an MSeg.

59. The NPSD of claim 41 , wherein the protected form comprises an encrypted form.

60. The NPSD of claim 59 , wherein the computer program code that causes the one or more processing units to unprotect the received source data into cleartext form comprises computer program code that causes the one or more processing units to decrypt the received source data.

Assignments (7)
RELEASE OF SECURITY INTEREST Recorded May 8, 2026
From: ANKURA TRUST COMPANY, LLC
To: ANONOS IP LLC
Reel/Frame 074607/0340 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2026
From: ANONOS TECHNOLOGIES LLC
To: ANONOS INNOVATIONS LLC
Reel/Frame 073688/0692 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 2, 2026
From: SONONA LLC
To: ANONOS TECHNOLOGIES LLC
Reel/Frame 073661/0128 →
ASSIGNMENT OF INTELLECTUAL PROPERTY Recorded Oct 3, 2025
From: ANKURA TRUST COMPANY, LLC
To: SONONA LLC
Reel/Frame 072997/0822 →
SECURITY INTEREST Recorded Oct 12, 2022
From: ANONOS IP LLC
To: ANKURA TRUST COMPANY, LLC
Reel/Frame 061395/0457 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 2, 2022
From: ANONOS INC.
To: ANONOS IP LLC
Reel/Frame 060978/0927 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 18, 2021
From: LAFEVER, MALCOLM GARY; MYERSON, TED N.; LITTLE, MARK; MASON, STEVEN
To: ANONOS INC.
Reel/Frame 057823/0976 →
Continuity (44)
Continuation In Part 17339814 · Jun 4, 2021
Continuation 16449037 · Jun 21, 2019
Continuation In Part 15963609 · Apr 26, 2018
Continuation In Part 15483997 · Apr 10, 2017
Continuation In Part 15174797 · Jun 6, 2016
Continuation In Part 14846167 · Sep 4, 2015
Continuation In Part 14530304 · Oct 31, 2014
Continuation 14529960 · Oct 31, 2014
Provisional Application 63262083 · Oct 4, 2021
Provisional Application 63163550 · Mar 19, 2021
Provisional Application 63125672 · Dec 15, 2020
Provisional Application 63091363 · Oct 14, 2020
Provisional Application 62800514 · Feb 3, 2019
Provisional Application 62772146 · Nov 28, 2018
Provisional Application 62688410 · Jun 22, 2018
Provisional Application 62649103 · Mar 28, 2018
Provisional Application 62644463 · Mar 17, 2018
Provisional Application 62580628 · Nov 2, 2017
Provisional Application 62554000 · Sep 4, 2017
Provisional Application 62535601 · Jul 21, 2017
Provisional Application 62491294 · Apr 28, 2017
Provisional Application 62059882 · Oct 4, 2014
Provisional Application 62055669 · Sep 26, 2014
Provisional Application 62051270 · Sep 16, 2014
Provisional Application 62045321 · Sep 3, 2014
Provisional Application 62043238 · Aug 28, 2014
Provisional Application 62037703 · Aug 15, 2014
Provisional Application 62019987 · Jul 2, 2014
Provisional Application 62015431 · Jun 21, 2014
Provisional Application 62001127 · May 21, 2014
Provisional Application 61994715 · May 16, 2014
Provisional Application 61994721 · May 16, 2014
Provisional Application 61994076 · May 15, 2014
Provisional Application 61992441 · May 13, 2014
Provisional Application 61988373 · May 5, 2014
Provisional Application 61974442 · Apr 3, 2014
Provisional Application 61969194 · Mar 23, 2014
Provisional Application 61948575 · Mar 6, 2014
Provisional Application 61945821 · Feb 27, 2014
Provisional Application 61944565 · Feb 25, 2014
Provisional Application 61941242 · Feb 18, 2014
Provisional Application 61938631 · Feb 11, 2014
Provisional Application 61899096 · Nov 1, 2013
Related Publication 20220050921A1 · Feb 17, 2022
Cited By (3)
US 12,519,639 US 12,524,562 US 12,720,127