# US 2011/0238828 A1 · Redirecting web content

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

- Number: US 2011/0238828 A1
- Document ID: US20110238828A1
- Status: Published application
- Kind: A1
- Application number: 13/156,152
- Filed: 2011-06-08
- Published: 2011-09-29
- Earliest claimed: 2008-07-23
- Assignees: International Business Machines Corporation
- Inventors: Travis M. Grigsby; Thomas J. Freund; Albert A. Lamb; Lee M. Surprenant
- Web page: https://patentgrep.com/patent/US20110238828A1

## CPC

- H04L 67/104: Peer-to-peer [P2P] networks
- G06F 15/173: using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/1012: based on compliance of requirements or conditions with available server resources
- H04L 67/1085: {involving dynamic management of active down- or uploading connections}
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- G06F 15/16: Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs {(coordinating program control therefor G06F9/52; in regulating and control system G05B)}
- H04L 67/1023: based on a hash applied to IP addresses or costs
- H04L 67/288: Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
- 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)

## Abstract

A peer group can be established for sharing Web cache data among a set of computing devices through a peer-to-peer network. The Web cache data can be used by each of the computing devices to respond to requests issued over a client-server network from a Web browser running on that computing device. Web cache data can be exchanged among the peers of the peer group via the peer-to-peer network. A client request issued from a Web browser of one of the computing devices can be satisfied using Web cache data obtained from a different one of the computing devices in the peer group. The client request can be a request to one of the Web servers for Web content. The server associated with the request may never provide the Web content responsive to the client request, which is obtained instead from the different one of the computing devices.

## Claims

### Claim 1

A method comprising:
establishing a peer group for sharing Web cache data among a set of computing devices through a peer-to-peer network, where each of the computing devices is referred to a peer of the peer-to-peer network, where the Web cache data is used by each of the computing devices to respond to requests issued over a client-server network from a Web browser running on that computing device, wherein each of said requests are issued from the computing devices to the Web servers using a client-server protocol;
exchanging Web cache data among the peers of the peer group via the peer-to-peer network; and
satisfying a client request issued from a Web browser of one of the computing devices using Web cache data obtained from a different one of the computing devices in the peer group through the peer-to-peer network, wherein the client request is a request to one of the Web servers for Web content, and wherein the server associated with the request never provides the Web content responsive to the client request, which is obtained instead from the different one of the computing devices.

### Claim 2 (depends on 1)

The method of claim 1, wherein the client request is one of a Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS) request, and wherein the different one of the computing devices is not referenced or explicitly indicated in the client request.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
determining whether bandwidth constraints prevent the Web server from being not capable of reasonably satisfying current requests, which include the client request, without exhibiting degraded performance;
when the bandwidth capabilities of a connection between the computing device and the Web server are not capable of reasonably satisfying current requests, which include the client request, without exhibiting degraded performance, responding to the client requests using Web cache data that is saved in a repository of one of the computing devices and not responding to the client requests using data from the Web server; and
when the bandwidth capabilities of a connection between the computing device and the Web server are capable of reasonably satisfying current requests, which include the client request, without exhibiting degraded performance, responding to the client requests using data from the Web server.

### Claim 4 (depends on 1)

The method of claim 1, wherein the client request is satisfied without the Web server ever receiving the request.

### Claim 5 (depends on 1)

The method of claim 1, wherein the client request is satisfied by the Web server redirecting the client to the different one of the computing devices.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
indexing at a centralized peer-to-peer server, Web content data available within of the peer group via the peer-to-peer network;
the peer-to-peer server receiving the client request and responsively querying the Web content data capable of satisfying the client request;
when Web content data capable of satisfying the request is discovered by the peer-to-peer server, directing the client request to the different one of the computing devices, which is a computing device that the peer-to-peer server has determined is sharing the Web content data capable of satisfying the request; and
when Web content data capable of satisfying the request is not discovered by the peer-to-peer server, directing the client request to the Web server.

### Claim 7 (depends on 1)

