JP2001067288A - Device having failure repair function, server device supporting the device, system having failure repair function, and program recording medium - Google Patents

Abstract

(57) [Summary] The present invention provides an apparatus having a failure repair function,
An object is to provide a server device that supports the device. When a failure occurs, a temporary system is constructed according to failure repair information stored in a database.
The system is restored by trying to restore the system accordingly, and if the system cannot be restored by that process, the information at that time is sent to the server device provided as a support device to provide the failure repair function. Implement a device that has On the other hand, the server device that supports the device creates failure repair information that realizes the repair of a failure that could not be repaired by the device according to the information sent from the device, and transmits it to the device. The database will be enhanced by going there. With this configuration, a system having a failure repair function is realized.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus having a failure repair function, a program recording medium storing a program used to realize the apparatus, a server apparatus supporting the apparatus, and an implementation of the server apparatus. And a system having a failure repair function.

[0002]

2. Description of the Related Art As seen on the Internet,
A server-client type system including a huge number of clients and a server connected to the clients via a network and providing services to the clients is widely used.

In such a server-client type system, conventionally, when a failure such as a communication failure occurs in a client, the client displays a message to that effect on a display screen to inform the user of the content of the failure. The processing is performed so as to instruct the user to repair the failure by the user or the serviceman.

[0004]

However, according to such a conventional technique, a user who is not familiar with a computer cannot repair a failure by himself, and therefore, a server until a service person arrives. There is a problem that the service can not be provided from.

[0005] Then, there is a problem that a company that provides a maintenance service has to arrange a large number of service personnel nationwide in accordance with an enormous number of clients.

[0006] Since many system modules have been provided to clients, many failures appearing to be the same at first glance, but actually having different causes, have been increasing. Yes,
There is a problem that it is taking time to repair a failure.

[0007] The present invention has been made in view of the above circumstances, and provides a client constituting a server-client type system with a failure repair function, and provides a server with a failure repair function. It is an object of the present invention to provide a new technology that can realize an automatic repair of a failure that has occurred in a client by providing a support function.

[0008]

FIG. 1 shows the principle configuration of the present invention.

In FIG. 1, reference numeral 1 denotes a client device provided with the present invention, and reference numeral 2 denotes a server device provided with the present invention connected to the client device 1 via a network.

The client device 1 of the present invention comprises a first database means 10, a first updating means 11, a second database means 12, a second updating means 13, a failure detecting means 14, a recovery It comprises means 15, notification means 16 and output means 17.

The first database means 10 manages system change information for repairing the fault and system information to which the system change information is applied, in association with the fault code. The first updating means 11
The information managed by the first database means 10 is updated by receiving and registering information to be registered in the first database means 10 from the server device 2.

The second database means 12 manages guide information for repairing the fault in association with the fault code. The second updating unit 13 updates information managed by the second database unit 12 by receiving and registering information registered in the second database unit 12 from the server device 2.

The fault detecting means 14 detects the occurrence of a fault and specifies a fault code of the fault. When a failure occurs, the recovery unit 15 constructs a temporary system based on the system change information managed by the first database unit 10 and restores the system by trying to recover the system according to the temporary system.

The notifying means 16 notifies the server device 2 of a code of a failure in which the system cannot be recovered and system information at the time of the failure. The output unit 17 acquires and outputs guide information for restoring a failure in which the system cannot be restored by the process of the restoration unit 15 in accordance with the information managed by the second database unit 12.

When adopting this configuration, the first database means 10 manages information on the number of times used for restoring the system for each management information in accordance with the information from the server device 2. The system recovery may be attempted while selecting the system change information according to the order of the frequency information.

On the other hand, the server device 2 according to the present invention comprises: an acquiring unit 20; a first database unit 21;
, A second database means 23, a third database means 24, and a transmission means 25.

This acquisition means 20 is a client device 1
From, the code of the failure that could not recover the system,
The system information at the time of the failure is obtained. The first database unit 21 stores the information obtained by the obtaining unit 20.

According to the interactive processing, the creating unit 22 associates the failure code acquired by the acquiring unit 20 with system change information for repairing the failure and system information to which the system change information is applied. It is created and registered in the second database means 23. Further, according to the interactive processing, guide information for repairing the failure is created in association with the failure code acquired by the acquisition means 20, and the third information is created. Register in the database means 24.

The second database means 23 is system change information created by the creating means 22 and associated with the fault code, for repairing the fault, and the system change information to which the system change information is applied. Manage system information. The third database means 24 manages the guide information created by the creating means 22 and associated with the fault code, for repairing the fault.

The transmitting means 25 transmits information managed by the second database means 23 to the client device 1, and further transmits information managed by the third database means 24 to the client device 1.

When adopting this configuration, the acquisition means 20
From the client device 1, the second database means 23
Of which information is used to recover the system using the information managed by
5 may transmit the counted value to the client device 1.

In the server / client system of the present invention configured as described above, when the fault detecting means 14 detects the fault code of the fault, the recovering means 15 searches the fault code and the current system information. By searching the first database means 10 as a key, system change information for repairing the failure is obtained, thereby constructing a temporary system, and attempting to restore the system in accordance therewith. Let it recover.

