A configuration environment system operation method and system based on microservice architecture

Abstract

The present invention discloses a configuration environment system operation system based on a microservice architecture, comprising a microservice function module set for providing configuration development tool software with the microservice function blocks required for writing configuration programs; the configuration development tool software for writing configuration program tasks and generating corresponding XML task information files and CPP program code files; the configuration environment system operation software for decomposing the configuration program tasks into multiple subtask microservices based on the configuration program task information and program code, and orchestrating and deploying the multiple subtask microservices to the system's task execution device set; and the task execution device set for receiving the subtask microservices deployed by the configuration environment system operation software and, after compiling, placing the subtasks in a lightweight virtualized runtime for execution. The system implements an integrated solution for configuration program task development, execution, and monitoring, and has excellent scalability.

Description

Technical Field

[0001] The present invention relates to the field of industrial control technology, and in particular to a configuration environment system operation method and system based on a microservice architecture. Background Art

[0002] Data acquisition and monitoring systems are widely used in discrete and process industries such as high-end equipment, electric power, and petrochemicals. The configuration environment system operating software is responsible for monitoring and processing real-time data, and performing specific control operations and data acquisition tasks within the data acquisition and monitoring system. While traditional data acquisition and monitoring systems can achieve centralized management of data acquisition equipment, they still rely heavily on on-site maintenance personnel for program debugging. Furthermore, advanced technologies such as complex system modeling and simulation, and intelligent operation monitoring are difficult to embed into existing systems and require access to third-party tool software. Furthermore, it is difficult to directly transfer data from the system for use. When faced with major projects, existing data acquisition and monitoring systems are unable to achieve safe, high-quality, and large-scale development, and there is an urgent need to transform the software system architecture and development tools.

[0003] The microservices architecture adopts a component-based design philosophy, breaking applications into a series of small, segmented, independently deployable, and autonomous services. Each service performs a specific function and can be deployed in batches using templates, making it suitable for large-scale business configuration and configuration sharing. However, since general-purpose microservices architectures struggle to meet the real-time, security, and reliability requirements of the industrial sector, direct migration is not feasible. Therefore, general-purpose microservices architectures are currently primarily used in the development of commercial internet systems, and there is a lack of industry-specific microservices architecture systems in real-world scenarios.

[0004] To solve the above technical problems, a Chinese patent discloses an end-edge cloud industrial microservice system, data interaction method and medium, with publication number CN 113111374 B. It uses a microservice architecture to implement equipment data collection and production data query, but cannot achieve access to functional demand services such as complex system modeling and simulation, intelligent operation monitoring, etc. It performs automated further processing based on the collected data to predict and lock faults and adjust and control equipment.

[0005] A Chinese patent also discloses an end-edge cloud industrial microservice system and method, with publication number CN115022306A. It adds a codec to ensure data security based on patent CN 113111374 B, but does not solve the above-mentioned problems.

[0006] To this end, a method and system for operating a configuration environment system based on a microservices architecture is urgently needed. This method transforms the traditional microservices architecture to meet industrial needs, leveraging the concept of microservices to build a system architecture that adapts to industrial scenarios. This innovative approach proposes the integrated development of three types of microservice functional modules: hybrid stream data access, complex system modeling and simulation, and data intelligent operation monitoring. This approach integrates the entire process of configuration program writing, orchestration, deployment, and execution. This approach can effectively address the development and expansion challenges inherent in high-end engineering data acquisition and monitoring systems, which are often complex, highly coupled, and face difficulties interoperating with third-party tools. Furthermore, program deployment can be performed through the cloud, reducing the need for on-site debugging. Summary of the Invention

[0007] In order to overcome the defects of the prior art, the present invention provides a configuration environment system operation method and system based on a microservice architecture to solve the above technical problems.

[0008] In order to solve the above technical problems, the technical solution of the present invention is:

[0009] A configuration environment system operation system based on a microservice architecture includes five parts: a microservice function module set, a configuration development tool software, a configuration environment system operation software, a task execution device set, and a communication information model.

