JP2001075899A - Resource managing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make a resource managing device able to flexibly deal with the change or extension of the form of management in a resource managing device constituted by integrating a management object. SOLUTION: This resource managing device is provided with a management object 11 having information to be supplied to the monitor of the specific hierarchy of resources to be monitored as a data base 10, for executing an operation based on the procedure of the management to the data base and a single or plural instances 12 for executing prescribed processing related with the management of the low rank hierarchy. In this case, the instances individually inform the management object of both or one of the situations and phenomena of the low rank hierarchy, and the management object is constituted by summarizing both or one of the situations and phenomena indicated by messages communicated by the instances.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a resource management apparatus provided with a management object adapted to a hierarchical structure of resources and managing the resource under the initiative of the management object.

[0002]

2. Description of the Related Art In recent years, mobile communication networks, the Internet, and other communication networks have rapidly spread, and these communication networks are required to have high reliability in accordance with increasing importance in social activities. Further, adaptation to the increase of users in these communication networks and provision of new forms of services are realized by performing monitoring control and maintenance / operation at low cost and with high accuracy.

[0003] Therefore, for monitoring and controlling such a communication network, there are many distributed objects that achieve flexible adaptation and high availability with respect to an increase in the scale of hardware and software and a change in configuration. Is being done.
FIG. 15 is a diagram illustrating a configuration example of a network management system to which a distributed object is applied.

In the figure, devices (for example, node devices) to be monitored and controlled are denoted by reference numerals “60-T1 to 60-T”.
3 "," 60-N1 ", and" 60-O1 ", three geographically separated regions (here, for simplicity,
Assume "Tokyo", "Nagoya", and "Osaka". )
And these devices 60-T1 to 60-T3, 6
0-N1 and 60-O1 to 60-O2 are communication links 61-
Server 62-T via T1-61-T3, 61-1N, 61-O1,
Connected to 62-N and 62-O. These servers 62-T,
62-N and 62-O are communication links 63-T and 63-
N, 63-O is connected to the corresponding communication port of the client 64.

[0005] By the way, as shown in FIG. 16, three packages 60P-T11 to 60P-T13 and a single package 6 are provided as devices to be monitored and controlled in the devices 60-T1 to 60-T3.
0P-T21 and two packages 60P-T31 to 60P-T32
Are provided respectively. Device 60-N1 and device 60-O1
As shown in FIG. 16, 3
One package 60P-N11 to 60P-N13 and two packages 60P-O11 to 60P-O12 are provided.

A server 62-T shown in FIG. 15 includes:-an NE manager 6 for interfacing with the communication links 61-T1 to 61-T3 in a desired layer including a physical layer.
2NE-T; a communication processing unit 62C-T that takes an interface with the communication link 63-T in a desired layer including a physical layer; and an MIB (Management Information Base) 6 described later.
And a processor (not shown) in which 2MI-T is incorporated as software.

[0007] The MIB62 MIB-T includes:-packages 60P-T11 to 60P-T13, 60P-T21,
A database (DB) 62DB-T in which states and settings relating to the 60P-T31 to 60P-T32 are to be registered; and-a package 60P-T11 to 60P-T13, 60P-T21, which is activated in response to a message described later. 60P-T31
A circuit pack 62CP-T, which is a "managed object" comprising a set of agents that perform processing related to monitoring and control of the 60P-T32, and a package 60P-T11 to 60P-T13 that is activated in response to a message to be described later. 60P-T21, 60P-T31
The device holder 62EH-T, which is a "managed object" consisting of a set of agents that perform processing related to monitoring and control of individual shelves on which the .about.60P-T32 is to be mounted; 6
And a network element 62NWE-T, which is a "managed object" configured as a set of agents that perform processing related to monitoring and controlling the network formed by 0-T1 to 60-T3.

[0008] The configuration of the servers 62-N and 62-O and the MIs individually incorporated in these servers 62-N and 62-O.
B (Management Information Base) 62 MIB-N, 62M
Regarding the configuration of the IB-O, the subordinate devices 60-N1,
Although the number of 60-O1 to 60-O2 is different, the package 60P-N
The correspondence relationship with 11-60P-N13 and 60P-O11-60P-O12 is the package 60P-T11-60P in the server 62-T.
-T13, 60P-T21, and 60P-T31 to 60P-T32, the corresponding components are denoted by the suffixes "N" and "O" instead of the suffix "T". The description is omitted here.

The above-mentioned package 60P-T11-6
0P-T13, 60P-T21, 60P-T31 to 60P-T32, Package 60P-N11 to 60P-N13, 60P-O11 to 60P-O
Regarding 12, in the following, for simplicity, as shown in FIG. 16, the mounted devices 60-T1 to 60-T3,
Regardless of 60-N1, 60-O1 to 60-O2 (area of description), third subscripts "1" to "3", "1", Identifiers “pk1” to “pk” obtained by adding “1” to “2” to the character string “pk”
3 "," pk1 ", and" pk1 "to" pk2 "as appropriate.

The devices 60-T1 to 60-T3, 60-N1, 6
About 0-O1 ~ 60-O2, below, for simplicity,
As shown in FIG. 16, the second subscripts "1" to "3", "1", "1" assigned to the reference numeral "60" for each area regardless of the area where the area is installed. Identifiers “U1” to “U” obtained by adding “2” to a character string “U”
3 "," U1 ", and" U1 "to" U2 "as appropriate.

Further, regarding a network formed by the devices 60-T1 to 60-T3, a network formed by the devices 60-N1, and a network formed under the cooperation of the devices 60-O1 to 60-O2. In the following, for simplicity, as shown in FIG.
It is appropriately indicated by "NE2" and "NE3". The client 64 includes: a communication interface unit (not shown) that interfaces with the communication links 63-T, 63-N, and 63-O.
And • a terminal (not shown) provided for a man-machine interface with a person involved in monitoring and control; • a circuit pack that is activated in response to a message described later and is a “managed object” described above. 62CP
-T, 62CP-N, 62CP-O, device holder 62EH-T,
A root object 65 which is a “management object” comprising a set of agents that perform processing related to monitoring and control for each site where the 62EH-N and 62EH-O and the network elements 62NWE-T, 62NWE-N and 62NWE-O are installed. Are provided as shown in FIG.

In the network management system having such a configuration, for example, if any failure occurs in the package 60P-T12 provided in the device 60-T1, the device 60-T1 is sent to the circuit pack 62CP-T. Figure 1
As shown in Fig. 7, this fault is as follows:-The identifier "CP-T" of the circuit pack 62CP-T
・ The identifier of the generated instance (hereinafter referred to as “source instance identifier”) “Tokyo / NE1 / U1 / pkg2”
And ・ Sensing importance indicating the importance (here, for simplicity,
Assume "Minor". ) And ・ “Assumption factors” that indicate the details (here, for simplicity,
Assume that it is identified by device 60-T1. ) And • generating alarm information including the time of occurrence.

Further, the device 60-T1 (package 60P)
The higher-level management object including -T12 as an instance) sends the alarm information as a “message”. Here, the “message” is configured to include an identifier of an object to be subjected to a predetermined process according to the above-described alarm information and a “method” to be activated for performing the process by the object. .

