CN116301750A - Rule engine system of Internet of things and execution method - Google Patents

Abstract

The disclosure provides an internet of things rule engine system and an execution method, the system comprises: the rule node assembly module is used for presetting a plurality of rule node assemblies; the rule management module is used for configuring the plurality of rule node assemblies to obtain rule chain execution links; and the rule engine module is used for acquiring the corresponding rule chain execution link according to the message and executing the rule node assembly in the rule chain execution link. According to the rule engine system and the execution method of the Internet of things, different rule nodes are corresponding to the form of a plurality of rule node components, so that the componentization, customization and flow of rule management and execution are realized.

Description

An Internet of Things rule engine system and execution method

technical field

The present disclosure relates to the technical field of the Internet of Things, and in particular to an Internet of Things rule engine system and execution method.

Background technique

With the rapid development of the Internet of Things industry, the Internet of Things technology has also made continuous innovations and breakthroughs. As the core functional system of the Internet of Things platform, the rule engine is the engine for processing various complex business logics, which is equivalent to the brain of the Internet of Things platform. Using the rule engine, the IoT platform can process massive amounts of device data and system internal message data every day, realizing the flexible processing of massive data replication business logic. Although the existing IoT platform rule engine can realize the business logic processing of trillions of massive data, it is not easy to use, and lacks visualization, componentization, customization and easy-to-use rule configuration functions. With the rule chain debugging function, it is difficult to locate and analyze system problems or faults. The function is relatively single, and it is not rich and perfect enough.

Contents of the invention

The present disclosure aims to solve at least one of the technical problems existing in the prior art, and provides an Internet of Things rule engine system and execution method.

An aspect of the present disclosure provides an Internet of Things rule engine system, including:

Rule node component module, used to preset multiple rule node components;

A rule management module, configured to configure the plurality of rule node components to obtain a rule chain execution link;

The rule engine module is configured to obtain the corresponding rule chain execution link according to the message, and execute the rule node component in the rule chain execution link.

Optionally, the rule engine module includes:

A message router, configured to execute a link according to the rule chain to obtain routing information;

A rule chain execution processor, configured to call a corresponding rule node execution processor according to the routing information;

The rule node execution processor is used to respond to the invocation request of the rule chain execution processor to invoke the corresponding rule node logic processor;

The rule node logical processor is used to execute the function of the corresponding rule node component.

Optionally, the message router is further configured to obtain the corresponding root rule chain according to the message, and according to the order configured in the rule chain execution link, the rule node components that need to be executed start from the root rule chain The routing information of is sent to the rule chain execution processor.

Optionally, the rule node component includes post-link configuration information, and the rule node logic processor is further configured to, after executing the last rule node component of the rule chain execution link, according to the last The post-link configuration information in a rule node component obtains the execution link of the next rule chain to be executed and sends it to the message router.

Optionally, the rule management module is also used to generate visualized rule node components and rule node component connection lines, and obtain the rule chain execution according to the selected rule node components and the connection lines between the selected rule node components link, and generate a corresponding visualized rule chain execution link graph.

Optionally, the rule management module is further configured to debug the rule chain execution link according to the selected debugging device and debugging data, and generate a visualized debugging process and debugging results.

Optionally, the rule management module is also used for scene rule management, setting the selected scene as a timed scene or a non-timed scene.

Optionally, the rule management module is further configured to, if the selected scene is set as a timing scene, match the selected scene with a corresponding timing template according to the scenario setting, and generate a timing task according to the timing template, The timing scenario rule chain execution link that is automatically executed according to the configuration of the timing task.

Optionally, the system also includes:

An alarm management module, configured to issue an alarm or eliminate an alarm according to the execution result of the rule node component in the rule node logic processor.

Another aspect of the present disclosure also provides a method for executing an Internet of Things rule engine, including:

Preset multiple rule node components;

Configuring the plurality of rule node components to obtain a rule chain execution link;

Obtain the corresponding rule chain execution link according to the message, and execute the rule node components in the rule chain execution link.

Another aspect of the present disclosure also provides an electronic device, including:

one or more processors;

The storage unit is used to store one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors can realize the Internet of Things rule engine described above Execution method.

Another aspect of the present disclosure further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the method for executing the Internet of Things rule engine described above can be realized.

An Internet of Things rule engine system according to an embodiment of the present disclosure realizes the preset rule node components through the rule node component module, realizes the configuration management of the preset rule node components through the rule management module, and forms different rule chain executions Link, using different rule node components to correspond to rule nodes with different functions, realizes componentized, customized and process-based rule management functions, and realizes simple and flexible configuration of rule chains, so that the Internet of Things can be processed in real time based on message-driven The data reported by the equipment or the internal message processing of the system can be processed through componentization, customization, and process-based processing of various IoT data to realize various intelligent and automated IoT business processing.