When the system cannot be recovered by the processing by the recovery means 15, the output means 17 searches the second database means 12 using the failure code detected by the failure detection means 14 as a search key, and detects the failure. By acquiring and outputting guide information for repair, a failure repair process performed by a user or the like is supported.

When the system cannot be recovered by the processing by the recovery unit 15, the notification unit 16 notifies the server device 2 of a failure code that cannot be recovered from the system and system information at the time of the failure.

In response to the notification from the client device 1, the acquiring means 20 acquires the code of the failure in which the system could not be restored and the system information at the time of the failure. By interacting with a service person or the like, in association with the failure code acquired by the acquisition unit 20, system change information for repairing the failure and system information to which the system change information is applied are created. Further, guide information for repairing the failure is created.

In response to the creation, the transmission means 25 transmits the system change information for repairing the failure and the system information to which the system change information is applied, which are defined in association with the failure code, to the client. By transmitting the information to the device 1, the management information of the first database means 10 of the client device 1 is updated, and the management information is enhanced.

The transmitting means 25 transmits the guide information for repairing the failure, which is defined in association with the failure code, to the client apparatus 1, thereby transmitting the second database means 12 of the client apparatus 1. Update the management information of

As described above, in the server-client system of the present invention, when a failure occurs, the client device 1 constructs a temporary system according to the failure repair information notified from the server device 2, and according to that, Attempting to recover the system restores the system,
When the system cannot be recovered, a request is made to the server device 2 to upgrade the failure repair information, thereby adopting a configuration for enriching the failure repair information. You will be able to recover.

When a failure occurs and the system cannot be restored by the change of the system by the failure repair information, the client device 1
By outputting guide information for repairing the failure notified from the server, the failure repair by the user or the like is supported, and when the system cannot be recovered, the server device 2
By requesting a version upgrade of the guide information, the configuration in which the guide information is enriched is adopted, so that the trouble that has occurred can be surely recovered.

[0030]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail according to embodiments.

FIG. 2 shows an embodiment of the present invention. As shown in this figure, a client device 1 of the present invention is connected to a server device 2 of the present invention via a network 4 and to one or a plurality of server devices 3 that provide information such as Web pages. Connected.

When the client device 1 reaches a prescribed cycle, the client device 1 executes a process of cyclically acquiring a plurality of pieces of information provided by the server device 3, and when a communication failure occurs during this execution, the communication failure occurs. And restore the system automatically.

In order to execute this processing, the client device 1 communicates with the client processing mechanism 30
It includes a database 31, a failure repair database 32, a failure repair guide database 33, a tour setting system data area 34, an occurrence failure data area 35, an unrecovered failure data area 36, and a failure repair update data area 37. .

On the other hand, the server device 2 of the present invention obtains information of an unrecoverable communication failure from the client device 1,
By interacting with a service person or the like, information for repairing the communication failure is created and transmitted to the client device 1 so that the client device 1 can repair a communication failure that cannot be repaired. Execute.

In order to execute this processing, the server device 2 of the present invention includes a server processing mechanism 40, an unrecovered failure database 41, a failure repair database 42, and a failure repair guide database 43.

The cyclic data provided by the client device 1
The database 31 manages information (tour data) acquired from the server device 3 that provides information such as Web pages.

The failure repair database 32 provided in the client device 1 updates what program module to what program module when a communication failure specified by a failure code occurs in the system specified by the target system. The system manages change information of the system as to whether the communication failure can be repaired when the communication failure is added or what program module is added.

FIG. 3 shows an embodiment of information managed by the failure repair database 32. For example, Windows
A system consisting of 95 dial-up connections
When a communication failure with a failure code of Error02 occurs, it is managed that if the currently used module 5 is replaced with the update module 5 and an additional module i is newly added, the communication failure may be repaired.

For example, when a user installs a certain program in the client device 1, the program rewrites a communication program and setting data necessary for communication, so that the system that has been operating normally operates normally. It happens that it doesn't work.

In such a case, the failure repair database 32 manages information such that such a failure can be repaired by, for example, upgrading the version of the communication program. Further, the failure repair database 32
Employs a configuration that also manages the number of times that a failure can be repaired by using the information (determined by counting the notifications from each client device 1 and serving as a measure of the validity of the information). Here, a failure repair ID is assigned to each record of the failure repair database 32.

The failure repair guide database 33 provided in the client device 1 stores what operation (a dip switch other than a change in the system configuration) when a communication failure specified by a failure code occurs in the system specified by the target system. , Etc.), document information (failure repair guide data) as to whether the communication failure can be repaired.

FIG. 4 shows an embodiment of information managed by the failure repair guide database 33. For example,
Document information such as "If you are using a modem, set the communication speed to 28.8K or less," if a communication failure with the error code HTTPError05 occurs, you can repair the communication failure. It manages. Here, the failure repair guide database 33
Is assigned a failure repair guide ID.

