Information processing system and information processing method

Abstract

To provide information processing means capable of early detecting an abnormality and improving reliability of application execution processing even in the case of an application including external processing.SOLUTION: In an information processing system that includes a plurality of application execution devices that execute applications, a central management device that manages the application execution devices, and an external device that instructs execution of a predetermined operation, the central management device receives first processing time information indicating a time to execute first processing from a first application execution device operating in a standby mode, determines that an abnormality has occurred in a second application execution device if second processing time information indicating a time to execute the first processing is not received from the second application execution device operating in an operation mode within a predetermined time after receiving the first processing time information, and changes the first application execution device from the standby mode to the operation mode to continue execution of the application.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an information processing system and an information processing method. [Background technology]

[0002] In today's rapidly changing business world, there is a demand for tools that allow users to quickly and efficiently build data flows while using trial and error in the hypothesis verification process.One such tool is a flow editor that allows users to define data flows without programming using a GUI (Graphical User Interface).

[0003] The flow editor provides a wide range of input / output interfaces, allowing users to create data flows as if combining blocks. This makes the editing environment more intuitive and easier to understand than traditional methods using programs or scripts, and it offers the advantages of being easy to use and highly productive, even for users without advanced technical knowledge.

[0004] Several proposals have been made regarding information processing means for providing a flow editor. For example, Japanese Patent No. 7013326 (Patent Document 1) describes an information processing system that executes software based on a data flow edited by a flow editor, the information processing system including a plurality of information processing devices constituting a cluster that performs distributed processing of the software, the data flow including a distributed processing start block that is a block that starts distributed processing, a distributed processing end block that is a block that ends distributed processing, and a distributed processing target block that is a block written between the distributed processing start block and the distributed processing end block, the master device being the information processing device constituting the cluster, when it reaches the distributed processing start block during execution of the data flow, sends a message including an execution instruction for the distributed processing target block to a plurality of worker devices constituting the cluster, each of which executes the distributed processing target block upon receiving the message and sends a message including the execution result of the distributed processing target block to the master device, the master device receiving the execution result from the plurality of worker devices, executes the block of the data flow that follows the distributed processing end block. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent No. 7013326 Summary of the Invention [Problem to be solved by the invention]

[0006] Patent Document 1 describes a means for executing a predetermined processing task using multiple process control tools (AP execution devices). In the means described in Patent Document 1, an application created by a flow editor and defined by multiple linked processing blocks is executed within each AP execution device. When processing in a specific AP execution device ends, that AP execution device notifies other AP execution devices of this fact. Meanwhile, if an abnormality occurs in a specific AP execution device and the processing does not end normally, the other AP execution devices that were waiting will restart the processing that did not end normally from the beginning. According to the means described in Patent Document 1, the reliability of application execution can be improved by using a plurality of process control tools (AP execution devices).

[0007] However, while the means described in Patent Document 1 focuses on internal processing that is completed within the AP execution device, in reality, the data flow of an application may include not only internal processing but also external processing that requires communication with an external device. Although Patent Document 1 describes information processing means for applications that include only internal processing, it does not consider how to handle applications that include external processing. These external processes may, for example, define instructions to control robots or machines that perform production processes. Therefore, if the information processing means described in Patent Document 1 is applied to an application that includes external processes, a process that did not end normally may be re-executed from the beginning, causing the external device to execute the same processing task multiple times, which may cause disruptions in the production line.

[0008] Furthermore, in the method described in Patent Document 1, whether or not processing has completed normally is determined at the final end block of the data flow, which poses a problem of delayed detection of abnormalities that occur midway through the data flow.

[0009] Therefore, an object of the present disclosure is to provide an information processing means that can detect abnormalities early and improve the reliability of application execution processing, even in the case of an application that includes external processing. [Means for solving the problem]

[0010] In order to solve the above-mentioned problems, one representative information processing system of the present invention is an information processing system in which a plurality of application execution devices executing applications based on a data flow in parallel, a central management device that manages the plurality of application execution devices, and an external device that performs predetermined operations based on commands from the application execution devices are connected via a communication network, wherein the application includes internal processing that is executed within the application execution device and external processing that requires communication with the external device, and the application execution device has an operating mode in which, when executing the external processing of the application, it sends command information to the external device instructing the execution of the predetermined operation and receives output information from the external device, and an operating mode in which, when executing the external processing of the application, it sends command information to the external device instructing the execution of the predetermined operation and receives output information from the external device. and a standby mode in which the central management device first receives, from a first application execution device operating in the standby mode, first processing time information indicating a time for the first process to be executed in the first application execution device, and, if the central management device does not receive, from a second application execution device operating in the operating mode, second processing time information indicating a time for the first process to be executed in the second application execution device within a predetermined time after receiving the first processing time information, determines that an abnormality has occurred in the second application execution device, and, if it has determined that an abnormality has occurred in the second application execution device, changes the first application execution device from the standby mode to the operating mode and causes the execution of the application to continue. [Effects of the Invention]

[0011] According to the present invention, it is possible to provide information processing means that can detect abnormalities early and improve the reliability of application execution processing, even in the case of an application that includes external processing. Other objects, configurations, and effects will become apparent from the following description of the preferred embodiments of the present invention. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 illustrates a computer system for implementing an embodiment of the present disclosure. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of an information processing system according to an embodiment of the present disclosure. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of a central management device according to an embodiment of the present disclosure. [Figure 4] FIG. 4 is a diagram illustrating an example of the configuration of an application execution device according to an embodiment of the present disclosure. [Figure 5] FIG. 5 is a diagram illustrating an example of the configuration of an external device according to an embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram illustrating an example of the configuration of a cluster management unit according to an embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram illustrating an example of the configuration of the application execution synchronization management unit according to an embodiment of the present disclosure. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of the flow edit management unit according to an embodiment of the present disclosure. [Figure 9] FIG. 9 is a diagram illustrating an example of the configuration of the application executing unit according to an embodiment of the present disclosure. [Figure 10] FIG. 10 is a diagram illustrating an example of a data flow according to an embodiment of the present disclosure. [Figure 11] FIG. 11 is a diagram illustrating an example of the flow of an application execution process in the information processing system according to an embodiment of the present disclosure. [Figure 12] FIG. 12 is a diagram illustrating a specific example of normal application execution processing in the information processing system according to an embodiment of the present disclosure. [Figure 13] FIG. 13 is a diagram illustrating an example of the flow of an abnormality handling process when an abnormality occurs during internal processing of the application execution process according to an embodiment of the present disclosure. [Figure 14]FIG. 14 is a diagram illustrating an example of the flow of an abnormality handling process when an abnormality occurs during processing outside the application execution process according to an embodiment of the present disclosure. [Figure 15] FIG. 15 is a diagram showing the flow of an abnormality handling process when an abnormality occurs after processing outside the application execution process according to the embodiment of the present disclosure. [Figure 16] FIG. 16 is a diagram illustrating an example of the flow of an application execution process in the application execution device of the operation section according to an embodiment of the present disclosure. [Figure 17] FIG. 17 is a diagram illustrating an example of the flow of management processing in the central management device according to an embodiment of the present disclosure. [Figure 18] FIG. 18 is a diagram illustrating an example of the flow of an external device process according to an embodiment of the present disclosure. [Figure 19] FIG. 19 is a diagram showing the flow of data transfer in the application execution device information processing system according to an embodiment of the present disclosure in the case of normal external processing. [Figure 20] FIG. 20 is a diagram showing a flow of data transfer in the information processing system when an abnormality occurs during external processing in the application execution processing according to an embodiment of the present disclosure. [Figure 21] FIG. 21 is a diagram illustrating a flow of data transfer in the information processing system when an abnormality occurs after external processing in the application execution processing according to an embodiment of the present disclosure. [Figure 22] FIG. 22 is a diagram illustrating a processing time information management table according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the present invention is not limited to this embodiment. In addition, in the description of the drawings, the same parts are designated by the same reference numerals. Furthermore, although terms such as "first," "second," and "third" may be used to describe various elements or components in this disclosure, it will be understood that these elements or components should not be limited by these terms. These terms are used only to distinguish one element or component from another. Thus, a first element or component discussed below could also be referred to as a second element or component without departing from the teachings of the inventive concept.

[0014] Background of the Disclosure In recent years, traditional process management tools (such as programmable logic controllers) used to control automated operations in production plants and other facilities are becoming legacy tools, with limited compatibility with artificial intelligence, IoT, and the latest programming languages. Furthermore, traditional process management tools are complex and require specialized knowledge to operate, placing a significant burden on users. Given these factors, new process management tools that improve efficiency and reliability are needed.

[0015] Therefore, edge devices such as microcontrollers are attracting attention as tools that provide flow editors that are compatible with artificial intelligence, IoT, and the latest programming languages ​​and allow users to easily create data flows as if combining blocks. However, compared to conventional processing management tools, edge devices such as microcontrollers are not designed for the environments in which they are used, and therefore have limited durability. Depending on the environmental conditions, they may experience problems such as memory failure or thermal runaway. Therefore, there is a need for a means to improve the reliability of application processes executed by process management tools.

[0016] As described above, for example, Patent Document 1 proposes improving the reliability of application execution by using a plurality of process control tools (AP execution devices). However, the means described in Patent Document 1 does not take into account applications that include external processing that requires communication with external devices, and since whether the processing has completed successfully is determined at the last end block of the data flow, there is a problem that detection of abnormalities that occur during the data flow is delayed.

[0017] Therefore, the present disclosure relates to providing an information processing means that can detect an abnormality early and improve the reliability of application execution processing, even in the case of an application that includes external processing.

[0018] First, referring to Figure 1, a computer system 100 for implementing embodiments of the present disclosure will be described. The mechanisms and devices of various embodiments disclosed herein may be applied to any suitable computing system. The main components of the computer system 100 include one or more processors 102, memory 104, a terminal interface 112, a storage interface 113, an I / O (input / output) device interface 114, and a network interface 115. These components may be interconnected via a memory bus 106, an I / O bus 108, a bus interface unit 109, and an I / O bus interface unit 110.

