JP2951151B2 - Fault recovery control system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a failure recovery control system for performing recovery when a failure occurs in a FAX-OCR system used between a branch of a financial institution and a district center, for example.

[0002]

2. Description of the Related Art In a financial institution such as a bank, image data of a transfer request form is transmitted from each branch office to a district center by facsimile, and the district center processes data from each branch office and transfers the data to a host. A processing system, a so-called FAX-OCR system, is employed. And
By adopting such a data processing system, the burden on the branch office is reduced, and the efficiency of business is improved.

FIG. 2 is an explanatory diagram of such a FAX-OCR system. The system shown in FIG.
0, 30, the district center 40, and the communication control device (CC
L) 50, a host 60, and a communication line 70.
The offices 10, 20, and 30 are provided with facsimile (FAX) 11, 21, and 31, respectively. These facsimile machines 11, 21 and 31 are connected to a facsimile reception control section (FC
U: facsimile control unit) 41.

The district center 40 includes a facsimile reception control unit (hereinafter, referred to as FCU) 41, a control unit (MCU: message control unit) 42, and a verification correction unit 43.
Etc. The FCU 41 is for transmitting and receiving facsimile data, and has a disk unit (DK) 44.
And the workstation 45 are connected. The disk device 44 is an external storage device for temporarily storing data and the like transmitted and received by facsimile. The workstation 45 includes a control unit, a display, a keyboard, and the like, and displays and operates data transmitted and received by facsimile.

A control unit (hereinafter referred to as an MCU) 42 includes a recognition device 46, a disk device (DK) 47, and a printer (O
PP) 48 and the verification correction unit 43 are connected, and the FCU 41
For managing various processes in the district center 40, such as receiving data from the local center and instructing the recognition device 46 to perform character recognition processing, and transmitting output data from the verification / correction unit 43 to the host 60. have.

The recognizing device 46 is a character recognizing unit for recognizing characters in each field on a form included in the image data received by the FCU 41 and obtaining code data.
Further, the disk device 47 is an external storage device for temporarily storing data recognized by the character recognition device 46,
The printer 48 is used when it is desired to print out a character recognition result or the like.

The verification / correction unit 43 includes a plurality of workstations 431 to 433. Workstation 43
Reference numerals 1 to 433 each include a personal computer having a display, a keyboard, and the like, each of which is assigned to an operator, collating the above image data with the code data, verifying whether or not the recognition result is correct, and checking errors. If there is, it is a device for making corrections. Further, a facsimile (FAX) 49 is a facsimile provided in the district center 40 and has a communication line 70 or a district center 4.
0-10 PBX (Private Branch Exchange)
For exchanging data with the host 60 and the like.

[0008] The communication control device 50 is a
The host (HOST) 60 is a device that controls transmission and reception from the CU 42.
It is a center that controls 0. The communication line 70 is a network configured by a public line or a dedicated line, and is a network for performing communication connection between the sales offices 10 to 30 and the district center 40 and between the sales offices 10 to 30 and the host 60.

Next, the operation of the FAX-OCR system will be described. Here, a case where the transfer request form is transmitted from the sales office 20 will be described. First, at the sales office 20, the bank employee receives a transfer request written by the customer at the counter (see FIG. 2,
Steps). As a result, the employees can receive the fax 21
Then, the received transfer request is transmitted to the district center 40 via the communication line 70 (step).

[0010] The FCU 41 of the district center 40 is
The form data (compressed image data) transmitted from the facsimile 21 of No. 0 is received and stored in the disk device 44 (step), and the data is stored in the MCU 42.
To send to. The MCU 42 transmits the form data transmitted from the FCU 41 to the recognition device 46, and the recognition device 46 performs character recognition of the form data. Then, the MCU 42 stores the result (character data + image data of the corresponding area) recognized by the recognition device 46 in the disk device 47 (step) and transmits it to the verification / correction unit 43 (step).

In the verification / correction unit 43, for example, the operator operates the workstation 431 to compare and collate the image data with the code data which recognizes the image data, and determines whether the recognizing device 46 has correctly recognized the image data. Judge. And if it is recognized normally,
On the other hand, if the recognition is incorrect, correction code data is generated. Then, such processing results are temporarily stored in a storage unit (not shown) provided separately in the workstations 431 to 433. The MCU 42 transfers the code data correctly recognized or corrected to the host 60 via the communication control device 50 (step). When the host 60 receives the character code corresponding to the character described in the transfer request form in this way, thereafter, the transfer processing based on the request from the sales offices 10 to 30 is executed.