The tour setting system data area 34 provided in the client device 1 includes a tour destination of the tour data, a server address for managing the tour data (it is not necessary to be the same server device 3), and an acquisition of the tour data. It stores tour setting system data describing system information (including OS information and the like) of necessary program modules and the like, a communication protocol necessary for acquiring the tour data, and information on the last tour date and time.

FIG. 5 shows an example of the tour setting system data. The tour setting system data shown in this figure includes program modules 1, 2,
5,7 (including differences in version numbers) and according to the HTTP communication protocol, "/index.htm" provided by the server device 3 having the server address "www.foo.co.jp".
l "is obtained. In the following description, for convenience of explanation, it is assumed that this tour setting system data defines acquisition of N pieces of tour data.

The fault data area 35 of the client device 1 stores fault data having a data structure described later with reference to FIG. The unrecovered failure data area 36 provided in the client device 1 stores unrecovered failure data having a data structure described later with reference to FIG. The failure repair update data area 37 provided in the client device 1 stores failure repair update data having a data structure described later with reference to FIG.

The unrecovered failure database 41 provided in the server device 2 of the present invention stores the unrecovered failure data sent from the client device 1. Further, the failure repair database 42 provided in the server device 2 of the present invention stores failure repair data to be sent to the client device 1. Also,
The failure repair guide database 43 provided in the server device 2 of the present invention stores failure repair guide data (document information) to be sent to the client device 1.

FIGS. 6 to 9 show an embodiment of the processing flow executed by the client processing unit 30, FIGS. 10 and 1.
FIG. 1 shows an embodiment of a processing flow executed by the server processing module 40. Next, according to these processing flows,
The present invention will be described in detail.

First, the processing executed by the client processing unit 30 will be described with reference to the processing flows of FIGS.

When the client processing mechanism 30 is activated upon reaching the automatic tour cycle (the cycle of acquiring N pieces of tour data defined by the tour setting system data), as shown in the processing flow of FIG. 6 to FIG. First, in step 1, "1" is set to a variable i.

Subsequently, in step 2, a process of acquiring the i-th round data is executed according to the i-th entry data of the round setting system data. That is, the module defined by the i-th entry data is used, and the acquisition of the cyclic data defined by the entry data is attempted from the server device 3 defined by the entry data according to the communication protocol defined by the entry data.

Subsequently, in step 3, it is determined whether or not the i-th cyclic data has been acquired by the acquisition processing. When it is determined that the i-th cyclic data has been acquired, the cyclic data is stored in the cyclic data database 31. After storing the variable i, the variable i is incremented by one. Then, in the following step 5, it is determined whether or not the variable i has become larger than N. When it is determined that the variable i has not become larger, the process returns to step 2. Then, the processing for acquiring the next traveling data is started.

On the other hand, when it is determined in step 3 that the i-th cyclic data cannot be obtained, that is, when it is determined that the cyclic data cannot be obtained due to the occurrence of a communication failure, the process proceeds to step 6, and the process proceeds to step 6. By using the communication failure code and the system information at the time of occurrence of the communication failure as a search key, the failure repair database 32 is searched to retrieve system change information that enables the repair of the communication failure.

Subsequently, in step 7, it is determined whether or not the system change information enabling the restoration of the communication failure can be searched by the search processing. If it is determined that the search cannot be performed, the process proceeds to step 8. In addition, the communication failure code is added to the generated failure data having the data structure shown in FIG. 12 defined by the connection of the failure codes, and the unrecovered failure data having the data structure shown in FIG. 13 is created. I do. That is, unrecovered failure data composed of pair data of the communication failure code and the system information at the time of occurrence of the communication failure is created.

Subsequently, in step 9, the variable i is incremented by one, and then in step 10, the variable i is set to N
When it is determined whether or not it has become larger than that, and it is determined that it has not become larger, the process returns to step 2 to start processing for acquiring the next cyclic data.

On the other hand, when it is determined in step 7 that the system change information enabling the restoration of the communication failure can be searched, the process proceeds to step 11 (the processing flow in FIG. 7), and all the searched system change information is processed. When it is determined whether or not the selection has been completed and it is determined that not all have been selected, the process proceeds to step 12, where the number of applications of the system change information (the failure is repaired by using the system change information) One unselected one from the retrieved system change information is selected in the descending order of the number of times that has been made.

Subsequently, in step 13, according to the selected system change information, instead of the system configuration used in the cyclic data acquisition processing (i-th cyclic data acquisition processing) executed in step 2, the system change is performed. Build a temporary system defined by the system configuration specified by the information. Subsequently, in step 14, the i-th cyclic data acquisition process is executed again using the temporary system. That is, using the temporary system, in accordance with the communication protocol defined by the i-th entry data, acquisition of cyclic data defined by the entry data is attempted from the server device 3 defined by the entry data.

Subsequently, in step 15, it is determined whether or not the i-th cyclic data has been acquired by the acquisition processing.
Proceeding to 6, the temporary system that has been constructed is deleted, and the process returns to step 11 in order to attempt acquisition processing by the next temporary system.