Description of drawings

1 is a schematic block diagram of an example electronic device for implementing an Internet of Things rule engine system and execution method according to an embodiment of the present disclosure;

2 is a schematic structural diagram of an Internet of Things rule engine system according to another embodiment of the present disclosure;

FIG. 3 is a schematic structural diagram of a rule engine module according to another embodiment of the present disclosure;

4 is a schematic diagram of a message processing flow of an Internet of Things rule engine system according to another embodiment of the present disclosure;

FIG. 5 is a schematic flowchart of a method for executing an Internet of Things rule engine according to another embodiment of the present disclosure.

Detailed ways

In order to enable those skilled in the art to better understand the technical solution of the present disclosure, the present disclosure will be described in further detail below in conjunction with the accompanying drawings and specific embodiments.

In order to enable those skilled in the art to better understand the technical solution of the present disclosure, the present disclosure will be described in further detail below in conjunction with the accompanying drawings and specific embodiments. Apparently, the described embodiments are some of the embodiments of the present disclosure, not all of them. Based on the described embodiments of the present disclosure, all other embodiments obtained by persons of ordinary skill in the art without creative effort fall within the protection scope of the present disclosure.

Unless otherwise specified, technical terms or scientific terms used in the present disclosure shall have the usual meanings understood by those skilled in the art to which the present disclosure belongs. "Include" or "comprising" used in this disclosure neither limit the mentioned shapes, numbers, steps, actions, operations, components, elements and/or their groups, nor exclude the occurrence or addition of one or more Other different shapes, figures, steps, actions, operations, components, elements and/or groups thereof, or additions to these. In the description of the present disclosure, "plurality" means two or more, unless otherwise specifically defined.

Before discussing in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (steps) as sequential processing, many of the operations may be performed in parallel, concurrently, or simultaneously. In addition, the order of operations can be rearranged. The process may be terminated when operations are complete, but may also have additional steps not included in the figure. The processing may correspond to a method, function, procedure, subroutine, subroutine, or the like.

Firstly, an Internet of Things rule engine system, execution method, and electronic device for implementing an embodiment of the present disclosure are described with reference to FIG. 1 .

As shown in FIG. 1 , an electronic device 300 includes one or more processors 310, one or more storage devices 320, an input device 330, an output device 340, etc., and these components are interconnected through a bus system and/or other forms of connection mechanisms 350. even. It should be noted that the components and structure of the electronic device shown in FIG. 1 are exemplary rather than limiting, and the electronic device may also have other components and structures as required.

The processor 310 may be a central processing unit (CPU) or other forms of processing units with data processing capabilities and/or instruction execution capabilities, and may control other components in the electronic device to perform desired functions.

The storage device 320 may include one or more computer program products, and the computer program products may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and/or cache memory (cache). The non-volatile memory may include, for example, a read-only memory (ROM), a hard disk, a flash memory, and the like. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor may execute the program instructions to realize the client functions (implemented by the processor) in the embodiments of the present disclosure described below and / or other desired functionality. Various application programs and various data, for example, various data used and/or generated by the application programs, may also be stored in the computer-readable storage medium.

The input device 330 may be a device used by a user to input instructions, and may include one or more of a keyboard, a mouse, a microphone, and a touch screen.

The output device 340 may output various information (such as images or sounds) to the outside (such as a user), and may include one or more of a display, a speaker, and the like.

Next, an Internet of Things rule engine system according to another embodiment of the present disclosure will be described with reference to FIG. 2 .

As shown in Figure 2, a rule engine system 100 for the Internet of Things includes a rule node component module 110, a rule management module 120, and a rule engine module 130, specifically:

The rule node component module 110 is configured to preset multiple rule node components.

Exemplarily, in this embodiment, the rule nodes of different functions or services in the Internet of Things that need to be executed are represented by corresponding rule node components, so that the rule nodes in the Internet of Things are componentized.

Specifically, the rule node component module provides rule node component definitions, including configuration parameter definitions and logic processing code definitions. Exemplarily, the rule engine system can only provide basic rule node components, and can also customize and develop rule node components that extend other functions according to actual usage requirements, that is, the rule node component module can only preset basic rule nodes Components can also be preset, custom-developed and extended to rule node components with other functions according to actual usage requirements, which is not specifically limited in this embodiment.

Exemplary, basic rule node components are as follows:

Message type filter node: filter messages according to message type;

Message type routing node: route messages according to message type;

JS script filter node: filter messages according to simple JavaScript script;

