IP Library Granted Patent US 9,654,387
Granted Patent B2
US 9,654,387 · App. 14/216,061 · Granted May 16, 2017

Techniques for privileged network routing

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 9,654,387
App. No.
14/216,061
Granted
May 16, 2017
Kind
B2
Abstract

Techniques for privileged network routing are provided. As traffic is received at a gateway of a network backbone provider environment it is interrogated for predefined criteria. If the traffic satisfies the predefined criteria, then the information is routed within the network backbone provider environment to use a set of reserved and restricted resources to provide premium service for the traffic being routed through the network backbone provider environment.

Claims (30)

1. A method, comprising:

determining, by a processor, to route traffic at a network backbone using reserved resources over a privileged network path;

initiating, by the processor, the traffic over the privileged network path; and

wherein when the traffic traverses to a different network backbone while traversing the privileged network path determining, based on evaluation of exit criteria evaluated at an exit from the network backbone process one of:

1) vectoring the traffic to one or more reserved routers for handling the traffic associated with second reserved resources over the different network backbone when the traffic exits the privileged network path and 2) vectoring the traffic to one or more non-reserved and normal routers for handing the traffic associated non-privileged and normal routing over the different network backbone when the traffic exits the privileged network, and wherein the network backbone and the different network backbone cooperate for utilizing a single address space with both the network backbone and the different network backbone processing the single address space for routing the traffic, and wherein the network backbone and the different network backbone provide peering interconnections between one another.

2. The method of claim 1 , wherein initiating further includes processing the traffic over the privileged network path utilizing the reserved resources as a privileged infrastructure set aside and managed by the network backbone.

3. The method of claim 1 , wherein determining further includes determining whether to route the traffic using the reserved resources based on an identity associated with a sender of the traffic.

4. The method of claim 1 , wherein determining further includes determining whether to route the traffic using the reserved resources based on a certificate associated with the traffic.

5. The method of claim 1 , wherein determining further includes determining whether to route the traffic using the reserved resources based on a Virtual Private Network (VPN) requested within the network backbone for the traffic.

6. The method of claim 1 , wherein determining further includes utilizing the one or more reserved routers of the network backbone as at least a portion of the reserved resources.

7. The method of claim 6 , wherein utilizing further includes selecting the one or more reserved routers based on reduced hops associated with the selected reserved routers through the network backbone.

8. The method of claim 1 , wherein initiating further includes changing an original addressing scheme used by the traffic to a new addressing scheme used by the privileged network path.

9. The method of claim 8 , wherein changing further includes changing the new addressing scheme back to the original addressing scheme when the traffic exits the network backbone.

10. A method, comprising:

rerouting, by a processor, network traffic directed to a destination over a privileged infrastructure of a network backbone; and

determining, by the processor, whether based on evaluation of exit criteria at an exit of the network backbone to process one of:

1) vectoring the network traffic to one or more reserved routers associated with a request a second privileged infrastructure of a second network backbone when the network traffic exits the privileged infrastructure and enters the second network backbone on its route to the destination after the network traffic has traversed a privileged network path associated with the network backbone and 2) vectoring the network traffic to one or more normal and non-reserved routers associated with non-privileged and normal routing over the second network backbone when the traffic exits the privileged infrastructure and enters the second network backbone on its route to the destination after the network traffic as traversed the privileged network path associated with the network backbone, and wherein the network backbone and the second network backbone cooperate for utilizing a single address space with both the network backbone and the second network backbone processing the single address space for routing the traffic, and wherein the network backbone and the second network backbone provide peering interconnections between one another.

11. The method of claim 10 , wherein rerouting further includes determining to process the network traffic over the privileged infrastructure based on a sender associated with sending the network traffic to the destination.

12. The method of claim 10 , wherein rerouting further includes utilizing the reserved routers of the network backbone as the privileged infrastructure.

13. The method of claim 10 , wherein rerouting further includes determining to process the network traffic over the privileged infrastructure based on an attribute associated with the network traffic.

14. The method of claim 10 further comprising, logging, by the processor, events detected as the network traffic traverses the privileged infrastructure.

15. The method of claim 14 further comprising, generating, by the processor, a compliance report based on the logged events.

16. The method of claim 15 further comprising, sending, by the processor, the compliance report to a sender associated with sending the network traffic to the destination.

17. A system, comprising:

a privileged network infrastructure; and

a privileged routing manager adapted and configured to:

i) execute on a processor, ii) interrogate traffic received at a network backbone to determine whether the traffic is to be rerouted over the privileged network infrastructure along a privileged network path, and iii) determine whether based on evaluation of exit criteria at an exit of the network backbone to process one of:

1) vector the traffic to one or more reserved routers associated with a second privileged network infrastructure of a second network backbone when the traffic exits the privileged network infrastructure in route to a destination of that traffic and 2) vector the traffic to one or more normal and non-reserved routers associated with non-privileged and normal routing over the second network backbone when the traffic exits the privileged network infrastructure in route to the destination of the traffic wherein the network backbone and the second network backbone cooperate for utilizing address space with both the network backbone and the second network backbone processing the single address space for routing the traffic, and wherein the network backbone and the second network backbone provide peering interconnections between one another.

18. The system of claim 17 , wherein the privileged routing manager is further adapted and configured to iv) generate a compliance report when the traffic utilizes the privileged network infrastructure.

19. The system of claim 17 , wherein the privileged network infrastructure includes the one or more reserved routers having less hops than other non-reserved routers within the network backbone.

Assignments (7)
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
RELEASE OF SECURITY INTEREST REEL/FRAME 035656/0251 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: BORLAND SOFTWARE CORPORATION; ATTACHMATE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.)
Reel/Frame 062623/0009 →
CORRECTIVE ASSIGNMENT TO CORRECT THE TO CORRECT TYPO IN APPLICATION NUMBER 10708121 WHICH SHOULD BE 10708021 PREVIOUSLY RECORDED ON REEL 042388 FRAME 0386. ASSIGNOR(S) HEREBY CONFIRMS THE NOTICE OF SUCCESSION OF AGENCY. Recorded Jul 26, 2018
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 048793/0832 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
NOTICE OF SUCCESSION OF AGENCY Recorded May 2, 2017
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 042388/0386 →
CHANGE OF NAME Recorded Sep 13, 2016
From: NOVELL, INC.
To: MICRO FOCUS SOFTWARE INC.
Reel/Frame 040020/0703 →
SECURITY INTEREST Recorded May 13, 2015
From: MICRO FOCUS (US), INC.; BORLAND SOFTWARE CORPORATION; ATTACHMATE CORPORATION; NETIQ CORPORATION; NOVELL, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 035656/0251 →