JPH11340979A - Repeater and fault notice method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent congestion by suppressing notices of plural faults caused in relation to a single fault. SOLUTION: The repeater consists of an exchange 1, a management device 2, high order devices to be managed 3-1-3-n, and low order devices to be managed 4-1-4-m, and each device has a fault occurrence state management table 50, a fault suppression information management table 60 and a related fault information management table 70. The fault information managed by the fault suppression information management table 60 are respectively related to those in the related fault information management table 70 storing related fault information. In the case of receiving fault information from low order devices or a fault is detected, the fault information are compared by using the related fault information management table 70 and the fault occurrence state management table 50 and the notices are suppressed when the related faults occur at the same time to prevent congestion.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an exchange, a network system, and a failure notification method for preventing congestion due to notification of failure information when failure information is notified from a large number of managed devices to a management device.

[0002]

2. Description of the Related Art In order to prevent congestion due to fault notification, it is useful to reduce the number of fault information to be notified.

[0003] As a method of reducing the number of fault information, faults occurring in a device are counted and whether a specified value is reached or not.
There is a system in which failures are collectively notified when a specified time has elapsed since the failure occurred (Japanese Patent Laid-Open No. 3-195).
No. 142).

As another method, there is a method of changing the detection sensitivity in accordance with the state of occurrence of a failure with respect to notification of line failure information as one type of failure (Japanese Patent Laid-Open No. 5-34).
No. 4119).

Further, in order to easily estimate the location of the failure, the management device confirms that the received failure information is not caused by the same cause as the previously processed failure. A method that does not perform processing has been proposed (Japanese Patent Application Laid-Open No. 8-79375).

Further, there has been proposed a method of transmitting a part of the generated fault information to another device and determining whether it is necessary to notify the monitoring device (Japanese Patent Laid-Open No. 3-123133).

[0007]

The problems of the above-mentioned system are as follows.

In the method of notifying congestion information together to prevent congestion, even if a single fault occurs, the notification is suppressed within a specified time, so that a notification delay occurs.

On the other hand, a method for changing the detection sensitivity of a fault is as follows.
Since only one type of fault notification, that is, a line fault, is to be suppressed, when a different type of fault occurs, the notification cannot be suppressed.

[0010] Further, in the above-mentioned conventional technology, it is not possible to suppress fault information that has occurred simultaneously in a plurality of devices accommodated by an upper managed device such as one concentrator or a private branch exchange.

[0011] Further, when there are obvious failures that occur due to the operation status of the managed device, these cannot be suppressed.

Further, in the method for estimating the location where a failure has occurred, the cause is determined in the management device, and congestion cannot be prevented.

In the method of determining whether it is necessary to notify fault information to the monitoring device in another device, only the fault information that is occurring is compared, so that an instantaneous alarm that occurs and recovers instantaneously is suppressed. Can not do.

An object of the present invention is to provide an exchange, a failure notification system, and a failure notification method that can suppress notification of failure information and instantaneous failure information that occur in a plurality of managed devices due to the same cause.

It is another object of the present invention to provide an exchange, a failure notification system, and a failure notification method that can suppress notification of failure information that is apparently caused by an operation situation.

It is still another object of the present invention to provide an exchange and a failure notification method that can detect a managed device in which an abnormality has occurred not only by a management device but also by a higher-level managed device using failure information generated in association with the switching device. .

[0017]

A management device is a higher-level managed device such as an exchange managed by the management device (hereinafter, referred to as an exchange, but is not limited to this. For example, a single device accommodates a plurality of devices and performs a relay function with the management device.) (Hereinafter, referred to as a wireless base station, but is not limited to this. A lower device accommodated in a higher device in a hierarchically constructed network, such as a subscriber terminal device in optical communication, may be used. Included in the exchange), it is possible to set the suppression information in the exchange. The suppression information includes failure information to be suppressed, failure information to be a suppression condition, and a time for suppressing the notification.

