Remote operation system and method of operating remote operation system

Abstract

To provide a remote operation system which can acquire an evidence for a procedure and a work through remote connection.SOLUTION: A remote operation system according to the present invention has an operation server apparatus, a testing server apparatus, and an operation terminal. The operation server apparatus executes operation software at a client side. The testing server apparatus executes testing software for maintenance and so on for the operation software. The operation terminal can be connected to a client system through remote connection and can carry out maintenance of the testing software and so on. The testing server apparatus has a storage processing unit, a testing monitoring unit, and a transition determination unit. The storage processing unit records contents of an operation for maintenance of the testing software and so on executed at the operation terminal for which remote connection is allowed. The testing monitoring unit can monitor the operation contents at the client side. The mitigation determination unit determines whether or not the testing software subjected to maintenance and so on under supervision is migrated to the operation server device as the operation software.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] An embodiment of the present invention relates to a remote operation system and a method for operating the remote operation system. [Background technology]

[0002] In recent years, there has been an increase in the number of work styles in which work is carried out from a remote location without going to the actual site. For example, telecommuting has become widespread, where a person does desk work by connecting a personal computer installed at home to a company system without coming to the office. In addition, services are being implemented that remotely perform maintenance and inspection of facilities and equipment installed in remote locations. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2014-239355 A [Patent Document 2] Special Publication No. 2021-526250 [Patent Document 3] JP 2007-334559 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, depending on the client and the information being handled, remote connection (online) work may not be easily permitted for security reasons. In such cases, written application procedures and approval procedures for applications may be required, or procedures, meetings, and actual work may be required to be carried out on-site. In addition, when performing maintenance or repair work on software, etc., there are cases where a customer is required to go to the site to carry out preliminary testing and migration work based on the results in the presence of the customer. In such cases, the same procedures and work may be carried out multiple times on site, resulting in poor work efficiency. Therefore, if a system could be provided that could easily and reliably obtain evidence of procedures and work when maintenance or repair work is carried out via remote connection, it would be useful to improve the efficiency and reliability of work via remote connections. [Means for solving the problem]

