JPH0955735A - Communication network fault diagnostic system and method therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To accurately specify a fault place by automatically analyzing a fault report with which the fault place can not be specified immediately. SOLUTION: This system is provided with a fault report storage part 8A which extracts only fault reports with which fault places can not be specified immediately from fault information among fault reports sent from communication network facilities 9 and stores them for a certain time, and a fault place decision part 8B which decides that a device exceeding its reference value is a faulty device by analyzing fault reports sent from the storage part 8A, one by one, by using the fault report storage part 8A, a suspicious section database 8H, and a facility information database 8J, making to count up an error counter for each device estimated in fault, and comparing addition result by devices presumed to be faulty at the time when addition processes for all fault reports stored in the fault report storage part 8A are completed with reference values by the devices which are controlled by the facility information database 8J and used to determine whether or not a fault occurs.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a communication network failure diagnosing method and a communication network failure diagnosing system for specifying a failure location of a communication network failure, and particularly to a failure in which the failure location cannot be immediately identified from one failure notification. On the other hand, the present invention relates to a failure diagnosis method and a communication network failure diagnosis system for automatically specifying a failure location based on a plurality of failure notifications.

[0002]

2. Description of the Related Art A conventional method for identifying a fault location in a communication network will be described with reference to FIG. In FIG. 7, 1 is communication network equipment, 2 is a line end, 3 is a concentrator I, 4 is a concentrator I
I, 5 are highways (HW), 6 is a communication network facility management operation system, and 7 is a failure notification display terminal.
First, when the line concentrator I3 or the line concentrator II4 detects a line failure, the communication network equipment 1 notifies the communication network equipment management operation system 6 of the failure. At this time, the failure notification includes the failure detection device (in this case, the concentrator I3 or the concentrator II4), the highway (HW) 5 number information, and the line end 2 information as the failure information. Is not uniquely shown.

The failure notification sent from the communication network equipment 1 is output to the failure notification display terminal 7 as it is or after being converted into a format that can be recognized by the operator. The operator recognizes the occurrence of the failure on the display of the failure notification display terminal 7, but the displayed information does not include the information specifying the failure location, and therefore the failure cannot be immediately repaired. Therefore, the operator searches for the same type of failure notification and analyzes whether the failure information has commonality. If there is commonality in the failure information, identify the failure location and take appropriate action (detour;
Failure recovery) can be taken. However, if no commonality can be found in the failure information, the failure location cannot be identified and the failure becomes latent.

[0004]

As described above, in the conventional communication network failure location identifying method, the failure location cannot be immediately identified only by the failure notification notified from the communication network equipment 1,
Analytical processing to identify the failure point, specifically, commonality of failure information such as whether a large number of failure information related to a specific device number or a specific highway number is output by collecting failure notifications of the same type. To identify the failure location. This failure location identification work is operator-dependent, and whether or not the failure location identification is possible depends on the operator's skill level and skill level. As a result, there is a risk that the failure cannot be identified and the potential becomes latent. An object of the present invention is to solve the above-mentioned problems and to accurately identify a failure point by automatically analyzing a failure notification that could not immediately identify the failure point with the communication network facility management operation system. A communication network failure diagnosis method and a communication network failure diagnosis system.

[0005]

In order to solve the above-mentioned problems, the communication network equipment management operation system 8 of the present invention specifies the failure location immediately from the failure information in the failure notification notified from the communication network equipment 9. Failure notification storage means (fault notification storage unit 8A) for extracting only failure notifications that cannot be identified for a certain period of time, a failure notification type for identifying a failure notification whose failure location cannot be immediately identified from one failure notification, and the failure notification type Suspicious section database 8H for accumulating information on the apparatus at the end of the suspected section for extracting the suspected apparatus for each case, at least the apparatus information of the communication network equipment, and for determining whether or not there is a failure for each of the apparatus information Using the reference value and the equipment information database 8J for accumulating the information of the upper device connected to the device, the failure notification notified from the failure notification storage unit 8A is reported. It is characterized by having a failure point decision means for identifying the defective unit by one by one analysis (failure position determination section 8B) a.

