Low-code service configuration engine and configuration method thereof

Abstract

The invention relates to the technical field of low codes, in particular to a low-code service configuration engine and a configuration method thereof. The device comprises a relation unit execution module used for defining and executing an input-operation-output relation unit; the JSON configuration analysis module is used for analyzing a configuration file in a JSON format, the configuration file comprises version information, variable initialization configuration and task configuration, and system behaviors are defined in a declarative configuration mode; the hardware abstract interface module is used for providing an operation interface irrelevant to hardware and realizing complete abstraction of hardware operation through a callback mechanism; the backup storage module is used for storing and backing up the configuration file by adopting two storage slots, and each storage slot is provided with a configurable storage space; and the real-time multi-task execution module is used for task scheduling and execution based on RTOS and supports multi-task parallel execution, conditional branching and loop control. According to the invention, the development complexity of the industrial control system is reduced, and non-technical personnel can quickly configure complex control logic.

Description

Technical Field

[0001] This invention relates to the field of low-code technology, and in particular to a low-code business configuration engine and its configuration method. Background Technology

[0002] In the field of industrial automation control, traditional control system development mainly adopts the following technical solutions:

[0003] 1. Traditional PLC programming technology: This solution is based on the IEC 61131-3 standard and uses five programming languages: ladder diagram, instruction list, structured text, sequential function chart, and function block diagram. Although powerful and compliant with international standards, it suffers from a steep learning curve, high programming complexity, strong hardware dependence, and the need for specialized IDE tools for configuration modifications. For simple logic control, traditional PLC programming is too complex and cumbersome.

[0004] 2. Embedded C language development is extremely fast, and control logic can be written directly in C language, which has a high degree of flexibility. However, it has problems such as high development threshold, tight coupling between code and hardware platform, high maintenance cost, and lack of standardized configuration management mechanism. For equipment manufacturers (OEMs), it is difficult to provide configurability to end customers.

[0005] 3. Configuration software technology provides a graphical configuration interface, which lowers the programming threshold, but it has limitations such as relatively limited functionality, the need for a dedicated development environment, the need to redeploy configuration modifications, insufficient ability to express complex logic, and difficulty in implementing configuration version management and remote updates.

[0006] Industrial IoT platforms are powerful but complex, exhibiting issues such as complex system architecture, high deployment costs, high hardware resource requirements, high learning costs, and complex maintenance. They are unsuitable for resource-constrained embedded environments. The main problems include: high development complexity (traditional solutions require specialized programming skills, have long development cycles, and high maintenance costs); strong hardware dependence (code is tightly coupled with the hardware platform, resulting in poor portability and difficulty adapting to multi-platform requirements); difficult configuration management (system parameter adjustments require recompilation and deployment, making hot updates impossible); difficulty meeting real-time requirements (traditional configuration methods cannot meet the stringent real-time requirements of industrial control); high reliability requirements (industrial environments demand extremely high system reliability, requiring robust fault tolerance and backup mechanisms); high learning curve (existing technologies require a high level of technical expertise from users, limiting widespread application); and lack of configurability (traditional solutions struggle to separate "logic" from "data," and configuration modifications still require "programming" thinking). Summary of the Invention

[0007] The present invention aims to solve at least one of the technical problems existing in the prior art.

[0008] To address this, the present invention provides a low-code business configuration engine, which reduces the development complexity of industrial control systems and allows non-technical personnel to quickly configure complex control logic.

[0009] According to an embodiment of the low-code service configuration engine of the present invention, the apparatus includes:

[0010] The relational unit execution module is used to define and execute input-operation-output relational units, wherein the relational unit includes an array of input variables, operator names, and an array of output variables;

[0011] The JSON configuration parsing module is used to parse JSON format configuration files, which contain version information, variable initialization configuration, and task configuration. The system behavior is defined using a declarative configuration approach.

[0012] The hardware abstraction interface module provides hardware-independent operation interfaces, achieving complete abstraction of hardware operations through a callback mechanism. These operation interfaces include I / O operation interfaces, task management interfaces, and system time interfaces.

[0013] A backup storage module uses two storage slots to store and back up the configuration file. Each storage slot has configurable storage space and contains a configuration header and a configuration file.

[0014] The real-time multitasking execution module is used for task scheduling and execution based on RTOS, and supports parallel execution of multiple tasks, conditional branching, and loop control.

[0015] The beneficial effects of this invention are that the low-code business configuration engine of this invention implements complex control logic through configuration files, while meeting the real-time and reliability requirements of industrial control, reducing the complexity of system development and maintenance, achieving complete separation of "logic" and "data", and enabling non-technical personnel to quickly configure complex control logic.

[0016] According to one embodiment of the present invention, the relation unit execution module includes:

[0017] The relational unit data structure unit is used to define the mapping relationship between input, operation and output. The input variable array and the output variable array support variables of configurable data.

