Visual arrangement method and device for internet of things rule chain, medium, product and equipment

Abstract

The invention belongs to the field of income and expenditure data processing, and provides an Internet of Things rule chain visual arrangement method and device, a medium, a product and equipment. The method comprises the following steps: receiving service logic, constructing a matched Internet of Things rule item and creating a rule chain canvas; analyzing the service logic, determining a required rule node, judging whether the required rule node exists in a preset rule chain node library or not, and if yes, directly calling the corresponding rule node; otherwise, customizing a rule node; arranging all required rule nodes in a rule chain canvas according to the business logic, configuring information of each rule node, and calling a connection tool to connect the corresponding rule nodes, so that the business logic is converted into a data flow path; and after verification operation and debugging operation are carried out on each rule node in the data flow path, an Internet of Things rule chain passing the test is obtained, and deployment and publishing are carried out. The visual editing efficiency and the data verification efficiency of the Internet of Things rule chain can be improved, and finally stable operation of service logic is guaranteed.

Description

Technical Field

[0001] The present invention belongs to the field of income and expenditure data processing, and particularly relates to an Internet of Things rule chain visualization orchestration method, device, medium, product and equipment. Background Technique

[0002] The statements in this part only provide background technical information related to the present invention and do not necessarily constitute prior art.

[0003] Rule Chain technology is a flexible data processing technology widely used in the field of the Internet of Things (IoT). Visualization orchestration of rule chains is an intuitive rule chain technology that allows users to build complex rule chains through a graphical interface.

[0004] The existing Internet of Things rule chain visualization orchestration methods still have the following problems: (1) To avoid users directly accessing the rule chain source code, the prior art uses drag-and-drop flowcharts to configure the Internet of Things rule chain. However, the existing rule node library is encapsulated and fixed. Before configuring the Internet of Things rule chain, the business logic needs to be sorted out into a logic that can be implemented by the rule nodes in the existing rule node library, which complicates simple logic and the configuration efficiency still needs to be improved.

[0005] (2) Data verification and saving is a step in the persistent operation of the rule chain project. Most of the current rule nodes perform data verification according to the rules set according to their uses. However, for an Internet of Things rule chain containing multiple types of rule nodes, the matching rule design is cumbersome, resulting in low data verification efficiency; in addition, during the process of data verification and saving, usually data entry is in the property panel corresponding to each rule node, and at most one node property panel can be displayed on the page at the same time. If there are multiple rule node data not saved, the data verification results cannot be presented in real time, thus also reducing the data verification efficiency. Summary of the Invention

[0006] To solve the above technical problems, the present invention provides an Internet of Things rule chain visualization orchestration method, device, medium, product and equipment, which can improve the visualization orchestration efficiency and data verification efficiency of the Internet of Things rule chain, and ultimately ensure the stable operation of the business logic.

[0007] To achieve the above object, the present invention adopts the following technical solutions: The first aspect of the present invention provides an Internet of Things rule chain visualization orchestration method.

[0008] In one or more embodiments, an Internet of Things rule chain visualization orchestration method is provided, including: Receive the service logic, construct a matching Internet of Things (IoT) rules project, and create a rules chain canvas; Parse the service logic to determine the required rules nodes, and judge whether the required rules nodes exist in a preset rules chain node library. If so, directly retrieve the corresponding rules nodes; otherwise, customize the rules nodes. Arrange all the required rules nodes in the rules chain canvas according to the service logic, configure the information of each rules node, and retrieve a connection tool to connect the corresponding rules nodes, so that the service logic is transformed into a data flow path; After performing a verification operation and a debugging operation on each rules node in the data flow path, obtain an IoT rules chain that passes the test and deploy and publish it.

[0009] As an implementation, during the process of performing a verification operation on each rules node in the data flow path, for non-customized rules nodes, the same set of data verification rules is used for verification.

