# US 12,223,079 B2 · Provisioning federated computation on distributed private data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,223,079 B2 - Document ID: US12223079B2 - Status: Granted - Kind: B2 - Application number: 17/483,543 - Filed: 2021-09-23 - Published: 2022-01-13 - Granted: 2025-02-11 - Earliest claimed: 2021-09-23 - Assignees: Intel Corporation - Applicants: Intel Corporation - Inventors: Prakash Narayana Moorthy; Patrick Foley; Micah Sheller; Clair Bowman; G. Anthony Reina; Jason Martin; Shih-Han Wang - Web page: https://patentgrep.com/patent/US12223079B2 ## CPC - G06F 21/6227: {where protection concerns the structure of data, e.g. records, types, queries} - G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes} - G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities - G06F 21/602: {Providing cryptographic facilities or services} - H04L 9/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)} - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/3247: {involving digital signatures} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L 67/133: Protocols for remote procedure calls [RPC] - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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. ## Claims ### Claim 1 A method comprising: receiving, by a processor of a computing device, metadata for one or more datasets maintained by data-owner devices; in response to receiving a request from an aggregator device, providing at least a portion of the metadata for the one or more datasets to the aggregator device; receiving, from the aggregator device, a compute plan to be implemented by the data-owner devices; monitoring one or more checkpoints in an execution phase of the compute plan; and distributing at least a portion of the compute plan to the data-owner devices, wherein the compute plan is executed by one or more of the data-owner devices as specified by the compute plan. ### Claim 2 (depends on 1) The method of claim 1, wherein in response to receiving, from the data-owner devices, one or more of a verification report or a certification for an enclave, wherein the enclave is bound to a host device, wherein the compute plan specifies one or more of: one or more pieces of software to be executed in the compute plan; or one or more data files to be used in the compute plan. ### Claim 3 (depends on 2) 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; an enclave identifier; and an encrypted file comprising the one or more data files to be used in the compute plan. ### Claim 4 (depends on 1) The method of claim 1, further comprising: approving the compute plan; and launching an enclave to execute the compute plan, wherein the enclave generates the certificate and returns the certificate to a data-owner device. ### Claim 5 An apparatus comprising: processor circuitry coupled to a memory, the processor circuitry to: receive metadata for one or more datasets maintained by data-owner devices; in response to receiving a request from an aggregator device, provide at least a portion of the metadata for the one or more datasets to the aggregator device; receive, from the aggregator device, a compute plan to be implemented by the data-owner devices; monitor one or more checkpoints in an execution phase of the compute plan; and distribute at least a portion of the compute plan to the data-owner devices, wherein the compute plan is executed by one or more of the data-owner devices as specified by the compute plan. ### Claim 6 (depends on 5) The apparatus of claim 5, wherein in response to receiving, from the data-owner devices, one or more of a verification report or a certification for an enclave, wherein the enclave is bound to a host device, wherein the compute plan specifies one or more of: one or more pieces of software to be executed in the compute plan; or one or more data files to be used in the compute plan. ### Claim 7 (depends on 6) The apparatus of claim 6, wherein the compute plan comprises: an image containing a binary file for execution; a hash of the image; a certification from a certification authority; an enclave identifier; and an encrypted file comprising the one or more data files to be used in the compute plan. ### Claim 8 (depends on 5) The apparatus of claim 5, wherein the processor circuitry is further to: approve the compute plan; and launch an enclave to execute the compute plan, wherein the enclave generates the certificate and returns the certificate to a data-owner device. ### Claim 9 At least one non-transitory computer-readable medium having stored thereon instructions which, when executed, cause a computing device to perform operations comprising: receiving metadata for one or more datasets maintained by data-owner devices; in response to receiving a request from an aggregator device, providing at least a portion of the metadata for the one or more datasets to the aggregator device; receiving, from the aggregator device, a compute plan to be implemented by the data-owner devices; monitor one or more checkpoints in an execution phase of the compute plan; and distributing at least a portion of the compute plan to the data-owner devices, wherein the compute plan is executed by one or more of the data-owner devices as specified by the compute plan. ### Claim 10 (depends on 9) The non-transitory computer-readable medium of claim 9, wherein in response to receiving, from the data-owner devices, one or more of a verification report or a certification for an enclave, wherein the enclave is bound to a host device, wherein the compute plan specifies one or more of: one or more pieces of software to be executed in the compute plan; or one or more data files to be used in the compute plan. ### Claim 11 (depends on 10) The non-transitory computer-readable medium of claim 10, wherein the compute plan comprises: an image containing a binary file for execution; a hash of the image; a certification from a certification authority; an enclave identifier; and an encrypted file comprising the one or more data files to be used in the compute plan. ### Claim 12 (depends on 9) The non-transitory computer-readable medium of claim 9, wherein the operations further comprise: approve the compute plan; and launch an enclave to execute the compute plan, wherein the enclave generates the certificate and returns the certificate to a data-owner device.