Information providing system having a network terminal and network management system which manages a network and provides information of the network to the network terminal

[0001] The present application is a continuation of application Ser. No. 10/026,830, filed Dec. 27, 2001; which is a continuation of application Ser. No. 09/516,500, filed Mar. 1, 2000, now U.S. Pat. No. 6,339,789; which is a continuation of application Ser. No. 09/027,202, filed Feb. 20, 1998, now U.S. Pat. No. 6,049,827, the contents of which are incorporated herein by reference.

BACKGROUND OF THE INVENTION

[0002] The present invention relates to a network management system for managing a network. More particularly, the present invention relates to a method, apparatus and computer program for allowing management of a network by use of network equipment, being managed on the network by a network management system, by preferentially displaying partial information related to the network equipment that is required for network management on the network equipment.

[0003] Generally, a network management system for collecting management information from each of plural network equipment existing in a network and storing the management information in the network management system is used for managing a network. Information required for network management including the collected management information is displayed by the network management system. Particularly, the network management information being displayed includes a configuration of the network being managed in the form of a map in which the network is schematically shown.

[0004] A network is divided into hierarchies such as geographical classification, management classification and detailed information and is displayed in the form of a map having a plurality of hierarchical levels as described on pages 60 to 65 in “Hewlet-Packard Journal”, April 1990. Such is performed so that a management operator can readily grasp a large-scale complicated network configuration at an instant. A technique for changing displayed contents of a configuration according to a management operator in consideration of a case that a network management system is used by plural managers is disclosed in Japanese published unexamined patent application No. 7-312596. A technique for enabling an arbitrary computer except a network management system, to access the same contents as contents displayed by the network management system utilizing a web browser is disclosed on pages 38 and 39 in “Nikkei Computer” November 11 Appendix 1996 as a type of network management in the environment of an Internet/intranetwork. However, in such a technique, a web browser which can access only one screen at a time cannot access plural maps simultaneously when, for example, in case a network management system displays a map for each hierarchy level. Thus, there is a problem that the display of a network configuration using a web browser is difficult to grasp. The utilization of a web browser allows network equipment which is managed by a network management system, to access the same contents displayed by the network management system and to execute network management.

[0005] For a user who executes network management via network equipment which is managed by a network management system may be either an end user or a management operator. However, an end user often requires partial information related to the managed network equipment being used of information required for network management. Similarly, a management operator may also require partial information related to the managed networks equipment being used. Such partial information is not supplied. Thus, a user who uses managed equipment is required to find the partial information related to the managed equipment being used. That is, the user must find partial information corresponding to the same contents as that displayed by a network management system. However, as the information volume of contents displayed by a network management system is enormous, the operation to find such partial information is very burdensome.

[0006] In conventional apparatus disclosed in Japanese published unexamined patent application No. 7-312596, only a change in the displayed contents performed by a management operator at, for example, a network management system which manages network equipment on a network are effected. Thus, when a management operator executes network management via a managed network equipment on the network the contents of the display are not changed.

SUMMARY OF THE INVENTION

[0007] An object of the present invention is to enable preferentially displaying partial information, related to network equipment being managed on the network by a network management system, equipment of information required for network management when network management is to be executed on the network equipment.

[0008] To achieve the above object, the present invention provides a network which is managed by a network management system. The network management system collects management information from each of a plurality of network equipment existing in the network and stores the management information collected from the plural network equipment. Network management of the network can be accomplished in response to a request from one of the network equipment by accessing the network management system and causing the network management system to transfer a program for managing the network to the network equipment requesting network management. The network equipment requesting network management informs the network management system of identification information for identifying the network equipment using the transferred program. The network management system then transfers partial information related to the network equipment as indicated by the identification information. The partial information includes information required for network management by the network equipment. The network equipment then displays the transferred partial information.

[0009] According to the present invention since partial information related to the network equipment requesting network management is transferred from the network management system to the network equipment and displayed on the network equipment, a user is not required to find partial information related to the network equipment being used. Therefore, the user can immediately execute network management.

[0010] If a browser has been installed in the network equipment and a program for managing a network has not been installed in the network equipment, then the network equipment can still effect management of the network according to the present invention. In the present invention the network equipment displays partial information obtained by a program for managing a network transferred from a network management system. Thus, a user can execute network management via the network equipment utilizing the browser. Therefore, the present invention provides a network management tool that can be installed in a network management system.

[0011] It should be noted that the present invention can be implemented using a computer program written in the JAVA programming language (JAVA is a trademark of Sun Microsystems Inc.) or the ACTIVE X programming language (ACTIVE X is a trademark of Microsoft Inc.). The ACTIVE X programming language is similar in operation to the JAVA programming language. In the present invention the program transferred from the network management system to the network equipment requesting network management can be written in the form of an “Applet” which causes the display of the partial information on the network equipment. An Applet is a special program transferable on a network that can be executed in the receiving computer. The Applet is activated when transferred from the network management system to the network equipment.

[0012] A first embodiment of the present invention provides a network management tool that can be installed in a network management system for collecting management information from each of a plurality of network equipment connected to a network, storing the management information therein and displaying the configuration of the network in the form of a plurality of hierarchically arranged maps. The network management system includes a display program which is activated when it is transferred to a network equipment. The display program, which can be an Applet in the JAVA or ACTIVE X programming languages, causes the display of information required for network management on a network equipment requesting network management of the network. The network management system also includes a transfer program for transferring the display program to the network equipment requesting management (hereinafter called “management request equipment”) and an information program for informing the display program transferred to the management request equipment of information required for display to effect network management.

[0013] The first embodiment of the present invention also provides a managed terminal included in each of the network equipment connected to the network. The managed terminal includes a transfer request program for requesting transfer of the display program when network management is to be conducted from the network equipment in which the managed terminal is installed.

[0014] The information program of the network management system executes processing for generating inclusive relationship information showing inclusive relationships among components on the network related to the network equipment specified by the display program transferred to the management request equipment. The network equipment is included in the hierarchically arranged maps that the network management system displays. The information program informs the display program of the generated inclusive relationship information. The display program executes processing for specifying the management request equipment by collecting identification information for identifying the management request equipment, informing the information program of the collected identification information and causing the display of a partial network configuration related to the management request equipment in the form of an inclusive tree based upon the inclusive relationship information informed by the information program.

[0015] According to the first embodiment, the partial network configuration related to the management request equipment can be preferentially displayed on the management request equipment. Particularly, as the hierarchically arranged maps are displayed in the form of an inclusive tree shown on one screen in the management request equipment, a user using the management request equipment can readily grasp the partial network configuration related to the management request equipment. Management in the above-described manner can be effected even if a browser being used can access only one screen at a time.

[0016] If a partial network configuration related to the management request equipment is not necessarily required to be displayed on one screen, the network management system may be constructed so that the information program executes processing for informing the display program of a partial map related to the network equipment specified by the display program transferred to the management request equipment. The display program executes processing for specifying the management request equipment by collecting identification information for identifying the management request equipment and informing the information program of the collected identification information. Thereafter the display program executes a processing for causing the display of the partial map as informed by the information program.

[0017] Also, if one screen is used and partial network configuration related to the management request equipment is not necessarily required to be displayed, the network management system may be constructed so that the information program executes processing for generating inclusive relationship information showing inclusive relationships among components included in each of the hierarchically arranged maps that the network management system displays. The information program also executes a processing for informing the display program of the generated inclusive relationship information. The display program executes processing for causing the display of the configuration of the network in the form of an inclusive tree based upon the inclusive relationship information from the information program.

[0018] In the above-described first embodiment, the display program can further execute a processing for causing the deletion of components selected by an external device if the selected components are shown in an inclusive tree, a processing for acquiring the inclusive relationship information from the information program of components selected by an external device not shown in an inclusive tree and a processing for causing the addition of a partial network configuration, related to a selected component of an inclusive tree, to the inclusive relationship information from the information program. The partial network configuration is obtained in response to a request for inclusive relationship information.

[0019] The information program can further execute a processing for generating inclusive relationship information showing inclusive relationships among components. The inclusive relationship information is required by the display program which causes the display of components included in each of the hierarchically arranged maps that a network management system displays and requested by the management request equipment for network management. The information program also executes a processing for informing the display program of the generated inclusive relationship information. Using the above-described features of the present invention a user of the management request equipment can delete an unnecessary part of the information being displayed and can add information to a part of the information being displayed deemed insufficient.

[0020] Further, in the above-described first embodiment, the information program can further execute a processing for calculating the number of components included in a map of a lower order level of the hierarchically arranged maps. The components correspond to components in each of the higher order level maps. The hierarchically arranged maps are displayed by the network management system. The components of the lower order level maps are hereinafter called “lower order components”. The information program also executes a processing of informing the display program transferred to the management request equipment of the calculated number of low order components. The display program executes a processing for causing the display of the number of lower order components from the information program together with all of the components shown in an inclusive tree. Using the above-described features of the present invention a user of the management request equipment can be informed of the number of components included in each of the components included in an inclusive tree by seeing the displayed number of lower order components.

[0021] Further, in the above-described first embodiment, the display program can further execute a processing for causing a part of the information displayed on the management request equipment related to the management request equipment to be highlighted. Using the above-described features of the present invention a user of the management request equipment can readily find a part related to the management request equipment within the displayed information.

[0022] A second embodiment of the present invention, similar to the first embodiment, provides a network management tool having a network management system and a managed terminal included in each of the network equipment as described above. However, the configuration of the network management system in the second embodiment is different from the first embodiment in that the network management system periodically collects event information from each of the network equipment connected to the network. The event information collected from the network equipment is stored in the network management system as an event log which includes information concerning the IP address of the network equipment in which an event has occurred, the time of the event, and information concerning the type of event. The display program when transferred to the management request equipment and activated by the transfer is informed of event information by the network management system. Thereafter the display program causes the display of event information from the network management system related to the management request equipment so as to permit network management. The second embodiment allows a user to expand the details of the event information being displayed on the management request equipment.

[0023] A third embodiment of the present invention, similar to the first embodiment, provides a network management tool having a network management system and a managed terminal included in each of the network equipment as described above. However the configuration of the network management system in the third embodiment is different from that in the first embodiment in that the network management system allows for retrieval of management information which satisfies a particular retrieval condition set by a user at a managed terminal which is included in a network equipment management request equipment. The management information which satisfies the set retrieval condition is management information related to the management request equipment. The user when using the managed terminal in the third embodiment may set the attribute of a retrieval condition through a retrieval screen displayed on the management request equipment.

[0024] A fourth embodiment of the present invention, similar to the first embodiment, provides a network management tool having a network management system and a managed terminal included in each of the network equipment as described above. However, the configuration of the network management system is different from that in the first embodiment in that a network management system determines the performance capabilities of the management request equipment and transfers an amount of management information to the management request equipment according to the determined performance capabilities. This feature of the fourth embodiment allows for the details of the display of management information to be set in accordance with the performance capabilities of the management request equipment.

BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The present invention will be more apparent from the following detailed description, when taken in conjunction with the accompanying drawings, in which:

[0026]FIG. 1 is a block diagram illustrating the configuration of a network management system and a managed terminal respectively equivalent to a first embodiment;

[0027]FIG. 2 is an explanatory drawing illustrating an example of the configuration of a network managed by the network management system;

[0028]FIG. 3 is an explanatory drawing illustrating the construction of a management information table in the first embodiment;

[0029]FIG. 4 is an explanatory drawing illustrating a hierarchical map displayed on the display of the network management system;

[0030]FIG. 5 is an explanatory drawing illustrating a configuration information table in the first embodiment;

[0031]FIG. 6 is a flowchart illustrating the outline of the operation of the network management system and the managed terminal in the first embodiment;

[0032]FIG. 7 is an explanatory drawing illustrating a state after a configuration information display program is transferred to the managed terminal in the first embodiment;

[0033]FIG. 8 is a flowchart illustrating the outline of the operation of the filtering section of a configuration information filtering program in the first embodiment;

[0034]FIG. 9 is an explanatory drawing illustrating a hierarchical information table in the first embodiment;

[0035]FIG. 10 is a flowchart illustrating the outline of the operation of the hierarchical symbol acquiring section of the configuration information filtering program in the first embodiment;

[0036]FIG. 11 is an explanatory drawing illustrating a display information table in the first embodiment;

[0037]FIG. 12 is a flowchart illustrating the outline of the operation of the configuration information display section of the configuration information display program in the first embodiment;

[0038]FIG. 13 is an explanatory drawing illustrating the construction of a configuration information internal table in the first embodiment;

[0039]FIG. 14 is an explanatory drawing illustrating a class/icon relating internal table in the first embodiment;

[0040]FIG. 15 is an explanatory drawing illustrating a state/icon color relating internal table in the first embodiment;

[0041]FIG. 16 is an explanatory drawing illustrating contents displayed on an inclusive tree screen in the first embodiment;

[0042]FIG. 17 is a flowchart illustrating the outline of symbol expanding/closing processing executed by the configuration information display section of the configuration information display program in the first embodiment;

[0043]FIG. 18 is an explanatory drawing illustrating contents displayed on the inclusive tree screen after symbol expanding processing is executed in the first embodiment;

[0044]FIG. 19 is an explanatory drawing illustrating contents displayed on the inclusive tree screen after symbol closing processing is executed in the first embodiment;

[0045]FIG. 20 is a block diagram illustrating the configuration of a network management system and a managed terminal respectively equivalent to a second embodiment;

[0046]FIG. 21 is an explanatory drawing illustrating an event information table in the second embodiment;

[0047]FIG. 22 is a flowchart illustrating the outline of the operation of the filtering section of an event information retrieval program in the second embodiment;

[0048]FIG. 23 is an explanatory drawing illustrating contents displayed on an event display screen in the second embodiment;

[0049]FIG. 24 is a flowchart illustrating the outline of enlargement processing executed by the retrieval and enlargement section of the event information retrieval program in the second embodiment;

[0050]FIG. 25 is a flowchart illustrating the outline of additional display processing executed by the event information display section of an event information display program in the second embodiment;

[0051]FIG. 26 is an explanatory drawing illustrating contents displayed on the event display screen after additional display processing is executed in the second embodiment;

[0052]FIG. 27 is a block diagram illustrating the construction of a network management system and a managed terminal respectively equivalent to a third embodiment;

[0053]FIG. 28 is an explanatory drawing illustrating contents displayed on a retrieval screen in the third embodiment;

[0054]FIG. 29 is a flowchart illustrating the outline of the operation of a management information sort program in the third embodiment;

[0055]FIG. 30 is a block diagram illustrating the configuration of a network management system and a managed terminal respectively of a fourth embodiment;

[0056]FIG. 31 is an explanatory drawing illustrating an each device display contents determining table in the fourth embodiment;

[0057]FIG. 32 is a flowchart illustrating the outline of the operation of the network management system and the managed terminal in the fourth embodiment;

[0058]FIG. 33 is an explanatory drawing illustrating a reconstituted display information table in the fourth embodiment; and

[0059]FIG. 34 is an explanatory drawing illustrating contents displayed on an inclusive tree screen displayed in the fourth embodiment.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0060] Referring to the drawings, embodiments to which a network management tool according to the present invention is applied will be described below.

[0061] First, referring to FIGS. <b>1</b> to <b>17</b>, a first embodiment of the present invention will be described.

[0062] The first embodiment enables partial network configuration related to a network equipment to be preferentially displayed in the form of a containment tree if network management is executed from an arbitrary network equipment provided with a display function (hereinafter called a managed terminal) which is equipment managed by a network management system.

[0063]FIG. 1 is a block diagram showing the configuration of a network management system and a managed terminal respectively equivalent to the first embodiment. As shown in FIG. 1, a reference number <b>10</b> denotes a network management system which collects management information from each of a plurality of network equipment <b>201</b> and <b>202</b> defined as managed equipment including, for example, a computer or a transfer equipment connected to a network <b>200</b> as shown in FIG. 2. Upon collecting the management information, the network management system <b>10</b> stores the management information therein. As also shown in FIG. 1, a reference number <b>20</b> denotes a managed terminal which is included in each network equipment <b>201</b> and <b>202</b> as shown in FIG. 2.

[0064] As shown in FIG. 1, the network management system <b>10</b> is provided with a communication control unit <b>11</b> for controlling communication between the network management system <b>10</b> and the network equipment <b>201</b> and/or <b>202</b> represented by the managed terminal <b>20</b>, a database <b>110</b> for storing a management information table <b>111</b> which stores management information collected from each of the network equipment <b>201</b> and <b>202</b> and a configuration information table <b>112</b> which stores configuration information required for displaying the configuration of the network <b>200</b>, a work memory <b>12</b> which functions as an operation area when a processing is conducted for storing information in the database <b>110</b> and a temporary storage area when a processing is conducted for retrieving required information from the database <b>110</b>, a program memory <b>13</b> for storing a management information collection program <b>131</b>, a configuration information filtering program <b>133</b>, a configuration information display program <b>136</b> and a transfer program <b>137</b>, and a central processing unit (CPU) <b>14</b> for controlling access to the work memory <b>12</b> and the database <b>110</b> and for executing each of the programs in the program memory <b>13</b>. Further, the network management system <b>10</b> is provided with a keyboard <b>15</b>, a mouse <b>16</b>, a display <b>17</b> and an input-output controller <b>18</b> for controlling the input-output of data to and from these elements.

[0065] The management information collection program <b>131</b> is a program for collecting management information from each of the computers <b>201</b> and <b>202</b> which are managed equipment and managing the registration/update of management information in the management information table <b>111</b>. The configuration information filtering program <b>133</b> is a program for acquiring configuration information required for displaying partial network configuration related to the managed terminal <b>20</b> and is provided with a filtering section <b>132</b> and hierarchical symbol acquiring section <b>138</b>. The configuration information display program <b>136</b> is a program transferred to the managed terminal <b>20</b> and activated in the managed terminal <b>20</b> for causing the display of partial network configuration related to the managed terminal <b>20</b> on the managed terminal <b>20</b> and is provided with a terminal information gathering section <b>134</b> and a configuration information display section <b>135</b>. The transfer program <b>137</b> is a program for transferring the configuration information display program <b>136</b> to the managed terminal <b>20</b>.

[0066] The configuration information display program <b>136</b> can be what is known in the art as an Applet which is a type of program transferable across networks according to the JAVA or the ACTIVE X programming languages. JAVA is a trademark of Sun Microsystems Inc., an ACTIVE X is a trademark of Microsoft Inc.

[0067] As shown in FIG. 1, the managed terminal <b>20</b> is provided with a communication control unit <b>21</b> for controlling communication between the managed terminal <b>20</b> and the network management system <b>10</b>, a work memory <b>22</b> which functions as an operation area when the configuration information display program <b>136</b> transferred from the network management system <b>10</b> is executed, a program memory <b>23</b> in which a transfer request program <b>24</b> for requesting the network management system <b>10</b> to transfer the configuration information display program <b>136</b> is stored and a CPU <b>29</b> for controlling access to the work memory <b>22</b> and for executing each of the programs stored in the program memory <b>23</b>. Further, the managed terminal <b>20</b> is provided with a keyboard <b>26</b>, a mouse <b>27</b>, a display <b>25</b> and an input-output controller <b>28</b> for controlling the input-output of data to and from these elements.

[0068] In the network management system <b>10</b>, CPU <b>14</b> periodically collects management information from each of the network equipment <b>201</b> and <b>202</b> represented by the managed terminal <b>20</b> via the communication control unit <b>11</b> and stores the collected management information in the management information table <b>111</b> by executing the management information collection program <b>131</b>.

[0069]FIG. 3 shows an example of the construction of the management information table <b>111</b>. For the purpose of example a TCP/IP communication protocol is used in the network <b>200</b>. Any other communication protocol can be used. As shown in FIG. 3, the management information table <b>111</b> includes for each identifier <b>302</b> of managed equipment representing network equipment <b>201</b> and <b>202</b>, the host name <b>303</b> of managed equipment and the IP address <b>304</b> of the managed equipment.

[0070] Further, CPU <b>14</b> displays a map hierarchically representing the configuration of the network <b>200</b> geographically expanded as shown in FIG. 4 for example based upon management information stored in the management information table <b>111</b> on the display <b>17</b>. As shown in FIG. 4, a reference number <b>401</b> denotes a map showing the whole configuration, for example, at a country level of the network <b>200</b>. The detailed configuration of the network <b>200</b> is hierarchically represented by sequentially pulling down from the map <b>401</b> to a map <b>402</b> showing partial configuration at, for example, an area level and a map <b>403</b> showing partial configuration at, for example, a site level. A table used when these maps <b>401</b> to <b>403</b> are displayed is the configuration information table <b>112</b> as shown in FIG. 5.

[0071] The configuration information table <b>112</b> includes for each identifier <b>502</b> of managed equipment representing the network equipment <b>201</b> and <b>202</b>, the name <b>503</b> of a symbol, a high order symbol <b>504</b> which is the identifier of a symbol included in a high order level of a map, the corresponding node <b>505</b> which is the identifier of managed equipment shown by the symbol, the state <b>506</b> of the managed equipment shown by the symbol and the class <b>507</b> of the managed equipment shown by the symbol for each identifier <b>502</b>. Each symbol <b>503</b> represents, for example, a managed equipment <b>20</b> for representing network equipment <b>201</b> and <b>202</b> included in the map <b>401</b> displayed as shown in FIG. 4 based upon management information stored in the management information table <b>111</b>.

