CN109683494B - Internet of things equipment linkage control system - Google Patents

Abstract

The invention provides a linkage control system of Internet of things equipment, which comprises: a WEB configuration module and a linkage service module; and the linkage service module utilizes the data stored in the database by the WEB configuration module to carry out rule screening, and completes the action of the equipment needing to be operated. The invention can link various Internet of things devices, including but not limited to a single lamp, a charging pile, wifi, a camera, emergency help, well lid monitoring, broadcasting, parking space monitoring and an LED large screen. Wherein, the single lamp, fill electric pile, wifi, promptly seek help, parking stall control, well lid control can be as trigger condition, and single lamp, camera, broadcast and large-size screen can be triggered and carry out the operation. The invention realizes complete user personalized configuration, all trigger conditions and trigger actions are configuration items, and the Internet of things equipment in the smart city is organically combined.

Description

IoT device linkage control system

technical field

The invention relates to the field of smart cities and the Internet of Things, and in particular, to a linkage control system for Internet of Things equipment.

Background technique

The prior art document "Water-Saving Irrigation Linkage Control System" was published in "Chinese Journal of Agricultural Engineering", No. 8, 2011. In order to save farmland irrigation water, improve water resources utilization efficiency, and realize automatic irrigation control, this paper adopts self-designed irrigation system. Control equipment and moisture monitoring equipment transmit data through GSM network, and design a set of water-saving irrigation linkage control system integrating moisture monitoring, irrigation control and expert decision support. The system consists of three parts: local control cabinet, data acquisition system and automatic control software. It realizes the functions of real-time monitoring of soil moisture, expert knowledge management, and automatic irrigation control according to different crops and water demand parameters in different growth periods. The application in the demonstration area proves that the system is stable and reliable, easy to operate, and can be widely used in large-scale planting, greenhouses, precision agriculture and other fields, and has important practical significance for the implementation of water-saving agriculture. But the irrigation system is just a linkage between soil monitoring and irrigation equipment.

The prior art document "On Lighting Control and Intelligent Lighting Control System" is published in "Low Voltage Electrical Appliances", Issue 6, 2008, which briefly introduces the basic principles of lighting control, the main implementation methods, and the basic requirements for lighting control in different occasions . The main functions realized by the intelligent lighting control system are expounded, and the application cases of the intelligent lighting control system are given. The advantages of DALI intelligent lighting control system are introduced from the aspects of design, installation and use. However, this document only controls the lighting through a fixed DALI system to realize the linkage between the illuminance sensor and the lamps. However, the urban resource such as light poles should become part of the smart city, not as simple as lighting, so it cannot be applied to In particular, the linkage between various devices such as illuminance can be used for intelligent control of switching lights and brightness adjustment.

SUMMARY OF THE INVENTION

Aiming at the defects in the prior art, the purpose of the present invention is to provide a linkage control system for IoT devices.

A linkage control system for IoT devices provided according to the present invention includes: a WEB configuration module and a linkage service module;

The linkage service module uses the data stored in the database by the WEB configuration module to filter the rules and complete the actions that the device needs to operate.

Preferably, the WEB configuration module includes a Web module;

New Condition Module: Configure trigger conditions,

New operation module: configure trigger operation;

Rule generation module: according to the trigger condition and trigger operation, generate a rule, wherein the rule includes a priority, an operation performed after being triggered, and the time of performing an operation after being triggered;

Wherein, the trigger condition includes the following information:

The operation performed after being triggered includes the following information:

Preferably, the trigger configuration of the component type is:

Preferably, the linkage service module includes the following modules:

Data receiving module: For the message sent by the hardware device, it is processed through RocketMQ. After receiving the message from RocketMQ, it parses the data in Json format, and transmits the parsed data to the conditional filtering module for logical processing;

Condition screening module: perform different logic processing according to different types of equipment to obtain rule IDs. The types of equipment include single lamp, charging pile, AP, emergency assistance, parking space monitoring, manhole cover monitoring, and LED advertising screen;

Action screening module: According to the rule ID, the priority of the actions in the rules is judged, and the actions that need to be operated are obtained;

Execution action module: package the action that needs to be operated into the corresponding data format, send it to RocketMQ, and send it to each device through RocketMQ through the gateway to perform the corresponding action;

Wherein, the logic processing flow is as follows:

Step 1: According to the data sent by the data receiving module, determine which device is sending the data, and then find the corresponding logic for processing;

Step 2: Go to the Redis database db to determine whether the code of this device is used as a list of condition keys. If it exists, go to the third step. If it does not exist, end the logic processing flow;

