JP5647597B2 - Maintenance management system and client terminal - Google Patents

Description

  The present invention relates to a maintenance management system, a server, and a client terminal that maintain a terminal connected to a network.

  As a system for remotely controlling and maintaining a large number of terminals connected to a network, for example, Patent Document 1 is known. Patent Document 1 describes a remote control system that can remotely operate various types of controlled devices of different manufacturers and models using a terminal equipped with browsing software such as an existing WWW browser. Has been.

JP 2003-143665 A

  In conventional maintenance systems, when multiple operators perform maintenance operations simultaneously, after one operator performs maintenance operations on a certain terminal, another operator performs another maintenance operation on the same terminal. As a result, there is a problem that the maintenance operation intended by the former operator cannot be performed. That is, when another operator performs another operation, the series of maintenance operations originally intended by the first operator is interrupted, and the series of maintenance operations of the first operator cannot be started or completed.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to perform maintenance on a certain terminal when a plurality of operators perform maintenance. It is an object of the present invention to provide a maintenance management system, a server, and a client terminal that can eliminate maintenance operations by the operator.

In order to achieve the above object, the present invention is a maintenance management system in which a server and a client terminal cooperate to manage a maintenance state, and the server receives an input from an operator and determines whether an operation is possible. And maintenance status management means for managing maintenance status information of the client terminal. The maintenance status information includes a maintenance identifier assigned for each maintenance, an operator ID, and a client terminal ID to be maintained. , The maintenance end scheduled time , the operation availability determination means refers to the maintenance status information, and the operation content by the operator based on the operator ID, client terminal ID, and operation content input from the operator When the maintenance status management unit determines that maintenance is possible, the maintenance status management unit determines whether maintenance is possible. To, to notify that it is possible to operate, the maintenance monitor each maintenance scheduled end time of the status information, maintenance continuation judging means for notifying the completion of maintenance on the client terminal maintenance scheduled end date has passed the current time When the maintenance continuation determination unit receives a maintenance state acquisition request from the client terminal, the maintenance continuation determination unit compares the request time at which the acquisition request is received with the scheduled maintenance end time, and the request time is the scheduled maintenance end time. In the earlier case, the client terminal is notified that the maintenance is in progress, and the client terminal holds the next maintenance status acquisition scheduled date and time, and maintains the maintenance status in the server based on the next maintenance status acquisition scheduled date and time. Maintenance status acquisition means for requesting maintenance status management means for determining whether maintenance can be continued based on the maintenance status acquired by the maintenance status acquisition means And when the maintenance status management means determines that maintenance cannot be continued, the maintenance status execution means for ending maintenance is received. When receiving a notification that maintenance operation is possible from the server, the maintenance status The acquisition means extends the held next maintenance status acquisition scheduled date and time for a certain period .

The present invention is a client terminal in a maintenance management system in which a server and a client terminal cooperate to manage a maintenance state, and holds a next maintenance status acquisition scheduled date and time, and stores the next maintenance status acquisition scheduled date and time in the server. Maintenance status acquisition means for requesting a maintenance status, maintenance status management means for determining whether maintenance can be continued based on the maintenance status acquired by the maintenance status acquisition means, and the maintenance status management means determined that maintenance cannot be continued If, possess a maintenance termination execution means for executing a termination of the maintenance, when receiving a notification from the server is capable of maintenance operation, the maintenance status obtaining means, the next maintenance status acquisition plan the retained Extend the date and time for a certain period .

  According to the present invention, when a plurality of operators perform maintenance, after a certain operator starts maintenance on a certain terminal, the maintenance management system, server, and A client terminal can be provided.