[0010] As an implementation, during the process of performing a verification operation on each rules node in the data flow path, the verification status of all non-customized rules nodes is uniformly packaged, and when a save command is received, the non-passed items are displayed in a message pop-up window; the non-passed items record the IDs of the corresponding non-customized rules nodes.

[0011] As an implementation, during the process of performing a verification operation on each rules node in the data flow path, for customized rules nodes, verification rules are adaptively matched.

[0012] As an implementation, the types of rules nodes stored in the preset rules chain node library include: trigger nodes, logic nodes, output nodes, and storage nodes.

[0013] As an implementation, for customized rules nodes, they obtain data from an external data source through the MQTT message subscription method, and then perform custom processing on the data through a custom function and save it.

[0014] The second aspect of the present invention provides an IoT rules chain visualization and orchestration device.

[0015] In one or more embodiments, an IoT rules chain visualization and orchestration device includes: An IoT rules project construction module, which is used to receive service logic, construct a matching IoT rules project, and create a rules chain canvas; A rule node determination module, which is used to parse the business logic, determine the required rule nodes, and judge whether the required rule nodes exist in a preset rule chain node library. If so, directly retrieve the corresponding rule nodes; otherwise, customize the rule nodes. A data flow path construction module, which is used to arrange all the rule nodes of the requirements in the rule chain canvas according to the business logic, configure the information of each rule node, and retrieve a connection tool to connect the corresponding rule nodes, so as to transform the business logic into a data flow path. An Internet of Things rule chain publishing module, which is used to perform a verification operation and a debugging operation on each rule node in the data flow path, obtain an Internet of Things rule chain that passes the test, and perform deployment and publishing.

[0016] The third aspect of the present invention provides a computer-readable storage medium.

[0017] A computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the steps in the above-mentioned Internet of Things rule chain visualization orchestration method.

[0018] The fourth aspect of the present invention provides a computer program product.

[0019] A computer program product includes computer programs / instructions. When the computer programs / instructions are executed by a processor, they implement the steps in the above-mentioned Internet of Things rule chain visualization orchestration method.

[0020] The fifth aspect of the present invention provides an electronic device. <(

[0021] An electronic device includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the steps in the above-mentioned Internet of Things rule chain visualization orchestration method.

[0022] Compared with the prior art, the beneficial effects of the present invention are: (1) The present invention first searches for and directly retrieves the required rule nodes parsed from the business logic from a preset rule chain node library. When the required rule nodes do not exist in the preset rule chain node library, it customizes the rule nodes, transforming the business logic into a matching data flow path, which makes the data flow path more in line with the actual business logic and has high configuration efficiency.

[0023] (2) The present invention validates non-customized rule nodes using the same set of data verification rules, avoiding the cumbersome process of rule design and improving data verification efficiency. Moreover, it uniformly packages the verification status of all non-customized rule nodes. When receiving a save command, it displays the non-passing items with the IDs of the corresponding non-customized rule nodes in the non-passing items of the message pop-up window, so that the node property panel of the corresponding item can be automatically opened, and the non-passing property items of the specific rule node can be quickly located, improving the verification efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The accompanying drawings forming a part of this specification are used to provide a further understanding of the present invention. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention.

[0025] Figure 1 is a schematic flowchart of the method for visual arrangement and orchestration of the Internet of Things rule chain in an embodiment of the present invention; Figure 2 is a schematic diagram of the process of visual arrangement and orchestration of the Internet of Things rule chain in an embodiment of the present invention; Figure 3 is a schematic structural diagram of the device for visual arrangement and orchestration of the Internet of Things rule chain in an embodiment of the present invention; Figure 4 is a schematic diagram of an electronic device in an embodiment of the present invention; Figure 5 is the rule node type in the preset rule chain node library in an embodiment of the present invention; Figure 6 is the configuration information of the rule node for MQTT message subscription in an embodiment of the present invention; Figure 7 is a schematic diagram of the verification operation for the data flow path in an embodiment of the present invention; Figure 8 is a schematic diagram of the debugging operation for the data flow path in an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0026] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0027] It should be noted that the following detailed description is illustrative and is intended to provide further explanation of the present invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which the present invention belongs.

