US 12,250,203 B2
Controlling transmission of information through a zero-knowledge data management network
Brett Shockley, Bonita Springs, FL (US); Alexander John Shockley, Denver, CO (US); Michael Joseph Frendo, Boulder, CO (US); Shmuel Shaffer, Palo Alto, CA (US); Kenneth Keiter, Portland, OR (US); and James M. Behmke, Duxbury, MA (US)
Assigned to Journey.ai, Denver, CO (US)
Filed by Journey.ai, Denver, CO (US)
Filed on Oct. 3, 2023, as Appl. No. 18/376,100.
Application 18/376,100 is a continuation of application No. 16/703,852, filed on Dec. 4, 2019, granted, now 11,777,913.
Claims priority of provisional application 62/852,850, filed on May 24, 2019.
Claims priority of provisional application 62/775,302, filed on Dec. 4, 2018.
Prior Publication US 2024/0106812 A1, Mar. 28, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 9/40 (2022.01); G06F 3/06 (2006.01); G06F 21/60 (2013.01); G06F 21/62 (2013.01); G06F 21/64 (2013.01); G06Q 20/38 (2012.01); G06Q 20/40 (2012.01); H04L 9/06 (2006.01); H04L 9/08 (2006.01); H04L 9/14 (2006.01); H04L 9/30 (2006.01); H04L 9/32 (2006.01)
CPC H04L 63/0471 (2013.01) [G06F 3/062 (2013.01); G06F 3/0655 (2013.01); G06F 3/067 (2013.01); G06F 21/602 (2013.01); G06F 21/62 (2013.01); G06F 21/645 (2013.01); G06Q 20/38215 (2013.01); G06Q 20/3829 (2013.01); G06Q 20/383 (2013.01); G06Q 20/401 (2013.01); H04L 9/0643 (2013.01); H04L 9/0819 (2013.01); H04L 9/0825 (2013.01); H04L 9/083 (2013.01); H04L 9/0833 (2013.01); H04L 9/0891 (2013.01); H04L 9/14 (2013.01); H04L 9/30 (2013.01); H04L 9/3218 (2013.01); H04L 9/3236 (2013.01); H04L 9/3242 (2013.01); H04L 9/3247 (2013.01); H04L 9/3263 (2013.01); H04L 9/3265 (2013.01); H04L 9/3268 (2013.01); H04L 63/0421 (2013.01); H04L 63/0442 (2013.01); H04L 63/083 (2013.01); H04L 63/101 (2013.01); H04L 63/102 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method, comprising:
participating, by a device, in a data storage system, wherein a storage server is configured to i) obtain source data from a source, wherein no device other than the source is able to read the source data; ii) obtain a conversion key specific to a particular recipient from the source; iii) convert, based on the conversion key and in response to a request to share the source data with the particular recipient, the source data into a format readable only by the particular recipient;
performing, by the device, a transaction with the source;
detecting, by the device, a trigger to share the source data that is stored at the storage server with the particular recipient based on the transaction; and
causing, by the device, the request to share the source data with the particular recipient to be sent to the storage server in response to the trigger to cause the particular recipient to i) receive the source data in the format readable only by the particular recipient; and ii) process the source data readable by the particular recipient.