IP Library Patent Application 13020762
Patent Application
App. No. 13/020,762

REDIRECTING CONTENT REQUESTS

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 None
App. No.
13/020,762
Abstract

Various techniques for redirecting content requests are disclosed. In some embodiments, in response to receiving a request for content published by a publisher from a client at a redirect host configured to implement a content delivery policy for the publisher, it is determined based on the content delivery policy whether to select a publisher server for servicing the request. In the event that a determination is made not to select a publisher server for servicing the request, the client or request is redirected to a content delivery network. In the event that a determination is made to select a publisher server for servicing the request, the client or request is redirected to the selected publisher server.

Claims (30)

1 . A method for redirecting a content request, comprising:

receiving at a redirect host a request, from a client, for content published by a publisher, wherein the redirect host is configured to implement a content delivery policy for the publisher;

determining, by the redirect host, based on the content delivery policy whether to select any of one or more publisher servers for servicing the request; and

in the event that a determination is made not to select any of the one or more publisher servers for servicing the request, redirecting the client or the request to a content delivery network.

2 . The method of claim 1 , further comprising: in the event that a determination is made to select a publisher server of the one or more publisher servers for servicing the request, redirecting the client or request to the selected publisher server.

3 . The method of claim 1 , wherein determining whether to select a publisher server of the one or more publisher servers for servicing the request is based on one or more of: the requested content, the requesting client, availability of the publisher server to service the request, geography, load balancing, and cache locality of the requested content.

4 . The method of claim 2 , wherein the selected publisher server comprises an internal server of a private network of the publisher.

5 . The method of claim 2 , wherein the selected publisher server is accessible via an external network or a public network.

6 . The method of claim 2 , wherein the selected publisher server comprises an origin server to which the requested content was originally published.

7 . The method of claim 2 , wherein the selected publisher server is part of a data center or a server farm.

8 . The method of claim 1 , further comprising determining to select a publisher server of the one or more publisher servers for servicing the request in the event that the publisher server has the capability to service the request.

9 - 16 . (canceled)

17 . A system for redirecting a content request, comprising:

a processor configured to:

receive a request, from a client, for content published by a publisher, wherein the processor is configured to implement a content delivery policy for the publisher;

determine based on the content delivery policy whether to select any of one or more publisher servers for servicing the request; and

in the event that a determination is made not to select any of the one or more publisher servers for servicing the request, redirect the client or request to a content delivery network; and

a memory coupled to the processor and configured to provide the processor with instructions.

18 . The system of claim 17 , wherein in the event that a determination is made to select a publisher server of the one or more publisher servers for servicing the request, the processor is further configured to redirect the client or request to the selected publisher server.

19 . The system of claim 18 , wherein the selected publisher server comprises an internal server of a private network of the publisher.

20 . The system of claim 18 , wherein the selected publisher server is accessible via an external network or a public network.

21 . (canceled)

22 . A computer program product for redirecting a content request, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a request, from a client, for content published by a publisher, wherein the computer program product is configured to implement a content delivery policy for the publisher;

determining based on the content delivery policy whether to select any of one or more publisher servers for servicing the request; and

in the event that a determination is made not to select any of the one or more publisher servers for servicing the request, redirecting the client or request to a content delivery network.

23 . The computer program product of claim 22 , wherein in the event that a determination is made to select a publisher server of the one or more publisher servers for servicing the request, further comprising computer instruction for redirecting the client or request to the selected publisher server.

24 . The computer program product of claim 23 , wherein the selected publisher server comprises an internal server of a private network of the publisher.

25 . The computer program product of claim 23 , wherein the selected publisher server is accessible via an external network or a public network.

26 . (canceled)

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 12, 2012
From: XDN, INC.
To: FORTINET, INC.
Reel/Frame 029458/0126 →
CHANGE OF NAME Recorded Dec 12, 2012
From: 3CROWD TECHNOLOGIES, INC.
To: XDN, INC.
Reel/Frame 029458/0205 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 18, 2011
From: LYON, BARRETT GIBSON
To: 3CROWD TECHNOLOGIES, INC.
Reel/Frame 026145/0760 →