[0072] The operation of the first embodiment will be described below.

[0073]FIG. 6 is a flowchart showing the outline of the operation of the network management system <b>10</b> and the managed terminal <b>20</b>. It should be noted that each of the steps of the flowchart correspond to code of a computer program.

[0074] As shown in FIG. 6, when a user instructs the managed terminal <b>20</b> to execute network management, first, the transfer request program <b>24</b> informs the transfer program <b>137</b> of the network management system <b>10</b> of a request for transferring the configuration information display program <b>136</b> (step <b>601</b>). When the transfer program <b>137</b> receives the request for transferring the configuration information display program <b>136</b> from the managed terminal <b>20</b>, the transfer program <b>137</b> transfers the configuration information display program <b>136</b> stored in the program memory <b>13</b> to the work memory <b>22</b> of the managed terminal <b>20</b> (step <b>602</b>).

[0075] When the configuration information display program <b>136</b> is transferred from the network management system <b>10</b> to the work memory <b>22</b>, it is automatically activated. FIG. 7 shows the state of the managed terminal <b>20</b> after the configuration information display program <b>136</b> has been transferred to the work memory <b>22</b> of the managed terminal <b>20</b>. When the configuration information display program <b>136</b> is activated in the managed terminal <b>20</b>, first, the terminal information gathering section <b>134</b> acquires the IP address of the managed terminal <b>20</b> and informs the configuration information filtering program <b>133</b> of the network management system <b>10</b> of the request for transferring configuration information together with the acquired IP address (step <b>603</b>).

[0076] As an alternative to the acquiring of the IP address of the managed terminal <b>20</b> the terminal information gathering section <b>134</b> can be included in the configuration information filtering program <b>133</b> on the network management system <b>10</b>. The terminal information gathering section <b>134</b> of this construction acquires the IP address of the managed terminal from a transfer log provided in the network management system <b>10</b>. The transfer log has stored therein log records providing information of the terminal that requested transfer of the configuration information display program <b>136</b>. The log records are caused to be generated by the transfer program <b>137</b> when the transfer program <b>137</b> transfers the configuration information display program <b>136</b> to the managed terminal <b>20</b>.

[0077] When the configuration information filtering program <b>133</b> receives the request for transferring configuration information and the IP address from the managed terminal <b>20</b>, the configuration information filtering program <b>33</b> acquires hierarchical information showing a location in a map including the symbol of the managed terminal <b>20</b> by filtering required information from the configuration information table <b>112</b> based upon the received IP address, and informs the configuration information display program <b>136</b> of the managed terminal <b>20</b> of the acquired hierarchical information (step <b>604</b>).

[0078]FIG. 8 is a flowchart showing the outline of the operation of the filtering section <b>132</b> of the configuration information filtering program <b>133</b>. It should be noted that each of the steps of the flowchart corresponds to code of a computer program.

[0079] As shown in FIG. 8, the filtering section <b>132</b> first retrieves an IP address <b>304</b> equal to the IP address received from the managed terminal <b>20</b> from the management information table <b>111</b> and acquires for selecting an identifier <b>302</b> corresponding to the retrieved IP address <b>304</b>, that is, the identifier <b>302</b> of the managed terminal <b>20</b> (step <b>801</b>). Next, the filtering section <b>132</b> acquires a symbol having the identifier <b>302</b> acquired in step <b>801</b> as the corresponding node <b>505</b>, that is, the symbol of the managed terminal <b>20</b> from the configuration information table <b>112</b> (step <b>802</b>). Next, the filtering section <b>132</b> specifies the symbol of the managed terminal <b>20</b> acquired in step <b>802</b> for a symbol to be acquired and stores the symbol information of the acquired symbol in a hierarchical information table <b>901</b> shown in FIG. 9 (step <b>803</b>).

[0080] As shown in FIG. 9, contents stored as symbol information includes the identifier <b>902</b> of an acquired symbol, the symbol name <b>903</b> of the acquired symbol, the state <b>904</b> of managed terminal shown by the acquired symbol, the class <b>905</b> of the managed terminal shown by the acquired symbol and the number of subordinate symbols <b>906</b> which is the number of symbols included in lower order levels of the map under the acquired symbol. The information <b>902</b> to <b>905</b> except the number of subordinate symbols <b>906</b>, are transferred from the configuration information table <b>112</b>. The number of subordinate symbols <b>906</b> can be acquired by checking the number of symbols the high order symbol <b>504</b> of which is a symbol to be acquired in the configuration information table <b>112</b> (step <b>804</b>).

[0081] When the symbol information of the acquired symbol is stored in the hierarchical information table <b>901</b> as described above, the filtering section <b>132</b> specifies that high order symbols <b>504</b> be acquired and stored in the hierarchical information table <b>901</b> (step <b>805</b>).

[0082] If a higher order symbol exist, then steps <b>803</b> to <b>805</b> are repeated until no high order symbol <b>504</b> exists (step <b>806</b>). If no higher order symbols <b>504</b> exist then the hierarchical information table <b>901</b> showing location in a map including the symbol of the managed terminal <b>20</b> is generated. When the generation of the hierarchical information table <b>901</b> is finished, the filtering section <b>132</b> informs the configuration information display section <b>135</b> of the managed terminal <b>20</b> of the generated hierarchical information table <b>901</b> (step <b>807</b>).

[0083] When the configuration information display section <b>135</b> receives the hierarchical information table <b>901</b> from the filtering section <b>132</b> of the network management system <b>10</b> as shown in FIG. 6, the configuration information display section <b>135</b> stores the received hierarchical information table <b>901</b> in the work memory <b>22</b> and informs the configuration information filtering program <b>133</b> of the network management system <b>10</b> of a request for transferring configuration information together with the identifier <b>902</b> of a symbol in a higher order level of the map of the managed terminal <b>20</b> in the hierarchical information table <b>901</b> (a step <b>605</b>). When the configuration information filtering program <b>133</b> receives the request for transferring configuration information and the identifier <b>902</b> of the symbol from the managed terminal <b>20</b>, configuration filtering program <b>133</b> informs the configuration information display section <b>135</b> of the managed terminal <b>20</b> of all symbols included in maps of lower order levels related to a symbol shown by the received identifier <b>902</b> by the hierarchical symbol acquiring section <b>138</b>. That is, all symbols included in lower order level maps related to the symbol of the managed terminal <b>20</b> (a step <b>606</b>) are informed.

[0084]FIG. 10 is a flowchart showing the outline of the operation of the hierarchical symbol acquiring section <b>138</b> of the configuration information filtering program <b>133</b>. It should be noted that each of the steps of the flowchart corresponds to code of a computer program.

[0085] As shown in FIG. 10, the hierarchical symbol acquiring section <b>138</b> extracts a symbol having the identifier <b>902</b> of a symbol received from the managed terminal <b>20</b> as a high order symbol <b>504</b> from the configuration information table <b>112</b> (step <b>1001</b>). Next, the hierarchical symbol acquiring section <b>138</b> specifies the symbol extracted in the step <b>1001</b> for a symbol to be acquired and stores symbol information of the acquired symbol in a display information table <b>1101</b> shown in FIG. 11 (step <b>1002</b>).

[0086] As shown in FIG. 11, the display information table <b>1101</b> includes symbol information consisting of an identifier <b>1102</b> of an acquired symbol, a symbol name <b>1103</b> of the acquired symbol, a class <b>1104</b> of managed equipment shown by the acquired symbol, a state <b>1105</b> of the managed equipment shown by the acquired symbol and the number of subordinate symbols <b>1106</b> which is the number of symbols included in lower order level maps under the acquired symbol. The information <b>1102</b> to <b>1105</b>, except the number of subordinate symbols <b>1106</b>, are picked up from the configuration information table <b>112</b>. The number of subordinate symbols <b>1106</b> can be acquired by checking the number of symbols the high order symbol <b>504</b> of which is an acquired symbol in the configuration information table <b>112</b> (step <b>1003</b>).

[0087] When the symbol information of the acquired symbol is stored in the display information table <b>1101</b> as described above, the hierarchical symbol acquiring section <b>138</b> returns processing to step <b>1001</b> to store the symbol information of the following symbols in the display information table <b>1101</b> until no other symbol having the identifier <b>902</b> of the symbol received from the managed terminal <b>20</b> as a high order symbol <b>504</b> exists (step <b>1004</b>). When the steps <b>1001</b> to <b>1004</b> are repeated, the display information table <b>1101</b> in which the symbol information of all symbols included in a map including the symbol of the managed terminal <b>20</b> is stored is generated. When the generation of the display information table is finished, the hierarchical symbol acquiring section <b>138</b> informs the configuration information display section <b>135</b> of the managed terminal <b>20</b> of the generated display information table <b>1101</b> (step <b>1005</b>).

[0088] As shown in FIG. 6, in the managed terminal <b>20</b>, when the configuration information display section <b>135</b> of the configuration information display program <b>136</b> receives the display information table <b>1101</b> from the hierarchical symbol acquiring section <b>138</b> of the network management system <b>10</b>, the configuration information display section <b>135</b> causes the display of a partial network configuration related to the managed terminal <b>20</b> in the form of an containment tree based upon the hierarchical information table <b>901</b> and the display information table <b>1101</b> (step <b>607</b>). The display information table <b>1101</b> and the hierarchical information table <b>901</b> stored in the work memory <b>22</b> in the step <b>605</b> are equivalent to containment relationship information showing containment relationship among symbols related to the managed terminal <b>20</b>.

[0089]FIG. 12 is a flowchart showing the outline of the operation of the configuration information display section <b>135</b> of the configuration information display program <b>136</b>. It should be noted that each of the steps of the flowchart corresponds to code of a computer program.

[0090] As shown in FIG. 12, the configuration information display section <b>135</b> first generates a configuration information internal table <b>1301</b> shown in FIG. 13 based upon the received display information table <b>1101</b> and the hierarchical information table <b>901</b> stored in the work memory <b>22</b> (step <b>1201</b>). FIG. 13 shows the construction of the configuration information internal table <b>1301</b>.

[0091] As shown in FIG. 13, the configuration information internal table <b>1301</b> includes for each identifier <b>1302</b>, a class <b>1303</b> of managed equipment shown by a symbol, a state <b>1304</b> of the managed equipment shown by the symbol, a symbol name <b>1305</b> of the symbol, a hierarchy <b>1306</b> of the symbol, a number of symbols under the symbol <b>1307</b> and a high order symbol <b>1308</b>. Symbols of each identifier <b>1302</b> are displayed in the form of an containment tree. In the configuration information internal table <b>1301</b>, a symbol the identifier <b>1302</b> of which is zero, ‘0’ is definitely set beforehand so that the corresponding class <b>1303</b> and symbol name <b>1305</b> are a root <b>1309</b>. A symbol which is the root <b>1309</b> is located at the highest order of all symbols and therefore, a hierarchy <b>1306</b> corresponding to the symbol is set to zero, “0”. Also, the information <b>1302</b> to <b>1305</b> and <b>1307</b>, except the hierarchy <b>1306</b> and the high order symbol <b>1308</b> are transferred from the hierarchical information table <b>901</b> or the display information table <b>1101</b>.