On the other hand, when it is determined in step 15 that the i-th cyclic data has been obtained, step 17
To store the traveling data in the traveling data database 31 and specify the i-th entry data of the traveling setting system data necessary for obtaining the i-th traveling data according to the constructed temporary system. Update the configuration.

Subsequently, at step 18, the failure repair ID
The failure repair update data having a data structure as shown in FIG. 14 defined by the connection of the (failure repair database 32 record IDs) includes the system change information selected in step 12 (the system change information for which the communication failure was successfully repaired). )
Is added.

Subsequently, at step 19, the variable i is incremented by one, and then at step 20, it is determined whether or not the variable i has become larger than N, and it is determined that the variable i has not become larger. In some cases, the process returns to step 2 to start the process of acquiring the next tour data.

On the other hand, when it is determined in step 11 that the selection of all the system change information searched in step 6 has been completed, that is, when it is determined that a communication failure cannot be repaired by the searched system change information,
Proceeding to step 21 (the processing flow of FIG. 8), the communication failure code is added to the occurrence failure data having the data structure shown in FIG. 12, and the data structure has the data structure shown in FIG. Create unrecovered failure data.

Subsequently, in step 22, the variable i is incremented by one, and then in step 23, it is determined whether or not the variable i is larger than N, and it is determined that the variable i is not larger. In some cases, the process returns to step 2 to start the process of acquiring the next tour data.

On the other hand, when it is determined in step 5 / step 10 / step 20 / step 23 that the variable i has become larger than N, that is, the acquisition processing of all cyclic data (the acquisition fails due to a communication failure) Sometimes)
When it is determined that has been executed, the process proceeds to step 24, where it is determined whether or not the fault repair update data (shown in FIG. 14) is stored in the fault repair update data area 37. When it is determined that the error has occurred, the process proceeds to step 25, where the stored failure repair update data is transmitted to the server device 2 of the present invention.

Subsequently, at step 26, it is determined whether or not unrecovered failure data (shown in FIG. 13) is stored in the unrecovered failure data area 36, and it is determined that the data is stored. In some cases, the process proceeds to step 27, where the stored unrecovered failure data is stored
Send to

Subsequently, at step 28, the latest data (sent in the form of differential data) of the failure repair data stored in the failure repair database 32 and the failure repair Guide database 3
A request for transmission of the latest data (sent in the form of differential data) of the failure repair guide data stored in the third data is issued.

Subsequently, in step 29, it is determined whether or not the difference data has been sent, and when it is determined that the difference data has been sent, that is, the failure repair data and the failure repair guide data are updated. If so, the process proceeds to step 30 (the processing flow in FIG. 9), and in accordance with the transmitted difference data, the fault repair data stored in the fault repair database 32 or the fault repair guide database 33 is stored. Update the repair guide data.

Subsequently, in step 31, it is determined whether or not the occurrence failure data (shown in FIG. 12) is stored in the occurrence failure data area 35, and when it is determined that the occurrence failure data is stored, Proceeding to step 32, the failure repair guide database 33 is searched by using the failure code of the generated failure data as a search key, and the failure repair guide data (what operation is performed can repair the communication failure). Document information), and outputs it to end the process.

As described above, the client processing mechanism 3
0 indicates that if a communication failure occurs during the execution of the cyclic data acquisition process, a temporary system is constructed according to the failure repair data sent from the server apparatus 2 of the present invention, and the system is restored in accordance with the provisional system. Is restored, and if the system cannot be restored, the information at that time is notified to the server device 2 of the present invention.

When the system cannot be restored by the change of the system by the failure repair data sent from the server 2 of the present invention, the client processing mechanism 30 restores the failure sent from the server 2 of the present invention. According to the guide data, processing is performed so as to output document information for repairing the communication failure that has occurred.

Next, the processing executed by the server processing module 40 will be described with reference to the processing flows of FIGS. 10 and 11.

When a request is issued from the client device 1, the server processing mechanism 40 first recovers a failure sent from the client device 1 in step 1 as shown in the processing flow of FIG. If it is determined whether the data is update data (shown in FIG. 14) or not and if it is determined that the failure repair update data has been sent, the process proceeds to step 2 and the number of times the record of the failure repair database 42 has The number of applications indicated by the fault repair ID of the fault repair update data is counted up. That is, processing is performed so as to count the number of applications of the failure repair data used for the failure repair.

On the other hand, in step 1, the client device 1
When it is determined that the data transmitted from the client device 1 is not the failure repair update data, the process proceeds to step 3 to determine whether the data transmitted from the client device 1 is the unrecovered failure data (shown in FIG. 13). When it is determined that the unrecovered failure data has been sent, the process proceeds to step 4 to store the sent unrecovered failure data in the unrecovered failure database 41.

On the other hand, in step 3, the client device 1
When it is determined that the data transmitted from the client device 1 is not the unrecovered failure data, the process proceeds to step 5 to determine whether the data transmitted from the client device 1 is a transmission request for the failure repair data / failure repair guide data. Judge
When it is determined that the request is the transmission request, the process proceeds to step 6, where the failure repair data stored in the failure repair database 42 and the failure repair guide data stored in the failure repair guide database 43 are transmitted from the previously transmitted one. It is determined whether or not it has been updated.