The circuit pack 62CP-T performs predetermined processing in response to such a message, and transmits and receives messages as needed in the course of the processing, so that the device holder 62EH-T, which is another management object, the network element 62NWE-T and root object 6
Works with all or part of 5. Note that the procedure of such processing and the contents and format of the message are not features of the present invention, and a description thereof will be omitted here.

Further, in the above-described linking process, the device holder 62EH-T and the network element 62NWE-T
And the root object 65 is a package 60P-T
11-60P-T13, 60P-T21, 60P-T31-60P-T32
18-20 for the failures and other events that occurred in
As shown by shading, the total number of lower-level objects (subordinate instances); and of these objects (instances), the objects (instances) whose operation state is enabled
And collects and identifies alarm information that consists of those objects (instances) that are outputting alarms and that is adapted to each layer of the configuration of the communication system.

The alarm information shown in FIG. 17 includes not only "Minor" indicating the occurrence of a minor fault, "Major" indicating the occurrence of a serious fault, "Cleared" or other meaning of recovery may be included as the sensing importance.

[0017]

By the way, in the above-mentioned conventional example, for example, the circuit pack 62CP-T includes the subordinate packages 60P-T11 to 60P-T13, 60P-T21, and 6P-T13.
Of the packages 0P-T31 to 60P-T32, the number of packages in which an event such as a failure has occurred is monitored as a database and updated as appropriate.

However, the root object 65, the network element 62NWE-T and the device holder 62E
As shown in FIGS. 18 to 20, the HT grasps an event such as a failure in units of only the above-described site (network element), device (device holder), and shelf (circuit pack). Among the subordinate packages, there is no attribute that gives the total number of failed packages as described above.

Therefore, of the packages under the control of any one of the desired sites, devices and shelves, the operator is connected to the client 64 and via a terminal provided with the man-machine interface. To be notified of the total number of circuit packs:-Circuit packs 62CP-T, 62CP-N, 62C
PO and device holders 62EH-T, 62EH-N, 62EH
-O and network element 62NWE-T, 62NW
By linking the E-N and the 62NWE-O, the packages 60P-T11 to 60P are addressed to the root object 65.
-T13, 60P-T21, 60P-T31 to 60P-T32, 60P-N
Fault information indicating faults of 11 to 60P-N13 and 60P-O11 to 60P-O12 is notified, and the root object 65 keeps a history of the failure information, and calculates a desired total number by referring to the history. "The first way"
When the request is given via the terminal, the root object 65 is stored in the circuit packs 62CP-T and 62CP.
-N, 62CP-O and device holder 62EH-T, 62EH-
N, 62EH-O and network element 62NWE-
T, 62NWE-N and 62NWE-O are linked with all or a part of them, and are provided through these objects and accumulate the number of failed packages or devices. Is applicable.

However, in the above-mentioned "first method", the more the number of packages and devices to be monitored and controlled, the more the communication links 61-T1 to 61-T3, 61-N1, and 61-O1 to 61-. O
2, 63-T, 63-N, 63-O, and the path used for inter-process communication between the above-described objects, are faults that increase traffic and occur in parallel with multiple packages and devices. Since there is a high possibility that a congestion state will occur due to such an event, it has been difficult to apply the system in practice because of restrictions on costs and reliability.

In addition, since the “second method” generally requires a longer time to obtain the above-mentioned number from all desired packages and devices than the “first method”, monitoring is not necessarily performed. Communication links 61-T1 to 61-T3, 61-N1, 61-O1 to 61 that do not conform to the control mode
-O2, 63-T, 63-N, 63-O and the transmission capacity of the path are:
It was difficult to secure enough due to cost and reliability constraints.

Further, in the conventional example, in order to perform centralized monitoring control for each of the sites "Tokyo", "Nagoya", and "Osaka", for which monitoring control has already been performed individually, a network shown in FIG. The root object 6
5 and network element 62NWE-T, 62NWE
-N, 62NWE-O, a network object 66, for example, must be provided as a management object above these network elements 62NWE-T, 62NWE-N, 62NWE-O.

However, in such a case, the route object 65 and the network element 6
The compatibility of the instance identifier to be included in the message passed between 2NWE-T, 62NWE-N, and 62NWE-O is not maintained. Therefore, for all of the three sites described above, the methods and the like of all the management objects have to be modified.

An object of the present invention is to provide a resource management apparatus which can flexibly adapt to a change or expansion of a management form without largely changing the basic configuration of an existing management object. .

[0025]

FIG. 1 is a block diagram showing the principle of the present invention.

According to the first aspect of the present invention, for a specific layer of a resource to be managed, information used for the management is provided as a database 10, and an operation based on the management procedure is performed in the database 10. A management object 11 to be applied, and a single or a plurality of instances 1 for performing a predetermined process related to management for a hierarchy lower than a specific hierarchy
In the resource management device provided with 2-1 to 12-n, single or multiple instances 12-1 to 12-n are individually and / or individually generated with respect to the lower hierarchy. To the managed object 11 as a message. The managed object 11 fetches the messages notified by the single or multiple instances 12-1 to 12-n, and either or not the situation and / or the event indicated by these messages. It is characterized in that one of them is consolidated.

According to a second aspect of the present invention, in the resource management apparatus according to the first aspect, the management object 11 aggregates at least one of a situation and an event for each specific attribute. Features. According to a third aspect of the present invention, in the resource management device according to the second aspect, the single or the plurality of instances 12-1 to 12-n include a message indicating a situation and an event to be notified as the message. Add unique attributes to both or one of them,
For each value of a specific attribute added to a message notified by one or more instances 12-1 to 12-n, the management object 11 aggregates the status and / or event indicated by the message. Is characterized.

According to a fourth aspect of the present invention, in the resource management apparatus according to any one of the first to third aspects,
The single or plural instances 12-1 to 12-n aggregate the status and / or the event in a chronological order over a predetermined period, and send a result of the aggregation to the management object 11 as a message. It is characterized by being notified as.

According to a fifth aspect of the present invention, in the resource management device according to any one of the first to fourth aspects,
The management object 11 is characterized by notifying the management object 13 above the management object 11 of the result of aggregation as a message. FIG.
It is a principle block diagram of the invention as described in ~ 9.

According to a sixth aspect of the present invention, information for management of one or a plurality of P subsystems 21-1 to 21-P to be managed is provided as a database 22. In response to the management object 23 for performing an operation based on the above procedure on these databases 22 and the identifiers of the single or multiple P subsystems 21-1 to 21-P, these subsystems 21-1 to 21-P Communication paths 24-1 to 24-2 individually formed between the management object 22 and
Storage means 25 in which a communication path identifier indicating 4-P is registered in advance
The management object 23 is provided from the outside or generated based on a management procedure, and includes a message including an identifier of a subsystem to be a destination among these subsystems 21-1 to 21-P. Depending on the communication channel 2
Storage means 25 corresponding to the identifier among 4-1 to 24-P
A message obtained by excluding the identifier from the message is transmitted to a communication path indicated by a communication path identifier registered in the above.

The present invention according to claim 7 is a system for managing one or a plurality of P subsystems 21A-1 to 21A-P to be managed.
Information for the management of the
A, and based on this management procedure, the communication path 24
A message is transferred to and from these subsystems 21A-1 to 21A-P via A, and a management object 23A for operating the database 22A is provided. 21A-1 to 21A-P, and a logical channel 26-1 on a physical communication path based on a datagram method.
26-P, and the management object 23A is
Given from outside or generated based on management procedures, among these subsystems 21A-1 to 21A-P,
The logical channel indicated by the identifier or unique information obtained by performing a predetermined operation on the identifier among the logical channels 26-1 to 26-P according to the message including the identifier of the subsystem to be the destination This message is transmitted.

