Multi-party encryption cube processing apparatuses, methods and systems

• US 10,366,239 B2
• Filed: 12/11/2018
• Issued: 07/30/2019
• Est. Priority Date: 02/12/2015
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Harris, Theodore, Edington, Scott
• Primary Examiner(s): Chen, Shin-Hon (Eric)
• Application Number:
  US16/215,975
• Publication Number:
  US 20190108352A1
• Time in Patent Office: 231 Days
• Field of Search: None
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a transaction
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: H04L 2209/46 Secure multiparty computation, e.g. millionaire problem
• CPC Class Codes: H04L 9/008 involving homomorphic encryption
• CPC Class Codes: H04L 9/085 Secret sharing or secret splitting, e.g. threshold schemes
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/033 of the user plane, e.g. user's traffic

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

1. A method for use within secure multi-pa rty computation, comprising:

storing, by one or more data processors, a plurality of operation preferences including allowed database operations and a cryptographic preference, which are both associated with a data set, each cryptographic preference specifying two or more encryption protocols;

storing, by the one or more data processors, the data set on an element by element basis, according to the cryptographic preference;

analyzing, by the one or more data processors, a query from a requestor associated with at least the data set;

determining, by the one or more data processors, that processing the query involves performing an allowable operation on the data set based on the operation preference;

determining, by the one or more data processors, elements of the data set required to perform the allowable operation on the data set;

selecting, by the one or more data processors, an encryption protocol specified by the cryptographic preference for each respective element of the data set; and

using, by the one or more data processors, the at least one of the two or more encryption protocols to perform the allowable operation on the data set, with a summarized version of a transactional data analysis provided to at least the requestor while keeping data from individual contributors to the data set private from one another.

2. The method of claim 1, wherein the data set is stored at a centralized database warehouse having transactional data from multiple merchants and payment service providers.

3. The method of claim 1, wherein the cryptographic preference is selected from a plurality of pre-defined cryptographic protocols.

4. The method of claim 1, wherein one of the two or more encryption protocols is specified by an owner of the data set.

5. The method of claim 1, wherein the operation preference includes an allowed join operation.

6. The method of claim 1, wherein the operation preference includes an allowed retrieval operation.

7. The method of claim 1, wherein a two tiered system is used where methods which require large in-memory usage for each data element can use distributed files system and methods which require less in-memory usage use in-memory databases.

8. A system for use within secure multi-party computation, comprising:

a memory; and

one or more processors disposed in communication with the memory and configured to issue processing instructions stored in the memory to;

store, by one or more data processors, an operation preference including an allowed database operation and a cryptographic preference, which are both associated with a data set, each cryptographic preference including a plurality of encryption protocols;

store, by the one or more data processors, the data set based on the operation preference and the cryptographic preference;

analyze, by the one or more data processors, a query from a requestor associated with at least the data set;

determine, by the one or more data processors, that processing the query involves performing an allowable operation on the data set based on the operation preference;

select, by the one or more data processors, one or more encryption protocols based on the data sets corresponding cryptographic preference and the query; and

use, by the one or more data processors, the one or more encryption protocols to perform the allowable operation on the data set, with a summarized version of a transactional data analysis output encrypted according to the cryptographic preference corresponding to the data set provided to at least the requester while keeping data from individual contributors to the data set private from one another.

9. The system of claim 8, wherein a centralized database warehouse stores transactional data comprising the data set that is received from multiple merchants and payment service providers.

10. The system of claim 8, wherein the cryptographic preference includes a plurality of encryption protocols prescribed for on individual elements of the data set.

11. The system of claim 8, wherein the operation preference includes an allowed join operation.

12. The system of claim 8, wherein the operation preference includes an allowed retrieval operation.

13. The system of claim 8, wherein a two tiered system is used where systems which require large in-memory usage for each data element can use distributed files system and systems which require less in-memory usage use in-memory databases.

14. A method for use in database operations on data sets from multiple parties such that an individual data set is visible only to the party that provided the data set, the method comprising:

storing a plurality of data sets, at least one data set from each of a plurality of parties;

storing an operation preference for each data set, the operation preference specifying, for each element of the data set, one of a plurality of encryption protocols and further specifying allowed database operations for each element of the data set;

receiving, from a requestor, a query associated with a first data set of the plurality of data sets;

analyzing the operation preference for the data set to determine that the query involves allowed database operations for elements of the data set involved in the query;

responsive to determining that the query involves an allowable database operation, selecting one or more encryption protocols according to the operation preference for the elements of the data set involved in the query; and

using the one or more encryption protocols to perform the allowable operation on the data set, with a summarized version of a transactional data analysis provided to at least the requestor while keeping data from individual contributors to the data set private from one another.

15. The method of claim 14, wherein storing the plurality of data sets comprises storing the plurality of data sets in a centralized database warehouse, wherein the data sets include transactional data from multiple merchants and payment service providers.

16. The method of claim 14, wherein the operation preference for a data set is specified by an owner of the data set.

17. The method of claim 14, wherein a query that involves a non-allowable database operation prohibits execution of the query.

18. The method of claim 14, further comprising analyzing the query to determine a memory requirement for the query.

19. The method of claim 18, wherein a first memory requirement uses an in-memory storage.

20. The method of claim 19, wherein a second memory requirement uses a file system when the memory requirement exceeds the in-memory storage.