US 11,934,550 B2
Replacing distinct data in a relational database with a distinct reference to that data and distinct de-referencing of database data
James Douglas Beecham, Austin, TX (US); Christopher Edward Struttmann, Indialantic, FL (US); and Scott Nathaniel Goldfarb, Washington, MI (US)
Assigned to ALTR SOLUTIONS, INC., Melbourne, FL (US)
Filed by ALTR Solutions, Inc., Austin, TX (US)
Filed on Apr. 20, 2022, as Appl. No. 17/725,503.
Application 17/725,503 is a continuation of application No. 16/449,235, filed on Jun. 21, 2019, granted, now 11,347,878.
Application 16/449,235 is a continuation of application No. 16/024,792, filed on Jun. 30, 2018, granted, now 10,366,247, issued on Jul. 30, 2019.
Application 16/024,792 is a continuation in part of application No. 15/845,436, filed on Dec. 18, 2017, granted, now 10,242,219, issued on Mar. 26, 2019.
Application 15/845,436 is a continuation of application No. 15/675,490, filed on Aug. 11, 2017, granted, now 9,881,176, issued on Jan. 30, 2018.
Application 15/675,490 is a continuation in part of application No. 15/171,347, filed on Jun. 2, 2016, granted, now 10,581,977, issued on Mar. 3, 2020.
Claims priority of provisional application 62/527,330, filed on Jun. 30, 2017.
Claims priority of provisional application 62/374,278, filed on Aug. 12, 2016.
Claims priority of provisional application 62/169,823, filed on Jun. 2, 2015.
Prior Publication US 2022/0318417 A1, Oct. 6, 2022
Int. Cl. G06F 21/62 (2013.01); G06F 16/901 (2019.01); H04L 9/32 (2006.01)
CPC G06F 21/6218 (2013.01) [G06F 16/9014 (2019.01); G06F 16/9024 (2019.01); H04L 9/3239 (2013.01); G06F 2221/2107 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A tangible, non-transitory, machine-readable medium storing instructions that when executed by one or more processors effectuate operations comprising:
obtaining, with one or more processors, criteria to select plain-text values in, or requested to be written to, a lower-trust database;
selecting, based on the criteria, a first plain-text value stored in, or requested to be stored in, a first entry in the lower-trust database;
in response to selecting the first plain-text value, determining, with one or more processors, a first reference value, wherein:
the criteria indicate whether the plain-text values are to be stored in the lower-trust database or a higher-trust database;
the lower-trust database stores relationships between both plain-text values stored in the lower-trust database and plain-text values stored in the higher-trust database; and
the first reference value does not reveal the first plain-text value without access to the higher-trust database;
storing, with one or more processors, the first plain-text value in the higher-trust database in a second entry identified by the first reference value;
storing, with one or more processors, the first reference value in the first entry of the lower-trust database;
selecting, with one or more processors, another instance of the first plain-text value stored in, or requested to be stored in, a third entry in the lower-trust database, the third entry being a different entry from the first entry; and
in response to selecting another instance of the first plain-text value stored in, or requested to be stored in, the third entry in the lower-trust database, storing, with one or more processors, a value associated with, or equal to, the first reference value.