[0092] However, the configuration information display section <b>135</b> stores a value showing the number of low order symbols <b>1307</b> relative to the symbol which is the root <b>1309</b> in the field of the hierarchy <b>1306</b> according to hierarchical relationship shown in the hierarchical information table <b>901</b> and stores the identifier of a symbol in a high order by one in the field of the high order symbol <b>1308</b>.

[0093] Next, the configuration information display section <b>135</b> locates each of the symbols to be displayed in an inclusive tree based upon the contents of the configuration information internal table <b>1301</b> generated in the step <b>1201</b> by repeating the steps <b>1202</b> to <b>1211</b>. That is, first, the configuration information display section <b>135</b> generates the symbol image <b>1602</b> of the symbol which is the root <b>1309</b>, locates the generated symbol image <b>1602</b> in a predetermined position on an inclusive tree screen <b>1601</b> shown in FIG. 16 and respectively sets initial values y1 and x1 having the location as an origin at an x-coordinate <b>1603</b> and at a y-coordinate <b>1604</b> (step <b>1202</b>). The x-coordinate <b>1603</b> and the y-coordinate <b>1604</b> at which the initial values are set show positions in which the symbol image of a symbol in a low order by one of the symbol which is the root <b>1309</b> is to be located.

[0094] Next, the configuration information display section <b>135</b> retrieves a symbol of the identifier of the high order symbol <b>1308</b> of which is equal to the identifier <b>1302</b> of the symbol which is the root <b>1309</b> from the configuration information internal table <b>1301</b> (step <b>1203</b>), generates the symbol image of the retrieved symbol and locates the generated symbol image in a position shown by values set at an x-coordinate <b>1603</b> and at a y-coordinate <b>1604</b> on the inclusive tree screen <b>1601</b> (step <b>1204</b>).

[0095] The details of step <b>1204</b> provides that the configuration information display section <b>135</b> determines the icon format of an acquired symbol based upon the contents of a class/icon relating internal table <b>1401</b> which stores relationships between the class <b>1402</b> of managed equipment shown by the symbol and an icon format <b>1403</b> shown in FIG. 14. The configuration information display section <b>135</b> determines the color of the determined icon format based upon the contents of a state/icon color relating internal table <b>1501</b> which stores relationship information indicating relationships between the state <b>1501</b> of the managed equipment shown by the acquired symbol and an icon color <b>1502</b> shown in FIG. 15. Further, the configuration information display section <b>135</b> creates symbol images <b>1605</b> and <b>1606</b> shown in FIG. 16 by adding a symbol name <b>1305</b> and the number of subordinate symbols <b>1307</b>. Finally, the configuration information display section <b>135</b> locates the created symbol images <b>1605</b> and <b>1606</b> in positions shown by the respective values set at an x-coordinate <b>1603</b> and at a y-coordinate <b>1604</b> on the inclusive tree screen <b>1601</b>.

[0096] Next, the configuration information display section <b>135</b> adds a predetermined value y1 to a value at a y-coordinate <b>1604</b> in a step <b>1205</b> and judges whether a symbol in a lower order level of the maps related to the symbol image of which is located in the step <b>1204</b> exists or not (step <b>1206</b>). The judgment can be executed by retrieving a symbol, the higher order symbol of which has the identifier <b>1302</b>, of the symbol image of which is located in the step <b>1204</b> for example. If such a symbol exists, the configuration information display section <b>135</b> returns processing to step <b>1204</b> after adding a predetermined value x1 to a value at an x-coordinate <b>1603</b> (step <b>1207</b>).

[0097] If no such symbol exists, the configuration information display section <b>135</b> judges whether a symbol in a higher order level of the map related to the symbol image of which is located in step <b>1204</b> exists or not (step <b>1208</b>). The judgment can be executed by retrieving a symbol having the same symbol as the higher order symbol <b>1308</b> of the symbol, the symbol image of which, is located in step <b>1204</b> as a high order symbol <b>1308</b> for example. If such a symbol exists, the configuration information display section <b>135</b> returns processing to step <b>1204</b>, generates and locates the symbol image of such a symbol. If no such symbol exists, the configuration information display section subtracts a predetermined value x1 from a value at an x-coordinate <b>1603</b> (step <b>1209</b>), next retrieves a symbol having the higher order symbol <b>1308</b> of the symbol retrieved in step <b>1208</b> as the identifier <b>1302</b> (step <b>1210</b>), repeats processing until a symbol to be next retrieved is the symbol which is the root <b>1309</b> (step <b>1211</b>) and returns processing to step <b>1208</b>.

[0098] Thus, if a symbol to be next retrieved is the symbol which is the root <b>1309</b> (step <b>1211</b>), the symbol images <b>1602</b>, <b>1605</b> and <b>1606</b> of all symbols to be displayed in an inclusive tree are located on the inclusive tree screen <b>1601</b>. Afterward, the configuration information display section <b>135</b> completes the inclusive tree screen <b>1601</b> by connecting the symbol images <b>1602</b>, <b>1605</b> and <b>1606</b> located on the inclusive tree screen <b>1601</b> (step <b>1212</b>). It is desirable that the configuration information display section <b>135</b> causes the symbol image <b>1606</b> equivalent to the managed terminal <b>20</b> on the inclusive tree screen <b>1601</b> shown in FIG. 16 to be highlighted (step <b>1213</b>).

[0099] As described above, according to the first embodiment, if network management is executed from the managed terminal <b>20</b>, which is equipment managed by the network management system <b>10</b>, a user who uses the managed terminal <b>20</b> is not required to retrieve the symbol of the managed terminal <b>20</b>. Therefore, the user can immediately execute network management because partial network configuration related to the managed terminal <b>20</b> can be preferentially displayed in an inclusive tree. However, as is conceivable a user of the managed terminal <b>20</b> may wish to access various network configurations outside of the partial network configuration related to the managed terminal <b>20</b>.

[0100] To enable the display of the configurations of various networks outside of the partial network configuration in an inclusive tree, if the symbol images of all symbols in a lower order level related to a symbol specified by a user are not located on the inclusive tree screen <b>1601</b>, symbol developing processing in which the symbol images of such symbols are newly located is further executed according to the first embodiment. Also, to enable displaying the configurations of various networks outside of the partial network configuration in an inclusive tree, if the symbol images of all symbols in a lower order level of the maps related to a symbol specified by a user are located on the inclusive tree screen <b>1601</b>, symbol closing processing in which the symbol images of such symbols are deleted is further executed according to the first embodiment.

[0101]FIG. 17 is a flowchart showing the outline of the symbol developing/closing processing executed by the configuration information display section <b>135</b> of the configuration information display program <b>136</b>. It should be noted that each of the steps of the flowchart corresponds to code of a computer program.

[0102] As shown in FIG. 17, when a desired symbol is specified by selecting the corresponding symbol image on the inclusive tree screen <b>1601</b> by a user operating the mouse <b>27</b>, the configuration information display section <b>135</b> of the configuration information display program <b>136</b> in the managed terminal <b>20</b> acquires the identifier <b>1302</b> of the symbol specified by the user from the configuration information internal table <b>1301</b> (step <b>1701</b>). Next, the configuration information display section <b>135</b> judges whether each of the symbols in lower level maps relate to the symbol specified by the user. That is whether each of the symbols having the symbol specified by the user as the higher order symbol <b>1308</b> are stored in the configuration information internal table <b>1301</b> or not (step <b>1702</b>). The judgment can be executed by retrieving symbols having the symbol specified by the user as the respective higher order symbol <b>1308</b> of the same number as the number of subordinate symbols <b>1308</b> corresponding to the identifier <b>1302</b> of the symbol specified by the user from the configuration information internal table <b>1301</b>.

[0103] First, the symbol developing processing executed when information indicating a relation between each of the symbols in a lower order level of the maps related to a symbol specified by a user is not stored in the configuration information internal table <b>1301</b> will be described.

[0104] In the symbol developing processing, the configuration information display section <b>135</b> first informs the hierarchical symbol acquiring section <b>138</b> of the network management system <b>10</b> of the identifier <b>1302</b> of a symbol specified by a user and a request for transferring configuration information (step <b>1703</b>). In the network management system <b>10</b>, the hierarchical symbol acquiring section <b>138</b> generates the display information table <b>1101</b> storing the symbol information of each of the symbols, the higher order symbol <b>504</b> of which, has the identifier <b>1302</b> informed by the configuration information display section <b>135</b> of the managed terminal <b>20</b> as described in the flowchart shown in FIG. 10, and informs the configuration information display section <b>1305</b> of the managed terminal <b>20</b> of the generated display information table <b>1101</b>.

[0105] When the configuration information display section <b>135</b> receives the display information table <b>1101</b> from the hierarchical symbol acquiring section <b>138</b> of the network management system <b>10</b> (step <b>1704</b>), the configuration information display section <b>135</b> determines the size of a display area required to locate the symbol images based upon the number of symbols, the symbol information of which, is stored in the display information table <b>1101</b> (step <b>1705</b>). Next, the configuration information display section <b>135</b> acquires all symbols, the symbol images of which are located at the y-coordinate of a value larger than the y-coordinate of a position at which the symbol image of a symbol specified by a user is located and shifts the y-coordinates of the respective locations of the symbol images of the acquired symbols so that a display area of the size determined in step <b>1705</b> can be secured (step <b>1706</b>). Thereafter the configuration information display section <b>135</b> adds the information of symbols, the symbol information of which is stored in the display information table <b>1101</b> received in the step <b>1704</b>, into the configuration information internal table <b>1301</b> (step <b>1707</b>). The configuration information display section <b>135</b> creates and locates the symbol images of the above symbols (step <b>1708</b>), and connects them (step <b>1709</b>).

[0106] As described above, the symbol images of all symbols in a lower order level of the maps related to one symbol specified by the user are newly located on the inclusive tree screen <b>1601</b> by repeating steps <b>1707</b> to <b>1709</b> for each symbol, the symbol information of which is stored in the display information table <b>1101</b>, received from the hierarchical symbol acquiring section <b>138</b> of the network management system <b>10</b> (step <b>1710</b>).

[0107] Next, the symbol closing processing executed when the information of all symbols in a lower order level of the maps related to a symbol specified by a user is stored in the configuration information internal table <b>1301</b> will be described.