When a fault is detected or when fault information is notified from the radio base station, the exchange determines whether or not the suppression condition is satisfied. If the condition is satisfied, notification of the fault is suppressed.

In the above means, by combining the restart report and the failure information, it is possible to suppress failure information that is likely to occur depending on the operation status, such as when the optional device is not connected.

If an abnormality occurs in the means for notifying a failure, an allowable error time and a detection flag are set in addition to the above information. When notifying the failure information, the exchange checks whether the detected abnormality is set as a suppression condition, and if so, checks whether a detection flag is set. When these conditions are satisfied, the allowable error time is measured using a timer, and it is confirmed whether or not a fault associated within the time occurs. If the associated fault does not occur, the fault of the fault notifying means is notified to the management device.

[0021]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a system diagram of a communication network provided with a failure notification suppressing function according to the present invention. A public switching device 1, a management device 2 connected to the public switching device 1, and a higher-level device connected to the public switching device 1. Managed devices 3-1 to higher-level managed devices 3-n (hereinafter simply referred to as exchanges, but are not limited thereto, and one device accommodates a plurality of devices, such as a line concentrator in a network for concentrating lines. Devices that perform a relay function with the management device are included in this, and the lower managed device 4-1 to the lower managed device 4-m (hereinafter, simply referred to as a wireless base station, but are not limited thereto). However, the lower device included in the higher device in the hierarchically constructed network is included, such as the subscriber terminating device in optical communication, etc. When the network hierarchy is 4 or more, the lower device is included. Furthermore the managed device in the lower layer of the managed device is provided, when viewed from the managed device, and a lower the managed device may be configured to operate as a host managed device). In addition, the term “managed device” simply refers to a device that is managed by the management device, including both an upper managed device such as an exchange and a lower managed device such as a wireless base station.

The management device 2 is connected to the public switching device 1 by a line 10, and the exchanges 3-1 to 3-n are connected to the public exchange 1 by lines 11-1 to 11-n, respectively.
Connected to and housed. The radio base stations 4-1 to 4-m
Line 12-1 to line 12-m are connected to and accommodated in exchange 3-1.

Each managed device such as an exchange and a radio base station has a failure occurrence status management table 50-3-1 to 50-3-n, 50-4-1 to 50-5 for managing a failure occurrence status.
0-4-m and a failure suppression information management table 60-3-1 that manages failure information in which suppression conditions for each failure are set.
60-3-n, 60-4-1 to 60-4-m, related fault information management tables 70-3-1 to 70-3 for managing fault information serving as a suppression condition associated with one type of fault
−n, 70-4-1 to 70-4-m.

In each table for managing information related to suppression, a plurality of pieces of failure information may be set as conditions for suppressing notification of certain failure information. 2 of the information management table and the related failure management table serving as the notification suppression condition
Divided into two parts. Therefore, each managed device has one failure information management table and a plurality of related failure information management tables. That is, the failure information management table grasps the failure to be suppressed, and the related failure information management table grasps in detail the condition for each failure managed in the failure information management table.

FIG. 2 is a diagram showing a hardware configuration of the managed device. Each managed device is a higher-level device I / F unit 1 that communicates with a higher-level device of a hierarchically configured network.
20, a lower-level device I / F unit 12 for communicating with a lower-level device
1, a CPU 122 for controlling the apparatus, a memory unit 123 for storing programs and the like, and a memory unit 124 for storing data such as a failure occurrence status management table, a failure suppression information management table, and a related failure information management table shown in FIG. Be composed.

When the restart notification is used as a suppression condition, it is stored in the memory unit 123 or 124.

FIG. 3 is a diagram showing an example of the fault occurrence status management table 50-3-1 of the exchange 3-1.

Fault occurrence status management table 50-3-1
Are device types 51-3-1-1 to 51-3-1-i + j indicating each wireless base station for i faults detected by the exchange 3-1 and j faults detected by the lower management device; Fault types 52-3-1-1 to 52-3-1 indicating the types of faults
−i + j, state indicating whether or not a failure has occurred 53-3-1-
1-53-3-1-i + j, state change times 54-3-1-1 to 54-3-1-i + j indicating the latest state change times
Manage.