By this determination processing, when it is determined that the fault repair data stored in the fault repair database 42 or the fault repair guide data stored in the fault repair guide database 43 has not been updated from the previously transmitted one. When it is determined that the update has been completed and the update has been performed, the process proceeds to step 7, and new failure repair data and failure repair guide data are transmitted to the client device 1 in accordance with the format of difference data from the previously transmitted one. I do.

As described above, the new failure repair data and the new failure repair guide data transmitted to the client device 1 in this manner allow the client device 1
Recovery database 32 and failure recovery guide
The information managed by the database 33 will be updated.

When a request is issued from a serviceman, the server processing mechanism 40 first stores the unrecovered failure data in the unrecovered failure database 41 in step 1 as shown in the processing flow of FIG. When it is determined whether or not the data is stored, and when it is determined that the data is not stored, the process is terminated.

On the other hand, when it is determined that the unrecovered failure data is stored in the unrecovered failure database 41, the process proceeds to step 2, where the stored unrecovered failure data is displayed on the display screen to provide the service. To the man.

Subsequently, in step 3, failure repair data of a repairable failure is created by interacting with the user through the presented unrecovered failure data, and stored in the failure repair database 42. That is, failure repair data as shown in FIG. 3 to be stored in the failure repair database 32 of the client device 1 is created and stored in the failure repair database 42. Subsequently, in step 4, the unrecovered failure data from which the created failure repair data was created is deleted from the unrecovered failure database 41.

Subsequently, in step 5, by interacting with the user through the presented unrecovered failure data, failure repair guide data serving as a hint for failure repair is created, and is used as the failure repair guide database 43. To be stored. That is, a failure repair guide for the client device 1
The failure repair guide data as shown in FIG. 4 to be stored in the database 33 is created and stored in the failure repair guide database 43. Subsequently, in step 6, from the unrecovered failure database 41,
The unrecovered failure data from which the created failure repair guide data was created is deleted, and the process ends.

As described above, the server processing mechanism 40
From the unrecovered failure data sent from the client device 1, failure repair data and failure repair guide data necessary for the client device 1 are created and transmitted to the client device 1. In addition to the enhancement of the failure repair data stored in the failure repair database 32 provided in the client device 1, the processing is performed so as to enhance the failure repair guide data stored in the failure repair guide database 33 provided in the client device 1. It is.

As described above, in the server / client system of the present invention, when a failure occurs, the client device 1 constructs a temporary system in accordance with the failure repair data notified from the server device 2 of the present invention, and accordingly, The system is restored by attempting to restore the system. On the other hand, when the system cannot be restored, the server device 2 of the present invention is requested to upgrade the version of the error recovery data, thereby enriching the error recovery data. By adopting a configuration that achieves this, it is possible to automatically recover the fault that has occurred.

When a failure occurs, the client device 1 outputs failure repair guide data notified from the server device 2 of the present invention when the system cannot be restored by changing the system using the failure repair data. This assists the user in repairing the failure, and when the system cannot be restored, the server device 2 of the present invention
By requesting a version upgrade of the failure repair guide data, a configuration in which the failure repair guide data is enriched is adopted, so that the failure that has occurred can be reliably recovered.

FIG. 15 shows the detailed device configuration of the client device 1 of the present invention described above, and FIG. 16 shows the detailed device configuration of the server device 2 of the present invention described above. Next, FIGS. 15 and 16 will be described.

First, the device configuration of the client device 1 will be described in detail with reference to FIG.

In FIG. 15, reference numeral 34a denotes tour setting system data, 300 denotes a communication fault notification mechanism, 33 denotes a fault repair guide database, 301 denotes a fault repair guide DB update mechanism, 302 denotes a tour data update mechanism, and 31 denotes a tour data update mechanism.
Database, 303, an automatic patrol mechanism, 304, a communication failure detection mechanism, 305, a failure repair DB update mechanism, 32, a failure repair database, 306, a communication failure repair mechanism, 30
7 is a temporary system erasure mechanism, 35a is failure data, 3
08 is an unrecovery countermeasure mechanism, 309 is a temporary system construction mechanism,
36a is unrecovered failure data, 310 is a test communication mechanism,
311 is a test communication failure detection mechanism, 37a is failure repair update data, and 312 is a system update mechanism.

The tour setting system data 34a records tour setting information for automatic tour communication.

The communication failure notifying mechanism 300 is provided when a failure is detected by the communication failure detecting mechanism 304 during automatic cyclic communication and the failure cannot be repaired by the communication failure repair mechanism 306 or the like. Notify the user of the content. At this time, if the fault repair guide data having the same fault code as the fault occurred exists in the fault repair guide database 33 using the fault data 35a, the fault guide information held by the fault repair guide data is stored. indicate. Thereafter, the fault code is deleted from the fault data 35a.

The failure repair guide database 33 stores failure repair guide data.