[0028] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present invention. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprise" and / or "include" are used in this specification, they specify the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0029] Figure 1 is a schematic flowchart of a method for visual orchestration of an Internet of Things rule chain in an embodiment of the present invention. As Figure 1 shown, the method for visual orchestration of the Internet of Things rule chain in this embodiment may include the following steps S101 to S104.

[0030] S101: Receive business logic, construct a matching Internet of Things rule project, and create a rule chain canvas.

[0031] In the specific implementation process, the business logic can be set according to the actual situation. For example, the status of lighting fixtures in a certain building is controlled.

[0032] Specifically, the Internet of Things rule project includes the name and code of the Internet of Things rule chain project. It can be understood here that for some common rule chain technologies, a rule chain template can also be formed based on certain rules. When building an Internet of Things rule project, an existing template can be selected for transformation to form the corresponding Internet of Things rule project.

[0033] S102: Analyze the business logic, determine the required rule nodes, and judge whether the required rule nodes exist in a preset rule chain node library. If so, directly retrieve the corresponding rule nodes; otherwise, customize the rule nodes.

[0034] Among them, as Figure 5 shown, the types of rule nodes stored in the preset rule chain node library include: trigger nodes, logic nodes, output nodes, and storage nodes.

[0035] It should be noted here that the trigger node can be configured as a timed task trigger, exception capture, MQTT message subscription, Websoket client, read message bus, HTTP request, and HTTP listener.

[0036] The logic node can be configured as a custom function, routing, delay / flow control, message splitting, and data injection.

[0037] The output node can be configured as message notification, MQTT message push, write to message bus, Kafka message push, command issuance, set device attributes, and HTTP response.

[0038] The storage node can be configured to write to a database and write to an object storage.

[0039] In some other alternative embodiments, the trigger node, the logic node, the output node, and the storage node can also be customized by those skilled in the art to form a custom rule node.

[0040] For the customized rule node, it obtains data from an external data source in the MQTT message subscription manner, and then customizes and processes the data through a custom function and saves it.

[0041] S103: Arrange all the rule nodes of the requirements in the rule chain canvas according to the business logic, configure the information of each rule node, and call the connection tool to connect the corresponding rule nodes, so that the business logic is transformed into a data flow path, as Figure 2 shown.

[0042] The data flow path here can be one or branched, depending on the business logic.

[0043] Under normal circumstances, the dragging of rule nodes should follow certain rules. Otherwise, randomly dragging and piecing together will also result in a rule chain, but this chain is meaningless. Usually, the trigger node should be placed at the front, followed by a logic node. The presence or absence of the logic node should be selected according to the current business scenario. There should be at least one output node and one storage node, and the connection of the connection lines is also restricted. The output of the previous node should point to the input of the next node, and the flow will be different vice versa.

[0044] For example, when the rule node needs to have the function of processing and storing time-series data, the user can select a rule node of "MQTT message subscription" to obtain data from an external data source, then customize and process the data through a "custom function" rule node, and finally save the data to the database through a "write to database" rule node, thus completing a simple rule chain.

[0045] Configuring node information is a continuous supplement and improvement to the design of the rule chain. In this embodiment, for each rule node, the user configures the corresponding attributes through the graphical user interface. Clicking on the node in the rule chain design canvas can open the corresponding configuration interface, and configure the attributes of the node as needed. In addition, each rule node will have a corresponding help information, which details and comprehensively introduces the usage skills of the node and how to fill in each attribute.

[0046] It can be understood here that the design of the rule chain and the configuration of node information are in a parallel relationship, that is, the flow direction of the rule chain can be designed first and then the nodes can be configured, or the node information can be configured first and then the rule nodes can be connected in series to form a rule chain.

[0047] For example, as Figure 6 shown, the rule nodes for MQTT message subscription contain information such as client ID, host, port, username, etc.