[0108] In the symbol closing processing, the configuration information display section <b>135</b> repeats processing for first deleting the information of each symbol from the configuration information internal table <b>1301</b> (step <b>1711</b>), deleting the symbol image of each symbol from the inclusive tree screen <b>1601</b> (step <b>1712</b>) and deleting a line connecting the symbol images of the symbols from the inclusive tree screen <b>1601</b> (step <b>1713</b>) for each symbol in a lower order level of the maps related to a symbol specified by a user (step <b>1714</b>). Next, the configuration information display section <b>135</b> acquires all symbols, the symbol images of which are located at the y-coordinate, of a value larger than the y-coordinate of a position in which the symbol image of the symbol specified by the user is located and shifts the y-coordinates of locations of the symbol images of the acquired symbols so that an area blanked by deleting all the symbol images in the step <b>1712</b> is filled (step <b>1715</b>). Thus, the symbol images of all the symbols in a lower order level of the maps related to the symbol specified by the user are deleted from the inclusive tree screen <b>1601</b>.

[0109] For example, when the symbol which is the root is specified by a user moving a cursor <b>1611</b> to the symbol image <b>1602</b> which is the root on the inclusive tree screen <b>1601</b> shown in FIG. 16 as shown in FIG. 18 and the user operates the mouse, the symbol developing processing is executed. As a result, the symbol image <b>1612</b> of a symbol in a lower order level of the map, related to the symbol which is the root, is newly located on the inclusive tree screen <b>1601</b>. Also, for example, when a symbol which is a sector <b>1</b> is specified by a user moving the cursor <b>1611</b> to a symbol image <b>1605</b> which is the sector <b>1</b> on the inclusive tree screen <b>1601</b> shown in FIG. 16 as shown in FIG. 19 and the user operates the mouse, the symbol closing processing is executed. As a result, the symbol image of a symbol in a lower order level of the maps related to the symbol which is the sector <b>1</b> is deleted from the inclusive tree screen <b>1601</b>. Thus, the configurations of various networks including partial network configuration and whole network configurations can be displayed in an inclusive tree by executing the above described symbol developing/closing processing.

[0110] Next, referring to FIGS. 9, 10, <b>12</b> and <b>20</b> to <b>25</b>, a second embodiment of the present invention will be described.

[0111] According to the second embodiment, when network management is executed from the managed terminal <b>20</b>, event information related to the managed terminal <b>20</b> collected by the network management system <b>10</b> from network equipment <b>201</b> and <b>202</b> each including a managed equipment <b>20</b> and stored in the network management system <b>10</b>, can be preferentially displayed.

[0112]FIG. 20 is a block diagram showing the configuration of a network management system <b>10</b> and a managed terminal <b>20</b> of the second embodiment.

[0113] In the second embodiment, the configuration of the managed terminal <b>20</b> is the same as in the first embodiment. In the second embodiment, the configuration of the network management system <b>10</b> is similar to that in the first embodiment. However, the configuration of the network management system <b>10</b> in the second embodiment is different from the first embodiment in that an event information display program <b>2021</b> is stored in program memory <b>13</b> in place of the configuration information display program <b>136</b>. The event information display program <b>2021</b>, similar to the configuration information display program <b>136</b>, can be an Applet as per the JAVA and ACTIVE X programming languages. Also an event information retrieval program <b>2011</b> is stored in the program memory <b>13</b> and an event information table <b>2001</b> is stored in the database <b>110</b>.

[0114] The event information display program <b>2021</b> is a program activated in a managed terminal <b>20</b> when it is transferred to the managed terminal <b>20</b> for causing the display of event information related to the managed terminal <b>20</b> on the managed terminal <b>20</b>. The event information display program <b>2021</b> is provided with a terminal information gathering section <b>2022</b> and an event information display section <b>2023</b>. The event information retrieval program <b>2011</b> is a program for acquiring event information related to a managed terminal <b>20</b> and is provided with a filtering section <b>2012</b> and a retrieval and enlargement section <b>2013</b>.

[0115] In the network management system <b>10</b>, CPU <b>14</b> periodically collects management information from each of network equipment <b>201</b> and <b>202</b> each including a managed terminal <b>20</b> via a communication control unit <b>11</b> by executing a management information collection program <b>131</b> as in the first embodiment. The collected management information is stored in a management information table <b>111</b>. In the second embodiment, CPU <b>14</b> further receives an event log spontaneously informed by each of the network equipment <b>201</b> and <b>202</b> via the communication control unit <b>11</b> by executing the management information collection program <b>131</b>. The event information of the received event log is stored in the event information table <b>2001</b> shown in FIG. 21. Contents stored as event information include an identifier <b>2102</b> uniquely showing an event log, an IP address <b>2103</b> of managed equipment informed about the event log, an informed time <b>2104</b> showing time in which the event log is informed, informed contents <b>2105</b> showing the contents of the event log and an information type <b>2106</b> showing the type of the event log as shown in FIG. 21. The identifier <b>2102</b> is a number given so that the closer to the present time the informed time <b>2104</b> is, the smaller the number is.

[0116] The operation of the second embodiment will be described below.

[0117] When a user instructs the managed terminal <b>20</b> to execute network management under the above environment, a transfer request program <b>24</b> first informs the transfer program <b>137</b> of the network management system <b>10</b> of a request for transferring the event information display program <b>2021</b>. In the network management system <b>10</b>, when the transfer program <b>137</b> receives the request for transferring the event information display program <b>2021</b> to the managed terminal <b>20</b>, the transfer program <b>137</b> transfers the event information display program <b>2021</b> stored in the program memory <b>13</b> to the work memory <b>22</b> of the managed terminal <b>20</b>. In the managed terminal <b>20</b>, when the event information display program <b>2021</b> is transferred to the work memory <b>22</b> from the network management system <b>10</b>, the event information display program <b>2021</b> is automatically activated. When the event information display program <b>2021</b> is activated in the managed terminal <b>20</b>, the terminal information gathering section <b>2022</b> first acquires the IP address of the managed terminal <b>20</b>, same as the terminal information gathering section <b>134</b> of the configuration information display program <b>136</b> in the first embodiment, and informs the event information retrieval program <b>2011</b> of the network management system <b>10</b> of the request for transferring event information together with the acquired IP address. In the network management system <b>10</b>, when the event information retrieval program <b>2011</b> receives the request for transferring event information and the IP address from the managed terminal <b>20</b>, the filtering section <b>2012</b> is operated as shown in the flowchart in FIG. 22.

[0118]FIG. 22 is a flowchart showing the outline of the operation of the filtering section <b>2012</b> of the event information retrieval program <b>2011</b>. It should be noted that each of the steps of the flowchart corresponds to code of a computer program.

[0119] As shown in FIG. 22, the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> first retrieves an IP address <b>304</b> equal to the IP address received from the managed terminal <b>20</b> from the management information table <b>111</b> and acquires an identifier <b>302</b> corresponding to the retrieved IP address <b>304</b>, that is, the identifier <b>302</b> of the managed terminal <b>20</b> (step <b>2201</b>). Next, the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> informs the filtering section <b>132</b> of a configuration information filtering program <b>133</b> of a request for configuration information together with the identifier <b>302</b> acquired in step <b>2201</b> (step <b>2202</b>).

[0120] When the filtering section <b>132</b> of the configuration information filtering program <b>133</b> is informed of the request for configuration information and the identifier <b>302</b> by the filtering section <b>2012</b> of the event information retrieval program <b>2011</b>, the filtering section <b>132</b> generates a hierarchical information table <b>901</b> showing a location in a map including a symbol having the informed identifier <b>302</b> as the corresponding node <b>505</b>, that is, the symbol of the managed terminal <b>20</b>. The filtering section <b>132</b> also informs the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> of the generated hierarchical information table <b>901</b> same as the operations described in the flowchart shown in FIG. 8. When the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> is informed of the hierarchical information table <b>901</b> from the filtering section <b>132</b> of the configuration information filtering program <b>133</b> (step <b>2203</b>), the filtering section <b>2012</b> informs a hierarchical symbol acquiring section <b>138</b> of the configuration information filtering program <b>133</b> of a request for configuration information together with the identifier <b>902</b> of a symbol in a high order related to the symbol of the managed terminal <b>20</b> in the hierarchical information table <b>901</b> (step <b>2204</b>).

[0121] When the hierarchical symbol acquiring section <b>138</b> of the configuration information filtering program <b>133</b> is informed of the request for configuration information and the identifier <b>902</b> of the symbol by the filtering section <b>2012</b> of the event information retrieval program <b>2011</b>, the hierarchical symbol acquiring section <b>138</b> generates the display information table <b>1101</b> which stores the symbol information of all symbols, the higher order symbol <b>504</b> of which has the informed identifier <b>902</b> of the symbol, that is, all symbols included in a map including the symbol of the managed terminal <b>20</b>. The hierarchical symbol acquiring section <b>138</b> also informs the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> of the generated display information table <b>1101</b> same as the operations described in the flowchart shown in FIG. 10.

[0122] When the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> is informed of the display information table <b>1101</b> by the hierarchical symbol acquiring section <b>138</b> of the configuration information filtering program <b>133</b> (step <b>2205</b>), the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> acquires the identifier of managed equipment corresponding to each symbol, the symbol information of which is stored in the display information table <b>1101</b> (step <b>2206</b>). In step <b>2206</b>, the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> retrieves the node <b>505</b> corresponding to a symbol having an identifier equivalent to an identifier <b>1102</b> stored in the display information table <b>1101</b> as the identifier <b>502</b> from a configuration information table <b>112</b>. Next, the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> acquires the IP address of each managed equipment, the identifier of which is acquired in step <b>2206</b> (step <b>2207</b>).

[0123] In step <b>2207</b>, the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> retrieves an IP address <b>304</b> corresponding to an identifier <b>302</b> equal to the corresponding node <b>505</b> from the management information table <b>111</b> because the corresponding node <b>505</b> retrieved in step <b>2206</b> is equivalent to an identifier <b>302</b> in the management information table <b>111</b>. The IP address <b>304</b> of any managed equipment existing in a partial network related to the managed terminal <b>20</b> is acquired by the above operation.

[0124] Afterward, the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> checks whether event information corresponding to any managed equipment, the IP address <b>304</b> of which is acquired in step <b>2207</b> is stored in the event information table <b>2001</b> or not. If event information has been stored, the filtering section <b>2012</b> informs the event information display program <b>2021</b> of the managed terminal <b>20</b> of a list of such event information. That is, the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> retrieves event information stored in the event information table <b>2001</b> in the order of identifiers <b>2102</b> (step <b>2208</b>), checks whether an IP address <b>2103</b> of the retrieved event information is equal to any of the IP addresses <b>304</b> acquired (step <b>2207</b>) or not (step <b>2209</b>) and if so, the filtering section stores the identifiers <b>2102</b> of the retrieved event information (step <b>2210</b>).

