JP2002032878A - Failure notification system - Google Patents

Abstract

(57) [Summary] [PROBLEMS] To provide a CATV station failure notification system that can promptly contact a manager when a failure occurs. A fault notification system includes a device monitoring unit 202 that monitors the status of broadcasting devices 102a to 102c installed in a CATV center station 100, and interprets a monitoring result of the device monitoring unit 202 to determine what kind of device the device has. Failure detail editing unit 20 that determines whether a failure has occurred based on past examples
6 and a transmission unit 210 that creates a message based on the output of the failure detail editing unit 206 and transmits the message to a mobile phone or the like of the managers 400a and 400b.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a failure notification system, and more particularly to a failure notification system that monitors the status of equipment installed in a CATV (cable television) station and notifies a manager when a failure occurs.

[0002]

2. Description of the Related Art In recent years, as the number of subscribers has increased due to the spread of CATV (cable television), CATV networks have been widespread and the scale of center stations has been increasing. For this reason, the effect of the interruption of the broadcast due to the occurrence of a failure in the broadcast equipment is increasing. On the other hand, in order to quickly recover from a failure, there is a problem that the cost of system maintenance is increased.

[0003] Therefore, in many cases, a sufficient number of managers cannot be secured depending on the center station mainly due to cost reasons.
By transferring the call to the center station where the manager is located, the manager is dispatched to the center station in question, and at that time, the trouble recovery work can be started.

On the other hand, a system for judging the cause of a failure by using a database and notifying the manager of the failure has conventionally been disclosed in Japanese Patent Application Laid-Open No. Hei 11 (1999).
No. 510661 and Japanese Patent Application Laid-Open No. 9-288594. In these techniques, the occurrence of a failure is determined based on conditions registered in advance in a database, and a message is notified to a display, a terminal connected to a network, or the like.

[0005]

However, Japanese Patent Application Laid-Open No. 11-510661 and Japanese Patent Application Laid-Open No. 9-2885 described above.
In the technology disclosed in Japanese Patent Application Publication No. 94-94, information is transmitted to a pager connected using a display, a printer, and a modem. There was a problem that it was not possible to notify the occurrence.

Further, since the manager is not always at a specific place, it is necessary to know the manager who can be contacted and to change the contact according to the trouble. Is impossible, and there is a problem that quick contact with the administrator is insufficient.

Further, even when the number of managers is small, the number of managers can be surely secured.
In addition to notifying the failure information, it is necessary for the administrator to confirm that the information has been received. In some cases it was not possible to send it to the location where it occurred.

Further, in the prior art, since the conditions for determining a failure are based on information registered in advance, there is a problem that interpretation of the failure is limited.

The present invention has been made to solve the above problems, and has as its object to provide a failure notification system capable of promptly notifying a manager of a failure.

Another object of the present invention is to provide a failure notification system that can accurately predict the reason for the occurrence of a failure.

[0011]

According to one aspect of the present invention, there is provided a fault notification system comprising:
A monitoring unit that monitors the status of the equipment installed in the ATV station;
It includes a detection unit that detects that a failure has occurred in the device by interpreting the monitoring result of the monitoring unit, and a notification unit that notifies the administrator by telephone based on the detection result of the detection unit.

[0012] Preferably, the telephone is a mobile telephone. Preferably, the telephone is capable of receiving e-mail.

Preferably, the notification unit includes a creation unit that creates a notification message based on a detection result of the detection unit.

According to another aspect of the present invention, a failure notification system monitors a state of a device installed in a CATV station, and interprets a monitoring result of the monitoring unit to cause a failure in the device. And a allocating unit for allocating a manager to call when a failure has been detected by the detecting unit.

[0015] Preferably, the allocating unit notifies the manager once, and allocates the manager to be called depending on the presence or absence of a response.