The method of claim 1, wherein the Web cache data that satisfies the client request comprises advertising that has been inserted into the Web cache data by a node of the peer-to-peer network, wherein the Web server that originally provided the Web cache data to one of the computing devices of the peer-to-peer network did not authorize or insert the advertising.

### Claim 8 (depends on 1)

The method of claim 1, wherein the Web server is not a peer of the peer-to-peer network, and wherein the peer-to-peer network is an unstructured network lacking a centralized server.

### Claim 9

A method comprising:
monitoring one or more downloads of Web content from one or more Web content servers, wherein each of the one or more downloads occurs via a client-server request from a Web browser of one of a set of at least two client computing devices and via receiving a corresponding response from one of the Web content servers;
tracking a storage of the one or more downloads of the Web content within Web browser caches of the a set of client computing devices;
establishing a peer group of a peer-to-peer network, which includes the set of client computing devices;
exchanging Web content of the Web browser caches among the set of client computing devices via the peer-to-peer network; and
satisfying download requests directed to the Web content servers utilizing Web content obtained from the Web browser caches via the peer-to-peer network, wherein each of the download requests is a client-server request from one of the computing devices to one of the Web content servers.

### Claim 10 (depends on 9)

The method of claim 9, wherein the Web content servers are peers of the peer-to-peer network, and wherein the Web content servers selectively redirect download requests from issued via a client-server message to Web content able to be obtained from the Web browser caches via the peer-to-peer network.

### Claim 11 (depends on 9)

The method of claim 9, wherein the Web content servers are not peers of the peer-to-peer network, and wherein the Web content servers never receive download requests issued from the computing devices that are satisfied utilizing Web content obtained from the Web browser caches via the peer-to-peer network.

### Claim 12 (depends on 9)

The method of claim 9, wherein the satisfied download requests are each a Hypertext Transfer Protocol (HTTP) or a Hypertext Transfer Protocol Secure (HTTPS) request, and wherein for each of the download requests the computing device that provided the Web content that satisfied the download requests is not referenced or explicitly indicated in the client request.

### Claim 13

The method comprising:
maintaining a Web content cache at a client device, which comprises cached data from Web browser activities performed between the client device and a set of Web servers, wherein the cached data is able to be utilized by the Web browser to respond to subsequent Web browser requests issued to one of the set of Web servers without having to obtain new data from any of the Web servers, as the subsequent responses are able to be handled by retrieving cached data from the Web content cache;
establishing a peer group of a peer-to-peer network, which includes the client device and a set of remotely located client devices;
sending at least a portion of the cached data from the client device to at least one of the remotely located client devices via the peer-to-peer network, wherein the remotely located client devices are able to utilize the cached data to handle Web browser requests issued from these remotely located client devices to the Web servers without having to obtain new data from any of the Web servers; and
receiving peer-shared cached data from the remotely located client devices via the peer-to-peer network, wherein the peer-shared cached data is able to be utilized by the Web browser to respond to subsequent Web browser requests issued to one of the set of Web servers without having to obtain new data from any of the Web servers.

### Claim 14 (depends on 13)

The method of claim 13, wherein the cached data of the Web content cache is continuously being updated responsive to Web browser activities performed between the client device and the set of Web servers.

### Claim 15 (depends on 13)

The method of claim 13, wherein peer-shared cached data provided to the computing device from the remotely located client devices via the peer-to-peer network is continuously being updated responsive to Web browsing activities performed on any of the remotely located client devices.

### Claim 16 (depends on 13)

The method of claim 13, wherein each of the subsequent Web browser requests are Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS) requests.

### Claim 17 (depends on 13)

A method of claim 13, wherein the peer-shared cached data comprises advertisements that were not inserted or authorized by any of the set of Web servers.

### Claim 18

