Design for scalable network management systems

• US 6,968,371 B1
• Filed: 05/17/2000
• Issued: 11/22/2005
• Est. Priority Date: 06/23/1999
• Status: Expired due to Fees

• Current Assignee: Clearwire Communications LLC (Deutsche Telekom AG), Clearwire Ip Holdings LLC (Deutsche Telekom AG)
• Original Assignee: Clearwire Corporation (Deutsche Telekom AG)
• Inventors: Srinivasan, Sanjay
• Primary Examiner(s): Etienne, Ario
• Assistant Examiner(s): JACOBS, LASHONDA T
• Application Number:
  US09/572,193
• Time in Patent Office: 2,015 Days
• Field of Search: 709/223, 709/224, 709/227, 709/228, 709/229
• US Class Current: 709/223
• CPC Class Codes: H04L 41/042 comprising distributed management centres cooperatively managing the network
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04Q 3/0095 Specification, development or application of network management software, e.g. software re-use

Abstract

A system and methodology for building highly scalable Network Management Systems (NMS)s for the management of large voice and data networks is provided. The NMS of the present invention is designed to manage a plurality of network elements communicating through network controlled links. The elements are combined into management groups of no more than n elements. A first functional subsystem controls and manages the communication functions associated with a first group of elements. Each function or process inside the subsystem is guaranteed to communicate with only one instance of every other type of process or function. As additional network elements are added to the system, additional management groups are also added, one functional subsystem for every management group of elements. The plurality of other functional subsystems are substantially the same as the first functional subsystem. Limiting the management process to intra-subgroup communications greatly simplifies expansion of the system. When a total of m management groups exist, at least (m−1) functional subsystems are replicated from the first NMS subsystem. Thus, the network is scaled up by using size-limited subsystems.

Claims

1. A scalable communications Network Management System (NMS) comprising:

a plurality of network elements (NE)s;

a first management group of no more than said NEs, where n is a pessimistic estimate of a small fraction of the final size of the network;

a first NMS subsystem for managing said first management group, said first NMS subsystem including a first plurality of management modules corresponding to a first plurality of management functions, each said management module having a port connected to said other management modules for communications limited to said first NMS subsystem;

a second management group of no more than said n NEs; and

a second NMS subsystem for managing said second management group, replicated from said first NMS subsystem, with a first plurality of management modules, where each said management module is connected to said other management module for communications limited to said second NMS subsystem.

2. The system of claim 1 in which said first NMS subsystem includes a fault management module, said fault management module monitoring communications with network elements in said first management group of elements for faults, said fault management module communicating with said other management modules in said first NMS subsystem to locate the monitored faults, and taking corrective action to fix located faults.

3. The system of claim 1 in which said plurality of NEs include parameter values to be set for interfacing between selected NEs;

in which said first NMS subsystem includes a configuration management module, said configuration management module communicating with said other management modules in said first NMS subsystem to set said NE parameters, facilitating communications between selected NEs.

4. The system of claim 1 in which said first NMS subsystem includes an account module, said account module communicating with said other management modules in said first NMS subsystem to generate billing data in response to the provision of services to said NEs in said first management group.

5. The system of claim 1 in which said first NMS subsystem includes a performance monitoring module, said performance monitoring module communicating with said other management modules in said first NMS subsystem to provide a measurement of the quality of service being enjoyed by said NEs of said first management group.

6. The system of claim 1 in which said first NMS subsystem includes a security module, said security module communicating with said other management modules in said first NMS subsystem to provide authorization and encryption of services to said NEs of said first management group.

7. The system of claim 1 further comprising;

a third NMS subsystem including a first plurality of updated management modules;

in which the management of said first management group of said elements is discontinued by said first NMS subsystem; and

in which said third NMS subsystem is engaged to manage said first management group of said NEs.

8. The system of claim 1 further comprising:

at least one graphical user interface (GUI) for monitoring said NE events in said first and second NMS subsystems;