More specifically, with respect to a plurality of failure notifications from the communication network equipment 9, the suspected section database 8H is searched by using the failure notification type representing the failure content for each failure notification as a key, and the plurality of failure notifications are reported. A failure notification whose failure location cannot be specified is immediately searched from one failure notification, and the suspected section database 8H is searched for the searched failure notification using the failure notification type as a key to obtain section information of a device estimated to be a failure. The suspicious section searching unit 8G to be obtained, the equipment information searching unit that searches the facility information database 8J by using the section information obtained by the suspicious section searching unit as a key, and obtains a device estimated to be a failure, are provided for each device. Error counter, error counter adding means 8K for adding 1 to the error counter for each device that is estimated to be in failure, and It has a reference value comparison means 8L for comparing the addition result of the error counter with the reference value at the time when the processing for the failure notification is completed, and for identifying a device whose addition result of the error counter exceeds the reference value as a failed device. It is characterized by that.

Further, the communication network failure diagnosis method of the present invention creates the suspected section database 8H and the equipment information database 8J as described above, and gives the failure contents for each failure notification for a plurality of failure notifications from the communication network equipment. Based on the indicated fault notification type, the suspected section database is referred to, and a failure notification whose failure location cannot be immediately identified from one failure notification and section information of the device estimated to be a failure are obtained, and based on the obtained section information. When a device estimated to be a failure is obtained by referring to the facility information database, the number of each device estimated to be the determined failure is counted, and when the count result exceeds the reference value accumulated in the facility information database, The device is determined to be out of order.

[0008]

BEST MODE FOR CARRYING OUT THE INVENTION In the present invention, the failure notification accumulating means 8A searches the suspected section database 8H for the failure notification notified from the communication network equipment 1 using the failure notification type as a key, and immediately detects the failure from the failure information. It is determined whether or not the failure notification cannot specify the location, and only failure notifications in which the failure location cannot be specified are immediately accumulated from the failure information. Thus, the failure notification required by the failure point determination means 8B can be automatically accumulated for a certain time.

On the other hand, the failure point determination means 8B searches the suspected section database 8H using the failure notification type as a key,
Obtain the section information (suspected section) of the device estimated to be defective,
The facility information database 8J is searched by using the obtained section information as a key, a device estimated to be in failure is obtained, an error counter is added to each obtained device, and at the time when the processing for all failure notifications is completed, The result of addition of the error counter of the device is compared with a predetermined reference value that is registered in the facility information database to determine whether or not the device has a failure, and the result of addition of the error counter exceeds the reference value. Then, the device is specified as a failed device. Then, the identified failure device (failure point) is repaired. As mentioned above,
According to the present invention, the communication network equipment management operation system can automatically analyze the failure notification in which the failure location cannot be specified immediately and identify the failure location, and as a result,
It becomes possible to repair the failure at the identified failure location, and the potential for the failure, which has been a problem in the past, can be eliminated.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a diagram showing an outline of a communication network failure diagnosis system according to the present invention. As shown in the figure, the communication network equipment management operation system 8 of the present invention is a communication network equipment 9
The failure notification storage unit 8A that extracts only the failure notification whose failure location cannot be specified immediately from the failure information among the failure notifications notified from and stores the failure notification for a certain period of time, and the failure notification notified from the failure notification storage unit 8A. Each device is analyzed one by one, and an error counter is added for each device that is estimated to be in failure, and each device that is inferred to be in failure when the addition process for all the error notifications accumulated in the error notification accumulating unit 8A is completed. Of the error counter addition result and the reference value for determining whether or not each device has a failure, and a failure point determination unit 8B that determines that the device whose error counter addition result exceeds the reference value is a failed device. To be done.

Next, the internal configuration of the communication network equipment management operation system 8 for implementing the present invention will be described in detail.
FIG. 2 is a detailed block diagram of an embodiment of the communication network facility management operation system 8. As shown in the figure, the communication network facility management operation system 8 of this embodiment includes a failure notification receiving unit 8C, a failure notification storage unit 8A, a failure location determination unit 8B, a failure location determination activation unit 8F, a suspected section database 8H, It is composed of a facility information database 8J and a failure notification unit 8M.

