JPH06237250A - Device for determining countermeasure against fault of communication network - Google Patents

Abstract

(57) [Summary] [Purpose] To develop appropriate countermeasures against failures in the communication network at an early stage without imposing a burden on the operator, and improve the reliability and performance of the communication network. [Structure] A failure countermeasure determination device that determines a countermeasure for a failure that has occurred based on the failure information from the network monitoring apparatus that monitors the operating state of the communication network. The most suitable maintenance staff for the measures,
Based on the failure information, the maintenance staff selection section that selects from a plurality of maintenance staff registered in advance compares whether or not the failure that has occurred reaches a predetermined severity, and only for failures that reach this severity, A configuration is provided such as an importance level comparison unit that permits the selection of the maintenance staff by the maintenance staff selection unit, and automatically selects a maintenance company according to the importance of the failure and requests countermeasures.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a communication network fault monitoring and maintenance service technique, and more particularly to a communication network fault countermeasure determining apparatus suitable for efficiently determining an optimum countermeasure against a fault that has occurred. Is.

[0002]

2. Description of the Related Art In the work of operating a computer and a network system, a customer who is a system operator, when a failure occurs on a network (communication network), investigates the failure and details of the failure. Understand the situation, determine the necessity of troubleshooting, select a maintenance company to request troubleshooting, contact the maintenance company, and explain the status of the failure.

Prior art relating to countermeasures against failures in such communication networks is described, for example, in pages 82 to 87 of "Nikkei Communications 1986.1.20" (published by Nikkei BP, 1986). There is something. This technology proposes countermeasures for failures in the relationship between the company that introduced the computer and the maintenance company (maintenance staff) who has a maintenance contract with the company, and when a failure occurs in the computer or network equipment, Failure detection and notification is done automatically. However, the countermeasure work for the failure is performed by the person in charge of operation of the company that introduced the computer. That is, the operation staff investigates the failure, determines the necessity of the failure countermeasure, and requests the maintenance company by telephone for the countermeasure for the restoration. Then, from the status report at that time, the maintenance staff of the maintenance company guesses the cause to some extent, goes to the trouble spot, and performs the trouble recovery work.

If there are maintenance contracts with a plurality of maintenance companies, the operator in charge selects a maintenance company to request a countermeasure for the failure based on the site where the failure has occurred, the device where the failure has occurred, etc. To do. Also, in the event of a failure at night, the operations staff must revise the time and call back during the service hours of the maintenance company. In such a situation, the person in charge of operation must be an expert on the failure, and it takes a lot of man-hours to request the countermeasure, so that it may not be possible to implement the countermeasure early. Even for a maintenance company that requires individual services, it is not possible to efficiently implement prompt measures against the increase in maintenance contract companies and maintenance target devices due to problems such as manpower.

That is, when some kind of failure occurs on the network, it is judged whether the measure against the failure is important or whether it is necessary to request the maintenance company to take a measure, or the countermeasure is taken to the maintenance company. When making a request for the above, there is a problem that it is not possible to efficiently take early countermeasures against the obstacles because human beings must perform the work of explaining the situation of the obstacles using a telephone or FAX. In addition, if a failure occurs outside the service hours of the maintenance company, the necessary measures cannot be taken early.

[0006]

The problem to be solved by the prior art is that in the prior art, in the countermeasure processing for a fault in a communication network, the necessity of the fault countermeasure is judged from the contents of the fault and the fault countermeasure is determined. Selection of the maintenance company to be requested, contact with the maintenance company, and a series of operations such as explaining the status of the failure are performed manually, which is a burden on the operator in charge of failure countermeasures and It is a point that necessary measures against can not be taken early. An object of the present invention is to solve these problems of the prior art, eliminate the need for human intervention in dealing with a fault in a communication network, efficiently perform early countermeasures for the fault, and improve the reliability and performance of the communication network. It is an object of the present invention to provide a failure countermeasure determination device for a communication network that enables the above.

[0007]

