Network traffic control in peer-to-peer environments

• US 7,600,033 B2
• Filed: 10/28/2003
• Issued: 10/06/2009
• Est. Priority Date: 11/15/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Rooney, John G., Scotton, Paolo, Waldvogel, Marcel, Bauer, Daniel N.
• Primary Examiner(s): Nguyen; Thuha T.
• Assistant Examiner(s): SCOTT, RANDY A
• Application Number:
  US10/535,123
• Publication Number:
  US 20060168304A1
• Time in Patent Office: 2,170 Days
• Field of Search: 709/227, 709/228, 709/229, 709/230, 709/231, 709/232
• US Class Current: 709/232
• 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 method for controlling traffic on a network, comprising:

receiving messages 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, wherein the request to be managed is a connect request issued from a peer node and directed to another peer node, dropping the intercepted message;

wherein managing the connect request is subject to existing connections a network traffic control unit is aware of the dropping of a plurality of intercepted messages,

wherein no message is sent to the addressee of the intercepted connect request when a connection is already established that can serve or be extended to serve the requesting peer node, and further comprising;

sending a connect request to the originator of the intercepted connect request in response to the intercepted connect request;

sending a connect request to the addressee of the intercepted connect request;

sending a connect request to the addressee of the intercepted connect request pretending the originator of the intercepted connect request is sending the connect request;

sending a connect request to a peer node other than the addressee of the intercepted connect request;

sending a connect request to another network traffic control unit; and

sending the connect request to another party than the originator of the intercepted connect request once the originator has accepted the connect request from the network traffic control unit directed to the originator, and

wherein a request to be managed is a data file query issued by a peer node,

wherein managing the query request is subject to an index that allocates keys representing data files for download to network traffic control units,

wherein managing the query request is subject to an index that allocates peer nodes to keys, and further comprising;

deriving one or more keys from the content of the query_request;

directing a request to one or more remote network traffic control units that are allocated to the derived keys according to a key—

network traffic control unit index;

receiving a list of peer nodes that are allocated to the keys, from a remote one of said network traffic control unit;

sending a hit message to a querying peer node;

administering a key—

peer node index for some keys, and

providing other network traffic control units on request with knowledge of which peer nodes are allocated to a requested key according to the key—

peer node index, wherein administering the key—

peer node index comprises removals of entries;

monitoring hit messages sent from an associated peer node,

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

allocating a sending said peer node to the derived keys, and

storing the key—

peer node relation in a key—

peer node index.