According to still another aspect of the present invention, a failure notification system monitors a state of a device installed in a CATV station, and interprets a monitoring result of the monitoring unit to generate a failure in the device. A detection unit that detects that a failure has occurred, a database that records the history of failures that occurred in the past, and when the detection unit detects that a failure has occurred, the database is taken into account to predict the reason for the failure. Prediction means for performing the calculation.

[0017] Preferably, the failure notification system includes a determination unit that determines a manager to call based on a prediction result of the prediction unit.

[0018]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a failure notification system according to one embodiment of the present invention will be described in detail with reference to the drawings.

The CATV center station is not always filled with managers (especially on holidays). In addition, it is desirable to respond to obstacles as quickly as possible due to the nature of broadcast media. Therefore, in the present embodiment, a telephone (particularly a mobile telephone capable of transmitting and receiving by voice and electronic mail) is used as a notification method of the failure notification system.
In addition, an administrator who can quickly rush to the site where the failure occurred can be grasped, and an administrator to be called is assigned, thereby promptly responding to the failure.

Further, once a failure occurs, its influence is widespread, so it is desirable to predict the occurrence of the failure and prevent it before it occurs. For this reason, in the present embodiment, a system is constructed in which it is easy to predict a failure (especially the reason for the failure) by periodically accumulating management information in a database.

FIG. 1 is a block diagram showing a configuration of a fault notification system according to one embodiment of the present invention. Referring to the figure, the failure notification system according to the present embodiment monitors a plurality of broadcast devices 102a to 102c installed in CATV center station 100 and, when a failure occurs, makes a portable telephone via public telephone network 300. Notification is given to the managers 400a and 400b by telephone, telephone, e-mail, or the like.

The fault notification system 200 includes a device monitoring unit 202 that obtains fault information by communicating with each of the broadcasting devices 102a to 102c of the CATV center station 100, and a fault information interpreting unit 204 that interprets the obtained fault information. A failure detail editing unit 206 for analyzing the details of the failure by associating a description of the cause of the failure or a past case based on a signal output from the failure information interpreting unit 204; Message creation unit 208 for creating a failure notification message suitable for the communication device that is performing
A notification message transmitting unit 210 that manages the generated notification message and transmits the message in a method suitable for an appropriate manager; a failure detail database 212 that stores necessary information such as past cases related to the failure; The system includes a notification message database 214 for recording data relating to a message, and a manager database 216 for recording a manager's telephone number, mail address, and other manager information.

The failure information of each of the broadcast devices 102a to 102c acquired by the device monitoring unit 202 is transmitted to the failure information interpretation unit 20.
4 and stored in the failure detail database 212. The failure detail editing unit 206 stores the failure detail database 2
Information is read from 12 as information for determining the cause of the failure.

The details of the failure compiled by the failure detail editing unit 206 are compiled into a plurality of expressions such as voice messages and electronic mails by the notification message creation unit 208. The source expressions of these messages are obtained from the notification message database 214.

Finally, notification message transmitting section 210
, A notification message is sent to the manager extracted from the manager database 216 on a medium as necessary.

In this embodiment, when interpreting the fault information and editing the fault details, the fault details database 212 capable of changing its contents and storing past data is used. It is possible to perform not only the interpretation of the failure as it is in the prior art but the interpretation of the failure as it is in the specification of the device, but also the identification of the cause of the failure and the enumeration of the possibilities, and the system can provide the cause estimating material.