The invention according to claim 8 has, as a database 22, information for single or plural P subsystems 21-1 to 21-P to be managed. In response to the management object 23 for performing an operation based on the above procedure on these databases 22 and the identifiers of the single or multiple P subsystems 21-1 to 21-P, these subsystems 21-1 to 21-P Communication paths 24-1 to 24-2 individually formed between the management object 22 and
Storage means 25 in which a communication path identifier indicating 4-P is registered in advance
And the management object 23 includes the communication paths 24-1 to 24-2.
When a message is given via any of 4-P,
Storage means 25 corresponding to the communication path identifier indicating the communication path;
Of the subsystems 21-1 to 21-P, and the identifier is applied as identification information indicating the subsystem that is the transmission source of this message.

According to the ninth aspect of the present invention, there is provided a single or plural P subsystems 21A-1 to 21A-P to be managed.
Information for the management of the
A, and based on this management procedure, the communication path 24
A is configured as a managed object 23A that transfers messages to and from these subsystems 21A-1 to 21A-P via A and operates the database 22A. The managed object 23A is a single or multiple P subsystems. When a message is given by any of the subsystems 21A-1 to 21A-P via the communication path 24A, an identifier of a transmission source included in the message is obtained, and the identifier or the identifier It is characterized in that unique information obtained by performing a predetermined operation is applied as identification information indicating a subsystem that is a transmission source of this message.

In the resource management apparatus according to the first aspect of the present invention, the management object 11 performs an operation based on a management procedure on information held as a database 10 for a specific hierarchy of a resource to be managed, and The instances 12-1 to 12-n perform predetermined processing on a layer lower than the specific layer. In the process of such management, the instances 12-1 to 12-n individually and / or individually send a status and / or an event to the management object 11 in the lower hierarchy described above as a message.
Notify. The management object 11 aggregates the status and / or the event indicated by each message notified by the instances 12-1 to 12-n.

That is, the management object 11 stores the status of the instances 12-1 to 12-n, which can change every moment, and / or the event individually generated in each of the instances 12-1 to 12-n. Can be identified and put together according to the message described above. Therefore, the status of the instances 12-1 to 12-n and / or the events occurring in the instances 12-1 to 12-n are comprehensively grasped by the management object 11.

In the resource management apparatus according to the second aspect of the present invention, in the resource management apparatus according to the first aspect, the management object 11 may include, for both or one of a situation and an event, a specific attribute. Aggregate to

In general, this specific attribute can be set as an attribute suitable for the configuration and operation form of the resource for a specific layer of the resource to be managed.
Therefore, the situations and events obtained by linking with the instances 12-1 to 12-n are integrated by the management object 11 under an appropriate division that maintains consistency with the above-described resource configuration and operation mode. Is grasped.

In the resource management apparatus according to the third aspect of the present invention, in the resource management apparatus according to the second aspect, the instances 12-1 to 12-n may include a message indicating a situation to be notified as a message. A unique attribute is added to both or one of the events. The management object 11 aggregates, for each value of the specific attribute added to the message notified in this way, one or both of the situation and the event indicated by the message.

That is, the above-described situations and events are comprehensively grasped by the management object 11 while being classified based on attribute values given under the initiative of the instances 12-1 to 12-n. Therefore, it is possible to flexibly adapt to the resource configuration and the operation form as compared with the case where such attribute values are given by the management object 11 initiatively.

According to a fourth aspect of the present invention, in the resource management apparatus according to any one of the first to third aspects, the instances 12-1 to 12-n
Collects a situation and / or an event in a chronological order over a predetermined period, and notifies the management object 11 of the result of the aggregation as a message. That is, the amount of information of messages and other information to be delivered from the instances 12-1 to 12-n to the management object 11 is significantly reduced as compared with the case where the above-described situations and events are delivered individually as messages.

Therefore, unnecessary occurrence and acceleration of an overload state or a congestion state can be avoided with high accuracy as compared with the resource management apparatus according to the first to third aspects. According to a fifth aspect of the present invention, there is provided the resource management apparatus according to the first to fourth aspects, wherein the management object
Notifies the management object 13 above the management object 11 of the result of aggregation as a message.

The result of such aggregation includes the statuses of the instances 12-1 to 12-n and the instances 12-1 to 12-n.
Both or any of the events occurring in .about.12-n are included as a summary while the amount of information is compressed. Therefore, as long as the above-mentioned aggregation form conforms to the management object 13, the management object 13 manages the management object 11 in an appropriate form as an upper management object of the management object 11 while maintaining the connection with the management object 11 roughly. It can be carried out.

In the resource management device according to the sixth aspect of the present invention, the storage means 25 stores these subsystems 21-1 to 21 -P in correspondence with the identifiers of the subsystems 21-1 to 21 -P to be managed. Communication path identifiers indicating communication paths 24-1 to 24-P individually formed between 1 to 21-P and the management object 22 are registered in advance. The management object 23 is
For the above-described subsystems 21-1 to 21-P, an operation is performed on the database 22 including information to be used for management based on the management procedure.

In such a management process, the management object 23 is given from the outside or generated based on the management procedure described above, and is managed by the subsystems 21-1 to 21-1.
From 21-P, a message including the identifier of the subsystem to be the destination is obtained. Further, the management object 2
3 is a message obtained by excluding the identifier from the message to the communication path indicated by the communication path identifier registered in the storage means 25 corresponding to the identifier among the communication paths 24-1 to 24-P. Is sent.

That is, messages to be delivered not only to the subsystems 21-1 to 21-P but also to any of the managed objects and instances that are constituent elements of these subsystems 21-1 to 21-P Compatibility with the messages delivered in the process in which the management of the subsystems 21-1 to 21-P is individually performed under the superordinate management object is maintained.

Therefore, the management object 23 performs desired operations on the management objects and instances that are the constituent elements of the subsystems 21-1 to 21-P, on the database of these management objects and instances. By issuing a request to indicate that the sub-systems 21-1 to 21-P are to be managed, management related to these subsystems 21-1 to 21-P can be initiatively performed.

In the resource management apparatus according to the seventh aspect of the present invention, the subsystem 2
The communication path 24A used for delivery of messages to 1A-1 to 21A-P is composed of these subsystems 21A-1 to 21A-P.
21A-P, and are formed as logical channels 26-1 to 26-P based on the datagram method on a physical communication path.

The management object 23A is given from the outside or generated based on a management procedure.
Further, a message including an identifier of a subsystem to be a destination among the subsystems 21A-1 to 21A-P is acquired. Further, the management object 23A sends this message to the logical channel indicated by the identifier or unique information obtained by performing a predetermined operation on the identifier among the logical channels 26-1 to 26-P.

That is, a message to be delivered from the management object 23A to any of the subsystems 21A-1 to 21A-P is converted into a message conforming to the above-described datagram method, so that the routing accuracy is improved. Done high.

