Core object model for network management configuration applications in telecommunication systems

• US 7,127,721 B2
• Filed: 08/29/2001
• Issued: 10/24/2006
• Est. Priority Date: 01/30/2001
• Status: Expired due to Fees

• Current Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Chaudhuri, Wasim H., Majid, Zomana
• Primary Examiner(s): BULLOCK JR, LEWIS ALEXANDER
• Application Number:
  US09/942,016
• Publication Number:
  US 20020103890A1
• Time in Patent Office: 1,882 Days
• Field of Search: 719/316, 717/108, 717/116, 717/120, 709223-226
• US Class Current: 719/316
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/08 Configuration management of networks or network elements address allocation H04L61/50

Abstract

The Core Network Management Object Model of the present invention generically models the physical and logical objects in a configuration management system. The present invention also models the generic action objects required to manipulate the network objects. Unique object level information is isolated at the leaf level of the object model and is not proliferated to other generic parts of the model. The action objects all model different actions that need to be performed in a configuration application architecture and insulates the network objects from having any knowledge of session and event information. Leaf objects and actions are specialized to perform any configuration related actions. In the Core Network Management Object Model an Object Factory creates the unique object and an Action Factory creates the unique action. The action shall then be performed on the unique object to get, set and modify device information through SNMP and also to store the information in the database. This makes the object model for both the network objects and actions re-usable, scalable, and extendable. Use of the present invention drastically reduces development time and effort so that the same objects can be re-used in different applications and solutions.

Claims

1. A method for providing network management of a telecommunications network that separately implements network objects at a network management system, comprising:

receiving a request for information from a network device; and

creating an object model architecture to generate a response to send to the network device, said creation further comprising;

creating a base framework object container interface and a base framework action container interface from a base framework container interface object;

creating a base framework network entity interface from said base framework object container interface; and

creating a base framework action interface from said base framework action container interface, a base framework interface object, a framework container interface object, and said framework object container interface,

wherein said base framework network entity interface is implemented separately from said base framework action container interface and base framework action interface.

2. The method of claim 1, wherein said base framework network entity interface and base framework network entity implementation objects each inherit corresponding communication connection class objects.

3. The method of claim 2 wherein said connection classes are circuit classes.

4. The method of claim 3 wherein said circuit classes include CircuitGenericEntityIfc, CircuitAxAtmIfc, CircuitAxCeIfc, CircuitAxFrameIfc, CircuitCoreAtmIfc, CircuitCoreCeIfc, CircuitCoreFrameIfc which represent interface objects for different types of sample Circuit objects and CircuitGenericEntityImpl, CircuitAxAtmImpl, CircuitAxCeImpl, CircuitAxFrameImpl, CircuitCoreAtmImpl, CircuitCoreCeImpl, CircuitCoreFrameImpl classes represent implementations of the respective Circuit interface objects.

5. The method of claim 3 wherein said circuit classes are selected from the group consisting of CircuitGenericEntityIfc, CircuitAxAtmIfc, CircuitAxCeIfc, CircuitAxFrameIfc, CircuitCoreAtmIfc, CircuitCoreCeIfc, and CircuitCoreFrameIfc which represent interface objects of different types of Circuit objects.

6. The method of claim 2, wherein said connection classes are logical port classes.

7. The method of claim 6 wherein said logical port classes include LPortGenericEntityIfc, LPortGeneralIfc, LPortEthernetIfc, LPortILMIIfc, LPortNodeToNodeIfc, LPortPNNIIfc, LportTrunkIfc which represent interface objects for the different types of sample Logical Port objects and LPortGenericEntityImpl, LPortGeneralImpl, LPortEthernetImpl, LPortI LMIImpl, LPortNodeToNodeImpl, LPortPNNIImpl, LPortTrunkImpl classes represent implementations of the respective Logical Port interface objects.

8. The method of claim 6 wherein said logical port classes are selected from the group consisting of LPortGenericEntityIfc, LPortGeneralIfc, LPortEthernetIfc, LPortILMIIfc, LPortNodeToNodeIfc, LPortPNNIIfc, LportTrunkIfc which represent interfaces objects of different types of Logical Port objects.

9. The method of claim 1, wherein said base framework action container interface and base framework action implementation abstract objects each inherit corresponding action classes.