When the automatic patrol mechanism 303 receives the failure repair guide data transmitted from the server device 2 of the present invention, the failure repair guide DB updating mechanism 301 uses the failure repair guide data to generate the failure repair guide data. Update the database 33.

The traveling data update mechanism 302 stores the traveling data received during the automatic traveling communication in the traveling data database 31.

The traveling data database 31 stores the traveling data received during the automatic traveling communication.

Upon receiving a user's automatic patrol request, the automatic patrol mechanism 303 executes automatic patrol communication in the order of the patrol ID specified by the patrol setting system data 34a, and operates the patrol data updating mechanism 302 to store the received data. call. At this time, when the failure repair data transmitted from the server device 2 of the present invention is received, the failure repair DB update mechanism 305 is called to store the data.
When the failure repair guide data transmitted from the server device 2 of the present invention is received, the failure repair guide DB update mechanism 301 is called to store the data.

Further, if there is the failure repair update data 37a created when the system is repaired, the automatic patrol mechanism 303 deletes the failure repair update data 37a by transmitting it to the server device 2 of the present invention. If there is unrecovered failure data 36a created when the system has not been recovered, it is transmitted to the server device 2 of the present invention and then deleted. Then, if the system has not been recovered, after the end of the automatic cyclic communication, the communication failure notification mechanism 300 is called by specifying the generated failure data 35a.

When a communication failure occurs in the communication processing executed by the automatic traversing mechanism 303, the communication failure detection mechanism 304 detects the communication failure and specifies a failure code corresponding to the communication failure. In order to execute the restoration, the communication failure restoration mechanism 306 is called by designating the failure code and the information (target system information) indicated by the traveling ID in which the failure has occurred.

When the automatic patrol mechanism 303 receives the failure repair data from the server device 2 of the present invention, the failure repair DB updating mechanism 305 updates the failure repair database 32 using the failure repair data.

The failure repair database 32 stores failure repair data.

When a communication failure is detected by the communication failure detection mechanism 304, the communication failure recovery mechanism 306 checks the failure code and the target system information of the failure recovery data managed by the failure recovery database 32. 304
The target system checks whether there is a record including the fault code passed from the client and the target system includes the corresponding client.
If it exists in the record, the fault code / code is used to construct a temporary system using the information stored in the record.
The temporary system construction module 309 is called for the number of records by designating the information of the tour ID / failure repair ID.

At this time, the communication failure repair mechanism 306 is considered to have a higher possibility of restoring the system as the updated system (the number of times the failure repair data has been applied) is more frequently applied to the system. The temporary system construction mechanism 309 will be called in the order of records having the largest number of applications.

Further, the communication failure repair mechanism 306 failed to recover from the failure even when all the temporary systems to be constructed were constructed, or the record having the corresponding failure code did not exist in the failure repair database 32. In this case, the non-recovery countermeasure mechanism 308 is called by designating the corresponding fault code / tour ID information.

The temporary system deletion mechanism 307 deletes the temporary system constructed by the temporary system construction mechanism 309.

The occurrence failure data 35a records information indicating what kind of failure has occurred during communication.

The unrecovery countermeasure mechanism 308 adds the current fault code to the fault data 35a when the fault data 35a exists, and uses the current fault code when the fault data 35a does not exist. The data 35a is created. Further, the non-recovery countermeasure mechanism 308
Acquires the client environment information and creates the unrecovered failure data 36a using the acquired client environment information and the corresponding failure code information. Thereafter, by returning the control to the automatic tour mechanism 303, the control is performed so that the continuation of the automatic tour communication is executed from the next tour ID of the current tour ID.

The temporary system construction mechanism 309 constructs a temporary system for the communication test using the information of the updated system stored in the failure repair data stored in the failure repair database 32. After that, the fault code / tour ID / fault repair I
The test communication mechanism 310 is called by designating the information of D.

In the unrecovered failure data 36a, a failure code that has not been recovered and client environment information at that time are recorded.

The test communication mechanism 310 uses the temporary system constructed by the temporary system construction mechanism 309 to perform a test as to whether a communication failure can be avoided.

The test communication failure detection mechanism 311 checks whether or not a failure has occurred in the communication processing executed by the test communication mechanism 310. If no failure has occurred, the failure code / circulation ID / The system update mechanism 312 is called by designating the information of the failure repair ID, and when a failure occurs, the temporary system erase mechanism 307 is called.

The failure repair update data 37a records failure repair ID information of the repair data that has been successfully repaired.

In order to apply the temporary system constructed by the temporary system construction mechanism 309 to the present system, the system updating mechanism 312 replaces the corresponding traveling ID portion of the traveling setting system data 34a with the failure repair data which has been successfully repaired. Update using the system information of.

Further, using the fault repair ID information of the fault repair data that has been successfully repaired, the fault repair update data 37a is used.
Create Then, the cyclic data database 31 is updated using the cyclic data received by the test communication mechanism 310. Thereafter, by returning the control to the automatic tour mechanism 303, the control is performed so that the continuation of the automatic tour communication is executed from the next tour ID of the current tour ID.