In order to achieve the above object, a communication network fault countermeasure determining device according to the present invention comprises: (1) based on fault information from a network monitoring device for monitoring the operating state of the communication network, It is a failure countermeasure decision device that decides the countermeasure against the occurred fault, and based on the fault information from the network monitoring device,
The present invention is characterized in that a maintenance person selecting section is provided for selecting the maintenance person who is most suitable for the countermeasure for the failure that has occurred from a plurality of maintenance persons registered in advance. Further, (2) in the communication network failure countermeasure determining device according to (1), based on the failure information,
It compares whether or not the failure that occurred exceeds the preset degree of importance, and only for failures that exceed this degree of importance, the degree of importance that allows the maintenance section to select the maintenance section. A feature is that a comparison unit is provided. Also,
(3) In the communication network failure countermeasure determining device according to (1) or (2) above, the maintenance person selecting section refers to the respective operating hours of a plurality of pre-registered maintenance persons. In addition, a time information reference unit for narrowing down the candidates for maintenance to be selected is provided. Also,
(4) In the communication network failure countermeasure determining device according to any one of (1) to (3) above, the maintenance person selecting unit refers to a plurality of pre-registered maintenance person's respective locations and selects the person. It is characterized by comprising a location reference unit for narrowing down the candidates for maintenance. (5) In the failure countermeasure determination device for a communication network according to any one of (1) to (4) above, the maintenance person selection unit is configured so that a plurality of pre-registered maintenance person's respective maintainable devices are provided. See the type
It is characterized by comprising a device type reference unit that narrows down the candidates for maintenance to be selected. (6) In the communication network fault countermeasure determining device according to any one of (1) to (5), the maintenance person selecting unit refers to condition information to be referred to when the selected maintenance person is determined to be optimum. Is provided with a selection condition registration unit that registers in advance. Also,
(7) In the communication network failure countermeasure determining device according to any one of (1) to (6) above, the failure information from the network monitoring device and the maintenance selected by the maintenance selection unit corresponding to this failure information The person in charge and the information used to select this maintenance person,
It is characterized in that a log information registration unit that registers in association with each other is provided. (8) In the communication network failure countermeasure determination device according to any one of (1) to (7), the maintenance person selected by the maintenance section selects the occurrence of a failure together with information related to this failure. A feature is that a failure notification unit for notifying is provided. (9) In the communication network failure countermeasure determining device according to any one of (1) to (8), the procedure for selecting a maintenance person to request maintenance by the maintenance person selecting unit is changed based on the degree of importance. It is characterized in that an importance reference section is provided. (10) In the communication network failure countermeasure determination device according to any one of (2) to (9) above,
When the number of occurrences of failure information that is not subject to maintenance is added and registered, and the added number of occurrences reaches a prescribed value,
It is characterized in that an importance addition changing unit is provided for changing the degree of importance of the failure information to the degree of maintenance.

[0008]

In the present invention, when the fault information of the communication network is notified from the network monitoring device, the contents of the fault, the place where the fault occurs, the location of each maintenance person (company) and the operating time (service providing time) Etc. are collated with each other, and the optimum maintenance staff to automatically recover the fault that occurred is automatically selected. As a result, it is possible to reduce the work man-hours required for the side operating the communication network to judge the importance of the failure, check the maintenance company suitable for the failure countermeasure, and check the service provision time. It is possible, and even the person in charge of operations who is not an expert can handle it. Also, since the selection conditions for maintenance personnel can be set and registered according to the content of the failure, it is possible to flexibly deal with an increase in the system scale, etc., and it is easy to improve to a more reliable and quick maintenance system. .

[0009]

Embodiments of the present invention will now be described in detail with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of a configuration relating to the present invention of a network system using a failure countermeasure determining device for a communication network of the present invention. In this figure, 1
Is a network that connects multiple computers, 2
Is a network monitoring device that monitors the operating state of the network 1 and sends out fault information related to a fault that has occurred. 3 is based on the fault information from the network monitoring device 2 and determines the fault countermeasures for the communication network according to the present invention. Failure countermeasure determination device to perform, 4-6
Is a terminal device of each maintenance company.