FIG. 4 is a diagram showing an example of the failure suppression information management table 60-3-1 of the exchange 3-1.

Failure suppression information management table 60-3-1
Is a device type 61-3-1-1 indicating a wireless base station in which a fault to be suppressed occurs for k notification-suppressed faults
61-3-1-k, failure types 62-3-1-1 to 62-3-1-k indicating the types of failures to be suppressed, and related failure information management table names 63-3-3 for managing notification suppression conditions 1-
1-63-3-1-k is managed. In this table, by selecting all the radio base stations for the device type, it is possible to easily set the suppression information common to all the radio base stations accommodated in the exchange.

FIG. 5 is a diagram showing an example of the related fault information management table 70-3-1 of the exchange 3-1.

Related fault information management table 70-3-1
Is a device type 7 indicating a radio base station in which a fault occurs, for a fault serving as a deterrence condition associated with one type of fault.
1-3-1-1 to 71-3-1-1, failure type 72-3-1-1 to 72-3-1-1 indicating the type of failure, state 73-3- indicating occurrence of failure 73-3-1 1-1 to 73-3-1-
1. Suppression time 74-3-1- indicating time to suppress notification
1-1 to 74-3-1-l are managed. Also in this table, it is possible to specify all wireless base stations accommodated in the exchange as the device type.

When detecting an abnormality in the fault notifying means, the table includes an allowable error time 75 indicating the time from when the fault is notified to when the fault notifying means is detected.
-3-1-1 to 75-3-1-1, detection flag 76-3-1-1 to indicate whether or not the failure is to be detected as a failure notification unit
76-3-1-l is added.

The configuration of a communication network to which the failure notification suppression function according to the present invention can be applied is specifically described as follows.
The management device 2 is a device that collects fault information of each device configuring a network such as a maintenance device. The exchanges 3-1 to 3-n are connected to a line concentrator in a network that performs line consolidation, or in a private network. Such as private branch exchanges. The wireless base stations 4-1 to 4-m are base stations in mobile communication, subscriber terminal devices in optical communication, and the like.

The configuration of the network to which the present invention can be applied is not limited to the configuration shown in FIG. 1, but the number of managed devices can be three or more or one. is there. In other words, the conditions for applying the present invention are:
The fault information can be associated with each managed device, and the fault information transmitted from the lower device can be confirmed.

Next, a sequence when the present invention is applied will be described with reference to FIG. As an example, a case where the line fault information of the lower-level device is suppressed when the exchange is restarted. In order to perform the suppression, a suppression information setting command 80 having a format as shown in FIG.
Must be set to -1.

The suppression information setting command 80 includes a message type 801 indicating the type of the command, a suppression device type 802 indicating the device in which the fault to be suppressed occurs, a suppression fault type 803 indicating the type of the fault to be suppressed, and a status of the fault to be suppressed. State 804 indicating a device in which a failure as a suppression condition occurs, a condition failure type 806 indicating a failure as a suppression condition, a condition state 807 indicating a failure condition as a suppression condition, and suppression of notification This is configured with a suppression time 808 indicating the time to perform. Further, when detecting an abnormality in the failure notifying unit, an allowable error time 809 indicating a time from when the failure is notified to when the abnormality in the failure notifying unit is detected, and a detection flag 8010 indicating whether to detect an abnormality in the failure notifying unit are set. Will be added.

In the exchange 3-1, the inhibition information setting command 80
Is received, a suppression information setting response 81 is transmitted to the management device 2, and necessary information is recorded in the management table. With this process, the restart of the exchange is associated with the line fault information detected by the lower-level device such as the wireless base station, and recorded as the suppression condition.