1 is an overall configuration diagram of a maintenance management system according to an embodiment of the present invention. It is a figure which shows an example of maintenance status management DB. It is a figure which shows an example of maintenance setting management DB. It is a figure which shows an example of maintenance status acquisition DB. It is a flowchart of a maintenance start process. It is a flowchart of an operation availability determination process. It is a flowchart of an individual maintenance operation process. It is a flowchart of a maintenance end process. It is a flowchart of the automatic maintenance end process by a server. It is a flowchart of the automatic maintenance end process by a terminal. It is a flowchart of the reset process by a terminal.

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

  FIG. 1 is an overall configuration diagram of a maintenance management system according to an embodiment of the present invention. The maintenance management system of this embodiment includes a server 1 and a plurality of terminals 2 connected to the server 1 via a network 3 such as the Internet. In the maintenance management system of the present embodiment, the server 1 and each terminal 2 cooperate with each other, and a plurality of operators perform remote maintenance of the plurality of terminals 2 over a certain period.

  The illustrated server 1 includes an operation availability determination unit 11, a maintenance continuation determination unit 12, a maintenance status management unit 13, a maintenance setting management unit 14, and a communication unit 15. The operation availability determination unit 11 determines whether or not these operations can be performed when performing an operation for starting maintenance of the terminal 2, an operation for ending maintenance, and individual maintenance operations.

  When the maintenance of the terminal 2 is started, the maintenance status management unit 13 issues operator information for performing a maintenance start operation, customer information, terminal information, maintenance start date and time, scheduled maintenance end date and time, and server 1 The maintenance identifier is stored in the maintenance status management DB 131 of the maintenance status management unit 13, and the associated information is deleted from the maintenance status management DB 131 when the maintenance is finished. FIG. 2 is a diagram illustrating an example of the maintenance status management DB 131.

  The maintenance continuation determination unit 12 determines whether or not to continue the maintenance based on each scheduled maintenance end date and time of the maintenance status management DB 131, and extends the scheduled maintenance end date and time when there is an individual maintenance operation. Further, the maintenance continuation determination unit 12 transmits an instruction for ending maintenance to the terminal 2.

  The maintenance setting management unit 14 associates the setting contents of the individual maintenance operations performed on the terminal 2 with the maintenance identifier, and holds them in the maintenance setting management DB 141 provided in the maintenance setting management unit 14. FIG. 3 is a diagram illustrating an example of the maintenance setting management DB 141. The communication unit 15 communicates with the terminal 2.

  The terminal 2 of this embodiment includes a communication unit 21, a maintenance end execution unit 22, a maintenance status acquisition unit 23, and a maintenance setting acquisition unit 24. The communication unit 21 communicates with the server 1. The maintenance status acquisition unit 23 holds the maintenance identifier notified from the server 1, the maintenance start date and time, and the next maintenance status acquisition scheduled date and time in the maintenance status acquisition DB 231 and makes an inquiry about the maintenance status to the server 1. Thus, it is determined whether or not the maintenance is continued. FIG. 4 is a diagram illustrating an example of the maintenance status acquisition DB 231.

  The maintenance end execution unit 22 returns the setting contents by the maintenance operation performed on the terminal 2 to the state before the maintenance start. The maintenance setting acquisition unit 24 designates a maintenance identifier and performs maintenance operation from the server 1 as needed (for example, when the terminal 2 takes over maintenance settings when the terminal 2 is restarted or when an operator's instruction is accepted). Get the settings.

  In the terminal 2 shown in the figure, the functions of the communication unit 21, the maintenance end execution unit 22, the maintenance status acquisition unit 23, and the maintenance setting acquisition unit 24 are realized by an agent (a program operating on the terminal) that communicates with the server 1. Shall.

  The server 1 and the terminal 2 can use, for example, a general-purpose computer system including a CPU, a memory, an external storage device such as an HDD, an input device, and an output device. In this computer system, each function of each device is realized by the CPU executing a predetermined program loaded on the memory. For example, the functions of the server 1 and the terminal 2 are executed by the CPU of the server 1 in the case of the program for the server 1 and the CPU of the terminal 2 in the case of the program (agent) for the terminal 2, respectively. Realized.

  Further, the program for the server 1 and the program for the terminal 2 can be stored in a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, a DVD-ROM, or distributed via a network. You can also.

  Next, the operation of this embodiment will be described.

  First, the “maintenance start process” will be described. In the present embodiment, the maintenance state of the terminal is managed in cooperation with the server and the terminal by explicitly performing the maintenance start operation by the operator before performing the individual maintenance operation on the terminal.

  FIG. 5 is a flowchart showing the maintenance start process.

  First, the server operation determination unit 11 receives a maintenance start instruction input by the operator (S11). That is, the operator inputs maintenance start instructions including target customer information, terminal information, operation details (maintenance start), and operator information to be operated at the time of maintenance start operation. When receiving the maintenance start instruction, the operation availability determination unit 11 determines whether the maintenance start can be performed according to the determination process shown in FIG. 6 (S12).

  FIG. 6 is a flowchart showing the determination process of S12.

  First, the operation availability determination unit 11 determines whether or not the terminal of the terminal information received in S11 is under maintenance (S21). That is, the terminal information is registered in the operation status management DB 131 in association with the maintenance identifier, and it is determined whether or not the terminal is in a maintenance state where maintenance has already started. If the terminal is not in the maintenance state (S21: NO), and the operation content accepted in S11 is the start of maintenance (S22: YES), the operation availability determination unit 11 determines that the maintenance can be started (S25). ).

  On the other hand, when the terminal is in the maintenance state (S21: YES) and when the operation content received in S11 is other than the maintenance start (S22: NO), the operation availability determination unit 11 determines that the maintenance start is impossible. (S26, S27, S28), the subsequent processing is stopped.

  By performing the determination processing shown in FIG. 6, it is possible to prevent the maintenance from being performed repeatedly for a terminal that is already in the maintenance state.

  In addition to the determination shown in FIG. 6, other terminal information associated with the same customer information in order to maintain only one operator to maintain one customer for the customer information received in S11. It may be determined whether or not maintenance has already started and is registered in the maintenance status management DB 131. If other terminal information associated with the same customer information has already started maintenance, and the operator information registered in the maintenance status management DB 131 is different from the operator information received in S11, the maintenance operation is disabled. As a result, when a plurality of terminals are installed in one customer, it is possible to improve the service to the customer by limiting the number of operators corresponding to maintenance to one.

  If the maintenance can be started (FIG. 6: S25), the process returns to FIG. 5 and the maintenance status management unit 13 pays out a maintenance identifier unique to the server (S13). Then, the maintenance status management unit 13 registers the maintenance status information including the issued maintenance identifier in the maintenance status management DB 131 (S14). Specifically, the operator information, the customer information, the terminal information, the maintenance start date and time (the time when the maintenance start instruction in S11 was accepted), and the scheduled maintenance end date and time are associated with the maintenance identifier. Register in the maintenance status management DB 131.

  The scheduled maintenance end date and time is a date and time set based on the maintenance start date and time, and is a date and time after a certain period from the information maintenance start date and time. In the example of the maintenance status management DB 131 shown in FIG. 2, the scheduled maintenance end date is 3 days after the maintenance start date. In the present embodiment, the scheduled maintenance end date and time is described as a certain period after the maintenance start date and time. However, when the operator inputs a maintenance start instruction, the scheduled maintenance end date and time may be specified.

  Then, using the communication unit 15, the maintenance status management unit 13 transmits the maintenance identifier registered in S14 to the agent operating on the terminal designated by the operator, and notifies the start of maintenance (S15). The communication unit 15 uniquely identifies the destination terminal using the terminal information set in the maintenance status management unit DB 131. In the specific example shown in FIG. 2, an IPv6 address is used for terminal information. However, the terminal information is not limited to an IPv6 address, and for example, an IPv4 address may be used.

  The communication unit 21 of the terminal (agent) receives the maintenance identifier from the server and grasps that the maintenance has started (S16).

  Then, the maintenance status acquisition unit 23 registers the maintenance identifier received in S16, the maintenance start date and time that is the current time, and the next maintenance status acquisition scheduled date and time in the maintenance status acquisition unit DB 231 (S17). The next maintenance status acquisition scheduled date and time is a scheduled date and time for acquiring the next maintenance status set based on the maintenance start date and time, and is a date and time after a certain period from the maintenance start date and time. In the example of the maintenance status acquisition DB 231 shown in FIG. 4, the next maintenance status acquisition scheduled date and time is 3 hours after the maintenance start date and time. In the present embodiment, the next maintenance status acquisition scheduled date and time will be described as a certain period after the maintenance start date and time. However, the next maintenance status acquisition scheduled date and time is calculated by the server maintenance status management unit 13 and sent from the server to the terminal. It is good also as transmitting. Further, instead of an explicit next maintenance status acquisition scheduled date and time, it may be an acquisition scheduled interval (for example, “3 hours later”).

  Next, “individual maintenance operation processing” will be described.

  In this embodiment, when an individual maintenance operation is performed by an operator who has started maintenance, the server retains the settings made by the individual maintenance operation and the scheduled maintenance end date and time registered when the maintenance is started To be extended.

  FIG. 7 is a flowchart showing individual maintenance operation processing.

  The operation availability determination unit 11 receives target terminal information, individual operation details, setting details associated with the operation details, and operator information to be operated, which are designated by the operator during individual maintenance operations (S31). Then, the operation availability determination unit 11 determines whether or not an individual maintenance operation can be performed according to the determination process illustrated in FIG. 6 (S32).

  In FIG. 6, the operation availability determination unit 11 determines whether or not the terminal of the terminal information received in S31 is under maintenance (S21). That is, the terminal information is registered in the operation status management DB 131 in association with the maintenance identifier, and it is determined whether or not the terminal is in a maintenance state where maintenance has already started. When the terminal is in a maintenance state (S21: YES) and the operation content received in S31 is other than the start of maintenance (S23: NO), the operation availability determination unit 11 indicates that the operator information received in S31 indicates the operation status. It is determined whether or not it matches the operator information registered in association with the terminal information in the management DB 131 (S24). When the operator information matches (S24: YES), the operation availability determination unit 11 determines that the individual maintenance operation received in S31 can be performed (S27).

  On the other hand, if it is not in the maintenance state (S21: NO) and the operation content accepted in S31 is not the start of maintenance (S22: NO), it is in the maintenance state (S21: YES), and the operation content accepted in S31 is maintenance. In the case of start (S23: YES) and when the operator information does not match (S24: NO), the operation availability determination unit 11 determines that the individual maintenance operation cannot be performed (S26, S28), and thereafter. Cancel the process.

  In the case of a terminal that is not in the maintenance state, when the operation content for the terminal in the maintenance state is maintenance start, and in the case of individual maintenance operations from an operator other than the operator who executed the maintenance start, the determination process shown in FIG. You can make it impossible.

  Note that the maintenance operation of an operator other than the operator who started the maintenance may be performed by changing the operator information registered in the server operation status management DB 131 that has started the maintenance. As a specific operator information change process, the maintenance status management unit 13 receives an operator information change instruction including a maintenance identifier, terminal information, and operator information to be changed, input by the operator. The maintenance status management unit 13 refers to the maintenance status management DB 131 and updates the operator information registered in association with the received maintenance identifier to the received operator information. As a result, operators other than the operator who started the maintenance can be made to perform individual maintenance operations on the terminal.

  If it is determined that an individual maintenance operation can be performed (FIG. 6: S27), the process returns to FIG. 7, and the maintenance status management unit 13 acquires the maintenance identifier associated with the terminal information and operator information received in S31. (S33).

  Then, the maintenance setting management unit 14 extends the scheduled maintenance end date and time registered in the maintenance status management DB 131 in association with the maintenance identifier acquired in S33 by a predetermined period (S34). The extension of the period is to add a predetermined period to the scheduled maintenance end date and time registered at that time, and to set the addition result as a new scheduled maintenance end date and time. Note that the extended period may be different depending on the operation content and the type of terminal. In this case, it is assumed that the maintenance setting management unit 14 includes an extension period table in which different extension periods are set for each operation content and terminal type.

  The maintenance setting management unit 14 registers, in the maintenance setting management DB 141, the individual operation contents received in S31, the setting contents accompanying the operation contents, and the necessity of resetting in association with the maintenance identifier acquired in S33 (S35). . Regarding the necessity of resetting, the maintenance setting management unit 14 holds “required” or “not required” corresponding to each operation content, and registers based on it. Note that whether or not resetting is necessary may be individually specified when the operator requests an individual maintenance operation in S31.

  In the example of the maintenance setting management DB 141 shown in FIG. 3, the operation contents and setting contents are the operation contents (log setting) for executing log output, and the log output target is the OS and application 2 to be output logs. The settings for ERROR and DEBUG are described. In addition, an operation content and a setting content for temporarily stopping the application 1 are described. Further, regarding the necessity of resetting, resetting is required only when the operation content is log setting. The operation content and the setting content are not limited to the example shown in FIG. 3, but are defined according to individual maintenance operations.

  Then, the maintenance status management unit 13 or the maintenance setting management unit 14 can use the communication unit 15 to perform individual maintenance operations on the agent operating on the terminal designated by the operator, that is, the maintenance identifier and the operation content. , Send the setting contents accompanying the operation contents. (S36).

  The communication unit 21 of the terminal (agent) receives the maintenance identifier, the individual operation content, and the setting content associated with the operation content from the server (S37). The maintenance setting acquisition unit 24 stores the maintenance identifier, the individual operation content, and the setting content associated with the operation content in a storage unit (not shown) included in the maintenance setting acquisition unit 24 according to the individual operation content and the setting content. (Register or update) (S38). Further, the maintenance status acquisition unit 23 may extend the next maintenance status acquisition scheduled date and time of the maintenance status acquisition DB 231 for a certain period.

  In addition, in order to be able to exclude unauthorized access, when the server address is stored in advance in the communication unit 21 in S37 and the exclusion process is enabled, the stored server address and the source address are stored. May be received only when they are the same. The communication unit 21 may determine whether or not the maintenance identifier received from the server is the same as the maintenance identifier held in the maintenance status acquisition DB 231 and may receive the same only.

  Next, “maintenance end processing” will be described.

  In this embodiment, after an individual maintenance operation is performed on the terminal, the maintenance end operation is explicitly performed by the operator, so that the server and the terminal cooperate to return to the original state before the terminal is maintained. .

  FIG. 8 is a flowchart showing the maintenance end process.

  The server operation propriety determination unit 11 receives target terminal information, operation details (maintenance end), and operator information to be operated, which the operator designates at the time of maintenance end operation (S41).

  Then, the operation availability determination unit 11 determines whether the maintenance end can be performed according to the determination process shown in FIG. 6 (S42).

  In FIG. 6, the operation availability determination unit 11 determines whether the terminal of the terminal information received in S41 is under maintenance (S21). That is, the terminal information is registered in the operation status management DB 131 in association with the maintenance identifier, and it is determined whether or not the terminal is in a maintenance state where maintenance has already started. When the terminal is in a maintenance state (S21: YES) and the operation content received in S41 is other than the start of maintenance (S23: NO), the operation availability determination unit 11 indicates that the operator information received in S41 indicates the operation status. It is determined whether or not it matches the operator information registered in association with the terminal information in the management DB 131 (S24). When the operator information matches (S24: YES), the operation availability determination unit 11 determines that the maintenance can be completed (S27).

  On the other hand, if it is not in the maintenance state (S21: NO) and the operation content accepted in S41 is not the start of maintenance (S22: NO), it is in the maintenance state (S21: YES), and the operation content accepted in S41 is the maintenance. When the operation is started (S23: YES) and when the operator information does not match (S24: NO), the operation availability determination unit 11 determines that the maintenance cannot be completed (S26, S28), and the subsequent processing is performed. Discontinue.

  By such a determination process shown in FIG. 6, in the case of a terminal that is not in a maintenance state, when the operation content for the terminal in the maintenance state is maintenance start, and from an operator other than the operator who performed maintenance start or individual maintenance operation In the case of a maintenance end operation, it can be disabled.

  If it is determined that the maintenance can be completed (FIG. 6: S27), the process returns to FIG. 8, and the maintenance status management unit 13 acquires the maintenance identifier associated with the terminal information and operator information received in S41 (S43). ). Then, the maintenance status management unit 13 deletes the maintenance status information (record) registered in association with the acquired maintenance identifier from the maintenance status management DB 131 (S44). Then, the maintenance setting management unit 14 deletes the maintenance setting information (record) registered in association with the acquired maintenance identifier from the maintenance setting management unit DB 141 (S45).

  Then, the maintenance status management unit 13 or the maintenance setting management unit 14 uses the communication unit 15 to include an operation that can be performed on the agent operating on the terminal designated by the operator, that is, the maintenance identifier acquired in S43. A maintenance end notification is transmitted (S46).

  The communication unit 21 of the terminal (agent) receives a maintenance end notification including a maintenance identifier from the server (S47). Then, the maintenance status acquisition unit 23 deletes the maintenance status information registered in association with the received maintenance identifier from the maintenance status management DB 231 (S48).

  Then, the maintenance end execution unit 22 performs a maintenance end process (for example, returns the setting contents to default settings) (S49). The default setting is the setting information stored in the non-volatile storage area of the terminal (the storage area that can retain the stored contents even when the power is turned off). In this case, the default setting is used before starting maintenance. Set to information.

  Next, automatic maintenance end processing by the server will be described. In the present embodiment, even when the above-described explicit maintenance end operation (see FIG. 8) is not performed by the operator, the server ends the maintenance and returns the terminal to the original state before the maintenance start.

  FIG. 9 is a flowchart for explaining automatic maintenance end processing by the server. The maintenance continuation determination unit 12 monitors and checks each scheduled maintenance end date and time registered in the maintenance status management DB 131 at a predetermined timing, and when the scheduled maintenance end date and time has passed the current time (YES in S51). Then, it is determined that maintenance cannot be continued for a terminal whose maintenance end scheduled date and time has passed the current time, and processing for automatically ending maintenance is performed. Note that the specific contents at the end of the maintenance are the same as the processes from S43 to S49 in the maintenance end operation of FIG.

  Next, automatic maintenance end processing by the terminal will be described. In the present embodiment, even when the maintenance end notification from the server to the terminal does not arrive for some reason, the maintenance end is automatically performed, and the terminal is returned to the original state before the start of maintenance.

  FIG. 10 is a flowchart for explaining automatic maintenance end processing by the terminal.

  When the next maintenance status acquisition scheduled date and time held in the maintenance status acquisition DB 231 has arrived (before the current time) (S61: YES), the maintenance status acquisition unit 23 uses the communication unit 21 to Is notified of the maintenance identifier, and the acquisition of the maintenance status is requested. When the maintenance status acquisition unit 23 succeeds in acquiring the maintenance status from the server (S62: YES) and the maintenance status is under maintenance (S63: YES), the maintenance status acquisition unit 23 determines that the maintenance can be continued, and the maintenance status acquisition DB 231. The next maintenance status acquisition scheduled date and time is extended by a predetermined period and updated.

  When the maintenance status management unit 13 of the server receives a maintenance status acquisition request from the terminal, the maintenance status management unit 13 refers to the maintenance status management DB 131 and ends the maintenance of the notified maintenance identifier notified of the request time (current time) when the acquisition request was received. When the requested time is before the scheduled maintenance end time, the maintenance status during maintenance is transmitted to the terminal using the communication unit 15. When the requested time is after the scheduled maintenance end time or when the notified maintenance identifier information does not exist, the maintenance status of the maintenance end is transmitted to the terminal using the communication unit 15.

  When the terminal requests acquisition of the maintenance state without specifying the maintenance identifier, the maintenance setting management unit 14 may determine the target terminal based on the address of the terminal that is the access source. In other words, the maintenance setting management unit 14 may search for a terminal whose access source address matches the terminal information held in the maintenance status management DB 131 and determine the maintenance state.

  Note that the next maintenance status acquisition scheduled date and time may be set by the maintenance status management unit 13 of the server and transmitted from the server together with the response of the maintenance status. By setting the next maintenance status acquisition scheduled date and time on the server, it is possible to consider the number of terminals being maintained and the load status of the server, so that access to the servers can be distributed. Further, it may be a scheduled acquisition interval instead of a specific date and time of the next maintenance status acquisition scheduled date and time.

  On the other hand, when the response from the server is not under maintenance (S63: NO), or when the maintenance status from the server cannot be acquired due to the occurrence of a network problem between the server and the terminal (the maintenance status acquisition request is Retry may be performed a predetermined number of times) (S62: NO), the maintenance end execution unit 22 determines that maintenance cannot be continued, and executes the maintenance end. Since the specific processing content at the end of the maintenance is the same as the processing from S48 to S49 in the maintenance end operation of FIG. 8, the description is omitted here.

  Next, processing for resetting the setting contents of individual maintenance operations on the terminal will be described. In the present embodiment, the setting content by the individual maintenance operation performed on the terminal is held by the server and reset on the terminal 2.

  FIG. 11 is a flowchart showing resetting processing at the terminal.

  The maintenance status acquisition unit 23 of the terminal stores the maintenance identifier received from the server in the nonvolatile area in S16 in the maintenance start operation of FIG. When the agent is activated due to the restart of the terminal or the like, the maintenance setting acquisition unit 24 checks the non-volatile area, and when the maintenance identifier exists (S71: YES), the communication unit 21 is used for the server. Is notified of the maintenance identifier and requests resetting contents.

  The maintenance setting management unit 14 of the server refers to the maintenance setting management DB 141, identifies the operation content and the setting content corresponding to the notified maintenance identifier and set to “required” whether or not resetting is required, and the terminal Send to.

  When the terminal requests resetting information without specifying a maintenance identifier, the maintenance setting management unit 14 determines the operation contents and setting contents to be reset based on the address of the terminal that is the access source. You may decide. That is, the maintenance setting management unit 14 searches for a maintenance identifier whose access source address matches the terminal information held in the maintenance status management DB 131, and searches the maintenance setting management DB 141 using the searched maintenance identifier. It is good.

  When the resetting contents can be acquired from the server (S72: YES), the maintenance setting acquiring unit 24 performs resetting based on the acquired setting contents. Since the specific processing content in the resetting is the same as the processing from S37 to S38 in the individual maintenance operation of FIG. 7, the description is omitted here. Note that the acquisition request of the maintenance setting acquisition unit 24 in S72 may be performed a predetermined number of retries.

  In addition to when the agent is activated, the server may accept a setting reset request from the operator, and may be performed when the maintenance setting acquisition unit 24 receives the notification.

  In addition, when the reset request is accepted, the setting contents set when the reset is performed may be added or changed based on an operator operation. Thereby, after confirming the setting content of the terminal after the restart, it can be made the intended content, and further, the amount of data transmitted from the server for the resetting can be reduced.

  In the present embodiment described above, remote maintenance is performed by performing various maintenance operations on a terminal for a certain period in an environment where a plurality of operators perform maintenance simultaneously by linking a server and a terminal. It is possible to prevent a plurality of operators from performing maintenance operations on the same terminal at the same time (for example, outputting a maintenance log for a certain period of time or operating a test application for maintenance). .

  In the present embodiment, even if the terminal 2 that has undergone a terminal setting change or the like by various individual maintenance operations is restarted and the setting change content in the terminal has been cleared, By performing the resetting process (FIG. 11), it is possible to reset the setting change contents by the maintenance operation.

  Further, in the present embodiment, even when there is no maintenance end operation instruction from the operator, the maintenance can be automatically ended by the server or the terminal, and the original state before the maintenance can be reliably restored. As a result, even if the operator forgets the explicit maintenance end operation, even if there is an explicit maintenance end operation, even if the terminal does not receive any maintenance end notification such as a network failure, It is possible to reliably return to the original state before maintenance.

  In addition, this invention is not limited to the said embodiment, Many deformation | transformation are possible within the range of the summary. For example, in the server of the above embodiment, the maintenance status management unit 13 and the maintenance setting management unit 14 include the maintenance status management DB 131 and the maintenance setting management DB 141, respectively, but the server includes an independent storage unit and the storage The information of the maintenance status management DB 131 and the maintenance setting management DB 141 may be stored together.