[0019] Computer system 100 may include one or more general-purpose programmable central processing units (CPUs) 102A and 102B, collectively referred to as processors 102. In some embodiments, computer system 100 may include multiple processors, while in other embodiments, computer system 100 may be a single CPU system. Each processor 102 executes instructions stored in memory 104 and may include an on-board cache.

[0020] In one embodiment, memory 104 may include random-access semiconductor memory, storage devices, or storage media (either volatile or non-volatile) for storing data and programs. Memory 104 may store all or part of the programs, modules, and data structures that perform the functions described herein. For example, memory 104 may store information processing application 150. In one embodiment, information processing application 150 may include instructions or descriptions that execute the functions described below on processor 102.

[0021] In some embodiments, information processing application 150 may be implemented in hardware via semiconductor devices, chips, logic gates, circuits, circuit cards, and / or other physical hardware devices instead of or in addition to a processor-based system. In some embodiments, information processing application 150 may include data other than instructions or descriptions. In some embodiments, cameras, sensors, or other data input devices (not shown) may be provided to communicate directly with bus interface unit 109, processor 102, or other hardware in computer system 100.

[0022] Computer system 100 may include a bus interface unit 109 that facilitates communication between processor 102, memory 104, display system 124, and I / O bus interface unit 110. I / O bus interface unit 110 may couple to an I / O bus 108 for transferring data to and from various I / O units. I / O bus interface unit 110 may communicate via I / O bus 108 with multiple I / O interface units 112, 113, 114, and 115, also known as I / O processors (IOPs) or I / O adapters (IOAs).

[0023] Display system 124 may include a display controller, a display memory, or both. The display controller may provide video, audio, or both data to display device 126. Computer system 100 may also include one or more sensors or other devices configured to collect data and provide the data to processor 102.

[0024] For example, computer system 100 may include biometric sensors that collect heart rate data, stress level data, etc., environmental sensors that collect humidity data, temperature data, pressure data, etc., and motion sensors that collect acceleration data, movement data, etc. Other types of sensors may also be used. Display system 124 may be connected to a display device 126, such as a standalone display screen, a television, a tablet, or a handheld device.

[0025] The I / O interface unit provides functionality for communicating with various storage or I / O devices. For example, the terminal interface unit 112 may be attached to user I / O devices 116, such as user output devices such as a video display, a television with speakers, and user input devices such as a keyboard, a mouse, a keypad, a touchpad, a trackball, buttons, a light pen, or other pointing device. A user may use a user interface to enter input data or instructions into the user I / O devices 116 and the computer system 100, and receive output data from the computer system 100, by operating the user input devices. The user interface may be displayed on a display, played through speakers, or printed via a printer via the user I / O devices 116, for example.

[0026] Storage interface 113 allows attachment of one or more disk drives or direct access storage device 117 (typically a magnetic disk drive storage device, but may also be an array of disk drives or other storage devices configured to appear as a single disk drive). In some embodiments, storage device 117 may be implemented as any secondary storage device. The contents of memory 104 may be stored in storage device 117 and retrieved as needed from storage device 117. I / O device interface 114 may provide an interface to other I / O devices, such as printers, fax machines, etc. Network interface 115 may provide a communications path that allows computer system 100 and other devices to communicate with each other. This communications path may be, for example, network 130.

[0027] In some embodiments, computer system 100 may be a device that receives requests from other computer systems (clients) without a direct user interface, such as a multi-user mainframe computer system, a single-user system, or a server computer. In other embodiments, computer system 100 may be a desktop computer, a portable computer, a laptop, a tablet computer, a pocket computer, a telephone, a smartphone, or any other suitable electronic device.

[0028] Next, with reference to FIG. 2, a configuration of an information processing system according to an embodiment of the present disclosure will be described.

[0029] Fig. 2 is a diagram illustrating an example of the configuration of an information processing system 200 according to an embodiment of the present disclosure. Information processing system 200 is an information processing system that is capable of early detection of anomalies in the execution processing of an application (hereinafter referred to as an "app") based on a data flow edited by a flow editor and promptly taking measures to deal with the anomaly, and as shown in Fig. 2, includes a central management device 210, a first app execution device 220, a second app execution device 230, an external device 240, and a communication network 250. In information processing system 200, central management device 210, first app execution device 220, second app execution device 230, and external device 240 may be connected via communication network 250 to transmit and receive data based on a standard communication protocol. 2 may be implemented as computer system 100 shown in Fig. 1. In this case, computer system 100 executes information processing application 150 that fulfills the functions of first application execution device 220, second application execution device 230, and external device 240, thereby functioning as an information processing device that performs the information processing means according to an embodiment of the present disclosure.

[0030] Central management device 210 is a device that manages first application execution device 220, second application execution device 230, and external device 240, and detects abnormalities in application execution processing. As shown in Fig. 2, central management device 210 includes at least a cluster management unit 211 and an application execution synchronization management unit 212.

[0031] Cluster management unit 211 is a functional unit for managing application execution device cluster 215, which includes first application execution device 220, second application execution device 230, etc. Cluster management unit 211 detects abnormalities in the application execution processes executed by application execution devices 220, 230 included in application execution device cluster 215, and can switch the operating mode of the application execution devices as a countermeasure to the detected abnormality.

[0032] The application execution synchronization management unit 212 is a functional unit that manages processing time information relating to application execution processing by each application execution device included in the application execution device cluster 215, and synchronizes the application execution processing.

[0033] The application execution device cluster 215 is a logical group including a plurality of application execution devices, such as a first application execution device 220 and a second application execution device 230. For convenience of explanation, Fig. 2 shows an example in which two application execution devices, such as a first application execution device 220 and a second application execution device 230, are included, but the present disclosure is not limited to this, and any number of application execution devices may be included.

[0034] The first application execution device 220 and the second application execution device 230 are devices for executing applications based on data flows created by so-called flow editors (e.g., flow editing management units 221 and 231, which will be described later). In an embodiment, the first application execution device 220 and the second application execution device 230 may be configured to operate in either an active mode or a standby mode.

[0035] In principle, one of the multiple application execution devices included in application execution device cluster 215 is set to operate in active mode, and the other application execution devices are set to operate in standby mode. For ease of explanation, the following description will be given as an example in which first application execution device 220 is set to operate as an "active" application execution device operating in active mode, and second application execution device 230 is set to operate as a "standby" application execution device operating in standby mode.

[0036] The operating mode here refers to an operation mode in which, when executing an external process included in the application execution process, an external message including input data to the external device 240 is sent to the external device 240, and output data is directly received from the external device 240. This input data may include, for example, command information that instructs the external device 240 to execute a predetermined operation. The standby mode here refers to an operating mode in which, when executing an external process included in the application execution process, an external message including input data to external device 240 is not sent to external device 240, but waits until output data from external device 240 is received via central management device 210. As will be described later, an application execution device set to the standby mode may be changed to the operating mode and used as a spare application execution device to become a new operating application execution device, for example, when an abnormality occurs in the operating application execution device.

[0037] As shown in FIG. 2, the first application execution device 220 and the second application execution device 230 include flow edit management units 221 and 231 and application execution units 222 and 232, respectively.

[0038] The flow editing management units 221 and 231 are functional units for creating and editing data flows for executing predetermined tasks (such as production management). In one embodiment, the flow editing management units 221 and 231 may be so-called flow editors that provide a GUI for creating and editing data flows by combining blocks that represent specific steps in a task.

[0039] The application execution units 222 and 232 are functional units for executing, as an application, the data flow created by the flow edit management unit 221. The application execution process for executing this application may be composed of internal processing performed within the application execution device and external processing requiring communication with an external device 240, which will be described later.

[0040] The external device 240 is a device used in the application execution process executed by the application execution units 222 and 232. When an external process in the application execution process is performed, the external device 240 receives input data from the application execution device in the operation section, operates based on the input data, and then transmits output data to the application execution device in the operation section and the central management device 210. As an example, when the information processing system 200 according to an embodiment of the present disclosure is applied to production work in a factory, the external device 240 may be, for example, a robot or machine for performing a specific production process.

[0041] The communication network 250 is a communication infrastructure that realizes communication in accordance with a specified communication protocol such as Ethernet (registered trademark) or TCP / IP, and may be, for example, a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, a dedicated line, a public communication network, etc.

[0042] According to the information processing system 200 described above, it is possible to provide an information processing means that can quickly detect abnormalities in the execution processing of an application based on a data flow edited by a flow editor and quickly take measures to deal with the abnormality.

[0043] Next, the configuration of the central management device according to the embodiment of the present disclosure will be described with reference to FIG.

[0044] 3 is a diagram illustrating an example of the configuration of central management device 210 according to an embodiment of the present disclosure. As described above, central management device 210 is a device that manages first application execution device 220, second application execution device 230, and external device 240, and detects abnormalities in application execution processing. As shown in FIG. 3, central management device 210 mainly includes a cluster management unit 211, an application execution synchronization management unit 212, a storage unit 305, and a communication unit 310.

[0045] The cluster management unit 211 is a functional unit for managing an application execution device cluster (for example, the application execution device cluster 215 shown in FIG. 2) including the first application execution device 220, the second application execution device 230, and so on. The detailed configuration of the cluster management unit 211 will be described later, and therefore will not be described here.

[0046] The application execution synchronization management unit 212 is a functional unit that manages processing time information relating to application execution processing by each application execution device included in the application execution device cluster 215, and synchronizes the application execution processing. The detailed configuration of the application execution synchronization management unit 212 will be described later, and therefore will not be described here.

[0047] The memory unit 305 is a storage area for storing various data used by the central management device 210. The memory unit 305 may also store processing data 306. This processing data 306 is data used by the central management device 210, and may include, for example, data related to the applications being executed by the first application execution device 220 and the second application execution device 230, output data from the external device 240, and the like.