Therefore, as compared with the case where such routing is performed by selecting a physical channel, the load of communication control related to message delivery is greatly reduced, and the configuration is simplified. In the resource management apparatus according to the eighth aspect, the storage means 25 stores the subsystems 21-1 to 21-21 to be managed.
These subsystems 21-1 to 21-P correspond to the identifiers of -P.
Communication path identifiers indicating communication paths 24-1 to 24-P individually formed between 21-P and the management object 22 are registered in advance. The management object 23 performs an operation on the above-described subsystems 21-1 to 21-P on the database 22 including information to be used for management based on the management procedure.

In such a management process, when a message is given via any of the above-described communication paths 24-1 to 24-P, the management object 23 adds the message to the communication path identifier indicating the communication path. Correspondingly, an identifier registered in the storage means 25 is obtained, and among the subsystems 21-1 to 21-P,
The identifier is applied as identification information indicating the subsystem that is the source of the message.

That is, not only the subsystems 21-1 to 21-P, but also messages to be delivered from the managed objects and instances that are constituent elements of these subsystems 21-1 to 21-P,
-1 to 21-P are individually managed under a higher-level management object, and maintain compatibility with messages delivered.

Therefore, the management object 23 executes the operation given as the message to the database 22 described above in response to the message given by the management object and the instance which are the constituent elements of the subsystems 21-1 to 21-P. By doing so, management related to these subsystems 21-1 to 21-P can be performed in a leading manner.

In the resource management apparatus according to the ninth aspect of the present invention, the management object 23A is
When a message is given by any of the subsystems 1A-1 to 21A-P via the communication path 24A,
An identifier of a transmission source included in the message is obtained, and the identifier or unique information obtained by performing a predetermined operation on the identifier is applied as identification information indicating a subsystem that is a transmission source of the message.

That is, the management object 23A is transmitted from the subsystems 21A-1 to 21A-P to the management object 2A.
For the message to be delivered to 3A, based on the identifier contained in the message as described above,
Of the subsystems 21A-1 to 21A-P, the transmission source subsystem can be reliably identified. Therefore, compared with the case where such identification is performed by determining the physical channel used for delivery of the corresponding message, the load of communication control for message delivery is greatly reduced, and the configuration is reduced. Simplified.

[0056]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG.
FIG. 3 is a diagram showing an embodiment corresponding to the invention described in FIG. In the figure, components having the same functions and configurations as those shown in FIG. 15 are denoted by the same reference numerals, and description thereof is omitted here.

The difference between this embodiment and the conventional example shown in FIG. 15 is that servers 30-T, 30-N and 30-O are provided instead of servers 62-T, 62N and 62-O, respectively. It is in the point. The difference between the server 30-T and the server 62-T is that the circuit pack 30CP is used instead of the circuit pack 62CP-T.
The CP-T is incorporated, the device holder 30EH-T is incorporated in place of the device holder 62EH-T, and the 30NWE-T is incorporated in place of the network element 62NWE-T.

Note that the configuration of the servers 30-N and 30-O is the same as the configuration of the server 30-T. Therefore, in the following, the same reference numerals are given to the corresponding components, and these codes are appended. Subscripts "N" and "O" instead of the letter "T"
And the description thereof is omitted here. For the correspondence between the present embodiment and the block diagrams shown in FIGS. 1 and 2, for example, in the server 30-T, the database 62DB-T corresponds to the database 10, and the device holder 30EN-T (network element 30NWE-
T) corresponds to the management object 11, the circuit pack 30CP-T (device holder 30EH-T) corresponds to the instances 12-1 to 12-n, and the device holder 30EH-T (network element 30NWE-T) has a higher rank. Corresponds to the management object 13.

FIG. 4 is an operation flowchart (1) of the circuit pack in this embodiment. FIG. 5 is an operation flowchart of the circuit pack according to the present embodiment.
(2). FIG. 6 is an operation flowchart of the apparatus holder according to the present embodiment.

Hereinafter, referring to FIGS. 3 to 6, claims 1 to 5 will be described.
The operation of the present embodiment corresponding to the invention described in (1) will be described.
In the following, since the operations of the servers 30-T, 30-N, and 30-O are basically the same, for simplicity, only the server 30-T will be focused on in principle.

The circuit pack 30CP-T incorporated in the server 30-T has a reception buffer 41-T shown in FIG. Further, the circuit pack 30CP-T includes the communication link 61-T2 and the NE manager 62N as in the conventional example.
The alarm information in the format shown in FIG.
-T2, the instance identifier included in the alert information (hereinafter, “source instance identifier D
N ". ) And “sensing importance” are extracted (FIG. 4).
(a)), and as shown by hatching in FIG.
"Alarm history information" consisting of a combination of "N" and "sensing importance" is sequentially accumulated (FIG. 4B).

The circuit pack 30CP-T is provided in subordinate devices 60-T1 to 60-T3 as shown in FIG.
And packages 60P-T11 to 60P-T to be managed
13, 60P-T21, and 60P-T31 to 60P-T32 corresponding to the "source instance identifier DN", and these packages 60P-N11 to 60P-N13, 60P-T21, and 60P-T31 to 6
It has an alarm information management table 42-T in which the latest "sensing importance" actually given by the OP-T32 is to be stored.

Further, the circuit pack 30CP-T
Among the records of the alarm information management table 42-T, the "sensing importance" of the record corresponding to the "source instance identifier DN" included in the "alarm history information" is referred to (FIG. 4 ( 1)), the priority of sensing the failure (one of "Major" and "Minor") (hereinafter referred to as "preceding failure importance") of the failure that occurred earlier is identified (FIG. 4). Along with (2)), the “sensing importance” included in the “alarm history information” is stored in the record (FIG. 4).
(3)).

As shown in FIG. 9, the circuit pack 30CP-T includes:-devices 60-T1 to 60-T3 which are instances to be managed by a higher-level management object (class) of the circuit pack 30CP-T; And the upper-level instance identifier “pk1” to “pk3” included in the “source instance identifier DN” are excluded from the “source instance identifier DN” described above. "DN _U ", and "Major" and "Minor", which are the valid alarm severities indicated by the above "Sensitivity Priority" and not extinguished.
・ The perceived importance levels "Majorclr" and "Minorcl", which mean the extinction of alarms whose significance levels are "Major" and "Minor", respectively.
r), and provides the storage of the `` difference count value '', which is the number of identified alert information of these sensing importance levels `` Major '', `` Minor '', `` Majorclr '' and `` Minorclr ''. And two storage areas (hereinafter simply referred to as “surfaces”) where writing and reading should be performed alternately for each period described later.
That. ) Is provided.

For the sake of simplicity, the “difference count value” is the sign of the value corresponding to the sense importance “Major” and “Minor” and the value corresponding to the sense importance “Majorclr” and “Minorclr”. Are different. Circuit Pack 30CP-T
New “alarm history information” in the alarm information management table 42-T
Each time that stores, by excluding the least significant identifier described above from the contained in the "alarm history information,""sender interface instance identifier DN", obtains the level instance identifier DN _U (Fig. 4 (4)) .

Further, the circuit pack 30CP-T
The “sensing importance” included in the “alarm history information” is “Ma
It is determined whether it corresponds to either “jor” or “Minor” (FIG. 4 (5)). If the result of the determination is true, the event compression buffer to be written at that time 4
3-T surface (hereinafter referred to as "write target buffer")
Of the record, increments the "difference count" of the record corresponding to its level instance identifier DN _U described above as "sensing importance" (FIG. 4 (6)).

