JP3150065B2 - Operation screen automatic generation method and operation screen automatic generation system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network management system conforming to an OSI management model, and more particularly, to an operation screen in which the operation definition of a management target is defined by an OSI management template and instructs a management operation to the management target. A method and system for generating.

[0002]

2. Description of the Related Art Conventionally, a management operation screen for a management target in a network management system has been mainly developed for each management target and for each type of operation to be operated. In the OSI management model, there is an operation definition template, which defines management attributes for each management target type, possible values, types of operation that can be instructed, combinations of parameters, and the like. We are developing.

For example, the technology described in Japanese Patent Application Laid-Open No. 3-231352 is a network management system based on the OSI management model, but does not have an operation screen automatic generation function.

[0004] The OSI management model is an open interconnection (Open System) as a network management system.
m Interconnection), and is an international standard.

[0005]

The first problem is that the number of development steps in the prior art is great. The reason is that, since development is performed for each screen, the screen layout is adjusted each time, and the attributes and behavior of the management target to be incorporated into the screen are manually developed while referring to the OSI operation definition template.

A second problem is that the quality of development decreases as the number of management operation screens to be developed increases. The reason is that in recent years, the types of management operations that can be performed from the network management system have increased due to the progress of network configuration devices, and the number of management operation screens developed on the network management system side has increased accordingly.
This is because there is a possibility that the quality evaluation man-hours for tests and the like will also be squeezed, resulting in quality deterioration.

An object of the present invention is to simply define screen display data corresponding to each attribute information defined in an OSI operation definition template as a database.
An object of the present invention is to automatically generate and display a management operation screen for a specified management target device (or component), reduce development of the management operation screen, improve reliability, and improve productivity.

[0008]

An operation screen automatic generation method according to the present invention is an operation screen automatic generation method for handling a network management system conforming to the OSI management model. An operation screen required for performing a management operation on the internal components is automatically generated and displayed.

An operation screen automatic generation system according to the present invention
An operation screen automatic generation system for network management management conforming to an SI management model, comprising: (a) an operation definition template for defining attributes and operations of a managed object; and (b) an operation screen for displaying an operation screen. A screen name data file for defining the required attribute and name data of the operation, (c) a compiler for automatically generating an operation screen that receives the operation definition template and the screen name data file, and (d) A screen generation data file generated by the operation screen automatic generation compiler, (e) a management target inclusion tree that defines the inclusion configuration of the management target object, and (f) a management target object to be operated are selected. Read data from the screen generation data file and the management target inclusion tree. Te comprises an operation screen automatic generation processing unit to automatically generate the operation screen necessary to operate, and an operation console that displays (g) operation screen the operation screen automatic generation processing unit has generated.

[0010]

Next, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram of an embodiment of the present invention.

Referring to FIG. 1, a network management system 100 has an operation definition template 10 in advance.
3, a screen name data file 104, a management target inclusion tree 101, an operation screen automatic generation compiler 105, and an operation screen automatic generation processing unit 107, and are connected to the operation console 200. . The screen generation data file 106 is generated by the operation screen automatic generation compiler 105 from the contents of the operation definition template 103 and the screen name data file 104. The operation screen automatic generation processing unit 107 has a function of receiving an instruction from the operation console 200, automatically generating and displaying an operation screen, searching for the inclusion tree 101 to be managed, and searching for the screen generation data file 106.

FIG. 2 is a configuration diagram of the operation definition template 103.

Referring to FIG. 2, in the operation definition template 103, a MANAGED class template 103a is defined for each type of management object based on OSI management, and each class (a class is a term in OSI management. ATTRI) for the attributes and actions of the property, for example, the type of managed object having the attributes and actions.
BUTE (attribute) template 103b, ACTION
(Operation) The configuration is such that the template 103c is referred to.

The attribute template 103b indicates a data type (numerical value or character) for each attribute (in FIG. 2, it indicates "Attribute A" and "Attribute B"). Is defined as “INTEGER (integer value type)”. Also, the operations for these attributes are described in the MANAGED class template 103a (in FIG. 2, the operation “GET” for “attribute A” and the operation for “attribute B” are “SE”).
T ").

The operation template 103c includes a set of attributes (“WITH INFORMATION SYNTA”) required for requesting a management target for each operation (referring to “operation A” and “operation B” in FIG. 2).
X ”, and in FIG. 2,“ INTEGER ”
), A collection of attributes included in the response received from the management target (a description following “WITH REPLY SYNTAX”, which in FIG. 2 indicates “INTEGER”), and information on these attributes is required. Is referred to in accordance with the attribute template 103b.