[0018] The operator management unit is used to register built-in and custom operators;

[0019] The variable type inference unit is used to automatically infer the variable type based on the variable name prefix.

[0020] The error handling mechanism unit is used for error detection and callback processing in the code.

[0021] According to one embodiment of the present invention, the JSON configuration parsing module includes:

[0022] A recursive descent parser is used to parse the version information, variable initialization, and task configuration of the configuration file layer by layer;

[0023] A configuration verification unit is configured to verify the JSON format, configuration structure, operators, and variable types in the configuration file;

[0024] The task configuration parsing unit parses the execution cycle, priority, and execution block configuration of each task in the task configuration;

[0025] The execution block execution unit supports the execution of various execution block types, including ordinary execution blocks that execute sequentially, conditional execution blocks that execute based on condition variables, and loop execution blocks that execute repeatedly based on loop variables.

[0026] According to one embodiment of the present invention, the hardware abstraction interface module includes:

[0027] The IO operation interface unit defines the callback functions for input and output operations, which are used to implement the abstraction of hardware IO operations;

[0028] The task management operation interface unit defines callback functions for task creation and deletion, which are used to implement the abstraction of RTOS task management;

[0029] The system time operation interface unit defines callback functions for time acquisition and delay, which are used to implement the abstraction of system time operation;

[0030] The interface verification system unit is used to verify all the aforementioned callback functions.

[0031] According to one embodiment of the present invention, the backup storage module further includes:

[0032] The version management unit automatically compares the version information of the configuration files in the two storage slots during loading and prioritizes loading the configuration file with the higher version.

[0033] The data verification unit verifies the configuration file using a verification algorithm.

[0034] According to one embodiment of the present invention, the real-time multitasking execution module includes:

[0035] The task scheduling mechanism unit of the RTOS supports multiple parallel tasks, each of which has an independent execution cycle and priority.

[0036] The conditional branching support unit specifies the condition variable through the condition keyword. The relational unit in the conditional execution block will only be executed if the condition variable is true.

[0037] The loop control support unit specifies the loop variable through the loop keyword. When the loop variable is non-zero, the relational unit in the loop execution block is repeatedly executed. The loop is completely controlled by the user-configured variable.

[0038] The task status management unit is used to monitor the task running status, count the number of task executions, and generate error detection reports;

[0039] The loop safety monitoring unit records warnings and generates logs when the loop execution exceeds a preset time.

[0040] A low-code business configuration engine method according to an embodiment of the present invention includes the following steps:

[0041] S1, initialize the low-code business configuration engine as described above, and register the callback functions of each operation interface in the hardware abstraction interface module and the built-in operators in the relational unit data structure unit;

[0042] S2, read the configuration file from the backup storage module, compare the version numbers of the configuration files in the two storage slots, and load the configuration file with the higher version that has passed the verification.

[0043] S3, the configuration file is parsed through the JSON configuration parsing module, parsing the version information, variable initialization and task configuration of the configuration file layer by layer, and creating a relational unit data structure;

[0044] S4 validates JSON format, configuration structure, operator and variable type matching through configuration validation units;

[0045] S5 creates RTOS tasks for each task through the real-time multi-task execution module and schedules tasks according to the configured execution cycle and priority.

[0046] S6 executes the relational units in each execution block of the relational unit execution module in sequence, processes the input-operation-output logic, and updates the output variables.

[0047] According to an embodiment of the present invention, step S6 specifically includes the following steps:

[0048] Read the value of the input variable and perform the corresponding data reading operation according to the variable type;

[0049] Based on the operator name defined in the relation unit, search for the corresponding operator function in the operator registry;

[0050] Verify that the types of the input and output variables match the input and output types defined in the operator function. If they match, call the operator function to perform the operation.

[0051] After the calculation is completed, the result is written to the output variable, and the corresponding data writing operation is performed according to the type of the output variable;

[0052] If the matching verification or calculation fails, the system calls the error callback function to record the task name, unit name, error type, and error information.

[0053] According to an embodiment of the present invention, step S4, which verifies the matching of JSON format, configuration structure, operators, and variable types, includes:

[0054] JSON format validation: Parse the JSON configuration file to ensure that the configuration file conforms to JSON syntax specifications;

[0055] Verify the configuration structure and check if the necessary configuration items exist.

[0056] Operator verification checks whether all used operators are registered, including built-in and custom operators;

[0057] Type matching verification infers the variable type based on the variable name, ensuring that the input and output types of the operator match the variable type.

[0058] According to an embodiment of the present invention, step S5 specifically includes the following steps:

[0059] Tasks are created and deleted through the Hardware Abstraction Interface module;

[0060] Tasks are executed according to the configured period through the task scheduling mechanism unit of the RTOS;