If the result of the above-described determination is false, the circuit pack 30CP-T reads out the record of the write target buffer if the above-mentioned “preceding failure importance” is “Major”. , The previously described sensing importance "Majorclr"
And decrements the "differential count" of the record corresponding to the upper instance identifier DN _U (Fig. 4 (7)). However, if the "prior Failure importance" is "Minor" is, circuit packs 30 cP-T, of the write target buffer records correspond sensing importance as "Minorclr" into upper instance identifier DN _U The “difference count value” of the record is decremented (FIG. 4 (8)).

Therefore, the event compression buffer 43-T
The, for the circuit pack 30 cP-T higher managed object (class) device which is individual instances to be managed by the holder 30EH-T (. Represented by aforementioned level instance identifier DN _U), that circuit pack Out of all the packages to be managed by the 30CP-T, a package with a detection severity of "Major" and "Minor" has occurred and the recovery has not been completed. Out of the packages that have been restored, the latest number of the packages that have recovered from the corresponding failure is individually stored as a difference count value.

Further, the circuit pack 30CP-T
For each predetermined cycle, the event compression buffer 43-T
Of the upper instance identifier DN _U in the two aspects of
And the surface to be read (hereinafter referred to as “read target buffer”) corresponding to
A series of processes shown in (6) are individually performed. (1) Overall instance identifier DN _U to determine the "differential count" the most recent of which individually corresponding to (FIG. 5 (1)).

(2) In the “difference count value”, the difference count value corresponding to the sense importance “Major” is replaced with the sum of the difference count value and the difference count value corresponding to the sense importance “Majorclr”, The difference count value corresponding to the sense importance “Majorclr” is set to “0”, and the difference count value corresponding to the sense importance “Minor” is set to the difference count value and the sense importance “Minorclr”.
And the difference count value corresponding to the sense importance "Minorclr" is set to "0" (FIG. 5 (2)).

(3) As shown in FIG. 10, the device holder 30EH which is a higher-level management object
And -T identifier "EH-T", a level instance identifier DN _U to-relevant and updated in the course of, the above-described processing (2) a "difference count", client 64 (root object 65) addressed Then, “general alarm information” including control information indicating whether or not notification is necessary is generated (FIG. 5 (3)).

(4) This “general alarm information” is transmitted to the device holder 30EH-T via the channel provided for inter-process communication (FIG. 5 (4)). (5) Switching between the surface to be written and the surface to be read (FIG. 5 (5)). (6) Initialization is performed to set the “difference count value” individually included in all records of the newly written surface to the initial value “0” (FIG. 5 (6)).

In the device holder 30EH-T, the “difference count value” included in the “general alarm information” described above corresponds to each of the above upper instance identifiers DN _U (devices to which the code “60-T” is assigned). And a register (not shown) to be stored. Furthermore, the device holder 30EH-T
When a new "integrated alarm information" is given, this register of the storage area, the "final alarm information" to a higher instance identifier DN was stored prior to the storage area corresponding to the _U "difference meter included The “numerical value” is individually summed with the “difference count value” included in the new “general alarm information” to update these “difference count values” (FIG. 6 (1)).

The device holder 30EH-T transmits the control information contained in the “general alarm information” to the client 64.
(To the root object 65), the "general alarm information"
To determine whether or not it should be notified (FIG. 6 (2)),
If the result of the determination is false, no special processing is performed. However, if the result of this determination is true, the device holder 30EH corresponds to the network element 30NWE-T, which is a higher-level management object (class), via a channel provided for inter-process communication. The alarm information is relayed (FIG. 6 (3)).

Further, the network element 30NW
ET is the upper management object (class) in the same way.
This "total alarm information" is relayed to the root object 65. By the way, the device holder 30EH-T
As shown with parentheses in FIG.
Compared with the -T, the latest "difference count value" actually given by the circuit pack 30CP-T (devices 60-T1 to 60-T3) is stored instead of the "sensing importance". It has a reception buffer 41EH-T.

[0076] Furthermore, device holder 30EH-T, when the above-described "General alarm information" is provided by the circuit pack 30 cP-T, the upper instance identifier DN _U and "difference count" contained in the "final alarm information" Are extracted, and the “alarm history information” including the combination of the “upper instance identifier DN _U ” and the “difference count value” is sequentially accumulated in the reception buffer 41EH-T (FIG. 6 (4)).

The device holder 30EH-T is provided with the device 60-T to be monitored and controlled as shown in FIG.
“Higher-level instance identifier DN” that individually indicates 1 to 60-T3
_U ”and has an alarm information management table 42EH-T in which the latest“ difference count value ”actually given by the circuit pack 30CP-T (devices 60-T1 to 60-T3) is to be stored.

Further, the device holder 30EH-T stores the alarm information management table 42EH-T
The four “difference count values” included in the “alarm history information” are stored in the record corresponding to the “upper instance identifier DN _U ” included in the “alarm history information” (FIG. 6 (5)). The device holder 30EH-T also individually corresponds to a network which is an instance to be managed by a higher-level management object (class) of the device holder 30EH-T, as shown in FIG. from the above-described "upper instance identifier DN _U", and its lowest identifier U1 included in the "Top instance identifier DN _U", made ... is excluded "instance identifier DNa", - sensing importance "Major", " Minor ”,“ Majorclr ”, and“ Minorclr ”are used to store“ difference count values ”individually corresponding to all combinations, and writing and reading should be performed alternately every period described above. It has an event compression buffer 43EH-T composed of three planes.

Each time the device holder 30EH-T stores new “alarm history information” in the alarm information management table 42EH-T, the device holder 30EH-T starts from the “upper instance identifier DN _U ” included in the “alarm history information”. The instance identifier DNa is obtained by excluding the lowest identifier (FIG. 6 (6)). Further, the device holder 30EH-T stores the event compression buffer 4 to be written at that time.
In the record of the 3EH-T plane (hereinafter, referred to as “write target buffer”), the instance identifier D described above is used.
In the “difference count value” included in the record corresponding to Na,
The “difference count value” included in the “alarm history information” is individually integrated (FIG. 6 (7)).

Therefore, the event compression buffer 43E
The HT includes a network element 30NW which is a higher-level management object (class) of the device holder 30EH-T.
Included in each instance to be managed by ET (indicated by the instance identifier DNa described above),
Out of all the packages to be managed by the circuit pack 30CP-T, a package in which a failure whose sensing importance is "Major" and "Minor" has occurred and the restoration has not been completed; Among the packages in which a failure has occurred, the latest number of packages in which the corresponding failure has been recovered is individually stored as a difference count value.

The device holder 30EH-T corresponds to each instance identifier DNa among the two surfaces of the event compression buffer 43EH-T at every predetermined cycle, and the surface to be read out (described above). Hereinafter, the buffer will be referred to as a “read buffer”).
Are individually performed. (1) The latest “difference count value” individually belonging to the upper instance identifier DNa is obtained (FIG. 6A).