The third step: According to the list found in the second step, find all the condition keys under the device, find the specific values of the conditions according to the condition keys, and judge these conditions in a loop. For the values that meet the conditions, record the rules corresponding to the values. ID, for the value that does not meet the conditions, the rule ID corresponding to the value is not recorded;

Step 4: Obtain a list of rule IDs from the third step, find all the conditions under the rule in Redis according to the rule ID, and judge whether these conditions are satisfied. If all are satisfied, record the rule ID;

Step 5: Obtain a list of rule IDs that finally meet the conditions according to Step 4, and pass it to the action screening module for logical processing.

Step 6: After the conditional screening, pass the rule IDs that meet the conditions to the action screening module for processing.

Preferably, the adopted Redis storage structure is:

The specific value of each condition is stored in db0 of Redis. The data structure used is hash. The child key and value of the hash correspond to the fields and corresponding values of the condition table in the mysql database. The parent key is CondigCondition plus this condition. A string composed of IDs in the condition table, if the ID is 1, the parent key is CondigCondition1;

What is stored in db1 of Redis is which conditions are included under each rule, and the data structure used is List; the key of the conditions under the rule is ConfigRule plus the ID of the rule in the mysql rule table, and the value of the key of List is the following rule key for all conditions;

All condition keys are stored in db3 of Redis, which is used for traversal. The data structure used by condition keys is List; there is only one key in Db3, which is ConfigCoditionList, and the value of ConfigCoditionList is all the condition keys that appear in db0;

Redis's db4 stores the codes of all devices with conditions, which are used for traversal. The storage structure used here is also List; there is only one key in the Code of devices with conditions, which is EquipmentCodeList;

Redis db5 stores the conditions owned by each device, and the data structure used is List; the key of the conditions owned by the device is the 14-bit code of the device, and the value of this key is the condition key owned by the device;

Redis stores the mapping between keys and different types of values, persists the key-value pair data stored in memory to the hard disk, and uses the replication feature to expand the read performance; where: O(1) commands are safe, When the O(N) command is used, if the magnitude of N is unpredictable, avoid using it; set the fsync function and execute the fsync function once per second; check the inherent delay and deploy Redis directly on the physical machine.

Preferably, among the WEB configuration module and the linkage service module, an abnormal state of one will not affect the operation of the other;

The WEB configuration module is used to store trigger conditions, trigger operations, generate trigger rules, and manage trigger rules; the WEB configuration module is mainly divided into presentation layer, business logic layer, data access layer, and database layer. MySQL for data persistence;

The linkage service module is mainly divided into a logic processing layer and a data persistence layer; in the logic processing layer, there are a data receiving module, a condition screening module, an action screening module, and an execution action module;

For the data persistence layer, the linkage service module adopts the implementation method of Redis database and Mysql.

Compared with the prior art, the present invention has the following beneficial effects:

1. Developed for multi-device, multi-response linkage control. Filter information reported by a large number of devices in real time, filter and trigger corresponding actions.

2. The various IoT devices in the smart city are organically linked, which is not limited to the equipment of agriculture or fire protection system, and realizes complete user-specific configuration, with high scalability.

3. Perform linkage control on the cameras, broadcasts, one-key alarms, manhole covers and other equipment on the smart light pole. After setting the rules, when a device answers a condition, it can trigger the action of another device. It can be connected to a variety of devices and has high expansibility.

4. Show the "wisdom" in the smart light poles. Each light pole is bound with a camera. When an alarm is triggered, the camera will automatically turn to the response position. It is also possible that the radio will automatically play a warning voice when the crowd is too dense. Really serve the smart light pole to the city.

5. A variety of IoT devices will be linked, including but not limited to single lights, charging piles, wifi, cameras, emergency help, manhole cover monitoring, broadcasting, parking space monitoring and large LED screens. Among them, single light, charging pile, wifi, emergency help, parking space monitoring, manhole cover monitoring can be used as trigger conditions, and single light, camera, broadcast and large screen can be triggered to perform operations. The invention realizes complete user personalized configuration, all trigger conditions and trigger actions are configuration items, and the Internet of Things devices in the smart city are organically combined.

Description of drawings

Other features, objects and advantages of the present invention will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:

Figure 1 is a system architecture diagram.

Figure 2 is a system function diagram.

Figure 3 is a network topology diagram.

Figure 4 is the database ER diagram.

Figure 5 is a screenshot of the new condition page interface.

Figure 6 is a screenshot of the new operation page interface.

Figure 7 is a screenshot of the rule management page interface.

Detailed ways