Thereafter, a restart 90 is performed in the exchange 3-1.
Is performed, a notification necessity confirmation process 91 is performed, and a failure notification 82 is transmitted and a failure notification response 83 is received. On the other hand, in the wireless base stations 4-1 to 4-m, the line failures 84-1 to 84-m are detected by the restart 90 of the exchange 3-1.
Confirmation processing 91 of the necessity of notification is performed. Thereafter, the failure information is transmitted to the exchange 3-1 by the failure notifications 85-1 to 85-m.
, And failure notification responses 86-1 to 86-m are returned. The exchange 3-1 executes the notification necessity confirmation process 91 again, and when the failure information notified from the radio base station satisfies the suppression condition, the notification to the management device 2 is suppressed.
In this way, although the (n + 1) pieces of fault information should be notified to the management apparatus, it is possible to narrow down to one fault information in the exchange, which is effective in preventing congestion.

The combinations of faults for which such effects can be expected are not limited to the example shown in FIG. 6, but may be a notification of an option device non-connection and a restart notification in a managed device having an optional device, or a line fault between the exchange and the wireless base station. And so on, depending on the configuration of the network and the type of fault to be detected. According to the present invention, a failure that is detected as a failure due to the configuration of a network device in which one exchange accommodates a plurality of wireless base stations can be effectively suppressed, and congestion can be prevented.

Next, the notification necessity confirmation processing performed in the managed device will be described with reference to FIG.

When a fault is detected or fault information is notified from the radio base station (100), the exchange acquires fault type, status, and occurrence time information (101). Next, the type of the wireless base station that has issued the notification, the type of the obtained failure is compared with the device type and the failure type managed in the failure suppression information management table, and it is confirmed whether the type is set as a suppression target ( 102).

If not set, the failure status management table is updated (103), and failure information is transmitted (104).

If set, all the faults contained in the related fault information management table specified by the related fault information management table name in the fault suppression information management table (105), the device type, the fault type, The status is compared with the device type, the fault type, and the status managed in the fault occurrence status management table (106).

If they match, the state change time is compared with the suppression time and the failure occurrence time, and it is confirmed whether notification should be suppressed (107). To suppress, update the failure information (10
If only 3) is performed, and if there is no need to suppress, the fault information is also transmitted.

In this example, a case where only single information is notified as the fault information is described. However, the present invention is not limited to this, and by repeating the same processing, a plurality of fault information can be included in one fault information. The present invention can also be applied to a case where failure information is included.

Finally, a process for detecting an abnormality in the failure notifying means will be described with reference to FIG.

When there is an abnormality in the failure notifying means, the failure is always detected on the receiving side. That is, if the status is normal, a failure notification is issued from all the radio base stations accommodated in the exchange, but not being sent from some of the radio base stations means that the failure notification means has an abnormality.
When detecting an abnormality in the failure notifying means, after transmitting the failure information (110), a search is made as to whether or not the transmitted failure information is associated as a suppression condition using the related failure information management tables (111).

If they are not related, the process is terminated. If they are related, it is confirmed whether a detection flag is set (112).

If set, the timer for abnormality detection is set to the allowable error time and started (113). After the timer times out (114), it is confirmed whether or not all the associated faults have occurred by using the fault occurrence status management table (115). If there is any failure information that has not occurred, it is detected as an abnormality of the failure notification means and notified to the management device (116).

[0052]

According to one embodiment of the present invention, since a failure caused by the same cause is suppressed by the exchange, congestion can be prevented by a failure notification.

Further, since the cause is determined in the exchange including the fault information transmitted from the radio base station, a fault that occurs between the radio base stations can be suppressed.

Further, since the detection sensitivity of the failure is not reduced and the notification timing is not delayed, it is possible to realize the failure notification without occurrence of the notification delay when the failure occurs frequently and during the normal operation.

Further, since the suppression is performed by the combination of the failures, it is possible to suppress the failures that are clearly caused by the operation status of the apparatus.

Further, by detecting that the set combination differs from the generated combination, it is possible to determine the abnormality of the failure notifying means.