[0048] Communication unit 310 is a functional unit for performing data communication among central management device 210, first application execution device 220, second application execution device 230, and external device 240. More specifically, as shown in Fig. 3, communication unit 310 may include a processing data acquisition unit 312 for acquiring processing data 306 from first application execution device 220, second application execution device 230, and external device 240, and a processing data transfer unit 314 for transferring the acquired processing data 306 to first application execution device 220, second application execution device 230, and external device 240.

[0049] Next, an application execution device according to an embodiment of the present disclosure will be described with reference to FIG.

[0050] 4 is a diagram illustrating an example of the configuration of an application execution device 400 according to an embodiment of the present disclosure. The application execution device 400 is a device for executing an application based on a data flow created by a so-called flow editor. As described above, the application execution device 400 may be set to operate in either an active mode or a standby mode. The application execution device 400 shown in FIG. 4 may be used as the first application execution device 220 or the second application execution device 230 shown in FIG.

[0051] As shown in FIG. 4, the application execution device includes a flow edit management unit 402, an application execution unit 404, a storage unit 405, a communication unit 410, and an instruction processing management unit 420.

[0052] Flow edit management unit 402 is a functional unit for creating and editing a data flow for executing a predetermined task (such as production management). Flow edit management unit 402 shown in Fig. 4 substantially corresponds to flow edit management unit 221 of first application execution device 220 and flow edit management unit 231 of second application execution device 230 shown in Fig. 2.

[0053] The application execution unit 404 is a functional unit for executing, as an application, the data flow created by the flow edit management unit 402. The application execution unit 404 shown in Fig. 4 substantially corresponds to the application execution unit 222 of the first application execution device 220 and the application execution unit 232 of the second application execution device 230 shown in Fig. 2. The application execution unit 404 will be described in detail later, and therefore will not be described here.

[0054] Memory unit 405 is a storage area for storing various data used by application execution device 400. Memory unit 405 may also store processing data 406. This processing data 406 is data used by application execution device 400, and may include, for example, data related to the application, input data to be transmitted to external device 240, output data from external device 240, and the like.

[0055] The communication unit 410 is a functional unit for performing data communication between the central management device 210, each application execution device included in the application execution device cluster 215, and the external device 240. More specifically, as shown in Fig. 4, the communication unit 410 may include a processing data acquisition unit 412 for acquiring processing data 406 from the central management device 210 or the external device 240, and a processing data transfer unit 414 for transferring the acquired processing data 406 to the central management device 210 or the external device 240.

[0056] The instruction processing management unit 420 is a functional unit for performing instruction processing (Message Processing) in application execution processing for executing an application. More specifically, the instruction processing management unit 420 may include an instruction configuration management unit 422 that configures the instruction processing, and an instruction processing calculation unit 424 that performs calculations for the instruction processing. In one embodiment, the instruction processing manager 420 may be configured to perform Transmission Control Protocol / Internet Protocol (TCP / IP), Message Queuing Telemetry Transport (MQTT), or Websocket Message Processing.

[0057] Next, the configuration of the external device according to the embodiment of the present disclosure will be described with reference to FIG.

[0058] 5 is a diagram illustrating an example of a configuration of the external device 240 according to an embodiment of the present disclosure. As described above, the external device 240 is a device used in the application execution process executed by the application execution units 222 and 232. As shown in FIG. 5, the external device 240 mainly includes a storage unit 505, a communication unit 510, an operation execution unit 522, and an operation status monitoring unit 524.

[0059] Memory unit 505 is a storage area for storing various data used by external device 240. Memory unit 505 may also store processing data 506. This processing data 506 is data used by external device 240, and may include, for example, input data from first application execution device 220 and second application execution device 230, output data generated by external device 240, and the like.

[0060] The communication unit 510 is a functional unit for performing data communication between the central management device 210, the first application execution device 220, and the second application execution device 230. More specifically, as shown in Fig. 5, the communication unit 510 may include a processing data acquisition unit 512 for acquiring processing data 506 from the central management device 210, the first application execution device 220, and the second application execution device 230, and a processing data transfer unit 514 for transferring the acquired processing data 506 to the central management device 210 or the external device 240.

[0061] The operation execution unit 522 is a functional unit for executing a predetermined operation based on input data acquired from the first application execution device 220 or the second application execution device 230 (the operation application execution device). The operation here may include any action, such as a processing task for processing data or an operation for moving parts. As an example, the operation execution unit 522 may be used to execute a predetermined production process, such as assembling parts or packaging products.

[0062] The operation status monitoring unit 524 is a functional unit for acquiring information regarding the status of the operation being executed by the operation executing unit 522. The operation status monitoring unit 524 may be a sensor device such as a motion sensor or a camera. In one embodiment, the operation status monitoring unit 524 may acquire data regarding the progress status of the operation (not started, in progress, completed) and the result of the operation, and transmit the data as output data to the application executing device of the operation unit or the central management device 210 via the processing data transfer unit 514.

[0063] Next, the configuration of the cluster management unit according to an embodiment of the present disclosure will be described with reference to FIG.

[0064] 6 is a diagram illustrating an example of the configuration of the cluster management unit 211 according to an embodiment of the present disclosure. As described above, the cluster management unit 211 is a functional unit for managing an application execution device cluster including a first application execution device 220, a second application execution device 230, etc., and as shown in FIG. 6, it mainly includes a cluster configuration management unit 610, a cluster operation status monitoring unit 612, an abnormality detection unit 614, an operation mode management unit 616, and a storage unit 605.

[0065] The cluster configuration management unit 610 is a functional unit for managing the configuration of the application execution devices included in the application execution device cluster (information for identifying each application execution device, etc.). The cluster operating status monitor 612 is a functional unit for managing the operating status (whether in operating mode or standby mode, etc.) of the application execution devices included in the application execution device cluster.

[0066] Anomaly detection unit 614 is a functional unit for detecting an abnormality in the application execution process executed by an application execution device included in the application execution device cluster. In one embodiment, abnormality detection unit 614 may detect an abnormality in the application execution process based on time information indicating the start time of the application execution process executed in each application execution device or output data from external device 240.

[0067] The operation mode management unit 616 is a functional unit for changing the operation mode of an application execution device included in an application execution device cluster. In one embodiment, when an abnormality is detected in an application execution device operating in active mode (i.e., an application execution device in the active mode), the operation mode management unit 616 may change an application execution device operating in standby mode (i.e., an application execution device in the standby mode) to active mode. This allows external communication during application execution processing to continue uninterrupted.

[0068] The memory unit 605 is a storage area for storing various data used by the cluster management unit 211. The memory unit 605 may also store processing data 606. This processing data 606 is data used by the cluster management unit 211, and may include, for example, processing time information indicating the start time of an application execution process executed in each application execution device, information indicating the operating mode of each application execution device, an operating mode change instruction for changing the operating mode of a specific application execution device, and the like.

[0069] Next, an application execution synchronization management unit according to an embodiment of the present disclosure will be described with reference to FIG.

[0070] 7 is a diagram illustrating an example of the configuration of the application execution synchronization management unit 212 according to an embodiment of the present disclosure. As described above, the application execution synchronization management unit 212 is a functional unit that manages processing time information related to application execution processing by each application execution device included in the application execution device cluster 215 and synchronizes the application execution processing. As shown in FIG. 7, the application execution synchronization management unit 212 mainly includes an application execution management unit 710, a pause / resume unit 712, a processing time information management unit 714, a data sharing unit 716, and a storage unit 720.

[0071] The application execution management unit 710 is a functional unit for managing application execution processing by each application execution device included in the application execution device cluster 215. For example, the application execution management unit 710 may control each application execution device included in the application execution device cluster 215 so that each application execution device starts application execution processing simultaneously and executes the processing in parallel.

[0072] The pause / resume unit 712 is a functional unit for pausing and resuming the application execution processing by each application execution device included in the application execution device cluster 215. In one embodiment, when an operating application execution device performs external communication with the external device 240 (i.e., after transmitting input data to the external device 240), the pause / resume unit 712 pauses the application execution processing in the application execution device. Thereafter, after the operating application execution device has finished external communication with the external device 240 and each application execution device has received output data from the external device 240, the pause / resume unit 712 may resume the application execution processing in the application execution device. This makes it possible to prevent the timing of application execution processes in the operating application execution device and the standby application execution device from being out of sync due to external communication.

[0073] The processing time information management unit 714 is a functional unit for acquiring and managing processing time information indicating the start time of application execution processing by each application execution device included in the application execution device cluster 215. As described above, the abnormality detection unit 614 in the cluster management unit 211 can determine whether an abnormality has occurred in the application execution processing by a specific application execution device based on this processing time information.

[0074] The data sharing unit 716 is a functional unit for sharing output data acquired from the external device 240 with the application execution devices in the waiting group. In one embodiment, when the application execution device in the operating group performs external communication with the external device 240, the data sharing unit 716 may acquire output data from the external device 240 and transfer the acquired output data to the application execution devices in the waiting group included in the application execution device cluster 215. In this way, each application execution device can acquire the output data required for the next process and execute subsequent processes in parallel.

[0075] The memory unit 720 is a storage area for storing various data used by the application execution synchronization management unit 212. The memory unit 720 may store processing data 721. This processing data 721 is data used by the application execution synchronization management unit 212, and may include, for example, processing time information indicating the start time of an application execution process executed in each application execution device, and output data acquired from the external device 240.

[0076] Next, a flow edit management unit according to an embodiment of the present disclosure will be described with reference to FIG.

[0077] 8 is a diagram illustrating an example of the configuration of a flow edit management unit 402 according to an embodiment of the present disclosure. The flow edit management unit 402 is a functional unit for creating and editing a data flow for executing a predetermined task. The flow edit management unit 402 illustrated in FIG. 8 substantially corresponds to the flow edit management unit 221 of the first application execution device 220 and the flow edit management unit 231 of the second application execution device 230 illustrated in FIG. 2.

