US2023367888A1PendingUtilityA1
Multi-party encryption cube processing apparatuses, methods and systems
Est. expiryFeb 12, 2035(~8.6 yrs left)· nominal 20-yr term from priority
G06F 21/602G06F 21/6245G06Q 20/3823G06Q 40/00H04L 9/008H04W 12/02H04W 12/033H04L 2209/46H04L 9/085
80
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
Computer-implemented systems and methods are disclosed herein for use within secure multi-party computation. A system and method are used for storing an operation preference and a cryptographic preference. A data set is stored based on the operation preference and the cryptographic preference. A determination is made that processing the query involves performing an allowable operation on the data set based on the operation preference.
Claims
exact text as granted — not AI-modified1 .- 21 . (canceled)
22 . A client system for use in database operations on data associated with multiple parties, the client system comprising:
a memory; and one or more processors for executing instructions stored in the memory to:
transmit, to a data processing system, first data handling preferences associated with first transaction data stored in a database;
transmit, to the data processing system, a query associated with an attribute of the first transaction data; and
receive, from the data processing system, a summarized version of a transaction data analysis, wherein the transaction data analysis is based on:
the attribute of the first transaction data;
second transaction data stored in the database, the second transaction data inaccessible to the client system; and
an allowable operation determined by the data processing system according to the first data handling preferences and second data handling preferences associated with the second transaction data, wherein the allowable operation is performed on the first transaction data and the second transaction data; and
wherein the summarized version of the transaction data analysis excludes the second transaction data.
23 . The client system of claim 22 , wherein the first data handling preferences comprise at least one of a first operation preference or a first encryption protocol.
24 . The client system of claim 23 wherein the allowable operation is performed with the first encryption protocol.
25 . The client system of claim 23 , wherein the second data handling preferences comprise at least one of a second operation preference or a second encryption protocol.
26 . The client system of claim 25 , wherein the allowable operation is performed with the encryption protocol and the second encryption protocol.
27 . The client system of claim 23 wherein the first operation preference includes at least one of an allowed join operation or an allowed retrieval operation.
28 . The client system of claim 22 , wherein the summarized version of the transaction data analysis comprises aggregated statistics.
29 . The client system of claim 22 , wherein the summarized version of the transaction data analysis excludes the first transaction data.
30 . The client system of claim 23 , wherein the first data handling preferences comprises Yao's algorithm.
31 . The client system of claim 27 wherein the allowable operation comprises the allowed join operation and the first encryption protocol.
32 . The client system of claim 31 , wherein the first encryption protocol is a homomorphic-like method or Yao's algorithm.
33 . A method for use in database operations on data associated with multiple parties, the method comprising:
providing, by a first user to a data processor, first data handling preferences associated with first transaction data stored in a database; submitting, by the first user to the data processor, a query associated with an attribute of the first transaction data; and receiving, by the first user from the data processor, a summarized version of a transaction data analysis, wherein the transaction data analysis is based on:
sensitive data elements associated with the first transaction data and second transaction data, wherein the second transaction data is stored in the database, the second transaction data inaccessible to the first user; and
an allowable operation determined by the data processor according to the first data handling preferences and second data handling preferences associated with the second transaction data, wherein the allowable operation is performed on the sensitive data elements; and
wherein the summarized version of the transaction data analysis comprises results of the transaction data analysis without reporting sensitive data elements associated with the second transaction data.
34 . The method of claim 33 , the method comprising providing, by the first user to the data processor, first data handling preferences associated with first transaction data stored in the database, wherein the first data handling preferences comprise at least one of a first operation preference or a first encryption protocol to be implemented on the first transaction data.
35 . The method of claim 34 , wherein the allowable operation is performed with the first encryption protocol.
36 . The method of claim 34 , wherein the second data handling preferences comprise at least one of a second operation preference or a second encryption protocol to be implemented on the second transaction data.
37 . The method of claim 33 , wherein the second data handling preference was provided by a second user.
38 . The method of claim 37 , wherein an identity of the second user is unknown to the first user.
39 . The method of claim 34 , wherein providing, by the first user to the data processor, first data handling preferences comprises selecting the first data handling preferences from a list of data handling preferences provided by the data processor.
40 . The method of claim 39 , wherein the list of data handling preferences comprises Yao's algorithm and a homomorphic-like method.
41 . The method of claim 33 , wherein providing, by the first user to the data processor, first data handling preferences comprises supplying, by the first user to the data processor, an encryption method previously unavailable to the data processor.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.