The present invention will be described in detail below with reference to specific embodiments. The following examples will help those skilled in the art to further understand the present invention, but do not limit the present invention in any form. It should be noted that, for those skilled in the art, several changes and improvements can be made without departing from the inventive concept. These all belong to the protection scope of the present invention.

According to an IoT device linkage control system provided by the present invention, the related tables are as follows:

Table 1 Trigger function analysis table

Table 2 Analysis of available conditions when triggered

Table 3 Analysis of available conditions when triggered

A linkage control system for IoT devices provided according to the present invention includes: a WEB configuration module and a linkage service module;

In both the WEB configuration module and the linkage service module, the abnormal state of one will not affect the operation of the other; the linkage service module uses the data stored in the database by the WEB configuration module to filter the rules and complete the actions that the device needs to operate.

WEB configuration module: store trigger conditions, trigger operations, generate trigger rules, and manage trigger rules; the WEB configuration module is mainly divided into presentation layer, business logic layer, data access layer, and database layer, which is developed using SSM framework and MySQL Data persistence.

The linkage service module is mainly divided into a logic processing layer and a data persistence layer; in the logic processing layer, there are a data receiving module, a condition screening module, an action screening module, and an execution action module. Since the data persistence layer needs to be queried quickly, the linkage service module uses the combination of Redis database and Mysql.

The system architecture diagram of the present invention is shown in FIG. 1 , and the system function diagram is shown in FIG. 2 . As shown in Figure 3, in the system provided by the present invention, when the system obtains a message from the MQ message queue, the first step will be to parse it, and after obtaining useful information, it will undergo two logical processing of condition screening and action screening. , use the information that the WEB configuration module has stored in the Redis and Mysql databases to filter out the last action to be done; finally, the action is encapsulated and sent to MQ, and finally the corresponding hardware is used to execute the action through the gateway. The program part in the present invention can be deployed on the windows system or the linux system.

The Web module mainly includes functions such as creating conditions, creating operations, generating rules and managing and managing logs. Among them, New Condition→Operation→Rule is a process, you can go to the previous step, the next step, and delete or add the selected conditions and operations.

Create a new condition, select the pole device or non-light pole device through the upper selection box, and then select the device, component, function, etc. to generate a trigger condition. After selecting a light pole device, click OK, and a modal box for light pole selection will pop up. Select a non-light pole device to refresh directly in the device bar. After selecting a device, click the question mark icon on the left, and a modal box will pop up to display which rules the current device has been occupied and the priority of each rule. As shown in Figure 5.

To create a new operation, select a light pole device or a non-light pole device through the upper selection box, and then select a device, component, function, etc. to generate a trigger operation. After selecting a light pole device, click OK, and a modal box for light pole selection will pop up. Select a non-light pole device to refresh directly in the device bar. As shown in Figure 6.

Finally, generate rules. After adding conditions and operations, enter the generation rules interface, fill in the priority and the time to execute the operation after triggering, and click Finish. As shown in Figure 7.

In the service logic of the linkage service module, the whole can be divided into four parts, namely data reception, condition screening, action screening and execution action.

(1) Data reception

Messages sent by hardware devices, such as alarm messages and notification messages, are processed by the system through RocketMQ. After our server receives the message from RocketMQ, it will parse the data in Json format, and transmit the parsed data to the system. Process the processing logic of the conditional filtering module.

(2) In the condition screening module, different logic processing is performed according to different equipment, including single lamp, charging pile, AP, emergency assistance, parking space monitoring, manhole cover monitoring, LED advertising screen, etc. The logical processing flow is as follows:

1) According to the data sent by the data receiving module, determine which device is sending the data, and then find the corresponding logic for processing.

2) The second step is to go to a db in Redis (db5 in this system, which can be selected by yourself, but cannot be changed after selection. The sub-library can avoid the duplication of keys to a certain extent, and can also make the logic more clear. Same as) to judge whether there is the code of this device as the key list, if it exists, go to the third step, if it does not exist, skip the logical judgment and do not proceed further.

3) According to the list found in the second step, find all the condition keys under the device, find the specific values of the conditions according to the condition keys, and judge these conditions in a loop. If a condition is met, record its rule ID, if not, then Skip the judgment logic directly and no longer execute it.

4) A list of rule IDs is obtained from the third step. According to the rule ID, all the conditions under the rule are found in Redis, and it is judged whether these conditions are satisfied. If all are satisfied, the rule ID is recorded.

5) Obtain a list of rule IDs that finally meet the conditions according to the fourth step, and pass it to the action screening module for logical processing.