[0125] After steps <b>2208</b> to <b>2210</b> are repeated for each event information stored in the event information table <b>2001</b> (step <b>2211</b>), the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> extracts event information shown by the identifiers <b>2102</b> based upon all the identifiers <b>2102</b> stored in (step <b>2210</b>) from the event information table <b>2001</b> and informs the event information display program <b>2021</b> of the managed terminal <b>20</b> of a list of the extracted event information (step <b>2212</b>). In the managed terminal <b>20</b>, when the event information display section <b>2023</b> of the event information display program <b>2021</b> receives the list of event information from the filtering section <b>2012</b> of the network management system <b>10</b>, the managed terminal <b>20</b> displays the list of the received event information in an event list display area <b>2302</b> on an event display screen <b>2301</b> as shown in FIG. 23.

[0126] As described above, event information, related to a managed terminal <b>20</b> is collected from the network equipment <b>201</b> and <b>202</b> including the managed terminal <b>20</b> by the network management system <b>10</b> and stored therein. Such event information can be preferentially displayed according to the second embodiment when network management is executed from the managed terminal <b>20</b>. A user who uses the managed terminal <b>20</b> is not required to retrieve the event information of the managed terminal <b>20</b> and can immediately execute network management.

[0127] However, it is conceivable that a user of a managed terminal <b>20</b> may want to access various event information except event information related to the managed terminal <b>20</b>. To enable displaying of the various event information, in the second embodiment, enlargement processing for gradually enlarging event information to be displayed according to the instruction of a user is further executed.

[0128]FIG. 24 is a flowchart showing the outline of enlargement processing executed by the retrieval and enlargement section <b>2013</b> of the event information retrieval program <b>2011</b>. It should be noted that each of the steps of the flowchart corresponds to code of a computer program.

[0129] As shown in FIG. 23, a display object enlarging button <b>2303</b> used by a user to instruct the enlargement of event information to be displayed on the event display screen <b>2301</b>. When a user instructs the enlargement of event information to be displayed by actuating the display object enlarging button <b>2303</b> via the mouse <b>27</b>, the event information display program <b>2021</b> of the managed terminal <b>20</b> informs the retrieval and enlargement section <b>2013</b> of the event information retrieval program <b>2011</b> of the network management system <b>10</b> of a request for enlarging a displayed object.

[0130] In the network management system <b>10</b>, when the retrieval and enlargement section <b>2013</b> of the event information retrieval program <b>2011</b> receives the request for enlarging the displayed object from the event information display program <b>2021</b> of the managed terminal <b>20</b> as shown in FIG. 24 (step <b>2401</b>), the filtering section <b>2012</b> of the event information retrieval program <b>2011</b> retrieves a symbol in a higher order level map related to the enlarged symbol in the last enlargement processing from the hierarchical information table <b>901</b> informed by the filtering section <b>132</b> of the configuration information filtering program <b>133</b> in the operation described in the flowchart shown in FIG. 22. That is, the hierarchical information table <b>901</b> shows a location in a map including the symbol of the managed terminal <b>20</b> and enlarges the above symbol (step <b>2402</b>).

[0131] In the step <b>2402</b>, in case this enlargement processing is the first enlargement processing after displaying a list of event information related to a managed terminal <b>20</b>, the retrieval and enlargement section <b>2013</b> receives and enlarges a symbol in a higher order level maps related to the symbol of the managed terminal <b>20</b>. Next, the retrieval and enlargement section <b>2013</b> acquires the identifiers of all symbols included in the least significant map sequentially pulled down from each symbol, except a symbol to be retrieved and enlarged, of all symbols included in a map including the above symbol to be retrieved and enlarged (step <b>2403</b>).

[0132] In step <b>2403</b>, the retrieval and enlargement section <b>2013</b> first informs the hierarchical symbol acquiring section <b>138</b> of the configuration information filtering program <b>133</b> of a request for configuration information and the identifier <b>902</b> of a symbol in a higher order level map related to the symbol to be retrieved and enlarged. If the symbol information of a symbol in a higher order level map related to the symbol to be retrieved and enlarged is not stored in the hierarchical information table <b>901</b>, the retrieval and enlargement section <b>2013</b> informs that the above symbol in a higher order level map is the most significant symbol in place of the identifier <b>902</b>.

[0133] When the hierarchical symbol acquiring section <b>138</b> is informed of the request for configuration information and the identifier <b>902</b> of the symbol by the retrieval and enlargement section <b>2013</b>, the hierarchical symbol acquiring section <b>138</b> generates the display information table <b>1101</b> which stores the symbol information of all symbols, the higher order symbol <b>504</b> of which includes the informed identifier <b>902</b> of the symbol. In other words, all symbols included in a map including the symbol to be retrieved and enlarged as the operation described in the flowchart shown in FIG. 10. The hierarchical symbol acquiring section <b>138</b> also informs the retrieval and enlargement section <b>2013</b> of the generated display information table <b>1101</b> when the hierarchical symbol acquiring section <b>138</b> is informed of information that the symbol is the most significant symbol by the retrieval and enlargement section <b>2013</b>. The hierarchical symbol acquiring section <b>138</b> generates the display information table <b>1101</b> which stores the symbol information of all symbols, of which no higher order symbol <b>504</b> exists, and informs such to the display information table.

[0134] When the retrieval and enlargement section <b>2013</b> is informed of the display information table <b>1101</b> by the hierarchical symbol acquiring section <b>138</b>, the retrieval and enlargement section <b>2013</b> informs the hierarchical symbol acquiring section <b>138</b> of a request for configuration and the identifier <b>1102</b> of each symbol, except the symbol to be retrieved and enlarged, of all symbols the symbol information of which is stored. This is done since the symbol information of the symbol to be retrieved and enlarged is also stored in the display information table <b>1101</b>. Thus, the display information table <b>1101</b> which stores the symbol information of symbols in a lower order level of the maps including the symbol to be retrieved and enlarged is informed by the hierarchical symbol acquiring section <b>138</b>.

[0135] As described above, if the display information table <b>1101</b> is informed by the hierarchical symbol acquiring section <b>138</b> of the identifiers <b>1102</b> of all symbols included in the least significant map sequentially pulled down from each symbol, except the symbol to be retrieved and enlarged then symbols included in a map including the symbol to be retrieved and enlarged can be acquired from the informed display information table <b>1101</b>. When the number of subordinate symbols <b>1106</b> in the symbol information is zero “0”, acquiring cannot occur. The retrieval and enlargement section <b>2013</b> acquires the identifier of managed terminal corresponding to each symbol of all the identifiers <b>1102</b> acquired in step <b>2403</b> respectively (step <b>2404</b>).

[0136] In step <b>2404</b>, the retrieval and enlargement section <b>2013</b> retrieves the node <b>505</b> corresponding to a symbol, the identifier <b>502</b> of which is equal to each identifier <b>1102</b> acquired in step <b>2403</b> from the configuration information table <b>112</b>. Next, the retrieval and enlargement section <b>2013</b> acquires the IP address of each managed terminal, the identifier of which is acquired in step <b>2404</b> (step <b>2405</b>).

[0137] In step <b>2405</b>, the retrieval and enlargement section <b>2013</b> retrieves the IP address <b>304</b> corresponding to an identifier <b>302</b> which is equivalent to the corresponding node <b>505</b> from the management information table <b>111</b>. This is done since the corresponding node <b>505</b> retrieved in step <b>2404</b> is equivalent to an identifier <b>302</b> in the management information table <b>111</b>. The IP addresses <b>304</b> of the managed terminal corresponding to all symbols included in the least significant map sequentially pulled down from each symbol are acquired by the above processing. All symbols are acquired except a symbol to be retrieved and enlarged.

[0138] Afterward, the retrieval and enlargement section <b>2013</b> checks whether event information corresponding to each managed terminal, the IP address <b>304</b> of which is acquired in the step <b>2405</b>, is stored in the event information table <b>2001</b> or not. If so, the retrieval and enlargement section <b>2013</b> informs the event information display program <b>2021</b> of the managed terminal <b>20</b> about a list of such event information.

[0139] The retrieval and enlargement section <b>2013</b> retrieves event information stored in the event information table <b>2001</b> in ascending order of identifiers <b>2102</b> (step <b>2406</b>). The retrieval and enlargement section <b>2013</b> also checks whether the IP address <b>2103</b> in the retrieved event information is equal to any of the IP addresses acquired in step <b>2405</b> or not (step <b>2407</b>). If so, the identifier <b>2102</b> in the retrieved event information is stored (step <b>2408</b>).

[0140] After steps <b>2406</b> to <b>2408</b> are repeated for each event information stored in the event information table <b>2001</b> (step <b>2409</b>), the retrieval and enlargement section <b>2013</b> extracts event information shown by all the identifiers <b>2102</b> stored in step <b>2408</b> from the event information table <b>2001</b> and informs the event information display program <b>2021</b> of the managed terminal <b>20</b> of a list of the extracted event information (step <b>2410</b>). In the managed terminal <b>20</b>, when the event information display section <b>2023</b> of the event information display program <b>2021</b> receives the list of event information from the retrieval and enlargement section <b>2013</b> of the network management system <b>10</b>, the managed terminal <b>20</b> adds the received list of event information to the event list display area <b>2302</b> on the event display screen <b>2301</b> and displays it.

[0141]FIG. 25 is a flowchart showing the outline of additional display processing executed when the event information display section <b>2023</b> adds and displays the list of the event information. It should be noted that each of the steps of the flowchart corresponds to code of a computer program.

[0142] As shown in FIG. 25, when the event information display section <b>2023</b> receives the list of event information from the retrieval and enlargement section <b>2013</b> of the network management system <b>10</b> (step <b>2501</b>), the event information display section <b>2023</b> sorts the received event information and any event information already displayed in the event list display area <b>2302</b> on the event display screen <b>2301</b> in ascending order of identifiers <b>1802</b> (step <b>2502</b>). Next, the event information display section <b>2023</b> judges whether each event information sorted in step <b>2506</b> is event information to be additionally displayed or not (step <b>2503</b>). This judgment can be executed by judging whether the above sorted event information is the event information received in the step <b>2501</b> or not. If the above event information is event information to be additionally displayed, the event information display section <b>2023</b> displays the event information and changes the color of the background of the event information (step <b>2504</b>). If the event information is not event information to be additionally displayed, the event information display section <b>2023</b> displays the event information without a change in the color of the background of the event information (step <b>2505</b>). When the display of event information is finished as described above, the event display screen <b>2301</b> shown in FIG. 23 is changed as shown in FIG. 26.