JS script routing node: route messages according to simple JavaScript scripts;

JS script conversion node: convert and process messages according to JavaScript scripts;

Product routing node: route the message according to the product number corresponding to the message reported by the device;

Device routing node: route the message according to the device number corresponding to the message reported by the device;

Event routing node: route messages according to the event code corresponding to the event message reported by the device;

Data filtering node: filter and filter messages according to the attribute parameter values in the attribute messages reported by the device, or filter and filter messages according to the event parameter values in the event messages reported by the devices;

Generate alarm node: Automatically trigger and generate alarm information according to configuration rules;

Eliminate the alarm node: automatically trigger the elimination of the alarm message according to the configuration rules;

Message distribution node: Distribute messages according to topics authorized by corresponding device users and configured data permissions, and push messages to topics corresponding to kafka or other message middleware;

RestAPI call node: triggers the call to the third-party RestAPI interface, and can send message data to the third-party interface in the form of parameters;

Send to kafka node: push the message to kafka;

Send to MQTT node: push the message to MQTT;

Time series data storage node: store the attribute data or event data reported by the device to the Elasticsearch library through the data storage module;

Service call node: call device instruction service, you can specify all devices under a certain product or select one or more devices under a certain product to call, or dynamically call the device corresponding to this message, and select according to the corresponding product model Service, setting service input parameters;

Attribute setting node: Call the device attribute setting command, select a device, select one of the attributes that can be set, and input the attribute value to set.

The rule management module 120 is configured to configure the multiple rule node components to obtain a rule chain execution link.

Specifically, the rule management module is responsible for managing the rule chain configuration data, configures the connection relationship between the rule node components through the rule chain configuration data, and obtains the configured rule node components that determine the connection relationship, that is, the rule chain execution link . Exemplarily, in the rule management module, the rule node component can be configured according to specific usage requirements, which is not specifically limited in this embodiment.

Exemplarily, the rule management module can implement functions such as adding a rule chain, modifying a rule chain, setting a rule chain, deleting a rule chain, setting a root rule chain, querying a rule chain, and viewing a rule chain through the above-mentioned method.

The rule engine module 130 is configured to obtain the corresponding rule chain execution link according to the message, and execute the rule node component in the rule chain execution link.

Specifically, the rule engine module is responsible for executing the rule chain processing business in a message-driven manner. The executed rule chain executes the link, and executes the rule node components in the rule chain execution link according to the preset connection relationship. When all the rule node components are executed, the pending business corresponding to the message is executed .

It should be noted that the message includes the message data received by the real-time receiving device through monitoring kafka or other message middleware or the message data pushed by other modules of the Internet of Things platform.

Exemplarily, the message types include: device information, device status information, device reported attribute message, device reported event message, device instruction issued message, alarm message, scene-driven message, rule chain configuration change message. The message data is in json format. The message includes a message header and a message body. The message header mainly includes the message unique identifier, message timestamp, message type, item number, and message metadata.

Exemplarily, the message metadata is in json format, mainly including device number, product number, device name, product name, and extended metadata attribute fields corresponding to different message types. The message body is in json string format, and the content of the message body is determined according to each message type. For example, the message body of the property message reported by the device is the property data reported by the device, and the message body of the event message reported by the device is the device event data.

It should be noted that the above-mentioned message types and message metadata formats are only illustrative, and those skilled in the art can make specific settings according to actual usage conditions.

An Internet of Things rule engine system according to an embodiment of the present disclosure realizes the preset rule node components through the rule node component module, realizes the configuration management of the preset rule node components through the rule management module, and forms different rule chain executions Link, using different rule node components to correspond to rule nodes with different functions, realizes componentized, customized and process-based rule management functions, and realizes simple and flexible configuration of rule chains, so that the Internet of Things can be processed in real time based on message-driven The data reported by the equipment or the internal message processing of the system can be processed through componentization, customization, and process-based processing of various IoT data to realize various intelligent and automated IoT business processing.

Next, an Internet of Things rule engine system according to another embodiment of the present disclosure will be further described with reference to FIG. 2 .

Exemplarily, as shown in FIG. 2 , an IoT rule engine system 100 according to an embodiment of the present disclosure further includes a device access module 140, an alarm management module 150, and a data storage module 160, specifically:

The device access module 140 is configured to receive and send messages with devices.

Exemplarily, the device is various devices used in conjunction with the Internet of Things, such as water pressure equipment, office projectors, mobile phones and other devices, which are not specifically limited in this embodiment.