[0078] As shown in FIG. 8, the flow editing management unit 402 mainly includes a flow editing unit 810 and a storage unit 820.

[0079] The flow editing unit 810 is a functional unit for creating a data flow, and includes a flow editing environment 812 and a flow file transfer unit 814 as shown in FIG. The flow editing environment 812 is a functional unit that provides the user with an interactive editing environment for data flows using a flow editor. Using the GUI of the flow editing environment 812, the user can create and edit data flows by combining blocks that represent specific steps in a task. The flow file transfer unit 814 is a functional unit for transferring a flow file 821, which is a file describing the substance of the data flow (the logic of the application) created by the flow editing environment 812. The flow file transfer unit 814 may transfer the flow file defining the data flow created by the flow editing environment 812 to, for example, the application execution unit 404.

[0080] The storage unit 820 is a storage area for storing various data used by the flow edit management unit 402. The storage unit 820 may store a flow file 821.

[0081] Next, the application execution unit according to the embodiment of the present disclosure will be described with reference to FIG.

[0082] 9 is a diagram illustrating an example of the configuration of the application execution unit 404 according to an embodiment of the present disclosure. As described above, the application execution unit 404 is a functional unit for executing, as an application, a data flow created by the flow edit management unit 402. As shown in FIG. 4, the application execution unit 404 mainly includes a flow processing unit 910 and a storage unit 930.

[0083] The flow processing unit 910 is a functional unit for executing a data flow, and includes an internal instruction processing unit 912 and an external instruction processing unit 914 as shown in FIG. The flow processing unit 910 can execute a data flow (i.e., a flow file) as an application by sequentially processing the blocks included in the data flow. As described above, the data flow constituting an application may be composed of blocks that define internal processing performed within the application execution device and blocks that define external processing that requires communication with the external device 240. The internal instruction processing unit 912 is a functional unit for executing internal processing defined in a data flow block. The external instruction processing unit 914 is a functional unit for executing external processing defined in a data flow block.

[0084] The memory unit 930 is a storage area for storing various data used by the application execution unit 404. The memory unit 930 may store a flow file 931 that defines a data flow.

[0085] Next, a data flow according to an embodiment of the present disclosure will be described with reference to FIG.

[0086] 10 is a diagram illustrating an example of a data flow 1000 according to an embodiment of the present disclosure. This data flow 1000 is a data structure generated by the flow editor provided by the flow editing management unit 402 described above. More specifically, the data flow 1000 is illustrated as a description of the processing flow (logic) of an application for executing a predetermined task, as a structure in which multiple blocks (also referred to as nodes) shown in rectangular frames are connected by connecting lines (also referred to as links) shown as arrows.

[0087] As shown in FIG. 10, data flow 1000 may include one or more input data blocks 1001, one or more pre-processing blocks 1002, one or more processing target blocks 1003, one or more post-processing blocks 1005, and one or more output data blocks 1006.

[0088] The input data block 1001 is a block that includes logic for acquiring input data to be processed. The pre-processing block 1002 is a block that includes logic for performing pre-processing on the input data acquired by the input data block 1001 (logic for converting the input data into data in a predetermined format, etc.).

[0089] The processing block 1003 is a block including logic for performing predetermined processing on the input data acquired by the input data block 1001. As described above, the processing block 1003 may be an internal processing block that defines internal processing performed within the application execution device, or an external processing block 1004 that defines external processing that requires communication with an external device 240. The post-processing block 1005 is a block including, for example, logic for performing post-processing on the data generated in the processing block 1003 (such as logic for converting the generated data into data in a predetermined format). The output data block 1006 is a block including logic for transferring the output data obtained in the post-processing block 1005 to a predetermined transfer destination (external device 240, central management device 210, etc.).

[0090] Next, with reference to FIG. 11, an application execution process in the information processing system according to an embodiment of the present disclosure will be described.

[0091] 11 is a diagram showing an example of the flow of application execution processing in an information processing system according to an embodiment of the present disclosure. More specifically, FIG. 11 shows the flow of application execution processing in an application execution device information processing system including a central management device 210, a first application execution device 220, a second application execution device 230, a third application execution device 235, and an external device 240. Here, an example will be described in which the first application execution device 220 is an operating device set in an operating mode, and the second application execution device 230 and the third application execution device 235 are standby devices set in a standby mode.

[0092] 11, the application execution units of first application execution device 220, second application execution device 230, and third application execution device 235 each execute application processing based on a data flow consisting of multiple processing blocks (A, B, C, D) that define a specific process. As described above, this application execution processing may be composed of internal processing performed within the application execution device and external processing that requires communication with external device 240, which will be described later.

[0093] As described above, the application execution processes executed by the application executing units of first application execution device 220, second application execution device 230, and third application execution device 235 are processes based on the same data flow. Furthermore, the application execution processes are synchronized with each other and executed in parallel in first application execution device 220, second application execution device 230, and third application execution device 235.

[0094] When an external process occurs during the application execution process, the first application execution device 220, which is the application execution device in charge of operation, transmits processing time information indicating the time to execute the external process to the central management device 210, and also transfers an external message including input data to the external device 240.

[0095] Next, application execution synchronization management unit 212 of central management device 210 receives processing time information indicating the time for executing external processing from first application execution device 220, second application execution device 230, and third application execution device 235, and then transmits a pause instruction (not illustrated in FIG. 19 ) to pause application execution processing in first application execution device 220, second application execution device 230, and third application execution device 235. As a result, application execution processing in first application execution device 220, second application execution device 230, and third application execution device 235 is paused until output data is transmitted from external device 240.

[0096] Next, the external device 240 receives input data from the first application execution device 220, performs a predetermined operation based on the acquired input data, and then transmits a message including output data to the first application execution device 220, which is the application execution device in charge of operation, and to the central management device 210.

[0097] Next, central management device 210 receives the output data from external device 240 and transfers the acquired output data to second application execution device 230 and third application execution device 235, which are on standby. After that, application execution synchronization management unit 212 of central management device 210 confirms that second application execution device 230 and third application execution device 235 have received the output data, and then transmits a resume instruction (not shown in FIG. 11 ) to resume application execution processing in first application execution device 220, second application execution device 230, and third application execution device 235.

[0098] Next, when the application execution units of first application execution device 220, second application execution device 230, and third application execution device 235 each start the next process in the data flow, they transmit processing time information indicating the time at which the process started to central management device 210. Application execution synchronization management unit 212 of central management device 210 stores the processing time information acquired from each application execution device. As will be described later, cluster management unit 211 of central management device 210 can detect an abnormality that has occurred in the application execution process of a specific application execution device based on this processing time information.

[0099] Next, a specific example of normal application execution processing in the information processing system according to an embodiment of the present disclosure will be described with reference to FIG.

[0100] 12 is a diagram showing a specific example of normal application execution processing in an information processing system according to an embodiment of the present disclosure. More specifically, FIG. 12 shows the flow of normal application execution processing in an application execution device information processing system including central management device 210, first application execution device 220, second application execution device 230, and external device 240. Here, the case where the first application execution device 220 is an operating device set in an operating mode, and the second application execution device 230 is a standby device set in a standby mode will be described as an example.

[0101] The same application execution process 1200 is executed in parallel in the first application execution device 220 and the second application execution device 230. As shown in Fig. 12, this application execution process 1200 is made up of an internal process 1201, an internal process 1202, an external process 1203, and an internal process 1204.

[0102] First, the first application execution device 220 transmits processing time information 1211A indicating the time to start the internal processing 1201 to the central management device 210, and then performs the internal processing 1201. Similarly, the second application execution device 230 transmits processing time information 1211B indicating the time to start the internal processing 1201 to the central management device 210, and then performs the internal processing 1201.

[0103] Next, the first application execution device 220 transmits processing time information 1212A indicating the time to start the internal processing 1202 to the central management device 210, and performs the internal processing 1202. Similarly, the second application execution device 230 transmits processing time information 1212B indicating the time to start the internal processing 1202 to the central management device 210, and performs the internal processing 1202.

[0104] Next, the first application execution device 220, which is the operation device, transmits processing time information 1213A indicating the time to start the external processing 1203 to the central management device 210, and also performs the external processing 1203 and transmits an external message 1213B including the input data to the external device 240. In addition, the second application execution device 230, which is in the waiting position, transmits to the central management device 210 a message 1213C including processing time information indicating the time to start the external processing 1203 and an output data request requesting output data from the external device 240.

[0105] Next, the central management device 210 transmits a pause instruction 1213D to the first application execution device 220 and the second application execution device 230 to pause the execution of the application execution process 1200.

[0106] Next, after performing a predetermined operation based on the input data, the external device 240 transmits a message 1213E including the generated output data to the first application execution device 220 and the central management device 210, which are in charge of operation.

[0107] Next, central management device 210 transmits message 1213F including the output data acquired from external device 240 to second application execution device 230, which is on standby. After confirming that second application execution device 230 has received message 1213F, central management device 210 transmits resume instruction 1213G to first application execution device 220 and second application execution device 230 to resume the application execution process.

[0108] Next, the first application execution device 220 transmits processing time information 1214A indicating the time to start the internal processing 1204 to the central management device 210, and then performs the internal processing 1204. Similarly, the second application execution device 230 transmits processing time information 1214B indicating the time to start the internal processing 1204 to the central management device 210, and then performs the internal processing 1204.

[0109] According to the application execution process 1200 described above, an application including internal processing and external processing can be executed in an application execution device cluster made up of a plurality of application execution devices.

