System and method for maintaining task operation continuity

Abstract

The embodiment of the invention provides a system for maintaining task operation continuity, and the system comprises a server which is in communication coupling with a first computer device and a second computer device. The server is configured to: monitor individual operating states of a first computer device and a second computer device, where the first computer device and the second computer device are individually deployed with at least a first task in a Docker form, and the first task is assigned to be run by the first computer device; and in response to determining that the first computer device cannot normally operate, assigning the first task to a normally operating second computer device to operate through the distributed architecture. Therefore, the task can be transferred to another computer device which normally runs to continue to run through the distributed architecture, so that the effect of maintaining the continuity of task operation is achieved. The invention further relates to a method for maintaining task operation continuity.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to an industrial control mechanism, and in particular, to a system and method for maintaining task operation continuity. BACKGROUND

[0002] There are multiple different devices working together on a production line. When a hardware failure occurs on a device, the production line can continue to operate immediately by simply replacing the spare parts. However, if a mechatronic controller (e.g., an industrial control computer) with software / hardware integration fails, the situation becomes complicated.

[0003] In a serious case, a cooperative vendor may be needed to help reinstall the operating system, industrial control software, and reset the functions of the machine, which can cause the production line to be shut down for a long time due to the failure to successfully perform a task (e.g., a processing task), thereby causing significant losses. SUMMARY

[0004] Therefore, the present disclosure provides a system and method for maintaining task operation continuity, which can be used to solve the above technical problems.

[0005] The present disclosure provides a system for maintaining task operation continuity, comprising a server communicatively coupled to a first computer device and a second computer device. The server is configured to monitor the operation status of the first computer device and the second computer device individually, wherein the first computer device and the second computer device are individually deployed with a first task in a Docker form, and the first task is assigned to be run by the first computer device; in response to determining that the first computer device cannot operate normally, assigning the first task to be run by the second computer device which operates normally through a distributed architecture.

[0006] According to one embodiment of the present disclosure, the distributed architecture comprises a 61499 distributed architecture.

[0007] According to one embodiment of the present disclosure, the server receives data and status of the tasks run by the first computer device and the second computer device individually.

[0008] According to one embodiment of the present disclosure, the server is further configured to receive a first device configuration from the first computer device and a second device configuration from the second computer device; in response to determining that a third computer device is connected to the server, restore the third computer device according to the first device configuration corresponding to the first computer device; and assign the first task running on the second computer device to be run by the third computer device through the distributed architecture.

[0009] According to one of the embodiments of the present disclosure, the third computer device is further configured to run a FIDO onboarding agreement, and is further configured to have a script configured to restore the device configuration of the first computer device; wherein the server is configured to restore the third computer device to correspond to the first computer device based on the FIDO onboarding agreement.

[0010] According to one of the embodiments of the present disclosure, the first computer device and the second computer device are further configured to run a second task in the Docker form, and the second task is assigned to the second computer device; wherein the second computer device has a primary end and a backup end, the primary end is configured to transmit data associated with the second task, and after the second computer device is assigned to run the first task, the second computer device transmits data associated with the first task through the backup end.

[0011] According to one of the embodiments of the present disclosure, the primary end and the backup end of the second computer device are both Ethercat ends.

[0012] According to one of the embodiments of the present disclosure, a hardware input / output switch is further coupled to the primary end and the backup end of the second computer device, and is configured to transmit the data associated with the first task and the data associated with the second task to a first controlled device and a second controlled device respectively.

[0013] According to one of the embodiments of the present disclosure, after the first task running on the first computer device is assigned to the normally operating second computer device through the distributed architecture, the server controls the hardware input / output switch to switch the data associated with the first task between the first controlled device and the backup end of the second computer device.

[0014] The embodiments of the present disclosure provide a method for maintaining task operation continuity, comprising: monitoring the operation state of a first computer device and a second computer device by a server communicatively coupled to the first computer device and the second computer device, wherein the first computer device and the second computer device are each configured to run at least a first task in the Docker form, and the first task is assigned to run by the first computer device; in response to determining that the first computer device cannot normally operate, assigning the first task to run by the normally operating second computer device through a distributed architecture by the server. BRIEF DESCRIPTION OF DRAWINGS

