Element management system with data-driven interfacing driven by instantiation of meta-model

• US 7,366,989 B2
• Filed: 05/14/2003
• Issued: 04/29/2008
• Est. Priority Date: 05/26/1999
• Status: Expired due to Fees

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: Naik, Dharmendra, Galou, Salim, Levesque, Gilbert, Zaeh, Rick
• Primary Examiner(s): SAX, STEVEN PAUL
• Application Number:
  US10/439,261
• Publication Number:
  US 20040081308A1
• Time in Patent Office: 1,812 Days
• Field of Search: 715734-739, 715771-773, 715708-709, 715802-803, 715/805, 715/745, 715/746, 715/747, 715/744, 715853-855, 715/801, 715/767, 715/765, 707/200, 707/1, 345/736, 709/223, 709/221, 709/224, 379/221.07
• US Class Current: 715/736
• CPC Class Codes: H04L 41/024 using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
• CPC Class Codes: H04L 41/044 comprising hierarchical management structures
• CPC Class Codes: H04L 41/0659 by isolating or reconfiguring faulty entities
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0866 Checking the configuration
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements
• CPC Class Codes: H04L 41/0883 Semiautomatic configuration, e.g. proposals from system
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04M 3/247 Knowledge-based maintenance systems

Abstract

A network element management system which can exploit the customized interface features of a variety of versions of a variety of complex system products from a variety of manufacturers. This is done by maintaining a meta-model, which is not itself a model until instantiated, of the possible known product configurations to be interfaced to. Once the meta-model is instantiated, it provides configuration parameters which the interface program uses to build a correct configuration for the management and/or monitoring interface. This is particularly advantageous in the preferred embodiment of a telecommunications network element management system, but also has potential applicability to other large “supersystem” applications.

Claims

1. A method for configuring an interface between a network element management system and a network element, comprising:

maintaining a meta-model having a plurality of configuration parameters, at least two of the configuration parameters being associated with different customized interface features corresponding to a plurality of system products of a plurality of manufacturers, at a network element management system;

instantiating the meta-model; and

automatically selecting first configuration parameters, of the plurality of configuration parameters, to build a first correct configuration for a first interface between the network element management system and a first network element.

2. The method of claim 1, further comprising:

instantiating the meta-model a second time; and

selecting second configuration parameters of the plurality of configuration parameters to build a second, correct configuration for a second interface between the network element management system and a second network element.

3. The method of claim 1, further comprising instantiating the meta-model and selecting a unique set of configuration parameters of the plurality of configuration parameters, for each new network element that is logged on to the network element management system.

4. The method of claim 1, wherein the step of automatically selecting first configuration parameters comprises automatically selecting between first and second mutually inconsistent configuration parameters, of the plurality of configuration parameters.

5. The method of claim 4, wherein the first and second mutually inconsistent configuration parameters are associated with first and second distinct manufacturers, respectively.

6. The method of claim 4, wherein the first and second mutually inconsistent configuration parameters are associated with first and second versions of related system products of a single manufacturer.

7. The method of claim 1, wherein the first interface comprises a management interface between the network element management system and the network element.

8. The method of claim 1, wherein the first interface comprises a monitoring interface between the network element management system and the network element.

9. A system for configuring an interface between a network element management system and a network element, comprising:

a network element management system;

a memory module of the network element management system storing a meta-model having a plurality of configuration parameters, at least two of the configuration parameters being associated with different customized interface features corresponding to a plurality of system products of a plurality of manufacturers;

a first interface between the network management system and a first network element;

a processor of the network element management system instantiating the meta-model; and

the processor automatically selecting first configuration parameters of the plurality of configuration parameters to build a first correct configuration for the first interface.

10. The system of claim 9, further comprising:

a second interface between the network element management system and a second network element;

the processor being further operable to instantiate the meta-model a second time; and

the processor being further operable to select second configuration parameters of the plurality of configuration parameters to build a second, correct configuration for the second interface.

11. The system of claim 9, wherein the processor is further operable to instantiate the meta-model and select a unique set of configuration parameters of the plurality of configuration parameters, for each new network element that is logged onto the network element management system.

12. The system of claim 9, wherein the processor is further operable to automatically select between first and second mutually inconsistent configuration parameters, of the plurality of configuration parameters.

13. The system of claim 12, wherein the first and second mutually inconsistent configuration parameters are associated with first and second distinct manufacturers, respectively.

14. The system of claim 12, wherein the first and second mutually inconsistent configuration parameters are associated with first and second versions of related system products of a single manufacturer.

15. The system of claim 9, wherein the interface comprises a management interface between the network element management system and the network element.

16. The system of claim 9, wherein the interface comprises a monitoring interface between the network element management system and the network element.