[0005] The remote operation system according to the embodiment includes a customer system including an operational server device and a test server device, and an operation terminal. The operational server device executes operational software for enabling operation of an information processing system on the customer side. The test server device executes test software for maintenance or modification of the operational software. The operation terminal is remotely connectable to the customer system and capable of maintaining or modifying the test software. The test server device includes a storage processing unit, a test system monitoring unit, and a migration determination unit. The storage processing unit records operation details for maintenance or modification of the test software executed on the operation terminal permitted to be remotely connected. The test system monitoring unit enables the operation details to be monitored on the customer side. The migration determination unit determines whether or not the test software maintained or modified under monitoring should be migrated to the operational server device as the operational software. [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is an exemplary schematic image diagram showing a remote control system according to an embodiment. [Diagram 2] FIG. 2 is an exemplary schematic block diagram illustrating a configuration of a test server device of the remote operation system according to the embodiment. [Diagram 3]FIG. 3 is an exemplary schematic block diagram illustrating a configuration of an operation server device of the remote operation system according to the embodiment. [Figure 4] FIG. 4 is an exemplary flowchart showing a flow of an early stage of a test-system rehearsal among the operations of the remote operation system according to the embodiment. [Diagram 5] FIG. 5 is an exemplary flowchart showing a flow of the middle stage of a test system rehearsal among the operations of the remote operation system according to the embodiment. [Figure 6] FIG. 6 is an exemplary flowchart showing a final stage of a test system rehearsal among the operations of the remote operation system according to the embodiment. [Figure 7] FIG. 7 is an exemplary flowchart showing the flow of the first half of the operational system release in the operation of the remote operation system according to the embodiment. [Figure 8] FIG. 8 is an exemplary flowchart showing the latter half of the flow of the operational system release from among the operations of the remote operation system according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The configuration of the embodiment described below, and the actions and results (effects) brought about by the configuration are merely examples, and are not limited to the contents described below.

[0008] FIG. 1 is an exemplary schematic image diagram showing a remote control system 10 according to an embodiment.

[0009] The remote operation system 10 is a system that can be applied to an online user information inquiry system, so that each end user business can connect via the Internet and share common information that is centrally managed by each business. For example, it can be applied to maintenance and repair work on a system that handles information related to ETC. The remote operation system 10 is a system constructed by connecting an operation system server device 14, which is equipment at a customer site, a test system server device 12, an approver terminal 16, and an operation terminal 18, which is equipment at a manufacturer site, via a communication line C such as the Internet. The remote operation system 10 enables maintenance and repair work on a system at the customer site (for example, software for operating an information processing system on the customer side) while transmitting and receiving data between the equipment at the customer site and the equipment at the manufacturer site. The system can be applied to an online user information inquiry system that enables each business operator, who is an end user, to connect via the Internet and to inquire about common information shared by each business operator under centralized management. For example, the system can be applied to maintenance and repair work on an ECT system that handles information related to ETC.

[0010] The customer site includes a test system server device 12, an operation system server device 14, an approver terminal 16, and the like.

[0011] The operational server device 14 is a server device that operates the services provided by the customer. In this system, it is the server that is the subject of testing. The operational server device 14 has a function of replaying (directly applying) the operation contents (contents of the software that has been maintained or modified and functioned without any problems) recorded in the rehearsal carried out in the test server device 12. In other words, the maintenance contents or modification contents cannot be modified or tampered with during the transition phase.

[0012] The operation system server device 14 can be configured with computer resources such as a general PC, etc. The operation system server device 14 is configured with, for example, a CPU, a ROM, a RAM, a storage unit such as an HDD or SSD, a communication interface, an input / output interface, etc.

[0013] The test system server device 12 is a server for constructing a test environment for testing the operational system server device 14. The test system server device 12 is independent from the operational system server device 14, and can be connected only to an operation terminal 18 on the manufacturer's side that is permitted to be connected, and rehearsals of software maintenance work, modification work, and the like can be performed.

[0014] The approver terminal 16 is a terminal that can be operated by a user (customer) at the customer site and can check and approve the displayed contents. The approver terminal 16 may be, for example, a general desktop PC, a notebook PC, a tablet terminal, etc. The approver terminal 16 is composed of, for example, a CPU, a ROM, a RAM, a storage unit such as an HDD or SSD, a communication interface, an input / output interface, etc.

[0015] The manufacturer site includes an operation terminal 18 . The operation terminal 18 can be connected to the test system server device 12 or the operational system server device 14 only when approval is obtained from the customer's person in charge (approver) who operates the approver terminal 16. In addition, the operation terminal 18 can perform rehearsal operations such as software maintenance work and repair work only when connected to the test system server device 12. In addition, when the operation terminal 18 is connected to the operational system server device 14, only the function of replaying the same content as the successful rehearsal content in the test system server device 12 is enabled, and operations such as maintenance work and repair work are disabled. The operation terminal 18 may be, for example, a general stationary type PC, a notebook type PC, a tablet terminal, etc. The operation terminal 18 is composed of, for example, a CPU, a ROM, a RAM, a storage unit such as an HDD or SSD, a communication interface, an input / output interface, etc.

[0016] In this embodiment, the customer issues and manages electronic authentication keys to be used in an authentication system operated by a subordinate organization of the customer, for example, by operating software supplied by a manufacturer on a business network. Since the issued authentication key is linked to personal information (such as name, address, date of birth, and payment information) that is set to use a device that uses the authentication key (a device that uses the authentication system operated by the subordinate organization), it is necessary to strictly manage the authentication key to maintain security. Similarly, ensuring security is important when maintaining or modifying software used by customers during operation. In this case, it is necessary to establish a system that takes into consideration the prevention of information leaks, unauthorized use, data tampering, etc., so that customers can smoothly agree to online connections to the business network of their systems (information processing systems) for the purpose of maintenance and modification work. In addition, it is desirable to increase reliability during operation of software that customers will use during operation by, for example, rehearsing it on a test system and, if it functions without problems, transferring (releasing) it to the operational system.

[0017] Therefore, in the remote operation system 10 of the present embodiment, a system is constructed that allows the manufacturer and the customer to easily and reliably ensure security during each task (operation) and to ensure evidence. In the case of the remote operation system 10 of this embodiment, for example, the operations performed in the rehearsal in the test system are recorded, and the operations recorded in the rehearsal are directly applied to the migration (release) to the production system. As a result, the reliability of the migration work is increased, and the record of the operations that were successful in the rehearsal is used as evidence to ensure the reliability of the migration work. In this case, the work content and its reliability can be explained to the customer smoothly and clearly. In addition, rehearsals and on-site work associated with the transition can be carried out online while maintaining security, reliability, and certainty, which contributes to reducing work costs, ensuring on-site safety, and improving work quality. The specific configuration of the remote operation system 10 of this embodiment will be described below.

[0018] FIG. 2 is an exemplary schematic block diagram showing a configuration of the test server device 12 of the remote operation system 10 according to the embodiment.

[0019] The test system server device 12 can be configured with, for example, computer resources such as a general PC (Personal Computer). Although not shown in Fig. 2, the test system server device 12 is configured with, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a storage unit such as a HDD (Hard Disk Drive) or an SSD (Solid State Drive), a communication interface, an input / output interface, etc. The test system server device 12 is equipped with a test system storage unit 22 that stores an operation command record data file 22a and a test system operation result data file 22b as action contents during rehearsals of software maintenance work, repair work, etc. The test system storage unit 22 can be configured with, for example, an HDD or SSD, but is designed so that data cannot be modified or added to once it has been written.

[0020] The CPU 20, for example, reads out a program installed and stored in a non-volatile storage unit such as a ROM or SSD, and, in accordance with the program, realizes various modules that function to perform rehearsals of software maintenance work, repair work, and the like in the test system server device 12. The CPU 20 can realize, for example, a test system use application receiving unit 20a, a test system use determining unit 20b, a test system connection processing unit 20c, a test system operation processing unit 20d, a recording processing unit 20e, a test system operation monitoring unit 20f, a test system operation completion checking unit 20g, a transition determining unit 20h, and the like.

[0021] The test system use application receiving unit 20a receives an application to use the test system server device 12 provided online from the operation terminal 18 operated by the person in charge at the manufacturer site via the approver terminal 16. The test system use application receiving unit 20a receives application information such as applicant information (company name, name, contact information), usage time (start date / end date / time), scope of work (system update / data update / data display, etc.), and increased data volume (MB), and saves it in a test system use application file, etc. The application information is also displayed on the display unit of the approver terminal 16.

[0022] The test system use determination unit 20b checks whether there are any defects in the application information, determines whether to permit or reject the use, and if the application is permitted, prompts the approver terminal 16 (approver) to issue a login user ID and password. If the application is rejected, the test system use determination unit 20b transmits information indicating this to the operation terminal 18 and displays it, thereby prompting the person in charge on the manufacturer side to resubmit the application.

[0023] When the use of the test system server device 12 is permitted, the test system connection processing unit 20c transmits a test system use application file and an electronic certificate to the operation terminal 18 of the manufacturer permitted to use the device, and displays them on the display unit of the operation terminal 18. In this case, the display unit of the operation terminal 18 displays a confirmation screen of application information such as applicant information (company name, name, contact information), use time (start date / end date / time), work scope (system update / data update / data display, etc.), and increased data volume (MB), as well as a use judgment (permit / reject) and, in the case of permission, a test system use permission number, a login user ID, a password, etc. If the use of the test system server device 12 is permitted and input of the test system use permission number, login user ID, password, etc. from the operation terminal 18 is confirmed, the test system connection processing unit 20c accepts a connection from the operation terminal 18 to the test system by a terminal emulator. In other words, it enables an online connection between the operation terminal 18 and the test system server device 12.

[0024] The test system operation processing unit 20d accepts operations of the terminal emulator by the person in charge on the manufacturer's side, and issues an instruction to start recording of operation commands in the terminal emulator to the recording processing unit 20e.

[0025] When the recording processing unit 20e receives an instruction to start recording an operation command, it converts the mouse operation and key operation for each behavior performed on the terminal emulator into a command line in the order of operation, and outputs the command to the operation command record data file 22a of the test system storage unit 22 together with the data of the start date and time of recording. This storage process is repeatedly executed until an instruction to end command recording is issued. In other words, the recording processing unit 20e sequentially records the operation contents for maintenance or repair of the test system software executed on the operation terminal 18 that is permitted to be remotely connected. In addition, the recording processing unit 20e can contribute to improving the ease of understanding when monitoring or checking the operation contents by converting the operation command record into a command line and storing it.

[0026] The test system operation monitoring unit 20f outputs the operation results in a log in parallel with the output of the operation command record data file 22a by the record processing unit 20e. For example, the test system operation monitoring unit 20f saves the history of the operation results in the test system operation result data file 22b of the test system storage unit 22. The test system operation monitoring unit 20f also displays the history of the operation results in real time on a screen (for example, the display unit of the approver terminal 16) that can be viewed by the person in charge at the customer site, so that the person in charge on the manufacturer's side and the person in charge on the customer's side can share the operation results and operation contents and monitor each other. This allows, for example, if an unauthorized operation is performed by the person in charge on the manufacturer's side, the person in charge on the customer's side to urgently interrupt the operation of the manufacturer. Also, if the person in charge on the manufacturer's side fails to perform an operation, he or she can interrupt the operation and start the operation over from the beginning.

[0027] When the person in charge at the manufacturer inputs an instruction to end command recording from the operation terminal 18, the test system operation completion confirmation unit 20g accepts the operation and ends output to the operation command recording data file 22a. As a result, the operation command recording data file 22a is closed and saved together with the date and time data of recording completion. In other words, the recorded contents cannot be changed thereafter. At the same time, the test system operation completion confirmation unit 20g also transmits to the operation terminal 18 at the customer site that the work on the test system server device 12 has been completed, and notifies the person in charge.

[0028] The transition determination unit 20h displays the monitoring result by the test system operation monitoring unit 20f, the result of saving to the operation command record data file 22a, and, if necessary, the result of playing back the operation command record data file 22a on the approver terminal 16. The transition determination unit 20h also checks predetermined check items and prompts the approver terminal 16 (approver) to determine whether the rehearsal result based on the operation of the person in charge on the manufacturer side can be operated on the operation system server device 14. In this case, each result is displayed on the display unit of the approver terminal 16, so that the person in charge on the customer side can check them in parallel. The transition determination unit 20h prompts the approver terminal 16 (approver) to make a transition determination (permission / rejection) on whether it is OK to release the operation performed by the transition determination unit 20h (and the person in charge on the customer side) on the test system (test system server device 12) on the operation system (operation server device 14). If the transition determination is negative, for example if the specified conditions for transition are not met, the application for use of the operational system (operational server device 14) cannot proceed, and the approver terminal 16 notifies the operation terminal 18 (person in charge) on the manufacturer side that it will wait for instructions from the person in charge on the customer side. On the other hand, if the transition determination is permitted, the application for use of the operational system (operational server device 14) can be made, and the approver terminal 16 notifies the operation terminal 18 (person in charge) on the manufacturer side of this fact.

[0029] FIG. 3 is an exemplary schematic block diagram showing a configuration of the operation server device 14 of the remote operation system 10 according to the embodiment.

[0030] The operational server device 14 can be configured with computer resources such as a general PC, etc. Although not shown in Fig. 3, the operational server device 14 is configured with, for example, a CPU, a ROM, a RAM, a storage unit such as an HDD or SSD, a communication interface, an input / output interface, etc.

[0031] 3, the operational server device 14 includes an operational storage unit 26 that records an operational operation result data file 26a, which records as a history the results of reproducing the operation command record data file 22a executed and stored by the test server device 12 in the operational server device 14. The operational storage unit 26 can be configured with, for example, an HDD or SSD, but is designed so that data cannot be modified or added to once it has been written.

[0032] The CPU 24, for example, reads out a program installed and stored in a non-volatile storage unit such as a ROM or SSD, and realizes various modules that function to release software that has been maintained or modified in the operational server device 14 according to the program. That is, it realizes a module for reproducing the contents of a successful result of a rehearsal (rehearsal of software maintenance work, modification work, etc.) performed in the test system server device 12 in its original state in the operational server device 14. The CPU 24 can realize, for example, an operational system use application receiving unit 24a, an operational system use determining unit 24b, an operational system connection processing unit 24c, an operational system operation processing unit 24d, a playback unit 24e, an operational system operation monitoring unit 24f, an operational system operation completion confirming unit 24g, and the like.

[0033] The operational system use application acceptance unit 24a accepts an application for use of the operational system server device 14 provided online through the approver terminal 16 from the operation terminal 18 operated by the person in charge at the manufacturer site. When the migration judgment unit 20h of the test system server device 12 permits migration judgment, the operational system use application acceptance unit 24a becomes able to accept a use application for the operation terminal 18 (operator on the manufacturer side) for which the migration application has been permitted. The operational system use application acceptance unit 24a accepts application information such as, for example, applicant information (company name, name, contact information), usage time (start date and time / end date and time), scope of work (system update / data update / data display, etc.), increased data volume (MB), migration judgment result, migration permission number, etc., and saves it in an operational system use application file, etc. Also, the application information is displayed on the display unit of the approver terminal 16.

[0034] The operational system usage determination unit 24b checks whether there are any defects in the application information, determines whether to permit or reject the use, and if the application is permitted, prompts the approver terminal 16 (approver) to issue a login user ID and password. In this case, the password may be different from the password issued by the test system server device 12. If the transition determination is rejected, the operational system usage determination unit 24b transmits information indicating this to the operation terminal 18 and displays it, thereby prompting the manufacturer's person in charge to resubmit the application.

[0035] When the use of the operational server device 14 is permitted, the operational connection processing unit 24c transmits an application file for use of the operational server device 14 and an electronic certificate to the operation terminal 18 of the permitted manufacturer, and displays them on the display unit of the operation terminal 18. In this case, the display unit of the operation terminal 18 displays a confirmation screen of application information such as applicant information (company name, name, contact information), use time (start date / end date / time), work scope (system update / data update / data display, etc.), and increased data volume (MB), as well as a use judgment (permit / reject) and, in the case of permission, a migration permission number, a login user ID, a password, etc. If the use of the operational server device 14 is permitted and input of the migration permission number, the login user ID, the password, etc. is confirmed from the operation terminal 18, the operational connection processing unit 24c accepts a connection from the operation terminal 18 to the operational system by a terminal emulator. In other words, it enables an online connection between the operation terminal 18 and the operational server device 14.

[0036] The operation processing unit 24d of the operation system accepts the operation of the terminal emulator by the person in charge of the manufacturer, and instructs the replay unit 24e to replay the operation command record in the terminal emulator. Note that the person in charge of the manufacturer cannot perform any operation other than the replay instruction in the operation system server device 14. However, it is possible to interrupt the operation if an abnormality occurs.

[0037] When the reproducing unit 24e acquires an instruction to reproduce the operation command record, the mouse operation and key operation for each behavior recorded on the terminal emulator of the test system (test system server device 12) are reproduced from the operation command record data file 22a in the order in which they were recorded. In other words, the reproducing unit 24e reproduces the operation contents of the test system software recorded by the recording processing unit 20e of the test system server device 12, and enables the operation system software to be realized by the operation system server device 14 as the operation system software.

[0038] The operation system operation monitoring unit 24f outputs the playback result in a log in parallel with the playback of the operation command record data file 22a by the playback unit 24e. For example, the operation system operation monitoring unit 24f saves the history of the playback result in the operation system operation result data file 26a of the operation system storage unit 26. The operation system operation monitoring unit 24f also displays the history of the playback result in real time on a screen (for example, the display unit of the approver terminal 16) that can be viewed by the person in charge at the customer site, so that the person in charge on the manufacturer's side and the person in charge on the customer's side can share the playback results and monitor each other. This allows the person in charge on the customer's side to urgently interrupt the playback operation if, for example, an unauthorized operation is performed by the person in charge on the manufacturer's side. Also, the person in charge on the manufacturer's side can interrupt the playback operation if an abnormality occurs during processing.

[0039] When playback of the operation command record data file 22a is all completed, the operational operation completion confirmation unit 24g ends the reception of all operations for the operational server device 14 and notifies the completion of the work on the operational system (operation server device 14) on the display unit or the like of the approver terminal 16 at the customer site together with the date and time data of the playback completion. Similarly, the operational operation completion confirmation unit 24g notifies the operation terminal 18 at the manufacturer site of the operation completion together with the date and time data of the playback completion.

[0040] Next, the operation will be described. The flow of processing in the remote operation system 10 configured as described above will be described with reference to FIGS.

[0041] First, FIGS. 4 to 6 are flow charts showing the process related to the test system rehearsal. FIG. 4 is an exemplary flowchart showing the flow of the early stage of a test system rehearsal among the operations of the remote operation system 10.

[0042] In step S100, the person in charge on the manufacturer's side (operation terminal 18) performs a test system use application process to the customer approver (approver terminal 16). In the test system use application process, the test system use application acceptance unit 20a performs a process to prompt the operation terminal 18 to input information such as applicant information (company name, name, contact information), usage time (start date and time / end date and time), scope of work (system update / data update / data display, etc.), and increased data volume (MB) as application details. In this case, the test system use application acceptance unit 20a prompts the approver terminal 16 to accept the application information and to save the test system use application file, etc.

[0043] Next, in step S102, the approver terminal 16 displays the application information so that the customer approver can determine whether or not to approve the test system use application from the manufacturer. In this case, the test system use determination unit 20b performs a check process to determine whether or not there are any defects in the application information, so that the approver can easily give approval on the approver terminal 16. In addition, the test system use determination unit 20b prompts the approver terminal 16 (approver) to issue a login user ID / password and an electronic certificate.

[0044] Then, in step S104, if it is determined that the application information is incomplete (No in S104), that is, if it is not approved, the process returns to step S100, and the test system usage determination unit 20b prompts the approver terminal 16 (approver) to resubmit the test system usage application. On the other hand, if there is no incompleteness in the application information (Yes in S104), that is, if it is approved, in step S106, the test system usage determination unit 20b performs settings related to the login user ID / password and electronic certificate in the test system server device 12 as a necessary item presetting process.

[0045] If the application for use of the test system server device 12 is approved, the login user ID / password issued in step S102 is notified from the client site in step S108, and a test system use permission certificate file is sent. As a result, the operation terminal 18 executes an application approval confirmation process, and executes a process for saving and confirming the login user ID, password, and test system use permission certificate file.

[0046] Then, in step S110, a process is executed for electronically authenticating the operation terminal 18 using a digital certificate that allows only the operation terminal 18 approved in the test system use application from the customer to be connected.

[0047] Next, in step S112, the test system use determination unit 20b identifies whether the client certificate of the operation terminal 18 is valid through electronic authentication, and determines whether to permit or reject the connection. If the result of the determination in step S114 is rejection (No in S114), the process returns to step S112 and repeats the confirmation process. In this case, for example, the operation terminal 18 may be requested to re-execute electronic authentication using the electronic certificate.

[0048] If electronic authentication is permitted in step S114, in step S116, the operation terminal (operator on the manufacturer's side) can execute a process of connecting to the test system server device 12 from the terminal emulator using approval information issued when the test system use application from the customer side is approved. In this case, the approval information is, for example, the login user ID and password issued in the process of step S102.

[0049] In step S118, the test system connection processing unit 20c logs in to the test system server device 12 using the approval information, and checks whether the login user ID and password match those preregistered in the test system server device 12. If they do not match in step S120 (No in S120), the process returns to step S112 and repeats the checking process. In this case, for example, the operation terminal 18 may be requested to re-execute electronic authentication using the electronic certificate.

[0050] If there is a match in step S120 (Yes in S120), the test system connection processing unit 20c, in step S122, connects to the test system server device 12 using the terminal emulator of the operation terminal 18, and performs processing to transition the test system server device 12 to a usable (operable) state.

[0051] Next, FIG. 5 is an exemplary flowchart illustrating the flow of the middle stage of the test system rehearsal among the operations of the remote operation system 10. In FIG.

[0052] In step S124, when the terminal emulator of the operation terminal 18 becomes able to connect to the test system server device 12 in step S122, the test system operation processing unit 20d causes the terminal emulator to execute a process of inputting a start instruction command for starting recording of operation commands in the test system server device 12. For example, a screen prompting the input operation is displayed on the display unit of the operation terminal 18.

[0053] Then, in step 126, the test system operation processing unit 20d accepts the operation of the terminal emulator by the person in charge on the manufacturer side, and causes the recording processing unit 20e to execute an operation command start request command that instructs the terminal emulator to start recording of the operation command. Then, the recording processing unit 20e transitions to a mode in which it starts a process of saving to an operation command record data file.

[0054] In step S128, the test system server device 12 enters a save mode for the operation command record data file in the operation terminal 18, and starts accepting command input. Then, in step S130, input processing of an operation command to the test system server device 12 is executed.

[0055] In step S132, the test system operation processing unit 20d executes the operation command, and the record processing unit 20e stores the operation command in the operation command record data file 22a of the test system storage unit 22.

[0056] In step S134, the test system operation monitoring unit 20f causes the approver terminal 16 to execute a process of displaying the execution result of the operation command from the test system server device 12. Also, in step S136, the test system operation monitoring unit 20f causes the operation terminal 18 to execute a process of displaying the execution result of the operation command from the test system server device 12. As a result, the customer site and the manufacturer site can mutually confirm and monitor the operation contents (registration contents) of the operation command executed in the test system server device 12.

[0057] In step S138, the test-system operation completion confirmation unit 20g causes the terminal emulator in the operation terminal 18 to confirm whether or not the recording of the operation command for the test system server device 12 has been completed. For example, it causes the display unit of the operation terminal 18 to display a confirmation message indicating whether or not the recording has been completed. If the recording of the operation command has not been completed (No in S138), the process proceeds to step S130 and the input process of the operation command continues.

[0058] Next, FIG. 6 is an exemplary flowchart for explaining the flow of the final stage of the test system rehearsal among the operations of the remote operation system 10.

[0059] If it is determined in step S138 that the recording of the operation command for the test system server device 12 has been completed (Yes in S138), in step S140, the test system operation completion confirmation unit 20g causes the terminal emulator of the operation terminal 18 to perform input processing to terminate the recording of the operation command for the test system server device 12.

[0060] Then, in step S142, the test system operation completion confirmation unit 20g executes the operation command end request command and executes the save end process to the operation command record data file. In other words, the recorded contents cannot be changed thereafter. In this case, the test system operation completion confirmation unit 20g may also simultaneously transmit to the operation terminal 18 at the customer site that the work of the test system server device 12 has been completed, to notify the person in charge.

[0061] Next, in step S144, the migration determination unit 20h prompts the operation terminal 18 (operator) to input migration application information on the application screen for migration determination processing, and causes the customer to perform the migration determination application processing. Here, the migration application information is, for example, applicant information (company name, name, contact information), test system use license number, operation command record data file name, etc.

[0062] If a migration determination application is made in step S144, in step S146, the migration determination unit 20h prompts the approver terminal 16 to accept the migration determination application, and prompts the approver terminal 16 (approver) to determine whether or not to permit the migration to the operational server device 14.

[0063] In step S148, if the transition determination is not permitted (No in S148), for example, if the content of the transition application does not satisfy the transition conditions of the customer, etc. In this case, the process returns to step S144, and the transition determination unit 20h may display a message on the display unit or the like of the operation terminal 18 to prompt the customer to apply for transition again.

[0064] In step S148, if the migration determination is permitted (Yes in S148), in step S150, the migration determination unit 20h executes a process of notifying the manufacturer side (operation terminal 18 side) of use application information required for the application for use of the operational system of the operational server device 14. The use application information for the operational server device 14 includes, for example, the result of the migration determination and a migration permission number.

[0065] Next, FIG. 7 and FIG. 8 will be used to explain the process related to the release of the operational system. FIG. 7 is an exemplary flowchart for explaining the flow of the first half of the operational system release among the operations of the remote operation system 10.

[0066] When the operation terminal 18 acquires the use application information of the operational server device 14, in step S152, the operational system use application receiving unit 24a prompts the approver terminal 16 (customer approver) to execute the operational system use application process. Information required for the operational system use application includes, for example, applicant information (company name, name, contact information), usage time (start date / end date / time), scope of work (system update / data update / data display, etc.), increased data volume (MB), migration judgment result, migration permission number, etc.

[0067] In step S154, the approver terminal 16 accepts the use application information according to the instruction of the operational system use application receiving unit 24a, and is prompted to execute authentication processing according to the instruction of the operational system use determining unit 24b. For example, the operational system use determining unit 24b checks the conditions for using the operational system server device 14, and causes the approver terminal 16 to display information required for approval by the approver. Then, the operational system use determining unit 24b prompts the approver terminal 16 (approver) to issue a login user ID, password, and electronic certificate.

[0068] In step S156, if authentication is not permitted (No in S156), the process proceeds to step S152, and the operational system use determination unit 24b prompts the operation terminal 18 (the operator on the manufacturer's side) to resubmit the application for use of the operational system. On the other hand, if there is no defect in the application for use of the operational system (Yes in S156), that is, if approved, in step S158, the operational system use determination unit 24b pre-sets the login user ID / password and electronic certificate for the operational system server device 14.

[0069] If the application for use of the operational server device 14 is approved, the login user ID / password issued in step S154 is notified from the client site and an operational system use permission certificate file is sent in step S160. As a result, the operation terminal 18 executes, for example, a process of saving and confirming the login user ID / password and the operational system use permission certificate file.

[0070] Then, in step S162, a process is executed for electronically authenticating the operation terminal 18 using a digital certificate that allows only the operation terminal 18 approved in the application for use of the active system from the customer to be connected.

[0071] Next, in step S164, the active system use determination unit 24b identifies whether the client certificate of the operation terminal 18 is valid through electronic authentication, and determines whether to permit or reject the connection. If the result of the determination in step S166 is rejection (No in S166), the process returns to step S164 and repeats the confirmation process. In this case, for example, the operation terminal 18 may be requested to re-execute electronic authentication using the electronic certificate.

[0072] If electronic authentication is permitted in step S166, in step S168, the operation terminal (operator on the manufacturer's side) can execute processing to connect to the operation system server device 14 from the terminal emulator using approval information issued when the application for use of the operation system from the customer's side is approved. In this case, the approval information is, for example, the login user ID and password issued in the processing of step S154.

[0073] In step S170, the operation system connection processing unit 24c logs in to the operation system server device 14 using the approval information, and checks whether the login user ID and password match those registered in advance in the operation system server device 14. If there is no match in step S172 (No in S172), the process returns to step S164 and the confirmation process is repeated. In this case, for example, the operation terminal 18 may be requested to re-execute electronic authentication using the electronic certificate.

[0074] If there is a match in step S172 (Yes in S172), in step S174, the terminal emulator of the operation terminal 18 connects to the operation system server device 14, and the operation system server device 14 is shifted to a usable (operable) state.

[0075] Next, FIG. 8 is an exemplary flowchart for explaining the flow of the first half of the operational system release among the operations of the remote operation system 10. In FIG. When connection to the operation system server device 14 becomes possible, in step S176, the reproducing unit 24e prompts the operation terminal 18 (operator) to input a reproducing instruction command. That is, the terminal emulator of the operation terminal 18 prompts the operator to input a reproducing instruction command for reproducing the operation command on the operation system server device 14 by using the operation command record data (the operation command record data file 22a of the test system storage unit 22) stored in the test system server device 12.

[0076] In step S178, the reproducing unit 24e executes the reproducing instruction command and starts the operation command reproducing process. In this case, the acceptance of the operation command input is temporarily stopped. Then, in step S180, the operation commands stored in the operation command recording data file 22a are executed (played back) in sequence up to the last line.

[0077] At this time, in step S182, the operation command execution results (reproduction results) from the operation system server device 14 are displayed in sequence on the approver terminal 16 in response to an instruction from the operation system operation monitoring unit 24f. Similarly, in step S184, the operation command execution results (playback results) from the operation server device 14 are sequentially displayed on the operation terminal 18 in response to an instruction from the operation operation monitoring unit 24f. As a result, the customer site and the manufacturer site can mutually confirm and monitor the playback contents of the operation commands being executed by the operation server device 14.

[0078] In step S186, if the sequential execution (playback) of the operation commands has not been performed up to the last line (No in S186), the process of step S180 continues. On the other hand, if the sequential execution (playback) of the operation commands has been performed (completed) up to the last line (Yes in S186), the operational system operation completion confirmation unit 24g ends the execution of the operation command playback command in step S188. Furthermore, in step S190, the operational operation completion confirmation unit 24g executes a notification process to notify the approver terminal 16 that the reproduction of the operation command in the operational server device 14 has ended. Similarly, in step S192, the operational operation completion confirmation unit 24g executes a notification process to notify the operation terminal 18 that the reproduction of the operation command has been completed in the operational server device 14. That is, the customer site and the manufacturer site are notified that the release of the software to the operational server device 14 has been completed, and a series of processing flows in the remote operation system 10 is terminated.

[0079] In this way, according to the remote operation system 10 of this embodiment, when connecting to the test server device 12, the operation commands (rehearsal contents) at that time are recorded one by one, and the contents of the operation commands can be confirmed in real time at the manufacturer site and the customer site. When connecting to the operational server device 14, the recorded rehearsal contents are played back as is and released on the operational server device 14. As a result, when performing maintenance work or repair work through a remote connection, evidence of the procedures and work can be easily and reliably obtained. As a result, various tasks through a remote connection can be performed smoothly while maintaining the security. In addition, it can contribute to improving the efficiency and reliability of work through a remote connection.

[0080] The remote operation system 10 described in this embodiment can be connected to a communication line C such as the Internet, and can be used in an environment that has a test system with the same configuration as the operational system (production system) used in operations, and in a field environment where a rehearsal with the test system is required in advance when transitioning to the operational system.

[0081] Although several embodiments of the present invention have been described above, the above-mentioned embodiments and modifications are merely examples and are not intended to limit the scope of the invention. The above-mentioned embodiments can be implemented in various forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. The above-mentioned embodiments and modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0082] 10 Remote Operation System 12 Test server equipment 14 Operational Server Equipment 16 Approver terminal 18 Operation terminal 20, 24 CPU 20a Test System Use Application Reception Department 20b Test system use judgment section 20c Test system connection processing section 20d Test system operation processing section 20e Recording processing section 20f Test System Operation and Monitoring Department 20g Test system operation completion confirmation part 20h Transition Judgment Section 22 Test system memory section 24a Operational System Use Application Reception Department 24b Operational system usage determination unit 24c Operational system connection processing unit 24d Operational system operation processing section 24e Playback section 24f Operation monitoring section 24g Active system operation completion confirmation part 26 Operational storage unit

Claims

1. A remote operation system including a customer system including an operation system server device that executes operation system software for enabling an information processing system to be operated on a customer side, and a test system server device that executes test system software for maintenance or modification of the operation system software, and an operation terminal that can be remotely connected to the customer system and can perform maintenance or modification of the test system software, The test system server device a recording processing unit that records operation contents for maintenance or modification of the test-system software executed on the operation terminal that is permitted to be remotely connected; a test system monitoring unit that enables the client to monitor the operation content; a migration determination unit that determines whether or not the test system software that has been maintained or repaired under monitoring should be migrated to the operational system server device as the operational system software; A remote operation system comprising:

2. The operational server device a playback unit that plays back the operation content of the test-system software recorded by the recording processing unit of the test-system server device, and enables the operation content to be realized by the operation-system server device as the operation-system software; an operational system monitoring unit that enables the client to monitor the contents of the playback; The remote operation system of claim 1 .

3. the recording processing unit of the test system server device stores the operation contents of the operation terminal in the order of operation as an operation command record data file; 3. The remote operation system according to claim 2, wherein the playback unit of the operational server device sequentially plays back the operation command record data files.

4. 4. The remote operation system according to claim 3, wherein the operation command record data file converts the operation contents into command lines and records them.

5. A method for operating a remote operation system including a customer system including an operation system server device that executes operation system software for enabling an information processing system to be operated on a customer side, and a test system server device that executes test system software for maintenance or modification of the operation system software, and an operation terminal that can be remotely connected to the customer system and can perform maintenance or modification of the test system software, comprising: The test system server device a recording process step of recording operation contents for maintenance or modification of the test-system software executed on the operation terminal permitted to be remotely connected; a test system monitoring step for enabling the client to monitor the operation content; a migration determination step of determining whether or not the test system software that has been maintained or repaired under supervision should be migrated to the operational system server device as the operational system software; A method for operating a remote operation system comprising:

6. The operational server device a reproducing step of reproducing the operation contents of the test system software recorded in the recording processing step of the test system server device, and making it possible to realize the operation contents of the test system software as the operation system software in the operation system server device; an operational system monitoring step for enabling the client to monitor the contents of the playback; The method for operating a remote operation system according to claim 5 , comprising:

Images