1: Server 11: Operation availability determination unit 12: Maintenance continuation determination unit 13: Maintenance status management unit 131: Maintenance status management DB
14: Maintenance setting management unit 141: Maintenance setting management DB
15: Communication unit 2: Terminal 21: Communication unit 22: Maintenance end execution unit 23: Maintenance status acquisition unit 231: Maintenance status acquisition DB
24: Maintenance setting acquisition unit 3: Network

Claims (4)

A maintenance management system in which a server and a client terminal cooperate to manage a maintenance state,
The server
Operation availability determination means for receiving input from an operator and determining whether or not an operation is possible;
Maintenance status management means for managing maintenance status information of the client terminal,
The maintenance status information includes a maintenance identifier assigned for each maintenance, an operator ID, a maintenance target client terminal ID, and a scheduled maintenance end time .
The operation availability determination unit refers to the maintenance status information, determines whether or not the operator can maintain the operation content based on the operator ID, the client terminal ID, and the operation content input from the operator,
When it is determined that maintenance is possible, the maintenance status management means notifies the maintenance target client terminal that the operation is possible ,
Maintenance continuation determining means for monitoring each maintenance end scheduled time of the maintenance status information and notifying the end of maintenance to the client terminal of the scheduled maintenance end date and time when the current time has passed,
When the maintenance continuation determination unit receives a maintenance state acquisition request from a client terminal, the maintenance continuation determination unit compares the request time at which the acquisition request is received with a scheduled maintenance end time, and if the request time is before the scheduled maintenance end time. Notifies the client terminal that it is under maintenance,
The client terminal is
Maintenance status acquisition means for holding the next maintenance status acquisition scheduled date and time and requesting the maintenance status from the server based on the next maintenance status acquisition scheduled date and time;
Maintenance status management means for determining whether maintenance can be continued based on the maintenance status acquired by the maintenance status acquisition means;
When the maintenance status management means determines that maintenance cannot be continued, it has maintenance end execution means for executing maintenance end,
The maintenance management system , wherein when receiving a notification that a maintenance operation is possible from the server, the maintenance status acquisition means extends the held maintenance status acquisition scheduled date and time for a certain period . The server
Maintenance setting management means for holding maintenance operation contents performed on the client terminal in association with the maintenance identifier based on an input from an operator,
The client terminal is
Claim the acquisition request of the performed maintenance operation content to the client terminal transmits to the server, characterized by having a maintenance setting acquisition means for setting a maintenance operation content obtained from the server to the storage unit 1 The maintenance management system described. A client terminal in a maintenance management system in which a server and a client terminal cooperate to manage a maintenance state,
Maintenance status acquisition means for holding the next maintenance status acquisition scheduled date and time and requesting the maintenance status from the server based on the next maintenance status acquisition scheduled date and time;
Maintenance status management means for determining whether maintenance can be continued based on the maintenance status acquired by the maintenance status acquisition means;
When the maintenance status management means determines that maintenance cannot be continued, it has maintenance end execution means for executing maintenance end,
The client terminal according to claim 1, wherein, when a notification indicating that a maintenance operation is possible is received from the server, the maintenance status acquisition unit extends the held maintenance status acquisition scheduled date and time for a certain period. The maintenance setting acquisition means to claim 3 in which the request for acquiring the operation content is performed for the client terminal transmits to the server, and sets the operation content obtained from the server in a storage unit The client terminal described.

Images