# US 2022/0035744 A1 · Systems and methods for implementing overlapping data caching for object application program interfaces

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

- Number: US 2022/0035744 A1
- Document ID: US20220035744A1
- Status: Published application
- Kind: A1
- Application number: 17/504,407
- Filed: 2021-10-18
- Published: 2022-02-03
- Earliest claimed: 2019-10-28
- Assignees: Intuit Inc.
- Applicants: Intuit Inc.
- Inventors: Philip Edward RUSSELL; Grigoriy E. KESLER; Peter A. VOGEL
- Web page: https://patentgrep.com/patent/US20220035744A1

## CPC

- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 12/0855: Overlapped cache accessing, e.g. pipeline (G06F12/0846 takes precedence)
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 2212/1016: Performance improvement
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods that may be used to implement overlapping data caching for object application program interfaces (APIs). A unique identifier may be assigned to each sub-component of an object API request. The unique identifiers may be used to determine if sub-components of one object API request overlaps with a sub-component of a prior different request such that a data response for the prior different request can be retrieved from the cache and used as part of the data response for the current object API request.

## Claims

### Claim 1

A computer implemented method for implementing an overlapping data cache, said method being performed on a computing device executing an application program interface (API) gateway, said method comprising:
inputting, over a network connection, an object API request from a client device, the object API request comprising a query for data associated with one or more data services in communication with the API gateway;
parsing the object API request into one or more sub-components;
for each sub-component, said method comprises:
determining if the sub-component overlaps with a sub-component of a prior object API request based on one or more secondary cache keys associated with the sub-component and the sub-component of the prior object API request, and data attributes of the sub-component are a subset of data attributes of the sub-component of the prior object API request,
retrieving response data associated with the sub-component of the prior request from the overlapping data cache when it is determined that the sub-component overlaps with the sub-component of the prior object API request, and
initiating a call to a data service of the one or more data service to receive response data associated with the sub-component when it is determined that the sub-component does not overlap with the sub-component of the prior object API request; and
returning to the client device a combined response to the API request, the combined response comprising any retrieved response data from the overlapping data cache and any received response data from the one or more data services.

### Claim 2 (depends on 1)

The method of claim 1, wherein parsing the object API request into one or more sub-components further comprises assigning an object identifier to each sub-component.

### Claim 3 (depends on 2)

The method of claim 2, wherein the object identifier is used as a primary cache key when there is a cache hit based on the object identifier.

### Claim 4 (depends on 2)

The method of claim 2, further comprising creating a cache entry associating the object identifier and the received data response.

### Claim 5 (depends on 1)

The method of claim 1, further comprising creating a cache correlation identifier for the sub-component.

### Claim 6 (depends on 5)

The method of claim 5, further comprising determining whether a data response is a single data response or a compound data response using the cache correlation identifier.

### Claim 7 (depends on 5)

The method of claim 5, further comprising:
determining that a data response is a single data response based on the cache correlation identifier;
creating a primary cache key for the data response; and
storing the primary cache key in the overlapping data cache.

### Claim 8 (depends on 5)

The method of claim 5, further comprising:
determining that a data response is a compound data response based on the cache correlation identifier;
creating one or more secondary cache keys for the data response; and
storing the one or more secondary cache keys in the overlapping data cache.

### Claim 9

A system for implementing an overlapping data cache, said system comprising:
a computing device executing an application program interface (API) gateway, the computing device being in communication with the overlapping data cache and being configured to:
input, over a network connection, an object API request from a client device, the object API request comprising a query for data associated with one or more data services in communication with the API gateway;
parse the object API request into one or more sub-components;
for each sub-component, the computing device is further configured to:
determine if the sub-component overlaps with a sub-component of a prior object API request based on one or more secondary cache keys associated with the sub-component and the sub-component of the prior object API request, and data attributes of the sub-component are a subset of data attributes of the sub-component of the prior object API request,
retrieve response data associated with the sub-component of the prior request from the overlapping data cache when it is determined that the sub-component overlaps with the sub-component of the prior object API request, and
initiate a call to a data service of the one or more data service to receive response data associated with the sub-component when it is determined that the sub-component does not overlap with the sub-component of the prior object API request; and
return to the client device a combined response to the API request, the combined response comprising any retrieved response data from the overlapping data cache and any received response data from the one or more data services.

### Claim 10 (depends on 9)

The system of claim 9, wherein the computing device is configured to parse the object API request into one or more sub-components by assigning an object identifier to each sub-component.

### Claim 11 (depends on 10)

The system of claim 10, wherein the computing device is configured to use the object identifier as a primary cache key when there is a cache hit based on the object identifier.

### Claim 12 (depends on 10)

The system of claim 10, wherein the computing device is configured to create a cache entry associating the object identifier and the received data response.

### Claim 13 (depends on 9)

The system of claim 9, wherein the computing device is configured to create a cache correlation identifier for the sub-component.

### Claim 14 (depends on 13)

The system of claim 13, wherein the computing device is configured to determine whether a data response is a single data response or a compound data response using the cache correlation identifier.

### Claim 15 (depends on 13)

The system of claim 13, wherein the computing device is configured to:
determine that a data response is a single data response based on the cache correlation identifier;
create a primary cache key for the data response; and
store the primary cache key in the overlapping data cache.

### Claim 16 (depends on 13)

The system of claim 13, wherein the computing device is configured to:
determine that a data response is a compound data response based on the cache correlation identifier;
create one or more secondary cache keys for the data response; and
store the one or more secondary cache keys in the overlapping data cache.

### Claim 17

A system for implementing an overlapping data cache, said system comprising:
a computing device executing an application program interface (API) gateway, the computing device being in communication with the overlapping data cache and being configured to:
input, over a network connection, an object API request from a client device, the object API request comprising a query for data associated with one or more data services in communication with the API gateway;
parse the object API request into one or more sub-components;
for each sub-component, the computing device is further configured to:
determine if the sub-component overlaps with a sub-component of a prior object API request by determining that there one or more secondary cache keys associated with the sub-component and the sub-component of the prior object API request that is based on an object identifier assigned to the sub-component and the sub-component of the prior object API request,
retrieve response data associated with the sub-component of the prior request from the overlapping data cache when it is determined that the sub-component overlaps with the sub-component of the prior object API request, and
initiate a call to a data service of the one or more data service to receive response data associated with the sub-component when it is determined that the sub-component does not overlap with the sub-component of the prior object API request; and
return to the client device a combined response to the API request, the combined response comprising any retrieved response data from the overlapping data cache and any received response data from the one or more data services.

### Claim 18 (depends on 17)

The system of claim 17, wherein the computing device is configured to use the object identifier as a primary cache key when there is a cache hit based on the object identifier.

### Claim 19 (depends on 17)

The system of claim 17, wherein the computing device is configured to create a cache entry associating the object identifier and the received data response.

### Claim 20 (depends on 17)

The system of claim 17, wherein the computing device is configured to create a cache correlation identifier for the sub-component.
