IP Library Granted Patent US 7,916,735
Granted Patent B2
US 7,916,735 · App. 12/315,351 · Granted Mar 29, 2011

Method for applying macro-controls onto IP networks using intelligent route indexing

Assignee: AT&T Intellectual Property I, L.P.
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,916,735
App. No.
12/315,351
Granted
Mar 29, 2011
Kind
B2
Abstract

Systems and methods are described that manage routing information in an IP network using extensible indexing and use the indexing to control the network. The indexing and associated controls apply to any router within the routing domain.

Claims (51)

1. A method for managing route information in an IP network comprising:

assembling a route information database for the IP network;

acquiring routes from the IP network;

an indexing stage comprising:

associating with each acquired route an index having one or more fields, each route index field representing a network/service route attribute and is an alpha-numeric index field that classifies a route relative to the number of route index fields used;

associating a network operating condition with a network/service route attribute; and

entering applicable network/service route attributes in corresponding index fields for each route based on information associated with the route from the route information database; and

a control stage comprising:

acquiring one or more network operating conditions from the IP network;

associating the one or more acquired network operating conditions with corresponding network/service route attributes;

comparing the one or more associated network/service route attributes with all route indices; and

for routes having index fields matching the one or more associated network/service route attributes, executing a predetermined control action modifying those routes.

2. The method according to claim 1 wherein the network operating conditions further comprise dynamic network operating conditions.

3. The method according to claim 2 wherein associating the one or more acquired network operating conditions with corresponding network/service route attributes further comprises:

associating a predetermined operating threshold for each dynamic network operating condition; and

if a dynamic network operating condition exceeds its predetermined operating threshold, triggering a network/service route attribute corresponding to the exceeded dynamic network operating condition.

4. The method according to claim 1 wherein a route index further includes customer subscription, application information associated with the access line from where a route is announced from and the IP network location where a route is announced from.

5. The method according to claim 1 wherein acquired routes originate from Route Reflector (RR) messages.

6. The method according to claim 1 wherein one route index field is a route source geographic location.

7. The method according to claim 1 wherein one route index field is a route destination geographic location.

8. The method according to claim 1 wherein one route index field is a route priority.

9. The method according to claim 1 wherein one route index field is an alternate route path.

10. The method according to claim 1 wherein one route index field is if the route is associated with a single path.

11. The method according to claim 1 wherein one route index field is if the route is delay intolerant.

12. The method according to claim 1 wherein one route index field is if the route is delay tolerant.

13. The method according to claim 1 further comprising, if the route information database indicates a change in status for a route, updating the affected route's index accordingly.

14. The method according to claim 1 wherein a predetermined control action further comprises applying a predetermined logic based on the one or more acquired network/service route attributes.

15. The method according to claim 14 wherein one predetermined logic sheds network load based on the one or more acquired network/service route attributes.

16. The method according to claim 1 wherein assembling a route information database further comprises receiving Border Gateway Protocol (BGP) and Open Shortest Path First (OSPF) messages.

17. The method according to claim 3 wherein one predetermined operating threshold is time of day.

18. The method according to claim 3 wherein one predetermined operating threshold is IP network capacity.

19. The method according to claim 3 wherein one predetermined operating threshold is IP network failure.

20. The method according to claim 3 wherein one predetermined operating threshold is customer feedback.

21. A system for managing route information in an IP network comprising:

means for assembling a route information database for the IP network;

means for acquiring routes from the IP network;

an indexing stage comprising:

means for associating with each acquired route an index having one or more fields, each route index field representing a network/service route attribute and is an alpha-numeric index field that classifies a route relative to the number of route index fields used;

means for associating a network operating condition with a network/service route attribute; and

means for entering applicable network/service route attributes in corresponding index fields for each route based on information associated with the route from the route information database; and

a control stage comprising:

means for acquiring one or more network operating conditions from the IP network;

means for associating the one or more acquired network operating conditions with corresponding network/service route attributes;

means for comparing the one or more associated network/service route attributes with all route indices; and

for routes having index fields matching the one or more associated network/service route attributes, means for executing a predetermined control action modifying those routes.

22. The system according to claim 21 wherein the network operating conditions further comprise dynamic network operating conditions.

23. The system according to claim 22 wherein means for associating the one or more acquired network operating conditions with corresponding network/service route attributes further comprises:

means for associating a predetermined operating threshold for each dynamic network operating condition; and

if a dynamic network operating condition exceeds its predetermined operating threshold, means for triggering a network/service route attribute corresponding to the exceeded dynamic network operating condition.

24. The system according to claim 21 further comprising, if the route information database indicates a change in status for a route, means for updating the affected route's index accordingly.

25. The system according to claim 21 wherein a predetermined control action further comprises means for applying a predetermined logic based on the one or more acquired network/service route attributes.

Assignments (4)
CHANGE OF NAME Recorded Aug 5, 2022
From: ATLASSIAN, INC.
To: ATLASSIAN US, INC.
Reel/Frame 061085/0690 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 16, 2019
From: AT&T INTELLECTUAL PROPERTY I, L.P.
To: ATLASSIAN INC.
Reel/Frame 050382/0862 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED ON REEL 022381 FRAME 0448. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. ASSIGNEE NAME SHOULD READ: AT&T INTELLECTUAL PROPERTY I, L.P. (NOT 1, L.P.). Recorded Jun 26, 2019
From: MULLIGAN, JOHN; NGUYEN, HAN Q.; SAAD, SAMIR; VAN DER MERWE, JACOBUS; ZELINGHER, SIMON
To: AT&T INTELLECTUAL PROPERTY I, L.P.
Reel/Frame 049601/0344 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 6, 2009
From: MULLIGAN, JOHN; NGUYEN, HAN Q.; SAAD, SAMIR; VAN DER MERWE, JACOBUS; ZELINGHER, SIMON
To: AT&T INTELLECTUAL PROPERTY 1, L.P.
Reel/Frame 022381/0448 →
Continuity (1)
Related Publication 20100135304A1 · Jun 3, 2010