METHODS AND APPARATUS FOR REDIRECTING REQUESTS FOR CONTENT

• US 20120259997A1
• Filed: 06/19/2012
• Published: 10/11/2012
• Est. Priority Date: 03/07/2002
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Liskov, Barbara, Carr, John F.
• Granted Patent: US 8,504,720 B2
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 2101/35 containing special prefixes
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A content engine receives a content request from a client, generates a result including one of a content-providing value and a redirection value in response to the content request, and selectively provides, to the client, one of (i) content when the result includes the content-providing value, and (ii) a redirection message when the result includes the redirection value, the redirection message including an extended domain name having a client identifier which identifies the client. The result can be used by a content router or content engine in deciding whether to provide content or a redirection. The decision to selectively provide can be based on client proximity to the content engines, past redirections, content size and type, content engine capacity, content availability and other factors.

Claims

1. A method of operating a content router in a system for routing content requests, comprising:

receiving, from a domain name service proxy device, a request for a computer address of a second content server, the request including an extended domain name having a client identifier which identifies a client, the extended domain name obtained from a redirection message selectively provided to the client by a first content server in response to a content request to the first content server from the client;

processing the extended domain name to identify the computer address based in part on the client identifier; and

sending the computer address to the domain name service proxy device for transmission to the client to access content at the second content server.

2. The method of claim 1, wherein processing includes reading, as part of the extended domain name, the client identifier, a domain name, and a flag indicating that the extended domain name includes the client identifier which identifies the client.

3. The method of claim 1, wherein processing includes reading, as at least part of the extended domain name, a domain name and an Internet Protocol address of the client as the client identifier.

4. The method of claim 1, wherein processing includes selecting the computer address from a table of computer addresses identifying computers containing the content, the computer address selected based on proximity of the client to the second content server.

5. The method of claim 1, wherein processing the extended domain name includes:

declining to identify the computer address if the computer represented by the computer address is identified in a list of references identifying computers receiving a prior content request from the client, the list of references formed as at least part of the extended domain name of the redirection message; and

identifying a different computer address.

6. The method of claim 5, wherein processing the extended domain name includes:

identifying the computer address, even if the computer represented by the computer address is in the list of references, when proximity criteria of the computer represented by the computer address in the list of references is superior to the proximity criteria of other computers.

7. The method of claim 1, wherein processing includes selecting the computer address based on information maintained on the content router, the information associated with a label included in the extended domain name.

8. The method of claim 1, wherein:

the request for a computer address is a second domain name service (DNS) request following a first DNS request generated by the client, the first DNS request including an unextended domain name lacking the client identifier;

the first content server was previously selected by the content router in response to the first DNS request from the client to provide requested content to the client; and

the second content server is determined by the content router to be well suited to deliver the requested content to the client based on the client identifier of the extended domain name of the second DNS request.

9. A computerized device operative as a content router in a system for routing content requests to handle a request for a computer address, comprising:

a communications interface for coupling the content router to a domain name server proxy device;

a memory that stores a control application; and

a processor coupled to the communications interface and the memory, the processor being operable in accordance with the control application to cause the computerized device to perform a method including;

receiving, from the domain name service proxy device, a request for a computer address of a second content server, the request including an extended domain name having a client identifier which identifies a client, the extended domain name obtained from a redirection message selectively provided to the client by a first content server in response to a content request to the first content server from the client;

processing the extended domain name to identify the computer address based in part on the client identifier; and

sending the computer address to the domain name service proxy device for transmission to the client to access content at the second content server.

10. The computerized device of claim 9, wherein processing includes reading, as part of the extended domain name, the client identifier, a domain name, and a flag indicating that the extended domain name includes the client identifier which identifies the client.

11. The computerized device of claim 9, wherein processing includes reading, as at least part of the extended domain name, a domain name and an Internet Protocol address of the client as the client identifier.

12. The computerized device of claim 9, wherein processing includes selecting the computer address from a table of computer addresses identifying computers containing the content, the computer address selected based on a proximity of the client to the second content server.

13. The computerized device of claim 9, wherein processing the extended domain name includes:

declining to identify the computer address if the computer represented by the computer address is identified in a list of references identifying computers receiving a prior content request from the client, the list of references formed as at least part of the extended domain name of the redirection message; and

identifying a different computer address.

14. The computerized device of claim 13, wherein processing the extended domain name includes:

identifying the computer address, even if the computer represented by the computer address is in the list of references, when proximity criteria of the computer represented by the computer address in the list of references is superior to the proximity criteria of other computers.

15. The computerized device of claim 9, wherein processing includes selecting the computer address based on information maintained on the content router, the information associated with a label included in the extended domain name.

16. The computerized device of claim 9, wherein:

the request for a computer address is a second domain name service (DNS) request following a first DNS request generated by the client, the first DNS request including an unextended domain name lacking the client identifier;

the first content server was previously selected by the content router in response to the first DNS request from the client to provide requested content to the client; and

the second content server is determined by the content router to be well suited to deliver the requested content to the client based on the client identifier of the extended domain name of the second DNS request.