Abstract: A method for data processing by a data clean room orchestration system is described. The method includes receiving an indication of mutually attested code for a data clean room between two or more partners. The method further includes configuring a trusted execution environment (TEE), including one or more virtual machines (VMs) that are individually or collectively operable to execute the mutually attested code. The method further includes transmitting, to endpoints associated with the partners, an attestation report including at least an encrypted token and a host public key of a host machine associated with the one or more VMs. The method further includes receiving respective partner secret keys wrapped with the host public key. The method further includes executing the mutually attested code on respective partner datasets in the TEE based on using a host private key of the host machine to unwrap the respective partner secret keys.

Abstract: Methods, systems, and devices for data processing are described. A process orchestration layer of a data processing system may obtain an indication of code that has been approved by two or more parties of a secured sharing session. The process orchestration layer may generate a stored procedure that includes an initialization function, an output function, and a run function with the approved code. The process orchestration layer may output, to a first sub-system associated with a first party of the secured sharing session, a request that causes the first sub-system to execute the stored procedure. The process orchestration layer may receive an indication of an encrypted session token from the first sub-system in accordance with the initialization function of the stored procedure. The process orchestration layer may validate the encrypted session token and provide the validated session token to other parties of the secured sharing session.

Abstract: Computer-readable media, computer systems, and computing devices for responding to advertising inventory queries that specify frequency caps limiting the number of impressions that are shown to a unique user. Impression logs are retrieved from logging servers and processed to generate a unique user distribution that provides information regarding the numbers of unique users that receive ad impressions at a specified location and during a specified time period. Estimates of frequency-capped capacity to fulfill a booking request and estimates of frequency-capped availability of inventory are computed using the unique user distribution.