The fault countermeasure determining device 3 determines, based on the fault information from the network monitoring device 2, whether or not a maintenance service for this fault should be requested to each maintenance company, and an importance degree comparing part 7. For the failure determined by the comparison unit 7 as a failure to be requested to the maintenance company, the maintenance charge selection unit 8 that selects the maintenance company most suitable for the countermeasure against this failure, and the maintenance selected by the maintenance charge selection unit 8 A failure notification unit 9 that notifies the company of a failure recovery request, information referred to by the maintenance selection unit 8 to select the most suitable maintenance company for the failure countermeasure, and failure information referred to by the importance comparison unit 7 Log information registration in which the selection condition registration unit 10 that pre-registers the degree of importance, the failure information from the network monitoring device 2, and the maintenance company name selected by the maintenance selection unit 8 for this failure are associated with each other. Part 11 and importance comparison Notified number of times has been a failure that is not determined to be the obstacle to ask the maintenance company by adding the 7,
When the added importance reaches a predetermined value, the importance addition changing unit 12 that changes the importance of the failure information to the degree of maintenance, and the importance corresponding to the failure information from the network monitoring device 2. On the basis of the degree of, the maintenance section selection section 8 changes the selection procedure of the maintenance company and the importance reference section 13.

In the selection condition registration section 10, a failure data registration table 14 in which failure data that needs to be requested to the maintenance company for countermeasures is registered together with its importance, and the maintenance data of each maintenance company that has a maintenance contract. A maintenance company information registration table 15 in which information such as location and contact information is registered is stored, and the log information registration unit 11 allows the network monitoring device 2 to enable the maintenance company to quickly perform failure recovery work. A failure history information file 16 is stored in which the failure information is registered every time the notification is sent from. In this way, the failure countermeasure determination device 3 registers in advance the selection condition with the information regarding the failure of the system of the network 1 that needs to contact the maintenance company and the information referred to for the selection of the maintenance company requesting the recovery measures of the failure. It is registered in the failure data registration table 14 and the maintenance company information registration table 15 of the department 10.

In such a configuration, when the fault information of the network 1 is notified from the network monitoring device 2, the fault countermeasure determining device 3 registers this fault information in the fault history information file 16 of the log information registration section 11. At the same time, it is passed to the importance comparing section 7. The importance degree comparing unit 7 compares the failure information with the registered content of the failure data registration table 14,
When the importance of the failure information in the failure data registration table 14 exceeds a predetermined value, the failure is detected as a failure requiring countermeasures.

In this way, when the importance level comparing section 7 detects a failure requiring countermeasures, the maintenance charge selecting section 8 refers to the maintenance company information registration table 15 of the selection condition registering section 10 to take countermeasures. Select the most suitable maintenance company to request.
At this time, the maintenance person selecting unit 8 selects an optimum maintenance company according to the instruction from the importance degree reference unit 13 in a procedure corresponding to the degree of importance of the failure. For example, in the case of a fault of high importance, the selection process is performed with the first selection condition being close to the place where the fault has occurred.

Further, when the importance comparing section 7 detects the failure information from the network monitoring device 2 as a failure for which failure countermeasure is unnecessary, the importance addition changing section 12 notifies the failure information of the failure information up to now. Add the number of times it has been done. If the number of times of addition reaches a predetermined value, the importance degree addition change unit 12 changes the degree of importance of the failure information to the degree of maintenance. As a result, when the fault information is notified from the network monitoring device 2 next time, the fault information is detected as requiring a countermeasure request. As described above, even for a failure of low importance, a specialized maintenance company can be requested to take countermeasures depending on the frequency of occurrence, and it is possible to prevent deterioration of system performance.

In this way, when the maintenance person selecting section 8 selects the most suitable maintenance company to request the countermeasures for the failure, the failure countermeasure determining apparatus 3 causes the failure notifying section 9 to select the terminal apparatus 4 of the maintenance company selected. Request ~ 6 to recover from the failure. At this time, the fault information notified from the network monitoring device 2 and the information related to this fault information that occurred previously are notified.

Next, the configuration and operation of the fault countermeasure determining device 3 will be described in detail. FIG. 2 is a block diagram showing a first embodiment of the configuration according to the present invention of the failure countermeasure determining device in FIG. In the present embodiment, the failure information 17 received by the importance comparing unit 7 includes a time 18 indicating the time when the failure is detected, a failure message 19 indicating the details of the failure, a device name 20 indicating the failed device, and a device It is composed of a registration field of a site name 21 indicating a place where the site is installed. Further, the maintenance person selecting unit 8 narrows down the candidates of the maintenance company selected by the maintenance person selecting unit 8 in the operating hours of each maintenance company, respectively.
It is composed of a time information reference unit 22, a location reference unit 23, and a device type reference unit 24, which is performed based on the location and the type of device that can be maintained.

