Network traffic control in peer-to-peer environments

• US 8,139,483 B2
• Filed: 05/22/2008
• Issued: 03/20/2012
• Est. Priority Date: 11/15/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bauer, Daniel N., Rooney, John G., Scotton, Paolo, Waldvogel, Marcel
• Primary Examiner(s): Nguyen, Thu Ha
• Assistant Examiner(s): SCOTT, RANDY A
• Application Number:
  US12/125,316
• Publication Number:
  US 20080259793A1
• Time in Patent Office: 1,398 Days
• Field of Search: 709/219, 709/203, 709/220, 709/224, 370/230.1
• US Class Current: 370/230.1
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1046 Joining 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 69/329 in the application layer [OSI layer 7]

Abstract

A method and an electronic unit are disclosed for controlling traffic on a network, especially for controlling peer-to-peer related traffic. A filter unit is intercepting messages related to peer-to-peer application from a network line, irrespective of the messages'"'"' destination, A control logic then manages a request represented by an intercepted message subject to its content and subject to peering specific information.

Claims

1. A network traffic control unit, comprising a computer program product including a non-transitory computer readable storage medium having computer executable instructions stored thereon that, when executed by a computer processor, are configured to provide:

a filter unit for intercepting messages

relating to peer-to-peer application,

from a network line,

irrespective of destination, and

a control logic that is configured for managing a request represented by an intercepted message subject to its content and subject to peering specific information the network traffic control unit provides,

which request to be managed is an intercepted connect request issued from a first peer node and directed to a second peer node;

wherein managing the intercepted connect request comprises;

dropping the intercepted connect request;

in the event the peering specific information comprises a connection that is already established that can serve or be extended to serve the intercepted connect request, sending a second connect request by the network traffic control unit to the first peer node in response to the intercepted connect request, and sending no message to the second peer node by the network traffic control unit; and

in the event the peering specific information does not comprise a connection that is already established that can serve or be extended to serve the intercepted connect request, sending a third connect request by the network traffic control unit to the second peer node pretending the first peer node is sending the third connect request.

2. A network traffic control unit according to claim 1, wherein the network traffic control unit is prepared to communicate according to a peer-to-peer application protocol.

3. A network traffic control unit according to claim 2, wherein the network traffic control unit is prepared to apply the peer-to-peer application protocol for managing connect requests.

4. A network traffic control unit according claim 1,

wherein the network traffic control unit is prepared to communicate according to a protocol different to the peer-to-peer application protocol.

5. A network traffic control unit according to claim 4,

wherein the network traffic control unit is prepared to apply the protocol different to the peer-to-peer application protocol for managing query requests.

6. A network traffic control unit according to claim 1,

wherein the peering specific information comprises information on peer-to-peer connections the network traffic control unit is currently aware of.

7. A network traffic control unit according to claim 1,

wherein the peering specific information comprises information on peer nodes associated to the network traffic control unit.

8. A network traffic control unit according to claim 1,

wherein the peering specific information comprises an index that allocates keys representing data files for download to network traffic control units.

9. A network traffic control unit according to claim 1,

wherein the peering specific information comprises an index that allocates peer nodes to keys representing data files for download.

10. A network traffic control unit according to claim 1,

wherein the control logic is configured for implementing a set of rules for deriving keys from intercepted query requests.

25. A network comprising:

at least one group of peer nodes,

a network line serving as an ingress/egress line for said at least one group, and

a network traffic control unit according to claim 1, intercepting messages from the network line.

11. A method for controlling traffic on a network implemented in a network traffic control unit, comprising:

receiving messages by the network traffic control unit related to peer-to-peer application, intercepted by a filter unit from a network line, irrespective of the messages'"'"' destination,

managing a request represented by an intercepted message subject to its content and subject to peering specific information by the network traffic control unit,

wherein the request to be managed is an intercepted connect request issued from a first peer node and directed to a second peer node, and further comprising;

dropping the intercepted connect request;

in the event the peering specific information comprises a connection that is already established that can serve or be extended to serve the connect request, sending a second connect request by the network traffic control unit to the first peer node in response to the intercepted connect request, and sending no message to the second peer node by the network traffic control unit; and

in the event the peering specific information does not comprise a connection that is already established that can serve or be extended to serve the intercepted connect request, sending a third connect request by the network traffic control unit to the second peer node pretending the first peer node is sending the third connect request.

12. A method according to claim 11, wherein the peering specific information comprises existing connections the network traffic control unit is aware of.

13. A method according to claim 11, comprising sending by the network traffic control unit a connect request to a peer node other than the second peer node after the first peer node has accepted the second connect request.

14. A method according to claim 11, further comprising sending by the network traffic control unit a connect request to another network traffic control unit after the first peer node has accepted the second connect request.

15. A method according to claim 11, further comprising intercepting and managing by the network traffic control unit a query request for a data file issued by a peer node.

16. A method according to claim 15, wherein managing the query request is subject to an index that allocates keys representing data files for download to network traffic control units.

17. A method according to claim 15, wherein managing the query request is subject to an index that allocates peer nodes to keys.

18. A method according to claim 15, comprising deriving one or more keys from the content of the query request.

19. A method according to claim 18, comprising directing a request to one or more remote network traffic control units that are allocated to the derived keys according to the key -network traffic control unit index.

20. A method according to claim 19, comprising receiving a list of peer nodes that are allocated to the keys, from the remote network traffic control unit.

21. A method according to claim 20, comprising sending a hit message to the querying peer node.

22. A method according to claim 11, comprising:

administering a key-peer node index for some keys, and

providing other network traffic control units on request with the knowledge which peer nodes are allocated to a requested key according to the key-peer node index.

23. A method according to claim 22, wherein administering the key-peer node index comprises removals of entries.

24. A method according to claim 11, comprising:

monitoring hit messages sent from an associated peer node,

deriving one or more keys from the content of a hit message,

allocating the sending peer node to the derived keys, and

storing the key-peer node relation in a key-peer node index.

26. A computer program product including a non-transitory computer readable storage medium having computer executable instructions stored thereon that, when executed by a computer processor, direct the computer processor to perform a method as claimed in claim 11.