[0010] The microservice function module set is used to provide the configuration development tool software with the microservice function blocks required for writing the configuration program;

[0011] The configuration development tool software is used to write configuration program tasks and generate corresponding XML task information files and CPP program code files;

[0012] The configuration environment system runs software for decomposing the configuration program task into a plurality of subtask microservices according to the information and program code of the configuration program task, and orchestrating and deploying the plurality of subtask microservices to a set of task execution devices of the system;

[0013] The task execution device set is used to receive the subtask microservices deployed by the configuration environment system running software, and place the subtasks in the runtime for execution after compilation;

[0014] The communication information model is used for data transmission between microservices in several task execution devices in a task execution device set, and for data calls between microservices in a task execution device and an industrial cloud server.

[0015] Preferably, the microservice functional blocks include hybrid stream data access microservices, modeling and simulation microservices, and data intelligent monitoring microservices.

[0016] Among them, the hybrid stream data access is connected to the data acquisition equipment through components of commonly used industrial field communication protocols such as RS232, RS485, Modbus, CAN (Controller Area Network), EtherCAT (Ethernet Control Automation Technology) and obtains real-time data; wherein, the data acquisition equipment includes a field controller, sensor or camera.

[0017] Among them, intelligent operation monitoring uses a multi-source domain generalization method to realize fault diagnosis of key components in multi-source domain scenarios, which can be injected into each data acquisition functional block.

[0018] Among them, complex system modeling and simulation in the process industry simulates flow data through digital modeling of production lines, and compares it with the flow data actually collected at the industrial site to achieve functional analysis, performance analysis, and reliability analysis of the complex model; in the discrete industry, the collected sensor data is compared with the virtual simulation data, and floating threshold denoising is performed to obtain virtual and real residuals and realize abnormal perception.

[0019] Preferably, the configuration development tool software uses the language specified in IEC 61131-3 to write configuration program tasks and calls the microservice function blocks provided by the microservice function module set.

[0020] Specifically, it includes three types of microservice functional modules, including hybrid stream data access, complex system modeling and simulation, and intelligent operation monitoring, and they are developed in an integrated manner.

[0021] Preferably, the configuration environment system operating software includes a device management module, a task scheduling module, a task deployment module and a communication module.

[0022] The device management module is used to access the task execution device and record its information for the task scheduling module to make task scheduling decisions;

[0023] The task scheduling module is used to perform scheduling according to the task scheduling decision and obtain the task deployment strategy;

[0024] The task deployment module is used to deploy tasks according to the task deployment strategy;

[0025] The communication module is used to provide a protocol communication interface to store the protocol communication interface exposed by the microservice in the task execution device in the database.

[0026] Preferably, the protocol communication interface is any one of a RESTful API communication interface, an OPC UA protocol communication interface, and a Modbus protocol communication interface.

[0027] The present invention also provides a method for operating a configuration environment system based on a microservice architecture, comprising the following steps:

[0028] Step 1: The application configuration environment system running software decomposes the configuration program task into multiple subtask microservices according to the configuration program task information and program code. The basis for the configuration program task decomposition includes the number of task POUs, the execution order of function block instances in each POU, the input and output pin binding variable information of the function block instance, and the execution environment required by the function block;

[0029] Step 2: Perform task orchestration on the multiple subtask microservices obtained by decomposition;

[0030] Step 3: Deploy the subtask microservice to the system's task execution device set according to the task deployment strategy;

[0031] Step 4: The task execution device set receives the subtask microservice deployed by the configuration environment system running software, and places the subtask in the lightweight virtualized runtime for execution after compilation.

[0032] Preferably, the specific method of step 2 is:

[0033] Step 2.1, construct a directed acyclic graph for representing the configuration program task structure, using subtasks as nodes and input-output dependencies between subtasks as edges;

[0034] Step 2.2: Arrange each subtask according to the directed acyclic graph, the abstract task scale of each subtask, and the task execution device information to obtain the optimal subtask microservice deployment strategy.

[0035] Preferably, in step 2.2, the method for obtaining the optimal subtask microservice deployment strategy is:

[0036] Tasks are scheduled based on the task size and the computing power of the execution device. Each task is considered in turn according to the breadth-first search order of the DAG. For each task, the relative execution time required on each task execution device in the cluster that meets the execution conditions is calculated. This time is added to the estimated execution time currently assigned to the device and then sorted. The task is assigned to the device that is expected to complete execution first. After traversing the DAG, the expected optimal cluster device task scheduling strategy is generated.

[0037] Preferably, in step 3, placing the subtask in the runtime for execution includes:

[0038] The task execution device is executed locally;

[0039] Using remote calling, a specific model is deployed in the industrial cloud server, and the corresponding RESTful API interface is called in the microservice runtime of the task execution device to upload the corresponding parameters and obtain the task execution results.

[0040] Preferably, the runtime includes:

[0041] When the main runtime is in use, it is responsible for processing the logical relationships between runtimes;

[0042] The sub-runtime is responsible for receiving the execution signal sent by the main runtime to run specific microservice functional modules, namely the hybrid stream data access microservice, modeling and simulation microservice, and data intelligent monitoring microservice.

[0043] The present invention has the following characteristics and beneficial effects:

[0044] The present invention realizes the deployment and execution of data collection and monitoring tasks by transforming the traditional microservice architecture, and provides an integrated development method for three functional modules: hybrid stream data access, complex system modeling and simulation, and intelligent operation monitoring. It does not require data export or import, and realizes efficient interconnection and intercommunication with advanced functional module data within the system. It has good expansion capabilities and can meet the needs of various industrial services such as data access processing, data monitoring, etc.

[0045] The present invention realizes an integrated solution for configuration program task development, execution and monitoring.

[0046] The present invention reduces the overall coupling degree of the system, and after the device is connected to the system, task deployment and update can be performed online from the cloud, which is beneficial to the development and debugging of the system.

[0047] The present invention uses communication protocols such as RESTful API or OPC UA to build information model mapping, realize microservice calling and data transmission, and use cloud-based remote calling strategies for complex tasks, taking into account the security, flexibility and real-time requirements of data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0049] Figure 1 A schematic diagram of the structure of a configuration environment system operation system based on a microservice architecture provided by an embodiment of the present invention;

[0050] Figure 2 A flowchart of a configuration environment system operation method based on a microservice architecture provided by an embodiment of the present invention;

[0051] Figure 3 An operation flow chart of each module in a configuration environment system operation system based on a microservice architecture provided by an embodiment of the present invention;

[0052] Figure 4 A directed acyclic graph reflecting the configuration program task structure provided by an embodiment of the present invention;

[0053] Figure 5 A routing table provided for an embodiment of the present invention;

[0054] Figure 6 The present invention provides a flowchart of a sample configuration program task instance. DETAILED DESCRIPTION

[0055] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other.

[0056] In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below with reference to the accompanying drawings.

[0057] On the contrary, the present invention covers any alternatives, modifications, equivalents, and solutions that fall within the spirit and scope of the present invention as defined by the claims. Furthermore, to facilitate a better understanding of the present invention, certain specific details are described in detail below in the detailed description of the present invention. Those skilled in the art will be able to fully understand the present invention without these details.

[0058] Example 1

[0059] The present invention provides a configuration environment system operation system based on microservice architecture, such as Figure 1 As shown, it includes five parts: microservice function module set, configuration development tool software, configuration environment system operation software, task execution device set, and communication information model;

[0060] A collection of microservice function modules, including microservice modules with multiple functions such as hybrid stream data access microservices, modeling and simulation microservices, and data intelligent monitoring microservices;

[0061] In this embodiment, the hybrid stream data access is connected to the data acquisition device through components of common industrial field communication protocols such as RS232, RS485, Modbus, CAN (Controller Area Network), EtherCAT (Ethernet Control Automation Technology), and real-time data is obtained; wherein the data acquisition device includes a field controller, sensor or camera;

[0062] Among them, intelligent operation monitoring uses a multi-source domain generalization method to implement fault diagnosis of key components in multi-source domain scenarios, which can be injected into each data acquisition function block;