The failure notification receiving unit 8C has a function of receiving a failure notification from the communication network equipment 9 and handing it over to the failure notification storage unit 8A. The failure notification accumulating unit 8A has a function of extracting only failure notifications from which a failure location cannot be immediately identified from a plurality of failure notifications inherited from the failure notification receiving section 8C, accumulating the failure notifications for a certain period of time, and then passing the failure notifications to the failure location determination unit 8B. have. The failure point determination unit 8B automatically analyzes the failure notification which cannot be immediately identified from the failure notification storage unit 8A and determines the failure point, and the failure notification unit 8B.
It has the function of handing over to M. Failure point determination activation unit 8
F transfers the failure notification held in the failure notification storage unit 8A (specifically, a failure notification holding unit 8E described later) to the failure position determination unit 8B in order to cause the failure position determination unit 8B to determine the failure position. This is for giving a signal (a failure location determination start signal) that triggers the failure notification to the failure notification accumulating unit 8A (specifically, a failure notification holding unit 8E described later).

The suspicious section database 8H stores a set of a failure notification type and information about a device at the end of the aggregation device that is estimated to be in failure. Specifically, among the failure notifications notified from the communication network equipment, the failure notification type for identifying the failure notification whose failure location cannot be immediately identified from one failure notification is accumulated, and the accumulated failure notifications are also accumulated. Information (apparatus type) of the apparatus at the end of the suspected section for extracting the suspected apparatus for each type is accumulated (see FIG. 5).

Further, the facility information database 8J stores, as a set, device information including a device type and a device number, a reference value for each device for determining whether or not there is a failure, and connected upper device information. ing. In addition to the device type and the device number, the connected higher-level device information is at a certain time when the device has a redundant redundant configuration of 0 system (for example, operating system) and 1 system (for example, standby system). The system number change time and the system number (whether system 0 or system 1) are stored so that it can be determined whether the device is system 0 or system 1 (see FIG. 6).

The failure notification section 8M is the failure location determination section 8
This is for notifying the failure location determined in B to the failure notification display terminal 7 together with the failure notification.

The fault location accumulating unit 8A is further composed of a fault notification searching unit 8D and a fault notification holding unit 8E. The failure notification searching unit 8D searches whether or not the failure notification is registered in the suspected section database 8H, using the failure notification type of the information constituting the failure notification inherited from the failure notification receiving unit 8C as a search key. If it is registered, it has a function of determining that it is a failure notification to be stored and handing it over to the failure notification holding unit 8E. The failure notification holding unit 8E holds the failure notification that the failure notification searching unit 8D has determined to be necessary to be stored and has taken over, and is held when the failure location determination activation signal is received from the failure location determination activation unit 8F. It has a function of handing over one failure notification to the failure location determination unit 8B one by one.

The failure point determination section 8B comprises a suspected section search section 8G, an equipment information search section 8I, an error counter addition section 8K, and a reference value comparison section 8L. The suspected section searching unit 8G searches the suspected section database 8H using the failure notification type as a search key for the failure notification inherited from the failure notification holding unit 8E, obtains the suspected section, and finds the suspected section and the failure notification in the equipment information searching section. It has the function of taking over to 8I. The equipment information search unit 8I takes over the failure notification and the suspicious section from the suspicious section search unit 8G, searches the equipment information database 8J using the information of the suspicious section as a key,
It has a function of searching the device information included in the suspected section and handing over the searched device information to the error counter adding unit 8K.

The error counter adding unit 8K has an error counter for each device, and adds 1 to the error counter of the corresponding device for each device information included in the suspected section inherited from the facility information searching unit 8I, It has a function of handing over the addition result to the reference value comparison unit 8L together with the failure notification. The reference value comparison unit 8L has an error counter addition unit 8K for all failure notifications held in the failure notification holding unit 8E.
At the time when the addition process in step 1 is completed, the equipment information database 8J is searched using the equipment information included in the suspected section as a search key to extract the reference value for each piece of equipment information for determining whether or not there is a failure, and the extracted reference value And the addition result of the error counter for each device are compared, and the device of the device information for which the addition result of the error counter exceeds the reference value is determined as a failure point, and the determined failure point information is notified together with the failure notification in the failure notification unit. It has the function of taking over to 8M.