[0061] By supporting conditional branch units, the value of the condition variable is checked, and when the condition variable is true, the relational unit in the conditional execution block is executed.

[0062] By supporting the loop control unit to check the value of the loop variable, when the loop variable is non-zero, the relational unit in the loop execution block is repeatedly executed. The user can modify the loop variable within the loop body to control the loop exit.

[0063] Error handling is provided through the loop safety monitoring unit. When the execution module of the relational unit fails, the registered error callback function is called to record the task name, unit name, error type and error message.

[0064] The task status management unit supports dynamic start and stop of tasks.

[0065] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0066] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0067] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0068] Figure 1 This is a schematic diagram of the low-code business configuration engine according to Embodiment 1 of the present invention.

[0069] Figure 2 This is a schematic diagram of the structure of the relational unit execution module in Embodiment 1 of the present invention.

[0070] Figure 3 This is a schematic diagram of the structure of the JSON configuration parsing module in Embodiment 1 of the present invention.

[0071] Figure 4 This is a schematic diagram of the hardware abstraction interface module according to Embodiment 1 of the present invention.

[0072] Figure 5 This is a schematic diagram of the backup storage module according to Embodiment 1 of the present invention.

[0073] Figure 6 This is a schematic diagram of the structure of the real-time multi-task execution module in Embodiment 1 of the present invention.

[0074] Figure 7 This is a flowchart of the method in Embodiment 2 of the present invention.

[0075] Figure 8 This is a flowchart of the configuration loading and version management process in Embodiment 1 of the present invention.

[0076] Figure 9 This is a schematic diagram of the structure of the JSON configuration parsing module in Embodiment 1 of the present invention.

[0077] In the diagram, 10 is a computer device; 1002 is a processor; 1004 is a memory; and 1006 is a transmission device. Detailed Implementation

[0078] The present invention will now be described in further detail with reference to the accompanying drawings. These drawings are simplified schematic diagrams, illustrating only the basic structure of the invention, and therefore only show the components relevant to the invention.

[0079] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential," etc., indicating orientation or positional relationships, are based on the orientation or positional relationships shown in the accompanying drawings and are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, features defined with "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0080] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0081] Example 1

[0082] This application provides a low-code business configuration engine, such as... Figure 1 As shown, the engine adopts a declarative configuration-driven architecture, and the device includes:

[0083] The relational unit execution module is used to define and execute input-operation-output relational units. A relational unit contains an array of input variables, operator names, and an array of output variables.

[0084] The JSON configuration parsing module is used to parse JSON format configuration files. The configuration files contain version information, variable initialization configuration, and task configuration, and use a declarative configuration approach to define system behavior.

[0085] The hardware abstraction interface module provides hardware-independent operation interfaces. It achieves complete abstraction of hardware operations through a callback mechanism. The operation interfaces include I / O operation interfaces, task management interfaces, and system time interfaces.

[0086] The backup storage module uses two storage slots to store and back up the configuration file. The two storage slots are the first storage slot and the second storage slot. Each storage slot has configurable storage space and contains a configuration header and a configuration file. The configuration header contains metadata such as magic number, version number, size, checksum, date information, and configuration data.

[0087] The real-time multitasking execution module is used for task scheduling and execution based on RTOS, and supports parallel execution of multiple tasks, conditional branching, and loop control.

[0088] It should be noted that before the low-code business configuration engine executes, the system needs to load and parse the task configuration in the configuration file. The task configuration includes task attributes and an array of execution blocks. The array of execution blocks consists of multiple execution blocks, and each execution block contains an array of relational units. The relational unit execution module is responsible for parsing and executing these relational units.

[0089] In this embodiment, the data types supported by the relational unit execution module include, but are not limited to, digital input, digital output, analog input, analog output, virtual digital, virtual analog, or constant types. Specifically, for example... Figure 2 As shown, the relational unit execution module includes:

[0090] The relational unit data structure unit is used to define the mapping relationship between input, operation and output. The input variable array and the output variable array support variables of configurable data.

[0091] The operator management unit is used to register built-in and custom operators. Built-in operators include, but are not limited to, logical operators, arithmetic operators, relational operators, bitwise operators, and mathematical functions. Through the custom operator registration mechanism, users can implement operator functions using programming languages, register them to the operator management unit, and use them directly in the configuration file.

[0092] The variable type inference unit is used to automatically infer the variable type based on the variable name prefix, and is used for variable type matching to prevent variable type errors.

[0093] The error handling mechanism unit is used for error detection and callback processing in the code.

[0094] The complex control logic is decomposed into simple "input-operation-output" relational units by setting up relational unit execution modules. Each relational unit is responsible for only one simple data flow processing. The relational unit data structure unit contains three core elements: an array of input variables, an operator name, and an array of output variables. Each relational unit implements the "input-operation-output" data flow processing pattern, following the single responsibility principle, which significantly reduces development complexity. In this embodiment, the control logic is defined through configuration files, achieving true low-code development, which can be configured even by non-technical personnel. It also supports dynamic combination, improving system flexibility and scalability. Variable classification avoids data type confusion.

