Managed object framework for network management application development

• US 20060070082A1
• Filed: 06/15/2004
• Published: 03/30/2006
• Est. Priority Date: 06/15/2004
• Status: Abandoned Application

• Current Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Zhao, Dong, Krishnamoorthy, Shankar, Sridhar, Manjula, Halkyard, Martin S., Shen, Xiangyang, Brunell, Edward G.
• Application Number:
  US10/868,327
• Publication Number:
  US 20060070082A1
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: G06F 8/427 Parsing
• CPC Class Codes: G06F 8/52 Binary to binary

Abstract

Methods of developing an application program to manage a distributed system or network are provided. In one embodiment, the method includes: a) defining managed objects in a resource definition language and storing the definition in resource definition language files, b) parsing the resource definition language files to ensure conformity with the resource definition language and creating an intermediate representation of the distributed system, c) processing the intermediate representation to form programming language classes, database definition files, and script files, d) developing a reusable asset center framework to facilitate development of the application program, the reusable asset center including a managed object framework that provides management functionality to the application programs to support requests communicated to the distributed system from a network management station to manage the managed objects, and e) building the application program from the programming language classes, database definition files, script files, and the reusable asset framework.

Claims

1. A method of developing one or more application programs that cooperate to manage a distributed system comprising one or more servers, wherein at least one application program is associated with each server, the method including the steps:

a) defining one or more managed objects associated with the distributed system in an object-oriented resource definition language and storing the definition of the one or more managed objects in one or more resource definition language files, wherein the definition of the one or more managed objects is based on an existing design and hierarchical structure of the distributed system, wherein parent-child relationships between the one or more managed objects are identified in the one or more resource definition language files using the object-oriented resource definition language to define the one or more managed objects in relation to the hierarchical structure of the distributed system;

b) parsing the one or more resource definition language files to ensure conformity with the object-oriented resource definition language and creating an intermediate representation of the distributed system from the one or more conforming resource definition language files;

c) processing the intermediate representation of the distributed system to form one or more programming language classes, one or more database definition files, and one or more script files;

d) providing a reusable asset center framework to facilitate development of the one or more application programs, the reusable asset center including a managed object framework that provides management functionality to the one or more application programs to support requests communicated to the distributed system from a network management station to selectively manage the one or more managed objects; and

e) building the one or more application programs from at least the one or more programming language classes, one or more database definition files, one or more script files, and the reusable asset framework.

2. The method as set forth in claim 1 wherein the distributed system is a network.

3. The method as set forth in claim 2 wherein the network is a telecommunication network.

4. The method as set forth in claim 1 wherein the managed object framework includes resource classes and interface classes.

5. The method as set forth in claim 4 wherein the resource classes include a managed object class and at least one of an attribute class, a distinguished name class, a managed object class list class, an attribute factory class, an attribute list class, an attribute iterator class, an action def class, a managed object def class, an attribute event handler class, an attribute event handlers list class, a containment tree node class, and a managed object containment tree class.

6. The method as set forth in claim 4 wherein the managed object framework also includes general purpose classes.

7. The method as set forth in claim 6 wherein the general purpose classes include at least one of a connection managed object class, a connection class, a TCP connection class, a network element class, a network element managed object class, a TMN managed object class, and a TMN resource class.

8. The method as set forth in claim 4 wherein the managed object framework also includes utility classes.

9. The method as set forth in claim 8 wherein the utility classes include at least one of a timer class, a timeout scheduler class, and a periodic scheduler class.

10. The method as set forth in claim 4 wherein the interface classes include at least one of attribute server interface classes, MOF notifier interface classes, name server interface classes, and server map interface classes.

11. The method as set forth in claim 10 wherein the attribute server interface classes include at least one of an attribute server local class, a CORBA attribute server interface class, an attribute server implementation class, an MOF agent class, an MOF agent implementation class, an MOF agent cache class, and a managed object adaptor class.

12. The method as set forth in claim 10 wherein the MOF notifier interface classes include at least one of an MOF notifier local class, a CORBA MOF notifier interface class, an MOF notifier implementation class, and an MOF notifier cache class.

13. The method as set forth in claim 10 wherein the name server interface classes include at least one of a managed object name server class, a CORBA name server interface class, a name server implementation class, a name server local class, and a managed object name server iterator class.

14. The method as set forth in claim 10 wherein the server map interface classes include an EORB server map class.

15. A method of developing one or more application programs in operative communication to manage a network including one or more servers, wherein at least one application program is associated with each server, the method including the steps:

a) defining one or more managed objects associated with the network in an object-oriented resource definition language and storing the definition of the one or more managed objects in one or more resource definition language files, wherein the definition of the one or more managed objects is based on an existing design and hierarchical structure of the network, wherein parent-child relationships between the one or more managed objects are identified in the one or more resource definition language files using the object-oriented resource definition language to define the one or more managed objects in relation to the hierarchical structure of the network;

b) parsing the one or more resource definition language files to ensure conformity with the object-oriented resource definition language and creating an intermediate representation of the network from the one or more conforming resource definition language files, wherein the intermediate representation of the network created in the parsing step includes a parse tree;