[0048] S104: After performing verification operations and debugging operations on each rule node in the data flow path, obtain an IoT rule chain that passes the test and deploy and release it.

[0049] In step S104, during the process of performing verification operations on each rule node in the data flow path, for non-custom rule nodes, the same set of data verification rules is used for verification.

[0050] Specifically, as long as the data of non-custom rule nodes changes, it will be verified through this shared verification logic, and the verification status of the corresponding rule nodes will be published to a certain topic. Consumers will obtain the verification status of each node, and the verification status of all rule nodes will be packaged, such as Figure 7 shown.

[0051] During the process of performing verification operations on each rule node in the data flow path, the verification statuses of all non-custom rule nodes are uniformly packaged, and when receiving a save command, the non-passing items are displayed in a message pop-up window; the non-passing items record the IDs of the corresponding non-custom rule nodes.

[0052] In this way, when clicking on a non-passing item, the node property panel of the corresponding item will be automatically opened, so that it is possible to quickly locate which rule nodes and which attributes do not pass the verification. After adjusting the non-passing items, you can continue to click save.

[0053] The following takes the Websocket client node as an example to give the process of packaging and processing the corresponding verification status: Define a json_schema structure for rendering the content values of the websocket node and processing verification rules. The requiredFields field is the configuration content for processing verification rules. For example, the url field is required. Add the url field to the requiredFields array, that is, form the code { key: 'url', message: t('property.ws-client-editor.320928-1')}. The supported rules include required, maximum value, minimum value, regular expression, and custom function, and can also be extended according to actual situations in the future.

[0054] When dragging the Websocket client node into the scenario of rule orchestration, an html page is rendered. During page initialization, the configuration information of the Websocket client node is rendered into the page and bound to the components used by the fields. At this time, the page has its own verification logic basis. If the user does not fill in the url field, a required field prompt will be given according to the corresponding rule, without interrupting the user operation process. At the same time, the current rule node and its rule information will also be published to a topic. The save interface will listen to this topic. As long as the current rule node changes, the save interface will listen to the data changes of this rule node in real time and update the data (data) of this page.

[0055] When the user clicks to save, the data (data) will be traversed, and then each item of this node will be verified according to the requiredFields in the json_schema. If the verification passes, no processing will be done. If the verification fails, the rule node that fails the verification, the field information that fails the verification, and the prompt information for the failed item will be organized and assigned to errorFields[] in a preset manner. For example, {nodeId: ‘xx’, field: ‘url’, errorMsg: ‘This item is required’}. After traversing the data, if errorFields is not empty, the submission operation will be interrupted. According to the UI design draft, the code will be organized to display all the failed information in the form of a pop-up window in the lower right corner. The user can find the corresponding node according to the prompt information to adjust the field settings until it meets the preset requirements.

[0056] In order to quickly find the fields in the node that do not conform to the rules, the following operations can be adopted: When clicking to save, all the failed field information will be updated to a shared state errorFields. Each node subscribes to this errorFields state and is bound to the component in real time through a function to change the state of the component, whether it is displayed normally or should be marked red. When the user clicks on a certain node, if there is error information about this node in erroFields, the components of these fields will be marked red, otherwise it will be displayed in the normal state.

[0057] During the process of verifying each rule node in the data flow path, for custom rule nodes, the verification rules are adaptively matched.

[0058] This embodiment sets up an automatic save mechanism. The newly dragged-in nodes will only save their basic information, and will be verified for required fields, etc. when the save button is clicked. In addition, when exiting the rule chain design, if there is information that has not been saved, a pop-up window will prompt that there is unsaved information.

[0059] Debugging is crucial for ensuring the normal operation, running quality, and reliability of the rule chain. Through the console, logical errors, runtime errors, or performance issues can be quickly located, and measures can be taken to solve them, thus ensuring the quality of the rule chain. As Figure 8 shown, the debugging operation process of this embodiment is as follows: Start the debugging mode, select the debugging nodes or all nodes, select the matching option from the debugging types, and start the debugging. If the debugging information content exceeds the preset threshold, the debug information can be cleared by clicking the clear debug button, or the debug button can be locked to lock the debugging information at a certain position and stop the message scrolling, so as to quickly locate the corresponding problem, and then perform relevant debugging operations according to the relevant prompts, and close the debugging to complete the debugging.

