IP Library Granted Patent US 8,572,281
Granted Patent B1
US 8,572,281 · App. 11/388,492 · Granted Oct 29, 2013

Leaking routes among routing engines in a highly scalable router

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 8,572,281
App. No.
11/388,492
Granted
Oct 29, 2013
Kind
B1
Abstract

A method and system for leaking routes between routing engines in a communication network. The method and system includes a route distribution service that receives and stores routing information from one or more exporting routers. The stored routing information includes the identity of one or more shared routes and may also include related route exportation criteria such as restrictions on which importing routers may receive shared routes. The route distribution service receives from one or more importing routers a request for one or more shared routes and provides one or more shared routes to the importing router. Importing routers can register with the service in order to receive shared routes or be notified when shared routes become available.

Claims (40)

1. A method for leaking routes among routers in a communication network, the method comprising:

receiving routing information from one or more exporting routers, the received routing information including:

one or more routes to be shared; and

route importing criteria for each route, the route importing criteria including a policy received from at least one of the exporting routers that restricts specific requesting routers from receiving exported shared routes and permits specific requesting routers to receive the exported shared routes;

storing the received routing information in a database accessible by more than one requesting router;

receiving from one or more requesting routers a request for one or more shared routes;

determining whether the request for the one or more shared routes matches the route importing criteria;

providing, only upon receipt of the request, one or more shared routes to the one or more requesting routers that are not restricted from receiving exported shared routes according to the policy received from the at least one exporting router; and

providing, only upon receipt of the request, the one or more shared routes to the one or more requesting routers that are permitted to receive the exported shared routes according to the policy received from the at least one exporting router.

2. The method of claim 1 , wherein the route importing criteria identifies the specific requesting routers that are permitted to receive the exported shared routes.

3. The method of claim 1 , wherein the request for one or more shared routes includes shared routes specifications that identify one or more of specific routes or specific exporting routers.

4. The method of claim 3 , further comprising notifying a requesting router when shared routes that match the requesting router's shared route specifications become available.

5. The method of claim 1 , wherein the requesting routers can query the database on demand to determine if any shared routes are available.

6. The method of claim 1 , wherein at least one of the routers is a virtual router.

7. A system for leaking routes among requesting and exporting routers in a communication network, the system comprising:

one or more routers;

a route distribution service for receiving routing information from one or more exporting routers, the received routing information including:

one or more shared routes; and

route importing criteria for each route, the route importing criteria including a policy received from at least one of the exporting routers that restricts specific requesting routers from receiving exported shared routes and permits specific requesting routers to receive the exported shared routes; and

a database for storing the received routing information, the database being accessible by more than one requesting router;

wherein the route distribution service receives from one or more requesting routers a request for one or more shared routes, determines whether the request for the one or more shared routes matches the route importing criteria, provides, only upon receipt of the request, one or more shared routes to the one or more requesting routers that are not restricted from receiving exported shared routes according to the policy received from the at least one exporting router, and provides, only upon receipt of the request, the one or more shared routes to the one or more requesting routers that are permitted to receive the exported shared routes according to the policy received from the at least one exporting router.

8. The system of claim 7 , wherein the route importing criteria identifies the specific requesting routers that are permitted to receive the exported shared routes.

9. The system of claim 7 , wherein the request for one or more shared routes includes shared routes specifications that identify one or more of specific routes or specific exporting routers.

10. The system of claim 9 , wherein the route distribution services notifies a requesting router when shared routes that match the requesting router's shared route specifications become available.

11. The system of claim 7 , wherein the requesting routers can query the database on demand to determine if any shared routes are available.

12. The system of claim 7 , wherein at least one of the routers is a virtual router.

13. A non-transitory computer-readable storage medium storing a computer program which when executed by a processing unit performs a method for leaking routes among routers in a communication network, the method comprising:

receiving routing information from one or more exporting routers, the received routing information including:

one or more routes to be shared; and

route importing criteria for each route, the route importing criteria including a policy received from at least one of the exporting routers that restricts specific requesting routers from receiving exported shared routes and permits specific requesting routers to receive the exported shared routes;

storing the received routing information in a database, the database being accessible by more than one requesting router;

receiving from one or more requesting routers a request for one or more shared routes;

determining, by a processor, whether the request for the one or more shared routes matches the route importing criteria;

providing, only upon receipt of the request, one or more shared routes to one or more requesting routers that are not restricted from receiving exported shared routes according to the policy received from the at least one exporting router; and

providing, only upon receipt of the request, the one or more shared routes to the one or more requesting routers that are permitted to receive the exported shared routes according to the policy received from the at least one exporting router.

14. The non-transitory computer-readable storage medium of claim 13 , wherein the route importing criteria identifies the specific requesting routers that are permitted to receive the exported shared routes.

15. The non-transitory computer-readable storage medium of claim 13 , wherein the request for one or more shared routes includes shared routes specifications that identify one or more of specific routes or specific exporting routers.

16. The non-transitory computer-readable storage medium of claim 15 , wherein the method further comprises notifying a requesting router when shared routes that match the importing router's shared route specifications become available.

17. The non-transitory computer-readable storage medium of claim 13 , wherein the requesting routers can query the database on demand to determine if any shared routes are available.

18. The non-transitory computer-readable storage medium of claim 13 , wherein at least one of the routers is a virtual router.

Assignments (8)
RELEASE OF SECURITY INTEREST Recorded Nov 20, 2023
From: BANK OF AMERICA, N.A.
To: CIENA CORPORATION
Reel/Frame 065630/0232 →
PATENT SECURITY AGREEMENT Recorded Nov 8, 2019
From: CIENA CORPORATION
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 050969/0001 →
RELEASE OF SECURITY INTEREST Recorded Oct 30, 2019
From: DEUTSCHE BANK AG NEW YORK BRANCH
To: CIENA CORPORATION
Reel/Frame 050938/0389 →
PATENT SECURITY AGREEMENT Recorded Jul 16, 2014
From: CIENA CORPORATION
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 033347/0260 →
SECURITY INTEREST Recorded Jul 15, 2014
From: CIENA CORPORATION
To: DEUTSCHE BANK AG NEW YORK BRANCH
Reel/Frame 033329/0417 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 19, 2010
From: CIENA LUXEMBOURG S.A.R.L.
To: CIENA CORPORATION
Reel/Frame 024252/0060 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 9, 2010
From: NORTEL NETWORKS LIMITED
To: CIENA LUXEMBOURG S.A.R.L.
Reel/Frame 024213/0653 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 24, 2006
From: JESURAJ, RAMASAMY
To: NORTEL NETWORKS LIMITED
Reel/Frame 017684/0717 →