[0015] Figure 1 is a system diagram illustrating a system for maintaining task operation continuity according to an embodiment of the present disclosure.

[0016] Figure 2 is a diagram illustrating a system for performing a backup task according to an embodiment of the present disclosure.

[0017] Figure 3 is a diagram illustrating a system for restoring a computer device according to an embodiment of the present disclosure. Figure 2

[0018] Figure 4 is a flowchart illustrating a method for maintaining task operation continuity according to an embodiment of the present disclosure.

[0019] Figure 5 is a flowchart illustrating a method for maintaining task operation continuity according to another embodiment of the present disclosure.

[0020]

List of reference numerals

[0021] 10: system

[0022] 11: server

[0023] C1-CM, C1': computer device

[0024] W: hardware input / output switch

[0025] D1-DN: controlled device

[0026] C21: preset end

[0027] C22: backup end

[0028] DT1, DT2: data

[0029] S410, S420, S510-S530: step DETAILED DESCRIPTION

[0030] Please refer to Figure 1 is a system diagram illustrating a system for maintaining task operation continuity according to an embodiment of the present disclosure.

[0031] In Figure 1 , the system 10 includes a server 11, computer devices C1-CM (M is a positive integer), a hardware input / output switch W, and controlled devices D1-DN (N is a positive integer), wherein the server 11 is communicatively coupled to the computer devices C1-CM and the hardware input / output switch W, and the hardware input / output switch W is communicatively coupled between the server 11, the computer devices C1-CM, and the controlled devices D1-DN.

[0032] ​In embodiments of the present disclosure, the server 11 is, for example, various smart devices and / or service devices, and can be used to manage the computer devices C1-CM and / or the hardware input / output switch W. In embodiments of the present disclosure, the server 11 can include a storage circuit and a processor. The storage circuit is, for example, any form of fixed or removable random access memory (RAM), read-only memory (ROM), flash memory, hard disk, or other similar devices or combinations of these devices, and can be used to record a plurality of program codes or modules.

[0033] The processor is coupled to the storage circuit, and can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in combination with a digit signal processor core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other kind of integrated circuit, a state machine, an advanced RISC machine (ARM) based processor, and the like.

[0034] In embodiments of the present disclosure, the processor can access the modules and program codes recorded in the storage circuit to implement the method for maintaining the continuity of task operation proposed by the present disclosure.

[0035] In some embodiments, the computer devices C1-CM can be industrial control computers individually, and can be used to perform the tasks assigned by the server 11. Figure 1 In embodiments of the present disclosure, the task assigned to the computer device C1 (hereinafter referred to as T1) is, for example, the exchange / transmission of data DT1 with the controlled device D1 (for example, a robot arm), so as to control the controlled device D1 to perform a corresponding behavior (for example, an assembly operation). Similarly, the task assigned to the computer device C2 (hereinafter referred to as T2) is, for example, the exchange / transmission of data DT2 with the controlled device D2 (for example, a robot arm), so as to control the controlled device D2 to perform a corresponding behavior (for example, a labeling operation or a locking operation). In addition, other computer devices can also control the corresponding controlled devices according to the assigned tasks.

[0036] In an embodiment, the server 11 can monitor the operation status of each computer device C1-CM, such as whether each computer device C1-CM is operating normally. In different embodiments, when a computer device has a failure (such as unable to boot, disconnection, etc.) that is sufficient to cause it to be unable to perform the assigned task normally, the server 11 can determine that the computer device is unable to operate normally, but the disclosure is not limited thereto.

[0037] In some embodiments, the server 11 can receive data and status of the tasks operated by each computer device C1-CM. For example, Figure 1 The computer device C1 in the above example can upload data and status of the task T1 to the server 11, and the computer device C2 can also upload data and status of the task T2 to the server 11, but the disclosure is not limited thereto.

