IP Library Granted Patent US 7,133,365
Granted Patent B2
US 7,133,365 · App. 10/040,902 · Granted Nov 7, 2006

System and method to provide routing control of information over networks

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,133,365
App. No.
10/040,902
Granted
Nov 7, 2006
Kind
B2
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 (44)

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.

Assignments (12)
RELEASE OF SECURITY INTEREST Recorded May 10, 2022
From: WILMINGTON TRUST, NATIONAL ASSOCIATION
To: INTERNAP HOLDING LLC
Reel/Frame 059884/0443 →
CHANGE OF NAME Recorded Dec 29, 2020
From: INTERNAP CORPORATION
To: INTERNAP HOLDING LLC
Reel/Frame 054868/0048 →
CORRECTIVE ASSIGNMENT TO CORRECT THE NATURE OF CONVEYANCE PREVIOUSLY RECORDED ON REEL 053382 FRAME 0721. ASSIGNOR(S) HEREBY CONFIRMS THE ORIGINALLY RECORDED AS "RELEASE BY SECURED PARTY" SHOULD BE CORRECTED TO READ --RELEASE OF SECURITY INTEREST BY DEBTOR--. Recorded Aug 5, 2020
From: COMDISCO, INC.
To: INTERNAP HOLDING LLC
Reel/Frame 053412/0782 →
RELEASE OF SECURITY INTEREST Recorded Aug 3, 2020
From: COMDISCO, INC.
To: INTERNAP HOLDING LLC
Reel/Frame 053382/0721 →
RELEASE OF SECURITY INTEREST Recorded May 11, 2020
From: JEFFERIES FINANCE LLC
To: INTERNAP CORPORATION
Reel/Frame 052628/0018 →
RELEASE OF PATENT SECURITY AGREEMENT RECORDED AT REEL 044547/FRAME 0029 Recorded May 8, 2020
From: JEFFERIES FINANCE LLC
To: INTERNAP CORPORATION
Reel/Frame 052617/0103 →
SECURITY INTEREST Recorded May 8, 2020
From: INTERNAP HOLDING LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 052616/0515 →
SECURITY INTEREST Recorded Jan 5, 2018
From: INTERNAP CORPORATION
To: JEFFERIES FINANCE LLC
Reel/Frame 044547/0029 →
RELEASE OF SECURITY INTEREST Recorded Apr 7, 2017
From: JEFFERIES FINANCE LLC
To: INTERNAP CORPORATION
Reel/Frame 041929/0328 →
CHANGE OF NAME Recorded Feb 16, 2015
From: INTERNAP NETWORK SERVICES CORPORATION
To: INTERNAP CORPORATION
Reel/Frame 035000/0349 →
SECURITY AGREEMENT Recorded Dec 5, 2013
From: INTERNAP NETWORK SERVICES CORPORATION
To: JEFFERIES FINANCE LLC (AS COLLATERAL AGENT)
Reel/Frame 031765/0527 →
RELEASE OF SECURITY INTEREST Recorded Dec 4, 2013
From: WELLS FARGO CAPITAL FINANCE, LLC (AS AGENT)
To: INTERNAP NETWORK SERVICES CORPORATION
Reel/Frame 031710/0635 →