Extensible configurable intelligent orchestration method, system, medium, and apparatus

Abstract

The application provides an extensible configurable intelligent linkage method, system, medium and equipment, comprising: step 1: obtaining the configuration file of the linkage trigger source and the preplan, obtaining the related information of the linkage trigger source and the trigger preplan; step 2: according to the type of the trigger source, performing the corresponding type of trigger source processing on the linkage trigger source information; step 3: according to the type of the trigger source, monitoring the trigger condition of the trigger source, if the trigger condition of the trigger source is reached, executing the corresponding trigger preplan execution command; step 4: when the linkage trigger source triggers and the preplan execution ends, recording the linkage trigger time, the trigger condition, the preplan execution time and the preplan execution result through a log. The application supports the configuration of multiple linkage trigger sources and trigger preplans, and can realize specific linkage functions through custom trigger sources and trigger preplans, thereby meeting various linkage requirements of the industrial control system.

Description

Technical Field

[0001] This invention relates to the field of intelligent linkage technology, and more specifically, to a scalable and configurable intelligent linkage method, system, medium, and device. Background Technology

[0002] With the rapid development of industrial automation, industrial control systems require extensive intelligent linkages for automatic control or various interconnections of equipment. Due to the widespread application of industrial control systems, higher standards have been set for the implementation of linkage solutions to support their diverse and customized linkage needs.

[0003] Intelligent linkage is a widely used function in industrial control systems. It typically requires the use of linkage functions to achieve automatic control and event triggering. However, linkage needs to support various triggering sources and triggering plans with different mechanisms.

[0004] Patent document CN102355060B (application number 201110306171.3) discloses a substation intelligent linkage system. The technical solution of this invention provides a substation intelligent linkage system, including a communication server responsible for communicating with the substation intelligent auxiliary integrated monitoring system and the substation SCADA system, receiving real-time data transmitted from them; a linkage inference server responsible for inferring the real-time data received by the communication server; if the real-time data conforms to a pre-set linkage logic, it searches for the corresponding virtual remote signal and outputs the virtual remote signal; and a linkage execution server responsible for converting the virtual remote signal sent by the linkage inference server into action commands to control the substation intelligent auxiliary integrated monitoring system and the substation SCADA system, and then controlling the substation intelligent auxiliary integrated monitoring system and the substation SCADA system according to these action commands. This patent infers the real-time data of the substation to determine whether it conforms to the pre-set linkage logic, then searches for the corresponding virtual remote signal, and then converts it into action commands. In this linkage system, the linkage judgment method and action commands are specific, resulting in relatively limited configuration and making it difficult to adapt to other linkage requirements. Summary of the Invention

[0005] In view of the deficiencies in the prior art, the purpose of this invention is to provide a scalable and configurable intelligent linkage method, system, medium and device.

[0006] The scalable and configurable intelligent linkage method provided by the present invention includes:

[0007] Step 1: Obtain the configuration files of the linkage trigger source and the trigger plan, and get relevant information about the linkage trigger source and the trigger plan;

[0008] Step 2: Process the linkage trigger source information according to the type of trigger source;

[0009] Step 3: Monitor the trigger source trigger condition according to the type of the trigger source. If the trigger condition of the trigger source is met, execute the corresponding trigger plan execution command;

[0010] Step 4: At the time of the linkage trigger source trigger and the end of the plan execution, record the linkage trigger time, trigger condition, plan execution time and plan execution result in the log.

[0011] Preferably, the step 1 comprises:

[0012] Step 1.1: Read the relevant configuration information from the configuration file, including trigger source name, trigger source type, trigger source trigger condition, plan name, plan type and plan action;

[0013] Wherein, the trigger source name is used to identify the configured trigger source, and the name of each trigger source is unique; the trigger source type is used to define the type of the trigger source trigger condition, including time trigger condition or event trigger condition; the plan name is used to identify the plan associated with the trigger source, and the name of each plan is unique; the plan type is used to define the type of the plan, including variable control or program execution; the plan action is used to define the specific action to be executed, and a trigger source is associated with multiple plans;