[0038] In some embodiments, each computer device C1-CM can not store any data related to the assigned task itself, but the disclosure is not limited thereto.

[0039] In Figure 1 the above example, the server 11 can control the hardware input / output switch W to achieve data exchange between each computer device C1-CM and the corresponding controlled device. For example, in Figure 1 the above example, the server 11 can control the hardware input / output switch W to connect the computer device C1 to the corresponding controlled device D1, and control the hardware input / output switch W to connect the computer device C2 to the corresponding controlled device D2, but the disclosure is not limited thereto.

[0040] In an embodiment of the disclosure, each computer device C1-CM can have a preset end and a backup end. For ease of understanding, the following takes the computer device C2 as an example for illustration.

[0041] In Figure 1 the above example, the computer device C2 can have a preset end C21 and a backup end C22 (at least one), where the preset end C21 and the backup end C22 are each, for example, an Ethercat end, but the disclosure is not limited thereto. In this embodiment, the preset end C21 can be used, for example, to perform data exchange related to the task T2 assigned to the computer device C2. In the above example, the preset end C21 can be connected to the controlled device D2 through the hardware input / output switch W to exchange data DT2 with the controlled device D2, but the disclosure is not limited thereto.

[0042] In addition, when the computer device C2 is assigned to perform tasks originally performed by other computer devices, the backup end C22 can be used, for example, to perform data exchange of these tasks.

[0043] Please refer to Figure 2 , which is a schematic diagram of performing backup tasks according to an embodiment of the disclosure. InFigure 2 In the above embodiment, assume that the computer device CI fails to operate normally due to a malfunction or the like. In this case, the server 11 can assign the task Tl originally executed by the computer device CI to the computer device C2 operating normally to execute, and accordingly control the hardware input / output switch W to connect the backup end C22 of the computer device C2 to the controlled device Dl. In this case, the computer device C2 can exchange data DTl related to the task Tl with the controlled device Dl through the backup end C22, and the computer device C2 in this case can be understood as being assigned to execute a backup task, but can not be limited thereto.

[0044] In the above embodiment, when the computer device CI fails to operate normally, the server 11 can assign the task Tl originally executed by the computer device CI to the computer device C2 to execute, for example, through a distributed architecture. In an embodiment, the distributed architecture is, for example, a 61499 distributed architecture, but can not be limited thereto.

[0045] Similarly, other computer devices can also be configured with corresponding preset ends and backup end(s), and can operate in a mechanism similar to the above-mentioned disclosure, the details of which are not described herein.

[0046] In some embodiments, each computer device CI-CM can also be provided with a single end, and can exchange data related to the assigned task (including a backup task) through this end, but can not be limited thereto.

[0047] In the above embodiment, in order for the computer device C2 to successfully execute the task Tl originally assigned to the computer device CI to execute, the task Tl can be pre-deployed on the computer device C2. And since the computer device C2 is assigned to execute the task T2, the task T2 also needs to be deployed on the computer device C2.

[0048] That is, in addition to the task T2 originally assigned to the computer device C2 to execute, the task Tl also needs to be deployed on the computer device C2 to facilitate the execution of the related backup task, but can not be limited thereto.

[0049] In an embodiment of the present disclosure, the tasks deployed on each computer device CI-CM are, for example, in the form of Docker. Specifically, the content of each task can be packaged as a Docker image file through the relevant virtualization technology to run the environment and settings of the industrial control software. Thus, the computer device can still obtain the same result when assigned to execute a backup task.

[0050] For example, since computer device C2 has pre-deployed task T1 (e.g., a Docker image file), when computer device C2 is assigned to execute the corresponding backup task, computer device C2 can achieve the same result as when computer device C1 executes task T1 (e.g., controlling the assembly operation performed by controlled device D1).

[0051] In the embodiments of this disclosure, each computer device C1-CM can periodically or irregularly upload its own device configuration to the server 11, and the server 11 can store the device configuration of each computer device C1-CM at different points in time, but is not limited to this.