The transmission of the form data from each of the offices 10 to 30 is performed through the district center 40 as described above.
In the district center 40, a failure may occur in the MCU 42. In such a case, since the data processing from the sales offices 10 to 30 cannot be performed, the following recovery processing is performed.

FIG. 3 is a flowchart showing a recovery process when an MCU 42 failure occurs. First, if any failure occurs in the MCU 42 (step S1), the FCU
No. 41 makes it impossible to receive facsimile data from the sales offices 10 to 30 (step S2). MCU4
The failure 2 means that the operation is stopped due to a hardware failure, software, or the like. At the time when the reception from the branch is disabled in step S2, image data which is temporarily stored as received and not transmitted to the MCU 42 usually exists as the stay data a in the disk device 44. .

Next, when the recovery processing of the MCU 42 is performed (step S3), in the recovery method, an operation of restarting the system is performed from any of the workstations 431 to 433 (step S4), whereby the operation is restarted. Is done. Workstation 431-43
The MCU 42 that has received the system restart instruction from the FCU 3
In response to 41, receive the MCU from
An instruction to clear the unsent data is transmitted to 42 (step S5).

The reason why the accumulated data in the FCU 41 is cleared is that, for example, when a failure occurs and the data is restored immediately before the end of reception of the host 60, and at this time the accumulated data transmitted from the FCU 41 to the MCU 42 is large, the accumulated data is This is because there is a possibility that the processing cannot be performed by the verification correction unit 43 or the like before the reception of the host 60 is completed.

The FCU 41 clears the staying data based on the clear instruction from the MCU 42 (step S).
6) On the other hand, the MCU 42 transmits the recovery information to the target branch office to the FCU 41 (step S).
7). As a result, the FCU 41 edits the image data to transmit the restoration information received from the MCU 42 by facsimile (step S8), and transmits the edited information to the target sales offices 10 to 30 (step S9). afterwards,
The FCU 41 is ready to receive facsimile data from the sales offices 10 to 30 (step S10).

FIG. 2B shows an example of a form of the recovery information transmitted in step S9. In this form, the MCU 4 is registered when the MCU 42 fails in step S1.
2. Output the received final FAX serial number and missing number information. For example, in the example shown in the figure, the final reception FAX serial number is “200”.
FAX serial numbers “191” to “193”, “19”
7 indicates that the data of the transfer request form is missing.

FIG. 4 shows an example of a transfer request form for entering a FAX serial number. In the drawing, a portion indicated by 201 is a frame in which a FAX serial number (FAX number) is entered. This FAX serial number means that each of the business offices 10 to 30 has a facsimile 11 to
It is a serial number assigned at the time of transmission at 31 and is assigned for each form. Accordingly, the sales offices 10 to 30 that have received the recovery information
Then, from the missing number information, it is possible to know which form has been cleared by the FCU 41.

Then, the business offices 10 to 3 receiving the restoration notice
0 indicates that if there is no time before the reception end time of the host 60, the data cleared in step S6 is directly transmitted to the host 60 from the office terminal not shown, and
If there is time before the reception end time of the host 60, the form is resent from the facsimile machines 11 to 31 of the offices 10 to 30, the data is processed at the district center 40, and the data is transmitted to the host 60.

[0020]

However, the above-described failure recovery processing has the following problems. (1) If there is sufficient time before the reception end time of the host 60, the processing time and the line usage fee for retransmitting the FCU stay data from the business offices 10 to 30 are wasted. That is, in this case, useless processing such as transmitting the same data as the once cleared data again has to be performed.

(2) In the case where it takes time until the MCU 42 is restored, the time for outputting the restoration notice to the offices 10 to 30 is delayed, and as a result, the response of the offices 10 to 30 is delayed.
There is a possibility that a serious accident such as generation of data not transmitted to the host 60 may occur. In other words, the inability to perform the transfer process that should be performed on the same day must not be a financial institution such as a bank, and a reliable measure against such an obstacle has been required.

