# US 2013/0254342 A1 · Method and system for edge server cache

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

- Number: US 2013/0254342 A1
- Document ID: US20130254342A1
- Status: Published application
- Kind: A1
- Application number: 13/430,044
- Filed: 2012-03-26
- Published: 2013-09-26
- Earliest claimed: 2012-03-26
- Assignees: Yahoo! Inc.
- Inventors: Shu Kit Francis Chan
- Web page: https://patentgrep.com/patent/US20130254342A1

## CPC

- G06F 16/9574: {of access to content, e.g. by caching}
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for fault tolerant content delivery. A request is received from a user for customized content on the network, the request for customized content comprising an identifier for the content and identification information. The request is forwarded from the user for the customized content over the network. Generic content corresponding to the customized content is stored in a cache for future use. The generic content is sent to the user if no customized content is received in response to the forwarded request from the user.

## Claims

### Claim 1

A method implemented on a machine having at least one processor, storage, and a communication platform connected to a network for fault tolerant content delivery, comprising:
receiving a request from a user for customized content on the network, the request for customized content comprising an identifier for the content and identification information;
forwarding the request from the user for the customized content over the network;
storing generic content corresponding to the customized content in a cache for future use; and
sending the generic content as a response to the request if no customized content is received in response to the forwarded request from the user.

### Claim 2 (depends on 1)

The method of claim 1, wherein if an error message is received in response to the forwarded request from the user:
retrieving generic content corresponding to the customized content from the cache; and
sending the generic content to the user.

### Claim 3 (depends on 1)

The method of claim 1, further comprising determining if the generic content is in the cache in response to receiving the request from the user for the customized content.

### Claim 4 (depends on 3)

The method of claim 3, further comprising if the generic content is not in the cache, requesting the generic content from a content server, and storing the generic content in the cache.

### Claim 5 (depends on 4)

The method of claim 4, wherein requesting the generic content from the content server comprises:
removing the identification information from the request from the user to form a generic request; and
sending the generic request over the network.

### Claim 6

A method implemented on a machine having at least one processor, storage, and a communication platform connected to a first network for fault tolerant content delivery, comprising:
receiving a request from a user for customized content via the first network, the request for customized content comprising an identifier for the content and identification information;
forwarding the request from the user for the customized content via a second network;
storing generic content corresponding to the customized content in a cache for future use; and
sending the generic content as a response to the request if no customized content is received from the second network in response to the forwarded request for the customized content.

### Claim 7 (depends on 6)

The method of claim 6, wherein if an error message is received in response to the forwarded request from the user:
retrieving generic content corresponding to the customized content from the cache; and
sending the generic content to the user on the first network.

### Claim 8 (depends on 6)

The method of claim 6, further comprising determining if the generic content is in the cache in response to receiving the request from the user for the customized content.

### Claim 9 (depends on 8)

The method of claim 8, further comprising if the generic content is not in the cache, requesting the generic content on the second network, and storing the generic content in the cache.

### Claim 10 (depends on 9)

The method of claim 9, wherein requesting the generic content comprises:
removing the identification information from the request from the user to form a generic request; and
sending the generic request on the second network.

### Claim 11

A machine-readable tangible and non-transitory medium having information recorded thereon, wherein the information, when read by a machine, causes the machine to perform a fault tolerant content delivery method, the method compromising:
receiving, by a first server, a request from a user for customized content on a network, the request for customized content comprising an identifier for the content and identification information;
forwarding the request from the user for the customized content to a second server on the network; and
storing, by the first server, generic content corresponding to the customized content in a cache for future use; and
sending the generic content as a response to the request if no customized content is received in response to the forwarded request.

### Claim 12 (depends on 11)

The machine-readable medium of claim 11, wherein if an error message is received in response to the forwarded request from the user:
retrieving generic content corresponding to the customized content from the cache; and
sending the generic content to the user.

### Claim 13 (depends on 11)

The machine-readable medium of claim 11, further comprising determining if the generic content is in the cache in response to receiving the request from the user for the customized content.

### Claim 14 (depends on 13)

The machine-readable medium of claim 13, further comprising if the generic content is not in the cache, requesting the generic content from the content server, and storing the generic content in the cache.

### Claim 15 (depends on 14)

The machine-readable medium of claim 14, wherein requesting the generic content from the content server comprises:
removing the identification information from the request from the user to form a generic request; and
sending the generic request over the network.

### Claim 16

A system for reliable content delivery comprising:
a receiver configured for receiving a request from a user, over a network for customized content;
a cache configured for storing a first set of generic content;
a cached content determining unit configured for determining whether generic content corresponding to the requested customized content is a part of the first set of generic content; and
a content delivery unit configured for transmitting content to the user, wherein the content transmitted to the user corresponds to the generic content corresponding to the requested customized content if no customized content is received and the generic content corresponding to the requested customized content is cached in the cache.

### Claim 17 (depends on 16)

The system according to claim 16, further comprising a content requesting unit configured to request the generic content if the cached content determining unit that determines that the generic content corresponding to the requested customized content is missing from the first set of generic content.

### Claim 18 (depends on 17)

The system according to claim 17, further comprising:
a generic content database comprising a second set of generic content; and
a content builder unit configured to build at least one of generic content or requested customized content based on a request from the content requesting unit for customized content and the second set of generic content.

### Claim 19 (depends on 18)

The system according to claim 18, wherein the content builder unit is configured to build the customized content if the content builder unit receives a request for content that includes at least one of user identification information, device identification information, or application identification information.

### Claim 20 (depends on 18)

The system according to claim 18, wherein the content builder unit is configured to build the generic content if the content builder unit receives a request for content that includes no identification information.