c) processing the parse tree to form one or more programming language classes, wherein the one or more programming language classes formed include at least one of one or more system classes, one or more module classes, one or more managed object classes, and one or more composite attribute classes;

d) providing a reusable asset center framework to facilitate development of the one or more application programs, the reusable asset center including a managed object framework that provides management functionality to the one or more application programs to support commands communicated to the distributed system from a network management station to selectively manage the one or more managed objects; and

e) building the one or more application programs from at least the one or more programming language classes and the reusable asset framework.

16. The method as set forth in claim 15 wherein the managed object framework includes resource classes and interface classes.

17. The method as set forth in claim 16 wherein the managed object framework also includes at least one of general purpose classes and utility classes.

18. The method as set forth in claim 15 wherein the one or more resource definition language files are prepared in accordance with the object-oriented resource definition language and include a module declaration.

19. The method as set forth in claim 18 wherein the module declaration in each of the one or more resource definition language files includes at least one of an attribute type definition declaration, an enum type definition declaration, a managed object class declaration, and another module declaration.

20. The method as set forth in claim 19 wherein at least one of the one or more resource definition language files includes a module declaration and a managed object class declaration, the managed object class declaration further including an index specification and an attribute declaration.

21. The method as set forth in claim 15 wherein the resource definition language reserves at least one of a “

module”

keyword, a “

class”

keyword, an “

AttributeType”

keyword, an “

index”

keyword, a “

const”

keyword, a “

Valid”

keyword, a “

readonly”

keyword, an “

extends”

keyword, an “

implements”

keyword, an “

enum”

keyword, an “

action”

keyword, an “

in”

keyword, and an “

out”

keyword.

22. The method as set forth in claim 15 wherein the resource definition language reserves an “

index”

keyword and an “

index”

declaration specifies one or more attribute declarations, wherein the one or more attribute declarations include at least one attribute declaration that specifies a child relationship from an associated managed object to another managed object.

23. The method as set forth in claim 15 wherein the resource definition language reserves an “

extends”

keyword and an “

extends”

declaration is associated with a first managed object and specifies another managed object that is inherited by the first managed object.

24. The method as set forth in claim 15 wherein the resource definition language reserves an “

implements”

keyword and an “

implements”

declaration is associated with a first managed object and specifies another managed object of which the first managed object is an implementation.

25. The method as set forth in claim 15 wherein the managed object framework supports at least one of a first command to create a managed object, a second command to delete a selected managed object, a third command to retrieve one or more attributes associated with a selected managed object, a fourth command to set one or more attributes associated with a selected managed object, a fifth command to modify one or more attributes associated with a selected managed object, and a sixth command to retrieve attributes associated with one or more managed objects.

26. The method as set forth in claim 15 wherein the managed object framework allows the one or more application programs to define, model, and distribute the one or more managed objects across the one or more servers.

27. The method as set forth in claim 26 wherein the managed object framework isolates the distribution of the one or more managed objects across the one or more servers using a managed object name service.

28. A method of developing an application program to manage a network, the method including the steps:

a) defining one or more managed objects associated with the network in an object-oriented resource definition language and storing the definition of the one or more managed objects in one or more resource definition language files, wherein the definition of the one or more managed objects is based on an existing design and hierarchical structure of the network, wherein parent-child relationships between the one or more managed objects are identified in the one or more resource definition language files using the object-oriented resource definition language to define the one or more managed objects in relation to the hierarchical structure of the network;

b) parsing the one or more resource definition language files to ensure conformity with the object-oriented resource definition language and creating an intermediate representation of the network from the one or more conforming resource definition language files, wherein the intermediate representation of the network includes object meta-data;

c) processing the object meta-data to form one or more programming language classes, one or more database definition files, and one or more script files, wherein the one or more programming language classes formed include at least one of an index class and a query class;

d) providing a reusable asset center framework to facilitate development of the application program, the reusable asset center including a managed object framework that provides management functionality to the one or more application programs to support commands communicated to the distributed system from a network management station to manage the one or more managed objects; and

e) building the application program from at least the one or more programming language classes, one or more database definition files, one or more script files, and the reusable asset framework.

29. The method as set forth in claim 28 wherein the managed object framework includes resource classes and interface classes.

30. The method as set forth in claim 29 wherein the managed object framework also includes at least one of general purpose classes and utility classes.

31. The method as set forth in claim 28 wherein the managed object framework identifies the one or more managed objects by at least one of a managed object class name and a distinguished name hierarchy name.

32. The method as set forth in claim 28 wherein the managed object framework supports at least one of a “

get”

command, a “

getfirst”

command, a “

getnext”

command, a “

set”

command, a “

create”

command, a “

delete”

command, an “

action”

command, a “

scope/bulk get”

command, and a “

processmofcommandlist”

command from the network management station.

33. The method as set forth in claim 28 wherein the managed object framework supports value-based attributes, reference-based attributes, and function-based attributes associated with the one or more managed objects in conjunction with the commands communicated by the network management station.