[0052] In some embodiments, when a computer device malfunctions, the maintenance personnel of system 10 can, for example, connect a new computer device to server 11 to replace it. In this case, server 11 can, for example, restore the new computer device based on the device configuration of the malfunctioning computer device, so that the new computer device has the same device configuration as the malfunctioning computer device. The following will be supplemented with... Figure 3 Further explanation is needed.

[0053] Please refer to Figure 3 It is based on Figure 2 A schematic diagram of a computer device for restoration is shown in the embodiment. Figure 3 In this scenario, assume that computer device C2 is exchanging data related to task T2 with controlled device D2 via preset terminal C21, and exchanging data related to task T1 with controlled device D1 via backup terminal C22. That is, computer device C2 is assigned to perform task T1 in place of computer device C1, which is not functioning properly.

[0054] In this case, assuming the new computer device C1' is connected to the server 11, the server 11 can restore the computer device C1' to the corresponding computer device C1 based on the device configuration that the computer device C1 previously uploaded to the server 11.

[0055] In one embodiment, computer device C1' is, for example, a device running FIDO device onboarding (FDO) protocol and is configured with a script to restore the device configuration corresponding to computer device C1. In this case, server 11 can, for example, restore computer device C1' to the configuration corresponding to computer device C1 based on the FIDO device onboarding protocol, thereby allowing computer device C1' to have the same configuration as computer device C1.

[0056] After the computer device C1' is restored to have the same configuration as the computer device C1, the computer device C1' will also present a state deployed with the task T1. In this case, the server 11 can assign the task T1 running on the computer device C2 to the computer device C1' to run through the distributed architecture (e.g., the 61499 distributed architecture).

[0057] In addition, the server 11 can control the hardware input / output switch W to connect (the preset end of) the computer device C1' to the controlled device D1. In this case, the computer device C1' can exchange (through its preset end) data DT1 related to the task T1 with the controlled device D1.

[0058] That is, when the computer device C1' used to replace the computer device C1 is connected to the server 11, the server 11 can restore the device configuration of the computer device C1 on the computer device C1'. Then, the server 11 can further assign the task T1 executed by the computer device C2 to the computer device C1' to continue executing the task T1 (e.g., control the controlled device D1 to perform the assembly work) by the computer device C1', but can not be limited to this.

[0059] In some embodiments, the connection between the computer device C1 and the server 11 can also be disconnected after the computer device C1 fails to operate normally (e.g., the computer device C1 is removed from the system 10).

[0060] Please refer to Figure 4 , which is a method flowchart for maintaining task operation continuity according to an embodiment of the present disclosure. The method of the present embodiment can be executed by the server 11 of Figures 1 to 3 , and the details of each step are described below in conjunction with the elements shown in Figures 1 to 3 . Figure 4

[0061] In step S410, the server 11 monitors the operation status of the first computer device (e.g., the computer device C1) and the second computer device (e.g., the computer device C2) respectively. In step S420, in response to determining that the first computer device fails to operate normally, the server 11 assigns the first task (e.g., the task T1) to the normally operating second computer device to run through the distributed architecture (e.g., the 61499 distributed architecture).

[0062] The details of steps S410 and S420 can refer to the related descriptions of the Figures 1 to 3 embodiment, which are not described here.

[0063] Please refer to Figure 5 , which is a method flowchart for maintaining task operation continuity according to another embodiment of the present disclosure.

[0064] In Figure 5 , in addition to​Figure 4 In addition to steps S410 and S420, the server 11 can further perform step S510 to receive the first computer device configuration from the first computer device (e.g., computer device C1) and receive the second computer device configuration from the second computer device (e.g., computer device C2).