[0014] Step 1.2: Analyze the trigger condition of the trigger source, including the analysis of the time format in the time trigger condition or the analysis of the expression containing the data variable in the event trigger condition, and the analysis of the custom parameters of the plan action.

[0015] Preferably, the step 2 comprises:

[0016] Step 2.1: Enqueue the relevant configuration including the trigger source type and the trigger condition to the trigger source queue, and limit the use of the linkage system resources by the upper limit of the queue of the trigger source queue;

[0017] Step 2.2: Dequeue the trigger source configuration from the trigger source queue, and monitor the trigger condition according to the type of the trigger source.

[0018] Preferably, the step 3 comprises:

[0019] Step 3.1: After obtaining the trigger source to be detected, monitor the trigger condition according to the type of the trigger source;

[0020] Step 3.2: The trigger source meets the trigger condition, and according to the trigger plan associated with the obtained trigger source, enqueues the trigger plan execution command to the plan command queue, and limits the use of the linkage system resources by the upper limit of the queue of the plan command queue;

[0021] Step 3.3: According to the type of the plan, the plan action and the plan custom parameters required to be executed are obtained from the plan execution command, the plan action is executed, and the linkage function is completed.

[0022] According to the application, an extensible and configurable intelligent linkage system is provided, comprising:

[0023] Module M1: Obtain the linkage trigger source and the configuration file of the plan, and obtain the linkage trigger source and the related information of the triggered plan;

[0024] Module M2: According to the type of the trigger source, the trigger source processing of the corresponding type is performed on the linkage trigger source information;

[0025] Module M3: According to the type of the trigger source, the trigger source trigger condition is monitored, and if the trigger condition of the trigger source is reached, the corresponding trigger plan execution command is executed;

[0026] Module M4: When the linkage trigger source triggers and the plan execution ends, the time of the linkage trigger, the trigger condition, the plan execution time and the result of the plan execution are recorded through the log.

[0027] Preferably, the module M1 comprises:

[0028] Module M1.1: Read the related configuration information from the configuration file, including the trigger source name, the trigger source type, the trigger source trigger condition, the plan name, the plan type and the plan action;

[0029] Wherein, the trigger source name is used to identify the configured trigger source, and the name of each trigger source is unique; the trigger source type is used to define the type of the trigger source trigger condition, including the time trigger condition or the event trigger condition; the plan name is used to identify the plan associated with the trigger source, and the name of each plan is unique; the plan type is used to define the type of the plan, including the variable control or the execution program; the plan action is used to define the specific action to be executed, and multiple plans are associated with the same trigger source;

[0030] Module M1.2: Analyze the trigger condition of the trigger source, including the analysis of the time format in the time trigger condition or the analysis of the expression containing the data variable in the event trigger condition, and analyze the custom parameters of the plan action.

[0031] Preferably, the module M2 comprises:

[0032] Module M2.1: The related configurations including the trigger source type and the trigger condition are enqueued to the trigger source queue, and the system resource usage of the linkage is limited through the upper limit of the queue of the trigger source queue;

[0033] Module M2.2: The trigger source configuration is dequeued from the trigger source queue, and the trigger condition is monitored according to the type of the trigger source.

[0034] Preferably, the module M3 comprises:

[0035] Module M3.1: after obtaining the trigger source to be detected, trigger condition monitoring is performed according to the type of the trigger source;

[0036] Module M3.2: when the trigger source monitoring meets the trigger condition, the trigger plan associated with the obtained trigger source is executed, and the trigger plan execution command is queued into the plan command queue, and the use of the linked system resources is limited by the upper limit of the queue of the plan command queue;

[0037] Module M3.3: according to the type of the plan, the plan action and the plan custom parameter required to be executed are obtained from the plan execution command, the plan action is executed, and the linkage function is completed.

[0038] According to the present application, a computer readable storage medium storing a computer program is provided, and the computer program is executed by a processor to realize the steps of the extensible and configurable intelligent linkage method.