[0063] In the process industry, the modeling and simulation microservice simulates flow data through digital modeling of production lines and compares it with the actual flow data collected at the industrial site to perform functional, performance, and reliability analysis of complex models. In the discrete industry, the collected sensor data is compared with the virtual simulation data and denoised using a floating threshold to obtain virtual and real residuals and realize anomaly perception.

[0064] The configuration development tool software writes configuration program tasks and generates corresponding task information files and program code files. The configuration program tasks are written in the language specified by IEC 61131-3 and include three types of microservice function modules in the microservice function module set, namely, hybrid stream data access, complex system modeling and simulation, and intelligent operation monitoring, and are developed in an integrated manner.

[0065] Specifically, in this embodiment, the configuration development tool software includes a configuration program writing module A1, an intermediate component page A2 and a function block A3, a configuration program compilation module A4, generated XML format configuration program task information A5, and CPP format configuration program code; the configuration program writing module A1 of the configuration development tool software is used to write configuration program tasks through the page A2 and the function block A3; the configuration program compilation module A4 is used to extract relevant information of the configuration program task, such as subtask decomposition results, subtask input and output dependencies, the number of data types transmitted between subtasks, the subtask execution requirement environment, etc., and compile the decomposed configuration program subtasks to generate CPP code.

[0066] The configuration environment system running software decomposes the specific task into multiple subtask microservices based on the information and program code of the specific configuration program task, and orchestrates the subtask microservices according to the computing power and execution environment of the task execution device connected to the system, and deploys the subtask microservices to the specific task execution device.

[0067] Specifically, in this embodiment, the task orchestration module B1 of the configuration environment system's operating software is used to orchestrate configuration program subtasks using the extracted XML task information file A5. The task deployment module B2 is used to deploy the orchestrated configuration program subtasks to the corresponding task execution devices. The device management module B3 is used to manage task management devices connected to the system, record their IP addresses, and perform heartbeat monitoring. The communication module B4 is used to manage communication between task execution devices, record the RESTful API interfaces exposed by each microservice during runtime, and remotely call the RESTful API interfaces exposed by the cloud server.

[0068] The task execution device compiles the received subtasks to generate executable files and places them into the lightweight virtualized microservice runtime, and executes the corresponding tasks according to the configuration program task content; wherein, the task execution device includes a programmable logic controller or an industrial gateway, supporting a variety of different industrial communication protocols.

[0069] In this embodiment, the task execution device provides three runtime samples: hybrid stream data access microservice runtime C1, modeling and simulation microservice runtime C2, and intelligent operation and monitoring microservice runtime C3.

[0070] Further, Figure 1 The task execution device provides three runtime examples: the hybrid streaming data access microservice runtime C1, the modeling and simulation microservice runtime C2, and the intelligent operation monitoring microservice runtime C3. In actual use, different runtimes can be generated based on the deployed configuration program subtasks. The industrial cloud server's model management module D1 is used to start and stop remote model calls and manage the RESTful API interfaces exposed by each model. Figure 1 Two remote call models are given: the modeling and simulation remote call microservice D2 and the intelligent operation monitoring remote call microservice D3. In actual use, more different models can be deployed as needed for runtime calls of task execution devices.

[0071] Furthermore, the communication information model implements RESTful or other communication protocols for communication between microservice runtimes deployed in the task execution devices and between the microservice runtimes and the microservice model of the industrial cloud server;

[0072] Among them, the communication module of the configuration environment system running software uniformly records all RESTful API communication interfaces and provides corresponding query services;

[0073] Among them, the other communication protocols may be OPC UA, Modbus and multiple network communication protocols not listed.

[0074] It should be noted that this embodiment also includes an industrial cloud server connected to the task execution device.

[0075] Specifically, the cloud server includes a model management module D1 and various remote call model microservices, such as the modeling and simulation remote call microservice D2 and the intelligent operation monitoring remote call microservice D3.