a mapping database, operatively connected to said GUI, to locate said NEs; and

in which system instructions to said NEs are routed through said GUI.

9. In a network of communicating network elements (NE)s, a method of scaling a network management function as the network expands, the method comprising:

grouping NEs into first and second management groups of no more than n NEs in each group, where n is a pessimistic estimate of a small fraction of the final size of the network;

configuring a first Network Management System (NMS) subsystem to manage a first plurality of functions for the first management group;

managing the first NMS subsystem through interactions between the first plurality of first NMS subsystem functions;

replicating the first NMS subsystem, creating a second NMS subsystem to manage the first plurality of functions for the second management group; and

managing the second NMS subsystem through interactions between the first plurality of second NMS subsystem functions.

10. The method of claim 9 in which managing the first NMS subsystem includes limiting interactions to the first plurality of first NMS subsystem functions;

and

in which managing the second NMS subsystem includes limiting interactions to the first plurality of second NMS subsystem functions.

11. The method of claim 10 further comprising:

adding NEs to the system;

grouping NEs into p additional management groups of no more than said n NEs; and

replicating p additional NMS subsystems from the first NMS subsystem to manage the p additional management groups.

12. The method of claim 10 in which managing the first NMS subsystem includes interacting a fault management function with the other subsystem functions to monitor the network for faults, locate the monitored faults, and take corrective action to fix located faults.

13. The method of claim 10 in which the grouping of NEs includes the NEs having parameter values which are set to interface selected NEs, and in which managing the first NMS subsystem includes interacting a configuration management function with other subsystem functions to set NE parameters, facilitating communication between selected NEs.

14. The method of claim 10 in which managing the first NMS subsystem includes interacting an accounting function with other subsystem functions to generate billing data in response to the provision of services to NEs.

15. The method of claim 10 in which managing the first NMS subsystem includes interacting a performance monitoring function with other subsystem functions to measure the quality of service provided to NEs.

16. The method of claim 10 in which managing the first NMS subsystem includes interacting a security function with other subsystem functions to provide authorization and encryption of services to NEs.

17. The method of claim 11 wherein the subsystem management functions are updated, and further comprising:

creating a third NMS subsystem to manage a first plurality of upgraded functions for the first management group;

discontinuing the management of the first management group by the first NMS subsystem; and

managing the first management group of network elements with the third NMS subsystem.

18. The method of claim 17 further comprising:

replicating the third NMS subsystem to create a fourth NMS subsystem; and

discontinuing the management of the second management group by the second NMS subsystem; and

managing the second management group of NEs with the fourth NMS subsystem.

19. The method of claim 18 further comprising:

iteratively repeating the replacement of NMS subsystems replicated from the first NMS subsystem with subsystems replicated from the third NMS subsystem until all p management groups are managed by an NMS subsystem replicated from the third NMS subsystem.

20. The method of claim 10 further comprising:

creating a database cross-referencing each NE to a managing group; and

locating a NE and routing system instructions to the NE.

21. The method of claim 20 in which the location of NEs includes creating a graphical user interface (GUI) to manipulate the location of NEs in the database.

22. In a network of communicating network elements (NE)s, a method of scaling a network management function as the network expands, the method comprising:

grouping NEs into a first network subsystem;

configuring a first Network Management System (NMS) subsystem to manage a plurality of functions for the first network subsystem;

when the number of NEs within the first network subsystem exceeds n NEs, where n is a pessimistic estimate of a small fraction of the final size of the network, creating a second network subsystem whereby the number of NEs in the first and second network subsystems each comprise no more than said n NEs;

replicating the first NMS subsystem to thereby create a second NMS subsystem-to manage the plurality of functions for the second network subsystem.

23. The method of claim 22 wherein additional network subsystems are created such that no network subsystem exceeds said n NES and additional NMS subsystems are replicated to manage the plurality of functions for each respective additional network subsystem.