Multi-level redirection system

• US 20060288119A1
• Filed: 01/26/2006
• Published: 12/21/2006
• Est. Priority Date: 06/15/2005
• Status: Active Grant

• Current Assignee: Hostway Corporation (Hosting.com, Inc.)
• Original Assignee: Hostway Corporation (Hosting.com, Inc.)
• Inventors: Kim, Jooyong, Yi, Sukwon, Abate, Jason Michael
• Granted Patent: US 7,647,424 B2
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

In a multi-level redirection method, a first level redirection of a first request is performed based on static information. At a manager, a second level redirection of a second request is performed to an agent server based on dynamic information. The manager is configured to monitor an individual status of the agent server. The static information is associated with selection of the manager and the dynamic information is associated with selection of the agent server. The second level redirection is application redirection performed based on application protocols and contents used in the first and second request.

Claims

1. A multi-level redirection method, comprising:

performing a first level redirection of a first request to a manager based on static information; and

at the manager, performing a second level redirection of a second request to an agent server based on dynamic information, the manager configured to monitor an individual status of the agent server; and

wherein the static information is associated with selection of the manager and the dynamic information is associated with selection of the agent server.

2. The multi-level redirection method of claim 1, wherein performing the first level redirection comprises redirecting to the manager a base page in response to the first request.

3. The multi-level redirection method of claim 2, wherein redirecting to the manager the base page comprises determining that the base page is cached at the manager.

4. The multi-level redirection method of claim 3, further comprising at the manager, sending a proxy request to the first server upon determination that the base page is not cached at the manager.

5. The multi-level redirection method of claim 2, wherein performing the second level redirection comprises redirecting to the agent server at least one embedded objects in response to the second request.

6. The multi-level redirection method of claim 5, further comprising at the manager, monitoring and evaluating the dynamic information relevant to the agent server on a real-time basis.

7. The multi-level redirection method of claim 1, wherein performing the first level redirection comprises providing an internet protocol (IP) address of the manager to a client.

8. The multi-level redirection method of claim 7, further comprising locating the manager proximate a location of the client.

9. The multi-level redirection method of claim 1, wherein the second level redirection is application redirection performed based on application protocols and contents used in the first and second requests.

10. The multi-level redirection method of claim 9, wherein performing the second level redirection comprises modifying a uniform resource locator (URL) of the embedded object to include a name of the agent server.

11. The multi-level redirection method of claim 1, wherein the first request and the second request are configured to request the identical object.

12. A multi-level redirection system, comprising:

a plurality of managers receiving a first request redirected with a first level redirection and performing a second level redirection of a second request; and

a plurality of cache servers supplying a response corresponding to the second request redirected with the second level redirection wherein each manager is associated with a group of the cache servers for monitoring and selecting the cache servers; and

wherein the first level redirection is associated with global information and the second level redirection is associated with local information.

13. The multi-level redirection system of claim 12, wherein one of the plurality of managers is located based on the global information.

14. The multi-level redirection system of claim 13, wherein the global information includes legal restriction on content service.

15. The multi-level redirection system of claim 12, wherein the first request and the second request are configured to request an identical object.

16. The multi-level redirection system of claim 15, wherein the first request and the second request comprise a request for an embedded object.

17. The multi-level redirection system of claim 12, wherein a manager is associated with a cache server group including multiple assigned cache servers and the manager monitors a live status of the cache server group.

18. The multi-level redirection system of claim 17, wherein the manager selects a best cache server within the cache server group based on the live status of the cache server group.

19. The multi-level redirection system of claim 12, wherein the first level redirection comprises redirection of a base page and the second level redirection comprises redirection of an embedded object.

20. The multi-level redirection system of claim 12, wherein the first request and the second request comprise a request for location of an object in a peer of a peer-to-peer (P2P) network.

21. The multi-level redirection system of claim 12, wherein at least one of the first request or the second request comprise a request for borrowing processing capacity of the cache servers.

22. The multi-level redirection system of claim 12, wherein the first level redirection is based on static information and the second level redirection is based on dynamic information, the dynamic information configured to change on a real-time basis and be more time-variant than the static information.

23. The multi-level redirection system of claim 12, wherein the plurality of cache servers comprises a plurality of supernode servers that operates as a contact point in a P2P network.

24. The multi-level redirection system of claim 12, wherein the second level redirection is an application redirection performed based on application protocols and contents used in the first and second requests.

25. A multi-level redirection system, comprising:

means for performing a first level redirection of a first request based on static information;

means for performing a second level redirection of a second request based on dynamic information; and

means for performing a third level redirection of the second request based on location of an object requested by the second request.

26. The multi-level redirection system of claim 25, further comprising means for performing an N level redirection of the second request upon determination that no content is found as a result of the third level redirection of the second request, N being a natural number greater than 3.

27. The multi-level redirection system of claim 25, wherein the first level redirection means comprises one of an origin server, a cooperative server and a domain name system (DNS) server, and the second level redirection means comprises a manager.

28. The multi-level redirection system of claim 27, wherein the third level redirection means comprises a plurality of cache servers associated with the manager.

29. The multi-level redirection system of claim 28, wherein the cache servers comprise at least one of a plurality of supernode servers or a plurality of user machines.

30. The multi-level redirection system of claim 25, wherein the second level redirection and the third level redirection are configured to be application redirection performed based on application protocols and contents used in the first and second requests.

31. The multi-level redirection system of claim 25, wherein the second level redirection means provides a response to the first request.

32. The multi-level redirection system of claim 25, wherein the first request and the second request comprise a request for an identical object.

33. The multi-level redirection system of claim 25, wherein the first request and the second request comprise a request for location of an object in a peer of a P2P network.