# US 2021/0176245 A1 · Requesting and transmitting data for related accounts

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

- Number: US 2021/0176245 A1
- Document ID: US20210176245A1
- Status: Published application
- Kind: A1
- Application number: 16/707,124
- Filed: 2019-12-09
- Published: 2021-06-10
- Earliest claimed: 2019-12-09
- Assignees: Google Inc.
- Applicants: Google LLC
- Inventors: Elliot Jaffe; Antonio Trapanese; Cong Chen
- Web page: https://patentgrep.com/patent/US20210176245A1

## CPC

- G06F 21/606: {by securing the transmission between two devices or processes}
- H04L 63/0869: {for achieving mutual authentication (cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273)}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 67/133: Protocols for remote procedure calls [RPC]
- H04L 67/306: User profiles
- 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

Systems and methods for efficiently and securely requesting and receiving, from a remote service, data for multiple accounts associated with the same device or application. In one example, a client device is configured to request application data for all accounts associated with the device or application installation using a single remote procedure call, rather than requiring separate calls for each account, and to do so by providing a single identifier rather than including identifiers specific to each associated account. The remote service is further configured to return the requested information in a manner that obfuscates the account identifiers and thus limits their potential use if the communication is intercepted, such that the application data can be efficiently transmitted together even where security or other concerns would otherwise dictate that separate transmissions should be made for each account.

## Claims

### Claim 1

A method of managing requests for account data over a network, comprising:
receiving, by one or more processors of a registry service, a remote procedure call from a client device that includes a first identifier;
identifying, by the one or more processors, from data maintained by the registry service, a plurality of second identifiers corresponding to a plurality of accounts that are associated with the first identifier;
obtaining, by the one or more processors, application data for each of the plurality of accounts from an application backend service;
performing, by the one or more processors, one or more hash functions on each of the plurality of second identifiers to obtain a hash value for each of the plurality of accounts;
reducing, by the one or more processors, each of the hash values to a predefined length to obtain a truncated hash value for each of the plurality of accounts;
generating a data structure by the one or more processors, the data structure comprising an entry for each of the plurality of accounts that associates the truncated hash value for the account with the application data received for the account, and which does not include any of the plurality of second identifiers; and
transmitting the data structure from the registry service to the client device.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
transmitting, from the registry service to the application backend service, a separate remote procedure call for each of the plurality of second identifiers, each separate remote procedure call including only one of the plurality of second identifiers.

### Claim 3 (depends on 1)

The method of claim 1, wherein generating the data structure at the registry service further comprises ordering at least two entries of the data structure based on a sorting of information relating to the accounts represented in the at least two entries of the data structure.

### Claim 4 (depends on 1)

The method of claim 1, wherein generating the data structure at the registry service further comprises ordering at least two entries of the data structure based on the second identifier corresponding to the account represented in each of the at least two entries of the data structure.

### Claim 5 (depends on 1)

The method of claim 1, wherein generating the data structure at the registry service further comprises ordering at least two entries of the data structure based on the hash value corresponding to the account represented in each of the at least two entries of the data structure.

### Claim 6 (depends on 1)

The method of claim 1, wherein the one or more hash functions performed on at least two of the plurality of second identifiers are not the same.

### Claim 7 (depends on 1)

The method of claim 1, wherein the application data within the data structure comprises a number of messages associated with each of the plurality of accounts.

### Claim 8

A method of requesting and receiving account data over a network, comprising:
transmitting, from a client device to a registry service, a remote procedure call that includes a first identifier;
identifying, by one or more processors of the client device, a plurality of second identifiers corresponding to a plurality of accounts that are associated with the first identifier;
performing, by the one or more processors, one or more hash functions on each of the plurality of second identifiers to obtain a hash value for each of the plurality of accounts;
reducing, by the one or more processors, each of the hash values to a predefined length to obtain a truncated hash value for each of the plurality of accounts;
receiving, by the one or more processors, a data structure from the registry service, the data structure comprising an entry for each of the plurality of accounts that associates the truncated hash value for a corresponding account with application data for the corresponding account, and which does not include any of the plurality of second identifiers; and
identifying, by the one or more processors, which application data within the data structure corresponds to each of the plurality of accounts using at least the truncated hash values for each of the plurality of accounts.

### Claim 9 (depends on 8)

The method of claim 8, wherein identifying which application data within the data structure corresponds to each of the plurality of accounts further comprises using the order of at least two of the entries of the data structure.

### Claim 10 (depends on 8)

The method of claim 8, wherein the application data within the data structure comprises a number of messages associated with each of the plurality of accounts.

### Claim 11 (depends on 10)

The method of claim 10, wherein the number of messages associated with each of the plurality of accounts represents a number of unread messages associated with each of the plurality of accounts.

### Claim 12 (depends on 10)

The method of claim 10, wherein the number of messages associated with each of the plurality of accounts represents a number of total messages associated with each of the plurality of accounts.

### Claim 13 (depends on 10)

The method of claim 10, further comprising:
generating, by the one or more processors, an indication on the client device of the number of messages associated with each of the plurality of accounts.

### Claim 14 (depends on 13)

The method of claim 13, wherein the indication comprises one or more of a visible, audible, or tactile indication.

### Claim 15 (depends on 8)

The method of claim 8, wherein the plurality of accounts is associated with a single application installation on the client device.

### Claim 16 (depends on 15)

The method of claim 15, wherein the single application installation is an installation of one of an email application, a social media application, or a banking application.
