System and method to provide routing control of information over networks

• US 7,133,365 B2
• Filed: 12/28/2001
• Issued: 11/07/2006
• Est. Priority Date: 11/02/2001
• Status: Active Grant

• Current Assignee: Internap Holding LLC
• Original Assignee: Internap Network Services Corporation
• Inventors: Johnson, Jeremy, Klinker, Eric
• Primary Examiner(s): MARCELO, MELVIN C
• Application Number:
  US10/040,902
• Publication Number:
  US 20030086422A1
• Time in Patent Office: 1,775 Days
• Field of Search: 370/238, 370/252, 370/253
• US Class Current: 370/238
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 43/026 using flow identification
• CPC Class Codes: H04L 43/0829 Packet loss
• CPC Class Codes: H04L 43/087 Jitter
• CPC Class Codes: H04L 43/0882 Utilisation of link capacity
• CPC Class Codes: H04L 43/12 Network monitoring probes
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/033 by updating distance vector protocols
• CPC Class Codes: H04L 45/302 Route determination based on requested QoS
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/308 Route determination based on user's profile, e.g. premium users
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 49/9023 for implementing a jitter-buffer
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/80 : Responding to QoS
• CPC Class Codes: H04L 69/14 : Multichannel or multilink protocols
• CPC Class Codes: H04L 69/22 : Parsing or analysis of headers
• CPC Class Codes: H04L 9/40 : Network security protocols

Abstract

A system and method for controlling routing of data. It is determined whether at least one data flow is active, the at least one data flow having an ingress portion of a current ingress path to a first point from a second point and an egress portion of a current egress path to the second point from the first point. Another data flow is routed via a next ingress portion of a next path to the first point from the second point.

Claims

1. A method for controlling data flow in a multi-homed network, the multi-homed network including a source connected to a destination through a plurality of data network connections, the method comprising:

identifying cost factors for a first data flow, the cost factors including one or more of carrier data, contract data, list usage data, or billing estimate data;

passively monitoring path performance for a path associated with the first data flow to obtain path performance information;

identifying a first ingress path for the first data flow from the destination to the source based at least in part on the cost factors and path performance information;

identifying a first data network connection within the plurality of data network connections that includes a portion of the first ingress path; and

routing the first data flow through the first data network connection so that the first data flow is routed along the first ingress path.

2. The method of claim 1 further comprising identifying whether the first data flow is active or inactive.

3. The method of claim 2 wherein identifying whether the first data flow is active or inactive comprises comparing one or more constituent elements of an IP data gram associated with a destination address against one or more inspection criteria.

4. The method of claim 2 wherein identifying whether the first data flow is active or inactive comprises reconstructing a data flow.

5. The method of claim 2 wherein the first data flow is identified as inactive and a second ingress path is identified for a next data flow.

6. The method of claim 2 wherein the first data flow is identified as active and the first ingress portion is preserved for a next data flow.

7. The method of claim 1 further comprising identifying a first egress path for the first data flow, the egress path including a second data network connection such that the first egress path is different than the first ingress path.

8. The method of claim 1 wherein passively monitoring path performance information includes monitoring one or more of traffic type, source address, destination address, application information, ToS field data, DSCP field data, or traffic volume.

9. The method of claim 1 wherein passively monitoring path performance information includes monitoring one or more of trip latency, packet loss percentage, or jitter.

10. The method of claim 1 wherein routing the first data flow through the first data network connection includes using one or more of source address manipulation or VRF routing.

11. A method for routing data in a network comprising a plurality of data network connections between a first point and a second point comprising:

passively monitoring performance characteristics of a first data flow along a first path;

determining an activity status of the first data flow based on the path performance characteristics;

if the activity status of the first data flow is active, then preserving a first ingress portion of the first path;

if the activity status of the first data flow is inactive, then determining that the first ingress portion is not available to route data.

12. The method of claim 11, wherein preserving the first ingress portion comprises:

forming an ingress association for the first data flow and the first ingress portion; and

routing the first data flow via the first ingress portion in accordance with the first ingress association.

13. The method of claim 12, wherein forming the ingress association comprises:

identifying the first data flow with at least one remote destination address related to the second point;

identifying the first ingress portion with a first local network address related to a local source address;

associating the at least one remote destination address with the first local network address; and

storing data representing the association between the at least one remote destination address with the first local network address in a data structure within a database.

14. The method of claim 11, further comprising:

preserving a first egress portion for the first data flow, if the activity status of the first data flow is active; and

determining that the first egress portion is not available to route data, if the activity status of the first data flow is inactive.

15. The method of claim 14, wherein preserving the first egress portion comprises:

forming an egress association for the first data flow and the first egress portion; and

routing data via the first egress portion in accordance with the first egress association.

16. The method of claim 15, wherein forming the first egress association comprises:

identifying the first data flow with at least one remote destination address related to the second point;

identifying the first egress portion with a first interface;

associating the at least one destination address with the first interface; and

storing data representing the association between the at least one remote destination address in a data structure within a database.

17. A system for controlling routing of data through one or more data networks, the system comprising:

a flow inspector designed to receive local network data traffic from or to a local source address, the flow inspector configured to determine that at least one data flow of the local network traffic is active by passive flow analysis;

an information base coupled to the flow inspector to receive data representing one or more flows that are active, the information base configured to provide a first ingress portion of a first ingress path for a first data flow from a second point to the first point; and

a data director coupled to the information base to receive the local network data traffic and data representing a second ingress portion of a second ingress path, the data director configured to route data via the first ingress portion for active flows and to route data via the second ingress portion for next data flows.

18. The system of claim 17, wherein the information base is futher configured to provide a first egress portion of a first egress path to the second point from the first point and wherein the data director is further configured to route data via the first egress portion for active flows and to route data via a second egress portion for next data flows.