FIG. 3 is a diagram showing the contents of the screen name data file 104. Referring to FIG. 3, the screen name data file 104 includes information (name, file name, and the like) required for displaying each attribute defined in the attribute template 103b and each operation defined in the operation template 103c. , Comments, etc.).

FIG. 4 is a conceptual diagram of the inclusion tree 101 to be managed. Referring to FIG. 4, the containment tree 101 is
Based on SI management, managed objects are arranged in a tree shape. The information of each object includes an identifier indicating an individual (referred to as a DN in OSI management) and a class ID indicating a type of a management target. The class ID is the class ID (in FIG. 2, shown in the MANAGED class template 103a of the operation definition template 103c.
"2-9-1003-2-45-600").

FIG. 5 shows a screen generation data file 106.
FIG. Referring to FIG. 5, the screen generation data file 106 has a class ID (“2-9 in FIG. 5”).
-1003-2-45-600 ”), the contents of the attribute template 103b and the operation template 103c for the attribute and operation used in the class.
And the contents of the screen name data file 104 are summarized.

Next, the operation of the embodiment of the present invention will be described with reference to FIG. 6 and FIG.

FIG. 6 shows a compiler 1 for automatically generating an operation screen.
It is an operation flowchart of 05. First, a screen generation data file 106 (hereinafter, "file 106") is newly opened (step A1 in FIG. 6). Next, the class ID is read from the MANAGED template 103a of the operation definition template 103 (step A2 in FIG. 6). If the class exists (NO in step A3 in FIG. 6), file 1
06, the class ID is registered (step A6 in FIG. 6), and the ATORIBUTE (attribute) of the class ID is set to MAN.
The data is read from the AGED template 103a (step A7 in FIG. 6). When there is an unread attribute (step A8 in FIG. 6)
NO), the matching attribute information is read out from the attribute template 103b and the screen name data file 104 (step A9 in FIG. 6) and written into the file 106 (step A10 in FIG. 6).

After completion of the above processing for the attribute of the class ID (YES in step A8 in FIG. 6),
ACTIO defined in ED template 103a
N (operation) is read (step A11 in FIG. 6).
If defined (NO in step A12 in FIG. 6), the operation template 103c and the operation template 103
The corresponding operation and attribute information are read from the attribute template 103b corresponding to the attribute name described in c (the attribute template 103b is not necessary in the example of FIG. 2) and the screen name data file 104, and Write to file 106 (steps A13, A1 in FIG. 6)
4, A15). If no definition has been made (YES in step A8 in FIG. 6), no processing is performed.

When the above process is performed on all the MANAGED templates 103a (Y in step A3 in FIG. 6)
ES), the file 106 is closed (Step A4 in FIG. 6), and the entire process is completed (Step A5 in FIG. 6).

FIG. 7 is an operation flowchart of the operation screen automatic generation processing unit 107. In accordance with an instruction from the operation console 200, the management server 200 searches the management target inclusion tree 101 (step B1 in FIG. 7) and determines an object to be operated (step B2 in FIG. 7). The class ID is acquired from the object information, and the screen generation data file 10
Then, all the information relating to the corresponding class ID is read out from Step 6 (Step B3 in FIG. 7). An operation screen is generated based on the read information and displayed on the operation console 200 (step B4 in FIG. 7).

Next, embodiments of the present invention will be described with reference to the drawings. FIG. 8 is an explanatory diagram showing a description example of the action definition template 103. Referring to FIG.
In the class A of the AGED class template 103a1, the attribute A and the attribute B, which can be GET (read), and the GET
-REPLACE (read and set) operable attribute C
There is an operation A as an ACTION (operation).
The attribute A is INTEGER (integer value) from the ATTRIBUTE (attribute) template 103b1 of the attribute A.

FIG. 9 is an explanatory diagram showing a description example of the screen name data file 104. Referring to FIG. 9, the screen name data file 104 describes display information such as a name for the attribute A, the number of display digits, and a comment.

FIG. 10 shows a screen generation data file 10 created by using an operation screen automatic generation compiler.
6 is an explanatory diagram showing a content example of No. 6. FIG.

Referring to FIG. 10, the generated screen generation data file 106 includes the templates shown in FIG.
The contents of the screen name data file 104 in FIG. 9 are passed to the operation screen automatic generation compiler 105, and all the information on the attributes and operations in class A is written out.