[0060] In this embodiment, during the debugging process, each rule node is also monitored. The monitoring function displays the running nodes, running time, running status, running results, CPU (time-consuming), memory usage, etc. in the form of a list, and highlights problems such as incorrect running status and high CPU time consumption for quick location.

[0061] When the rule chain passes the test, the user can deploy it to the production environment and publish the corresponding rule chain through the "Publish" button in the lower part of the page. After successful publication, the rule chain will start listening to and processing the actual data stream, or the actually running rule chain can be stopped by clicking the "Stop" button.

[0062] The visual orchestration rule chain of the present invention is intuitive, concise, highly operable, and has a low learning cost. Especially for non-technical personnel, it can greatly simplify the creation and maintenance process of the rule chain, enabling them to get away from complex code logic and greatly improving the usage experience and work efficiency of non-technical personnel.

[0063] The method for visual orchestration of IoT rule chains of the present invention enables users to intuitively create and modify rule chains through a graphical interface without the need to focus on and write code.

[0064] As Figure 3 shown, the device for visual orchestration of IoT rule chains provided by the embodiment of the present invention can be implemented in software. The device for visual orchestration of IoT rule chains 300 includes the following software modules: an IoT rule project construction module 301, a rule node determination module 302, a data flow path construction module 303, and an IoT rule chain publishing module 304.

[0065] The functions of each software module in the device for visual orchestration of IoT rule chains 300 are introduced below: The IoT rule project construction module 301 is used to receive the business logic, construct a matching IoT rule project, and create a rule chain canvas.

[0066] In the specific implementation process, the business logic can be set according to the actual situation. For example, the status of lighting fixtures in a certain building can be controlled.

[0067] Specifically, the Internet of Things rule project includes the name and coding of the Internet of Things rule chain project. It can be understood here that for some common rule chain technologies, a rule chain template can also be formed based on certain rules. When building an Internet of Things rule project, an existing template can be selected for modification to form the corresponding Internet of Things rule project.

[0068] The rule node determination module 302 is used to parse the business logic, determine the required rule nodes, and judge whether the required rule nodes exist in the preset rule chain node library. If so, the corresponding rule nodes are directly retrieved; otherwise, custom rule nodes are defined. The types of rule nodes stored in the preset rule chain node library include: trigger nodes, logic nodes, output nodes, and storage nodes.

[0069] It should be noted here that the trigger node can be configured as a timed task trigger, exception capture, MQTT message subscription, Websoket client, reading the message bus, HTTP request, and HTTP listening.

[0070] The logic node can be configured as a custom function, routing, delay / flow control, message splitting, and data injection.

[0071] The output node can be configured as message notification, MQTT message push, writing to the message bus, Kafka message push, command issuance, setting device attributes, and HTTP response.

[0072] The storage node can be configured as writing to the database and writing to the object storage.

[0073] In some other alternative embodiments, the trigger node, logic node, output node, and storage node can also be used by those skilled in the art to customize operators to form custom rule nodes.

[0074] For the custom rule node, it obtains data from an external data source in the MQTT message subscription manner, and then customizes and processes the data through a custom function and saves it.

[0075] The data flow path construction module 303 is used to arrange all the required rule nodes in the rule chain canvas according to the business logic, configure the information of each rule node, and retrieve the connection tool to connect the corresponding rule nodes, so that the business logic is transformed into a data flow path. The types of rule nodes stored in the preset rule chain node library include: trigger nodes, logic nodes, output nodes, and storage nodes.

[0076] It should be noted here that the trigger node can be configured as a timed task trigger, exception capture, MQTT message subscription, Websoket client, reading the message bus, HTTP request, and HTTP listening.