Further, the communication device (mobile phone,
The method of notifying a message can be flexibly changed depending on the type of telephone, mobile terminal, etc., so that necessary information can be promptly and reliably transmitted to an appropriate manager.

Thus, in the present embodiment, CA
When a failure occurs in a broadcasting device at a TV center station, the administrator (administrator) is immediately notified of the failure. As a result, the start time of failure recovery can be shortened, and the recovery time can be reduced.

That is, in the present system, when the fault information interpreting unit 204 determines that a fault or a suspected fault has occurred, the fault detail editing unit 206 adds information presumed to be the cause of the fault to the fault occurrence information. Then, a notification message creation unit 208 creates a voice or text message and sends it to the managers 400a and 400b by telephone, electronic mail, or the like.

The determination of a failure is based on information registered in advance in the failure detail database 212 and on the basis of a case added in response to a subsequent failure or a case added by an administrator's operation. Is performed.
Then, importance is placed on a failure that has a statistically high frequency of occurrence or a case that was not initially determined to be a failure but later developed into a serious failure, and the administrator is notified.

Further, a method of changing a manager to call (a manager to send a message) or a method of notifying (notifying by a mobile phone or notifying by e-mail, etc.) according to the degree of importance of a failure is described. By making the change, quick notification can be made and excessive system operation costs can be reduced.

For example, in the case of giving a voice notification of a fault by telephone, an outline of the fault is first played by voice, and detailed information can be obtained by voice or facsimile by inputting an appropriate number by an administrator. Preferably it is possible. That is, it is desirable to provide a notification having a hierarchical menu structure that allows the administrator to easily retrieve information according to the situation.

Next, C in the device monitoring unit 202 of FIG.
Broadcast equipment 102a to 102c of ATV center station 100
From the information acquisition, the notification message created by the occurrence of the failure is transmitted to the managers 400a and 400b via the public telephone network 300 (this may be a communication line such as the Internet).
The flow of information up to the transmission of the information will be described.

The device monitoring unit 202 communicates with the broadcasting devices 102a to 102c of the CATV center station 100 for obtaining information at regular intervals. Then, the device monitoring unit 202 acquires a status value indicating the status of the broadcast devices 102a to 102c.

Each state value and the details of the state indicated by the state value are classified by the fault information interpretation unit 204 for each device (broadcasting equipment) as shown in FIG. 2, for example. Information necessary for interpreting each of these status values is registered in the failure detail database 212 in advance.

In the example of FIG. 2, in the device A (broadcasting equipment A), for each of the status values 1 to 3, the input signal interruption, the output abnormality, and the synchronous clock abnormality are assigned as the status indicated by the status value. .

Further, the status value 1 of the device B (broadcasting device B)
Input signal disconnection and output abnormality are assigned to each of the two.

The fault information interpreting unit 204 merely replaces the status value with a message (details of status), and the fault detail editing unit 206 organizes the information.

For example, in FIG. 2, it is assumed that an output abnormality (state value 2) occurs in apparatus A and an input signal interruption (state value 1) occurs in apparatus B. In this case, each abnormality can be considered to have occurred individually,
As shown in FIG. 3, when the device A is the device on the upstream side of the information and the device B is the device on the downstream side, the abnormality of the device B is caused by the abnormality of the device A or between the device A and the device B. May have been triggered by the disconnection of the transmission line. Therefore, such an interpretation is used as the reason for the occurrence of the fault,
In addition, if a similar trouble has occurred in the past, the contents of the past trouble and the number of occurrences are added as shown in FIG.

The fault detail editing unit 206 also creates a numerical value called a degree of importance (or a degree of personnel requirement) for determining how important the occurring fault is. When a failure occurs, the manager is always sent to the site where the failure occurred. At that time, the number of managers to be convened and / or the management with what kind of technology (how much skill) The numerical value of importance is used to determine whether to send a person.
Referring to FIG. 4, when the status value of device B is 1, the status indicates an "input signal cutoff" status. The reason for the occurrence is as shown in (1) to (3). It is assumed that two reasons have been recorded in the past history. That is, the reason why the input signal was interrupted in the past is as follows: (1) Output abnormality of the device A (severity 3, the past 5 occurrences) (2) Input port failure (severity 3, the past 2 occurrences) (3) It is recorded that there were three reasons for transmission line disconnection between device A and device B (importance: 5, one occurrence in the past). In this example, the importance of each occurrence reason is a numerical value artificially assigned by the administrator, and the number of past occurrences is a value automatically counted by the system.

As the importance to be notified to the administrator when the status value of the device B is 1, a value obtained by weighting and averaging the importance of the cause of the past failure by the number of occurrences is used.

That is, in the example of FIG. 4, when the status value is 1, the importance to be notified to the administrator is determined based on the following equation.

Importance = Σ (Individual Importance × Number of Occurrences) / Σ (Number of Occurrences) More specifically, the importance and occurrence recorded for each of the occurrence reasons (1) to (3) in FIG. Based on the number of cases, the importance notified to the administrator is (3 × 5 + 3 × 2 + 5 × 1) / (5 + 2 + 1) = 3.2.
5 (= 4). That is, when the state of “input signal cut-off” of the state value 1 occurs, the administrator is notified that the importance is “4”.

In the example of FIG. 4, the importance is evaluated and recorded in five levels for each occurrence reason. However, the invention is not limited to this, and the importance may be expressed by a score of 0 to 100, for example. .

The weighted average value of importance may be reported as it is, may be rounded off, or may be reported by truncating or rounding up decimal places.

For example, a notification may be given to the same number of personnel (administrators) as the numerical value indicated by the degree of importance, and the failure may be recovered. That is, if the importance is “1”, it is considered that no serious failure has occurred,
A call may be made to only one manager, and if the importance is "5", it is considered that a serious failure has occurred, and five managers may be called.

The detailed information of the edited fault is converted into a notification message in the notification message creation unit 208. The notification message is created as a voice message when the communication device owned by the administrator sending the message is a telephone, and is created as a text message when the communication device is an electronic mail. When communication of both (voice message and e-mail) is possible, priority is given to voice (for example, a voice message from a mobile phone or the like) with emphasis on urgency.

The created notification message is transmitted to the administrator selected according to the importance of the fault. Here, for example, in the case of "importance 3", three of the managers may be requested to immediately come to the CATV center station by telephone, and the other three may be notified of the situation by e-mail. . Then, the number of persons to be contacted and the contact method may be changed according to the degree of importance, such as making a telephone call to four persons when the degree of importance is four.

To ensure that the notification message is transmitted to the administrator and that the administrator can quickly come to the CATV center station, the response from the administrator is obstructed as shown in FIG. Preferably, the notification system is transmitted. In this case, a two-way communication server may be used for the notification message transmitting unit 210.

Referring to FIG. 5, when notifying a message by telephone, the administrator is notified that "failure OO has occurred. For details, enter the number and press the" ♯ "button. Is transmitted, and when the “♯” button of the administrator's mobile phone is pressed, it is assumed that the administrator has been contacted and the person is managed as a person who can come to the CATV center station. This is effective.

When a message is transmitted by e-mail, a message “A failure has occurred. The cause is probably XX” is transmitted to the administrator to display statistical information. May be provided, and when that part is clicked, it may be determined that contact has been made with the administrator.

After the failure handling is completed, the cause of the failure that has occurred is assigned a degree of importance and registered in the failure detail database 212 to be used as data for dealing with the next failure. In addition, by obtaining statistical information of faults that have occurred during a certain period before and after the occurrence of a fault (for example, one week before and after the fault), the administrator can be provided with information for statistically predicting a fault induced by a certain fault occurrence. The function to be provided may be provided in the failure detail editing unit 206.

As described above, in the present embodiment, the CA which has conventionally started to respond in response to a complaint from a customer.
Regarding the management of TV center stations, quick and accurate failure recovery can be realized by collectively managing the information of broadcast equipment and monitoring the occurrence of failures, and voluntarily notifying the administrator of this including detailed information. There is an advantageous effect.

Also, as a method of determining the importance of a failure based on the information stored in the database to select a manager or as a method of notifying the failure, consideration is given to a response from the manager (receiver) such as reception confirmation, etc. By performing communication, it is possible to provide a system capable of automatically performing more flexible and accurate response.

The fault detail editing unit 206 may derive basic information from the acquired information and transmit it to the administrator as a summary of the fault information.

Further, when notification by telephone is not possible, the system may select or switch transmission means of fault information such as notification by e-mail. Further, periodic log information of the status of the broadcast devices 102a to 102c may be acquired by the device monitoring unit 202 and notified to the administrator by e-mail or the like.

Further, when it is found that a certain manager is absent, the system may consider the destination such as contacting the next candidate manager (alternate manager).

[Modification 1] A list of callers is recorded in the manager database 216 as shown in FIG. 6 in accordance with the importance (personnel requirement) in FIG. 4, and the caller is called in accordance with the importance. May be selected.

That is, in the example shown in FIG. 6, when the number of required personnel is 5, a call is made to A to D by a mobile phone among the managers of A to F, and a mail is sent to E and F. Is called.

When the number of required personnel is 4, A,
A call is made to D and E by a mobile phone, and a call is made to F by mail. Further, when the number of required personnel is 3, a call is made to B, C, and E by a mobile phone.

Also, in the example of FIG.
, A and B or E and F are to be called by a mobile phone. In this method, a call is made to one of the groups, and the other group is called when the call cannot be reached.

When the number of required personnel is 1, D,
Only one manager is called by a mobile phone in the priority order of C, B, E, F, and A.

[Modification 2] Further, the skills of each manager and the materials that can be brought in are recorded in the manager database 216, and for each reason for the trouble (trouble), it is necessary to deal with the trouble. Skills (or necessary materials) may be requested, and an administrator may be called according to the skills or materials.

For example, for each failure, the reason for occurrence is recorded as shown in FIG. 7, and how many persons having specific skills (A) to (C) are required to deal with each reason for occurrence. Keep it. Then, the probability of occurrence is recorded for each reason of occurrence.

In the example of FIG. 7, it is assumed that trouble A (failure A) has occurred eight times in the past,
Twice, once and once.

In order to cope with the occurrence reason 1, 0.5 persons have skills (a) to (c), respectively.
It is assumed that 1.2 and 0.3 people are required.

Similarly, in order to cope with the second reason, the value of 0.
It is assumed that five, 0.5, and 0.2 human resources are required, and one, two, and 1.5 human resources are required to deal with the third cause.

On the other hand, an administrator list shown in FIG. 8 is registered in the administrator database 216. FIG.
In the example, the skills (A) to (A)
(C) is recorded. In addition, the arrival time at the site for each manager (for example, C
The time required to arrive at the ATV center station, etc.), whether the manager is moving (whether it is possible to rush) and whether it is possible to go out are recorded.

In this example, when the trouble A shown in FIG. 7 occurs, the average skill level of the manager who is required is calculated as follows.

For the skill (A), from the weighted average based on the probability, 0.5 × 5/8 + 0.5 × 2/8 + 1 × 1/8 [person] For the skill (A), 1.2 × 5 / 8 + 0.5 x 2/8 + 2 x 1/8 [person] For skill (c), 0.3 x 5/8 + 0.2 x 2/8 + 1.5 x 1/8
It is estimated that [person] personnel are required. Then, one or more optimal human resources are picked up from the manager list shown in FIG. 8 so as to satisfy all skills, and a call is made.

In this call, a random number element may be added. Also, not only skills,
The manager to be called may be selected based on the arrival time at the site, whether or not it is in operation, whether or not it can be dispatched, and the like.

FIG. 9 is a flowchart showing the processing of the failure detail editing unit 206 when calling a manager in consideration of skills.

Referring to FIG. 9, in step S101, the past failure detail database 212 is searched to create a list of reasons for occurrence according to the failure. In step S102, the probability of the failure reason (see FIG. 7) is determined from the number of failure occurrences based on the occurrence reason.

In step S103, skills required for each occurrence reason are obtained. Then, step S10
In 4, the weighting operation is performed by multiplying the probability and the skill. In step S105, the information (personnel request level) regarding the person making the call in the notification message transmitting unit is completed.

FIGS. 10 and 11 are flowcharts showing the processing of the notification message transmitting section for calling the manager in consideration of the skill.

Referring to FIG. 10, in step S201, an administrator list (FIG. 8) is obtained from the administrator database. In step S202, skills for each manager are acquired from the manager list.

In step S203, movable (can rush) personnel are extracted from the manager list.

In step S204, of the movable personnel, the skill and the usual location (or time of arrival at the site)
Create a priority list of administrators to call from Then, in step S205, messages are transmitted by the number of necessary personnel from the highest priority in the created priority list.

In step S206 (FIG. 11), the administrator with the highest priority is selected, and it is determined in step S207 whether a notification has been received from the administrator that the message has been received. If YES, step S208
Deletes the administrator from the list.

It is determined in step S209 whether the number of people is sufficient. If YES, the notification is completed in step S210.

On the other hand, if there is no notification that the message has been received from the administrator in step S207,
In step S211, the priority of the manager is made lowest, and the process returns to step S206.

If NO in step S209, the process returns to step S206. In this way, if a call is made in accordance with the skill of the manager or the like, it is possible to provide a system that can more quickly cope with a failure.

In FIG. 7, the required skills are (A)
The case where there are three cases (a) and (c) has been described. Skills are not limited to the various skills and qualifications that each manager has,
It goes without saying that personal elements such as knowledge and authority may be registered in the manager base 216. Further, the number of items is not limited to three, and more items such as skill (d) and skill (e) can be provided. Further, if the element is a personal element, not only the skill but also a machine, a material, a part, etc. which can be brought by only a specific manager may be registered. Then, for each reason for the occurrence of the failure (trouble), these resources required for dealing with the failure are obtained, and the administrator can be called according to the resources. For example, replacement parts X instead of skills (c), special tools Y instead of skills (d),
If a special tester Z is registered instead of the skill (e), the resources (skill (a), skill (a), replacement part X, special tool Y, special tester Z) possessed by each of these managers It is possible to call the administrator in consideration of the above. Of course, when calling the administrator, it goes without saying that he / she should be told to bring these devices and the like.

[Others] The failure notification system can also be configured as follows.

(1) A failure notification system having communication means with each broadcasting device at a CATV center station and communication means with an external manager by telephone, e-mail, etc., for passively receiving failure information. Alternatively, a failure monitoring function that obtains information through active inquiries and periodically reports it to the management center as log information, and how much serious failures are based on the obtained failure information of each device, mainly A failure determination function that accurately determines whether the failure is caused by a failure, and a failure report medium such as a voice message or an electronic message according to the communication means of the administrator such as a mobile phone or mobile terminal when a failure occurs And configure the media so that the administrator can easily understand the details of the failure without preparing special materials, such as two-way communication and Web links. A failure report notification function that notifies the administrator by setting the number of managers to convene according to the degree of the failure, and the next candidate if there is an administrator who can not reach the telephone or rush to the site Notification destination management function, such as selecting a fault, and classifying the location and type of fault in the past fault reports, linking faults that have occurred individually, and improving the fault determination function thereafter. A failure notification system having a failure information management function to perform.

(2) In the system of (1),
In addition to determining only those that are immediately determined to be faults from the fault information given from the device, referencing past fault information and selecting the fault that is most likely statistically from multiple candidates, A failure notification system that has a failure determination function that predicts a serious failure that can evolve from a minor failure.

(3) In the system of (1) or (2) above, details of faults that have occurred in the past are accumulated, and when determining a fault from fault information of each device, these statistical information and details are referred to. Notification system that has a database for determining the importance of a failure.

(4) In any one of the above-mentioned systems (1) to (3), the communication means that can be selected by the administrator and the notification destination administrator are selected in accordance with the importance of the failure, and the Efficient, such as transmitting fault information via media such as telephone or e-mail, and making the communication line bidirectional so that the administrator can check the details after hearing the summary and confirm that the notification has been received from the sender. A failure notification system that has a notification message creation unit, notification message database, and notification message transmission unit that realizes situation grasp.

(5) In any one of the above-mentioned systems (1) to (4), an administrator to be contacted is selected according to the importance of the fault, and an optimum number of managers and an optimum manager are allocated to the site of the fault. A failure notification system having an administrator database and a notification message transmission unit.

Note that the processing described in the above embodiment may be performed by software or by using a hardware circuit.

Further, a program for executing the processing in the above-described embodiment can be provided, and the program is stored in a CD-ROM, a floppy (registered trademark).
The information may be recorded on a recording medium such as a disk, a hard disk, a ROM, a RAM, and a memory card and provided to the user.

The embodiments disclosed this time are to be considered in all respects as illustrative and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a failure notification system according to one of the embodiments of the present invention.

FIG. 2 is a diagram illustrating a relationship between a state value and a failure state of the apparatus.

FIG. 3 is a diagram for explaining a transmission path between two devices.

FIG. 4 is a diagram showing an example of editing a device failure, its occurrence reason and importance.

FIG. 5 is a diagram for explaining a method of transmitting a notification message.

FIG. 6 is a diagram showing a specific example of a list of callers according to the number of required personnel.

FIG. 7 is a diagram showing a specific example of a table in which the occurrence reason and the skill are recorded in association with each other.

FIG. 8 is a diagram showing a specific example of a list for recording information such as managers and their skills.

FIG. 9 is a flowchart illustrating a process of a failure detail editing unit in a system for dealing with a failure according to a skill.

FIG. 10 is a flowchart illustrating a process of a notification message transmitting unit in a system that handles a failure according to a skill.

FIG. 11 is a flowchart following the flowchart of FIG. 10;

[Explanation of symbols]

100 CATV center station, 102a to 102c broadcasting equipment, 200 failure notification system, 202 equipment monitoring unit, 204 failure information interpretation unit, 206 failure detail editing unit, 208 notification message creation unit, 210 notification message transmission unit, 212 failure detail database, 214
Notification message database, 216 administrator database, 300 public telephone network (or Internet),
400a, 400b Administrator.

 ──────────────────────────────────────────────────続 き Continued on the front page F-term (reference) LL12 MM07

Claims (8)

[Claims] A monitoring unit configured to monitor a state of a device installed in a CATV station; a detection unit configured to interpret a monitoring result of the monitoring unit to detect that a failure has occurred in the device; A notification unit for notifying a manager by telephone based on a detection result of the unit. 2. The fault notification system according to claim 1, wherein said telephone is a mobile phone. 3. The fault notification system according to claim 1, wherein said telephone is capable of receiving an e-mail. 4. The failure notification system according to claim 1, wherein the notification unit includes a creation unit that creates a notification message based on a detection result of the detection unit. 5. A monitoring unit for monitoring a state of a device installed in a CATV station, a detecting unit for interpreting a monitoring result of the monitoring unit to detect that a failure has occurred in the device, And a allocating unit for allocating an administrator to be called when a fault is detected by the unit. 6. The fault notification system according to claim 5, wherein the allocating unit notifies the administrator once and allocates the administrator to be called based on the response. 7. A monitoring unit for monitoring a state of a device installed in a CATV station, a detecting unit for interpreting a result of monitoring by the monitoring unit to detect that a failure has occurred in the device, A failure notification comprising: a database that records the history of the failure that has occurred; and a prediction unit that predicts the reason for the failure by referring to the database when the detection unit detects that the failure has occurred. system. 8. The fault notification system according to claim 7, further comprising a determination unit that determines a manager to call based on a prediction result of the prediction unit.