Exemplarily, the device access module is responsible for docking device data, and pushes the device data to the rule engine module in real time through kafka or other message middleware with real-time messages as the carrier for processing. Exemplarily, the device data includes basic device information, attribute data, event data, and alarm data collected by the device. Exemplarily, the way of interfacing with devices includes directly interfacing with devices through various Internet of Things protocols (such as MQTT, OPC, KNX, etc.), interfacing with device gateways, and interfacing with third-party device management systems. Exemplarily, the device access module is also used to issue device instruction services and device attribute setting instructions to the device. Those skilled in the art can choose different ways to set the interaction mode between the device data and the rule engine module, the information included in the device data, the device connection mode, etc. according to the actual usage, and no specific limitations are set in this embodiment.

Exemplarily, when the rule engine module is connected with the device access module, the service call node and attribute setting node in the basic rule node components described above can be selected to implement the call to the Rest API interface provided by the device access module The ability to send commands to the device.

The alarm management module 150 is configured to issue an alarm or eliminate an alarm according to the execution result of the rule node component.

Exemplarily, the alarm management module is responsible for managing alarm data and providing an alarm management interface. Exemplarily, it includes functions such as querying alarms, viewing alarms, processing alarms, and counting alarms. Exemplarily, it also includes providing new alarms and modifying alarms. The API interface is given to the alarm rule node and the alarm elimination rule node. Exemplarily, processing an alarm mainly includes confirming an alarm or eliminating an alarm, modifying the corresponding alarm state, and inputting relevant remarks at the same time, that is to say, the alarm management module obtains alarm data according to different execution results of different rule node components, and according to different alarm Data selects the alarm-related functions that need to be performed. It should be noted that those skilled in the art may choose different design manners of the alarm function according to actual usage conditions, which are not specifically limited in this embodiment.

The data storage module 160 is used for data storage and management.

Specifically, in the data storage module, the data storage module is responsible for data storage management, including storage management of rule chain configuration data, storage management of device-related configuration data, storage management of device-reported data, wherein configuration-related data is stored in MySQL, etc. Relational database, attribute data, event data and other log data reported by devices are stored in the Elasticsearch library for online search queries or statistical analysis.

Specifically, in the data storage module, the rule node component module can store the definition data of the rule node component in the data storage module, and the rule management module can store the configuration data of the rule node component, that is, the execution link of the rule chain In the data storage module, the rule engine module can call the stored rule node component and the corresponding configuration data from the data storage module according to the received message, that is, call the rule chain execution link to complete the subsequent rule node component execution. In addition, the data storage module can also be used for storage and query of alarm data, as well as storage of data collected and reported by equipment. Exemplarily, the business logic processing unit of the time series data storage rule node defined by the rule node component module is executed in the rule chain Store data while the link is executing.

An Internet of Things rule engine system according to an embodiment of the present disclosure further elaborates a device access module, an alarm management module, and a data storage module, so that the system can further realize the functions of automatically storing or forwarding data, automatically generating alarm messages, and storing and forwarding data.

Next, the rule engine module of another embodiment of the present disclosure will be further described with reference to FIG. 3 .

Exemplarily, the rule engine module 130 includes a message router 131, a rule chain execution processor 132, a rule node execution processor 133, and a rule node logic processor 134, specifically:

The message router 131 is configured to execute a link according to the rule chain to obtain routing information.

Specifically, the message router is responsible for managing the routing information of messages inside the rule engine system. Exemplarily, the message router queries and acquires the routing information corresponding to the rule node component in the rule chain execution link according to the received rule chain execution link, and sends it to the rule chain execution processor. Exemplarily, the rule chain execution processor can call out the rule chain execution link corresponding to the message from the data storage module according to the item number in the message header, and then send the rule chain execution link to the message router, and then the message router can query The corresponding routing information is returned to the rule chain execution processor.

Exemplarily, the rule chain execution processor notifies the message router to perform initialization processing when the system is initialized or receives a rule chain configuration change message, obtains the rule chain configuration data from the rule management module and generates a routing table accordingly, that is, the routing table The table includes the routing information of each rule node component or nested rule chain, and the routing configuration initialization processing of the message router is completed through the above process.

The rule chain execution processor 132 is configured to invoke a corresponding rule node execution processor according to the routing information.

Specifically, the rule chain execution processor acquires the message for processing. Exemplarily, the rule chain execution processor queries the message router to obtain the routing information of the rule chain execution link corresponding to the item number according to the item number in the message header. The message calls the corresponding rule node execution processor, so as to process the corresponding rule node or nested rule chain on the rule chain execution link.

The rule node execution processor 133 is configured to respond to the call request of the rule chain execution processor to call the corresponding rule node logic processor.

Specifically, the rule node execution processor is responsible for receiving the call execution request of the rule chain execution processor, and then calls the corresponding rule node logic processor to process the message.