Next, a specific embodiment of the communication network failure diagnosis system of the present invention will be described by taking as an example the case where a failure occurs in the communication network equipment 9 having the connection configuration shown in FIG. In FIG. 3, the communication network equipment 9 has a line end i (i =
0 to 127) and the line concentrator Ijk (j = 0 to 0) that takes a redundant redundant configuration with host devices at the line ends i (i = 0 to 127)
7, k = 0 or 1) and a concentrator IImn (m = 0, n =) that takes a redundant redundant configuration with the host device of the concentrator Ijk.
0 or 1). In the case of adopting the redundant redundancy configuration (k, n = 0 or 1), for example, when k and n are 0, it indicates that it is an active system and when it is 1, it is a standby system.
It is needless to say that the numerical range of i, j, and m shown here is merely an example, and can be arbitrarily changed depending on the configuration of the communication network equipment. Absent.

Each device at the line end i (i = 0 to 127) has a device type (specifically, "line end") and a device number (specifically, "i", that is, "0" to "127". ). Concentrator Ijk (j = 0 to 7, k =
Each device of 0 to 1) has a device type (specifically, “concentrator I”), a device number (specifically “j”, that is, “0” to “7”), and a system number (of a redundant configuration). It is a number for identifying what is operated in the device, and is specifically identified by "k", that is, "0" or "1"). Each device of the concentrator IImn (m = 0, n = 0 or 1) is a device type (specifically, “concentrator I”), a device number (specifically, “m” or “0”) and a system. A number (a number for identifying a device operating in a redundant configuration device, specifically, "n", that is, "0" or "1") is identified. The systems of the concentrators I and II having the redundant redundant configuration switch over time, that is, the system number "k" of the concentrator I and the system number "n" of the concentrator II are "0 (for example, operating system)" with time. It changes between "1 (for example, a backup system)".

In the communication network equipment 9, there is a functional unit (not shown) which detects a failure in the communication network equipment, generates a failure notification, and notifies the communication network equipment management operation system 8 of the failure notification. . The communication network equipment 9 receives the failure information detected by the line end, the concentrator I, and the concentrator II by this function unit, generates a failure notification according to the failure information, and notifies the failure notified from each apparatus. It becomes possible to determine the type of failure notification based on the information and identify the type of failure such as line failure.

The failure notification notified from the communication network equipment 9 to the communication network equipment management operation system 8 includes the failure notification type, the device type of the line end which is one end of the suspected section and the device number as the failure information. There is. For example, FIG. 4 shows a specific example of the failure notification in the case of the communication network equipment having the connection configuration shown in FIG. The fault notification shown in FIG. 4 is an example in the case of a line fault in which the suspected section is "line end 127-concentrator I7k-concentrator II0n", and the fault notification type is "00000."
1 ”at the time“ August 1, 1995, 8:00:00 ”
The device number "1" in the device type "line end" detected in "seconds"
It indicates that there is a line failure related to the line end of "27".

Here, a specific configuration example of the suspected section database 8H and the equipment information database 8J in the communication network equipment management operation system for the communication network equipment 9 shown in FIG. 3 will be described. In the suspected section database 8H, for example, as shown in FIG. 5, “000001” is set as the failure notification type for identifying the failure notification whose failure location cannot be immediately identified from one failure notification. “Concentrator II” is registered as the device type of the aggregation device end that is estimated to be in failure, that is, the information of the device that is the end of the suspected section for extracting the suspected device.

Further, in the facility information database 8J, as shown in FIG. 6, for example, the device type of the device information is "line end", the device number is "127", and the reference value for determining whether or not there is a failure is ". 2 ”, the device type as the connected upper device information is“ concentrator I ”, the device number is“ 7 ”, the system number change time is“ August 1, 1995 7:00:00 ”, the system number Is "0", the device type of the device information is "concentrator I", the device number is "7", the reference value is "16", and the device type as the connected upper device information is "Concentrator II", device number "0 (for example, operating system)", system number change time "August 1, 1995, 6:00
Equipment information data having a system number of "0 minutes 00 seconds" and a system number of "1 (for example, a standby system)" is registered. In this example, the concentrator I7 changes from the 1-system to the 0-system on August 1, 1995 at 7:00:00, and the concentrator II0 changes from the 0-system on August 1, 1995 at 6:00:00. It shows that it has changed to 1 system. In the above example, for the sake of simplicity, the suspected section database 8
Although only one set of data in H and two sets of data in the facility information database 8J are shown, it goes without saying that a large number of sets of data are registered as necessary.