(2) In the “difference count value”, the difference count value corresponding to the sense importance “Major” is replaced with the sum of the difference count value and the difference count value corresponding to the sense importance “Majorclr”, The difference count value corresponding to the sense importance “Majorclr” is set to “0”, and the difference count value corresponding to the sense importance “Minor” is set to the difference count value, the sense importance, and “Minorclr”.
And the difference count value corresponding to the sense importance “Minorclr” is set to “0” (FIG. 6B).

(3) As shown in FIG. 10 together with parentheses, an identifier “NWE-T” of the network element 30NWE-T, which is a higher-level management object; an applicable instance identifier DNa; The “general alarm information” including the “difference count value” updated in the process 2) and the control information indicating whether or not the notification is required to the client 64 (the root object 65) is generated (FIG. 6 ( c)).

(4) This “general alarm information” is transmitted to the network element 30NWE-T via the channel provided for inter-process communication (FIG. 6 (d)). (5) Switching between the surface to be written and the surface to be read (FIG. 6 (e)). (6) Initialization is performed to set the “difference count value” individually included in all records of the newly written surface to the initial value “0” (FIG. 6 (f)).

Further, the network element 30NW which is a higher-level management object of the device holder 30EH-T
The ET performs the same processing as the above-described processing performed by the device holder 30EH-T, when the above-described “general alarm information” is given. That is, the circuit pack 30C
The PT, the device holder 30EH-T, the network element 30NWE-T, and the route object 65 are all mounted on a device to be monitored and controlled under the hierarchical hardware configuration shown in FIGS. Out of all the packages, the number of packages in which a failure has occurred can be grasped at the above-described cycle for each degree of importance of sensing the failure.

Also, the circuit pack 30CP-T, the device holder 30EH-T, the network element 30NWE
-T and the traffic of the channels provided for the inter-process communication between the route objects 65, the information to be delivered via these channels is the area, device,
Since the data is compressed by being aggregated in the unit of the shelf, even if the number of mounted packages and devices increases, the value is suppressed to a small value.

Therefore, according to the present embodiment, when an instruction is given by the operator, the failed packages are individually confirmed for each desired area, device, and shelf. Compared to the conventional example where the numbers had to be integrated, the total number and distribution of packages with some kind of failure can be obtained efficiently and accurately without the increase in load or congestion, and the maintenance and operation Effective utilization becomes possible.

In this embodiment, the devices 60-T1 to 60-T1
Describes the processing that each managed object cooperates in the process of delivering a failure that has occurred in any package mounted on 0-T3, 60-N1, 60-O1 to 60-O2, or a message indicating the recovery of the failure. Have been. However, the present embodiment is not limited to such a message. For example, the devices 60-T1 to 60-T3, 60-N1, 60-O1 to 60-O2
Units, or these devices 60-T1 to 60-T3, 60-N
The present invention is similarly applicable to a process in which a failure that has occurred in a unit of a shelf provided in 1, 60-O1 to 60-O2 or a message indicating recovery of the failure is delivered.

Further, these messages are not limited to the above-mentioned messages indicating the failure or the restoration of the failure. For example, all or some of the above-mentioned packages, shelves, and devices indicate whether or not they are implemented. The state of implementation, indicating the distribution of traffic, the concentration rate, the degree of congestion (in the case of the message exchange method, the occupancy rate of the payload, the number of logged-in subscribers), etc., and any other status or event Information may be included.

Further, in this embodiment, the importance of the faults that have occurred and the recovery of the faults corresponding to these importances are shown.
One of the three values is included in the alert information. However, instead of such alarm information, for example,
The present invention can be similarly applied to a case where alarm information is repeatedly given at a predetermined frequency and alarm information indicating both or one of the presence or absence of a failure as binary information or multilevel information is given. is there.

Further, in this embodiment, all the records of the event compression buffer 43-T (43EH-T) are resident in the main storage of the circuit pack 30CP-T (device holder 30EH-T) or in the database DB-T. ing. However, such an event compression buffer 43-T (43EH
For records -T), for example, some event is generated appropriately individually corresponding to level of the administrative objects that have occurred, or the aforementioned level instance identifier DN _U and instance identifier DNa to be notified, sensing important Assignment corresponding to both or one of the degrees may be appropriately performed.

Further, in this embodiment, in order to allow an increase in the traffic of the channel provided for the inter-process communication, the general alarm information may be sent to the higher-level management object aperiodically or appropriately. In the present embodiment, not only the above-described comprehensive alarm information but also, for example, a message that is output as a message by the circuit pack 30CP-T, and is relayed by the device holder 30EH-T and the network element 30NWE-T under a relay. 6
4 (the root object 65), a desired message is transmitted, or these circuit packs 30CP-
A desired message may be transmitted to the client 64 (the root object 65) as a result of the above-described processing performed in cooperation with the T, the device holder 30EH-T, and the network element 30NWE-T.

Further, such a message may appropriately include, for example, the time of occurrence of a failure and other additional information as shown by hatching in FIG. FIG.
It is a figure which shows the embodiment corresponding to the invention of Claims 6-9. In the figure, components having the same functions and configurations as those shown in FIG. 3 are denoted by the same reference numerals, and description thereof is omitted here.

The difference between the present embodiment and the embodiment shown in FIG. 3 lies in the configuration of the client 51 provided in place of the client 64. The client 51 includes: a terminal interface unit 53 for interfacing with a terminal 52 provided for a man-machine interface with the operator; and a communication laid between the servers 30-T, 30-N, 30-O. A communication processing unit 54 that takes an interface with a link in a desired layer including a physical layer; and an MIB (Management Information Base) 5 described later.
And a processor (not shown) incorporated as software.

The MIB 55 includes: a server 30 which is a lower system of the client 51;
-T, 30-N, a database (DB) 56 in which states and settings relating to 30-N are to be registered;-a root object 57 in place of the above-described root object 65;-activated in response to a predetermined message; Server 30-
T, 30-N, 30-N and devices 60-T1 to 60-T3, 60-N1,
A network 58 that is configured as a set of agents that perform predetermined processing related to monitoring and control of 60-O1 to 60-O2 and is a "managed object" below the root object 57; The subtree manager 59-1 is formed as a lower-level management object of the server 57 and interfaces with the servers 30-T, 30-N, and 30-N through the communication processing unit 54, as will be described later. Consists of

The correspondence between the present embodiment and the block diagram shown in FIG. 2 is described with reference to the servers 30-T, 30-N, 30-N.
-O indicates subsystems 21-1 to 21-P and 21A-1 to 21A-P
And the database 56 corresponds to the databases 22, 22.
A, the subtree manager 59 corresponds to the managed objects 23, 23A, and
-1 to 21-P, the communication link formed between 21A-1 to 21A-P and the communication processing unit 54 are communication paths 24-1 to 24-P,
4A, 26-1 to 26-P, and a lower system management table 59L-1 and a higher system management table 59 which will be described later.
U-1 corresponds to the storage means 25.