A computer program product comprising:
a computer usable medium having computer usable program code embodied therewith, the computer usable program code comprising:
computer usable program code configured to establish a peer group for sharing Web cache data among a set of computing devices through a peer-to-peer network, where each of the computing devices is referred to as a peer of the peer-to-peer network, where the Web cache data is used by each of the computing devices to respond to requests issued over a client-server network from a Web browser running on that computing devices, wherein each of said requests are issued from the computing devices to Web servers using a client-server protocol;
computer usable program code configured to exchange Web cache data among the peers of the peer group via the peer-to-peer network; and
computer usable program code configured to satisfy client request issued from a Web browser of one of the computing devices using Web cache data obtained from a different one of the computing devices in the peer group through the peer-to-peer network, wherein the client request is a request to one of the Web servers for Web content, and wherein the server associated with the request never provides the Web content responsive to the client request, which is obtained instead from the different one of the computing devices.

### Claim 19 (depends on 18)

The computer program product of claim 18, wherein the client request is one of a Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS) request, and wherein the different one of the computing devices is not referenced or explicitly indicated in the client request.

### Claim 20 (depends on 18)

The computer program product of claim 18, further comprising:
computer usable program code configured to determine whether bandwidth constraints prevent the Web server from being not capable of reasonably satisfying current requests, which include the client request, without exhibiting degraded performance;
computer usable program code configured to, when the bandwidth capabilities of a connection between the computing device and the Web server are not capable of reasonably satisfying current requests, which include the client request, without exhibiting degraded performance, respond to the client requests using Web cache data that is saved in a repository of one of the computing devices and not responding to the client requests using data from the Web server; and
computer usable program code configured to, when the bandwidth capabilities of a connection between the computing device and the Web server are capable of reasonably satisfying current requests, which include the client request, without exhibiting degraded performance, respond to the client requests using data from the Web server.

### Claim 21 (depends on 18)

The computer program product of claim 18, further comprising:
computer usable program code configured to index at a centralized peer-to-peer server, Web content data available within of the peer group via the peer-to-peer network;
computer usable program code configured to, at the peer-to-peer server, receive the client request and responsively querying the Web content data capable of satisfying the client request;
computer usable program code configured to, when Web content data capable of satisfying the request is discovered by the peer-to-peer server, direct the client request to the different one of the computing devices, which is a computing device that the peer-to-peer server has determined is sharing the Web content data capable of satisfying the request; and
computer usable program code configured to, when Web content data capable of satisfying the request is not discovered by the peer-to-peer server, direct the client request to the Web server.

### Claim 22

A computer program product comprising:
a computer usable medium having computer usable program code embodied therewith, the computer usable program code comprising:
computer usable program code configured to monitor one or more downloads of Web content from one or more Web content servers, wherein each of the one or more downloads occurs via a client-server request from a Web browser of one of a set of at least two client computing devices and via receiving a corresponding response from one of the Web content servers;
computer usable program code configured to track a storage of the one or more downloads of the Web content within Web browser caches of the a set of client computing devices;
computer usable program code configured to establish a peer group of a peer-to-peer network, which includes the set of client computing devices;
computer usable program code configured to exchange Web content of the Web browser caches among the set of client computing devices via the peer-to-peer network; and
computer usable program code configured to satisfy download requests directed to the Web content servers utilizing Web content obtained from the Web browser caches via the peer-to-peer network, wherein each of the download requests is a client-server request from one of the computing devices to one of the Web content servers.

### Claim 23 (depends on 22)

The computer program product of claim 22, wherein the Web content servers are peers of the peer-to-peer network, and wherein the Web content servers selectively redirect download requests from issued via a client-server message to Web content able to be obtained from the Web browser caches via the peer-to-peer network.

### Claim 24 (depends on 22)

The computer program product of claim 22, wherein the Web content servers are not peers of the peer-to-peer network, and wherein the Web content servers never receive download requests issued from the computing devices that are satisfied utilizing Web content obtained from the Web browser caches via the peer-to-peer network.

### Claim 25 (depends on 22)

The computer program product of claim 22, wherein the satisfied download requests are each a Hypertext Transfer Protocol (HTTP) or a Hypertext Transfer Protocol Secure (HTTPS) request, and wherein for each of the download requests the computing device that provided the Web content that satisfied the download requests is not referenced or explicitly indicated in the client request.