[0076] Among them, the industrial cloud server has powerful computing power, which can support data simulation of large-scale production line digital models, data monitoring of massive parts and components, and other functions; the configuration development tool software is responsible for writing configuration program tasks and generating corresponding task information and program code; the configuration environment system operation software can perform task orchestration and deployment through the information of configuration program tasks and the computing power and execution environment of the task execution equipment; the task execution equipment is a processing equipment deployed at the industrial site, such as a programmable logic controller or an industrial gateway, which receives the task code file, compiles it into a microservice program and puts it into the runtime for execution.

[0077] Example 2

[0078] This embodiment is based on a configuration environment system operation system based on a microservice architecture provided in Example 1, and proposes a corresponding operation method, such as Figure 2 and Figure 3 As shown, the method specifically includes the following steps:

[0079] Step 1. The application configuration environment system running software decomposes the configuration program task into multiple subtask microservices according to the configuration program task information and program code. The basis for the configuration program task decomposition includes the number of task POUs, the execution order of function block instances in each POU, the input and output pin binding variable information of the function block instance, and the execution environment required by the function block.

[0080] The method for obtaining configuration program task information and program code is as follows: The microservice function module set provides integrated development of three microservice function modules: hybrid stream data access, complex system modeling and simulation, and intelligent operation monitoring. In this embodiment, the user first selects the required modules from the packaged microservice function module set based on the specific project implementation scenario to generate a project-specific microservice function module library. If the set is missing a required module, a new corresponding module should be created and added to the module set.

[0081] In the configuration development tool software, users write configuration program tasks for a specific project based on the obtained project-specific microservice function modules, supplemented by general data processing function blocks, communication function blocks, etc. After compilation, the corresponding program is obtained as an XML-formatted configuration program task information file and a CPP-formatted configuration program code file.

[0082] Furthermore, users can import the XML-formatted configuration program task information file A5 and the CPP-formatted configuration program code file A6 generated by the configuration development tool software to divide the task into subtasks and build task models for each subtask within the system. By importing different related files, users can enable the system to perform various configuration program tasks, such as mixed stream data access, intelligent operation monitoring, and complex system modeling and simulation.

[0083] Step 2: Perform task orchestration on the multiple subtask microservices obtained by decomposition.

[0084] Specifically, in this embodiment, the task scheduling module B1 schedules the configuration program subtask as follows: First, the configuration program task information is extracted from the XML task information file A5 to construct a directed acyclic graph (DAG), such as Figure 4 As shown in the figure, this diagram reflects the structure of the entire task model. Each node represents a subtask, and the directed edges between nodes represent the input-output dependencies between subtasks. Secondly, the task scheduling module B1 obtains information about the task execution devices currently connected to the system from the device management module B3, including the device system architecture, task operating environment, the number of currently assigned subtasks, and the estimated relative execution time. This information serves as a reference for subtask scheduling. Thirdly, task scheduling is performed based on the task size and the computing power of the execution devices. Each task is considered sequentially according to the breadth-first search order of the DAG. For each task, the relative execution time required on each task execution device in the cluster that meets the execution conditions is calculated. This time is added to the device's currently assigned estimated execution time, and the task is then sorted. The task is assigned to the device that is expected to complete execution first. After traversing the DAG, the optimal task scheduling strategy for the cluster devices is generated.

[0085] Step 3: Deploy the subtask microservice to the system's task execution device set according to the task deployment strategy.

[0086] Specifically, in this embodiment, after the subtasks are orchestrated, the task deployment module B2 generates a JSON-formatted device task description file for each task execution device and distributes it, along with the subtask configuration program code file, to the device via FTP. The device task description file records information related to the subtask deployed on that device, including information about the subtask configuration program code file, the environment required for subtask compilation, the number of subtask input and output dependencies, and information about the corresponding task execution device to which it is deployed.

[0087] Step 4: The task execution device set receives the subtask microservice deployed by the configuration environment system running software, and places the subtask in the lightweight virtualized runtime for execution after compilation.

