US 12,273,448 B2
Secure information sharing systems and methods
Gavin Bunshaw, Melbourne (AU); Leon Madafferi, Melbourne (AU); and Rallas Buttriss, Melbourne (AU)
Assigned to DB RESULTS PTY LTD, Melbourne (AU)
Appl. No. 17/633,779
Filed by DB RESULTS PTY LTD, Melbourne (AU)
PCT Filed Aug. 13, 2020, PCT No. PCT/AU2020/050844
§ 371(c)(1), (2) Date Feb. 8, 2022,
PCT Pub. No. WO2021/026611, PCT Pub. Date Feb. 18, 2021.
Claims priority of application No. 2019902918 (AU), filed on Aug. 13, 2019.
Prior Publication US 2022/0278830 A1, Sep. 1, 2022
Int. Cl. H04L 9/08 (2006.01); G06Q 20/38 (2012.01); H04L 9/40 (2022.01)
CPC H04L 9/088 (2013.01) [G06Q 20/3829 (2013.01); H04L 63/0428 (2013.01); G06Q 2220/00 (2013.01)] 16 Claims
OG exemplary drawing
 
1. A system for secure information sharing comprising:
one or more processors; and
a memory accessible to the one or more processors,
the memory comprising executable program code to implement an information sharing engine, the information sharing engine when executed configures the one or more processors to:
receive a first request from a data owner device to define a data access key, the first request comprising data access parameters and a data access policy,
create a data owner account for a data owner associated with the data owner device, the data owner account comprising a data owner public identifier to publicly identify the data owner and a data owner private identifier, the data owner private identifier not being publicly known;
encrypt the data access parameters to generate the data access key based on the data access parameters, wherein the data access parameters enable querying of a system of record to extract data records;
define a data access control configuration based on the data access policy, the data access control configuration defining data access rights of one or more data consumers;
transmit to a distributed ledger network a request to store the data access key and the data access control configuration on the distributed ledger network;
receive a second request to access the data records from a data consumer device, the second request comprising a data consumer identifier;
create a data consumer account for a data consumer associated with the data consumer device, the data consumer account comprising a data consumer public identifier to publicly identify the corresponding data consumer and a data consumer private identifier, the data consumer private identifier not being publicly known;
responsive to the second request, generate and transmit a third request to access the data records to the distributed ledger network, the third request comprising the data consumer identifier;
when the third request to access data records is determined to be valid based on the data access control configuration, receiving the data access key from the distributed ledger network and making the received data access key accessible to the data consumer device.