IP Library Granted Patent US 8,805,950
Granted Patent B1
US 8,805,950 · App. 12/026,772 · Granted Aug 12, 2014

Client web cache

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,805,950
App. No.
12/026,772
Granted
Aug 12, 2014
Kind
B1
Abstract

A method and system for improving data access times for a client system located remote from a central server. One example system includes the client system, the central server, and a client web cache located in close geographical proximity to the client system. The central server receives data requests from the client system and retrieves the data from the appropriate data source. The central server also sends the requested data and scripts to the local client web cache for instructing the client web cache to store the cache data. Alternatively, client web cache may have received a prior one-time instruction to cache predetermined types of data. The client web cache receives the data from the central server and based on the scripts or the one-time instruction, and caches the cache data, as instructed. The cache data may then be accessed by the client system.

Claims (40)

1. A method for caching data in a distributed web cache environment including a web cache computer, a central server computer, one or more client systems, and one or more data sources, the method being performed by the central server computer and comprising:

receiving a data request from a client system, the data request requesting data stored at a data source; and

in response to receiving the data request from the client system:

retrieving the requested data from the data source;

identifying data other than the requested data based on a likelihood of the other data being requested in the future by the client system;

retrieving the other data that has a likelihood of being requested in the future by the client system from the one or more data sources;

selecting the web cache computer from among a plurality of available web cache computers such that the distance between the client system and the web cache computer is less than the distance between the web cache computer and the central server computer;

sending, to the client system, the requested data;

sending, to the web cache computer, the other data that has a likelihood of being requested in the future by the client system;

generating a one-time executable script instructing the web cache computer to cache all protected user data of a specified type retrieved from the central server; and

sending the generated executable script from the central server computer to the web cache computer, wherein the web cache computer is intermediate the central server computer and the client system and is remote from the central server computer and from the client system, and the executable script is configured to cause the web cache computer to cache the protected user data of a specified type retrieved from the central server for access by the client system, the specified type comprising at least one of email, calendar data, and address book data.

2. The method as recited in claim 1 , wherein data communication latency between the client system and the intermediate web cache computer is shorter than data communication latency between the client system and the central server computer.

3. A method for storing cache data configured to be accessible by a client system, the method being performed by a web cache computer located in close proximity to a client system and comprising:

receiving a data request from the client system;

sending a request for the data to a central server, the web cache computer being intermediate a central server and the client system, the web cache computer being remote from the central server and remote from the client system;

receiving the requested data from the central server;

receiving data other than the requested data that has a likelihood of being requested in the future by the client system;

receiving executable scripts at the web cache computer from the central server, the executable scripts instructing the web cache computer to store protected user data of a specified type received from the central server for future access by the client system, the specified type comprising at least one of email, calendar data, and address book data; and

storing the protected user data received from the central server in cache, in response to executing the executable scripts received from the central server.

4. The method as recited in claim 3 , further comprising sending the requested data to the client system.

5. A central server computer in a distributed network for storing data at a web cache, the central server computer comprising:

a communication device configured to receive a data request from a client system over the network;

one or more processing modules configured, in response to receiving the data request from the client system, to:

retrieve the requested data from a data source on the network;

identify data other than the requested data based on a likelihood of the other data being requested in the future by the client system;

retrieve the other data that has a likelihood of being requested in the future by the client system;

select a web cache computer from among a plurality of available web cache computers such that the distance between the client system and the web cache computer is less than the distance between the web cache computer and the central server computer;

send, to the client system, the requested data and the other data that has a likelihood of being requested in the future by the client system; and

send executable scripts from the central server computer to the web cache computer to cause the web cache computer to store protected user data of a specified type retrieved from the central server, such that the protected user data is accessible by the client system, the specified type comprising at least one of email, calendar data, and address book data.

6. The central server computer of claim 5 , wherein data communication latency between the client system and the intermediate web cache computer is shorter than data communication latency between the client system and the central server computer.

7. The central server computer of claim 5 , wherein the one or more processing modules are further configured to send the requested data to the client system over the network.

8. A web cache computer within a distributed network, the web cache computer located in close proximity to a client system for storing cache data configured accessible by the client system, the web cache computer comprising:

a communication device for receiving a data request from the client system; and

one or more processing modules configured to:

send a request for the data to a central server, the web cache computer being intermediate the central server and the client system and being remote from the central server and from the client system;

receive the requested data from the central server;

receive data other than the requested data that has a likelihood of being requested in the future by the client system;

receive executable scripts at the web cache computer from the central server, the executable scripts instructing the web cache computer to store protected user data of a specified type retrieved from the central server for future access by the client system, the specified type comprising at least one of email, calendar data, and address book data; and

execute the executable scripts received from the central server to store the protected user data in cache.

9. The web cache computer of claim 8 , wherein the one or more processing units are further configured to send the requested data to the client system.

Assignments (9)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 19, 2021
From: VERIZON MEDIA INC.
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 057453/0431 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2020
From: OATH INC.
To: VERIZON MEDIA INC.
Reel/Frame 054258/0635 →
CHANGE OF NAME Recorded Aug 24, 2017
From: AOL INC.
To: OATH INC.
Reel/Frame 043672/0369 →
RELEASE OF SECURITY INTEREST IN PATENT RIGHTS -RELEASE OF 030936/0011 Recorded Jul 1, 2015
From: JPMORGAN CHASE BANK, N.A.
To: AOL ADVERTISING INC.; AOL INC.; BUYSIGHT, INC.; MAPQUEST, INC.; PICTELA, INC.
Reel/Frame 036042/0053 →
SECURITY AGREEMENT Recorded Aug 2, 2013
From: AOL INC.; AOL ADVERTISING INC.; BUYSIGHT, INC.; MAPQUEST, INC.; PICTELA, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 030936/0011 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS Recorded Nov 16, 2010
From: BANK OF AMERICA, N A
To: AOL INC; AOL ADVERTISING INC; GOING INC; LIGHTNINGCAST LLC; MAPQUEST, INC; NETSCAPE COMMUNICATIONS CORPORATION; QUIGO TECHNOLOGIES LLC; SPHERE SOURCE, INC; TACODA LLC; TRUVEO, INC; YEDDA, INC
Reel/Frame 025323/0416 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 31, 2009
From: AOL LLC
To: AOL INC.
Reel/Frame 023720/0509 →
SECURITY AGREEMENT Recorded Dec 14, 2009
From: AOL INC.; AOL ADVERTISING INC.; BEBO, INC.; ICQ LLC; GOING, INC.; LIGHTNINGCAST LLC; MAPQUEST, INC.; NETSCAPE COMMUNICATIONS CORPORATION; QUIGO TECHNOLOGIES LLC; SPHERE SOURCE, INC.; TACODA LLC; TRUVEO, INC.; YEDDA, INC.
To: BANK OF AMERICAN, N.A. AS COLLATERAL AGENT
Reel/Frame 023649/0061 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 7, 2008
From: LANDSMAN, RICHARD A.; REDDY, SAILU
To: AOL LLC
Reel/Frame 020474/0970 →