(3) In the branch offices 10 to 30, the district center 4
Since the status of 0 is not known, even if a failure occurs in the MCU 42, it is not possible to immediately take a measure according to the status. That is, even if a failure occurs in the district center 40, the sales offices 10 to 30 only know that the form data cannot be transmitted normally, and cannot determine the cause. Alternatively, no prompt action could be taken unless confirmation was made to the district center 40 by telephone. The present invention has been made to solve the above-mentioned conventional problems, and has as its object to provide an efficient and highly reliable fault recovery control system.

[0023]

According to a first aspect of the present invention, there is provided a failure recovery control system which is connected to a plurality of data transmission sources via a communication line and transmits data from each data transmission source. In a system including a management center for storing and processing data, the management center includes:
Assuming that a failure has occurred in the management center, a recovery pattern table in which a recovery processing pattern corresponding to the failure occurrence time is set in advance, and if a failure has occurred in the management center, refer to the recovery pattern table,
A recovery processing unit that performs a recovery process corresponding to the failure occurrence time.

A fault recovery control system according to a second aspect of the present invention
In the first invention, the recovery pattern table is:
A failure is assumed to occur in the management center, and a recovery processing pattern is set in advance corresponding to the failure occurrence time and the data transmission destination from the data transmission source.

[0025] The failure recovery control system according to the third invention comprises:
In the above first or second invention, the recovery processing unit comprises:
It operates in a pattern based on a reception control that controls whether to resume data reception after a failure occurs and a return control that controls whether unprocessed data until the failure is returned to the data transmission source. It is assumed that.

A failure recovery control system according to a fourth aspect of the present invention
In the above first or second invention, the recovery processing unit comprises:
A pattern is determined based on reception control for controlling whether to resume data reception after a failure occurs and return control for controlling whether to return unprocessed data until the failure to the data transmission source. A broadcast message corresponding to each pattern is output to the data transmission source.

[0027]

In the fault recovery control system according to the first aspect of the present invention, when a fault occurs in the MCU of the district center, the FCU
First, the recovery processing unit reads the current time, and then obtains a recovery processing pattern corresponding to the current time from the recovery pattern table. Then, the recovery processing unit executes the recovery processing of the obtained pattern.

Further, in the failure recovery control system according to the second aspect of the present invention, data from a data transmission source is separately stored corresponding to the transmission destination. When a failure occurs in the district center, the recovery processing unit refers to the recovery pattern table and obtains a recovery processing pattern based on the current time and the transmission destination. Then, the recovery processing unit performs the recovery processing using the pattern obtained for each transmission destination.

Further, in the failure recovery control system according to the third aspect of the present invention, when a failure occurs, the recovery processing unit, for example, if there is a sufficient time before the reception end time of the host, once the data from the data transmission source is received. The reception reception is stopped, and when the failure is recovered thereafter, the data reception reception is restarted. In this case, the data received from the data transmission source until the failure occurs is not returned to the data transmission source. If the failure occurrence time is a time with some allowance before the reception of the host is completed, the data reception from the data transmission source thereafter is stopped, and the unprocessed data at the district center is processed at the district center. If the failure occurrence time is immediately before the end of the reception of the host, data received before the failure and not processed by the district center is returned to the data transmission source and processed by the data transmission source.

In the fault recovery control system according to the fourth invention, the same recovery processing as in the third invention is performed, and a broadcast message corresponding to the recovery pattern is output. For example, if there is sufficient time before the host's reception end time, a message to stop data transmission is sent for a while, and if there is some time before the host's reception end time, the unsent data is the data transmission source. In the case where it is immediately before the end of host reception, a message is sent to return unprocessed data at the district center.

[0031]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a block diagram showing an embodiment in which the failure recovery control system of the present invention is applied to a FAX-OCR system in a financial institution. In the figure, offices 10 to 30 are provided with facsimile machines (FAX) 11 to 31 as data transmission sources, and image data from these facsimile machines 11 to 31 are transmitted via a communication line 70 to the district center 40 as in the conventional case. Is sent to

A district center 40, which is a management center for storing data from the facsimile machines 11 to 31 and processing the data, is provided with a facsimile reception control unit (FCU).
410, a control unit (MCU) 42, a verification correction unit 43, a disk device 44, a workstation (WS) 45, a recognition device 46, a disk device 47, a printer 48, and a facsimile 49. Here, the FCU 410 is provided with a recovery pattern table 101, which is a feature of the present embodiment, and a recovery processing unit 102. The recovery pattern table 101 stores the M of the district center 40.
If a failure has occurred in the CU 42, the table indicates in advance the type of recovery processing corresponding to the failure occurrence time.

