System and method for efficiently storing Internet of Things data into time sequence database
By designing a system for efficient timing database for IoT data storage, the problems of high resource occupation and low intake efficiency when massive IoT devices are directly connected to timing databases in low bandwidth and high latency network environments are solved, and efficient data storage and resource utilization are achieved.
Patent Information
- Application Number
- CN202411451174.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-17
- Publication Date
- 2025-03-21
AI Technical Summary
When a large number of IoT devices are directly connected to the timing database, they occupy high system resources and low data entry efficiency, especially in low bandwidth and high latency network environments.
A system for efficient database storage of IoT data is designed, including a message receiving module, a message filtering module and a message writing module. The message receiving module establishes a connection with the Internet of Things devices through the TCP/IP protocol. The message filtering module uses the rule engine to filter and convert data. The message writing module writes the filtered data to the timing database in a data integration manner.
Through lightweight features, low bandwidth consumption and efficient resource utilization, the system meets the needs of massive IoT devices access and data entry, reduces resource consumption at the database side and improves data entry efficiency.
Smart Images
Figure CN119669319A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of distributed databases, and in particular to a system and method for efficiently storing Internet of Things data into a time series database. Background Art
[0002] With the rapid development of Internet of Things (IoT) technology, the demand for communication between devices is increasing. The access and management of massive IoT devices pose great challenges to network bandwidth, communication protocols, and platform service architecture. Some IoT devices have limited resources, low bandwidth, high latency, or unstable network environments, which also adds an additional challenge. If massive IoT devices are directly connected to the time series database, not only will they occupy a large amount of system resources of the time series database, but the efficiency of data storage will also be low.
[0003] How to efficiently store IoT data into a time series database is a technical problem that needs to be solved. Summary of the invention
[0004] The technical task of the present invention is to address the above shortcomings and provide a system and method for efficiently storing IoT data into a time series database, so as to solve the technical problem of how to efficiently store IoT data into a time series database.
[0005] In a first aspect, the present invention provides a system for efficiently storing IoT data in a time series database, including a message receiving module, a message filtering module, and a message writing module;
[0006] The message receiving module is configured with a message data interaction mechanism, which is used to establish a connection with the IoT device based on the TCP / IP protocol, to receive IoT data uploaded by the IoT device through message subscription based on the message data interaction mechanism, and to push the IoT data to the message filtering module;
[0007] The message filtering module has a built-in rule engine, which describes the data source, data processing process and destination of the processing results, and is used to extract IoT data based on the data source and filtering conditions described in the rule engine, filter and convert IoT data based on the data processing process described in the rule engine, and output the filtered IoT data based on the processing results described in the rule engine;
[0008] The data writing module is connected to the time series database in a data integration manner, and is used to write the filtered Internet of Things data into the time series database.
[0009] Preferably, the message receiving module establishes a connection with the IoT device based on SSL / TLS encryption.
[0010] Preferably, the message data interaction mechanism includes three mechanisms, namely a first mechanism, a second mechanism and a third mechanism;
[0011] The first mechanism: The message is delivered at most once. After the sender sends a message to the receiver, it does not need to wait for the receiver's confirmation, and the sender does not need to store or retransmit the message that has been sent.
[0012] Second mechanism: The message is delivered at least once. After the sender sends a message to the receiver, based on the response and retransmission mechanism, the sender determines that the message is sent successfully after receiving the confirmation message from the receiver. Otherwise, the message is retransmitted to the receiver. Before the sender receives the confirmation message from the receiver, the sent message is stored.
[0013] The third mechanism: The message is delivered only once, and the request / response process is performed at least twice between the sender and the receiver.
[0014] Preferably, the rule engine specifies the data source through the FROM clause of the SQL statement to filter the IoT data through the topic;
[0015] The rule engine describes the data processing process through SQL statements and functions. The WHERE clause of the SQL statement is used to filter data, and the SELECT clause of the SQL statement and the SQL function are used to extract and transform data.
[0016] One or more actions are defined in the rule engine to process the output results of SQL statements. If the SQL statement is executed successfully, the rule engine executes the corresponding actions in sequence.
[0017] Preferably, the message writing module writes the matched filtered IoT data into the time series database through the RESTful API interface of the time series database;
[0018] The message writing module writes IoT data in batch mode in data integration. When writing IoT data in batch mode, a single piece of IoT data requested each time is temporarily stored. After a predetermined time is reached or a predetermined number of IoT data are accumulated, the entire batch of temporarily stored IoT data is written into the time series database.
[0019] In a second aspect, the present invention provides a method for efficiently storing IoT data in a time series database, wherein the IoT data is stored in a time series database through a system for efficiently storing IoT data in a time series database as described in any one of the first aspects, and the method comprises the following steps:
[0020] Message receiving: The message receiving module establishes a connection with the IoT device based on the TCP / IP protocol, receives the IoT data uploaded by the IoT device through message subscription based on the message data interaction mechanism, and pushes the IoT data to the message filtering module;
[0021] Message filtering: The rule engine of the message filtering module describes the data source, data processing process, and destination of the processing results. IoT data is extracted based on the data source and filtering conditions described in the rule engine, and the IoT data is filtered and converted based on the data processing process described in the rule engine. The filtered IoT data is output based on the processing results described in the rule engine.
[0022] Message writing: The data writing module is used to connect to the time series database in a data integration manner to write the filtered IoT data into the time series database.
[0023] Preferably, the message receiving module establishes a connection with the IoT device based on SSL / TLS encryption.
[0024] Preferably, the message data interaction mechanism includes three mechanisms, namely a first mechanism, a second mechanism and a third mechanism;
[0025] The first mechanism: The message is delivered at most once. After the sender sends a message to the receiver, it does not need to wait for the receiver's confirmation, and the sender does not need to store or retransmit the message that has been sent.
[0026] Second mechanism: The message is delivered at least once. After the sender sends a message to the receiver, based on the response and retransmission mechanism, the sender determines that the message is sent successfully after receiving the confirmation message from the receiver. Otherwise, the message is retransmitted to the receiver. Before the sender receives the confirmation message from the receiver, the sent message is stored.
[0027] The third mechanism: The message is delivered only once, and the request / response process is performed at least twice between the sender and the receiver.
[0028] Preferably, the rule engine specifies the data source through the FROM clause of the SQL statement to filter the IoT data through the topic;
[0029] The rule engine describes the data processing process through SQL statements and functions. The WHERE clause of the SQL statement is used to filter data, and the SELECT clause of the SQL statement and the SQL function are used to extract and transform data.
[0030] One or more actions are defined in the rule engine to process the output results of SQL statements. If the SQL statement is executed successfully, the rule engine executes the corresponding actions in sequence.
[0031] Preferably, the message writing module writes the matched filtered IoT data into the time series database through the RESTful API interface of the time series database;
[0032] The message writing module writes IoT data in batch mode in data integration. When writing IoT data in batch mode, a single piece of IoT data requested each time is temporarily stored. After a predetermined time is reached or a predetermined number of IoT data are accumulated, the entire batch of temporarily stored IoT data is written into the time series database.
[0033] The system method for efficiently storing IoT data into a time series database of the present invention has the following advantages:
[0034] 1. The system meets the needs of massive IoT device access, device management and data storage with its lightweight characteristics, low bandwidth consumption and efficient use of resources;
[0035] 2. The decoupling of data senders and data receivers is achieved, which effectively reduces network traffic and resource usage, and reduces resource consumption on the database side when connecting to the time series database;
[0036] 3. The efficiency of data entry has been improved through batch mode and multiple data integration. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0038] The present invention is further described below in conjunction with the accompanying drawings.
[0039] Figure 1 This is a flowchart of a method for efficiently storing IoT data into a time series database according to Example 2. DETAILED DESCRIPTION
[0040] The present invention is further described below in conjunction with the accompanying drawings and specific embodiments so that those skilled in the art can better understand the present invention and implement it. However, the embodiments are not intended to limit the present invention. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments may be combined with each other.
[0041] The embodiments of the present invention provide a system and method for efficiently storing IoT data into a time series database, which is used to solve the technical problem of how to efficiently store IoT data into a time series database.
[0042] Embodiment 1:
[0043] The present invention discloses a system for efficiently storing Internet of Things data into a time series database, comprising a message receiving module, a message filtering module and a message writing module.
[0044] The message receiving module is configured with a message data interaction mechanism, which is used to establish a connection with the IoT device based on the TCP / IP protocol, to receive the IoT data uploaded by the IoT device through message subscription based on the message data interaction mechanism, and to push the IoT data to the message filtering module.
[0045] In this embodiment, the message receiving module and the IoT device establish a connection based on SSL / TLS encryption, and the message data interaction mechanism includes three mechanisms, namely the first mechanism, the second mechanism and the third mechanism, which are as follows:
[0046] The first mechanism: The message is delivered at most once. After the sender sends a message to the receiver, it does not need to wait for the receiver's confirmation, and the sender does not need to store or retransmit the message that has been sent.
[0047] Second mechanism: The message is delivered at least once. After the sender sends a message to the receiver, based on the response and retransmission mechanism, the sender determines that the message is sent successfully after receiving the confirmation message from the receiver. Otherwise, the message is retransmitted to the receiver. Before the sender receives the confirmation message from the receiver, the sent message is stored.
[0048] The third mechanism: The message is delivered only once, and the request / response process is performed at least twice between the sender and the receiver.
[0049] Among the above three mechanisms, the first mechanism is that messages are sent and discarded immediately, and there is no need to wait for confirmation, store or retransmit. Therefore, the receiver never needs to worry about receiving duplicate messages. In order to ensure the arrival of messages, the second mechanism adds a response and retransmission mechanism on the basis of the first mechanism. The sender can only consider the message delivery successful after receiving the message from the receiver. Before that, the sender needs to store the message for the next retransmission. The third mechanism solves the problem that messages may be lost or duplicated in the first and second mechanisms, but correspondingly, it also brings the most complex interaction process and the highest overhead. Each message delivery of the third mechanism requires the sender and the receiver to go through at least two request / response processes.
[0050] IoT devices use TCP / IP protocol to establish a connection with the system, and can choose to use SSL / TLS encryption to achieve secure communication. IoT devices are responsible for publishing messages to topics, and can only send data to one topic at a time. There is no need to care about the state of the time series database when publishing messages. The system is responsible for processing IoT device requests, including establishing connections, disconnecting connections, subscribing and unsubscribing, and is also responsible for receiving and forwarding messages.
[0051] IoT devices may run in a network-restricted environment. Relying only on the underlying TCP transmission protocol cannot fully guarantee the reliable arrival of messages. Therefore, the system provides three message data interaction mechanisms for selection. The core is to design a variety of message interaction mechanisms to provide different service qualities to meet users' requirements for message reliability in various scenarios. Among them, using the first mechanism may result in message loss, using the second mechanism can ensure that messages are received, but messages may be repeated, and using the third mechanism can ensure that messages are neither lost nor repeated. The mechanism level from low to high not only means the improvement of message reliability, but also the improvement of transmission complexity.
[0052] The message filtering module has a built-in rule engine, which describes the data source, data processing process and the destination of the processing results. It is used to extract IoT data based on the data source and filtering conditions described in the rule engine, filter and convert IoT data based on the data processing process described in the rule engine, and output the filtered IoT data based on the processing results described in the rule engine.
[0053] As a specific implementation of the rule engine, the rule engine specifies the data source through the FROM clause of the SQL statement to filter IoT data through the topic; the rule engine describes the data processing process through SQL statements and functions, the WHERE clause of the SQL statement is used to filter data, and the SELECT clause of the SQL statement and the SQL function are used to extract and transform data; one or more actions are defined in the rule engine to process the output results of the SQL statement. If the SQL statement is executed successfully, the rule engine executes the corresponding actions in sequence.
[0054] In this embodiment, the rule engine is a built-in SQL-based data processing component of the system. When used with data integration, one-stop IoT data extraction, filtering, conversion, storage and processing can be achieved without writing code. The rule engine describes three aspects: data source, data processing process, and the destination of processing results.
[0055] Data source: The data source of the rule engine is the messages published by IoT devices. The rule engine specifies the source of the data through the FROM clause of SQL, so that message data can be filtered by topic.
[0056] Data processing process: The rule engine uses SQL statements and functions to describe the data processing process. The SQL WHERE clause is used to filter data, so that data can be filtered by message content. The SELECT clause and SQL functions are used to extract and convert data.
[0057] Destination of processing results: The rule engine can define one or more actions to process the output results of SQL. If the SQL is executed successfully, the rule engine will execute the corresponding actions in sequence.
[0058] The data writing module connects to the time series database in a data integration manner and is used to write the filtered IoT data into the time series database.
[0059] The message writing module writes the matched filtered IoT data into the time series database through the RESTful API interface of the time series database;
[0060] As a specific implementation of the message writing module, the message writing module writes IoT data in batch mode in data integration. When writing IoT data in batch mode, a single piece of IoT data requested each time is temporarily stored. After a predetermined time is reached or a predetermined number of IoT data are accumulated, the entire batch of temporarily stored IoT data is written into the time series database.
[0061] The system is connected to the time series database through data integration, and the matched data can be written into the time series database through the time series database RESTful API interface and other methods.
[0062] In data integration, through the connection pool, users do not need to recreate the connection for each request, which helps to reduce resource consumption and improve connection efficiency and concurrency.
[0063] Batch mode can also be used in data integration to improve writing efficiency and reduce network latency. Batch mode can write multiple pieces of data into external data integration at the same time. After enabling batch, the system will temporarily store a single piece of data for each request. After a certain period of time or a certain number of pieces of data have been accumulated, the entire batch of temporarily stored data will be written to the target data system. Compared with the writing method of a single message, in batch mode, the database system generally caches or preprocesses the message before formally processing it, thereby improving writing efficiency. Batch writing can also reduce the number of network transmissions, thereby reducing network latency.
[0064] Embodiment 2:
[0065] The present invention provides a method for efficiently storing IoT data into a time series database. The IoT data is stored in a time series database through a system as disclosed in Example 1. The method includes three steps: message receiving, message filtering, and message writing.
[0066] Step S100 message reception: The message receiving module establishes a connection with the IoT device based on the TCP / IP protocol, receives the IoT data uploaded by the IoT device through message subscription based on the message data interaction mechanism, and pushes the IoT data to the message filtering module.
[0067] In this embodiment, the message receiving module and the IoT device establish a connection based on SSL / TLS encryption, and the message data interaction mechanism includes three mechanisms, namely the first mechanism, the second mechanism and the third mechanism, which are as follows:
[0068] The first mechanism: The message is delivered at most once. After the sender sends a message to the receiver, it does not need to wait for the receiver's confirmation, and the sender does not need to store or retransmit the message that has been sent.
[0069] Second mechanism: The message is delivered at least once. After the sender sends a message to the receiver, based on the response and retransmission mechanism, the sender determines that the message is sent successfully after receiving the confirmation message from the receiver. Otherwise, the message is retransmitted to the receiver. Before the sender receives the confirmation message from the receiver, the sent message is stored.
[0070] The third mechanism: The message is delivered only once, and the request / response process is performed at least twice between the sender and the receiver.
[0071] Among the above three mechanisms, the first mechanism is that messages are sent and discarded immediately, and there is no need to wait for confirmation, store or retransmit. Therefore, the receiver never needs to worry about receiving duplicate messages. In order to ensure the arrival of messages, the second mechanism adds a response and retransmission mechanism on the basis of the first mechanism. The sender can only consider the message delivery successful after receiving the message from the receiver. Before that, the sender needs to store the message for the next retransmission. The third mechanism solves the problem that messages may be lost or duplicated in the first and second mechanisms, but correspondingly, it also brings the most complex interaction process and the highest overhead. Each message delivery of the third mechanism requires the sender and the receiver to go through at least two request / response processes.
[0072] IoT devices use TCP / IP protocol to establish a connection with the system, and can choose to use SSL / TLS encryption to achieve secure communication. IoT devices are responsible for publishing messages to topics, and can only send data to one topic at a time. There is no need to care about the state of the time series database when publishing messages. The system is responsible for processing IoT device requests, including establishing connections, disconnecting connections, subscribing and unsubscribing, and is also responsible for receiving and forwarding messages.
[0073] IoT devices may run in a network-restricted environment. Relying only on the underlying TCP transmission protocol cannot fully guarantee the reliable arrival of messages. Therefore, this method provides three message data interaction mechanisms for selection. The core is to design a variety of message interaction mechanisms to provide different service qualities to meet users' requirements for message reliability in various scenarios. Among them, using the first mechanism may result in message loss, using the second mechanism can ensure that messages are received, but messages may be repeated, and using the third mechanism can ensure that messages are neither lost nor repeated. The mechanism level from low to high not only means the improvement of message reliability, but also the improvement of transmission complexity.
[0074] Step S200 message filtering: The rule engine of the message filtering module describes the data source, data processing process and destination of the processing results. The IoT data is extracted based on the data source and filtering conditions described in the rule engine, the IoT data is filtered and converted based on the data processing process described in the rule engine, and the filtered IoT data is output based on the processing results described in the rule engine.
[0075] As a specific implementation of the rule engine, the rule engine specifies the data source through the FROM clause of the SQL statement to filter IoT data through the topic; the rule engine describes the data processing process through SQL statements and functions, the WHERE clause of the SQL statement is used to filter data, and the SELECT clause of the SQL statement and the SQL function are used to extract and transform data; one or more actions are defined in the rule engine to process the output results of the SQL statement. If the SQL statement is executed successfully, the rule engine executes the corresponding actions in sequence.
[0076] In this embodiment, the rule engine is a data processing component based on SQL. It can be used with data integration to achieve one-stop IoT data extraction, filtering, conversion, storage and processing without writing code. The rule engine describes three aspects: data source, data processing process, and the destination of processing results.
[0077] Data source: The data source of the rule engine is the messages published by IoT devices. The rule engine specifies the source of the data through the FROM clause of SQL, so that message data can be filtered by topic.
[0078] Data processing process: The rule engine uses SQL statements and functions to describe the data processing process. The SQL WHERE clause is used to filter data, so that data can be filtered by message content. The SELECT clause and SQL functions are used to extract and convert data.
[0079] Destination of processing results: The rule engine can define one or more actions to process the output results of SQL. If the SQL is executed successfully, the rule engine will execute the corresponding actions in sequence.
[0080] Step S300 message writing: connecting to the time series database in a data integration manner through a data writing module to write the filtered IoT data into the time series database.
[0081] As a specific implementation of message writing, IoT data is written in batch mode in data integration. When IoT data is written in batch mode, a single piece of IoT data requested each time is temporarily stored. After a predetermined time is reached or a predetermined number of IoT data pieces are accumulated, the entire batch of temporarily stored IoT data is written into a time series database.
[0082] By connecting to the time series database through data integration, the matched data can be written into the time series database through the time series database RESTful API interface and other methods.
[0083] In data integration, through the connection pool, users do not need to recreate the connection for each request, which helps to reduce resource consumption and improve connection efficiency and concurrency.
[0084] Batch mode can also be used in data integration to improve writing efficiency and reduce network latency. Batch mode can write multiple pieces of data into external data integration at the same time. After enabling batch, the system will temporarily store a single piece of data for each request. After a certain period of time or a certain number of pieces of data have been accumulated, the entire batch of temporarily stored data will be written to the target data system. Compared with the writing method of a single message, in batch mode, the database system generally caches or preprocesses the message before formally processing it, thereby improving writing efficiency. Batch writing can also reduce the number of network transmissions, thereby reducing network latency.
[0085] The present invention has been shown and described in detail above through the accompanying drawings and preferred embodiments. However, the present invention is not limited to these disclosed embodiments. Based on the above multiple embodiments, those skilled in the art can know that the means in the above different embodiments can be combined to obtain more embodiments of the present invention, and these embodiments are also within the protection scope of the present invention.
Claims
1. A system for efficiently storing IoT data in a time series database, characterized in that: It includes a message receiving module, a message filtering module and a message writing module; The message receiving module is configured with a message data interaction mechanism, which is used to establish a connection with the IoT device based on the TCP / IP protocol, to receive IoT data uploaded by the IoT device through message subscription based on the message data interaction mechanism, and to push the IoT data to the message filtering module; The message filtering module has a built-in rule engine, which describes the data source, data processing process and destination of the processing results, and is used to extract IoT data based on the data source and filtering conditions described in the rule engine, filter and convert IoT data based on the data processing process described in the rule engine, and output the filtered IoT data based on the processing results described in the rule engine; The data writing module is connected to the time series database in a data integration manner, and is used to write the filtered Internet of Things data into the time series database.
2. According to claim 1, the system for efficiently storing IoT data in a time series database is characterized in that: The message receiving module establishes a connection with the IoT device based on SSL / TLS encryption.
3. The system for efficiently storing IoT data in a time series database according to claim 1 is characterized in that: The message data interaction mechanism includes three mechanisms, namely the first mechanism, the second mechanism and the third mechanism; The first mechanism: The message is delivered at most once. After the sender sends a message to the receiver, it does not need to wait for the receiver's confirmation, and the sender does not need to store or retransmit the message that has been sent. Second mechanism: The message is delivered at least once. After the sender sends a message to the receiver, based on the response and retransmission mechanism, the sender determines that the message is sent successfully after receiving the confirmation message from the receiver. Otherwise, the message is retransmitted to the receiver. Before the sender receives the confirmation message from the receiver, the sent message is stored. The third mechanism: The message is delivered only once, and the request / response process is performed at least twice between the sender and the receiver.
4. The system for efficiently storing IoT data in a time series database according to claim 1 is characterized in that: The rule engine specifies the data source through the FROM clause of the SQL statement to filter IoT data through topics; The rule engine describes the data processing process through SQL statements and functions. The WHERE clause of the SQL statement is used to filter data, and the SELECT clause of the SQL statement and the SQL function are used to extract and transform data. One or more actions are defined in the rule engine to process the output results of SQL statements. If the SQL statement is executed successfully, the rule engine executes the corresponding actions in sequence.
5. The system for efficiently storing IoT data in a time series database according to claim 1 is characterized in that: The message writing module writes the matched filtered IoT data into the time series database through the RESTful API interface of the time series database; The message writing module writes IoT data in batch mode in data integration. When writing IoT data in batch mode, a single piece of IoT data requested each time is temporarily stored. After a predetermined time is reached or a predetermined number of IoT data are accumulated, the entire batch of temporarily stored IoT data is written into the time series database.
6. A method for efficiently storing IoT data in a time series database, characterized in that: The IoT data is stored in a time series database by using a system for efficiently storing IoT data in a time series database as described in any one of claims 1 to 5, and the method comprises the following steps: Message receiving: The message receiving module establishes a connection with the IoT device based on the TCP / IP protocol, receives the IoT data uploaded by the IoT device through message subscription based on the message data interaction mechanism, and pushes the IoT data to the message filtering module; Message filtering: The rule engine of the message filtering module describes the data source, data processing process, and destination of the processing results. IoT data is extracted based on the data source and filtering conditions described in the rule engine, and the IoT data is filtered and converted based on the data processing process described in the rule engine. The filtered IoT data is output based on the processing results described in the rule engine. Message writing: The data writing module is used to connect to the time series database in a data integration manner to write the filtered IoT data into the time series database.
7. The method for efficiently storing IoT data into a time series database according to claim 6, characterized in that: The message receiving module establishes a connection with the IoT device based on SSL / TLS encryption.
8. The method for efficiently storing IoT data into a time series database according to claim 6, characterized in that: The message data interaction mechanism includes three mechanisms, namely the first mechanism, the second mechanism and the third mechanism; The first mechanism: The message is delivered at most once. After the sender sends a message to the receiver, it does not need to wait for the receiver's confirmation, and the sender does not need to store or retransmit the message that has been sent. Second mechanism: The message is delivered at least once. After the sender sends a message to the receiver, based on the response and retransmission mechanism, the sender determines that the message is sent successfully after receiving the confirmation message from the receiver. Otherwise, the message is retransmitted to the receiver. Before the sender receives the confirmation message from the receiver, the sent message is stored. The third mechanism: The message is delivered only once, and the request / response process is performed at least twice between the sender and the receiver.
9. The method for efficiently storing IoT data into a time series database according to claim 6, characterized in that: The rule engine specifies the data source through the FROM clause of the SQL statement to filter IoT data through topics; The rule engine describes the data processing process through SQL statements and functions. The WHERE clause of the SQL statement is used to filter data, and the SELECT clause of the SQL statement and the SQL function are used to extract and transform data. One or more actions are defined in the rule engine to process the output results of SQL statements. If the SQL statement is executed successfully, the rule engine executes the corresponding actions in sequence.
10. The method for efficiently storing IoT data into a time series database according to claim 6, characterized in that: The message writing module writes the matched filtered IoT data into the time series database through the RESTful API interface of the time series database; The message writing module writes IoT data in batch mode in data integration. When writing IoT data in batch mode, a single piece of IoT data requested each time is temporarily stored. After a predetermined time is reached or a predetermined number of IoT data are accumulated, the entire batch of temporarily stored IoT data is written into the time series database.