System and method for lowering proxy bandwidth utilization

• US 20070073878A1
• Filed: 09/23/2005
• Published: 03/29/2007
• Est. Priority Date: 09/23/2005
• Status: Abandoned Application

• Current Assignee: Qurio Holdings Incorporated
• Original Assignee: Qurio Holdings Incorporated
• Inventors: Issa, Alfredo
• Application Number:
  US11/234,493
• Publication Number:
  US 20070073878A1
• Time in Patent Office: Days
• US Class Current: 709/225
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1063 Discovery through centralising entities
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

A hybrid peer-to-peer network that lowers proxy bandwidth utilization is provided. The peer-to-peer network includes peer nodes, a proxy server, and one or more guest nodes. To initiate a transfer of digital content residing on a peer node, a requesting node, which may be another peer node or a guest node, sends an HTTP request to the proxy server. The proxy server determines whether the requested digital content is bandwidth rich content such as digital images, video, or audio. If so, the proxy server generates a URL for the digital content and sends an HTTP redirect message. The requesting node then generates a second HTTP request based on the HTTP redirect message and sends the second HTTP request to the peer node. In response, the peer node generates an HTTP response including the requested digital content and sends the HTTP response to the requesting node.

Claims

1. A proxy server for a hybrid peer-to-peer system comprising:

a) a communication interface coupled to a network; and

b) a control system adapted to;

i) receive a first request for digital content residing at a first node from a requesting node via the communication interface; and

ii) redirect the requesting node to the first node if the digital content is bandwidth rich content such that a transfer of the digital content from the first node to the requesting node by-passes the proxy server.

2. The proxy server of claim 1 wherein if the digital content is not bandwidth rich content, the control system is further adapted to obtain the digital content from the first node and provide the digital content to the requesting node.

3. The proxy server of claim 1 wherein the control system is further adapted to:

determine a type of the digital content; and

determine whether the type of the digital content is one of at least one predetermined type associated with bandwidth rich content, thereby determining whether the digital content is bandwidth rich content.

4. The proxy server of claim 1 wherein the control system is further adapted to communicate with the first node via the communication interface to determine whether the digital content is bandwidth rich content.

5. The proxy server of claim 1 wherein the control system is further adapted to request a size of the digital content from the first node via the communication interface and determine whether the digital content is bandwidth rich content based on the size of the digital content.

6. The proxy server of claim 1 wherein the control system is further adapted to send a request to the first node for a determination of whether the digital content is bandwidth rich content, wherein the first node determines whether the digital content is bandwidth rich content based on at least one attribute of the digital content selected from the group consisting of file size and type.

7. The proxy server of claim 1 wherein the first request is a first Hypertext Transfer Protocol (HTTP) request and, in order to redirect the requesting node to the first node, the control system is further adapted to:

determine an Internet Protocol (IP) address of the first node;

construct a Uniform Resource Locator (URL) for the digital content; and

provide an HTTP redirect message including the URL for the digital content to the requesting node via the communication interface.

8. The proxy server of claim 7 further comprising memory storing an IP address table storing an IP address for each of a plurality of web serving nodes including the first node, wherein the control system is further adapted to determine the IP address of the first node by retrieving the IP address of the first node from the IP address table.

9. The proxy server of claim 8 wherein, for each of the plurality of web serving nodes, the control system is further adapted to receive the IP address of the web serving node from the web serving node and store the IP address in the IP address table.

10. The proxy server of claim 9 wherein, for each of the plurality of web serving nodes, the control system is further adapted to receive the IP address of the web serving node from the web serving node periodically.

11. The proxy server of claim 9 wherein, for each of the plurality of web serving nodes, the control system is further adapted to receive the IP address of the web serving node from the web serving node via a pre-established socket connection between the web serving node and the proxy server.

12. The proxy server of claim 7 wherein the requesting node generates a second HTTP request based on the HTTP redirect message and provides the second HTTP request to the first node, and the first node provides the digital content to the requesting node in response to the second HTTP request.

13. The proxy server of claim 1 wherein the first request is a first HTTP request and, in order to redirect the requesting node to the first node, the control system is further adapted to:

generate a unique single use token;

provide the unique single use token to the first node;

determine an Internet Protocol (IP) address of the first node;

construct a Uniform Resource Locator (URL) for the digital content and including the unique single use token; and

provide an HTTP redirect message including the URL for the digital content to the requesting node via the communication interface.

14. The proxy server of claim 13 wherein the requesting node generates a second HTTP request including the URL based on the HTTP redirect message and provides the second HTTP request to the first node, and the first node examines the second HTTP request for the unique single use token and provides the digital content to the requesting node in response to the second. HTTP request if the second HTTP request includes the unique single use token.

15. The proxy server of claim 13 further comprising memory storing an IP address table including an IP address for each of a plurality of web serving nodes including the first node, wherein the control system is further adapted to determine the IP address of the first node by retrieving the IP address of the first node from the IP address table.

16. The proxy server of claim 15 wherein, for each of the plurality of web serving nodes, the control system is further adapted to receive the IP address of the web serving node from the web serving node and store the IP address in the IP address table.

17. The proxy server of claim 16 wherein, for each of the plurality of web serving nodes, the control system is further adapted to receive the IP address of the web serving node from the web serving node periodically.