The failure data registration table 14 of the selection condition registration section 10 has a failure message 25 indicating the details of each failure.
In addition, there are registration fields such as an importance level 26 indicating whether or not each failure requires recovery work by a maintenance company, and an occurrence count 27 indicating the addition result of the importance level addition and change unit 12. Also,
The maintenance company information registration table 15 includes a company name 28, a location 29 of each maintenance company, a service device 30 indicating a type of device that can be maintained, a service time 31 indicating an operation time zone of maintenance work, a telephone number, a facsimile number, and the like. It has a registration field such as contact information 32. In this way, the data relating to the failure requiring contact with the maintenance company is stored in the selection condition registration unit 10
The failure data registration table 14 and the maintenance company information registration table 15 are registered in advance. The registration contents of the failure data registration table 14 and the maintenance company information registration table 15 are preset and can be arbitrarily changed through an input device (not shown).

All the fault information 17 sent from the network monitoring device 2 in FIG. 1 is registered in the fault history information file 16 of the log information registration unit 11, but efficient registration and retrieval can be performed. In order to do so, the failure history information file 16 registers a field of a failure name 33 in which the failure is classified and registered for each failure message 19 of the failure information 17, and the occurrence history situation for each failure name. The column of fault history information 34 is provided.

When the network monitoring device 2 in FIG. 1 notifies the fault countermeasure determining device having such a configuration of the fault information 17, the importance comparing unit 7 causes the fault indicated by the fault message 19 column in the fault information 17. Contents and failure message 25 in failure data registration table 14 of selection condition registration unit 10
And the registered contents of importance level 26 are checked, and importance level 2
If 6 exceeds a predetermined value (degree), it is detected as a failure that requires the maintenance company to request troubleshooting. If the failure countermeasure request is detected as an unnecessary failure, the importance addition changing unit 12 adds one to the registration content of the number of occurrences 27 in the failure data registration table 14. As a result of the addition, the registered content of the number of occurrences 27 is a predetermined value, for example,
When it reaches “20”, the importance addition changing unit 12
The registration content of the importance level 26 in the failure data registration table 14, that is, the importance level is changed to the degree that it is necessary to request a failure countermeasure.

Further, when the importance comparing section 7 detects a failure requiring a countermeasure request, the maintenance selecting section 8 requests a countermeasure using the maintenance company information registration table 15 of the selection condition registering section 10. Choose the best maintenance company for That is, the maintenance person selection unit 8 causes the time information reference unit 22 to indicate the time indicated in the column of time 18 of the failure information 17 and the operating time of the maintenance company indicated in the column of service time 31 of the maintenance company information registration table 15. Check with and select a maintenance company that can take immediate action. In addition, the location reference unit 23 collates the location indicated in the column of the site name 21 of the failure information 17 with the location of the maintenance company indicated in the column of the location 29 of the maintenance company information registration table 15, and the failure occurs. Select a maintenance company near your location. Further, by the device type reference unit 24, the model of the device indicated in the column of the device name 20 of the failure information 17 and the type of device that can be dealt with by each maintenance company indicated in the column of the service device 30 of the maintenance company information registration table 15. Select the maintenance company that can handle the failure that occurred by comparing with.

Here, the maintenance selection unit 8 causes the importance reference unit 13 to determine the time information reference unit 22 and the location reference unit 23 based on the importance 26 in the failure data registration table 14 of the selection condition registration unit 10. Also, the priority of processing by the device type reference unit 24 is changed. For example, if the obstacle is of high importance, first, the location reference unit 23
The maintenance company closest to the location where the failure has occurred is sequentially selected, and each time the selection is made, the device type reference unit 24 determines whether or not this maintenance company is compatible, and the time information reference unit 22 performs maintenance. Determine if it is a time when the company can operate.

In this way, when the maintenance person selecting section 8 selects the optimum maintenance company to request the countermeasure for the failure, the failure notifying section 9 requests the terminal device of the selected maintenance company for the recovery work of the failure. To do. At this time, the failure notification unit 9 extracts the failure information corresponding to the failure information 17 notified from the network monitoring device 2 of FIG. 1 from the failure history information file 16 of the log information registration unit 11, and selects the maintenance company of the selected maintenance company. Notify the terminal device. As a result, the maintenance company that receives the request can know the details of the failure accurately and quickly, and can perform efficient failure recovery work.