[0110] As described above, an abnormality may occur when an application execution device executes an application execution process. These abnormalities may be caused by, for example, memory failure, thermal runaway, or aging. When such an abnormality occurs, a countermeasure is required to smoothly continue the application execution process. The countermeasure varies depending on the timing of the abnormality occurrence. Therefore, one aspect of the information processing means according to an embodiment of the present disclosure relates to taking an appropriate countermeasure to smoothly continue the application execution process in accordance with the timing of the abnormality occurrence. Hereinafter, application execution processing when abnormalities occur at different times will be described with reference to FIGS.

[0111] 13 is a diagram showing an example of the flow of an abnormality handling process when an abnormality occurs during internal processing of an application execution process according to an embodiment of the present disclosure. More specifically, FIG. 13 shows the flow of an abnormality handling process when an abnormality occurs during internal processing of an application execution process in an application execution device information processing system made up of central management device 210, first application execution device 220, second application execution device 230, and external device 240. Here, the case where the first application execution device 220 is an operating device set in an operating mode, and the second application execution device 230 is a standby device set in a standby mode will be described as an example.

[0112] The same application execution process 1300 is executed in parallel in the first application execution device 220 and the second application execution device 230. As shown in Fig. 13, this application execution process 1300 is made up of internal process 1301, internal process 1302, external process 1303, and internal process 1304. Fig. 13 also shows a case where an abnormality occurs in internal process 1302 of this application execution process 1300.

[0113] First, the first application execution device 220 transmits processing time information 1311A indicating the time to start the internal processing 1301 to the central management device 210, and then performs the internal processing 1301. Similarly, the second application execution device 230 transmits processing time information 1311B indicating the time to start the internal processing 1301 to the central management device 210, and performs the internal processing 1301.

[0114] Next, the first application execution device 220 transmits processing time information 1312A indicating the time to start the internal processing 1302 to the central management device 210, but an error 1312X occurs and the internal processing 1302 is not executed. On the other hand, the second application execution device 230 transmits processing time information 1312B indicating the time to start the internal processing 1302 to the central management device 210, and then executes the internal processing 1302 normally.

[0115] Next, the second application execution device 230 on standby sends a message 1313A to the central management device 210, which includes processing time information indicating the time to start the external processing 1303 and a request for output data from the external device 240, and performs the external processing 1303. However, due to the abnormality 1312X that occurred during the internal process 1302, the first application execution device 220 on standby is unable to execute the external process 1303, and therefore does not transmit processing time information indicating the time to start the external process 1303 to the central management device 210, nor does it transmit input data to the external device 240.

[0116] Next, the central management device 210 receives from the second application execution device 230 on standby a message 1313A including processing time information indicating the time to start the external processing 1303 and a request for output data from the external device 240, and then transmits a pause instruction 1313B to the first application execution device 220 and the second application execution device 230 to pause the execution of the application execution process 1300.

[0117] Next, central management device 210 receives message 1313A from second application execution device 230, including processing time information indicating the time to start external processing 1303, but does not receive the processing time information indicating the time to start external processing 1303 from first application execution device 220, which is the operating device, within a predetermined time, and therefore determines that an abnormality has occurred in first application execution device 220, which is the operating device.

[0118] After detecting that an abnormality has occurred in the first application execution device 220 in the operating position, the central management device 210 changes the operation mode of the second application execution device 230 in the standby position to the operating mode. Thereafter, the second application execution device 230, now in the operating position, transmits an external message 1313C including input data to the external device 240.

[0119] Next, after performing a predetermined operation based on the input data, the external device 240 transmits a message 1313D including the generated output data to the second application execution device 230 and the central management device 210 that are now in charge of operation.

[0120] Next, the central management device 210 transmits a message including the output data acquired from the external device 240 to the other application execution devices on standby (not shown in FIG. 13). Thereafter, the central management device 210 transmits a resume instruction 1314 to the second application execution device 230 to resume the application execution process, and continues the internal process 1304 and subsequent processes.

[0121] 14 is a diagram showing an example of the flow of an abnormality handling process when an abnormality occurs during external processing of an application execution process according to an embodiment of the present disclosure. More specifically, FIG. 14 shows the flow of an abnormality handling process when an abnormality occurs during external processing of an application execution process in an application execution device information processing system made up of central management device 210, first application execution device 220, second application execution device 230, and external device 240. Here, the case where the first application execution device 220 is an operating device set in an operating mode, and the second application execution device 230 is a standby device set in a standby mode will be described as an example.

[0122] The same application execution process 1400 is executed in parallel in the first application execution device 220 and the second application execution device 230. As shown in Fig. 14, this application execution process 1400 is made up of internal process 1401, internal process 1402, external process 1403, and internal process 1404. Fig. 14 also shows a case where an abnormality occurs during external process 1403 of this application execution process 1400.

[0123] First, the first application execution device 220 transmits processing time information 1411A indicating the time to start the internal processing 1401 to the central management device 210, and then performs the internal processing 1401. Similarly, the second application execution device 230 transmits processing time information 1411B indicating the time to start the internal processing 1401 to the central management device 210, and performs the internal processing 1401.

[0124] Next, the first application execution device 220 transmits processing time information 1412A indicating the time to start the internal processing 1402 to the central management device 210, and performs the internal processing 1402. Similarly, the second application execution device 230 transmits processing time information 1412B indicating the time to start the internal processing 1402 to the central management device 210, and performs the internal processing 1402.

[0125] Next, the first application execution device 220, which is in charge of operation, sends processing time information 1413A indicating the time to start external processing 1403 to the central management device 210, but an abnormality 1413X occurs in external processing 1403, and the message including the input data is not sent to the external device 240. On the other hand, the second application execution device 230 transmits to the central management device 210 a message 1413B including processing time information indicating the time to start the external processing 1403 and a request for output data from the external device 240, and then performs the external processing 1403 normally.

[0126] Next, the central management device 210 receives processing time information 1413A, 1413B indicating the time to start the external processing 1403, and then transmits a pause instruction 1413C to the first application execution device 220 and the second application execution device 230 to pause the execution of the application execution process 1400.

[0127] Next, central management device 210 waits until it receives a message including output data from external device 240. However, because external device 240 has not received the message including input data from first application execution device 220 due to abnormality 1413X, it is unable to perform any operation and will not send the message including the output data to central management device 210 or first application execution device 220. Therefore, if the central management device 210 does not receive a message including output data from the external device 240 within a predetermined time, it determines that an abnormality has occurred in the first application execution device 220, which is in charge of operation.

[0128] After detecting that an abnormality has occurred in the first application execution device 220 in the operating position, the central management device 210 changes the operation mode of the second application execution device 230 in the standby position to the operating mode. Thereafter, the second application execution device 230, now in the operating position, transmits an external message 1413D including input data to the external device 240.

[0129] Next, after performing a predetermined operation based on the input data, the external device 240 transmits a message 1413E including the generated output data to the second application execution device 230 and the central management device 210 that are now in charge of operation.

[0130] Next, the central management device 210 transmits a message including the output data acquired from the external device 240 to the other application execution devices on standby (not shown in FIG. 14). Thereafter, the central management device 210 transmits a resume instruction 1414 to the second application execution device 230 to resume the application execution process, and continues the internal process 1404 and subsequent processes.

[0131] 15 is a diagram showing the flow of an abnormality handling process when an abnormality occurs after external processing of an application execution process according to an embodiment of the present disclosure. More specifically, FIG. 15 shows the flow of an abnormality handling process when an abnormality occurs after external processing of an application execution process in an application execution device information processing system including central management device 210, first application execution device 220, second application execution device 230, and external device 240. Here, the case where the first application execution device 220 is an operating device set in an operating mode, and the second application execution device 230 is a standby device set in a standby mode will be described as an example.

[0132] The same application execution process 1500 is executed in parallel in the first application execution device 220 and the second application execution device 230. As shown in Fig. 15, this application execution process 1500 is made up of internal process 1501, internal process 1502, external process 1503, and internal process 1504. Fig. 15 also shows a case where an abnormality occurs after external process 1503 of this application execution process 1500 has been executed.

[0133] First, the first application execution device 220 transmits processing time information 1511A indicating the time to start the internal processing 1501 to the central management device 210, and then performs the internal processing 1501. Similarly, the second application execution device 230 transmits processing time information 1511B indicating the time to start the internal processing 1501 to the central management device 210, and performs the internal processing 1501.

[0134] Next, the first application execution device 220 transmits processing time information 1512A indicating the time to start the internal processing 1502 to the central management device 210, and performs the internal processing 1502. Similarly, the second application execution device 230 transmits processing time information 1512B indicating the time to start the internal processing 1502 to the central management device 210, and performs the internal processing 1502.

[0135] Next, first application execution device 220, which is in charge of operation, transmits processing time information 1513A indicating the time to start external processing 1503 to central management device 210, and also transmits external message 1513B including input data to external device 240. However, after transmitting external message 1513B to external device 240, abnormality 1513X occurs in first application execution device 220. The second application execution device 230 transmits to the central management device 210 a message 1513C including processing time information indicating the time to start the external processing 1503 and a request for output data from the external device 240, and performs the external processing 1503.

[0136] Next, the central management device 210 receives processing time information 1513A, 1513C indicating the time to start the external processing 1503, and then transmits a pause instruction 1513D to the first application execution device 220 and the second application execution device 230 to pause the execution of the application execution process 1500.

[0137] Next, after performing a predetermined operation based on the input data, external device 240 transmits message 1513E including the generated output data to first application execution device 220 and central management device 210. However, due to the occurrence of abnormality 1513X, first application execution device 220 is unable to receive message 1513E.

[0138] Next, the central management device 210 transmits a message 1513F including the output data acquired from the external device 240 to the second application execution device 230, which is on standby. Thereafter, the central management device 210 transmits a resume instruction 1513G to the second application execution device 230 to resume the application execution process.

[0139] Next, the second application execution device 230 transmits processing time information 1514 indicating the time to start the internal processing 1504 to the central management device 210, and performs the internal processing 1504. On the other hand, due to the abnormality 1513X that occurred after the execution of the external process 1503, the first application execution device 220 is unable to execute the internal process 1504, and therefore does not transmit processing time information indicating the time to start the internal process 1504 to the central management device 210.