Next, the device configuration of the server device 2 of the present invention will be described in detail with reference to FIG.

In FIG. 16, reference numeral 400 denotes an unrecovered failure data storage mechanism, 41 denotes an unrecovered failure database, 401 denotes a failure analysis and resolution mechanism, 402 denotes a communication mechanism, 403 denotes a failure recovery guide DB addition / update mechanism, and 404 denotes a failure recovery. DB addition / updating mechanism, 405 is a failure repair guide data acquisition mechanism, 43 is a failure repair guide database, 406 is a failure repair DB
An update mechanism, 407 is a failure repair data acquisition mechanism, and 42 is a failure repair database.

The unrecovered failure data storage mechanism 400 stores the unrecovered failure data transmitted from the client device 1 in the unrecovered failure database 41.

The unrecovered failure database 41 stores the unrecovered failure data transmitted from the client device 1.

The failure analysis / resolution mechanism 401 acquires the unrecovered failure data stored in the unrecovered failure database 41, analyzes the contents of the failure from the information on the unrecovered failure data, and automatically identifies the failure. When there is a method of repairing the error, the failure repair DB addition / update mechanism 404 is called to store the solution in the failure repair database 42, and the corresponding unrecovered failure data is deleted from the unrecovered failure database 41.

If there is no automatic repair method, but there is information that is a hint for the repair, a failure repair guide DB addition / update mechanism is required to store the hint information in the failure repair guide database 43. 40
3 is deleted, and the corresponding unrecovered failure data is deleted from the unrecovered failure database 41. On the other hand, when there is no automatic restoration method and when there is no hint information, deletion of unrecovered failure data is not executed.

The communication mechanism 402 calls the failure repair DB update mechanism 406 when the failure repair update data is transmitted from the client device 1, and calls the unrecovered failure data from the client device 1 when the failure repair update data is transmitted from the client device 1. , The unrecovered failure data storage mechanism 400 is called. Then, when there is a request for transmission of the failure repair data / failure repair guide data from the client device 1, the failure repair guide data acquisition mechanism 405 / failure repair data acquisition mechanism 407 is called, and if there is data to be transmitted, these are transmitted to the client device. Send to 1.

Failure recovery guide DB addition / update mechanism 403
Although there is no method for automatically restoring the unrecovered failure data stored in the unrecovered failure database 41, if there is information to be used as a hint for repair, the information to be used as a hint is provided by the failure repair guide. -In the database 43,
Store in the form of failure repair guide data.

The failure repair DB addition / update mechanism 404 sends a solution to the unrecovered failure data stored in the unrecovered failure database 41 to the failure repair database 42.
Store in the form of failure repair data.

The failure repair guide data acquisition mechanism 405
Failure repair guide database 3 for client device 1
In the case where data newer than the data stored in No. 3 is stored in the failure repair guide database 43,
The data of the new difference is acquired, and it is transmitted to the communication mechanism 4
Hand over to 02.

[0120] The failure repair guide database 43 stores failure repair guide data.

When the failure repair update data is transmitted from the client device 1, the failure repair DB update mechanism 406 has a failure repair ID having the same failure repair ID as that of the transmitted failure repair update data. One is added to the information on the number of times of application of the failure repair data stored in the database 42.

The failure repair data acquisition mechanism 407 acquires new difference data when newer data than the data stored in the failure repair database 32 of the client device 1 is stored in the failure repair database 42. And passes it to the communication mechanism 402.

The present invention has been described with reference to the illustrated embodiments.
The present invention is not limited to this. For example, in the embodiments, the present invention has been described by taking a specific example of application to a system that executes traveling data acquisition. However, the present invention is not limited to a system that executes traveling data acquisition. Further, in the embodiment, a communication failure is assumed as a failure that occurs, but the present invention is not limited to the application of the communication failure.

[0124]

As described above, according to the present invention, when a failure occurs, a system repair module for automatically repairing the failure from the content of the failure is temporarily applied,
It is possible to provide a mechanism for reflecting only modules that have no problems after executing a test in the system to which the provisional application has been applied to the actual system.

From now on, to date, it has been very difficult due to time and distance constraints. Failure repair and test for all failed clients are performed only when there is no problem in the test results. It is possible to take a work process that is considered to be the most important at the time of repairing a fault, such as a system repair, so that a more reliable repair of a fault can be performed.

As a result, the reliability of the system is improved. Further, when a temporary system is constructed in the system restoration, a mechanism for constructing the temporary system in a descending order of the possibility of restoring the system is provided, so that the speed of restoration can be improved.

Further, since the present invention operates only when a failure occurs, the system is erroneously updated for a system that is operating stably, which causes a factor of failure on the contrary. Nothing like that happens.

Further, according to the present invention, when a failure occurs, a failure repair suitable for the client is automatically executed for each client, so that the user is not notified of the failure more than necessary. From this, it becomes possible to give the user a sense of security as a reliable system that is hard to break.

Further, according to the present invention, even when a failure cannot be automatically repaired, the user can be provided with information for repairing the failure, so that the user can self-solve the failure by using this information. The possibilities expand,
As a result, it is possible to reduce the number of support operations.

