# US 2025/0094561 A1 · Verifiable secure dataset operations with private join keys

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0094561 A1
- Document ID: US20250094561A1
- Status: Published application
- Kind: A1
- Application number: 18/573,374
- Filed: 2023-07-24
- Published: 2025-03-20
- Earliest claimed: 2022-07-24
- Assignees: Google Inc.
- Applicants: Google LLC
- Inventors: Carlos Cela; John Tobler; Eugene Shaphir; Chanda Patel; Quaseer Mujawar; Farshid Shariatzadeh; Dina Kurman; Minh Hoang
- Web page: https://patentgrep.com/patent/US20250094561A1

## CPC

- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/6227: {where protection concerns the structure of data, e.g. records, types, queries}
- G06F 2221/033: Test or assess software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

To performing a join operation, a module executing in a trusted execution environment (TEE) receives a first dataset including personal identifiable information (PII) data and non-PII data from a first-party (1P) data source. The module pre-processes the PII data to generate first formatted PII data, the first formatted PII data conforming to a predefined format: matches, in the TEE, the first formatted PII data to second formatted PII data included in a second dataset: performs a join operation between the first dataset and the second dataset based on the matching, to generate a joined dataset: and provides, to a data service operating independently of the 1P data source, the joined dataset.

## Claims

### Claim 1

A method in one or more servers for performing a join operation, the method comprising:
receiving, at a module executing in a trusted execution environment (TEE) from a first-party (1P) data source, a first dataset including personal identifiable information (PII) data and non-PII data;
pre-processing the PII data to generate first formatted PII data, the first formatted PII data conforming to a predefined format;
matching, in the TEE, the first formatted PII data to second formatted PII data included in a second dataset;
performing a join operation between the first dataset and the second dataset based on the matching, to generate a joined dataset; and
providing, to a data service operating independently of the 1P data source, the joined dataset.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
performing, by the module and prior to the receiving of the first dataset, authentication with the 1P data source.

### Claim 3 (depends on 2)

The method of claim 2, wherein the performing of the authentication includes performing a decryption operation using credentials associated with the 1P data source.

### Claim 4 (depends on 1)

The method of claim 1, wherein:
the module implements a secure connector configured to use credentials associated with the 1P data source; and
the matching is implemented in a secure join module which is prevented from accessing the credentials associated with the 1P data source.

### Claim 5 (depends on 4)

The method of claim 4, the method further comprising:
providing the first formatted PII data from the secure connector to the secure join module via an extract-transform-load (ETL) pipeline.

### Claim 6 (depends on 5)

The method of claim 5, wherein the ETL pipeline is configured to provide the first formatted PII data to (i) the data service and (ii) a repository for time-deferred consumption of the first formatted PII data.

### Claim 7 (depends on 4)

The method of claim 4, further comprising:
receiving, at the secure connector, the encrypted DEK associated with the 1P data source;
providing, from the secure connector to the secured join module, the encrypted DEK.

### Claim 8 (depends on 7)

The method of claim 7, further comprising:
decrypting the encrypted DEK using a key management service (KMS) to generate a DEK;
wherein:
the PII data received with the first dataset from the 1P data source is encrypted;
the pre-processing of the PII data includes decrypting the received PII data prior to generating the first formatted PII data.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
encrypting the first formatted PII data using the DEK at the secure connector prior to providing the first formatted PII data to the secure join module.

### Claim 10 (depends on 8)

The method of claim 8, further comprising:
hashing the first formatted PII data at the secure connector prior to providing the first formatted PII data to the secure join module.

### Claim 11 (depends on 10)

The method of claim 10, wherein the matching of the first formatted PII data to second formatted PII data is implemented in the secure join module and is based on hashed PII data.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
discarding non-matched rows in the first dataset and the second dataset.

### Claim 13 (depends on 1)

The method of claim 1, wherein:
both the receiving and the matching are implemented in the module configured to operate as a secure connector and a PII match component; and
the providing of the joined dataset includes providing the joined dataset from the secure connector and the PII match component to the data service via an ETL pipeline.

### Claim 14 (depends on 1)

The method of claim 1, wherein the receiving of the first dataset includes receiving the first dataset in cleartext over an encrypted link.

### Claim 15

A system comprising:
one or more servers including processing hardware and configured to:
receive, at a module executing in a trusted execution environment (TEE) from a first-party (1P) data source, a first dataset including personal identifiable information (PII) data and non-PII data;
pre-process the PII data to generate first formatted PII data, the first formatted PII data conforming to a predefined format;
match, in the TEE, the first formatted PII data to second formatted PII data included in a second dataset;
perform a join operation between the first dataset and the second dataset based on the matching, to generate a joined dataset; and
provide, to a data service operating independently of the 1P data source, the joined dataset.

### Claim 16 (depends on 15)

The system of claim 15, wherein the one or more servers are further configured to:
perform, by the module and prior to the receiving of the first dataset, authentication with the 1P data source.

### Claim 17 (depends on 16)

The system of claim 16, wherein the one or more servers are configured to perform the authentication by performing a decryption operation using credentials associated with the 1P data source.

### Claim 18 (depends on 15)

The system of claim 15, wherein:
the module implements a secure connector configured to use credentials associated with the 1P data source; and
the matching is implemented in a secure join module which is prevented from accessing the credentials associated with the 1P data source.

### Claim 19 (depends on 18)

The system of claim 18, wherein the one or more servers are further configured to:
provide the first formatted PII data from the secure connector to the secure join module via an extract-transform-load (ETL) pipeline.

### Claim 20 (depends on 19)

The system of claim 19, wherein the ETL pipeline is configured to provide the first formatted PII data to (i) the data service and (ii) a repository for time-deferred consumption of the first formatted PII data.