[0140] Next, the central management device 210 receives processing time information 1514 indicating the time to start internal processing 1504 from the second application execution device 230, but does not receive processing time information indicating the time to start internal processing 1504 from the first application execution device 220, which is the operating device, within the specified time period, and therefore determines that an abnormality has occurred in the first application execution device 220, which is the operating device. After detecting that an abnormality has occurred in the first application execution device 220 in the operating position, the central management device 210 changes the operating mode of the second application execution device 230 in the standby position to the operating mode. Thereafter, the second application execution device 230, now in the operating position, continues the subsequent processing.

[0141] 13 to 15, when an abnormality occurs in the application execution process of the operating application execution device, the standby application execution device can become the new operating device. The new operating application execution device then performs external communication with the external device that was not performed normally due to the abnormality, allowing the application execution process to continue smoothly even for an application that includes external processing. Furthermore, in the abnormality response processing described above, the occurrence of an abnormality is determined not only at the time when the data flow ends but also at the time when each processing block starts, based on the processing time information received from each application execution device and the output data from an external device, so that abnormalities can be detected early in the application execution processing.

[0142] Next, application execution processing in the application execution device according to an embodiment of the present disclosure will be described with reference to FIG.

[0143] 16 is a diagram showing an example of the flow of application execution processing 1600 in an application execution device of an operation section according to an embodiment of the present disclosure. The application execution processing 1600 is processing for executing an application based on a data flow edited by a flow editor in the application execution device of an operation section, and is executed by an application execution device according to an embodiment of the present disclosure (for example, the first application execution device 220, the second application execution device 230, etc. shown in FIG. 2).

[0144] First, in step S1601, the application execution device acquires input data. This input data is data to be processed, and may be, for example, output data from a processing block that has already been processed immediately before. This input data may be subjected to, for example, the preprocessing described above and converted into a predetermined format.

[0145] Next, in step S1602, the application execution device determines whether the input data acquired in step S1601 requires external processing (i.e., processing requiring communication with an external device). If it is determined that external processing is required, the process proceeds to step S1603. On the other hand, if it is determined that external processing is not required, the process proceeds to step S1605.

[0146] Next, in step S1603, if it is determined that external processing is required, the operating application execution device transmits processing time information indicating the time for executing the external processing to the central management device, and after executing the external processing, receives a pause instruction from the central management device to pause the application execution processing. This pause instruction causes the application execution device to wait until output data is transmitted from the external device.

[0147] Next, in step S1604, the application execution device receives the output data from the external device. As described above, the operating application execution device receives the output data directly from the external device via the communication network.

[0148] Next, in step S1605, if it is determined that external processing is not required, the application execution device executes processing (that is, internal processing).

[0149] Next, in step S1606, the application execution device determines whether or not there is any unexecuted processing. If there is unexecuted processing, the process returns to step S1602 and continues the application execution processing. On the other hand, if there is no unexecuted processing, the process proceeds to step S1607.

[0150] In step S1607, the application execution device generates an output result indicating the history of processes that have been executed so far and the status of each device, and transmits the output result to a predetermined notification destination such as a central management device or a client terminal.

[0151] According to the application execution process 1600 described above, the application execution process can be smoothly executed even for an application that includes an external process that requires communication with an external device in addition to an internal process.

[0152] Next, with reference to FIG. 17, a management process in the central management device according to an embodiment of the present disclosure will be described.

[0153] 17 is a diagram showing an example of the flow of management processing 1700 in a central management device according to an embodiment of the present disclosure. The management processing 1700 is processing for managing application execution processing by application execution devices, and is executed by the central management device 210 as described above.

[0154] First, in step S1701, the central management device acquires processing time information indicating the time required to execute the target process from each application execution device, and stores the information in a memory unit of the cluster management unit described above (for example, the memory unit 605 of the cluster management unit 211 shown in FIG. 6).

[0155] Next, in step S1702, the central management unit determines whether external processing (i.e., processing requiring communication with an external device) is required. If it is determined that external processing is required, the process proceeds to step S1703. On the other hand, if it is determined that external processing is not required, the process proceeds to step S1705.

[0156] Next, in step S1703, if it is determined that external processing is required, the application execution synchronization management unit of the central management device (for example, the pause / resume unit 712 of the application execution synchronization management unit 212 shown in FIG. 7) transmits a pause instruction to each application execution device to pause the application execution processing in each application execution device.

[0157] Next, in step S1704, an anomaly detection unit of the cluster management unit of the central management device (e.g., anomaly detection unit 614 of the cluster management unit 211 shown in FIG. 6) determines whether an anomaly has occurred in an operating application execution device (e.g., the first application execution device 220 shown in FIG. 2). Here, the anomaly detection unit may determine whether an anomaly has occurred in an operating application execution device based on the processing time information acquired from each application execution device in step S1701. In one embodiment, the anomaly detection unit may determine that an anomaly has occurred in an operating application execution device if it has not received processing time information from the operating application execution device within a predetermined time after receiving processing time information from a standby application execution device. In another embodiment, the anomaly detection unit may determine that an anomaly has occurred in an operating application execution device if it has not received processing time information from the operating application execution device within a predetermined time. If it is determined that an abnormality has occurred in the operation unit's application execution device, the process proceeds to step S1705. On the other hand, if it is determined that an abnormality has not occurred in the operation unit's application execution device, the process proceeds to step S1706.

[0158] Next, in step S1705, if it is determined that an abnormality has occurred in the operating application execution device, the operation mode management unit of the central management device (for example, the operation mode management unit 616 of the cluster management unit 211 shown in FIG. 6) changes the operation mode of the standby application execution device (for example, the second application execution device 230 shown in FIG. 2) from standby mode to operating mode. The application execution device thus changed from standby to operating performs external communication for the external process in which the abnormality occurred.

[0159] Next, in step S1706, the central management unit receives the output data from the external device via the communication network.

[0160] Next, in step S1707, the central management device transfers the output data received from the external device in step S1706 to the application execution device on standby.

[0161] In step S1708, if it is determined that external processing is not required, the abnormality detection unit of the cluster management unit of the central management device (for example, the abnormality detection unit 614 of the cluster management unit 211 shown in FIG. 6) determines whether an abnormality has occurred in an application execution device in charge of operation (for example, the first application execution device 220 shown in FIG. 2). If it is determined that an abnormality has occurred in the operation unit's application execution device, the process proceeds to step S1709. On the other hand, if it is determined that an abnormality has not occurred in the operation unit's application execution device, the process proceeds to step S1710.

[0162] In step S1709, if it is determined that an abnormality has occurred in the application execution device in the operating section, the operation mode management unit of the central management device (e.g., the operation mode management unit 616 of the cluster management unit 211 shown in FIG. 6) changes the operation mode of the application execution device in the standby section (e.g., the second application execution device 230 shown in FIG. 2) from the standby mode to the operating mode.

[0163] In step S1710, the central management unit continues the application execution process.

[0164] According to the management process 1700 described above, it is possible to detect abnormalities early even in applications that include external processes that require communication with external devices in addition to internal processes, and improve the reliability of application execution processes.

[0165] Next, external device processing according to an embodiment of the present disclosure will be described with reference to FIG.

[0166] 18 is a diagram showing an example of the flow of external device processing 1800 according to an embodiment of the present disclosure. The external device processing 1800 shown in Fig. 18 is processing performed based on input data received through external communication with an application execution device, and is executed by an external device according to an embodiment of the present disclosure (for example, external device 240 shown in Fig. 2).

[0167] First, in step S1801, the external device receives input data from the application execution device in charge of operation via a communications network. As described above, this input data may include an instruction requesting the execution of a predetermined process or operation.

[0168] Next, in step S1802, the external device executes the processing or operation instructed by the input data based on the input data received in step S1801. For example, if the external device is a machine for performing a production process in a factory, the external device may assemble parts, pack products, etc. based on the received input data.

[0169] Next, in step S1803, the external device transmits output data to the application execution device in charge of operation and the central management device. The output data here may include, for example, information regarding the progress of the process or operation executed by the external device in step S1802.

[0170] According to the external device processing 1800 described above, the external device can perform operations related to external processing in the application execution processing being executed within the application execution device.

[0171] Next, with reference to FIG. 19, a data transfer flow in the case of normal external processing in the information processing system according to the embodiment of the present disclosure will be described.

[0172] 19 is a diagram showing the flow of data transfer in the case of normal external processing in an application execution device information processing system according to an embodiment of the present disclosure. More specifically, FIG. 19 shows the flow of data transfer in the case of normal external processing in an application execution device information processing system made up of central management device 210, first application execution device 220, second application execution device 230, third application execution device 235, and external device 240. Here, an example will be described in which the first application execution device 220 is an operating device set in an operating mode, and the second application execution device 230 and the third application execution device 235 are standby devices set in a standby mode.

[0173] First, when an external process occurs during application execution processing, the first application execution device 220, the second application execution device 230, and the third application execution device 235 transmit processing time information (not shown in FIG. 19 ) indicating the time when the external process will start to the central management device 210. In addition, the first application execution device 220, which is the operation application execution device, transfers a message IN1 including input data to the external device 240.

[0174] Next, the application execution synchronization management unit 212 of the central management device 210 transmits a pause instruction (not illustrated in FIG. 19 ) to the first application execution device 220, the second application execution device 230, and the third application execution device 235 to pause the application execution process until a message OUT1 including output data from the external device 240 is received.

[0175] Next, the external device 240 receives the message IN1, performs a predetermined operation or process based on the acquired input data, and then transmits a message OUT1 including output data to the first application execution device 220, which is an application execution device in the operation department, and to the central management device 210.