FIG. 5 shows the recovery pattern table 1
FIG. 11 is a diagram showing the details of a content No. 01 and a flowchart for executing a recovery process. That is, the recovery pattern table 101
The time zone of the failure occurrence time is divided into four, and patterns corresponding to these time zones are respectively set. For example, when the time zone is from 8:00 to 12:00, the pattern A, 12:00
From 13:00 to 13:00, pattern B, 13:00 to 15:00
In pattern C, the pattern is determined in advance, such as pattern A, from 15:00 to 17:00. still,
The contents of the patterns A to C will be described later in detail.

In FIG. 1, the recovery processing unit 102
When a failure occurs in the MCU 42, the MCU 42 has a function of referring to the recovery pattern table 101 and performing recovery processing corresponding to the failure occurrence time. In addition, other F
The functions of the CU 410 and the other components in the district center 40 are the same as those of the related art, and thus description thereof will be omitted. Further, the configurations of the communication control device (CCL) 50, the host (HOST) 60, and the communication line 70 are the same as those in the related art.

Next, the operation when a failure occurs in the FAX-OCR system having the above configuration will be described. In addition, FAX-OC
Flow of data processing of the R system, that is, steps to
The operation indicated by is the same as the conventional operation, and the description thereof is omitted here. When any failure occurs in the MCU 42 of the district center 40, the FCU 410 performs a recovery process as shown in FIG.

First, when the FCU 410 detects a failure of the MCU 42 (step S1), the recovery processing unit 102 of the FCU 410 reads the current time from a clock in the FCU 410 (not shown) (step S2). Next, the recovery processing unit 102 reads the recovery pattern table 101 (step S3), and determines a recovery pattern from the current time read in step S2 (step S4). Then, the recovery processing unit 102
The determined recovery processing is executed (step S5).

Next, the recovery patterns A to C will be described. << First Pattern >> FIG. 6 is a flowchart for explaining the first pattern (pattern A). This pattern A is a case where there is sufficient time until the reception of the host 60 is completed. In the recovery pattern table 101 shown in FIG. 5, the time zone 15:00 to 17:00 is the pattern A because the transfer processing to another line is usually until about 15:00 and the processing on the day is not performed. This is because the processing is aborted, that is, the reception of the host between the other lines is terminated, and the subsequent processing is performed only between the lines, and in this case, there is a sufficient time margin.

A fault occurs in the MCU 42 (step S).
1) When the FCU 410 detects this (Step S)
2) First, the recovery processing unit 102 reads the text of the broadcast message of the first pattern (step S3).
The wording of the broadcast message and the wording of a recovery message described later are transferred from the MCU 42 when the system is started, or are stored in advance in a memory (not shown) or the disk device 44 in the FCU 410.

When the wording of the first pattern is read in step S2, the recovery processing unit 102 transmits the broadcast message to each of the offices 10 to 30 (step S2).
4). In each of the sales offices 10 to 30, the broadcast message is received by each of the facsimile machines 11 to 31, and is output (step S5). The b in the figure is an example of this broadcast message, in which a failure occurs in the district center 40, and a message is transmitted so as to stop transmitting the form until the failure is recovered.

Thereafter, when the failure of the MCU 42 is recovered (step S6), the MCU 42 sends a recovery notification to the FCU 41.
Output is made for 0 (step S7). Thereby, F
The recovery processing unit 102 of the CU 410
The image data (shown by a in the figure) of the form staying in the document 4 is transmitted to the MCU 42 (step S8). Next, the recovery processing unit 102 edits the recovery notification message into image data for facsimile transmission (step S9), and transmits this to each of the business offices 10 to 30 (step S10).

In each of the sales offices 10 to 30, this is received by the facsimile 11 to 31 and output as a message (step S11). The restoration message c in the figure indicates that the transmission of the form can be resumed.
As described above, in the pattern A, each branch 1
Since the form data transmitted from 0 to 30 to the district center 40 is processed by the district center 40, there is no need to resend the data from the sales offices 10 to 30.

<< Second Pattern >> FIG. 7 is a flowchart for explaining the second pattern (pattern B). This pattern B is a recovery process that is effective when a failure occurs when there is a certain period of time before the reception of the host 60 is completed.