Exemplarily, the rule node execution processor initializes the rule node component when the system is initialized or receives a rule node component change message.

The rule node logic processor 134 is configured to execute the function of the corresponding rule node component.

Specifically, the rule node logic processor is responsible for receiving the call execution request of the rule node execution processor, and processing the message according to the defined logic processing code, that is, realizing the function of the corresponding rule node component by specifically executing the logic processing code. It should be noted that the logic processing code in the rule node logic processor is defined and managed in the rule node component, and the rule node logic processor is only responsible for executing the logic processing code.

Exemplarily, the rule node logic processor performs initialization processing when the system is initialized or receives a rule node component change message, loads configuration information of the corresponding rule node component from the rule management module, and sets corresponding configuration parameters.

An Internet of Things rule engine system in the embodiment of the present disclosure further elaborates the specific structure of the rule engine module, realizes querying the routing information of the rule chain execution link according to the message, and executes different rule node logic processors according to the routing information The function of different rule node logic processors is used to execute the logic processing code of different rule nodes, and further realize the processing of messages through componentization.

Next, the rule engine module of another embodiment of the present disclosure will be further described.

Exemplarily, the message router 131 is further configured to obtain the corresponding root rule chain according to the message, and according to the order of configuration in the rule chain execution link, the rules that need to be executed starting from the root rule chain The routing information of the node component is sent to the rule chain execution processor.

Exemplarily, when the rule chain execution processor obtains the routing information of the message, the message router first finds the root rule chain corresponding to the item according to the item number in the message header, and executes the rule chain according to the link configured by the rule chain from the root rule chain , that is to say, the message router sends the routing information of the rule node components to be executed from the root rule chain to the rule chain execution processor, and then the rule chain execution processor executes the routing information of the rule node components as needed The information calls the rule node execution processor, and then the rule node execution processor calls the corresponding rule node logic processor, and finally the rule node logic processor specifically executes the corresponding logic processing code, thus completing the processing of the rule node, according to The above method sequentially processes each rule node component in the rule chain execution link starting from the root rule chain, thereby completing the processing of the entire rule chain execution link, and further completing the processing of the message.

It should be noted that each message has one and only one root rule chain, that is, each item number corresponds to only one root rule chain, and the first rule node of the root rule chain is the entry point for the rule engine to execute the rule chain to process messages .

Exemplarily, the rule node component includes post-link configuration information, and the rule node logic processor 134 is further configured to, after executing the last rule node component of the rule chain execution link, according to the The post-link configuration information in the last rule node component obtains the execution link of the next rule chain to be executed and sends it to the message router.

Exemplarily, the rule node logic processor specifies the next rule chain execution link to be executed after processing the message, and then the message router searches for the routing information of the corresponding rule chain execution link and returns it to the rule chain execution processor. The chain execution processor calls the rule node execution processor and the rule node logic processor to process the next rule chain execution link to be executed in the manner described above.

An Internet of Things rule engine system in an embodiment of the present disclosure further elaborates that the router and the rule chain execution processor execute the rule chain execution link from the root rule node, and the rule node logic processor executes the next rule chain to be executed The designation of the link further improves the automation and intelligence of the system in the link processing of the rule chain execution, and improves the automation and intelligence of the Internet of Things message processing.

Next, the rule engine module of another embodiment of the present disclosure will be further described.

Exemplarily, the rule engine module 130 also includes a message receiver 135 and a message buffer 136, specifically:

The message receiver 135 is used to receive the message and send it to the message buffer. Exemplarily, the message receiver receives the message data pushed by the device access module or other modules of the Internet of Things platform in real time by listening to kafka or other message middleware. After the message receiver receives the message, it performs simple conversion and packaging processing on the message, and then sends the message to the message buffer.

The message buffer 136 is used for message buffering, so that the rule chain execution processor can obtain the buffered messages. Exemplarily, the message cache is used to cache the internal messages of the rule engine to kafka or the message queue in the memory of the rule engine server. Exemplarily, if the rule engine module includes a message buffer, the rule chain execution processor acquires messages from the message buffer for processing.

The Internet of Things rule engine system in the embodiment of the present disclosure further elaborates the message receiver and message buffer in the rule engine module, so that the rule engine module has a cache function and improves processing efficiency.

Next, the rule management module of another embodiment of the present disclosure will be further described.

Exemplarily, the rule management module 120 is also configured to provide the user with a rule chain management interface and a scenario rule management interface. Exemplarily, the user includes a project administrator, and the management interface may be a web management interface.