[0088] Each task execution device compiles the received subtasks into an executable file and places it into a lightweight virtualized microservice runtime. The runtime then executes the corresponding task according to the configured program task content. The microservice runtimes on each task execution device are independent of each other and call each other via a RESTful API. Each microservice runtime is encapsulated in a lightweight virtualized container, ensuring that even microservices on the same device do not interfere with each other. Even if one runtime crashes, it will not affect the execution of subtasks in other runtimes, and the crashed subtask can be quickly recovered.

[0089] It should be noted that since some configuration program tasks require a more complex execution environment or require a large amount of computing power, they cannot be run on conventional task execution devices. Instead, a remote call method can be used to deploy specific models in the industrial cloud server. For example, modeling and simulation remotely call microservice D2, intelligent operation monitoring remotely call microservice D3, etc., and the corresponding RESTful API interface is called in the microservice runtime of the task execution device to upload the corresponding parameters and obtain the task execution results.

[0090] Among them, whether it is the communication between microservices in the task execution device runtime or the remote call of microservices of a specific model on the industrial cloud server when the task execution device is running, the agreed communication interface is uniformly recorded in the communication module B4 of the configuration environment system running software and provides query services. The communication module B4 will maintain a table such as Figure 5 The routing table is shown. Users can manually add remote call-related interfaces, such as simulator model creation and simulator update. Whenever a new exposed interface microservice is deployed to the runtime of the task execution device, the corresponding record information is also added in batches.

[0091] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

[0092] like Figure 6 The following illustrates the execution process of a sample configuration program task instance provided by an embodiment of the present invention. Consider a practical scenario: monitoring a steam generator in a heat transfer loop in a nuclear power plant thermal control process. The microservices architecture configuration environment system operation method deploys tasks to the steam generator's task execution device cluster. On-device sensor data is collected using the hybrid stream data acquisition microservice, and exception monitoring and fault diagnosis are performed using the intelligent operation monitoring microservice and the modeling and simulation microservice.

[0093] Reference Figure 6 As shown, the configuration environment system's runtime software retrieves the task's XML task information file, constructs the task's Directed Graph (DAG) graph, and orchestrates the tasks. It then assigns specific control microservice subtasks and hybrid stream data access microservice subtasks to task execution devices connected to the corresponding physical control mechanisms and sensors. It also allocates the intelligent operation monitoring microservice subtasks and modeling and simulation microservice subtasks to the optimal device based on the device's computing power and the scale of the task to be executed. Based on the orchestration results, the software deploys the CPP program code for the specific subtasks to the appropriate device and begins executing the task.

[0094] The mixed flow data access microservice loop collects the temperature, pressure and other data of the steam at the inlet and outlet of the primary side loop, and sends the data to the modeling and simulation microservice and the intelligent operation monitoring microservice through information model mapping.

[0095] After receiving a deployed task, the modeling and simulation microservice first selects the simulation model corresponding to the current task scenario. Each time it receives a data packet from the hybrid streaming data access microservice, it performs a step-by-step deduction of the model, comparing the simulated data results with the actual data to assist in troubleshooting when a fault occurs.

[0096] Each time the intelligent operation monitoring microservice receives a collection data packet sent by the hybrid stream data access microservice, it selects the corresponding component from the intelligent monitoring component set for the data of each measurement point. Through knowledge-driven operation monitoring, it provides early warning before abnormalities or failures occur in core components.

[0097] The embodiments of the present invention are described in detail above with reference to the accompanying drawings, but the present invention is not limited to the described embodiments. It will be apparent to those skilled in the art that various changes, modifications, substitutions, and variations of these embodiments, including components, without departing from the principles and spirit of the present invention are still within the scope of protection of the present invention.

Claims

