Methods and apparatus for routing in a network

• US 7,852,767 B2
• Filed: 01/24/2005
• Issued: 12/14/2010
• Est. Priority Date: 02/09/2004
• Status: Expired due to Fees

• Current Assignee: Velocix Ltd. (Nokia Corporation)
• Original Assignee: Velocix Ltd. (Nokia Corporation)
• Inventors: Twiss, Adam
• Primary Examiner(s): Moe; Aung S
• Assistant Examiner(s): ELLIOTT IV, BENJAMIN H
• Application Number:
  US10/588,586
• Publication Number:
  US 20080049619A1
• Time in Patent Office: 2,150 Days
• Field of Search: 370/236, 370/349, 370/229, 370/235, 370/386, 370/389, 370/392, 370/395.1, 370/395.31, 370/395.32, 370/395.4, 370/395.52, 370/395.72, 370/401, 370/471, 370/496, 709/238, 709/242, 709/243, 709/244
• US Class Current: 370/235
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/60 Router architectures
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1091 Interfacing with client-server systems or between P2P systems
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

The invention generally relates to methods and apparatus for routing data in networks, in particular packet data routing in TCP/IP (Transmission Control Protocol/Internet Protocol). Application of the invention include routing of peer-to-peer (P2P) network data. A method of controlling traffic on a data network, said traffic comprising payload data and associated signaling data, the method comprising reading a portion of said payload data for a communications session between a first entity and a second entity communicating over said network; determining whether said portion of payload data identifies a type of traffic to be controlled; storing, responsive to said determining, signaling data associated with said portion of payload data; reading said signaling data to identify an attempt to begin a further communications session of said identified traffic type or to resume said communication session; and controlling traffic of said further or resumed communications session responsive to said identification.

Claims

1. A method of controlling traffic on a data network, said traffic comprising payload data and associated signaling data, the method comprising:

reading a portion of said payload data for a first traffic of a first communications session between a first entity and a second entity communicating over said data network;

using a signature in the portion of the payload data to determine whether said portion of the payload data identifies peer-to-peer (P2P) traffic;

storing signaling data associated with said portion of the payload data;

reading signaling data for a second traffic of a second communications session on said data network;

comparing said read signaling data with said stored signaling data to identify said second traffic as the P2P traffic and

controlling said second communications session responsive to said identification of the P2P traffic, by limiting propagation of the P2P traffic without limiting propagation of non-P2P traffic.

2. The method of claim 1, wherein said controlling further comprises:

controlling a route of said second communications session traffic.

3. The method of claim 1, further comprising:

reading at least a portion of said signaling data for said second traffic;

determining from said signaling data an address of an originator of said second communications session, said originator comprising one of said first and second entities; and

sending a signal to said originator using said determined address.

4. The method of claim 1, wherein said controlling further comprises:

signaling with said signaling data.

5. The method of claim 1, wherein said controlling further comprises:

sending a message in said payload data.

6. The method of claim 5, wherein said message includes a request to retry establishing said second communications session.

7. The method of claim 1, wherein said storing is responsive to said determining.

8. The method of claim 1, wherein said reading of the portion of said payload data for the first traffic further comprises:

reading first payload data for a communication from said first to said second entity and second payload data for a communication from said second to said first entity, and wherein said determining whether said portion of payload data

identifies the P2P traffic; and

determines whether both said first and said second payload data contain the P2P traffic.

9. The method of claim 8, further comprising

buffering said first and second payload data for said determining.

10. The method of claim 1, further comprising:

signaling, responsive to said determining, to at least one of said first and second entities to interrupt said communications session.

11. The method of claim 1, wherein said second traffic comprises an attempt to begin a further communications session of the P2P traffic or to resume said communications session, and wherein said controlling further comprises:

controlling traffic of said second communications session.

12. The method of claim 1, wherein said network comprises a packet data network and wherein said signaling data includes a destination identifier.

13. The method of claim 12, wherein said network comprises an internet protocol (IP) network and wherein said signaling data includes a destination address and port number.

14. The method of claim 1, wherein said traffic content type to be controlled includes P2P protocol network traffic employing a variable TCP port number for P2P connections.

15. The method of claim 14, wherein said controlling further comprises:

routing said P2P traffic to a P2P network gateway.

16. The method of claim 14, wherein said controlling further comprises:

routing said P2P traffic to a P2P network cache.

17. A router for controlling traffic on a data network, said traffic comprising payload data and associated signaling data, the router comprising:

a network interface that interfaces with said data network;

a packet switch coupled to the network interface that separates the traffic into peer-to-peer (P2P) traffic and non P2P traffic, wherein propagation of the P2P traffic is limited without limiting propagation of the non P2P traffic;

a data memory that stores data to be processed;

an instruction memory that stores computer executable code; and

a processor coupled to said network interface, to said data memory, and to said instruction memory that processes said data in accordance with the computer-executable code stored in said instruction memory, whereby said processor is configured to;

read a portion of said payload data for a first traffic of a communications session between a first entity and a second entity communicating over said network;

using a signature in the portion of the payload data to determine whether said portion of payload data identifies the P2P;

store signaling data associated with said portion of payload data;

read signaling data for a second traffic on said network; and

to

compare said read signaling data with said stored signaling data to identify an attempt to begin a second communications session of said P2P traffic; and

control said second communications session responsive to said identification.

18. The router of claim 17, wherein network comprises a packet data network, wherein said signaling data comprises a destination identifier to identify a destination of a packet of data comprising said first traffic, and wherein said storing stores a destination identifier for said first traffic that is the P2P traffic in said data memory responsive to identifying said P2P traffic.

19. The router of claim 18, wherein said processor is further configured to:

store portions of said payload data of said communications session sent from both said first and said second entity; and

determine when communications from both said first and second entities are the P2P traffic.