[0039] According to the present application, an electronic device is provided, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is executed by the processor to realize the steps of the extensible and configurable intelligent linkage method.

[0040] Compared with the prior art, the present application has the following beneficial effects:

[0041] (1) The linkage trigger source of the present application supports different types and custom types, so as to meet the linkage requirements of the industrial control system under different trigger sources;

[0042] (2) The present application has multiple trigger plan configurations for the same trigger source, supports multiple linkage plans of different types, and supports complex plan actions of the industrial control system;

[0043] (3) The present application has different parameter types and specific parameter configurations for different linkage configurations, and the configuration of the linkage can be distributed. BRIEF DESCRIPTION OF DRAWINGS

[0044] Other features, objects and advantages of the present application will become more apparent from the following detailed description of non-limiting embodiments, made with reference to the accompanying drawings:

[0045] Figure 1 is a framework diagram of the present application;

[0046] Figure 2 is the overall process of the present design. DETAILED DESCRIPTION

[0047] The application will be described in detail below with reference to specific embodiments. The following examples will help those skilled in the art to further understand the application, but do not limit the application in any form. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the application. These are within the scope of protection of the application.

[0048] Embodiments

[0049] As Figure 1 and Figure 2 The application provides an extensible and configurable intelligent linkage method, comprising the following steps:

[0050] Step 1: Obtain the configuration information of the linkage trigger source and the preplan, and read the configuration related information from the configuration file by the linkage configuration module M100.

[0051] Step 2: Distribute the obtained linkage trigger source information to the trigger source processing module M102 of the corresponding type according to the type of the trigger source by the linkage trigger source distribution module M101.

[0052] Step 3: According to the type of the trigger source, the trigger source trigger condition is monitored by the corresponding trigger source processing module M102, and if the trigger condition of the trigger source is reached, the corresponding trigger preplan execution command is sent to the preplan execution command distribution module M103.

[0053] Step 4: After the preplan execution command distribution module M103 receives the preplan execution command, according to the type of the preplan execution command, it is distributed to the corresponding preplan execution module M104, and the module executes the preplan.

[0054] Step 5: When the linkage trigger source triggers and the preplan execution ends, the linkage log recording module M105 records the time and trigger condition of the linkage trigger, and the result of the preplan execution.

[0055] The step 1 comprises the following steps:

[0056] Step 1.1: The linkage configuration module M100 reads the related configuration information from the configuration file, such as Figure 2 The flow S100 comprises the related information of the linkage trigger source and the trigger preplan, such as the trigger source name, the trigger source type, the trigger source trigger condition, the preplan name, the preplan type, and the preplan action, for example:

[0057] Trigger source name Trigger source type Trigger condition Plan name Plan type Plan action trigger Time trigger source Daily 14:00:00 plan Variable control Variable var value plus 1

[0058] Wherein the trigger source name is used to identify the configured trigger source, the name of each trigger source is unique, the trigger source type is used to define the type of trigger condition of the trigger source, such as a time trigger condition or an event trigger condition, the preplan name is used to identify the preplan associated with the trigger source, the name of each preplan is unique, and the preplan type is used to define the type of preplan, such as variable control or program execution. The preplan action is used to define a specific action to be executed, and multiple preplans can be associated with the same trigger source.

[0059] Step 1.2: As Figure 2 Flow S101, the trigger condition of the trigger source is parsed from the read trigger source configuration information, such as the parsing of the time format in the time trigger condition or the parsing of the expression containing the data variable in the event trigger condition. The custom parameters of the preplan action are parsed.

[0060] The step 2 includes the following steps:

[0061] Step 2.1: After the configuration information of the linkage is parsed in step 1.2, as Figure 2 Flow S200, the trigger source type and trigger condition related configuration are enqueued to the trigger source queue TriggerQueue by the linkage trigger source distribution module M101, and the use of system resources for linkage is limited by the upper limit of the TriggerQueue queue.