1. A configuration environment system operation system based on microservice architecture, characterized in that: Including microservice function module set, configuration development tool software, configuration environment system operation software, task execution equipment set, communication information model, The microservice function module set is used to provide the configuration development tool software with the microservice function blocks required for writing the configuration program; The configuration development tool software is used to write configuration program tasks and generate corresponding XML task information files and CPP program code files; The configuration environment system runs software for decomposing the configuration program task into a plurality of subtask microservices according to the information and program code of the configuration program task, and orchestrating and deploying the plurality of subtask microservices to a set of task execution devices of the system; The configuration environment system running software includes a device management module, a task scheduling module, a task deployment module and a communication module. The device management module is used to access the task execution device and record its information for the task scheduling module to make task scheduling decisions; The task scheduling module is used to perform scheduling according to the task scheduling decision and obtain the task deployment strategy; The task deployment module is used to deploy tasks according to the task deployment strategy; The communication module is used to provide a protocol communication interface to store the protocol communication interface exposed by the microservice in the task execution device in the database; The task execution device set is used to receive the subtask microservices deployed by the configuration environment system running software, and place the subtasks in the lightweight virtualized runtime for execution after compilation; The communication information model is used for data transmission between microservices in several task execution devices in a task execution device set, and for data calls between microservices in a task execution device and an industrial cloud server.

2. A configuration environment system operation system based on microservice architecture according to claim 1, characterized in that: The microservice functional blocks include hybrid stream data access microservice, modeling and simulation microservice, and data intelligent monitoring microservice.

3. The configuration environment system operation system based on microservice architecture according to claim 1, characterized in that: The configuration development tool software uses the language specified in IEC 61131-3 to write configuration program tasks and calls the microservice function blocks provided by the microservice function module set.

4. The configuration environment system operation system based on microservice architecture according to claim 1, characterized in that: The protocol communication interface is any one of a RESTful API communication interface, an OPC UA protocol communication interface, and a Modbus protocol communication interface.

5. The method for operating a configuration environment system based on a microservice architecture according to any one of claims 1 to 4, characterized in that: The steps include: Step 1: The application configuration environment system running software decomposes the configuration program task into multiple subtask microservices according to the configuration program task information and program code. The basis for the configuration program task decomposition includes the number of task POUs, the execution order of function block instances in each POU, the input and output pin binding variable information of the function block instance, and the execution environment required by the function block; Step 2: Perform task orchestration on the multiple subtask microservices obtained by decomposition; Step 3: Deploy the subtask microservice to the system's task execution device set according to the task deployment strategy; Step 4: The task execution device set receives the subtask microservice deployed by the configuration environment system running software, and places the subtask in the lightweight virtualized runtime for execution after compilation.

6. The method for operating a configuration environment system based on a microservice architecture according to claim 5, characterized in that: The specific method of step 2 is: Step 2.1, construct a directed acyclic graph for representing the configuration program task structure, using subtasks as nodes and input-output dependencies between subtasks as edges; Step 2.2: Arrange each subtask according to the directed acyclic graph, the abstract task scale of each subtask, and the task execution device information to obtain the optimal subtask microservice deployment strategy.

7. A configuration environment system operation method based on microservice architecture according to claim 6, characterized in that: In step 2.2, the method for obtaining the optimal subtask microservice deployment strategy is: Tasks are scheduled based on the task size and the computing power of the execution device. Each task is considered in turn according to the breadth-first search order of the DAG. For each task, the relative execution time required on each task execution device in the cluster that meets the execution conditions is calculated. This time is added to the estimated execution time currently assigned to the device and then sorted. The task is assigned to the device that is expected to complete execution first. After traversing the DAG, the expected optimal cluster device task scheduling strategy is generated.

8. The method for operating a configuration environment system based on a microservice architecture according to claim 5, characterized in that: In step 3, placing the subtask in a lightweight virtualized runtime for execution includes: The task execution device is executed locally; Using remote calling, a specific model is deployed in the industrial cloud server, and the corresponding RESTful API interface is called in the microservice runtime of the task execution device to upload the corresponding parameters and obtain the task execution results.

9. The method for operating a configuration environment system based on a microservice architecture according to claim 8, characterized in that: The runtime includes: When the main runtime is in use, it is responsible for processing the logical relationships between runtimes; The sub-runtime is responsible for receiving the execution signal sent by the main runtime to run specific microservice functional modules, namely the hybrid stream data access microservice, modeling and simulation microservice, and data intelligent monitoring microservice.

Images