FIG. 13 is an operation flowchart of the present embodiment corresponding to the sixth to ninth aspects of the present invention. Less than,
With reference to FIGS. 12 and 13, the operation of the present embodiment corresponding to the inventions of claims 6 to 9 will be described. As shown in FIG. 14 (a), the subtree manager 59-1 is individually installed as software for the servers 30-T, 30-N, and 30-O, and is a managed object (lower-level instance). A certain network element (for example, network element 30NW
“E.T), an“ instance identifier DN _L ”that individually indicates: • an identifier“ / ”of the network 58 to be a higher-level management object for this network element;
“NW” is set as a constant, “correlation higher-level object name”, and a network element (for example, network element 30N) as an instance of network 58
“WE-T”, a “related instance identifier” (for example, “/ Tokyo”), and “the lower system host name that logically indicates the server (for example, server 30-T), which is a lower system described above. (For example, “Tokyo System”), and “destination information” individually indicating a server (for example, server 30-T) that is a source or destination of a message to be transmitted / received, and is registered in advance. It has a lower system management table 59L-1 in which "connection status" indicating the status of a communication link (path) formed individually with a server (for example, server 30-T) is to be stored.

Further, as shown in FIG. 14 (b), the subtree manager 59-1 makes the servers 30-T, 30-N, 30-O
For each region (site) where is installed, an “instance identifier” (for example, “/ Tokyo”) that is incorporated as software and logically indicates a server (for example, server 30-T) that is the lower-level system described above )
"Related object identifier" (for example, "Subtree Manager") indicating the subtree manager 59-1 which is a virtual upper management object of the corresponding network element (for example, network element 30NWE-T); An upper system management table 59U in which a "related instance identifier" (for example, "Tokyo System Manager") indicating a corresponding server (for example, server 30-T) as a lower instance of the subtree manager 59-1 is registered in advance. Has -1.

[0099] The root object 57 is provided, for example, in response to a request given by the operator via the terminal 52.
A message (hereinafter, referred to as a “down message”) to which an instance (indicated by the identifier “/ Tokyo / NE1”) to be monitored and controlled under -T is given via the terminal interface unit 53. Then, the "down message" is given to the subtree manager 59-1.

The subtree manager 59-1 is the server 3
It is determined based on a predetermined communication procedure whether or not the communication links (paths) individually formed between 0-T, 30-N, and 30-O are normal, and the result of the determination is determined by the lower system. "Connection status" of the corresponding record in the management table 59L-1
Store in field. Also, subtree manager 5
9-1 extracts a partial instance identifier "/ Tokyo" corresponding to the highest management object and indicating the above-mentioned area from the instance identifier "/ Tokyo / NE1" included in the downlink message (FIG. 13 (1)).

Further, the subtree manager 59-1
Among the records of the lower-level system management table 59L-1, a record in which the value of the “correlation instance identifier” field described above is equal to the partial instance identifier “/ Tokyo” described above (hereinafter, referred to as “target record”) is specified (FIG. FIG. 13 (2)). Also, the subtree manager 59-1
By referring to the value of the “connection status” field included in the target record, the server 30-T, 30
-N, 30-O, the partial instance identifier "/
It is determined whether the communication link (path) formed with the server corresponding to "Tokyo" is normal (FIG. 13 (3)).

Further, the subtree manager 59-1
Only when the result of this determination is true, the above-mentioned partial instance identifier “/ Tokyo” is excluded from the above-mentioned downlink message out of the instance identifiers “/ Tokyo / NE1” included in the downlink message. A "downlink transfer message" is generated (FIG. 13 (4)). Further, the subtree manager 59-1 communicates with the server 30 via the communication link (path) confirmed to be normal as described above.
-T (network element 30NWE-T), and sends the "downward transfer message" (FIG. 13 (5)).

On the other hand, the network element 30NWE
-T, and includes the network element 30NWE-T and other identifiers "/ NW ...", and a message to be transmitted to the root object (hereinafter referred to as an "up message") is sent to the communication processing unit 54. To the subtree manager 59-1.

The subtree manager 59-1 cooperates with the communication processing unit 54 to form the servers 30-T, 30-
N, 30-O (network element 30NWE-T, 3
0NWE-N, 30NWE-O), "destination information" indicating the transmission source of this uplink message is obtained (FIG. 13 (6)).
Further, the subtree manager 59-1 specifies a first record whose value of the "destination information" field is equal to the "destination information" among the records of the lower system management table 59L-1 (FIG. 13 (7)). ), The values of the “instance identifier DN _L ” field and “correlation superior object name” field of the first record (“Tokyo System Manager” and “/ NW”, respectively) are obtained (FIG. 1).
3 (8)).

The subtree manager 59-1 is the second record in the upper system management table 59U-1 in which the value of the "correlation instance identifier" field is equal to the value of this "instance identifier""Tokyo System Manager". Is specified (FIG. 13 (9)). Further, the sub-tree manager 59-1, by adding the value "/ Tokyo" in the instance identifier DN _U of the second record in higher identifier "/ NW ..." included in the upstream message as described above, "uplink "Transfer message" is generated (FIG. 13
(Ten)) . The “uplink transfer message” is given to the route object 57 (FIG. 13 (11)).

As described above, according to the present embodiment, the server 3
Even if the systems that have been individually monitored and controlled under the control of 0-T, 30-N, and 30-O are integrated under the control of the client 51, the messages to be exchanged with these systems are exchanged. Compatibility is guaranteed under the above-described processing performed by the subtree manager 59-1. Also, the root object 5
7 and the network 58 can identify a desired instance based on an identifier adapted to a logical hierarchical structure formed by integrating these systems, and can take a man-machine interface with the operator via the terminal 52. it can.

Therefore, according to the present embodiment, flexible adaptation to the addition of servers, which are lower-level systems, and the consolidation of servers to be monitored and controlled, can be achieved at low cost and with high accuracy. In the present embodiment, the routing of the downstream message and the upstream message to be delivered via the subtree manager 59-1 is performed according to the lower system management table 59L-1 and the upper system management table 5 described above.
9U-1 is realized.

However, for such a routing, the servers 30-T, 30-N,
If the format and contents of the messages transmitted and received by 30-O are compatible and the compatibility with the supervisory control system integrated by the network 58 is achieved under the initiative of the MAP manager 59-1, the lower system Management table 59
Any type of table may be applied instead of L-1 and the upper system management table 59U-1.

In each of the embodiments described above, the present invention is applied to the network management system. But,
The present invention is not limited to such a network management system, and can be applied to any device or system as long as desired resources are managed based on an object-oriented or distributed object system.

Further, in each of the above-described embodiments, hardware used for transmitting a message to be delivered between managed objects and a communication control procedure are not described in detail. However, these hardware and communication control procedures are not features of the present invention.
Since this can be realized by applying various known technologies such as RBA and distributed OLE, the description is omitted here.

Further, in each of the above-described embodiments, the processing performed by linking a plurality of managed objects and the operation target of the processing are described, and the configuration of software for implementing these managed objects is not described. . However, in general, a managed object is a database that implements a desired function and a database that implements a desired function, regardless of the configuration of the physical processor, database, task (thread), etc. that implements the managed object, or the geographical arrangement. It is defined as a set of programs that perform operations on them.

Therefore, such a software configuration has a desired communication link (including communication between processors).
Anything can be used as long as it can be linked via.

[0113]

As described above, according to the first aspect of the present invention, the status of each instance and / or the event that occurred in these instances are comprehensively grasped by the upper management object. .

According to the second aspect of the present invention, the statuses and events of the instances are appropriately divided in a form that maintains consistency with the configuration and operation form of the resources, and are comprehensively managed by the management object. Be grasped. Furthermore, according to the third aspect of the invention, it is possible to flexibly adapt to the configuration and operation of the resources, as compared with the case where the value of the attribute is given initiatively by the management object.