[0095] In this embodiment, as Figure 3 As shown, the JSON configuration parsing module includes:

[0096] A recursive descent parser is used to parse the version information, variable initialization, and task configuration of the configuration file layer by layer.

[0097] Configure a validation unit to validate the JSON format, configuration structure, operators, and variable types in the configuration file;

[0098] The task configuration parsing unit parses the execution cycle, priority, and execution block configuration of each task in the task configuration;

[0099] The execution block execution unit supports the execution of various execution block types, including ordinary execution blocks that execute sequentially, conditional execution blocks that execute based on condition variables, and loop execution blocks that execute repeatedly based on loop variables.

[0100] The JSON configuration parsing module uses JSON-formatted configuration files to completely define system behavior, achieving complete separation of configuration and code. It provides a declarative configuration approach, eliminating the need for any code writing. The configuration file also includes date information, execution block and relational unit definitions, operator references, and validation metadata, ensuring the system can fully restore the task logic structure after loading the configuration file, enabling configurable execution and remote updates. This embodiment supports task-level configuration, with each task independently configuring parameters such as execution cycle and task priority. It supports multiple execution block types, and the configuration file can be modified using any text editor without requiring a dedicated IDE. It achieves complete separation of configuration and code, supports hot updates and remote configuration, provides a standardized configuration format for easy tool support and version management, supports remote configuration and parameter adjustment without recompilation, and features easy-to-understand and modify configuration files, reducing maintenance costs. It is easy to manage and supports modern CI / CD practices.

[0101] In this embodiment, as Figure 4As shown, the hardware abstraction interface module includes:

[0102] The IO operation interface unit defines the callback functions for input and output operations, which are used to implement the abstraction of hardware IO operations;

[0103] The task management operation interface unit defines callback functions for task creation and deletion, which are used to implement the abstraction of RTOS task management;

[0104] The system time operation interface unit defines callback functions for time acquisition and delay, which are used to implement the abstraction of system time operation;

[0105] The interface verification system unit is used to verify all callback functions.

[0106] The hardware abstraction interface module (HAPI) achieves complete abstraction of hardware operations through a callback mechanism, completely decoupling the core engine from the hardware platform. All hardware operations are completed through callback functions. This invention also supports rapid portability to multiple hardware platforms, requiring only the implementation of the interface layer. Furthermore, variable naming is completely abstracted, hardware mapping is completed at the underlying level, and configurations can be reused across platforms. Implemented in C, it possesses excellent cross-architecture capabilities, supporting multiple hardware platforms, including but not limited to ARM Cortex-M series, RISC-V architecture, and x86 architecture processors. The HAPI module significantly improves software portability; reduces hardware dependencies, facilitating system integration and upgrades; and enables truly hardware-independent design. Additionally, configuration files can be reused across different platforms, simplifying the hardware integration process and reducing the workload of adapting to new platforms.

[0107] In this embodiment, as Figure 5 As shown, the backup storage module also includes:

[0108] The version management unit automatically compares the version information of the configuration files in the two storage slots during loading and prioritizes loading the configuration file with the higher version. In other words, the version management unit adopts an intelligent version management strategy, automatically selecting the configuration file with the higher version number during loading. If the higher version configuration file is corrupted, it will automatically fall back to the lower version configuration file, and the new configuration file will overwrite the storage slot with the lower version number.

[0109] The data verification unit verifies the configuration file using a verification algorithm to prevent data corruption and ensure data integrity. Magic number verification ensures data validity. This dual protection ensures the reliability of the engine. Specifically, when the data verification unit detects a corrupted configuration file or a verification failure through CRC check or magic number verification, the system will automatically trigger a failover process, which includes:

[0110] Prioritize rolling back and loading the backup configuration file from another storage slot.

[0111] If both storage slots fail verification, the system automatically loads the built-in factory default security configuration to ensure that core tasks can start securely.

[0112] Fault events and rollback sources are recorded in the system log for maintenance and tracking.

[0113] This ensures that even if the main configuration file is corrupted, the system can continue to run in a predictable state, thereby improving the reliability and fault tolerance of the low-code business configuration engine.

[0114] The backup storage module uses a dual-slot mechanism for configuration backup, ensuring the reliability, security, and fault tolerance of configuration files to meet the stringent requirements of industrial environments; it also supports configuration rollback through the version management unit, providing comprehensive version management.

[0115] In this embodiment, as Figure 6 As shown, the real-time multi-task execution module includes:

[0116] The task scheduling mechanism unit of the RTOS supports multiple parallel tasks, meeting the real-time requirements of industrial control. Each task has an independent execution cycle and priority, and each task contains multiple execution blocks, supporting complex control logic.

[0117] Conditional branching supports units that specify condition variables using the condition keyword. The relational unit in the conditional execution block will only be executed if the condition variable is true.

[0118] The loop control support unit specifies the loop variable through the loop keyword. When the loop variable is non-zero, the relational unit in the loop execution block is repeatedly executed. The loop is completely controlled by the user-configured variable.

[0119] The task status management unit is used to monitor the task running status, count the number of task executions, and generate error detection reports;

[0120] The loop safety monitoring unit records warnings and generates logs when the loop execution exceeds a preset time, helping to promptly detect potential infinite loop problems.

[0121] The real-time multi-task execution module supports high-precision task cycles and complex control logic, provides efficient task scheduling, and has complete control flow management. The conditional branch support unit and loop control support unit include conditional branch selective execution based on conditions, loop control repeated execution until conditions are not met, and user-controlled loop exit conditions, which can meet the real-time requirements of industrial control. The set task status management unit and loop safety monitoring unit provide a complete error handling and monitoring mechanism, which improves operating efficiency.

[0122] This embodiment of the invention provides a low-code service configuration engine that implements complex control logic through configuration files. This engine simultaneously meets the real-time and reliability requirements of industrial control, reduces the complexity of system development and maintenance, achieves complete separation of "logic" and "data," and allows non-technical personnel to quickly configure complex control logic. It fills the market gap between traditional PLC programming and configuration software, providing equipment manufacturers with an ideal configurability solution.

[0123] Example 2

[0124] This application provides a low-code business configuration engine method, such as... Figure 7 As shown, the method includes the following steps:

[0125] S1, Initialize the low-code business configuration engine of Example 1, and register the callback functions of each operation interface in the hardware abstraction interface module and the built-in operators in the relational unit data structure unit;

[0126] S2 reads the configuration file from the backup storage module, compares the version numbers of the configuration files in the two storage slots, and loads the configuration file with the higher version that has passed the verification.

[0127] S3 parses the configuration file through the JSON configuration parsing module, parsing the version information, variable initialization and task configuration of the configuration file layer by layer, and creating a relational unit data structure;

[0128] S4 validates JSON format, configuration structure, operator and variable type matching through configuration validation units;

[0129] S5 creates RTOS tasks for each task through the real-time multi-task execution module and schedules tasks according to the configured execution cycle and priority.

[0130] S6 executes the relational units in each execution block of the relational unit execution module in sequence, processes the input-operation-output logic, and updates the output variables.

[0131] In this embodiment, step S6 specifically includes the following steps:

[0132] Read the value of the input variable and perform the corresponding data reading operation according to the variable type. For example, digital input variables and analog input variables are read directly, and constant values ​​are parsed directly.

[0133] Based on the operator name defined in the relation unit, search for the corresponding operator function in the operator registry.

[0134] Verify that the types of the input and output variables match the input and output types defined in the operator function. If they match, call the operator function to perform the operation.

[0135] After the calculation is completed, the result is written to the output variable, and the corresponding data writing operation is performed according to the type of the output variable. For example, if the output variable is a digital quantity, a digital value is written; if the output variable is an analog quantity, an analog value is written.

[0136] If the matching verification or operation fails, the system calls the error callback function. In other words, if the corresponding operator for the input variable is not found, the input variable type does not match, or the operator function is not executed, the error handling mechanism unit will be activated to handle the error and record the task name, unit name, error type, and error information.

[0137] In this embodiment, as Figure 8 As shown, step S2 specifically includes:

[0138] S21, Initialize the backup storage module;

[0139] S22, Read the configuration header information of the first storage slot;

[0140] S23, determine whether the magic number in the configuration header of the first storage slot is valid. If it is invalid, the first storage slot is an invalid storage slot. If it is valid, check whether the verification passes.

[0141] If successful, the first storage slot is a valid storage slot, and the process proceeds to step S26; otherwise, the first storage slot is an invalid storage slot.

[0142] S24, Read the configuration header information of the second storage slot;

[0143] S25, determine whether the magic number in the configuration header of the second storage slot is valid. If it is invalid, the second storage slot is an invalid storage slot. If it is valid, check whether the verification passes.

[0144] If successful, the second storage slot is a valid storage slot, and the process proceeds to step S26; otherwise, the second storage slot is an invalid storage slot.

[0145] S26. Compare the version numbers of the configuration files in the first storage slot and the second storage slot. If the version number of the first storage slot is higher, load the configuration file of the first storage slot. If the version number of the second storage slot is higher, load the configuration file of the second storage slot.

[0146] S27, retrieve the configuration file with the higher version number, and enter the JSON configuration parsing module to parse the configuration file.

