Provisioning federated computation on distributed private data

Patent metadata

Field	Value
Publication number	US-2022012355-A1
Application number	US-202117483543-A
Country	US
Kind code	A1
Filing date	Sep 23, 2021
Priority date	Sep 23, 2021
Publication date	Jan 13, 2022
Grant date	—

Abstract

A method comprises receiving in a governor device, from a plurality of data owner devices, metadata for one or more datasets maintained by the plurality of data owner devices, registering the metadata for the one or more datasets with the governor device, in response to a request from an aggregator, providing at least a portion of the metadata for the one or more datasets to the aggregator, receiving, from the aggregator, a compute plan to be implemented by the plurality of data owner devices, distributing at least a portion of the compute plan to the plurality of data owner devices, in response to receiving, from the plurality of data owner devices, a verification report and a certification for an enclave, binding the enclave to a host device, and providing the compute plan to the plurality of data owner devices.

First claim

What is claimed is:

1 . A method comprising:
receiving in a governor device, from a plurality of data owner devices, metadata for one or more datasets maintained by the plurality of data owner devices; registering the metadata for the one or more datasets with the governor device; in response to a request from an aggregator, providing at least a portion of the metadata for the one or more datasets to the aggregator; receiving, from the aggregator, a compute plan to be implemented by the plurality of data owner devices; distributing at least a portion of the compute plan to the plurality of data owner devices; in response to receiving, from the plurality of data owner devices, a verification report and a certification for an enclave, binding the enclave to a host device; and providing the compute plan to the plurality of data owner devices.

2 . The method of claim 1 , wherein the compute plan specifies:
a set of data owner devices from the plurality of data owner devices that are to execute the compute plan; one or more pieces of software to be executed in the compute plan; and one or more data files to be used in the compute plan.

3 . The method of claim 2 , wherein the compute plan comprises:
an image containing a binary file for execution; a hash of the image; a certification from a certification authority; and an enclave identifier.

4 . The method of claim 2 , wherein the compute plan comprises:
an encrypted file comprising the one or more data files to be used in the compute plan.

5 . The method of claim 1 , wherein the plurality of data owner devices:
approve the compute plan; and launch an enclave to execute the compute plan.

6 . The method of claim 5 , wherein the enclave:
generates a certificate; and returns the certificate to a data owner device in the plurality of data owner devices.

7 . The method of claim 1 , further comprising:
monitoring one or more checkpoints in an execution phase of the compute plan.

8 . An apparatus comprising:
a processor; and a computer readable memory comprising instructions which, when executed by the processor, cause the processor to:
receive in a governor device, from a plurality of data owner devices, metadata for one or more datasets maintained by the plurality of data owner devices;
register the one or more datasets with the governor device;
in response to a request from an aggregator, provide at least a portion of the metadata for the one or more datasets to the aggregator;
receive, from the aggregator, a compute plan to be implemented by the plurality of data owner devices;
distribute at least a portion of the compute plan to the plurality of data owner devices;
in response to a receipt, from the plurality of data owner devices, of a verification report and a certification for an enclave, bind the enclave to a host device; and
provide the compute plan to the plurality of data owner devices.

9 . The apparatus of claim 8 , wherein the compute plan specifies:
a set of data owner devices from the plurality of data owner devices that are to execute the compute plan; one or more pieces of software to be executed in the compute plan; and one or more data files to be used in the compute plan.

10 . The apparatus of claim 9 , wherein the compute plan comprises:
an image containing a binary file for execution; a hash of the image; a certification from a certification authority; and an enclave identifier.

11 . The apparatus of claim 9 , wherein the compute plan comprises:
an encrypted file comprising the one or more data files to be used in the compute plan.

12 . The apparatus of claim 8 , wherein the plurality of data owner devices:
approve the compute plan; and launch an enclave to execute the compute plan.

13 . The apparatus of claim 12 , wherein the enclave:
generates a certificate; and returns the certificate to a data owner device in the plurality of data owner devices.

14 . The apparatus of claim 8 , the computer readable memory comprising instructions which, when executed by the processor, cause the processor to:
monitor one or more checkpoints in an execution phase of the compute plan.

15 . One or more computer-readable storage media comprising instructions stored thereon that, in response to being executed, cause a computing device to:
receive in a governor device, from a plurality of data owner devices, metadata for one or more datasets maintained by the plurality of data owner devices; register the one or more datasets with the governor device; in response to a request from an aggregator, provide at least a portion of the metadata for the one or more datasets to the aggregator; receive, from the aggregator, a compute plan to be implemented by the plurality of data owner devices; distribute at least a portion of the compute plan to the plurality of data owner devices; in response to a receipt, from the plurality of data owner devices, of a verification report and a certification for an enclave, bind the enclave to a host device; and provide the compute plan to the plurality of data owner devices.

16 . The one or more computer-readable storage media of claim 16 , wherein the compute plan specifies:
a set of data owner devices from the plurality of data owner devices that are to execute the compute plan; one or more pieces of software to be executed in the compute plan; and one or more data files to be used in the compute plan.

17 . The one or more computer-readable storage media of claim 16 , wherein the compute plan comprises:
an image containing a binary file for execution; a hash of the image; a certification from a certification authority; and an enclave identifier.

18 . The one or more computer-readable storage media of claim 16 , wherein the compute plan comprises:
an encrypted file comprising the one or more data files to be used in the compute plan.

19 . The one or more computer-readable storage media of claim 15 , wherein the plurality of data owner devices:
approve the compute plan; and launch an enclave to execute the compute plan.

20 . The one or more computer-readable storage media of claim 16 , wherein the enclave:
generates a certificate; and returns the certificate to a data owner device in the plurality of data owner devices.

21 . The one or more computer-readable storage media of claim 20 , further comprising instructions stored thereon that, in response to being executed, cause the computing device to:
monitor one or more checkpoints in an execution phase of the compute plan.

Assignees

• Intel Corp

Inventors

• Narayana Moorthy Prakash
• Foley Patrick
• Sheller Micah
• Bowman Clair
• Reina G Anthony
• Martin Jason
• Wang Shih-Han

Classifications

• H04L9/50

  using hash chains, e.g. blockchains or hash trees · CPC title

• H04L9/3234

  involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853) · CPC title

• H04L9/3239

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title

• H04L67/133

  Protocols for remote procedure calls [RPC] · CPC title

• H04L9/3247

  involving digital signatures · CPC title