Exemplarily, the rule management module 120 is also configured to set the root rule chain of the message according to the root rule chain setting information, specifically, any rule chain execution link corresponding to the message can be set as the root rule on the rule chain management interface Chain, that is, set any rule chain execution link corresponding to the project number as the root rule chain, and other rule chain execution links can be nested and set in the links of the root rule chain.

Exemplarily, the rule management module 120 is also used to generate visualized rule node components and rule node component connection lines, and obtain the rule chain execution chain according to the selected rule node components and the connection lines between the selected rule node components. path, and generate the corresponding visualized rule chain execution link graph. Specifically, the rule chain setting function of the rule management module is used to dynamically configure the rule chain execution link graph and provide a visual and componentized setting interface. The rule link execution link graph is composed of start nodes, rule nodes, connecting lines, and embedded rule chain nodes. The system provides defined rule node components and rule chain nodes. The project administrator can drag and drop the rule node components that need to be executed to the canvas for configuration, configure the name and parameter information of each node, and then connect the nodes according to the Connect the required logic. Other rule chains can be embedded in the rule chain execution link and displayed in the form of rule chain nodes.

Exemplarily, the rule management module 120 is further configured to debug the execution link of the rule chain according to the selected debugging device and debugging data, and generate a visualized debugging process and debugging results. Specifically, the rule chain debugging function of the rule management module can select debugging equipment, select attribute reporting or event reporting, input attribute reporting or event reporting simulation data, and input each attribute field value or event parameter value in the form of a physical model. You can directly input attribute reporting or event reporting simulation data in json format, click the execute button on the rule chain management interface to generate device attribute reporting messages or event reporting messages in the background, push them to the rule engine for execution, and display the information on the rule chain management interface The rule chain execution link diagram dynamically displays the executed rule node components and connection lines with special effects. After the execution is completed, the interface is lowered to display the execution result information.

Exemplarily, the rule management module 120 is also used for scene rule management, setting the selected scene as a timed scene or a non-timed scene. Specifically, the scene rule management function of the rule management module includes adding scene rules, modifying scene rules, setting scene rules, deleting scene rules, querying scene rules, viewing scene rules, and executing scene rules; , you can set the newly added or modified scene as a timed scene.

Exemplarily, the rule management module 120 is also configured to, if the selected scene is set as a timing scene, match the corresponding timing template for the selected scenario according to the scenario setting, generate a timing task according to the timing template, and generate a timing task according to the timing template. The timing task configures an execution link of a timing scenario rule chain that is automatically executed. Specifically, if the scenario is selected as a timing scenario, you can select a timing template to automatically generate a timing task cron expression based on the timing template, or manually configure a timing task cron expression, and the background will automatically execute the timing scenario rules based on the timing task configuration.

Exemplarily, the execution scenario rule function of the rule management module can be manually triggered by the project administrator user on the interface to execute the scenario rule, and at the same time provide an API interface for third-party system calls to execute.

An Internet of Things rule engine system according to an embodiment of the present disclosure further elaborates the rule management function, debugging function, and timing scene setting function of the rule management module. Send device instructions, and implement rule chain debugging, visually display the execution process and effect of rule chains. Compared with other common rule engine systems or open source rule engines, it has the advantages of ease of use, strong scalability, and richer functions. In addition, Provides timing triggering, manual interface triggering, and third-party interface triggering of scene rule chains, provides visual debugging functions for rule chains, dynamically and visually displays the execution process and logic of rule chains, and has strong scalability.

In the following, the workflow of an Internet of Things rule engine system will be further described with examples.

Exemplarily, as shown in FIG. 4 , an example of the message processing flow of an Internet of Things rule engine system in this embodiment is described. The device access module collects device data and pushes it to Kafka in real time in the form of a message. The rule The message receiver of the engine module receives messages from kafka in real time, performs simple packaging processing, and then pushes the messages to the message buffer of the rule engine, and the rule chain execution processor receives and obtains messages from the message buffer in real time, according to the item number in the message header Get the rule chain from the message router to execute routing, first call the first rule node of the root rule chain to process the message, after processing, judge whether it is the last rule node according to the routing connection, if not, continue to execute the next rule node processing according to the route message, if it is the last rule node, the processing ends.

Exemplarily, if the rule node component selects the message type filter node to process the message reported by the device, then an Internet of Things rule engine system in this embodiment performs message processing according to the following process: the device access module receives the message data reported by the device, And send it to the rule engine module, trigger the rule engine module to obtain and execute the rule chain execution link corresponding to the message, that is, to execute the message type filter node, first filter the message through the message type filter node, if the message is an attribute message reported by the device, Then execute the timing data storage rule node, and send the attribute data reported by the device to the data storage module through the interface and store it in the Elasticsearch library. If the message is not the attribute message reported by the device, the processing will end directly.