Next, with reference to the block diagram of the communication network equipment management operation system 8 of FIG. 2, the processing in the communication network failure diagnosis system of the present invention will be mainly described, and a concrete example of the communication network equipment 9 of FIG. This will be described with reference to a specific example of the suspected section database 8H and a specific example of the facility information database 8J in FIG.

In the communication network equipment 9 (see FIG. 3), the line end,
Based on the failure information detected by the concentrator I, the concentrator II, etc., a failure notification (see FIG. 4) is generated and transmitted to the communication network facility management operation system 8. In the communication network equipment management operation system 8, the failure notification receiving unit 8C receives the failure notification transmitted from the communication network equipment 9. As shown in a specific example in FIG. 4, the failure notification includes the failure notification type, the failure detection time, and the failure information including the device type and the device number of the line end that is one end of the suspected section. The failure notification reception unit 8C takes over the received failure notification to the failure notification search unit 8D in the failure notification storage unit 8A.

The failure notification search unit 8D uses the failure notification type as a search key to search the suspected section database 8H in order to determine whether the failure notification taken over from the failure notification receiving unit 8C cannot immediately identify the failure location. Search for. As a result of the search, if the failure notification type serving as the search key has already been registered, it is determined that the failure location cannot be immediately identified, and the failure notification is handed over to the failure notification holding unit 8E. Here, the reason why it is determined that the failure location cannot be immediately identified when the search result is registered is the failure notification (failure notification of the failure notification that cannot immediately identify the failure location among the failure notifications notified from the communication network equipment. This is because only the (type) is registered in the suspected section database in advance, and thus the registered failure notification type is considered to be the type of failure notification in which the failure location cannot be immediately identified. For example, in the failure notification shown in FIG. 4, since the failure notification type “000001” is already registered in the suspected section database 8H shown in FIG. 5,
It is determined that the failure location cannot be immediately identified, and the failure notification holding unit 8E holds the failure location.

In the failure notification holding unit 8E, the failure notification is inherited from the failure notification retrieval unit 8D, and the failure location determination activation unit 8 receives the failure notification.
Hold until activated by F. When the failure location determination activation unit 8F activates failure location determination in the failure notification storage unit 8E, the failure notification storage unit 8E takes over the retained failure notifications one by one to the suspected section search unit 8G.

The suspected section search unit 8G searches the suspected section database 8H for each failure notification inherited from the failure notification holding unit 8E by using the failure notification type as a search key, and the aggregation device end (here, estimated to be a failure) The aggregator end is a device facing the line end among the two devices forming the suspected section, and specifically, the concentrator I or the concentrator I.
(Pointing to I) is obtained. In the case of the suspected section database 8H shown in FIG. 5, the device type at the end of the aggregation device is “concentrator II”.

The suspicious section based on the information of the line end (device type "line end" and device number "127") included in the failure notification and the device type (concentrator II) of the aggregation device end obtained from the suspicious section database 8H. Is selected. In our example,
As shown in FIG. 3, "line end 127-concentrator I-
Concentrator II ”is selected as the suspicious section. Information on the suspected section selected by the suspected section search unit 8G and a failure notification (see FIG. 4).
(Refer to) and are taken over by the equipment information search unit 8I.

In the equipment information searching unit 8I, the line end information (device type "line end" and device number "127") of the suspected section information taken over from the suspected section searching unit 8G is included in the failure notification. Failure detection time "August 1, 1995 8
The equipment information database 8J is searched by using "hour 00:00" as a search key, and information of the upper device to which the line end included in the failure notification is connected is obtained. In the case of the facility information database 8J shown in FIG. 6, the device type is “concentrator I”, the device number “7”, and the system number change time “August 1, 1995, 7:00 00” Seconds and system numbers "0" are required.

If the device type of the upper device information obtained by the equipment information searching unit 8I matches the device type of the aggregation device end of the suspected section inherited from the suspected section searching unit 8G, the device information included in the suspected section The search has been completed. If they do not match, all the device information included in the suspected section can be searched by repeating the same operation using the higher-level device information of the search result as a search key. In this case, the device type of the higher-level device information obtained by the facility information searching unit 8I is "concentrator I", whereas the device type of the aggregation device end of the suspected section inherited from the suspected section searching unit 8G. Is the "concentrator II" and the two do not match. Therefore, the facility information database 8J is further searched using the device type "concentrator I" of the higher-level device information obtained by the facility information searching unit 8I as a search key.

In the example of FIG. 6, since the upper device information of the search result is the device type “concentrator I” and the device number “7”,
When the facility information database 8J is searched again by using this as a search key, the device type “concentrator II”, device number “0”, and system number change time “August 1, 1995, 6 o'clock” as the information of the connected upper device. "00 minutes 00 seconds" and system number "1" are required. This is the suspicious section search unit 8G
Since it matches the device type “concentrator II” at the aggregation device end of the suspected section inherited from, the search by the facility information search unit 8I ends. When the search by the equipment information search unit 8I is completed, the device information included in the suspected section obtained by the search and the failure notification are taken over by the error counter addition unit 8K.

Here, when the failure detection time in the failure notification is temporally before the system change time of the "connected upper-level device information" in the equipment information database 8J, at the time of failure detection, the level of the higher-level device still remains. Since the system number has not changed to the system number shown in the facility information database 8J, the reverse system number is adopted.

The error counter adding section 8K is provided with an error counter corresponding to the apparatus, and the equipment information searching section 8I is provided.
1 is added to the error counter corresponding to the device included in the suspected section inherited from. After adding 1 to all the devices included in the suspected interval, the device information included in the suspected interval that has been inherited, the failure notification, and the error counter value for each device are inherited to the reference value comparison unit 8L.

In the reference value comparison unit 8L, the failure notification holding unit 8
For all the failure notifications held by E, the suspected section search unit 8G, the equipment information search unit 8I, and the error counter addition unit 8
It is determined whether the process in K is completed, and if not completed, the same process as described above is repeated for the remaining failure notification.

Suspicious section search unit 8 for all failure notifications
When the processing of G, the equipment information search unit 8I, and the error counter addition unit 8K is completed, the equipment information database 8J is searched using the equipment information as a search key for all the equipment included in the taken over suspected section. , A reference value for each device for determining whether or not a failure has occurred. The reference value for each device registered in the facility information database 8J is determined in advance based on the number of calls added to each device and the fluctuation rate of the number of calls added.

The reference value obtained for the device included in the suspected section is compared with the error counter value taken over from the error counter adding unit 8K, and the device having the error counter value exceeding the reference value is identified as the failure point. Then, the failure notification unit 8M takes over together with the failure notification. In the example of the equipment information database 8J shown in FIG. 6, when the number of failure notifications including the line end 127 as a suspected section exceeds 2, the line end 127 is identified as a failure and a failure including the concentrator I7 as a suspected section. Concentrator I7 when the number of notifications exceeds 16.
Means to be identified as a failure.

The failure notification section 8M notifies the failure notification display terminal 7 of the failure location identified as the failure notification taken over from the reference value comparison section 8L. The failure notification display terminal 7 displays the failure notification notified from the failure notification unit 8M and the failure location identified. The operator refers to the identified failure location and the failure notification on the display of the failure notification display terminal 7 to perform necessary measures, such as repair of the failure location.

As described above, in the prior art, even if the failure notification is such that the failure location cannot be specified immediately, the failure location can be automatically specified by using the communication network failure diagnosis system of the present invention. By notifying the operator of the specified failure point and performing a repair or the like, the potential of the failure point can be eliminated. Since it is common to duplicate the upper device in a communication network, the above embodiment has described an example of a device that is double redundant as the upper device (concentrator). It is obvious that the device does not have to be a device to be used, and in that case, it is not necessary to provide a system number change time or system number column in the facility information database.

[0041]

As described above, according to the present invention,
It is now possible to automatically analyze communication network failures that may be difficult to identify immediately and may become latent, and as a result, the failure location can be identified by repairing the identified failure location. It can be prevented from becoming latent.

[Brief description of drawings]

FIG. 1 is a schematic diagram of a communication network equipment management operation system, a communication network equipment, and a failure notification display terminal to which the present invention is applied.

FIG. 2 is a block diagram showing an embodiment of a communication network equipment management operation system to which the present invention is applied.

FIG. 3 is a diagram including a specific configuration of communication network equipment for explaining the operation of the present invention.

FIG. 4 is a specific example of a failure notification according to the embodiment of the present invention.

FIG. 5 is a specific example of a suspected section database 8H in the embodiment of the present invention.

FIG. 6 is a specific example of the facility information database 8J in the embodiment of the present invention.

FIG. 7 is a schematic diagram of a conventional communication network equipment, a communication network equipment management operation system, and a failure notification display terminal.

[Explanation of symbols]

1: Communication network equipment in conventional example, 2: Line end, 3: Concentrator I, 4: Concentrator II, 5: Highway (HW), 6: Communication network facility management operation system in conventional example, 7: Failure notification display Terminal, 8: communication network equipment management operation system to which the present invention is applied, 8A: failure notification accumulation unit, 8B: failure location determination unit, 8C: failure notification reception unit, 8D: failure notification search unit, 8E: failure notification retention Part, 8F: failure point determination start part, 8G: suspected section search part, 8H: suspected section database, 8I: equipment information search part, 8J: equipment information database, 8K: error counter addition part, 8L: reference value comparison part, 8M: failure notification unit, 9: communication network equipment in the embodiment of the present invention

Claims (3)

[Claims] 1. A communication network failure diagnosis system in a communication network equipment management operation system for managing communication network equipment, wherein a failure notification type for identifying a failure notification whose failure location cannot be immediately identified from one failure notification and the failure. A suspicious section database for accumulating information on the device at the end of the suspicious section for extracting the suspected device for each notification type, at least the device information of the communication network equipment, and for determining whether or not there is a failure for each device information The equipment information database for accumulating the reference value and the higher-level equipment information connected to the equipment, and a plurality of failure notifications from the communication network equipment, using the failure notification type indicating the failure content for each failure notification as a key. The section database is searched, and from one of the plurality of failure notifications, a failure notification whose failure location cannot be immediately identified from one failure notification is searched, and the search is performed. With respect to the generated failure notification, the suspected section database is searched by using the failure notification type as a key, and section information of the apparatus estimated to be in failure is obtained, and the section information obtained by the suspected section searching unit is used as a key. A facility information search unit that searches the facility information database to find a device that is estimated to have a failure, an error counter that is provided for each device, and an error counter that increments the error counter by 1 for each device that is estimated to have a failure A criterion for comparing the addition result of the error counter with the reference value at the time when the processing for all the failure notifications is completed, and for identifying the device in which the addition result of the error counter exceeds the reference value as the failed device. A communication network fault diagnosis system having a value comparison means. 2. The communication network facility has a double redundant configuration, and the upper device information accumulated in the facility information database includes information for identifying the device, connection state change time and connection state. The communication network fault diagnosis system according to claim 1, further comprising connection state history information including the changed connection state. 3. A failure notification type for identifying a failure notification whose failure location cannot be immediately identified from one failure notification and a failure notification method in a communication network failure diagnosis method in a communication network equipment management operation system for managing communication network equipment. A suspicious section database for accumulating information on the device at the end of the suspicious section for extracting the suspected device for each notification type, at least the device information of the communication network equipment, and for determining whether or not there is a failure for each device information Create a facility information database that stores the reference value of and the information of the upper device connected to the device,
With respect to a plurality of failure notifications from communication network equipment, a failure notification and a failure cannot be immediately identified from one failure notification by referring to the suspected section database based on a failure notification type indicating failure content for each failure notification. Then, the section information of the apparatus estimated to be obtained is obtained, the apparatus estimated to be a failure is obtained by referring to the facility information database based on the obtained section information, and the number of each apparatus estimated to be the obtained failure is counted. A communication network failure diagnosis method, wherein when the counting result exceeds a reference value stored in the facility information database, the device is determined to be a failure.