[0062] Step 2.2: As Figure 2 Flow S201, the trigger source configuration is dequeued from the trigger source queue TriggerQueue, and the type of trigger source is called, such as a time trigger source, which calls the time trigger source processing module M102 interface to distribute the trigger source to the time trigger source processing module M102 for monitoring of the trigger condition; such as an event trigger source, which calls the event trigger source processing module M102 interface to distribute the trigger source to the event trigger source processing module M102 for monitoring of the trigger condition; a custom trigger source processing module can also be defined for monitoring of the corresponding trigger condition.

[0063] The step 3 includes the following steps:

[0064] Step 3.1: After the trigger source to be detected is obtained by the trigger source processing module M102, as Figure 2 Flow S300, the trigger condition is monitored according to the type of trigger source, such as a time trigger source, which detects the parsed time condition, and if the specified time or time period is reached, the trigger condition of the trigger source is met.

[0065] Step 3.2: The trigger source monitoring meets the trigger condition in step 3.1, as Figure 2Flow S301, according to the trigger source associated with the trigger plan obtained in step 1, the trigger plan execution command is sent to the plan execution command distribution module M103, and is queued to the plan command queue PlanQueue, and the use of the linked system resources is limited by the upper limit of the PlanQueue queue.

[0066] The step 4 includes the following steps:

[0067] Step 4.1: as Figure 2 Flow S400, after the plan execution command distribution module M103 receives the plan execution command, the plan command is dequeued from the plan command queue PlanQueue, and according to the type of the plan, such as variable control, the variable control plan execution module interface is called, and the plan execution command is distributed to the variable control plan execution module. If there are multiple plans, the plan execution command is distributed to the corresponding plan execution module M104.

[0068] Step 4.2: After the plan execution module M104 receives the plan execution command, as Figure 2 Flow S401, the plan action to be executed is obtained from the plan execution command, the plan self-defined parameter is executed, the plan action is completed, and the linkage function is completed.

[0069] The step 5 includes the following steps:

[0070] Step 5.1: as Figure 2 Flow S500, after the linkage plan execution is completed, it indicates that the linkage trigger source has been triggered and the corresponding linkage plan action has been executed. The linkage trigger source trigger time, trigger condition, plan execution time, and plan action execution result are sent to the linkage log recording module M105, and the linkage log is recorded.

[0071] Those skilled in the art know that in addition to implementing the system, device and each module thereof provided by the present application in a pure computer readable program code manner, the same program can be realized in the form of logic gates, switches, special integrated circuits, programmable logic controllers and embedded microcontrollers by logically programming the method steps. Therefore, the system, device and each module thereof provided by the present application can be considered as a hardware component, and the modules included therein for realizing various programs can also be considered as structures within the hardware component; the modules for realizing various functions can also be considered as both software programs for realizing methods and structures within hardware components.

[0072] The specific embodiments of the present application are described above. It needs to be understood that the present application is not limited to the specific embodiments described above, and various changes or modifications can be made by those skilled in the art within the scope of the claims, which does not affect the essential content of the present application. The embodiments of the present application and the features in the embodiments can be combined with each other at will without conflict.

Claims

