# US 2015/0106827 A1 · Rpc acceleration based on previously memorized flows

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

- Number: US 2015/0106827 A1
- Document ID: US20150106827A1
- Status: Published application
- Kind: A1
- Application number: 14/055,463
- Filed: 2013-10-16
- Published: 2015-04-16
- Earliest claimed: 2013-10-16
- Assignees: Google Inc.
- Applicants: Google Inc.
- Inventors: Noah FIEDEL; Jeremy NELSON
- Web page: https://patentgrep.com/patent/US20150106827A1

## CPC

- G06F 9/4843: {by program, e.g. task dispatcher, supervisor, operating system}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques for acceleration of remote procedure calls are disclosed. Such techniques include steps of receiving a content request, the content request including at least one data request for information from a database; analyzing the received content request; and determining whether the analyzed content request includes at least one data request that can be separately executed in parallel with execution of the received content request. In response to a determination that at least one data request that can be separately executed in parallel, initiating the execution of the parallel data request; receiving the requested data in response to that data request; locally storing the received requested data; and providing the stored received requested data in response to execution of the received content request.

## Claims

### Claim 1

A system comprising:
a processor;
a processor-readable memory having stored therein instructions that cause the processor to perform a method comprising the steps of:
receiving a content request, the content request including at least one data request for information from a database;
analyzing the received content request;
determining whether the analyzed content request includes at least one data request that can be separately executed in parallel with execution of the received content request;
in response to a determination that the received content request includes at least one data request that can be separately executed in parallel with the received content request, initiating the execution of said at least one data request in parallel with execution of the received content request, said executing including sending said at least one data request to at least one database for execution;
receiving requested data from said at least one database in response to said at least one data request;
locally storing the received requested data; and
providing the stored received requested data in response to said execution of the received content request.

### Claim 2 (depends on 1)

The system of claim 1, the content request including two or more data requests for information from one or more databases, said two or more data requests including a first data request and a second data request; and
said initiating the execution including initiating the execution of the first data requests in parallel with the second data request and in parallel with the received content request.

### Claim 3 (depends on 2)

The system of claim 2, said receiving requested data including receiving requested data in response to the first data request and receiving requested data in response to the second data request.

### Claim 4 (depends on 1)

The system of claim 1, the step of sending at least one data request to at least one database for execution including sending said at least one data request to a data center.

### Claim 5 (depends on 1)

The system of claim 1, the step of analyzing including identifying all data requests included in the received content request; and
the step of determining including determining whether the identified data requests match a known or previously executed set of data requests associated with a known or previously executed content request.

### Claim 6 (depends on 1)

The system of claim 1, the step of analyzing including determining whether the received content request is substantially the same as a previously-executed received content request; and
in response to a determination that the received content request is substantially the same as a previously-executed received content request,
determining that the received content request includes at least one data request that can be separately executed in parallel with the received content request,
and initiating the execution of those data requests associated with the previously-executed received content request in parallel with execution of the received content request.

### Claim 7 (depends on 1)

The system of claim 1, said analyzing including generating request signature based on the received content request; and
said determining including comparing the generated request signature to one or more known or previously-generated request signatures, the known or previously-generated request signatures each being associated with a set of one or more known or previously-executed data requests.

### Claim 8 (depends on 7)

The system of claim 7, where the received content request includes information about an application originating the content request; and
where the request signature is generated based on the information about the application originating the content request.

### Claim 9 (depends on 1)

The system of claim 1, the step of determining including comparing a result of said analyzing against one or more known or previous analysis results, each of said known or previous analysis results being associated with a set of one or more previously-executed data requests.

### Claim 10 (depends on 9)

The system of claim 9, where the known or previous analysis results are stored in said processor-readable memory.

### Claim 11

A method comprising:
receiving a content request from a data access device, the content request including at least one data request for information from a database;
generating a request signature from the received content request, the request signature uniquely identifying said at least one data request included in the received content request;
comparing the generated request signature to at least one known request signature, said known request signature being associated with at least one known data request;
in response to a determination that the generated request signature matches the known request signature, initiating the execution of said at least one known data request in parallel with execution of the received content request, said executing including sending said at least one known data request to at least one database for execution;
receiving requested data from said at least one database in response to said at least one known data request;
storing the received requested data in a processor-readable memory; and
providing the stored received requested data in response to said execution of the received content request.

### Claim 12 (depends on 11)

The method of claim 11, the content request including two or more data requests for information from one or more databases, said two or more data requests including a first data request and a second data request; and
said initiating the execution including initiating the execution of the first data requests in parallel with the second data request and in parallel with the received content request.

### Claim 13 (depends on 12)

The method of claim 12, said receiving requested data including receiving requested data in response to the first data request and receiving requested data in response to the second data request.

### Claim 14 (depends on 11)

The method of claim 11, the step of sending at least one data request to at least one database for execution including sending said at least one data request to a data center.

### Claim 15 (depends on 11)

The method of claim 11, the generated request signature identifying all data requests included in the received content request; and
the step of comparing including determining whether the identified data requests match a known or previously executed set of data requests associated with a known request signature.

### Claim 16 (depends on 11)

The method of claim 11, the step of comparing including determining whether the generated request signature is substantially the same as a previously-generated request signature; and
in response to a determination that the generated request signature is substantially the same as a previously-generated request signature, initiating the execution of those data requests associated with the previously-generated request signature in parallel with execution of the received content request.

### Claim 17 (depends on 16)

The method of claim 16, the step of comparing further comprising:
comparing the generated request signature to one or more known or previously-generated request signatures, the known or previously-generated request signatures each being associated with a set of one or more known or previously-executed data requests.

### Claim 18 (depends on 17)

The method of claim 17, where the received content request includes information about an application originating the content request; and
where the request signature is generated based on the information about the application originating the content request.

### Claim 19 (depends on 11)

The method of claim 11, the step of comparing including comparing the generated request signature against one or more known or previously-generated request signatures, each of said known or previously-generated request signatures being associated with a set of one or more previously-executed data requests.

### Claim 20 (depends on 19)

The method of claim 19, where the known or previously-generated request signatures are stored in said processor-readable memory.

### Claim 21

A system comprising:
a processor;
a processor-readable memory having stored therein instructions that cause the processor to perform a method comprising the steps of:
receiving a request for content from a requesting entity;
generating a request fingerprint based on the received request for content;
first determining whether the generated request fingerprint matches a stored request fingerprint;
in response to a determination that the generated request fingerprint matches the stored request fingerprint, initiating the remote procedure calls associated with that stored request fingerprint in parallel;
serially executing remote procedure calls associated with the received request after said first determining step, said serially executing including, for each of the remote procedure calls being serially executed
attaching a result stub to the remote procedure call, the result stub representing a placeholder for a result of one of the remote procedure calls executed in parallel;
determining whether said one of the remote procedure calls executed in parallel has completed execution;
in response to a determination that said one of the remote procedure calls executed in parallel has completed execution, returning a result of said one of the remote procedure calls executed in parallel has completed execution to the result stub; and
in response to a determination that said one of the remote procedure calls executed in parallel has not completed execution, suspending serial execution of the remote procedure call until said one of the remote procedure calls executed in parallel has completed execution and returning a result of the completed one of the remote procedure calls executed in parallel to the result stub; and
in response to all of said serially executed remote procedure calls having a result, returning a request result to the requesting entity based on the remote procedure call results.
