Techniques for upstream failure detection and failure recovery

• US 20060075279A1
• Filed: 08/15/2005
• Published: 04/06/2006
• Est. Priority Date: 08/17/2004
• Status: Active Grant

• Current Assignee: Intellectual Ventures I LLC (Intellectual Ventures LLC)
• Original Assignee: Shaw Parsing LLC (Intellectual Ventures LLC)
• Inventors: Albright, Wade, Cameros, Brian
• Granted Patent: US 9,043,635 B2
• Time in Patent Office: Days
• US Class Current: 714/4
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/562 Brokering proxy services
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

The content provider provides content to the first data center, which then provides the content to the client. The client determines that a failure between content provider and the first data center may have occurred. When the client determines that a failure may have occurred, the client may connect to a second data center to receive content from the content provider through the second data center. Accordingly, the failure is detected and additionally, automatic failure recovery may be provided at the client.

Claims

1. A client capable of providing failure recovery, the client comprising:

logic capable of receiving, at the client, an application from a first data center;

logic capable of receiving content from the first data center; and

logic capable of determining, at the client, that a failure occurred between a content provider and the first data center, wherein the content provider is capable of providing content to the first data center,

wherein the application is capable of automatically connecting, at the client, to a second data center to receive content from the second data center in response to determining the failure occurred.

2. The client of claim 1, further comprising logic capable of setting up a status message, wherein the status message is received from the content provider through the first data center at the client, wherein the status message is used to determine the failure.

3. The client of claim 2, wherein the failure is detected when the status message is not received for a certain period of time.

4. The client of claim 1, further comprising:

logic capable of sending a request for information using a first identifier, wherein the request is serviced by the first data center; and

logic capable of receiving a plurality of IP addresses, the IP addresses including global and specific IP addresses, the global IP addresses corresponding to the first identifier and the specific IP addresses corresponding to a second identifier, wherein the application is capable of automatically connecting to the second data center using a specific IP address for the second data center when the failure is determined.

5. The client of claim 4, wherein the application is an unsigned application.

6. A system for failure recovery, the system comprising:

a first data center comprising an application capable of determining a failure occurred between a content provider and the first data center and capable of automatically connecting to a second data center; and

wherein the first data center is capable of;

receiving a connection request from a client;

sending the application to the client in response to the request;

receiving content from the content provider; and

sending the received content to the client.

7. The system of claim 6, wherein the application is capable of determining, at the client, the failure occurred between the content provider and first data center and capable of automatically connecting, at the client, to the second data center to receive content from the second data center in response to determining the failure occurred.

8. The system of claim 6, wherein the application is capable of setting up a status message, wherein the status message is received from the content provider through the data center at the client, wherein the status message is used to determine the failure.

9. The system of claim 8, wherein the failure is detected when the status message is not received for a certain period of time.

10. The system of claim 6, wherein the first data center is further capable of sending a plurality of IP addresses to the client, the IP addresses including global and specific IP addresses, the global IP addresses corresponding to the first identifier and the specific IP addresses corresponding to a second identifier, wherein the application is capable of automatically connecting to the second data center using a specific IP address for the second data center when the failure is determined.

11. The system of claim 10, wherein the first identifier comprises a first URL and the second identifier comprises a second URL.

12. The system of claim 6, wherein the application is an unsigned application.

13. A method for failure recovery, the method comprising:

receiving a connection request from a client at a first data center;

sending an application to the client in response to the request;

receiving content from the content provider at the first data center; and

sending the content from the content provider to the client,

wherein the application is capable of determining, at the client, a failure occurred between the content provider and first data center and to automatically connect, at the client, to a second data center to receive content from the second data center in response to determining the failure occurred.

14. The method of claim 13, wherein the application is capable of setting up a status message, wherein the status message is received from the content provider through the data center at the client, wherein the status message is used to determine the failure.

15. The method of claim 14, wherein the failure is detected when the status message is not received for a certain period of time.

16. The method of claim 13, further comprising:

sending a plurality of IP addresses to the client, the IP addresses including global and specific IP addresses, the global IP addresses corresponding to the first identifier and the specific IP addresses corresponding to a second identifier, wherein the application is capable of automatically connecting to the second data center using a specific IP address for the second data center when the failure is determined.

17. The method of claim 16, wherein the application is an unsigned application.

18. The method of claim 16, wherein the first identifier comprises a first URL and the second identifier comprises a second URL.

19. A system for providing failure recovery, the system comprising:

a first data center capable of processing requests for a first identifier and capable of processing requests for a second identifier specific to the first data center; and

a second data center servers capable of processing requests for the first identifier and capable of processing requests for a third identifier specific to the second data center;

wherein either the first data center or second data center processes a request from a client for information using the first identifier, wherein the first data center or second data center sends an application to the client,

wherein the application capable of determining that a failure occurred between a content provider and the first or second data center that processed the request and to use the second identifier or third identifier, at the client, to automatically connect to the first or second data center that did not process the request when the failure is determined.

20. The system of claim 19, wherein the first data center is associated with a first set of one or more global IP addresses associated with the first identifier and a first set of one or more specific IP addresses associated with the second identifier and the second data center is associated with a second set of one or more global IP addresses associated with the first identifier and a second set of one or more specific IP addresses associated with the third identifier.

21. The system of claim 19, wherein if the first data center processes the request, sending the second set of specific IP addresses with the application to the client and if the second data center processes the request, sending the first set of specific IP addresses with the application to the client.

22. A system capable of providing failure recovery from a first data center, the system comprising:

a second data center capable of;

receiving a connection request from an application of a client, the application being downloaded from the first data center to the client;

allowing the application to connect to the second data center;

receiving content from the content provider; and

sending the content received from the content provider to the client.

23. The system of claim 22, wherein the first data center is associated with a first set of one or more global IP addresses associated with the first identifier and a first set of one or more specific IP addresses associated with the second identifier and the second data center is associated with a second set of one or more global IP addresses associated with the first identifier and a second set of one or more specific IP addresses associated with the third identifier.

24. The system of claim 23, wherein the client is sent the first set of one or more global IP addresses and the second set of specific IP addresses with the application for the first data center.

25. The system of claim 24, wherein the connection request includes one of the second set of specific IP addresses associated with the second data center.