Next, the processing operation according to the present invention of the fault countermeasure determining device 3 having the configuration shown in FIG. 2 will be described with reference to a flowchart. FIG. 3 is a flow chart showing an embodiment of the processing operation according to the present invention of the failure countermeasure determining device in FIG. First, when fault information is sent from the network monitoring device 2 of FIG. 1 (step 301), this fault information is registered in the fault history information file 16 of the log information registration unit 11 of FIG. 2 (step 302). 2, the importance comparing unit 7 of FIG. 2 refers to the failure data registration table 14 of FIG. 2 to search the importance of the failure indicated by this failure information (step 303), and the failure indicated by this failure information is maintained. It is determined whether or not the failure requires a request for troubleshooting from the company (step 304). For example, even if there is a message indicating a failure in the failure information, the failure has almost no hindrance in business processing, the cause is clear, and the operation is performed without requesting the maintenance company for troubleshooting. It is determined whether the person in charge (user) can handle the failure, or whether the user cannot handle the failure and the failure causes a problem in business processing.

Here, when it is determined that the failure does not require the maintenance company to take a countermeasure request, the failure data registration of FIG. 2 is performed by the importance addition changing unit 12 of FIG. 2 as shown in FIG. 4 described later. The registered contents of the table 14 are changed (step 305), the process returns to step 301 and waits for the next failure information. If the failure requires the maintenance company to make a countermeasure request, as shown in FIG. 5 to be described later, the maintenance person selecting section 8 in FIG. 2 notifies the failure in a procedure corresponding to the importance of the received failure information. An optimum maintenance company is selected to recover the failure that has been caused (step 306). Then, the failure notification unit 9 of FIG. 2 requests the maintenance company thus selected to implement countermeasures for this failure (step 30).
7). At the time of this request, by taking out the history information of this failure from the failure history information file 16 of the log information registration unit 11 of FIG. 2 and contacting it together, the maintenance company side can easily formulate a countermeasure.

FIG. 4 is a flow chart showing an embodiment of the processing operation according to the present invention of the importance addition changing unit in FIG. When the importance comparing unit 7 in FIG. 2 determines that the failure information does not require the maintenance company to request the troubleshooting, the importance addition changing unit 12 in FIG. 2 firstly selects the selection condition registering unit in FIG. The content N of the number of occurrences 27 in the failure data registration table 14 of 10 is incremented by 1 (step 401). Next, based on this addition result, it is determined whether or not the number of occurrences N has reached a predetermined value (step 4
02), if the predetermined value is reached, the importance level 2 in the failure data registration table 14 of the selection condition registration unit 10 of FIG.
6 is changed (step 403). That is, the degree of importance corresponding to the failure information is changed to the degree that the importance comparing unit 7 in FIG. 2 determines that the failure requires a maintenance company to take countermeasures against the failure. By this,
Next time the fault information is received, the maintenance company is requested to take measures.

FIG. 5 is a flow chart showing an embodiment of the processing operation according to the present invention of the maintenance person selecting section in FIG. When the importance level comparison unit 7 in FIG. 2 determines that it is necessary to request the maintenance company to take troubleshooting measures,
The maintenance person selection unit 8 in 1 first refers to the degree of importance by the importance reference unit 13 in FIG. 2 (step 501). Then, according to the procedure based on the degree, the maintenance company that requests the implementation of the countermeasure is selected. For example, if the degree of importance is 90% or more (step 502), urgent restoration work is necessary, and the maintenance company is selected with priority given to the base location.

That is, first, the location reference unit 23 in FIG.
Thus, the column of the location 29 in the maintenance company information registration table 15 of the selection condition registration unit 10 of FIG. 2 is searched, and the maintenance company closest to the location of the failure is selected (step 5).
03). Next, the device type reference unit 24 of FIG. 2 searches the column of the service device 30 in the maintenance company information registration table 15 of FIG. 2 corresponding to the selected maintenance company (step 504), and selects the selected maintenance company. The company determines whether or not it is possible to repair the device in which this failure has occurred (step 505). If the repair work cannot be performed, select the maintenance company next to the location where the failure occurred (step 50).
6) Similarly, it is determined whether or not the repair work of the device in which the failure has occurred is possible.