Next, the operation of the embodiment of the present invention will be described with reference to FIGS. FIG. 11 is an explanatory diagram showing an exchange between the operation console 200 and the operation screen automatic generation processing unit 107 that operates under the circumstances of FIGS. 8, 9, and 10. The management target inclusion tree 101 in FIG. 11 includes a class A object as a management target object. Referring to FIG. 11, an operation target object is specified from the operation console 200, and the operation screen automatic generation processing unit 107 searches the management target inclusion tree 101 to obtain the class ID of the specified object. Next, the screen generation data file 106 is searched to obtain information of the corresponding class.
An operation screen is generated and the screen is displayed on the operation console 200.

In the screen example of FIG. 11, the operation menu screen 110 is displayed first, and when one of the operations in the menu is selected, the corresponding operation screen is displayed. When the designated object is class A, the names of the attributes and actions are <device usage rate>, <registration number>, and <setting of allowable maximum usage rate>. The operation menu screen 110 displays these names and the like.
Display as When <device usage rate> is selected, the attribute operation screen 111 of the attribute A is displayed. When <setting of allowable maximum usage rate> is selected, the operation parameter setting screen 112 of the operation A and the operation execution The subsequent operation execution result screen 113 is displayed.

[0031]

The first effect is that the man-hour for developing the operation screen is reduced.

The reason is that, when describing the operation definition template, the operation screen is automatically generated only by describing the screen name data file in the same procedure. (1) The screen is created for each operation. There is no need to develop, (2) the screen layout of each screen is unified, so that it takes less time to check the layout compared to manual development, and (3) the same operation screen appears for the same attribute and the same operation. Therefore, there is no need to duplicate the screen development.

The second effect is that the quality of the developed system is improved.

The reasons are as follows: (1) In the case of a newly developed system, it is possible to take time for a quality check process such as an operation test by reducing the number of manufacturing steps, and (2) an operation screen adding work after the development is completed. In the case of, the operation definition template and the screen name data file are rewritten (additional description) and the operation screen automatic generation compiler is executed, so it can be handled simply by performing system generation work, so the additional screen itself needs to be developed. This is because maintainability is also improved by eliminating it.

[0035]

[Brief description of the drawings]

FIG. 1 is a block diagram of an embodiment of the present invention.

FIG. 2 is a configuration diagram of an operation definition template.

FIG. 3 is a diagram showing the contents of a screen name data file.

FIG. 4 is a conceptual diagram of a management target inclusion tree.

FIG. 5 is a diagram illustrating a content configuration of a screen generation data file.

FIG. 6 is an operation flowchart of an operation screen automatic generation compiler.

FIG. 7 is an operation flowchart of an operation screen automatic generation processing unit.

FIG. 8 is a configuration diagram of an example of an operation definition template.

FIG. 9 is a configuration diagram of an embodiment of a screen name data file.

FIG. 10 is an explanatory diagram showing the contents of a screen generation data file.

FIG. 11 is an explanatory diagram showing an exchange between an operation screen automatic generation processing unit and an operation console.

[Explanation of symbols]

 REFERENCE SIGNS LIST 100 network management system 101 managed inclusion tree 103 operation definition template 104 screen name data file 105 operation screen automatic generation compiler 106 screen generation data file 107 operation screen automatic generation processing unit 110 operation menu screen 111 attribute operation screen 112 operation Parameter setting screen 113 Operation execution result screen 200 Operation console

Continuation of front page (56) References JP-A-7-312596 (JP, A) JP-A-5-73495 (JP, A) JP-A-2-284264 (JP, A) JP-A-7-79245 (JP) , A) Japanese Patent Application Laid-Open No. 8-6883 (JP, A) "A method for constructing a service management software generation environment in advanced IN", IEICE Technical Report, SSE94-174 (1995-01), pp. 139-184. 49-54, "Integrated Management of Distributed LAN Domains Using OSI", Information Processing, June 1993, Vol. 34, no. 6, pp. 1426-1440 (58) Field surveyed (Int.Cl. ⁷ , DB name) G06F 9/06-9/54 G06F 3/00-3/14 G06F 13/00

Claims (1)

(57) [Claims] 1. A network conforming to an OSI management model.
Automatic operation screen generation system for
Te, the operation to define the attributes and behavior of a managed object
Definition template, the attributes and the attributes required when displaying the operation screen
Screen name data file that defines the name data of the operation
And the operation definition template and the screen name data
Compiler for automatically generating operation screens with file input
When, generated by the operation screen automatic generation compiler
A screen generation data file and a management pair defining an inclusion configuration of the managed object.
An elephant containment tree and a management pair to be operated on in the managed object containment tree.
When an elephant object is selected, the screen generation data
Corresponding to the managed object selected from the file
Automatically read the operation screen required for operation
An operation screen automatic generation processing unit to be generated and an operation screen generated by the operation screen automatic generation processing unit are displayed.
An operation screen having an operation console
Automatic surface generation system.