IP Library Granted Patent US 7,447,153
Granted Patent B2
US 7,447,153 · App. 11/063,057 · Granted Nov 4, 2008

System and method for end to end route control

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,447,153
App. No.
11/063,057
Granted
Nov 4, 2008
Kind
B2
Abstract

Session independent end to end route control is provided by coordination between a pair of route control devices. Each device determines whether received traffic qualifies for end to end route control and whether the device at the other end supports end to end route control. If so, then the route control devices determine a routing mode, such as tunneling or address translation, and routing parameters. The performance of the selected path is monitored and is changed if the performance becomes unacceptable. Path performance can be measured using one-way measurement techniques that use a common inbound path or a control channel.

Claims (24)

1. A method for end to end route control between a source and a destination, comprising:

determining a routing mode and routing parameters based on routing configuration information exchanged between a source route control device and a destination route control device, wherein the routing parameters include an inbound provider;

selecting a packet source address which corresponds to the inbound provider so that inbound traffic from the destination to the source is routed through the inbound provider;

routing traffic using the routing mode and the routing parameters;

monitoring performance of an outbound path from the source to the destination specified by the routing parameters; and

if the performance of the outbound path is below a threshold, then adjusting the routing parameters to change the outbound path.

2. The method of claim 1 , further comprising:

receiving inbound traffic from the destination to the source;

comparing a destination address associated with the inbound traffic with a destination address associated with previously routed outbound traffic from the source to the destination; and

if the destination address associated with the inbound traffic differs from the destination address associated with the previously routed outbound traffic, then using the destination address associated with the inbound traffic for future outbound traffic.

3. The method of claim 2 , wherein using the destination address associated with the inbound traffic for future outbound traffic, comprises:

providing a translation from the destination address associated with the previous outbound traffic to the destination address associated with the inbound traffic.

4. The method of claim 1 , wherein the routing parameters include a destination provider, further comprising:

selecting a destination address which corresponds to the destination provider so that outbound traffic from the source to the destination and inbound traffic from the destination to the source are routed through the destination provider.

5. The method of claim 1 , wherein outbound traffic from the source to the destination is routed via the inbound provider.

6. The method of claim 1 , wherein the routing parameters include an outbound provider, further comprising:

selecting a secondary address which corresponds to the outbound provider so that outbound traffic from the source to the destination is routed through the outbound provider.

7. The method of claim 1 , wherein the routing parameters include an outbound provider, further comprising:

selecting an interface which corresponds to the outbound provider so that outbound traffic from the source to the destination is routed via the outbound provider.

8. The method of claim 1 , wherein outbound traffic from the source to the destination is routed via an outbound provider, which is distinct from the inbound provider.

9. The method of claim 1 , wherein the routing mode includes tunneling.

10. The method of claim 1 , wherein the routing mode includes address translation.

11. The method of claim 1 , further comprising:

determining whether traffic associated with a session qualifies for end to end route control.

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 →
RELEASE OF SECURITY INTEREST Recorded May 11, 2020
From: JEFFERIES FINANCE LLC
To: INTERNAP CORPORATION
Reel/Frame 052628/0018 →
SECURITY INTEREST Recorded May 8, 2020
From: INTERNAP HOLDING LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 052616/0515 →
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 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 →
SECURITY AGREEMENT Recorded Nov 9, 2010
From: INTERNAP NETWORK SERVICES CORPORATION
To: WELLS FARGO CAPITAL FINANCE, LLC, AS AGENT
Reel/Frame 025337/0437 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 5, 2008
From: KLINKER, ERIC
To: INTERNAP NETWORK SERVICES CORPORATION
Reel/Frame 021485/0953 →