US6385693B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Network server platform/facilities management platform caching server
Assignee: AT&T Inc
•
Filing: 1997-12-31
•
Granted: 2002-05-07
•
Expires: 2017-12-31
Abstract
Abstract The location of large caches of memory located at the network server platform can reduce traffic on the network trunks or Internet backbone. In some instances these memory caches might be located at the facilities management platform. Those users supported on a specific network server platform no longer would be required to download regularly used information from the Internet backbone minimizing congestion on the network. These memory caches can be supplemented or refreshed with new data on a regular basis based on the requirements or changing requirements of the users. The close location of regularly accessed data allows for faster downloads and minimizes congestion on the communication network. In addition to user requested information, push information can be stored in these caches for fast downloading to the users.
Inventors
- 👤 Irwin Gerszberg
- 👤 Kenny Xiaojian Huang
- 👤 Christopher K. Kwabi
- 👤 Sumit Roy
- 👤 Gabriel Valdez
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-28 00:25
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/90; G06F16/95; G06F16/957; G06F16/9574
Claims Analysis
Total Claims: 17
Claim 1
Independent Claim
183 words
A network caching system, comprising: a plurality of memory caches connectable to a computer network; a plurality of cache engines connected to said plurality of memory caches and further connectable to said computer network, each said cache engine being configured to receive a request from a user for data stored on a remote source connected to said computer network; wherein each said cache engine is configured to retrieve said data from at least one of said memory caches and transmit said data to said user when said data is stored in one of said memory caches; whereas each said cache engine is configured to transmit a request for said data to said remote source, receive said data from said remote source, store said data in a memory cache, and transmit said data to said user, when said data is not already stored in one of said memory caches; a cache engine controller connected to said plurality of cache engines, said cache engine controller being configured to manage said plurality of cache engines to provide balanced load access to said plurality of cache engines.
Claim 2
Dependent Claim
183 words
A network caching system, comprising: a plurality of memory caches connectable to a computer network; a plurality of cache engines connected to said plurality of memory caches and further connectable to said computer network, each said cache engine being configured to receive a request from a user for data stored on a remote source connected to said computer network; wherein each said cache engine is configured to retrieve said data from at least one of said memory caches and transmit said data to said user when said data is stored in one of said memory caches; whereas each said cache engine is configured to transmit a request for said data to said remote source, receive said data from said remote source, store said data in a memory cache, and transmit said data to said user, when said data is not already stored in one of said memory caches; a cache engine controller connected to said plurality of cache engines, said cache engine controller being configured to manage said plurality of cache engines to provide balanced load access to said plurality of cache engines.
Claim 3
Dependent Claim
23 words
The system of claim 1 , where said cache engines are each configured to enforce user access restrictions imposed by said remote source.
Claim 4
Dependent Claim
49 words
The system of claim 1 , where said cache engines are each configured to retrieve, at the occurrence of a predefined event, a current version of data that is already stored in a respective said memory cache and store said current version of data in said respective memory cache.
Claim 5
Dependent Claim
19 words
The system of claim 3 , where said predefined event is the lapse of a predefined period of time.
Claim 6
Dependent Claim
26 words
The system of claim 3 , where said predefined event is the issuance of a user request to update the content of said respective memory cache.
Claim 7
Dependent Claim
39 words
The system of claim 1 , where said cache engine controller is configured to reallocate traffic loading among said cache engines, whereby responsibilities of a heavily loaded cache engine are reallocated to a relatively less heavily loaded cache engine.
Claim 8
Dependent Claim
31 words
The system of claim 6 , where said cache engine controller is configured to reallocate a traffic load of a failed said cache engine to remaining ones of said cache engines.
Claim 9
Dependent Claim
45 words
The system of claim 1 , where said cache engine controller is configured to maintain a user profile for said user, search said computer network for information relevant to said user profile, and store said relevant information in one or more of said memory caches.
Claim 10
Dependent Claim
17 words
The method of claim 1 , where said memory caches are located within a network server platform.
Claim 11
Dependent Claim
17 words
The method of claim 1 , where said memory caches are located within a facilities management platform.
Claim 12
Dependent Claim
166 words
In a network caching system including a plurality of memory caches connectable to a computer network and a plurality of cache engines connected to said plurality of memory caches and further connectable to said computer network, a method comprising: receiving a request at each said cache engine from a user for data stored on a remote source connected to said computer network; retrieving said data from at least one memory cache; transmitting said data from each said cache engine to said user when said data is stored in one of said memory caches; when said data is not already stored in one of said of memory caches, transmitting a request for said data from each said cache engine to said remote source, receiving said data from said remote source, storing said data in a memory cache, and transmitting said data from each said cache engine to said user; and managing said plurality of cache engines to provide balanced load access to said plurality of cache engines.
Claim 13
Dependent Claim
166 words
In a network caching system including a plurality of memory caches connectable to a computer network and a plurality of cache engines connected to said plurality of memory caches and further connectable to said computer network, a method comprising: receiving a request at each said cache engine from a user for data stored on a remote source connected to said computer network; retrieving said data from at least one memory cache; transmitting said data from each said cache engine to said user when said data is stored in one of said memory caches; when said data is not already stored in one of said of memory caches, transmitting a request for said data from each said cache engine to said remote source, receiving said data from said remote source, storing said data in a memory cache, and transmitting said data from each said cache engine to said user; and managing said plurality of cache engines to provide balanced load access to said plurality of cache engines.
Claim 14
Dependent Claim
17 words
The method of claim 11 , further comprising enforcing user access restrictions imposed by said remote source.
Claim 15
Dependent Claim
43 words
The method of claim 11 , further comprising retrieving, at the occurrence of a predefined event, a current version of data that is already stored in a respective said memory cache and storing said current version of data in said respective memory cache.
Claim 16
Dependent Claim
35 words
The method of claim 11 , wherein said managing includes reallocating traffic loading among said cache engines, wherein responsibilities of a heavily loaded cache engine are reallocated to a relatively less heavily loaded cache engine.
Claim 17
Dependent Claim
27 words
The method of claim 11 , wherein said managing includes reallocating a traffic load of a failed said cache engine among remaining ones of said cache engines.
References Cited (Backward Citations)
US4456925A
Cited
US4620289A
Cited
US4725694A
Cited
US4916441A
Cited
US5561604A
Cited
US5014267A
Cited
US5157717A
Cited
US5572005A
Cited
US5393964A
Cited
US5546316A
Cited
US5587735A
Cited
US5684918A
Cited
US5682195A
Cited
US5335276A
Cited
US5778424A
Cited
US5406615A
Cited
US5644628A
Cited
US5512935A
Cited
US5534913A
Cited
US5488412A
Cited
US5584054A
Cited
US5619684A
Cited
US5583965A
Cited
US5671267A
Cited
US5835943A
Cited
US5925100A
Cited
US5896506A
Cited
US5860158A
Cited
US5987506A
Cited
US5944780A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2005-05-06 | 2005-11-05 | 2006-05-07 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2009-05-06 | 2009-11-05 | 2010-05-07 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2013-05-06 | 2013-11-05 | 2014-05-07 | $7700.00 | Window Closed / Lapsed |