18. The proxy server of claim 16 wherein, for each of the plurality of web serving nodes, the control system is further adapted to receive the IP address of the web serving node from the web serving node via a pre-established socket connection between the web serving node and the proxy server.

19. The proxy server of claim 13 wherein the first node establishes a socket connection with the proxy server prior to the proxy server receiving the first HTTP request and the control system is further adapted to provide the unique single use token to the first node via the socket connection.

20. The proxy server of claim 19 further comprising memory storing a socket connection table that, for each of a plurality of web serving nodes including the first node, includes indicia identifying a socket connection for communicating with the web serving node, and wherein the control system is further adapted to determine the socket connection for the first node using the socket connection table.

21. The proxy server of claim 1 wherein the first request is a first HTTP request and, if the digital content is not bandwidth rich content, the control system is further adapted to:

translate the HTTP request into a request message;

provide the request message to the first node via a pre-established socket connection;

receive at least one response packet including the digital content from the first node;

convert the at least one response packet into an HTTP response; and

provide the HTTP response to the requesting node.

22. The proxy server of claim 21 further comprising memory storing a socket connection table that, for each of a plurality of web serving nodes including the first node, includes indicia identifying a socket connection for communicating with the web serving node, and wherein the control system is further adapted to determine the socket connection for the first node using the socket connection table.

23. A method for providing digital content from a peer node in a hybrid peer-to-peer system to a requesting node comprising:

providing a proxy server communicatively coupled to a network;

receiving a first request for digital content residing at the peer node from the requesting node at the proxy server;

determining whether the digital content is bandwidth rich content; and

redirecting the requesting node to the peer node if the digital content is bandwidth rich content such that a transfer of the digital content from the peer node to the requesting node by-passes the proxy server.

24. The method of claim 23 further comprising obtaining the digital content from the first node and providing the digital content to the requesting node if the digital content is not bandwidth rich content.

25. The method of claim 23 wherein determining whether the digital content is bandwidth rich content comprises:

determining a type of the digital content; and

determining whether the type of the digital content is one of at least one predetermined type associated with bandwidth rich content, thereby determining whether the digital content is bandwidth rich content.

26. The method of claim 23 wherein determining whether the digital content is bandwidth rich content comprises:

retrieving a size of the digital content from the peer node; and

determining whether the digital content is bandwidth rich content based on the size of the digital content.

27. The method of claim 23 wherein determining whether the digital content is bandwidth rich content comprises:

sending a request to the peer node for a determination of whether the digital content is bandwidth rich content; and

determining at the peer node whether the digital content is bandwidth rich content based on at least one attribute of the digital content selected from the group consisting of file size and type.

28. The method of claim 23 wherein the first request is a first Hypertext Transfer Protocol (HTTP) request and redirecting the requesting node to the peer node comprises:

determining an Internet Protocol (IP) address of the peer node;

constructing a Uniform Resource Locator (URL) for the digital content; and

providing an HTTP redirect message including the URL for the digital content to the requesting node.

29. The method of claim 28 further comprising:

receiving the IP address of the peer node from the peer node; and

storing the IP address of the peer node in an IP address table in memory associated with the proxy server;

wherein determining the IP address of the peer node comprises retrieving the IP address of the peer node from the IP address table.

30. The method of claim 29 wherein receiving the IP address of the peer node comprises receiving the IP address of the peer node from the peer node via a pre-established socket connection connecting the peer node to the proxy server.

31. The method of claim 28 further comprising:

generating a second HTTP request at the requesting node based on the HTTP redirect message;

providing the second HTTP request from the requesting node to the peer node; and

providing the digital content from the peer node to the requesting node in response to the second HTTP request.

32. The method of claim 23 wherein the first request is a first HTTP request and redirecting the requesting node to the peer node comprises:

generating a unique single use token;

providing the unique single use token to the peer node;

determining an Internet Protocol (IP) address of the peer node;

constructing a Uniform Resource Locator (URL) having the unique single use token embedded therein for the digital content; and

providing an HTTP redirect message including the URL for the digital content to the requesting node.

33. The method of claim 32 further comprising:

generating a second HTTP request including the URL having the unique single use token at the requesting node based on the HTTP redirect message;

providing the second HTTP request to the peer node;

examining the second HTTP request for the unique single use token at the peer node; and

providing the digital content to the requesting node in response to the second HTTP request if the second HTTP request includes the unique single use token.

34. The method of claim 32 further comprising:

receiving the IP address of the peer node from the peer node; and

storing the IP address of the peer node in an IP address table in memory associated with the proxy server;

wherein determining the IP address of the peer node comprises retrieving the IP address of the peer node from the IP address table.

35. The method of claim 34 wherein receiving the IP address of the peer node comprises receiving the IP address of the peer node from the peer node via a pre-established socket connection connecting the peer node to the proxy server.

36. The method of claim 32 wherein the peer node establishes a socket connection with the proxy server and the control system is further adapted to provide the unique single use token to the peer node via the socket connection.

37. The method of claim 23 wherein the first request is a first HTTP request and, if the digital content is not bandwidth rich content, the method further comprises:

translating the HTTP request into a request message;

providing the request message to the peer node via a pre-established socket connection;

receiving at least one response packet including the digital content from the peer node at the proxy server;

converting the at least one response packet into an HTTP response; and

providing the HTTP response from the proxy server to the requesting node.