Resource definition language for network management application development

• US 20050278709A1
• Filed: 06/15/2004
• Published: 12/15/2005
• 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, Shen, Xiangyang, Brunell, Edward G.
• Application Number:
  US10/868,375
• Publication Number:
  US 20050278709A1
• Time in Patent Office: Days
• US Class Current: 717/136
• CPC Class Codes: G06F 8/24 Object-oriented

Abstract

Methods of defining a distributed system or network to facilitate development of an application program to manage the 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, wherein the definition is based on an existing design and hierarchical structure of the distributed system or network, wherein parent-child relationships between the managed objects are identified in the resource definition language files using the resource definition language to define the managed objects in relation to the hierarchical structure, b) parsing the resource definition language files to ensure conformity with the resource definition language and creating an intermediate representation of the distributed system or network from the conforming resource definition language files, and c) processing the intermediate representation to form programming language classes, database definition files, and script files.

Claims

1. A method of defining a distributed system to facilitate development of an application program to manage the distributed system, 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; and

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.

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 one or more managed objects includes a first managed object and one or more other managed objects are defined as an implementation of the first managed object.

5. The method as set forth in claim 4 wherein the first managed object does not exist in the hierarchical structure of the distributed system.

6. The method as set forth in claim 5 wherein the first managed object acts as an external proxy interface with respect to the distributed system.

7. The method as set forth in claim 1 wherein at least a first managed object is defined and a second managed object is defined to inherit the first managed object.

8. The method as set forth in claim 7 wherein at least a third managed object is defined to inherit the second managed object, thereby also inheriting the first managed object.

9. The method as set forth in claim 1 wherein the one or more managed objects includes a first managed object, a second managed object, and a third managed object, wherein the third managed objects is defined as an implementation of the first managed object and is also defined to inherit the second managed object.

10. The method as set forth in claim 1 wherein at least a first managed object is defined and a second managed object is defined as a child of the first managed object.

11. The method as set forth in claim 10 wherein a third managed object is defined as a child of the second managed object and as a child of the first managed object.

12. The method as set forth in claim 1 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.

13. The method as set forth in claim 12 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.

14. The method as set forth in claim 13 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.

15. The method as set forth in claim 1 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.

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

index”

keyword and an “

index”

declaration specifies one or more attribute declaration, 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.

17. The method as set forth in claim 1 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.

18. The method as set forth in claim 1 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.

19. The method as set forth in claim 1, further including the step:

d) defining an options file with one or more commands for customizing operation of the processing step, wherein the processing is subsequently performed in accordance with the one or more commands in the options file.

20. The method as set forth in claim 19 wherein the options file includes at least one of an “

include-module”

command, an “

exclude-module”

command, a “

collection-mo-list”

command, a “

default-mo-list”

command, a “

root-dm-gen-flag”

command, a “

root-dm-class-name”

command, a “

generate-make-file-flag”

command, a “

make-file-name”

command, a “

compact-mo-gen-flag”

command, a “

row-status-flag”

command, an “

enforce-enum-flag”

command, a “

generate-root-classes-flag”

command, a “

mo-impl-name”

command, and a “

mo-impl-gen-flag”

command.

21. The method as set forth in claim 19, further including the step:

e) initiating the processing step with a command with one or more command line options for customizing operation of the processing step, wherein the processing is subsequently performed in accordance with the one or more command line options in the initiate processing step command.

22. The method as set forth in claim 21 wherein the initiate processing step command includes at least one of a first command line option that specifies a resource definition line file to be processed, a second command line option that specifies persistent manage objects to be processed, a third command line option that specifies managed objects that are implemented by other managed objects, a fourth command line option that specifies a storage location for the programming language classes, database definition files, and script files, a fifth command line option that specifies the options file to be used for customizing the processing step, a sixth command line option that specifies a storage location for a DDE file generated during the processing step for subsequent use by a DDE ADS tool for data range checking, a seventh command line option that specifies a trigger method to be registered during the processing step, and an eighth command line option that instructs the processing step to accept strings larger than 2000 characters for generation of data definitions.

23. A method of defining a network to facilitate development of an application program to manage the 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 created in the parsing step includes a parse tree; and

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.

24. The method as set forth in claim 23 wherein the one or more system classes include at least one of an adapter definition class, a Root Dm class, and an Nmake class.

25. The method as set forth in claim 23 wherein the one or more module classes include at least one of an attribute names and factory registration class, an enum definitions class, an enum attribute and factory definition class, and an managed object definitions class.

26. The method as set forth in claim 23 wherein the one or more managed object classes include at least one of a transient managed object class, a selective managed object class, a collection managed object class, and a persistent managed object class.

27. The method as set forth in claim 26 wherein the one or more managed object classes includes a selective managed object class and further includes an implementation class associated with the selective managed object class.

28. The method as set forth in claim 26 wherein the one or more managed object classes includes a collection managed object class and further includes at least one of a managed object handle class and a Dm class, wherein the at least one of the managed object handle class and Dm class are associated with the collection managed object class.

29. The method as set forth in claim 26 wherein the one or more managed object classes includes a persistent managed object class and further includes at least one of a managed object handle class, a specialized adapter class, and a Dm class, wherein the at least one of the managed object handle class, specialized adapter class, and Dm class are associated with the persistent managed object class.

30. The method as set forth in claim 23 wherein the one or more programming language classes are formed in a C++ programming language.

31. A method of defining a network to facilitate development of an application program to manage the 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; and

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.

32. The method as set forth in claim 31 wherein the one or more database definition files include at least one of data definitions, trigger definitions, and database schema.

33. The method as set forth in claim 31 wherein the one or more script files are formed in corresponding Unix shell scripts.