According to the fourth aspect of the present invention, unnecessary occurrence of an overload state or a congestion state and acceleration are avoided with high accuracy. Furthermore, in the invention described in claim 5, as long as the form of aggregation conforms to the lower-level management object, the higher-level management object performs management in an appropriate form while keeping the connection with the lower-level management object coarse. be able to.

According to the invention described in claim 6, the management object issues a request to the management object and the instance which are the constituent elements of the subsystem, thereby leading the supervisory control relating to these subsystems. It can be carried out. Further, according to the seventh and ninth aspects of the present invention, the load of communication control related to message delivery is greatly reduced, and the configuration is simplified.

According to the invention described in claim 8, the management object takes the initiative in monitoring and controlling the subsystems in response to messages given by the management objects and instances which are constituent elements of the subsystems. It can be carried out. Therefore, in the resource management system to which these inventions are applied, flexible management relating to lower layers can be realized inexpensively and efficiently without impairing the advantages of the object-oriented or distributed object system, and Reliability and service quality are improved.

[Brief description of the drawings]

FIG. 1 is a principle block diagram of the invention according to claims 1 to 5;

FIG. 2 is a principle block diagram of the invention according to claims 6 to 9;

FIG. 3 is a diagram showing an embodiment corresponding to the first to fifth aspects of the present invention.

FIG. 4 is an operation flowchart (1) of the circuit pack according to the embodiment.

FIG. 5 is an operation flowchart (2) of the circuit pack in the embodiment.

FIG. 6 is an operation flowchart of the apparatus holder according to the embodiment.

FIG. 7 is a diagram illustrating a configuration of a reception buffer.

FIG. 8 is a diagram showing a configuration of an alarm information management table.

FIG. 9 is a diagram showing a configuration of an event compression buffer.

FIG. 10 is a diagram showing a configuration example of general alarm information notified to a higher-level management object.

FIG. 11 is a diagram showing an example of a message transmitted to a client (root object).

FIG. 12 is a diagram showing an embodiment corresponding to the invention described in claims 6 to 9;

FIG. 13 is an operation flowchart of the present embodiment corresponding to the inventions of claims 6 to 9;

FIG. 14 is a diagram showing a configuration of a lower system management table and a higher system management table.

FIG. 15 is a diagram illustrating a configuration example of a network management system to which a distributed object is applied.

FIG. 16 is a diagram illustrating a configuration example of a communication system to be monitored and controlled.

FIG. 17 is a diagram showing a configuration of alarm information.

FIG. 18 is a diagram illustrating a configuration of monitoring information individually included in the device holder.

FIG. 19 is a diagram illustrating a configuration of monitoring information individually included in network elements.

FIG. 20 is a diagram illustrating a configuration of monitoring information individually included in a root object.

FIG. 21 is a diagram showing a model of an integrated supervisory control system.

[Explanation of symbols]

 10, 22, 22A database 11, 23, 23A management object 12 instance 13 upper management object 21, 21, A subsystem 24, 24A communication path 25 storage means 26 logical channel 30, 62 server 30CP, 62CP circuit pack 30EH, 62EH device holder 30NWE, 62NWE Network element 41, 41EH Reception buffer 42, 42EH Alarm information management table 43, 43EH Event compression buffer 51, 64 Client 52 Terminal 53 Terminal interface unit 54, 62C Communication processing unit 55, 62 MIB MIB 56, 62DB Database (DB) 57,65 Root object 58 Network 59 Subtree manager 59L Lower system management table 59U Upper Stem management table 60 device 60P package 61,63 communications link 62NE NE manager 66 network object

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5B089 GB10 KA07 KA08 KA10 KA13 KB03 KB06 KC15 KC28 KC54 5K030 GA08 GA11 GA16 HB16 JA10 KA02 KA07 MA01 MB01 MC07 MD07 9A001 CC07 JJ12 KK56 LL09

Claims (9)

[Claims] 1. A management object for a specific layer of a resource to be managed, which has information to be managed as a database, and performs an operation on the database based on the management procedure; In a resource management apparatus comprising a single or a plurality of instances for performing a predetermined process related to the management with respect to a lower hierarchy, Notify the managed object as a message to the managed object, and / or the managed object captures the message notified by the single or multiple instances, and compares the situation and the event indicated by these messages. A resource management device characterized in that both or any one of them is consolidated. 2. The resource management apparatus according to claim 1, wherein the management objects aggregate at least one of a situation and an event for each specific attribute. 3. The resource management device according to claim 2, wherein the single or the plurality of instances add an attribute specific to the situation and / or the event to be notified as the message to the message. The management object, for each value of a specific attribute added to the message notified by the single or multiple instances, aims to aggregate the situation and / or the event indicated by the message. Resource management device. 4. The resource management device according to claim 1, wherein the single or the plurality of instances include both a status and an event or a status and an event in a chronological order over a predetermined period. A resource management apparatus for performing any one aggregation and notifying a management object of a result of the aggregation as a message. 5. The resource management device according to claim 1, wherein the management object notifies a management object higher than the management object of a result of the aggregation as a message. Resource management device. 6. A management object for a single or a plurality of P subsystems to be managed, which has information provided for the management as a database, and performs operations based on the management procedure on these databases; Storage means in which communication path identifiers indicating communication paths formed individually between these subsystems and the management object are registered in advance in correspondence with the identifiers of the single or plural P subsystems The management object is provided from the outside or generated based on the management procedure, and in accordance with a message including an identifier of a subsystem to be a destination among these subsystems, the management object includes: The identifier is transmitted from this message to the communication path indicated by the communication path identifier registered in the storage means corresponding to the identifier. A resource management device for sending a message that has been excluded. 7. A system for managing one or a plurality of P subsystems to be managed, the database having information to be used for the management, and based on the management procedure, these subsystems are connected via a communication path. And a message that is passed, and is configured as a managed object that operates on the database. The communication path individually corresponds to the single or multiple P subsystems,
And a logical channel is formed on the physical communication path based on the datagram method, and the management object is given from outside or generated based on the management procedure, and is a destination among these subsystems. In response to the message including the identifier of the subsystem to be transmitted, the transmission of this message to the logical channel indicated by the identifier or unique information obtained by performing a predetermined operation on the identifier among the logical channels. Characteristic resource management device. 8. A management object for a single or a plurality of P subsystems to be managed, which has information provided for the management as a database, and performs operations based on the management procedure on these databases; Storage means in which communication path identifiers indicating communication paths formed individually between these subsystems and the management object are registered in advance in correspondence with the identifiers of the single or plural P subsystems The management object, when a message is given via any of the communication paths, acquires an identifier registered in the storage unit corresponding to a communication path identifier indicating the communication path; A resource management device, wherein the identifier is applied as identification information indicating a subsystem that is a transmission source of the message among the subsystems. . 9. For a single or a plurality of P subsystems to be managed, information for management is provided as a database, and these subsystems are connected via a communication path based on the management procedure. The managed object is configured to deliver a message to the database and perform an operation on the database, and the managed object is configured to transmit a message via the communication path by any one of the single or multiple P subsystems. Is given, the identifier of the sender included in the message is obtained, and the identifier or unique information obtained by performing a predetermined operation on the identifier indicates the subsystem that is the sender of the message. A resource management device characterized by being applied as identification information.