[0143] In FIG. 26 the event information <b>5</b>, <b>10</b> and <b>16</b> on the event display screen <b>2301</b> indicate that they are event information additionally displayed after a user activates the display object enlarging button <b>2303</b> via the mouse <b>27</b>. According to processing shown in the flowchart in FIG. 25, the event information display section <b>2023</b> changes the color of the background of event information when event information to be additionally displayed is displayed. This is executed to permit a user to easily identify the event information that is event information additionally displayed. However, the present invention is not limited to this embodiment, for example, event information to be additionally displayed may be underlined and the color of the event information itself may be also changed. Event information to be displayed can be gradually enlarged by executing the above enlargement processing and additional display processing.

[0144] Next, referring to FIGS. <b>27</b> to <b>29</b>, a third embodiment of the present invention will be described.

[0145] The third embodiment enables preferentially displaying management information related to a managed terminal and matched with a retrieval condition set by a user who uses the managed terminal <b>20</b> when network management is executed from the managed terminal <b>20</b>. FIG. 27 is a block diagram showing the configuration of a network management system <b>10</b> and a managed terminal <b>20</b> included in the third embodiment.

[0146] In the third embodiment, the configuration of the managed terminal <b>20</b> is the same as in the first embodiment. Also, in the third embodiment, the configuration of the network management system <b>10</b> is similar to that in the first embodiment. However, the configuration of the network management system in the third embodiment is different from that in the first embodiment in that a management information display program <b>2702</b> is stored in program memory <b>13</b> in place of a configuration information display program <b>136</b> and a management information sort program <b>2701</b> is stored in the program memory <b>13</b>. Here again the management information display program <b>2701</b>, similar to the configuration information display program <b>136</b>, can be an Applet according to the JAVA and ACTIVE X programming languages.

[0147] The management information display program <b>2702</b> is a program activated in a managed terminal <b>20</b> when it is transferred to the managed terminal <b>20</b> for causing the display of management information matched with a retrieval condition set by a user using the managed terminal <b>20</b>. The management information display program <b>2702</b> is provided with a terminal information gathering section <b>2703</b> and a management information display section <b>2704</b>. The management information sort program <b>2701</b> is a program for sorting management information so that the display of management information related to a managed terminal <b>20</b> is effected. In the network management system <b>10</b>, CPU <b>14</b> periodically collects management information from each network equipment <b>201</b> and <b>202</b> each including a managed terminal <b>20</b> via a communication control unit <b>11</b> by executing a management information collection program <b>131</b> as in the first embodiment and stores the collected management information in a management information table <b>111</b>.

[0148] The operation of the third embodiment will be described below.

[0149] When a user instructs a managed terminal <b>20</b> to execute network management under the above environment, a transfer request program <b>24</b> first informs the transfer program <b>137</b> of the network management system <b>10</b> of a request for transferring the management information display program <b>2702</b>. In the network management system <b>10</b>, when the transfer program <b>137</b> receives the request for transferring the management information display program <b>2702</b> from the managed terminal <b>20</b>, the transfer program <b>137</b> transfers the management information display program <b>2702</b> stored in the program memory <b>13</b> to the work memory <b>22</b> of the managed terminal <b>20</b>. In the managed terminal <b>20</b>, the management information display program <b>2702</b> is automatically activated when it is transferred from the network management system <b>10</b> to the work memory <b>22</b>.

[0150] In the managed terminal <b>20</b>, when the management information display program <b>2702</b> is activated, the terminal information gathering section <b>2703</b> first causes the display of a retrieval screen <b>2801</b> shown in FIG. 28 for example on a display <b>25</b> after acquiring the IP address of the managed terminal <b>20</b> similar to the terminal information gathering section <b>134</b> of the configuration information display program <b>136</b> in the first embodiment. The management information display program <b>2702</b> then waits for a user to set a retrieval condition and instruct the execution of a retrieval using the set retrieval condition.

[0151] As shown in FIG. 28, the retrieval screen <b>2801</b> includes a retrieval condition attribute setting area <b>2802</b> for allowing a user to set the attribute of a retrieval condition, an attribute value input area <b>2803</b> for allowing a user to input an attribute value equivalent to the retrieval condition, a retrieval button <b>2804</b> for allowing a user to instruct the execution of retrieval and a retrieval result display area <b>2805</b> for displaying the result of the retrieval. On the retrieval screen <b>2801</b> shown in FIG. 28, an example is illustrated where a user sets an IP address as the attribute of a retrieval condition and inputs “AA. AB. *.*” as an attribute value so as to set a retrieval condition. The above code means that a user wants to retrieve an IP address in the format of “AA. AB.*.*”. After the user sets the retrieval condition, the execution of the retrieval by activating the retrieval button <b>2804</b> via the mouse <b>27</b> is instructed.

[0152] In the managed terminal <b>20</b>, when the user instructs the execution of the retrieval, the terminal information gathering section <b>2703</b> informs the management information sort program <b>2701</b> of the network management system <b>10</b> of a request for transferring management information together with the already acquired IP address and the retrieval condition set by the user. In the network management system <b>10</b>, when the management information sort program <b>2701</b> receives the request for transferring management information, the IP address and the retrieval condition from the managed terminal <b>20</b>, the network management system <b>10</b> is operated as shown in the flowchart in FIG. 29.

[0153]FIG. 29 is a flowchart showing the outline of the operation of the management information sort program <b>2701</b>. It should be noted that each of the steps of the flowchart corresponds to code of a computer program.

[0154] As shown in FIG. 29, the management information sort program <b>2701</b> first acquires the IP address of any managed equipment existing in a partial network related to the managed terminal <b>20</b> by executing the same operation in steps <b>2901</b> to <b>2907</b> as steps <b>2201</b> to <b>2207</b> shown in FIG. 22 executed by the filtering section <b>2012</b> of the event information retrieval program <b>2011</b>. That is, the management information sort program <b>2701</b> retrieves an IP address <b>304</b> equal to the IP address received from the managed terminal <b>20</b> from the management information table <b>111</b> and acquires an identifier <b>302</b> corresponding to the retrieved IP address <b>304</b>. The identifier <b>302</b> is of the managed terminal <b>20</b> (step <b>2901</b>). Next, the management information sort program <b>2701</b> informs the filtering section <b>132</b> of the configuration information filtering program <b>133</b> of a request for configuration information together with the identifier <b>302</b> acquired in step <b>2901</b> (step <b>2902</b>).

[0155] As the hierarchical information table <b>901</b> showing a location in a map including the symbol of the managed terminal <b>20</b> is informed by the filtering section <b>132</b> of the configuration information filtering program <b>133</b> (step <b>2903</b>), the management information sort program <b>2701</b> informs the hierarchical symbol acquiring section <b>138</b> of the configuration information filtering program <b>133</b> of the request for configuration information together with the identifier <b>902</b> of a symbol in a higher order level map which includes a symbol of the managed terminal <b>20</b> in the hierarchical information table <b>901</b> (step <b>2904</b>). As the display information table <b>1101</b> which stores the symbol information of all symbols included in a map including the symbol of the managed terminal <b>20</b> is supplied by the hierarchical symbol acquiring section <b>138</b> of the configuration information filtering program <b>133</b> (step <b>2905</b>), the management information sort program <b>2701</b> acquires the identifier of managed equipment corresponding to each symbol, the symbol information of which is stored in the display information table <b>1101</b> (step <b>2906</b>).

[0156] In step <b>2906</b>, the management information sort program <b>2701</b> retrieves the node <b>505</b> corresponding to a symbol provided with an identifier <b>502</b> equal to an identifier <b>1102</b> stored in the display information table <b>1101</b> from the configuration information table <b>112</b>. Next, the management information sort program <b>2701</b> acquires the IP address of each managed equipment the identifier of which is acquired in step <b>2906</b> (step <b>2907</b>). In the step <b>2907</b>, as the corresponding node <b>505</b> retrieved in step <b>2906</b> is equivalent to an identifier <b>302</b> in the management information table <b>111</b>, the management information sort program <b>2701</b> retrieves the IP address <b>304</b> corresponding to an identifier <b>302</b> equal to the corresponding node <b>505</b> from the management information table <b>111</b>. The IP address <b>304</b> of any managed equipment existing in a partial network related to the managed terminal <b>20</b> is acquired by the above operation.

[0157] Thereafter, the management information sort program <b>2701</b> generates a list of the management information matched with the retrieval condition received from the managed terminal <b>20</b> and retrieved from the management information table <b>111</b> (step <b>2908</b>). In step <b>2908</b>, as shown in FIG. 28, retrieval condition set by a user on a retrieval screen <b>2801</b> provides, for example, that the management information sort program <b>2701</b> retrieves an IP address <b>304</b> according to a format of “AA. AB.*.*”, that is, “AA. AB. AC. AD”, “AA. AB. AC. AE”, “AA. AB. AC. AF”, “AA. AB. AG. AH”, “AA. AB. AG. AI” and “M. AB. AJ. AK”.

[0158] Next, the management information sort program <b>2701</b> checks whether the IP address <b>304</b> corresponding to each management information, the list of which is generated in step <b>2908</b> (step <b>2911</b>), is equal to any of the IP addresses <b>304</b> acquired in step <b>2907</b> or not (step <b>2909</b>). If so the management information sort program <b>2701</b> shifts such management information at the head of the list (step <b>2910</b>). The management information related to the managed terminal <b>20</b> is located in a higher order by sorting the list of management information generated in step <b>2908</b> as described above. Thereafter, the management information sort program <b>2701</b> informs the management information display program <b>2702</b> of the managed terminal <b>20</b> of a sorted list of management information (step <b>2911</b>).

[0159] In the managed terminal <b>20</b>, when the management information display section <b>2704</b> of the management information display program <b>2702</b> receives the list of management information from the management information sort program <b>2701</b> of the network management system <b>10</b>, the managed terminal <b>20</b> displays the list of management information in the retrieval result display area <b>2805</b> on the retrieval screen <b>2801</b> shown in FIG. 28 as the result of retrieval. As described above, according to the third embodiment, management information related to a managed terminal can be located in a higher order when a list of management information matched with a retrieval condition set by a user is displayed on the managed terminal <b>20</b> and when network management is executed from the managed terminal <b>20</b>. The management information is displayed in such manner to allow the user of the managed terminal <b>20</b> to readily recognize management information related to the managed terminal <b>20</b>.

[0160] In the third embodiment, the management information sort program <b>2701</b> of the network management system <b>10</b> may inform a list of management information related to a managed terminal <b>20</b> and a list of other management information separately to the managed terminal <b>20</b>. The management information display section <b>2704</b> of a managed terminal <b>20</b> may also display a boundary line between both lists.

[0161] Next, referring to FIGS. <b>30</b> to <b>34</b>, a fourth embodiment of the present invention will be described.