10. The method of claim 9 wherein said action classes include a BFWGetOperationalInfoActionIfc, a BFWGetPeriodicStatisticsActionIfc, a BFWGetStatisticsActionIfc, a BFWStopStatisticsActionIfc, a BFWAddActionIfc, a BFWDeleteActionIfc, a BFWGetActionIfc, a BFWListObjectByParentActionIfc, and a BFWListObjectByTypeActionIfc interface object.

11. The method of claim 9 wherein said action classes are selected from the group consisting of BFWGetOperationalInfoActionIfc, a BFWGetPeriodicStatisticsActionIfc, a BFWGetStatisticsActionIfc, a BFWStopStatisticsActionIfc, a BFWAddActionIfc, a BFWDeleteActionIfc, a BFWGetActionIfc, a BFWListObjectByParentActionIfc, and a BFWListObjectByTypeActionIfc interface object.

12. The method of claim 9 wherein said action classes are selected from the group consisting of BFWGetOperationalInfoActionIfc, a BFWGetPeriodicStatisticsActionIfc, a BFWGetStatisticsActionIfc, a BFWStopStatisticsActionIfc, a BFWAddActionIfc, a BFWDeleteActionIfc, a BFWGetActionIfc, a BFWListObjectByParentActionIfc, and a BFWListObjectByTypeActionIfc interface object.

13. The method of claim 1, wherein said network entity interface inherits a base framework attribute container interface.

14. A computer readable medium including software code for providing network management of a telecommunications network that separately implements network objects within a network management system, comprising:

code for generating a response to a request for information from a network device, including code for creating an object model architecture to generate the response said code further comprising;

code for creating a base framework object container interface and a base framework action container interface from a base framework container interface object;

code for creating a base framework network entity interface from said base framework object container interface; and

code for creating a base framework action interface from said framework action container interface, a framework interface object, a framework container interface object, and said base framework object container interface,

wherein said base framework network entity interface is implemented in code separately from said base framework action container interface and said base framework action interface.

15. The computer readable medium of claim 14, wherein said network entity interface inherits a base framework attribute container interface.

16. The computer readable medium of claim 14 wherein said connection classes are circuit classes.

17. The computer readable medium of claim 16 wherein said circuit classes are selected from the group consisting of CircuitGenericEntityIfc, CircuitAxAtmIfc, CircuitAxCeIfc, CircuitAxFrameIfc, CircuitCoreAtmIfc, CircuitCoreCeIfc, CircuitCoreFrameIfc which represent interface objects for different types of sample Circuit objects and CircuitGenericEntityImpl, CircuitAxAtmImpl, CircuitAxCeImpl, CircuitAxFrameImpl, CircuitCoreAtmImpl, CircuitCoreCeImpl, CircuitCoreFrameImpl classes represent implementations of the respective Circuit interface objects.

18. The computer readable medium of claim 14, wherein said connection classes are logical port classes.

19. The computer readable medium of claim 18, wherein said logical port classes include LPortGenericEntityIfc, LPortGeneralIfc, LPortEthemetIfc, LPortILMIIfc, LPortNodeToNodeIfc, LPortPNNIIfc, LportTrunkIfc which represent interface objects for the different types of sample Logical Port objects and LPortGenericEntityImpl, LPortGeneralImpl, LPortEthernetImpl, LPortILMIImpl, LPortNodeToNodeImpl, LPortPNNIImpl, LPortTrunkImpl classes represent implementations of the respective Logical Port interface objects.

20. The computer readable medium of claim 14 wherein said action classes are selected from the group consisting of BFWGetOperationalInfoActionIfc, a BFWGetPeriodicStatisticsActionIfc, a BFWGetStatisticsActionIfc, a BFWStopStatisticsActionIfc, a BFWAddActionIfc, a BFWDeleteActionIfc, a BFWGetActionIfc, a BFWListObjectByParentActionIfc, and a BFWListObjectByTypeActionIfc interface object.

21. The computer readable medium as in claim 14 wherein said base framework network entity interface objects and a base framework network entity implementation objects each inherit corresponding communication connection class objects and wherein said base framework action interface and base framework action implementation abstract objects each inherit corresponding action classes.