If a maintenance company capable of repair work is selected in steps 503 to 506, the service in the maintenance company information registration table 15 of the selection condition registration unit 10 of FIG. 2 is selected by the time information reference unit 22 of FIG. The column of time 31 is searched (step 507), and it is determined whether or not the selected maintenance company is in a time period in which service can be provided (step 508). If it is outside the service hours,
Returning to step 506, the next maintenance company that is near the location of the failure and is ready for repair work is selected. If it is during the service providing time, the selected maintenance company is selected as the maintenance company requesting the countermeasure for the failure (step 509).

If the degree of importance is 90% or less in step 502, first, the device type reference unit 24 in FIG.
Then, a maintenance company that can handle this failure is selected (step 510), and then the time information reference unit 22 in FIG. 2 corresponds to the selected maintenance company in the maintenance company information registration table 15 in FIG. The column of service time 31 is searched (step 511), and it is determined whether or not the selected maintenance company is in a service available time zone (step 51).
2). If it is during the service providing time, the selected maintenance company is selected as the maintenance company requesting the countermeasure for the failure (step 509). If it is outside the service provision time and the degree of importance is 60% or more (step 513), the process returns to step 510 and the next maintenance company that can deal with the failure is selected. Also, the degree of importance is 60%
If the following is the case, wait until the service time of the selected maintenance company comes (step 514), then
It is selected as a maintenance company requesting countermeasures against failures (step 509). The maintenance company selected in this way is shown in Figure 1.
The failure notification unit 9 notifies the failure countermeasure request.

As described above with reference to FIGS. 1 to 5, in the failure countermeasure determining apparatus of this embodiment, a rule for making a judgment concerning a countermeasure for a failure is registered in advance so that a failure or the like is detected. When an event occurs, this rule is referenced to automatically determine what kind of processing should be performed for the failure that has occurred. That is, when some kind of failure occurs on the network, according to the failure level (degree of importance) corresponding to the failure information, from the content of the failure information and the information about the failed site and device, Automatically select a maintenance company to request troubleshooting.

As a result, the customer of the network system (system operation person in charge) can reduce the number of man-hours required for judging the importance of the failure and checking the maintenance company suitable for the failure countermeasure and the service providing time. Therefore, it is possible for the person in charge of operations to respond even if the person in charge of operations is not an expert. Further, since the service condition can be set according to the content of the failure, a reliable and prompt service can be requested. Furthermore, it is possible to deal with an increase in the number of customers who make a contract by simply adding the conditions of each table. Further, since the maintenance company is notified of the information regarding the failure when requested, the maintenance company can effectively and surely carry out the maintenance service.

The present invention is not limited to the embodiment described with reference to FIGS. 1 to 5, and various modifications can be made without departing from the scope of the invention. For example, the procedure for selecting a request destination to be changed according to the importance is set to be different from that shown in the flowcharts of FIGS. 3 to 5, the search for service time, the search for a device that can be handled, and the location of failure occurrence. You may perform the search in the order of the location near to.

[0033]

According to the present invention, in the countermeasure processing for a failure in the communication network, the necessity of the failure countermeasure is determined from the content of the failure, the maintenance company requesting the failure countermeasure is selected, and the maintenance company. It is possible to carry out a series of tasks such as contacting the customer and explaining the status of a failure without human intervention, reducing the load on the operator in charge of troubleshooting, and taking appropriate measures against the failure. It can be performed early and the reliability and performance of the communication network can be improved.

[Brief description of drawings]

FIG. 1 is a block diagram showing an embodiment of a configuration according to the present invention of a network system using a failure countermeasure determining device for a communication network of the present invention.

FIG. 2 is a block diagram showing a first embodiment of the configuration of the failure countermeasure determining device in FIG. 1 according to the present invention.

FIG. 3 is a flow chart showing an embodiment of a processing operation according to the present invention of the failure countermeasure determining device in FIG.

FIG. 4 is a flowchart showing an embodiment of a processing operation according to the present invention of the importance addition changing unit in FIG.

5 is a flowchart showing an embodiment of a processing operation according to the present invention of a maintenance person selecting section in FIG.

[Explanation of symbols]

 1 network 2 network monitoring device 3 failure countermeasure determination device 4 to 6 terminal device 7 importance comparison unit 8 maintenance person selection unit 9 failure notification unit 10 selection condition registration unit 11 log information registration unit 12 importance addition change unit 13 importance reference Part 14 Failure data registration table 15 Maintenance company information registration table 16 Failure history information file 17 Failure information 18 Time 19 Failure message 20 Device name 21 Site name 22 Time information reference section 23 Location reference section 24 Equipment type reference section 25 Failure message 26 Important Frequency 27 Number of occurrences 28 Company name 29 Location 30 Service equipment 31 Service hours 32 Contact 33 Fault name 34 Fault history information