[0077] The logic node can be configured as a custom function, routing, delay / flow control, message splitting, and data injection.

[0078] The output node can be configured as message notification, MQTT message push, writing to the message bus, Kafka message push, command issuance, setting device attributes, and HTTP response.

[0079] The storage node can be configured as writing to a database and writing to object storage.

[0080] In some other alternative embodiments, the trigger node, logic node, output node, and storage node can also be customized operators by those skilled in the art to form a custom rule node.

[0081] For the custom rule node, it obtains data from an external data source in the MQTT message subscription manner, and then customizes and processes the data through a custom function and saves it.

[0082] The Internet of Things rule chain publishing module 304 is used to perform a verification operation and a debugging operation on each rule node in the data flow path, and then obtain a tested Internet of Things rule chain and deploy and publish it.

[0083] During the process of performing a verification operation on each rule node in the data flow path, for non-custom rule nodes, the same set of data verification rules is used for verification.

[0084] Specifically, as long as the data of the non-custom rule node changes, it will be verified through this common verification logic, and the verification status of the corresponding rule node will be published to a certain topic. The consumer will obtain the verification status of each node, and the verification status of all rule nodes will be packaged and processed, such as Figure 7 shown.

[0085] During the process of performing a verification operation on each rule node in the data flow path, the verification status of all non-custom rule nodes is uniformly packaged and processed, and when receiving a save command, the non-passed items are displayed in a message pop-up window; the non-passed items record the IDs of the corresponding non-custom rule nodes.

[0086] In this way, when clicking on a non-passed item, the node property panel of the corresponding item will be automatically opened, so that it is possible to quickly locate which rule nodes and which attributes do not pass the verification. After adjusting the non-passed items, you can continue to click save.

[0087] It should be noted here that Figure 3 each module in the Internet of Things rule chain visualization and orchestration device in Figure 1 corresponds one-to-one with each step in the Internet of Things rule chain visualization and orchestration method in , and the specific implementation process is the same, which will not be elaborated here.

[0088] Next, a detailed description will be given of the structure of the electronic device according to the embodiments of the present invention. Figure 4 FIG. is a schematic structural diagram of the composition of the electronic device provided by the embodiment of the present invention. It can be understood that Figure 4 only an exemplary structure of the electronic device is shown, rather than all structures. According to needs, some or all of the structures shown can be implemented.

[0089] The electronic device provided by the embodiment of the present invention includes: at least one processor 401, a memory 402, a user interface 403, and at least one network interface 404. Each component in the Internet of Things rule chain visualization and orchestration device is coupled together through a bus system 405. It can be understood that the bus system 405 is used to realize the connection and communication between these components. In addition to including a data bus, the bus system 405 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 4 all kinds of buses are labeled as the bus system 405.

[0090] Among them, the user interface 403 may include a display, a keyboard, a mouse, a trackball, a click wheel, a button, a button, a touchpad, or a touch screen, etc.

[0091] It can be understood that the memory 402 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The memory 402 in the embodiment of the present invention can store data to support the operation of the terminal. Examples of these data include: any computer program for operating on the terminal, such as an operating system and application programs. Among them, the operating system contains various system programs, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks. The application programs may include various application programs.

[0092] In some embodiments, the Internet of Things (IoT) rule chain visualization and orchestration device 300 provided by the embodiments of the present invention can be implemented in a combination of software and hardware. As an example, the IoT rule chain visualization and orchestration device 300 provided by the embodiments of the present invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the IoT rule chain visualization and orchestration method provided by the embodiments of the present invention. For example, a processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0093] As an example, the processor 401 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0094] As an example of the IoT rule chain visualization and orchestration device 300 provided by the embodiments of the present invention being implemented in hardware, the device provided by the embodiments of the present invention can be directly executed and completed by a processor 401 in the form of a hardware decoding processor. For example, it can be executed by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components to implement the IoT rule chain visualization and orchestration method provided by the embodiments of the present invention.