[Brief description of the drawings]

FIG. 1 is a diagram showing an example of a network to which the present method can be applied.

FIG. 2 is a block diagram of a managed device.

FIG. 3 is a diagram showing a failure occurrence status management table.

FIG. 4 is a diagram showing a failure suppression information management table.

FIG. 5 is a diagram showing a related fault information management table.

FIG. 6 is a diagram showing an example of a sequence between a management device and a managed device.

FIG. 7 is a diagram showing contents of a suppression information setting command.

FIG. 8 is a flowchart of a failure notification suppression determination flow.

FIG. 9 is a flowchart of failure detection unit abnormality detection.

[Explanation of symbols]

1: Public switching device 2: Management device 3: Switching device 4: Wireless base station 50: Failure occurrence status management table 60: Failure suppression information management table 70: Related failure information management table 80 to 86: Message between management device and managed device 80-1 to 80-10: Element of inhibition information setting instruction message 90: Restart processing 91: Notification necessity confirmation processing 100 to 107: Individual processing in notification necessity confirmation processing 110 to 117: Individual in failure notification means abnormality detection Processing 120 to 124: hardware components in the managed device

Claims (11)

[Claims] 1. A relay device of a hierarchical network, comprising: an upper interface unit for communicating with a management device; a lower interface unit for communicating with a plurality of lower devices; Fault detecting means for detecting a fault, means for managing a plurality of fault information notified from the plurality of lower devices, and associating fault information notified from the plurality of lower devices managed by the management means, When the plurality of pieces of fault information are caused by the same cause,
A relay notification suppression unit for notifying the upper interface unit as one piece of failure information. 2. The relay device according to claim 1, wherein the means for managing the fault information sets fault suppression conditions via the management device. 3. The failure notification suppressing means compares a suppression condition set in the failure management means with failure information notified from the plurality of lower-level devices, and suppresses the failure notification. The relay device according to claim 2, wherein: 4. The failure information managing means includes a first table for managing a type of a failure to be notified, and a second table for managing a suppression condition for each failure. The relay device according to claim 1. 5. When the fault information notified from the lower-level device is not set in the first table, the fault suppression means stores the notified fault information in a third table. Notify the management device, and if set in the first table, compare with the contents of the second table, and if they match, compare the corresponding notified fault occurrence time, and within a certain time 5. The relay device according to claim 4, wherein the relay device suppresses the notification if there is, and notifies the relay device beyond a predetermined time. 6. A failure notification method for a network hierarchically constituted by a management device, a relay device connected to the management device, and a lower device accommodated in the relay device, wherein the relay device includes: Managing a plurality of pieces of fault information notified from a plurality of lower-level devices, associating the pieces of fault information notified from the plurality of managed lower-level devices with each other; Notification method as one piece of failure information. 7. The failure notification method according to claim 6, wherein the management device notifies the relay device and the lower device of failure notification suppression information for suppressing notification in advance. 8. The relay apparatus according to claim 1, wherein the relay apparatus suppresses a failure notification by comparing a suppression condition set in a means for managing the failure with failure information notified from the plurality of lower-level apparatuses. The failure notification method according to claim 7, wherein 9. The failure notification method according to claim 6, wherein the relay device separately manages a failure type to be notified and manages a suppression condition for each failure. 10. The relay device, if the failure information notified from the lower device does not correspond to the failure notification suppression information notified in advance from the management device, notifies the management device of the failure notification suppression information. In this case, if the fault occurrence time is within the time specified by the fault information notified from the lower-level device, this is not notified, and if it is out of time, this is notified. 9. The failure notification method according to claim 8, wherein: 11. A method of notifying a failure of a network hierarchically constituted by a management device, a relay device connected to the management device, and a lower device accommodated in the relay device, the method comprising: The startup report is used as fault information, and a line abnormality fault detected in a lower device is associated with the restart of the relay device, and it is determined that there is a fault in a line with a lower device that has not been notified of the fault. Network failure notification method.