[0065] After step S420, in step S520, in response to determining that the third computer device (e.g., computer device C1') is connected to the server 11, the server 11 restores the third computer device to correspond to the first computer device according to the first computer device configuration. Then, in step S530, the server 11 assigns the first task running on the second computer device to the third computer device to run through the distributed architecture.

[0066] Details of steps S510, S520, and S530 can also refer to the related descriptions of the embodiments of the present disclosure, which are not repeated here. Figures 1 to 3

[0067] In summary, when a computer device cannot perform the assigned task due to failure, disaster, or the like, the technical solution of the embodiments of the present disclosure can transfer the task to another computer device running normally through the distributed architecture to continue running. Therefore, the task can be avoided from being interrupted, thereby achieving the effect of maintaining the continuity of task operation.

[0068] In addition, when a new computer device is online, the technical solution of the embodiments of the present disclosure can also restore the device configuration of the failed computer device on the new computer device based on the FDO agreement, and transfer the above task back to the new computer device to execute. Therefore, the data security of the task can be guaranteed due to the secure encrypted channel and the late binding feature provided by the FDO agreement.

[0069] Although the present disclosure has been disclosed as above with embodiments, it is not intended to limit the present disclosure, and any person skilled in the art can make some changes and modifications without departing from the concept and scope of the present disclosure, so the protection scope of the present disclosure shall be subject to the definition of the claims.​

Claims

1. A system for maintaining the continuity of task operation, characterized in that, include: A server, communicatively coupled to a first computer device and a second computer device, and configured to: Monitor the individual operational status of the first computer device and the second computer device, wherein each of the first computer device and the second computer device is deployed with a first task in Docker format, and the first task is assigned to the first computer device for execution; and In response to the determination that the first computer device is not functioning properly, the first task is assigned to the second computer device that is functioning properly through a distributed architecture.

2. The system as described in claim 1, characterized in that, The distributed architecture mentioned above includes the 61499 distributed architecture.

3. The system as described in claim 1, characterized in that, The server receives data and status of its individual tasks from the first computer device and the second computer device.

4. The system as described in claim 1, characterized in that, The server is also configured to: Receive a first device configuration from the first computer device and a second device configuration from the second computer device; The system determines that a third computer device is connected to the server and restores the third computer device to the configuration corresponding to the first computer device based on the configuration of the first device. as well as The first task, which operates on the second computer device, is assigned to the third computer device for execution through the distributed architecture.

5. The system as described in claim 4, characterized in that, It also includes the third computer device, wherein the third computer device is a device running a FIDO device access protocol and is configured with a script to restore the device configuration corresponding to the first computer device; The server restores the third computer device to correspond to the first computer device based on the FIDO device network access protocol.

6. The system as described in claim 1, characterized in that, It also includes the first computer device and the second computer device, wherein the first computer device and the second computer device are further deployed with a second task having the Docker form, and the second task is assigned to the second computer device to run; The second computer device has a preset terminal and a backup terminal. The preset terminal is used to transmit data associated with the second task, and after the second computer device is assigned to run the first task, the second computer device transmits data associated with the first task through the backup terminal.

7. The system as described in claim 6, characterized in that, The preset terminal and the backup terminal of the second computer device are each an Ethercat terminal.

8. The system as described in claim 6, characterized in that, It also includes a hardware input / output switch coupled to the preset end and the backup end of the second computer device, and is used to transfer the data associated with the first task and the data associated with the second task to a corresponding first controlled device and a second controlled device, respectively.

9. The system as described in claim 8, characterized in that, After the first task running on the first computer device is assigned to the normally functioning second computer device through the distributed architecture, the server controls the hardware input / output switch to exchange the data associated with the first task between the first controlled device and the backup terminal of the second computer device.

10. A method for maintaining the continuity of task operation, characterized in that, include: A server, communicatively coupled to a first computer device and a second computer device, monitors the individual operational status of the first computer device and the second computer device, wherein each of the first computer device and the second computer device is deployed with at least one first task in Docker form, and the first task is assigned to be run by the first computer device; and In response to the determination that the first computer device is not functioning properly, the server assigns the first task to the second computer device that is functioning properly through a distributed architecture.

Images