# US 2016/0241667 A1 · Extended http object cache system and method

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

- Number: US 2016/0241667 A1
- Document ID: US20160241667A1
- Status: Published application
- Kind: A1
- Application number: 15/047,594
- Filed: 2016-02-18
- Published: 2016-08-18
- Earliest claimed: 2015-02-18
- Assignees: Actmobile Networks, Inc.
- Applicants: Actmobile Networks, Inc.
- Inventors: Pankaj G. Kulkarni; Phaniraj M. Raghavendra; Rakesh Padinjeredil; Andrew Foss; John Coronella
- Web page: https://patentgrep.com/patent/US20160241667A1

## CPC

- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- G06F 21/606: {by securing the transmission between two devices or processes}
- H04L 63/062: {for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819)}
- H04W 4/18: Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

An Extended Object Cache system for reducing network traffic and methods for making and using the same. The Extended Object Cache system allows caching of HTTP responses where the response headers do not include Etag headers to indicate whether contents of the response have changed, but the contents have not changed. The system allows caching of dynamically generated content as well as static content that does not include an ETag in the response headers.

## Claims

### Claim 1

A method for reducing network traffic between an application and a destination server, comprising:
intercepting a network request from the application via a client proxy;
forwarding the network request to a server proxy;
receiving a network response from the destination server at the server proxy;
determining at the server proxy whether the network response is the same as a cached response at the client proxy; and
transmitting a ‘304 Act Not Modified’ response to the client proxy if the cached response at the client proxy is the same as the network response, otherwise transmitting the network response to the client proxy to transmit the network response to the application.

### Claim 2 (depends on 1)

The method of claim 1, wherein said intercepting the network request comprises intercepting a Hypertext Transfer Protocol request.

### Claim 3 (depends on 1)

The method of claim 1, further comprising computing a hash digest of the network responses to identify if a selected network response has changed.

### Claim 4 (depends on 1)

The method of claim 1, further comprising maintaining a cache of network responses at the client proxy.

### Claim 5 (depends on 4)

The method of claim 4, further comprising adding a Hypertext Transfer Protocol header “X-ActEtag: value” to a selected network response before storing the selected network response in the cache at client proxy.

### Claim 6 (depends on 5)

The method of claim 5, further comprising updating the X-ActEtag header via at least one of the client proxy and the server proxy.

### Claim 7 (depends on 4)

The method of claim 4, wherein said forwarding the network request to the server proxy comprises adding a Hypertext Transfer Protocol header “X-ActEtag: value” to the network request when there is a stale cached response in the cache at the client proxy.

### Claim 8 (depends on 7)

The method of claim 7, further comprising computing a hash digest of the a selected network response and comparing the hash digest with the value from the header “X-ActEtag: value” of the network Request to determine if the cached response at the client is same as the selected network response from the destination server.

### Claim 9 (depends on 1)

The method of claim 1, further comprising fetching the cached response from the cache based on said transmitting the ‘304 Act Not Modified’ response and sending the cached response to the application.

### Claim 10

A method for reducing Hypertext Transfer Protocol traffic between an application and a destination server, comprising:
intercepting a Hypertext Transfer Protocol request from the application via a server proxy;
receiving a Hypertext Transfer Protocol response from the destination server at the server proxy;
determining at the server proxy whether the Hypertext Transfer Protocol response is same as a cached response at the application; and
transmitting a ‘304 Not Modified’ response to the application if the cached response at is the same as the Hypertext Transfer Protocol response, otherwise transmitting the Hypertext Transfer Protocol response to the application.

### Claim 11 (depends on 10)

The method of claim 10, further comprising computing a hash digest of the Hypertext Transfer Protocol response to identify if a selected Hypertext Transfer Protocol response has changed.

### Claim 12 (depends on 11)

The method of claim 11, further comprising adding a Hypertext Transfer Protocol header “Etag: act-hashvalue” to a selected Hypertext Transfer Protocol response before sending the Hypertext Transfer Protocol response to the application.

### Claim 13 (depends on 12)

The method of claim 12, further comprising comparing a hashvalue from the “Etag: act-hashvalue” header with the computed hash digest of the Hypertext Transfer Protocol response from the destination server to determine if the cached response at the application is the same as the Hypertext Transfer Protocol response from the destination server and sending a ‘304 Not Modified’ Hypertext Transfer Protocol response if the hashvalue and the computed hash value of the Hypertext Transfer Protocol response are the same.