─────────────────────────────────────────────────── ─── Continuation of the front page (51) Int.Cl. ⁵ Identification code Internal reference number FI Technical display location H04L 29/14 H04M 3/00 E 8426-5K 3/22 Z 8426-5K H04Q 9/00 311 G 7170-5K 7240-5K H04L 13/00 311 (72) Inventor Tomoko Arakawa 12 890 Kashimada, Sachi-ku, Kawasaki-shi, Kanagawa 12 Hitachi Ltd. Information Systems Division (72) Inventor Masanori Sugaya Kawasaki-shi, Kanagawa 12 890 Kashimada, Ltd. Information Systems Division, Hitachi, Ltd. (72) Inventor Shiro Suzuki 2-6-2 Otemachi, Chiyoda-ku, Tokyo Within Hitachi Information Network, Inc. (72) Koichi Imamura Yokohama, Kanagawa 2-5-15 Kitayuki, Nishi-ku, Japan Computer Research Institute

Claims (10)

[Claims] 1. A fault countermeasure determining device for determining a countermeasure against a fault that has occurred based on fault information from a network monitoring device that monitors the operating state of a communication network. Based on fault information from the network monitoring device, A failure countermeasure determining device for a communication network, comprising: a maintenance staff selecting means for selecting a maintenance staff most suitable for the countermeasure of an occurred failure from a plurality of registered maintenance staff. 2. The communication network fault countermeasure determining device according to claim 1, wherein, based on the fault information, it is determined whether or not the fault that has occurred exceeds a preset degree of importance, Only for disorders that exceed the degree of importance,
A failure countermeasure determining apparatus for a communication network, comprising: importance comparing means for permitting the maintenance person to be selected by the maintenance person selecting means. 3. The communication network fault countermeasure determining device according to claim 1, wherein the maintenance person selecting means is configured to operate each of the plurality of pre-registered maintenance persons. An apparatus for determining a failure countermeasure for a communication network, comprising: time information reference means for narrowing down candidates for maintenance selected by referring to a band. 4. The failure countermeasure determining apparatus for a communication network according to claim 1, wherein the maintenance person selecting means refers to respective locations of the plurality of maintenance persons registered in advance. And a fault countermeasure determining apparatus for a communication network, comprising: a location reference unit for narrowing down the candidates for maintenance to be selected. 5. The failure countermeasure determining apparatus for a communication network according to claim 1, wherein the maintenance person selecting means is a maintainable device of each of the plurality of maintenance persons registered in advance. The communication network failure countermeasure determining apparatus, further comprising: a device type reference unit that narrows down the selected candidates for maintenance by referring to the type. 6. A condition to be referred to by the maintenance person selecting means when determining the selected maintenance person as an optimum one in the communication network fault countermeasure determining device according to any one of claims 1 to 5. A failure countermeasure determination device for a communication network, comprising selection condition registration means for pre-registering information. 7. The fault countermeasure determining device for a communication network according to claim 1, wherein the fault information from the network monitoring device and the maintenance person selecting means corresponding to the fault information are provided. A failure countermeasure determining apparatus for a communication network, comprising: a log information registration unit that registers the selected maintenance personnel and the information used for the selection of the maintenance personnel in association with each other. 8. The communication network failure countermeasure determining device according to claim 1, wherein the maintenance person selected by the maintenance person selecting means indicates the occurrence of the failure together with information about the failure. A fault countermeasure determining device for a communication network, comprising: fault notifying means for notifying. 9. The failure countermeasure determining device for a communication network according to claim 1, further comprising a procedure for selecting a maintenance person who requests the maintenance by the maintenance person selecting means based on the degree of importance. An apparatus for determining a failure countermeasure for a communication network, which is provided with an importance reference means for changing. 10. The communication network fault countermeasure determining device according to claim 2, wherein the number of occurrences of fault information that is not subject to maintenance is added and registered, and the added number of occurrences is predetermined. The communication network failure countermeasure determining device is provided with an importance addition changing means for changing the degree of importance of the failure information to a degree to be maintained when the value becomes.