[Brief description of the drawings]

FIG. 1 is a principle configuration diagram of the present invention.

FIG. 2 is an embodiment of the present invention.

FIG. 3 is an example of a failure repair database.

FIG. 4 is an example of a failure repair guide database.

FIG. 5 is an explanatory diagram of tour setting system data.

FIG. 6 is a processing flow of a client processing mechanism.

FIG. 7 is a processing flow of a client processing mechanism.

FIG. 8 is a processing flow of a client processing mechanism.

FIG. 9 is a processing flow of a client processing mechanism.

FIG. 10 is a processing flow of a server processing mechanism.

FIG. 11 is a processing flow of a server processing mechanism.

FIG. 12 is an example of occurrence failure data.

FIG. 13 is an example of unrecovered failure data.

FIG. 14 is an example of failure repair update data.

FIG. 15 is a device configuration diagram of a client device.

FIG. 16 is a device configuration diagram of a server device.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Client apparatus 2 Server apparatus 10 1st database means 11 1st update means 12 2nd database means 13 2nd update means 14 Failure detection means 15 Recovery means 16 Notification means 17 Output means 20 Acquisition means 21 First Database means 22 Creation means 23 Second database means 24 Third database means 25 Transmission means

Claims (9)

[Claims] 1. A database means for managing system change information for repairing a fault in association with a fault code and system information to which the system change information is applied, and connected via a network. An update unit that updates information managed by the database unit by receiving and registering information registered in the database unit from a server device, and a system change information managed by the database unit when a failure occurs. Recovery means for constructing a temporary system and restoring the system by trying to restore the system in accordance therewith; notification means for notifying the server device of a code of a failure in which the system cannot be recovered and system information at the time of the failure; A device having a failure repair function. 2. An apparatus having a fault repair function according to claim 1, wherein said second database means manages guide information for repairing the fault in association with the fault code, and is connected via a network. Second update means for updating information managed by the second database means by receiving and registering information to be registered in the second database means from the server device, and managing the second database means. According to the information
An output unit that obtains and outputs the guide information for restoring a failure in which the system cannot be recovered by the processing by the recovery unit, and that has a failure recovery function. 3. An apparatus having a failure repair function according to claim 1, wherein said database means operates according to information from the server apparatus.
Failure management characterized by managing information on the number of times used for system recovery for each piece of management information, and attempting recovery of the system while selecting system change information according to the order of the number of times information. A device with functions. 4. An acquisition means for acquiring, from a plurality of support target devices connected via a network, a code of a failure in which the system could not be recovered and system information at the time of the failure, Creating means for creating system change information for repairing the failure and system information to which the system change information is applied in association with the failure code acquired by the acquiring means; and information created by the creating means. And a transmission unit for transmitting a message to the support target device, wherein the server device supports a device having a failure repair function. 5. A server device for supporting a device having a fault repair function according to claim 4, wherein the creating means creates guide information for repairing the fault in association with the fault code acquired by the acquiring means. And a transmitting unit that transmits the guide information created by the creating unit to the support target device, the server device supporting a device having a failure repair function. 6. A server device for supporting a device having a failure repair function according to claim 4 or 5, wherein the acquisition means uses any one of the system change information created by the creation means from the support target apparatus. The transmission means supports the device having the failure repair function characterized by acquiring information on whether or not the device has been restored, counting the information, and transmitting the count value counted by the acquisition device to the support target device. Server device. 7. A system comprising a server device and a client device connected via a network, wherein the client device associates with a failure code, and system change information for repairing the failure, and the system Database means for managing system information to which the change information is to be applied; update means for updating information managed by the database means by receiving and registering information registered in the database means from a server device; When a problem occurs, a temporary system is constructed based on the system change information managed by the database means, and the system is restored by trying to restore the system accordingly. And notifies the server device of the system information at the time of the failure On the other hand, the server device obtains, from the client device, a code of a failure in which the system could not be recovered and system information at the time of the failure. Creating means for creating system change information for repairing the failure and system information to which the system change information is to be applied in association with the obtained failure code; And a transmission means for transmitting the data to the system. 8. An access process for accessing database means for managing system change information for repairing the fault and system information to which the system change information is applied in association with the fault code, and An update process for updating information managed by the database means by receiving and registering information to be registered in the database means from a server device connected via the server, and managing the database means when a failure occurs. The above-described server device is used to construct a temporary system based on the system change information and restore the system by attempting to restore the system in accordance with the system change information, a failure code for which the system cannot be restored, and the system information at the time of the failure. Stores a program that causes the computer to execute the notification process that notifies the A program recording medium characterized by being performed. 9. A method according to claim 1, further comprising: acquiring from a plurality of support target devices connected via a network, a failure code for which the system cannot be restored and system information at the time of the failure; Creation processing for creating system change information for repairing the failure and system information to which the system change information is applied in association with the failure code acquired by the acquisition processing; and information created by the creation processing. A program for causing a computer to execute a transmission process of transmitting the information to the support target device.