[0162] The fourth embodiment enables preferentially displaying partial network configuration related to a managed terminal <b>20</b> in an inclusive tree as in the first embodiment when network management is executed from the managed terminal <b>20</b>. The fourth embodiment also allows for the contents of the display of the partial network configuration to be changed according to the performance of the managed terminal <b>20</b>.

[0163]FIG. 30 is a block diagram showing the configuration of a network management system <b>10</b> and a managed terminal <b>20</b> of the fourth embodiment. The configuration of a managed terminal <b>20</b> in the fourth embodiment is the same as in the first embodiment. Also, the configuration of the network management system <b>10</b> in the fourth embodiment is similar to that in the first embodiment. However, the network management system of the fourth embodiment is different from that in the first embodiment in that an each device display contents determining table <b>3001</b> is stored in the database <b>110</b>. FIG. 31 shows an example of the each device display contents determining table <b>3001</b>.

[0164] As shown in FIG. 31, the each device display contents determining table <b>3001</b> is a matrix table relating contents displayed on a managed terminal <b>20</b> to keys of the memory capacity <b>3102</b> of work memory <b>22</b> and the CPU format <b>3103</b> of CPU <b>29</b>. For example, on a managed terminal <b>20</b> the memory capacity <b>3102</b> of the work memory <b>22</b> is 10 MB or less and the CPU format of CPU <b>29</b> is CPU-A. Partial network configuration related to the managed terminal <b>20</b> is displayed in an inclusive tree in which symbol images, each of which includes a symbol name, are connected.

[0165] The operation of the fourth embodiment will be described below.

[0166]FIG. 32 is a flowchart showing the outline of the operation of the network management system <b>10</b> and a managed terminal <b>20</b> in the fourth embodiment of the present invention. It should be noted that each of the steps of the flowchart corresponds to code of a computer program.

[0167] As shown in FIG. 32, when a user instructs the managed terminal <b>20</b> to execute network management, a transfer request program <b>24</b> first informs the transfer program <b>137</b> of the network management system <b>10</b> of a request for transferring a configuration information display program <b>136</b> as in the first embodiment (step <b>3201</b>). In the network management system <b>10</b>, when the transfer program <b>137</b> receives the request for transferring the configuration information display program <b>136</b> from the managed terminal <b>20</b>, the network management system <b>10</b> transfers the configuration information display program <b>136</b> stored in the program memory <b>13</b> to the work memory <b>22</b> of the managed terminal <b>20</b> as in the first embodiment (step <b>3202</b>).

[0168] In the managed terminal <b>20</b>, when the configuration information display program <b>136</b> is transferred from the network management system <b>10</b> to the work memory <b>22</b>, the configuration information display program <b>136</b> is automatically activated. When the configuration information display program <b>136</b> is activated, a terminal information gathering section <b>134</b> first acquires the IP address of the managed terminal <b>20</b> as in the first embodiment. However, in the fourth embodiment, the terminal information gathering section further gathers the CPU format of CPU <b>29</b> and the memory capacity of the work memory <b>22</b>. The terminal information gathering section <b>134</b> informs the configuration information filtering program <b>133</b> of the network management system <b>10</b> of a request for transferring configuration information together with the gathered IP address, CPU format and memory capacity (step <b>3203</b>).

[0169] In the network management system <b>10</b>, when the configuration information filtering program <b>133</b> receives the request for transferring configuration information together with the IP address, CPU format and memory capacity from the managed terminal <b>20</b>, the network management system <b>10</b> first determines contents to be displayed on the managed terminal <b>20</b> by retrieving the each device display contents determining table <b>3001</b> using the CPU format and the memory capacity respectively received from the managed terminal <b>20</b> as keys in the fourth embodiment (step <b>3204</b>). Thereafter, the configuration information filtering program <b>133</b> generates a hierarchical information table <b>901</b> showing a location in a map including the symbol of the managed terminal <b>20</b> by the filtering section <b>132</b> which filters required information from a configuration information table <b>112</b> based upon the IP address received from the managed terminal <b>20</b> as in the first embodiment. However, in the fourth embodiment, the configuration information filtering program <b>133</b> further informs the configuration information display program <b>136</b> of the managed terminal <b>20</b> of a relocated (modified) hierarchical information table <b>901</b> after the generated hierarchical information table <b>901</b> is relocated according to the contents determined in the step <b>3204</b> (step <b>3205</b>).

[0170] For example, in a managed terminal <b>20</b> the memory capacity <b>3102</b> of the work memory <b>22</b> is 10 MB or less and the CPU format of CPU <b>29</b> is CPU-A. A partial network configuration related to the managed terminal <b>20</b> is displayed in an inclusive tree in which symbol images, each of which includes a symbol name, are connected. The symbol information of each symbol includes the identifier <b>902</b> and the symbol name <b>903</b> in the relocated hierarchical information table <b>901</b>. In the managed terminal <b>20</b>, when the configuration information display section <b>135</b> receives the hierarchical information table <b>901</b> from the configuration information filtering program <b>133</b> of the network management system <b>10</b>, the configuration information display section <b>135</b> stores the received hierarchical information table <b>901</b> in the work memory <b>22</b> and informs the configuration information filtering program <b>133</b> of a request for transferring configuration information together with the identifier <b>902</b> of a symbol in a high order of the symbol of the managed terminal <b>20</b> in the hierarchical information table <b>901</b> as in the first embodiment (step <b>3206</b>).

[0171] In the network management system <b>10</b>, when the configuration information filtering program <b>133</b> receives the request for transferring configuration information and the identifier <b>902</b> of the symbol from the managed terminal <b>20</b>, the hierarchical symbol acquiring section <b>138</b> of the configuration information filtering program generates a display information table <b>110</b> storing the symbol information of all symbols included in a map pulled down from the symbol shown by the received identifier <b>902</b>. Thus, the display includes all symbols included in a map including the symbol of the managed terminal <b>20</b> as in the first embodiment. However, in the fourth embodiment, the hierarchical symbol acquiring section <b>138</b> further informs the configuration information display program <b>136</b> of the managed terminal <b>20</b> of a relocated (modified) display information table <b>1101</b> after relocating the generated display information table <b>1101</b> according to contents determined in the step <b>3204</b> (step <b>3207</b>).

[0172] For example, in a managed terminal <b>20</b> the memory capacity <b>3102</b> of the work memory <b>22</b> is 10 MB or less and the CPU format of CPU <b>29</b> is CPU-A. Partial network configuration related to the managed terminal <b>20</b> is displayed in an inclusive tree in which symbol images, each of which includes only a symbol name, are connected. The symbol information of each symbol includes the identifier <b>1102</b> and the symbol name <b>1103</b> as shown in FIG. 33 in the relocated display information table <b>1101</b>.

[0173] In the managed terminal <b>20</b>, the configuration information display section <b>135</b> of the configuration information display program <b>136</b> receives the display information table <b>1101</b> from the configuration information filtering program <b>133</b> of the network management system <b>10</b>. The configuration information display section <b>135</b> displays partial network configuration related to the managed terminal <b>20</b> based upon the display information table <b>1101</b> and the hierarchical information table <b>901</b> stored in the work memory <b>22</b> in step <b>3206</b>. The partial network configuration is displayed in an containment tree as in the first embodiment (step <b>3208</b>).

[0174] In step <b>3208</b>, the configuration information display section <b>135</b> of the configuration information display program <b>136</b> executes the operation shown in the flowchart in FIG. 12. However, in the fourth embodiment, the contents of the configuration information internal table <b>1301</b> generated in the step <b>1201</b> are different according to the hierarchical information table <b>901</b> and the display information table <b>110</b> respectively received from the configuration information filtering program <b>133</b> of the network management system <b>10</b>. The symbol image created in the step <b>1204</b> is also different according to the configuration information internal table <b>1301</b>.

[0175] For example, in a managed terminal <b>20</b> the memory capacity <b>3102</b> of the work memory <b>22</b> is 10 MB or less and the CPU format of CPU <b>29</b> is CPU-A. As the symbol information of each symbol respectively includes the identifier <b>902</b>, <b>1102</b> and the symbol name <b>903</b>, <b>1103</b> in the received hierarchical information table <b>901</b> and display information table <b>1101</b>, the configuration information display section <b>135</b> generates a configuration information internal table <b>1301</b> including items of the identifier <b>1302</b>, the symbol name <b>1305</b>, the hierarchy <b>1306</b> and the higher order symbol <b>1308</b>. Also, as the configuration information display section <b>135</b> generates and locates a symbol image including the symbol name <b>1305</b>, if such a configuration information internal table <b>1301</b> is generated, an containment tree screen <b>1601</b> in which symbol images <b>3401</b>, each of which includes the symbol name <b>1305</b> connected as shown in FIG. 34, is displayed on the display <b>25</b> of the managed terminal <b>20</b>.

[0176] As described above, according to the fourth embodiment, partial network configuration related to a managed terminal <b>20</b> can be preferentially displayed in an containment tree as in the first embodiment. When network management is executed from the managed terminal <b>20</b> a user using the managed terminal <b>20</b> is not required to retrieve the symbol of the managed terminal <b>20</b> and can immediately execute network management.

[0177] Further, according to the fourth embodiment, contents to be displayed can be changed according to the performance of the managed terminal <b>20</b>. For example, a part of display information can be deleted when partial network configuration related to the managed terminal <b>20</b> is displayed in an inclusive tree. Thus, the load of the managed terminal <b>20</b> can be reduced.

[0178] In the fourth embodiment, the performance of a managed terminal is defined by the memory capacity <b>3102</b> of its work memory <b>22</b> and the CPU format <b>3103</b> of CPU <b>29</b>. However, the fourth embodiment is not limited to a situation where only information defining the performance of a managed terminal <b>20</b> effects the processing of the configuration information display program <b>136</b>. Any other information can be collected by the terminal information gathering section <b>134</b> and used to effect processing of the configuration information display program <b>136</b>.

[0179] As described above, the fourth embodiment is based upon the application of the first embodiment. The second and third embodiments are respectively independent of the first embodiment. However, it should be well understood by those of ordinary skill in the art that two or more of the first (or the fourth) to the third embodiments may be combined.

[0180] As described above, the present invention provides for partial information related to a managed terminal of information required for network management to be preferentially displayed on the managed terminal when network management is executed from the managed terminal. The present invention permits a user to easily manage the network by use of the network management system at any location in the network.

[0181] The present invention further provides for partial network configuration related to a managed terminal to be preferentially displayed in the form of an containment tree when the configuration of a network displayed in the form of a hierarchical map by a network management system is displayed on the managed terminal. The present invention permits a user to easily grasp the layout of the partial network configuration related to the managed terminal on one screen.

[0182] While the present invention has been described in detail and pictorially in the accompanying drawings it is not limited to such details since many changes and modifications recognizable to those of ordinary skill in the art may be made to the invention without departing from the spirit and the scope thereof.