6) After the conditional screening, pass the rule IDs that meet the conditions to the action screening module for processing. This part is mainly to judge the priority of the actions in the rules.

7) After the action screening, package the action to be done in the corresponding data format, send it to RocketMQ, and send it to each device through RocketMQ through the gateway to perform the corresponding action.

The following describes the design of the Redis storage structure.

Redis is a high-performance key-value in-memory database of nosql, which supports network and can also be persisted locally. Clustering is already supported in version 3.0.0Beta. To use Redis well, it is necessary to design the storage structure of Redis according to the actual business scenario, and the construction rules of keys are also very important. In this system, db0 to db5 of Redis are used, and each part has its own storage structure.

The specific value in each condition is stored in db0. The data structure used here is hash. Its child key and value correspond to the fields and corresponding values of the condition table in the mysql database. The parent key is "CondigCondition" plus This condition is a string composed of IDs in the condition table. If the ID is 1, the parent key is CondigCondition1.

What is stored in db1 is which conditions are included under each rule, and the data structure used is List. Its key is "ConfigRule" plus the ID of the rule in the mysql rule table, and its value is the key of all conditions under this rule. If the rule ID is 1, and the ID of the condition it contains is 1, then in db1 The performance is that the key is ConfigRule1 and the value is a List of CondigCondition1.

db2 is not used at this stage and is reserved for future supplementation.

All condition keys are stored in db3, which is used for traversal, and the data structure it uses is List. There is only one key in Db3, which is ConfigCoditionList, and its value is all the condition keys that appear in db0.

The code of all devices with conditions is stored in db4, which is used for traversal. The storage structure used here is also List. It also has only one key in it, which is EquipmentCodeList.

What is stored in db5 is the conditions owned by each device, and the data structure used is List. Its key is the 14-bit code of the device, and the value of this key is the condition key owned by the device. For example, if the AP numbered 01070000000001 has the condition key CondigCondition2, there will be a List in the db with the key 01070000000001 and the value CondigCondition2.

The key technologies and solutions are described below.

Redis is a very fast non-relational database that can store mappings between keys and 5 different types of values, and can persist the key-value pair data stored in memory to hard disk , you can use the replication feature to expand read performance. Although Redis is a very fast in-memory data storage medium, it does not mean that Redis will not cause performance problems. So pay attention to some issues when using it to ensure the performance of Redis.

Long time-consuming commands should be avoided. The time complexity of most Redis read and write commands is between O(1) and O(N). The time complexity of each command is described in the text and official documents. Generally speaking, O(1) commands are safe, O(N) commands need to be used with care and should be avoided if the magnitude of N is unpredictable. For example, executing HGETALL/HKEYS/HVALS commands on a Hash data with an unknown number of fields. Generally speaking, these commands are executed quickly, but if the number of fields in the Hash is extremely large, the time-consuming will increase exponentially. Redis provides the Slow Log function, which can automatically record commands that take a long time. We can find out which commands are taking too long and optimize accordingly.

Latency caused by data persistence. The data persistence work of Redis itself will bring delay, and a reasonable persistence strategy needs to be formulated according to the security level and performance requirements of the data. This system adopts the AOF persistence strategy, setting fsync every second and fsyncing once per second, which not only maintains the correctness of persistence to a large extent, but also takes into account the impact on performance.

Latency caused by the virtual machine. Now that the linkage configuration subsystem is deployed on the virtual machine, and Redis is also deployed in the same place, there may be inherent delays caused by the virtual machine environment. Intrinsic latency can be viewed with the ./redis-cli --intrinsic-latency 100 command. At the same time, if there are high requirements for the performance of Redis, you should deploy Redis directly on the physical machine as much as possible.

Those skilled in the art know that, in addition to implementing the system, device and each module provided by the present invention in the form of pure computer readable program code, the system, device and each module provided by the present invention can be completely implemented by logically programming the method steps. The same program is implemented in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded microcontrollers, among others. Therefore, the system, device and each module provided by the present invention can be regarded as a kind of hardware component, and the modules used for realizing various programs included in it can also be regarded as the structure in the hardware component; A module for realizing various functions can be regarded as either a software program for realizing a method or a structure within a hardware component.

Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the above-mentioned specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essential content of the present invention. The embodiments of the present application and features in the embodiments may be combined with each other arbitrarily, provided that there is no conflict.

Claims (3)

1. The utility model provides a thing networking device coordinated control system which characterized in that includes: a WEB configuration module and a linkage service module;

the linkage service module utilizes the data stored in the database by the WEB configuration module to carry out rule screening to complete the action of the equipment needing to be operated;