[0176] Next, central management device 210 receives message OUT1 from external device 240 and transfers the acquired output data to waiting second application execution device 230 and third application execution device 235. Thereafter, after central management device 210 confirms that second application execution device 230 and third application execution device 235 have received message OUT1, central management device 210 transmits a resume instruction (not shown in FIG. 19 ) to resume application execution processing in first application execution device 220, second application execution device 230, and third application execution device 235.

[0177] In this way, when no abnormality occurs, the application execution processes in the first application execution device 220, the second application execution device 230, and the third application execution device 235 can be executed synchronously while external processing is being performed.

[0178] Next, with reference to FIG. 20, a flow of data transfer in the information processing system when an abnormality occurs during external processing in the application execution processing according to an embodiment of the present disclosure will be described.

[0179] 20 is a diagram showing the flow of data transfer in an information processing system when an abnormality occurs during external processing in application execution processing according to an embodiment of the present disclosure. More specifically, FIG. 20 shows the flow of data transfer in an application execution device information processing system including central management device 210, first application execution device 220, second application execution device 230, third application execution device 235, and external device 240 when an abnormality occurs during external processing. Here, an example will be described in which the first application execution device 220 is an operating device set in an operating mode, and the second application execution device 230 and the third application execution device 235 are standby devices set in a standby mode.

[0180] First, when external processing occurs during application execution processing, the first application execution device 220, the second application execution device 230, and the third application execution device 235 transmit processing time information (not illustrated in FIG. 20) indicating the time to start the external processing to the central management device 210, and receive a pause instruction (not illustrated in FIG. 20) from the central management device 210 to pause the application execution processing until a message OUT1 including output data from the external device 240 is received. Note that first application execution device 220, which is the operation unit, is supposed to transmit message IN1 including input data to external device 240. However, in the example shown in Fig. 20, a case is considered in which an abnormality occurs in first application execution device 220, which is the operation unit, and message IN1 is not transmitted to external device 240.

[0181] Next, cluster management unit 211 of central management device 210 detects that an abnormality has occurred in first application execution device 220, which is in charge of operation. Here, cluster management unit 211 may determine that an abnormality has occurred in first application execution device 220 if message OUT1 is not received from external device 240 within a predetermined time after receiving processing time information indicating the time to start external processing from first application execution device 220.

[0182] In this case, the cluster management unit 211 of the central management device 210 changes the operation mode of a standby application execution device such as the second application execution device 230 from standby mode to active mode.

[0183] Next, the second application execution device 230, which has been changed to the operating device, transmits to the external device 240 a message IN1 including the input data (that is, the message that the first application execution device 220 was unable to transmit due to the occurrence of the abnormality).

[0184] Next, after performing a predetermined operation based on the input data, the external device 240 transmits a message OUT1 including the generated output data to the second application execution device 230 and the central management device 210 that are now in charge of operation.

[0185] Next, the central management device 210 transmits the message OUT1 acquired from the external device 240 to other application execution devices on standby, such as the third application execution device 235. After confirming that all application execution devices have received the message OUT1, the central management device 210 transmits a resume instruction to the second application execution device 230 and the third application execution device 235 to resume the application execution process, causing them to execute the next process.

[0186] In this way, if a message containing output data is not received from the external device within a specified time after receiving processing time information indicating the time to start external processing from the application execution device, it is possible to quickly determine that an abnormality has occurred in the operating unit.

[0187] Next, with reference to FIG. 21, a flow of data transfer in the information processing system when an abnormality occurs after external processing in the application execution processing according to an embodiment of the present disclosure will be described.

[0188] 21 is a diagram showing the flow of data transfer in an information processing system when an abnormality occurs after external processing in an application execution process according to an embodiment of the present disclosure. More specifically, FIG. 21 shows the flow of data transfer in an information processing system when an abnormality occurs after external processing in an application execution device information processing system including central management device 210, first application execution device 220, second application execution device 230, third application execution device 235, and external device 240. Here, an example will be described in which the first application execution device 220 is an operating device set in an operating mode, and the second application execution device 230 and the third application execution device 235 are standby devices set in a standby mode.

[0189] First, when external processing occurs during application execution processing, the first application execution device 220, the second application execution device 230, and the third application execution device 235 transmit processing time information (not illustrated in FIG. 21) indicating the time to start the external processing to the central management device 210, and receive a pause instruction (not illustrated in FIG. 21) from the central management device 210 to pause the application execution processing until a message OUT1 including output data from the external device 240 is received.

[0190] Here, first application execution device 220, which is the operation unit, transmits processing time information (not shown in FIG. 20) indicating the time to start external processing to central management device 210, and at the same time transmits message IN1 including input data to external device 240. However, in the example shown in FIG. 21, a case will be considered in which, after first application execution device 220, which is the operation unit, transmits message IN1 to external device 240, an abnormality occurs, making it unable to perform any further processing.

[0191] Next, after performing a predetermined operation based on message IN1, external device 240 transmits message OUT1 including the generated output data to first application execution device 220 and central management device 210. However, due to the occurrence of an abnormality, first application execution device 220 is unable to receive message OUT1.

[0192] Next, central management device 210 transmits message OUT1 including the output data acquired from external device 240 to second application execution device 230 and third application execution device 235, which are on standby. Thereafter, central management device 210 transmits a resume instruction (not shown in FIG. 21 ) to second application execution device 230 and third application execution device 235 to resume the application execution process.

[0193] Next, the second application execution device 230 and the third application execution device 235 transmit processing time information indicating the time to start the next process in the application execution process to the central management device 210, and perform the process. However, due to an abnormality that occurred after the execution of the external process, the first application execution device 220 of the operation section is unable to execute the next process, and therefore does not transmit processing time information indicating the time to start the process to the central management device 210.

[0194] Next, central management device 210 receives processing time information indicating the time to start processing from second application execution device 230 and third application execution device 235, but does not receive processing time information indicating the time to start the processing from first application execution device 220, which is the operating device, within a predetermined time, and therefore determines that an abnormality has occurred in first application execution device 220, which is the operating device. When an abnormality is detected in the first application execution device 220 in the operating position, the central management device 210 changes the operating mode of a standby application execution device, such as the second application execution device 230, to the operating mode. Thereafter, the second application execution device 230, now in the operating position, continues the subsequent processing.

[0195] In this way, processing time information indicating the time to start processing is received from the application execution device of the waiting clerk, and if the processing time information indicating the time to start the processing is not received from the application execution device of the operating clerk within a specified time, it is possible to quickly determine that an abnormality has occurred in the operating clerk.

[0196] Next, a processing time information management table according to an embodiment of the present disclosure will be described with reference to FIG.

[0197] 22 is a diagram illustrating processing time information management tables T221, T222, T223, and T224 according to an embodiment of the present disclosure. As described above, the cluster management unit 211 of the central management device according to an embodiment of the present disclosure can store processing time information acquired from each application execution device in table format. Below, with reference to the processing time information management tables T221, T222, T223, and T224, a description will be given of the case where an application execution process is normal and the case where an abnormality occurs in the application execution process.

[0198] Table T221 shows an example of processing time information stored when an application execution process is executed normally. As shown in table T221, processing time information for each of internal process 1-IMP, internal process 2-IMP, external process 3-IMP, and internal process 4-IMP is received from application execution device PU1 in the operating role and application execution devices PU2 and PU3 in the standby role, and is stored.

[0199] Table T222 shows an example of processing time information stored when an abnormality occurs during internal processing of an application execution process. As shown in table T222, processing time information for the processing of internal process 1-IMP is received from application execution device PU1 in the operating role and application execution devices PU2 and PU3 in the standby role, and is stored. However, for internal process 2-IMP, although processing time information has been received from the application execution units PU2 and PU3 in the standby state, processing time information has not been received from the application execution unit PU1 in the operating state. Therefore, if the processing time information corresponding to internal process 2-IMP is not received from the operating application execution unit PU1 within a predetermined time, the central management unit determines that an abnormality has occurred in the operating application execution unit PU1. The central management unit then changes the operating mode of the standby application execution unit, such as application execution unit PU2, from standby mode to active mode, and continues the subsequent processing.

[0200] Table T223 shows an example of processing time information stored when an abnormality occurs during external processing of an application execution process. As shown in table T223, processing time information for each of internal processing 1-IMP and internal processing 2-IMP is received from application execution device PU1 in operation and application execution devices PU2 and PU3 in standby, and is stored. However, it is assumed that the central management device has not received a message (not shown in table T223) containing output data corresponding to external process 3-EMP from the external device.

[0201] Therefore, if a message including output data corresponding to external process 3-EMP is not received from the external device within a predetermined time, the central management device determines that an abnormality has occurred in the operating application execution unit PU1. The central management device then changes the operating mode of the standby application execution unit, such as application execution unit PU2, from standby mode to operating mode. Then, application execution unit PU2, which has been changed from standby mode to operating mode, transmits input data for external process 3-EMP to the external device and continues subsequent processing. Note that, here, an example has been described in which it is determined that an abnormality has occurred in the operating app execution device when a message including output data is not received from an external device within a predetermined time, but the present disclosure is not limited to this, and for example, as described above, it is also possible to determine that an abnormality has occurred in the operating app execution device when processing time information indicating the start time of the next processing is not received.

[0202] Table T224 shows an example of processing time information stored when an abnormality occurs after external processing of an application execution process. As shown in table T224, processing time information for each of internal processing 1-IMP and internal processing 2-IMP is received from application execution device PU1 in the operating role and application execution devices PU2 and PU3 in the standby role, and stored. Also, although not shown in table T224, it is assumed that the central management device receives a message including output data from an external device.

[0203] However, for internal process 4-EMP, although processing time information has been received from the application execution units PU2 and PU3 in the standby state, processing time information has not been received from the application execution unit PU1 in the operating state. Therefore, if processing time information corresponding to internal process 4-EMP is not received from application execution unit PU1 within a predetermined time, the central management unit determines that an abnormality has occurred in application execution unit PU1 in the operating position.The central management unit then changes the operating mode of a standby application execution unit, such as application execution unit PU2, from standby mode to operating mode, and continues subsequent processing.