[0147] It should be noted that if both the first and second storage slots are invalid, or if the JSON configuration parsing module fails to parse the configuration file, the default configuration will be used.

[0148] In this embodiment, step S4, which verifies the matching of JSON format, configuration structure, operators, and variable types, includes:

[0149] JSON format validation: Parse the JSON configuration file to ensure that the configuration file conforms to JSON syntax specifications;

[0150] Verify the configuration structure and check if the necessary configuration items exist.

[0151] Operator verification checks whether all used operators are registered, including built-in and custom operators;

[0152] Type matching verification infers the variable type based on the variable name, ensuring that the input and output types of the operator match the variable type.

[0153] In this embodiment, step S5 specifically includes the following steps:

[0154] Tasks are created and deleted through the Hardware Abstraction Interface module;

[0155] Tasks are executed according to the configured period through the task scheduling mechanism unit of the RTOS;

[0156] By supporting conditional branch units, the value of the condition variable is checked, and when the condition variable is true, the relational unit in the conditional execution block is executed.

[0157] By supporting the loop control unit to check the value of the loop variable, when the loop variable is non-zero, the relational unit in the loop execution block is repeatedly executed. The user can modify the loop variable within the loop body to control the loop exit.

[0158] Error handling is provided through the loop safety monitoring unit. When the execution module of the relational unit fails, the registered error callback function is called to record the task name, unit name, error type and error message.

[0159] The task status management unit supports dynamic start and stop of tasks.

[0160] The following is a detailed description of this embodiment using an industrial scenario:

[0161] Industrial Scenario 1: For example, the temperature control and speed regulation system of a packaging machine production line requires complex control logic such as multi-sensor data fusion, PID control, and safety interlocks. This packaging machine production line includes multiple temperature sensors, speed sensors, pressure sensors, and actuators such as heaters, coolers, conveyor belts, and safety doors. Traditional solutions require writing complex control programs involving multi-task coordination, data fusion algorithms, and PID parameter adjustment, resulting in long development cycles and difficult maintenance.

[0162] The implementation process in this embodiment specifically includes: the temperature control and speed regulation system of the packaging machine production line adopts a three-layer architecture design, where the application layer is responsible for the specific hardware operation implementation, the interface layer sets up the hardware abstraction interface module, and the core layer executes the JSON configuration parsing module and the relational unit execution module. The temperature control logic is implemented through the relational unit execution module, where the input variable array reads temperature sensor data, operators perform arithmetic operations and logical judgments, and the output variable array controls the heater and cooler.

[0163] The implementation steps include:

[0164] Step 1: System initialization, such as... Figure 7 As shown, the JSON configuration parsing module and relational unit execution module in the core layer are initialized first, and then the hardware operation callback function is registered through the hardware abstraction interface module in the interface layer.

[0165] Step 2: Configuration loading. Load the JSON configuration file from the backup storage module. The configuration file structure is as follows: Figure 3 As shown, it includes version information, variable initialization, and task configuration.

[0166] Step 3: Task creation. Based on the task definitions in the configuration file, create RTOS tasks. Each task has an independent execution cycle and priority.

[0167] After the system starts, it enters the task execution flow. The temperature control task is executed in 100ms cycles. First, the relational unit in the first execution block is executed: read the data from the three temperature sensors RAI0, RAI1, and RAI2, perform addition to get the sum VA0; divide VA0 by 3 to get the average temperature VA1; determine whether VA1 is less than 50 degrees. If it is true (temperature is below 50 degrees), then execute the heater control logic and output to RDO0 to control the heater.

[0168] As can be seen, this embodiment achieves complex multi-task coordinated control through simple JSON configuration without writing any code; the configuration parameters can be flexibly adjusted according to different product types, improving the adaptability of the equipment; the safety interlock logic is clear and easy to understand and maintain; and the parallel execution of multiple tasks improves the real-time performance and efficiency of the control system.

[0169] Industrial Scenario 2: Injection molding machine manufacturers need to provide configurable control systems for different customers. Customers can adjust control parameters according to their product characteristics, but manufacturers need to protect the core control logic. Injection molding machines include multiple subsystems such as temperature control, pressure control, speed control, and position control. In traditional solutions, customers need to modify the control program to adjust parameters, which presents problems such as high technical barriers, susceptibility to errors, and the need for on-site service.

[0170] The implementation process in this embodiment specifically includes: through the hardware abstraction interface module of the interface layer, the core engine is completely decoupled from the hardware platform, allowing the core control logic to be embedded in the core engine, while adjustable parameter configurations are exposed through the interface layer. At startup, the optimal configuration file is automatically selected through a configuration loading and version management process, and device behavior is adjusted by modifying the parameters in the configuration file, without requiring modification of the program code.

[0171] The implementation steps include:

[0172] Step 1: Template configuration generation provides preset configuration file templates for different product types, including control parameters such as temperature, pressure, and speed.

[0173] Step 2: Adjust customer parameters. Adjust the parameter values ​​in the configuration file according to the product characteristics, such as temperature setpoint, pressure threshold, speed parameters, etc.

[0174] Step 3: Configuration verification and deployment. The system verifies the correctness of the configuration file and ensures the reliability of the configuration through a dual-version backup mechanism.

[0175] Based on the injection molding machine temperature control configuration template, adjust the configuration as follows: For example, if the temperature setpoint is 220 degrees Celsius, the system executes the temperature control task every 50ms. First, the relational unit in the first execution block is executed: read the current temperature RAI0, subtract it from the set temperature VA0 (220 degrees Celsius) to obtain the temperature deviation VA1; determine if the temperature deviation is greater than 5 degrees Celsius, and store the result in VD0; determine if the temperature deviation is less than -5 degrees Celsius, and store the result in VD1. Then, the conditional execution block is executed: if VD0 is true (temperature is more than 5 degrees Celsius below the setpoint), turn on the heater RDO0; if VD1 is true (temperature is more than 5 degrees Celsius above the setpoint), turn on the cooler RDO1.

[0176] As can be seen, this embodiment achieves a good balance between core logic protection and parameter openness; customers can adjust equipment parameters independently without on-site service; configuration templates improve configuration efficiency; remote configuration updates reduce maintenance costs and ensure high reliability.

[0177] Example 3

[0178] This application provides a computer device including a processor and a memory. The memory stores at least one instruction or at least one program, which is loaded and executed by the processor to implement a low-code business configuration engine method as provided in the above method embodiments.

[0179] Figure 9 A schematic diagram of the hardware structure of a device for implementing a low-code business configuration engine method provided in the embodiments of this application is shown. The device may participate in or include the apparatus or system provided in the embodiments of this application. Figure 9 As shown, the computer device 10 may include one or more processors 1002 (the processor may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 1004 for storing data, and a transmission device 1006 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 9 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer device 10 may also include... Figure 9 The more or fewer components shown, or having the same Figure 9 The different configurations shown.

[0180] It should be noted that the aforementioned one or more processors and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuit may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer device 10 (or mobile device). As involved in the embodiments of this application, the data processing circuit serves as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0181] The memory 1004 can be used to store software programs and modules of application software, such as the program instruction / data storage device corresponding to a low-code service configuration engine method in this embodiment of the application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 1004, thereby implementing the aforementioned method. The memory 1004 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1004 may further include memory remotely located relative to the processor, and these remote memories can be connected to the computer device 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0182] The transmission device 1006 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer device 10. In one example, the transmission device 1006 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 1006 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0183] The display may be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer device 10 (or mobile device).

[0184] Example 4

[0185] This application embodiment also provides a computer-readable storage medium, which can be disposed in a server to store at least one instruction or at least one program related to implementing a low-code service configuration engine method in the method embodiment. The at least one instruction or the at least one program is loaded and executed by the processor to implement the low-code service configuration engine method provided in the above method embodiment.

[0186] Optionally, in this embodiment, the storage medium may be located at at least one of the multiple network servers in a computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0187] Example 5

[0188] This invention also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform a low-code business configuration engine method provided in the various optional embodiments described above.

[0189] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, the above description focuses on specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than that shown in the embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired results. In some implementations, multitasking and parallel processing are also possible or may be advantageous.

[0190] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device, equipment, and storage medium embodiments are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0191] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0192] Based on the above-described preferred embodiments of the present invention, and through the foregoing description, those skilled in the art can make various changes and modifications without departing from the inventive concept. The technical scope of this invention is not limited to the contents of the specification, but must be determined according to the scope of the claims.

Claims

1. A low-code business configuration engine, characterized by, The device comprises: a relationship unit execution module for defining and executing an input-operation-output relationship unit, the relationship unit comprising an input variable array, an operator name and an output variable array; a JSON configuration parsing module for parsing a JSON format configuration file, the configuration file comprising version information, variable initialization configuration and task configuration, and defining system behavior in a declarative configuration manner; a hardware abstraction interface module for providing a hardware-independent operation interface, realizing complete abstraction of hardware operation through a callback mechanism, the operation interface comprising an IO operation interface, a task management interface and a system time interface a backup storage module, the backup storage module storing and backing up the configuration file using two storage slots, each storage slot having a configurable storage space, each storage slot comprising a configuration header and a configuration file; a real-time multi-task execution module for task scheduling and execution based on an RTOS, supporting multi-task parallel execution, conditional branching and loop control.

2. The low-code business configuration engine of claim 1, wherein, The relationship unit execution module comprises: a relationship unit data structure unit for defining a mapping relationship between input-operation-output, the input variable array and the output variable array supporting configurable data variables; an operator management unit for registering built-in operators and custom operators; a variable type inference unit for automatically inferring variable types according to variable name prefixes; an error handling mechanism unit for error detection and callback processing of code.