[0095] The memory 402 in the embodiments of the present invention is used to store various types of data to support the operation of the IoT rule chain visualization and orchestration device 300, or to store for execution Figure 1The program code of the method shown. Examples of such data include: any executable instructions for operating on the IoT rule chain visualization orchestration device, such as executable instructions. The program implementing the IoT rule chain visualization orchestration method of the embodiments of the present invention may be included in the executable instructions.

[0096] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product that includes a computer program carried on a computer-readable medium, and the computer program includes instructions for performing Figure 1 the program code of the method shown. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part, and / or installed from a removable medium. When the computer program is executed by the central processing unit, various functions defined in the device of the present application are performed.

[0097] Wherein, Figure 1 The computer program instructions corresponding to the method shown can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device, and the instruction device implements the functions specified in one process Figure 1 one process or multiple processes and / or boxes Figure 1 one box or multiple boxes.

[0098] The above is only the preferred embodiment of the present invention and is not used to limit the present invention. For those skilled in the art, the present invention can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for visual orchestration of Internet of Things rule chains, characterized in that Including: Receiving the business logic, constructing a matching Internet of Things (IoT) rule project and creating a rule chain canvas; Parsing the business logic to determine the required rule nodes, and judging whether the required rule nodes exist in a preset rule chain node library. If so, directly retrieve the corresponding rule nodes; Otherwise, customize the rule nodes; Arranging all the required rule nodes in the rule chain canvas according to the business logic, configuring the information of each rule node, and retrieving a connection tool to connect the corresponding rule nodes, so that the business logic is transformed into a data flow path; After performing a verification operation and a debugging operation on each rule node in the data flow path, obtaining a tested IoT rule chain and deploying and publishing it.

2. The method for visual orchestration of Internet of Things rule chains according to claim 1, wherein During the process of performing a verification operation on each rule node in the data flow path, for non-customized rule nodes, the same set of data verification rules is used for verification.

3. The method for visual orchestration of Internet of Things rule chains according to claim 1 or 2, characterized in that During the process of performing a verification operation on each rule node in the data flow path, the verification statuses of all non-customized rule nodes are uniformly packaged, and when a save command is received, the non-passed items are displayed in a message pop-up window; the non-passed items record the IDs of the corresponding non-customized rule nodes.

4. The method for visual orchestration of Internet of Things rule chains according to claim 1, wherein During the process of performing a verification operation on each rule node in the data flow path, for customized rule nodes, verification rules are adaptively matched.

5. The method for visual orchestration of the Internet of Things rule chain according to claim 1, wherein The types of rule nodes stored in the preset rule chain node library include: trigger nodes, logic nodes, output nodes, and storage nodes.

6. The visualization and orchestration method of the Internet of Things rule chain according to claim 1, characterized in that For customized rule nodes, they obtain data from an external data source through the MQTT message subscription method, and then perform custom processing on the data through a custom function and save it.

7. An Internet of Things rule chain visualization and orchestration device, characterized in that, Including: An IoT rule project construction module, which is used to receive the business logic, construct a matching IoT rule project and create a rule chain canvas; A rule node determination module, which is used to parse the business logic, determine the required rule nodes, and judge whether the required rule nodes exist in a preset rule chain node library. If so, directly retrieve the corresponding rule nodes; otherwise, customize the rule nodes; A data flow path construction module, which is used to arrange all the required rule nodes in the rule chain canvas according to the business logic, configure the information of each rule node, and retrieve a connection tool to connect the corresponding rule nodes, so that the business logic is transformed into a data flow path; An IoT rule chain publishing module, which is used to perform a verification operation and a debugging operation on each rule node in the data flow path, obtain a tested IoT rule chain and deploy and publish it.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by a processor, it implements the steps in the IoT rule chain visual orchestration method according to any one of claims 1-6.

9. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by a processor, it implements the steps in the IoT rule chain visual orchestration method according to any one of claims 1-6.

10. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the IoT rule chain visual orchestration method according to any one of claims 1-6.

Images