First, a failure occurs in the MCU 42 (step S1), and when this is detected by the FCU 410 (step S2), the recovery processing unit 102 reads the wording of the second pattern (step S3) and sends it to each business office. 10-30
Is transmitted as a broadcast message (step S4). In each of the stores 10 to 30, the facsimile 11 to 31
And output as a message (step S
5). This broadcast message is shown in FIG. That is, after the occurrence of the failure, the district center 40 does not accept the data processing, and the subsequent form data processing is a message to be processed by the sales offices 10 to 30.

On the other hand, the recovery processing unit 10 of the FCU 410
2 adds the data read at step S3 to the stay data a received until the occurrence of the failure, and adds the text read at step S3 to the district center 40.
Is output to the facsimile 49 (step S6).

FIG. 8 shows an image of a form output by the facsimile 49. The image data of this form is shown in FIG.
This indicates the contents of the transfer request form indicated by, and in the figure, A
Is the wording added.

As a result, in the district center 40, the MCU
42 is restored (step S7), the restoration notice is sent to F
While transmitting to the CU 410 (step S8),
Data processing of the form output in step S6 is performed (step S9). This form data processing is performed by the
The data entry from the workstations 431 to 433, that is, the processing by manual input by the operator,
Alternatively, there is a method of performing data entry using another terminal device installed in the district center 40, or the like. As described above, the second pattern (pattern B) is characterized in that the stay data received before the occurrence of the failure is processed by the district center 40.

<< Third Pattern >> FIG. 9 is a flowchart for explaining the third pattern (pattern C). This pattern C is a recovery process effective when a failure occurs immediately before the reception of the host 60 ends.

First, a failure occurs in the MCU 42 (step S1), and when this is detected by the FCU 410 (step S2), the recovery processing unit 102 reads the wording of the third pattern (step S3) and sends it to each business office. 10-30
Is transmitted as a broadcast message (step S4). Also, the stay data a received before the occurrence of the failure is returned (step S5). In each of the sales offices 10 to 30, these transmission data are received and output by the facsimile machines 11 to 31 (steps S6 and S7).

The broadcast message output in step S6 is shown in FIG. In other words, the unsent form and the return form that are to be transmitted from the business offices 10 to 30 are messages requesting that the business offices 10 to 30 process them. The return form is as follows.

FIG. 10 is an example of a return form. The image data of the form shows the contents of the transfer request sent from each of the facsimile machines 11 to 31 to the district center 40, and is a word to which A is added in the drawing. Thus, each of the sales offices 10 to 30 transmits the data directly to the host 60, and ends the processing. As described above, in the third pattern, all data that has not been processed by the MCU 42 after the occurrence of a failure is processed by each of the sales offices 10 to 30.

Next, another embodiment in which a recovery processing pattern is set in the recovery pattern table 101 in accordance with not only the failure occurrence time but also the data transmission destination will be described. FIG. 11 is a flowchart of a recovery pattern table and a recovery process for explaining another embodiment. That is, in this embodiment, the FCU 410 in the district center 40 performs a recovery process according to the exchange of the form transmission to another bank and the form transmission to the own bank by changing the telephone number (line). For example, the processing from 8:00 to 17:00 for the other line whose reception end time of the host 60 is earlier (usually around 15:00) is “A,
B, C, A ", and the processing of the host 60 whose address is late for the reception end time has a pattern of" A, A, B, C ". It should be noted that the use of the line 70a and the line 70b can be easily handled by applying to the public network.

In another embodiment configured as described above, the sales offices 10 to 30 transmit a report addressed to another line to the telephone number (for example, 0484-31-1234) as the line 70a (step S1). And a telephone number as the line 70b (for example, 0484-3
1-5678), the form addressed to the bank is transmitted (step S2).
The FCU 410 tanks (deposits) these form data in another file in the disk device 44.

When a failure occurs in the MCU 42 and the FCU 410 detects this (step S3), the recovery processing unit 102 reads the current time (step S3).
4), the recovery pattern table 101 is read (step S5). After that, the recovery processing unit 102
A recovery pattern corresponding to the stay data a addressed to another row and the stay data b addressed to the own row is determined (steps S6 and S7). For example, if the failure occurrence time is “13: 3
If it is “0”, the recovery pattern of the staying data a addressed to another row is “C”, and the recovery pattern of the staying data b addressed to the own row is “B”. Therefore, the stay data a addressed to another bank is returned to the sales offices 10 to 30 (step S8),
In the case of the stay data b addressed to the own line, the MCU 42 waits for the recovery of the MCU 42 (step S9). That is, the stay data b addressed to the own bank
In the case of, after the failure recovery, the FCU 410 transmits the message to the MCU.