Exemplarily, if the rule node component selects the message type filter node, product rule node, data filter node, and alarm generation rule node to process the water pressure product alarm, then a rule engine system of the Internet of Things in this embodiment is as follows Process for message processing: the device access module receives the message data reported by the device and sends it to the rule engine module, which triggers the rule engine module to obtain the rule chain execution link corresponding to the message and execute it, that is, execute the message type filter node, first pass The message type filtering node filters messages. If the message is an attribute message reported by the device, execute the product rule node to filter the message by product. If it is a water pressure product, execute the data filtering node to filter out the message data whose water pressure value is less than 0.1MPa, and then Execute the generating alarm rule node, automatically generate alarm message data according to the configuration of the generating alarm rule node, and send it to the alarm management module through the interface for storage. If the attribute message is not reported by the device, or the message is not reported by the device corresponding to the water pressure product, or the water pressure value in the attribute message reported by the device is not less than 0.1MPa, then the processing is directly ended.

Exemplarily, if the rule node component selects the message type filter node, product rule node, event rule node, and service call rule node to perform conference room device control processing, then a rule engine system of the Internet of Things in this embodiment is as follows Process for message processing: the device access module receives the message data reported by the device and sends it to the rule engine module, which triggers the rule engine module to obtain the rule chain execution link corresponding to the message and execute it, that is, execute the message type filter node, first pass The message type filtering node filters messages. If the event message is reported by the device, execute the product rule node to filter the message by product. If it is a conference room pad product, execute the event rule node to filter the message by event. If it is a conference room door opening log event, Then execute the service call rule node to call the curtain device service corresponding to the conference room to open the curtains, and then execute the service call rule node to call the air conditioner corresponding to the conference room to turn on the air conditioner. If the attribute message is not reported by the device, or the message is not reported by the device corresponding to the conference room pad product, or the event message reported by the device is not the conference room door opening log event, the processing is directly ended.

Exemplarily, the scene controlled by the conference room equipment can also be set as a timing scene. For example, the project administrator adds a scene rule "office scene in the office lobby" on the scene rule management interface through the rule management module, sets it as a timing scene, and configures the timing The task executes the Cron expression, for example, it is executed at 18:00 every day, and the scene rule chain execution link is set, for example, the property setting rule node is used to turn off all lights in the office lobby, and the attribute setting rule node is used to close the office Hall air conditioner, set service call rule node for automatic disinfection of robots. After the new scene rule is submitted, the background automatically creates a scheduled task for the scene rule, which is triggered to execute at 18:00 every day. When executing, first add a scene driving message, push the driving message to the rule engine module for processing, and the rule engine module executes the setting of the scene rule Rule chains execute chains for processing.

Exemplarily, the scenarios controlled by the above-mentioned meeting room devices support manual triggering of immediate execution of scenario rules or a third-party system calls the API interface provided by the system to trigger the execution of scenario rules. The scenario rules can be scheduled task scenarios or non-scheduled task scenarios. It is also the first to add a scene-driven message, push the drive message to the rule engine module for processing, and the rule engine module executes the rule link set by the scene rule for processing.

Exemplarily, when the rule management module executes the debugging function, the project administrator selects a configured rule chain execution link on the rule management interface, clicks the "debug rule chain" button to enter the debugging interface, selects a debugging device, and selects the attribute report Or event reporting, input the attribute value or event parameter value, click the "Submit" button to submit the debugging request, the background will automatically generate the device reporting message according to the submitted data, and push the message to the rule engine module for execution, and the rule engine module will record the rule chain debugging information and push it For the rule management module, it mainly records the current execution rule node and the previous execution rule node. The rule management module returns the debugging message to the interface in real time through WebSocket. The interface dynamically displays the effect of the rule chain execution process in real time. If the rule chain debugging is completed, the interface will display Debugging result information, otherwise wait to continue execution.

Next, a method for executing an Internet of Things rule engine according to another embodiment of the present disclosure is described in conjunction with FIG. 5 , including:

S100: Presetting multiple rule node components.

S200: Configure the multiple rule node components to obtain a rule chain execution link.

S300: Obtain the corresponding rule chain execution link according to the message, and execute the rule node component in the rule chain execution link.

An Internet of Things rule engine execution method according to an embodiment of the present disclosure, preset rule node components, configure and manage preset rule node components, form different rule chain execution links, and use different rule node components to correspond to different The functional rule node realizes componentized, customized and process-based rule management functions, and realizes simple and flexible configuration of rule chains, so that real-time processing of data reported by IoT devices or internal message processing of the system can be processed based on message-driven, through components Customized, customized, and process-based processing of various IoT data to realize various intelligent and automated IoT business processing.

