Core object model for network management configuration applications in telecommunication systems

• US 20020103890A1
• Filed: 08/29/2001
• Published: 08/01/2002
• Est. Priority Date: 01/30/2001
• Status: Active Grant

• Current Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Chaudhuri, Wasim H., Majid, Zomana
• Granted Patent: US 7,127,721 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• 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. An object model architecture for providing network management of a telecommunications network, said architecture comprising:

a base framework interface object;

a base framework container interface object;

a base framework object container interface and a base framework action container interface each being inherited from said base framework container interface;

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

a base framework action interface inherited from said base framework action container interface, said base framework interface, said base framework container interface, said base framework object container interface, said base framework action container interface and said base framework action interface being implemented by corresponding implementation abstract objects and said base framework network entity interface being implemented by a base framework network entity implementation class object.

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

3. The architecture of claim 1, wherein said base framework action interface and said base framework action implementation abstract object each inherit corresponding action classes.

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

5. The architecture of claim 2 wherein said connection classes are circuit classes.

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

7. The architecture of claim 5 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, CircuitCoreAtmlImpl, CircuitCoreCeImpl, CircuitCoreFrameImpl classes represent implementations of the respective Circuit interface objects.

8. The architecture of claim 5 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.

9. The architecture 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, LPortILMIImpl, LPortNodeToNodeImpl, LPortPNNIImpl, LPortTrunkImpl classes represent implementations of the respective Logical Port interface objects.

10. The architecture 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.

11. The architecture of claim 5 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.

12. The architecture of claim 5 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 architecture of claim 6 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.

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

16. The architecture of claim 14 wherein said connection classes are circuit classes.

17. The architecture of claim 14, wherein said connection classes are logical port classes.

18. The architecture 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.

19. The architecture of claim 16, 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, LPortILMIImpl, LPortNodeToNodeImpl, LPortPNNIImpl, LPortTrunkImpl classes represent implementations of the respective Logical Port interface objects.

20. The architecture 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.

14. A computer readable medium including an object model architecture in software for providing network management of a telecommunications network, said architecture comprising:

a base framework interface object;

a base framework container interface object;

a base framework object container interface and a base framework action container interface each being inherited from said base framework container interface;

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

a base framework action interface inherited from said base framework action container interface, said base framework interface, said base framework container interface, said base framework object container interface, said base framework action container interface and said base framework action interface being implemented by corresponding implementation abstract objects and said base framework network entity interface being implemented by a base framework network entity implementation class object;

wherein said base framework network entity interface object and said base framework network entity implementation object each inherit corresponding communication connection class objects and wherein said base framework action interface and said base framework action implementation abstract object each inherit corresponding action classes.