In each of the above embodiments, three types of recovery patterns are used in the recovery pattern table 101. However, the present invention is not limited to this, and more types of recovery patterns can be used. The processing may be variously changed according to the form of the system to be applied. Further, in each of the above-described embodiments, the case where the FAX-OCR system in the financial institution is described as a system to which the failure recovery control system is applied. However, data is transmitted from a plurality of data transmission sources to the management center, and these data are managed. If the processing is performed by the center, the same effects as in the above embodiments can be obtained.

[0055]

As described above, according to the failure recovery control system of the first invention, the recovery processing pattern corresponding to the failure time is set in advance, and if a failure occurs, the recovery processing is performed for each pattern. Since it is performed, there is no need to retransmit data, and the efficiency is improved. In addition, recovery processing optimal for a failure can be performed, so that the reliability of the system can be improved.

According to the fault recovery control system of the second invention, the recovery processing pattern is set in accordance with the data transmission destination. Therefore, in addition to the effects of the first invention, the efficiency and the reliability are further improved. Can be achieved.

According to the fault recovery control system of the third aspect of the present invention, the recovery process controls whether the management center resumes reception after a fault occurs or returns unprocessed data before the fault to the transmission source. Since the above pattern is adopted, in addition to the effect of the first aspect, the data transmission source can quickly and reliably perform the processing after the occurrence of the failure.

According to the fault recovery control system of the fourth invention, when a fault occurs, a broadcast message corresponding to each pattern is transmitted to each data transmission source. The situation can be understood, and the subsequent processing can be promptly performed.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an application example of a failure recovery control system according to an embodiment of the present invention.

FIG. 2 is a system block diagram for explaining a conventional failure recovery control process.

FIG. 3 is a flowchart of a conventional failure recovery process.

FIG. 4 is a diagram showing an example of a form.

FIG. 5 is a diagram showing an operation flowchart and a recovery pattern table of the failure recovery control system of the present invention.

FIG. 6 is an explanatory diagram showing a first pattern of recovery processing in the failure recovery control system according to the present invention.

FIG. 7 is an explanatory diagram showing a second pattern of the recovery processing in the failure recovery control system according to the present invention.

FIG. 8 is an explanatory diagram showing an output form image in a second pattern of the recovery processing in the failure recovery control system of the present invention.

FIG. 9 is an explanatory diagram showing a third pattern of the recovery processing in the failure recovery control system according to the present invention.

FIG. 10 is an explanatory diagram showing an output form image in a third pattern of the recovery processing in the failure recovery control system according to the present invention.

FIG. 11 is an explanatory diagram showing another embodiment in the failure recovery control system of the present invention.

[Explanation of symbols]

 11, 21, 31 Data source (facsimile) 40 Management center (district center) 42 Control unit 49 Facsimile 60 Host 101 Recovery pattern table 102 Recovery processing unit

Claims (4)

(57) [Claims] 1. A system comprising: a plurality of data transmission sources; and a management center connected to the plurality of data transmission sources via a communication line, stores data from each of the data transmission sources, and performs data processing. The management center, assuming that a failure has occurred in the management center, and a recovery pattern table in which a recovery processing pattern corresponding to the time of occurrence of the failure is set in advance; A failure recovery control system comprising: a recovery processing unit that refers to a table and performs a recovery process corresponding to a failure occurrence time. 2. The recovery pattern table is characterized in that a failure in the management center is assumed, and a recovery processing pattern is set in advance corresponding to the failure occurrence time and the data transmission destination from the data transmission source. The fault recovery control system according to claim 1, wherein 3. A recovery processing unit for controlling whether or not to resume data reception after a failure, and a return control for controlling whether or not unprocessed data until a failure is returned to a data transmission source. 3. The fault recovery control system according to claim 1, wherein the fault recovery control system operates in a pattern based on: 4. A recovery control unit for controlling whether or not to resume data reception after the occurrence of a failure, and a return control for controlling whether or not unprocessed data until the occurrence of the failure is returned to a data transmission source. 3. The failure recovery control system according to claim 1, wherein a pattern is determined based on the above, and a broadcast message corresponding to each pattern is output to a plurality of data transmission sources.