Routing proxy for resource requests and resources

• US 8,504,723 B2
• Filed: 06/15/2011
• Issued: 08/06/2013
• Est. Priority Date: 06/15/2011
• Status: Expired due to Fees

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Kohli, Jaspal
• Primary Examiner(s): Donabed, Ninos
• Application Number:
  US13/161,117
• Publication Number:
  US 20120324110A1
• Time in Patent Office: 783 Days
• Field of Search: None
• US Class Current: 709/245
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00
• CPC Class Codes: H04L 67/1078 Resource delivery mechanisms
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A device receives, from a client device, a request for a resource, where the request provides an identifier of the client device. The device selects a target device for the resource, connects with the selected target device, and provides a proxy of the request to the selected target device, where the proxy of the request hides the identifier of the client device. The device receives the resource from the selected target device, where the resource provides an identifier of the target device. The device provides a proxy of the resource to the client device, where the proxy of the resource hides the identifier of the target device.

Claims

1. A method comprising:

receiving, by a computing device and from a client device, a first request for a first resource,

the first request including an identifier of the client device;

selecting, by the computing device, a first target device for the first resource;

connecting the computing device with the first target device;

providing, by the computing device, a proxy of the first request to the first target device,

the proxy of the first request spoofing the identifier of the client device;

receiving, by the computing device, a first portion of the first resource from the first target device,

the first portion of the first resource including an identifier of the first target device;

receiving, by the computing device and after receiving the first portion of the first resource from the first target device, an indication of an event associated with the first target device or a network associated with the first target device;

selecting, by the computing device and after receiving the indication of the event, a second target device for the first resource;

retrieving, by the computing device, a second portion of the first resource from the second target device;

providing, by the computing device and to the client device, a proxy of the first resource based on the first portion of the first resource and the second portion of the first resource,

the proxy of the first resource spoofing the identifier of the first target device;

receiving, by the computing device and from the client device, a second request for a second resource,

the first request and the second request being associated with a connection;

selecting, by the computing device, a third target device for the second resource;

retrieving, by the computing device, the second resource from the third target device; and

providing, by the computing device, a proxy of the second resource to the client device,

the proxy of the second resource spoofing an identifier of the third target device.

2. The method of claim 1, where selecting the first target device comprises:

selecting the first target device from a plurality of server devices and a local cache, provided in or locally connected to the computing device, that store resources that include the first resource.

3. The method of claim 2, where selecting the first target device comprises:

determining that the first resource is not stored in the local cache; and

selecting the first target device from the plurality of server devices after determining that the first resource is not stored in the local cache.

4. The method of claim 1, further comprising:

creating the proxy of the first request by replacing the identifier of the client device, in the first request, with an Internet protocol (IP) address of the computing device.

5. The method of claim 1, further comprising:

creating the proxy of the first resource by replacing the identifier of the first target device, in the first portion of the first resource, with an Internet protocol (IP) address of the computing device.

6. The method of claim 1, where the first resource comprises content or a service.

7. The method of claim 1, where the indication of the event includes information indicating that the second portion of the first resource cannot be retrieved from the first target device.

8. The method of claim 1, where selecting the first target device comprises:

providing, to a server, a query for a location of a first target device that stores the first resource, and

receiving, from the server, information identifying the location of the first target device,

the computing device and the first target device being connected based on the information identifying the location of the first target device.

9. The method of claim 1, where retrieving the second portion of the first resource comprises:

providing the proxy of the first request to the second target device, and

receiving, from the second target device, the second portion of the first resource as a response to the proxy of the first request.

10. The method of claim 1, where the first target device is closer, in distance, to the computing device than the second target device or any other target device that stores the first resource.

11. The method of claim 1, further comprising:

determining whether to terminate the connection based on the second request, and

providing, to the client device, information indicating whether the connection is terminated.

12. A network device comprising:

a processor to;

receive, from a client device, a first request for a first resource,

the first request including an identifier of the client device, select a first target device for the first resource,

provide a proxy of the first request to the first target device,

the proxy of the first request substituting the identifier of the client device with an Internet protocol (IP) address of the network device, receive a first portion of the first resource from the first target device,