the WEB configuration module comprises a Web module;

newly building a condition module: the trigger condition is configured to be set up,

newly building an operation module: configuring a trigger operation;

a rule generation module: generating a rule according to the trigger condition and the trigger operation, wherein the rule comprises a priority, an operation executed after being triggered and an operation execution time after being triggered;

wherein the trigger condition includes the following information:

wherein, the execution operation after being triggered comprises the following information:

the triggering of the component type is configured as:

the linkage service module comprises the following modules:

a data receiving module: processing the message sent by the hardware equipment through a RocketMQ, after receiving the message of the RocketMQ, analyzing the data in the Json format, and transmitting the analyzed data to a condition screening module for logic processing;

a condition screening module: performing different logic processing according to different types of equipment to obtain a rule ID, wherein the types of the equipment comprise a single lamp, a charging pile, an AP, emergency help, parking space monitoring, well lid monitoring and an LED advertising screen;

an action screening module: judging the priority of the actions in the rule according to the rule ID to obtain the actions needing to be operated;

an execution action module: packaging the action to be operated into a corresponding data format, sending the data format to a RocketMQ, and sending the data format to each device through a gateway through the RocketMQ to perform corresponding action;

wherein the logic processing flow is as follows:

the first step is as follows: judging which kind of equipment transmitted data according to the data transmitted by the data receiving module, and then finding corresponding logic for processing;

the second step is that: judging whether the code of the equipment is used as a list of condition keys or not in a database db without Redis, if so, performing the third step, and if not, ending the logic processing flow;

the third step: finding all condition keys below the equipment according to the list found in the second step, finding specific values of the conditions according to the condition keys, circularly judging the conditions, recording rule IDs corresponding to the values if the conditions are in accordance, and not recording the rule IDs corresponding to the values if the conditions are not in accordance;

the fourth step: obtaining a List List of rule IDs from the third step, finding all conditions under the rule in Redis according to the rule IDs, judging whether the conditions are met, and recording the rule ID if the conditions are met;

the fifth step: according to the fourth step, a List of the rule IDs which finally meet the conditions is obtained and is transmitted to an action screening module for logic processing;

and a sixth step: after condition screening, the rule ID meeting the conditions is transmitted to an action screening module for processing.

2. The internet of things device linkage control system according to claim 1, wherein the adopted Redis storage structure is as follows:

specific values of each condition are stored in db0 of Redis, the used data structure is hash, child keys and values of the hash correspond to fields and corresponding values of a condition table in a mysql database, a parent key is a character string formed by CondigCondition and an ID of the condition in the condition table, and if the ID is 1, the parent key is CondigCondigCondition 1;

stored in db1 of Redis is which conditions are contained under each rule, and the data structure used is a List; the key of the condition under the rule is Configresults plus the ID of the rule in the mysql rule table, and the value of the key of the List is the key of all the conditions under the rule;

all condition keys are stored in db3 of Redis and used as traversal uses, and the data structure used by the condition keys is List; only one key in Db3 is the ConfigCoditionList, whose value is all conditional keys present in Db 0;

stored in db4 of Redis are codes of all devices having a condition, used for traversal, and the storage structure used here is also a List; there is also only one key inside the Code of the device with the condition, which is equal to EquipmentCodeList;

stored in db5 of Redis are the conditions owned by each device, using a List data structure; the key of the condition owned by the equipment is the 14-bit code of the equipment, and the value of the key is the key of the condition owned by the equipment;

mapping between the Redis storage key and different types of value values, persisting key value pair data stored in a memory to a hard disk, and expanding the reading performance by using a copying characteristic; wherein: the command of O (1) is safe, and the command of O (N) is used if the order of N is unpredictable, so that the command is avoided; setting a fsync function, and executing the fsync function once every second; looking at the inherent delays, Redis is deployed directly on the physical machine.

3. The Internet of things equipment linkage control system according to claim 1, wherein one of the WEB configuration module and the linkage service module is in an abnormal state, so that the operation of the other one cannot be influenced;

the WEB configuration module is used for storing the trigger conditions, triggering operation, generating trigger rules and managing the trigger rules; the WEB configuration module is divided into a presentation layer, a business logic layer, a data access layer and a database layer, an SSM framework is adopted for development, and MySQL is used for data persistence;

the linkage service module is divided into a logic processing layer and a data persistence layer; the logic processing layer is provided with a data receiving module, a condition screening module, an action screening module and an action executing module;

and a data persistence layer and a linkage service module adopt an implementation mode that a Redis database and Mysql are matched for use.

Images