[0204] The information processing means according to the embodiment of the present disclosure has been described above. As described above, one aspect of the information processing means according to the embodiment of the present disclosure relates to determining whether an abnormality has occurred in an operating application execution device based on processing time information acquired from the application execution device at the start of each processing block included in the application execution process that executes an application based on a data flow created by a flow editor. This allows for early detection of whether an abnormality has occurred not only when the data flow ends but also during the application execution process.

[0205] Another aspect of the information processing means according to an embodiment of the present disclosure relates to, when an abnormality occurs in the application execution process of an operating application execution device, designating a standby application execution device as the new operating device. The new operating application execution device then performs processing, such as external communication with an external device, that was not performed properly due to the abnormality. This allows smooth continuation of the application execution process, even when an abnormality occurs in an application including external processing, by executing processing from the point where the abnormality occurred, rather than restarting the data flow from the beginning.

[0206] In this way, according to the information processing of the embodiment of the present disclosure, it is possible to provide an information processing means that can detect abnormalities early and improve the reliability of the application execution processing, even in the case of an application that includes external processing.

[0207] As described above, the abnormality determination means according to the embodiment of the present disclosure includes the following aspects.

[0208] (Aspect 1) a plurality of application execution devices that execute applications based on data flow in parallel; a central management device that manages the plurality of application execution devices; An information processing system connected to an external device via a communication network, the external device performing a predetermined operation based on a command from the application execution device, The application an internal process executed within the application execution device; an external process that requires communication with the external device; The application execution device an operating mode in which, when executing an external process in the application, command information instructing execution of the predetermined operation is transmitted to the external device and output information is received from the external device; When executing an external process in the application, the device is configured to operate in one of two operation modes: a standby mode in which command information instructing execution of the predetermined operation is not transmitted to the external device, and the device waits until the output information transmitted via the central management device is received; The central management device receiving, from a first application execution device operating in the standby mode, first processing time information indicating a time for which a first process is to be executed in the first application execution device; determining that an abnormality has occurred in the second application execution device when second processing time information, which indicates a time for the second application execution device to execute the first process, is not received from the second application execution device operating in the active mode within a predetermined time after receiving the first processing time information; when it is determined that an abnormality has occurred in the second application execution device, changing the mode of the first application execution device from the standby mode to the operating mode and allowing the first application execution device to continue executing the application; An information processing system comprising:

[0209] (Aspect 2) The central management device when first external processing time information indicating a time for which a first external processing is to be executed in the first application execution device is received from the first application execution device operating in the standby mode, transmitting a pause instruction to pause execution of the application to the first application execution device and the second application execution device; determining that an abnormality has occurred in the second application execution device when the output information from the external device is not received within a predetermined time after receiving the first external processing time information; if it is determined that an abnormality has occurred in the second application execution device, changing the mode of the first application execution device from the standby mode to the operating mode; controlling the second application execution device to transmit the command information to the external device; transmitting a resume instruction to the second application execution device to resume execution of the application when the output information is received from the external device; 2. The information processing system according to aspect 1.

[0210] (Aspect 3) The central management device when first external processing time information indicating a time for which a first external processing is to be executed in the first application execution device is received from the first application execution device operating in the standby mode, transmitting a pause instruction to pause execution of the application to the first application execution device and the second application execution device; transmitting a resume instruction to resume execution of the application to the first application execution device and the second application execution device when the output information from the external device is received within a predetermined time after receiving the first external processing time information; receiving, from the first application execution device operating in the standby mode, third processing time information indicating a time for the first application execution device to execute a second process subsequent to the first external process; determining that an abnormality has occurred in the second application execution device when fourth processing time information, which indicates a time for the second process to be executed in the second application execution device, is not received from the second application execution device operating in the active mode within a predetermined time after receiving the third processing time information; when it is determined that an abnormality has occurred in the second application execution device, changing the mode of the first application execution device from the standby mode to the operating mode and allowing the first application execution device to continue executing the application; 3. The information processing system according to aspect 1 or 2.

[0211] Although the embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the gist of the present invention. [Explanation of symbols]

[0212] 200 Information Processing Systems 210 Central management unit 211 Cluster Management Department 212 Application execution synchronization management unit 215 Application Execution Device Cluster 220 First application execution device 221 Flow Editorial Management Department 222 Application execution unit 230 Second application execution device 231 Flow Editorial Management Department 232 Application execution unit 240 External device

Claims

1. a plurality of application execution devices that execute applications based on data flow in parallel; a central management device that manages the plurality of application execution devices; An information processing system connected to an external device via a communication network, the external device performing a predetermined operation based on a command from the application execution device, The application an internal process executed within the application execution device; an external process that requires communication with the external device; The application execution device an operating mode in which, when executing an external process in the application, command information instructing execution of the predetermined operation is transmitted to the external device and output information is received from the external device; When executing an external process in the application, the device is configured to operate in one of two operation modes: a standby mode in which command information instructing execution of the predetermined operation is not transmitted to the external device, and the device waits until the output information transmitted via the central management device is received; The central management device receiving, from a first application execution device operating in the standby mode, first processing time information indicating a time for which a first process is to be executed in the first application execution device; determining that an abnormality has occurred in the second application execution device when second processing time information, which indicates a time for the second application execution device to execute the first process, is not received from the second application execution device operating in the active mode within a predetermined time after receiving the first processing time information; when it is determined that an abnormality has occurred in the second application execution device, changing the mode of the first application execution device from the standby mode to the operating mode and allowing the first application execution device to continue executing the application; An information processing system comprising:

2. The central management device transmitting a pause instruction to pause execution of the application to the first application execution device and the second application execution device when first external processing time information indicating a time for which the first external processing is to be executed in the first application execution device is received from the first application execution device operating in the standby mode; determining that an abnormality has occurred in the second application execution device when the output information from the external device is not received within a predetermined time after receiving the first external processing time information; if it is determined that an abnormality has occurred in the second application execution device, changing the first application execution device from the standby mode to the operating mode; controlling the second application execution device to transmit the command information to the external device; transmitting a resume instruction to the second application execution device to resume execution of the application when the output information is received from the external device; 2. The information processing system according to claim 1, wherein:

3. The central management device transmitting a pause instruction to pause execution of the application to the first application execution device and the second application execution device when first external processing time information indicating a time for which the first external processing is to be executed in the first application execution device is received from the first application execution device operating in the standby mode; transmitting a resume instruction to resume execution of the application to the first application execution device and the second application execution device when the output information from the external device is received within a predetermined time after receiving the first external processing time information; receiving, from the first application execution device operating in the standby mode, third processing time information indicating a time for the first application execution device to execute a second process subsequent to the first external process; determining that an abnormality has occurred in a second application execution device when fourth processing time information, which indicates a time for the second process to be executed in the second application execution device, is not received from the second application execution device operating in the active mode within a predetermined time after receiving the third processing time information; when it is determined that an abnormality has occurred in the second application execution device, changing the mode of the first application execution device from the standby mode to the operating mode and allowing the first application execution device to continue executing the application; 2. The information processing system according to claim 1, wherein:

4. a plurality of application execution devices that execute applications based on data flow in parallel; a central management device that manages the plurality of application execution devices; 1. An information processing method executed in an information processing system connected via a communication network to an external device that performs a predetermined operation based on a command from the application execution device, The application an internal process executed within the application execution device; an external process that requires communication with the external device; The application execution device an operating mode in which, when executing an external process in the application, command information instructing execution of the predetermined operation is transmitted to the external device and output information is received from the external device; When executing an external process in the application, the device is configured to operate in one of two operation modes: a standby mode in which command information instructing execution of the predetermined operation is not transmitted to the external device, and the device waits until the output information transmitted via the central management device is received; The information processing method includes: receiving, from a first application execution device operating in the standby mode, first processing time information indicating a time for which a first process is to be executed in the first application execution device; determining that an abnormality has occurred in a second application execution device when second processing time information indicating a time for executing the first process in the second application execution device is not received from the second application execution device operating in the active mode within a predetermined time after receiving the first processing time information; when it is determined that an abnormality has occurred in the second application execution device, changing the mode of the first application execution device from the standby mode to the operating mode and continuing execution of the application; The information processing method is characterized in that the above is executed by the central management device.

5. The information processing method includes: transmitting, when first external processing time information indicating a time for which a first external processing is to be executed in the first application execution device from the first application execution device operating in the standby mode, a pause instruction to pause execution of the application to the first application execution device and the second application execution device; determining that an abnormality has occurred in the second application execution device when the output information from the external device is not received within a predetermined time after receiving the first external processing time information; changing the mode of the first application execution device from the standby mode to the operating mode when it is determined that an abnormality has occurred in the second application execution device; controlling the second application execution device to transmit the command information to the external device; transmitting, when the output information is received from the external device, a resume instruction to resume execution of the application to the second application execution device; 5. The information processing method according to claim 4, wherein the above is executed by the central management device.

6. The information processing method includes: transmitting, when first external processing time information indicating a time for which a first external processing is to be executed in the first application execution device from the first application execution device operating in the standby mode, a pause instruction to pause execution of the application to the first application execution device and the second application execution device; transmitting a resume instruction to resume execution of the application to the first application execution device and the second application execution device when the output information from the external device is received within a predetermined time after receiving the first external processing time information; receiving, from the first application execution device operating in the standby mode, third processing time information indicating a time for the first application execution device to execute a second processing subsequent to the first external processing; determining that an abnormality has occurred in a second application execution device when fourth processing time information indicating a time for the second process to be executed in the second application execution device is not received from the second application execution device operating in the active mode within a predetermined time after receiving the third processing time information; when it is determined that an abnormality has occurred in the second application execution device, changing the mode of the first application execution device from the standby mode to the operating mode and continuing execution of the application; 5. The information processing method according to claim 4, wherein the above is executed by the central management device.

Images