3. The low-code business configuration engine of claim 1, wherein, The JSON configuration parsing module comprises: a recursive descent parser for layer-by-layer parsing of version information, variable initialization and task configuration of the configuration file; a configuration verification unit for verifying JSON format, configuration structure, operators and variable types in the configuration file; a task configuration parsing unit for parsing execution period, priority and execution block configuration of each task in the task configuration; an execution block execution unit supporting multiple execution block types, including normal execution block sequential execution relationship unit, conditional execution block execution according to conditional variables, and loop execution block repeated execution according to loop variables.

4. The low-code business configuration engine of claim 1, wherein, The hardware abstraction interface module comprises: an IO operation interface unit defining callback functions of input-output operations, for realizing abstraction of hardware IO operations; a task management operation interface unit defining callback functions of task creation and deletion, for realizing abstraction of RTOS task management; a system time operation interface unit defining callback functions of time acquisition and delay, for realizing abstraction of system time operations; an interface verification system unit for verifying all the callback functions.

5. The low-code business configuration engine of claim 1, wherein, The backup storage module further comprises: a version management unit automatically comparing version information of the configuration file in the two storage slots during loading, and preferentially loading the configuration file with a higher version; a data verification unit verifying the configuration file through a verification algorithm.

6. The low-code business configuration engine of claim 1, wherein, The real-time multi-task execution module comprises: an RTOS task scheduling mechanism unit supporting multiple parallel tasks, each task having an independent execution period and priority; The conditional branch support unit specifies a condition variable through a condition keyword, and only when the condition variable is true, the relational unit in the conditional execution block is executed; The loop control support unit specifies a loop variable through a loop keyword, and when the loop variable is not zero, the relational unit in the loop execution block is repeatedly executed, and the loop is completely controlled by the variable configured by the user; The task state management unit is used for monitoring the task running state, counting the task execution times, and generating error detection reports; The loop safety monitoring unit records a warning and generates a log when the loop execution exceeds a preset time.

7. A low-code business configuration engine method, characterized by, The method comprises the following steps: S1, initializing the low-code business configuration engine according to any one of claims 1 to 6, and registering the callback function of each operation interface in the hardware abstraction interface module and the built-in operator in the relational unit data structure unit; S2, reading the configuration file from the backup storage module, comparing the version numbers of the configuration files in the two storage slots, and loading the configuration file with a high version number and passing the verification; S3, parsing the configuration file through the JSON configuration parsing module, layer by layer parsing the version information, variable initialization and task configuration of the configuration file, and creating a relational unit data structure; S4, verifying the JSON format, configuration structure, operator and variable type matching through the configuration verification unit; S5, creating an RTOS task for each task through the real-time multi-task execution module, and scheduling the tasks according to the configured execution period and priority; S6, sequentially executing the relational units in each execution block in the relational unit execution module, processing the input-operation-output logic, and updating the output variables.

8. The low-code business configuration engine method of claim 7, wherein, The step S6 specifically comprises the following steps: Read the value of the input variable, and perform the corresponding data reading operation according to the variable type; According to the operator name defined in the relational unit, find the corresponding operator function in the operator registration table; Verify whether the types of the input and output variables match the input and output types defined by the operator function, and if they match, call the operator function to perform the operation; After the operation is completed, write the result to the output variable, and perform the corresponding data writing operation according to the output variable type; If the matching verification or operation execution fails, the system calls the error callback function to record the task name, unit name, error type and error information.

9. The low-code business configuration engine method of claim 7, wherein, The step S4 of verifying the JSON format, configuration structure, operator and variable type matching comprises: JSON format verification, parsing the JSON configuration file to ensure that the configuration file conforms to the JSON syntax specification; Configuration structure verification, checking whether the necessary configuration items exist; Operator verification, checking whether all used operators have been registered, including built-in operators and custom operators; Type matching verification, inferring the variable type according to the variable name to ensure that the input and output types of the operator match the variable type.

10. The low-code business configuration engine method of claim 7, wherein, The step S5 specifically comprises the following steps: Creating and deleting tasks through the hardware abstraction interface module; Executing the tasks according to the configured period through the task scheduling mechanism unit of the RTOS; By supporting conditional branch unit, check the value of condition variable, when condition variable is true, execute the relational unit in conditional execution block; By supporting loop control unit, check the value of loop variable, when loop variable is non-zero, repeat the execution of relational unit in loop execution block, user modify loop variable in loop body to control loop exit; By loop safety monitoring unit, provide error handling, when relational unit execution module fails, call the registered error callback function, record task name, unit name, error type and error message; By task state management unit, support dynamic start and stop of task.

Images