Further, this embodiment also discloses an electronic device, including:

one or more processors;

The storage unit is used to store one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors can realize the aforementioned Internet of Things Rule engine execution method.

Further, this embodiment also discloses a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it can implement the aforementioned method for executing an Internet of Things rule engine.

Wherein, the computer-readable medium may be included in the apparatus, device, or system of the present disclosure, or may exist independently.

Among them, the computer-readable storage medium can be any tangible medium containing or storing programs, which can be electrical, magnetic, optical, electromagnetic, infrared, semiconductor systems, devices, and equipment. More specific examples include but are not limited to: having one or Electrical connection of multiple wires, portable computer disks, hard disks, optical fibers, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), portable compact disk read only memory ( CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

Wherein, the computer-readable storage medium may also include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program codes therein. Specific examples thereof include but are not limited to electromagnetic signals, optical signals, or any suitable The combination.

In the description of this specification, descriptions referring to the terms "one embodiment", "some embodiments", "example", "specific examples", or "some examples" mean that specific features described in connection with the embodiment or example , structure, material or characteristic is included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the described specific features, structures, materials or characteristics may be combined in any suitable manner in any one or more embodiments or examples. In addition, those skilled in the art can combine and combine different embodiments or examples and features of different embodiments or examples described in this specification without conflicting with each other.

It can be understood that, the above implementations are only exemplary implementations adopted to illustrate the principle of the present disclosure, but the present disclosure is not limited thereto. For those skilled in the art, without departing from the spirit and essence of the present disclosure, various modifications and improvements can be made, and these modifications and improvements are also regarded as the protection scope of the present disclosure.

Claims (10)

1. A rule engine system for the Internet of Things, characterized in that, comprising: Rule node component module, used to preset multiple rule node components; A rule management module, configured to configure the plurality of rule node components to obtain a rule chain execution link; The rule engine module is configured to obtain the corresponding rule chain execution link according to the message, and execute the rule node component in the rule chain execution link. 2. A kind of Internet of things rule engine system according to claim 1, is characterized in that, described rule engine module comprises: A message router, configured to execute a link according to the rule chain to obtain routing information; A rule chain execution processor, configured to call a corresponding rule node execution processor according to the routing information; The rule node execution processor is used to respond to the invocation request of the rule chain execution processor to invoke the corresponding rule node logic processor; The rule node logical processor is used to execute the function of the corresponding rule node component. 3. A rule engine system for the Internet of Things according to claim 2, wherein the message router is also used to obtain the corresponding root rule chain according to the message, and execute the configuration in the link according to the rule chain In order, the routing information of the rule node components to be executed is sent to the rule chain execution processor from the root rule chain. 4. A kind of Internet of things rule engine system according to claim 3, it is characterized in that, described rule node assembly comprises rear link configuration information, and described rule node logical processor is also used for, when executing described After the last rule node component of the rule chain execution link, the next rule chain execution link to be executed is obtained according to the post link configuration information in the last rule node component and sent to the message router. 5. A kind of Internet of Things rule engine system according to any one of claims 1 to 4, wherein the rule management module is also used to generate visualized rule node components and rule node component connecting lines, and according to The selected rule node components and the connecting lines between the selected rule node components obtain the rule chain execution link, and generate a corresponding visualized rule chain execution link diagram. 6. A rule engine system for the Internet of Things according to any one of claims 1 to 4, wherein the rule management module is also used to debug the execution of the rule chain according to the selected debugging device and debugging data link, and generate a visualized debugging process and debugging results. 7. A rule engine system for the Internet of Things according to any one of claims 1 to 4, wherein the rule management module is also used for scenario rule management, and the selected scenario is set as a timing scenario or a non-timing scenario Scenes. 8. A kind of Internet of Things rule engine system according to claim 7, is characterized in that, described rule management module is also used for, if described selected scene is set as timing scene, then according to scene setting as described selected The scenario matches the corresponding timing template, a timing task is generated according to the timing template, and a timing scenario rule chain execution link that is automatically executed is configured according to the timing task. 9. A kind of Internet of things rules engine system according to any one of claims 1 to 4, characterized in that said system also includes: An alarm management module, configured to issue an alarm or eliminate an alarm according to the execution result of the rule node component. 10. An Internet of Things rule engine execution method is characterized in that, comprising: Preset multiple rule node components; Configuring the plurality of rule node components to obtain a rule chain execution link; Obtain the corresponding rule chain execution link according to the message, and execute the rule node components in the rule chain execution link.

Images