the first portion of the first resource including an identifier of the first target device,

receive, after receiving the first portion of the first resource from the first target device, an indication of an event associated with the first target device or a network associated with the first target device,

select, after receiving the indication of the event, a second target device for the first resource,

retrieve a second portion of the first resource from the second target device;

provide, to the client device, a proxy of the first resource based on the first portion and the second portion,

the proxy of the first resource substituting the identifier of the first target device with the IP address of the network device,

receive, from the client device, a second request for a second resource, the first request and the second request being associated with a connection,

select a third target device for the second resource,

retrieve the second resource from the third target device, and

provide a proxy of the second resource to the client device,

the proxy of the second resource substituting an identifier of the third target device with the IP address of the network device.

13. The network device of claim 12,

where, when selecting the first target device, the processor is to:

select the first target device from a plurality of server devices that store resources that include the first resource, and

where, when selecting the second target device, the processor is to;

select the second target device from the plurality of server devices.

14. The network device of claim 12, where, when selecting the first target device, the processor is to:

determine that the first resource is not stored in a local cache associated with the network device, and

select the first target device from a plurality of server devices after determining that the first resource is not stored in the local cache.

15. The network device of claim 12, where the indication of the event includes information indicating that the second portion of the first resource cannot be retrieved from the first target device.

16. The network device of claim 12, where, when selecting the first target device, the processor is to:

provide, to a server, a query for a location of a first target device that stores the first resource, and

receive, from the server and before connecting the network device with the first target device, information identifying the location of the first target device as a response to the query.

17. The network device of claim 12, where, when retrieving the second portion of the first resource, the processor is to:

provide the proxy of the first request to the second target device, and

receive, from the second target device, the second portion of the first resource as a response to the proxy of the first request.

18. The network device of claim 12, where the first target device is closer, in distance, to the network device than the second target device or any other target device that stores the first resource.

19. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors of a system, cause the one or more processors to;

receive, from a client device, a first request for a first resource,

the first request including an identifier of the client device;

select a first target device for the first resource from a plurality of server devices storing resources that include the first resource;

provide a proxy of the first request to the first target device,

the proxy of the first request spoofing the identifier of the client device;

receive a first portion of the first resource from the first target device, and

the first portion of the first resource including an identifier associated with the first target device;

receive, after receiving the first portion of the first resource from the first target device, an indication of an event associated with the first target device or a network associated with the first target device;

select, after receiving the indication of the event, a second target device for the first resource from the plurality of server devices;

retrieve a second portion of the first resource from the second target device;

provide, to the client device, a proxy of the first resource based on the first portion and the second portion,

the proxy of the first resource spoofing the identifier of the first target device;

receive, from the client device, a second request for a second resource,

the first request and the second request being associated with a connection;

select a third target device for the second resource;

retrieve the second resource from the third target device; and

provide a proxy of the second resource to the client device,

the proxy of the second resource spoofing an identifier of the third target device.

20. The non-transitory computer-readable medium of claim 19, where the instructions further comprise:

one or more instructions that, when executed by the one or more processors, cause the one or more processors to;

create the proxy of the first request by replacing the identifier of the client device, in the first request, with an Internet protocol (IP) address associated with the system.

21. The non-transitory computer-readable medium of claim 19, where the instructions further comprise:

one or more instructions that, when executed by the one or more processors, cause the one or more processors to;

create the proxy of the first resource by replacing the identifier of the first target device with an Internet protocol (IP) address associated with the system.

22. The non-transitory computer-readable medium of claim 19, where the indication of the event includes information indicating that the second portion of the first resource cannot be retrieved from the first target device.

23. The non-transitory computer-readable medium of claim 19, where the first resource comprises content or a service.

24. The non-transitory computer-readable medium of claim 19, where the one or more instructions to retrieve the second portion of the first resource include:

one or more instructions that, when executed by the one or more processors, cause the one or more processors to;

provide the proxy of the first request to the second target device, and

receive, from the second target device, the second portion of the first resource as a response to the proxy of the first request.

25. The non-transitory computer-readable medium of claim 19, where the first target device is closer, in distance, to the system than the second target device or any other target device that stores the first resource.