1. A scalable and configurable intelligent linkage method, characterized in that, include: Step 1: Obtain the configuration files of the linkage trigger source and the trigger plan, and get relevant information about the linkage trigger source and the trigger plan; Step 2: Process the linkage trigger source information according to the type of trigger source; Step 3: Based on the type of trigger source, monitor the trigger conditions of the trigger source. If the trigger conditions of the trigger source are met, execute the corresponding trigger plan execution command. Step 4: When the linkage trigger source is triggered and the contingency plan is executed, record the trigger time, trigger conditions, contingency plan execution time, and contingency plan execution results in the log. Step 1 includes: Step 1.1: Read the relevant configuration information from the configuration file, including the trigger source name, trigger source type, trigger source trigger condition, plan name, plan type, and plan action; Among them, the trigger source name is used to identify the configured trigger source, and each trigger source name is unique; the trigger source type is used to define the type of trigger condition of the trigger source, including time trigger condition or event trigger condition; the plan name is used to identify the plan associated with the trigger source, and each plan name is unique; the plan type is used to define the type of plan, including variable control or execution program; the plan action is used to define the specific action to be executed, and multiple plans can be associated with the same trigger source; Step 1.2: Parse the triggering conditions of the triggering source, including parsing the time format in the time triggering condition or parsing the expression containing data variables in the event triggering condition, and parsing the custom parameters of the pre-planned action; Step 3 includes: Step 3.1: After obtaining the trigger source to be detected, monitor the trigger conditions according to the type of trigger source; Step 3.2: When the trigger source monitoring meets the triggering conditions, according to the trigger plan associated with the obtained trigger source, the execution command of the trigger plan is enqueued into the plan command queue. The upper limit of the plan command queue is used to limit the use of linked system resources. Step 3.3: Based on the type of contingency plan, obtain the contingency plan actions to be executed and the custom parameters of the contingency plan from the contingency plan execution command, execute the contingency plan actions, and complete the linkage function.

2. The scalable and configurable intelligent linkage method according to claim 1, characterized in that, Step 2 includes: Step 2.1: Enqueue the relevant configurations, including the trigger source type and trigger conditions, into the trigger source queue, and limit the use of linked system resources by using the upper limit of the trigger source queue; Step 2.2: Dequeue the trigger source configuration from the trigger source queue and monitor the trigger conditions according to the type of trigger source.

3. A scalable and configurable intelligent linkage system, characterized in that, include: Module M1: Obtain the configuration files of the trigger source and the pre-set plan for linkage, and get relevant information about the trigger source and the trigger plan; Module M2: Processes the linkage trigger source information according to the type of trigger source; Module M3: Based on the type of trigger source, monitor the trigger conditions of the trigger source. If the trigger conditions of the trigger source are met, execute the corresponding trigger plan execution command. Module M4: When the linkage trigger source is triggered and the contingency plan is executed, the time of the linkage trigger, the triggering conditions, the contingency plan execution time, and the result of the contingency plan execution are recorded in the log. The module M1 includes: Module M1.1: Reads relevant configuration information from the configuration file, including trigger source name, trigger source type, trigger source trigger condition, plan name, plan type, and plan action; Among them, the trigger source name is used to identify the configured trigger source, and each trigger source name is unique; the trigger source type is used to define the type of trigger condition of the trigger source, including time trigger condition or event trigger condition; the plan name is used to identify the plan associated with the trigger source, and each plan name is unique; the plan type is used to define the type of plan, including variable control or execution program; the plan action is used to define the specific action to be executed, and multiple plans can be associated with the same trigger source; Module M1.2: Parses the triggering conditions of the triggering source, including parsing the time format in the time triggering condition or parsing the expression containing data variables in the event triggering condition, and parsing the custom parameters of the pre-planned action; The module M3 includes: Module M3.1: After obtaining the trigger source to be detected, it monitors the trigger conditions according to the type of the trigger source; Module M3.2: When the trigger source is detected and the trigger condition is met, the trigger plan associated with the obtained trigger source is queued into the plan command queue. The upper limit of the plan command queue is used to limit the use of linked system resources. Module M3.3: Based on the type of contingency plan, it obtains the contingency plan actions to be executed and the custom parameters of the contingency plan from the contingency plan execution command, executes the contingency plan actions, and completes the linkage function.

4. The scalable and configurable intelligent linkage system according to claim 3, characterized in that, The module M2 includes: Module M2.1: Enqueues relevant configurations, including trigger source type and trigger conditions, into the trigger source queue, and limits the use of linked system resources by using the upper limit of the trigger source queue; Module M2.2: Dequeues trigger source configurations from the trigger source queue and monitors trigger conditions based on the type of trigger source.

5. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the scalable and configurable intelligent linkage method as described in any one of claims 1 to 2.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the computer program is executed by the processor, it implements the steps of the scalable and configurable intelligent linkage method as described in any one of claims 1 to 2.

Images