Data processing method and industrial internet of things edge gateway system
By acquiring rule configuration information and collecting device data in the edge gateway system, local rule judgment and control are performed, solving the problems of high cloud computing pressure and low rule calculation efficiency, and achieving efficient data processing and real-time performance.
Patent Information
- Application Number
- CN202511173065.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-21
- Publication Date
- 2025-11-04
AI Technical Summary
In existing technologies, the cloud computing pressure of industrial IoT edge gateway systems is too high, the efficiency of rule calculation is low, and the data processing latency is large, resulting in low computing efficiency of industrial IoT platforms.
The data processing method implemented in the edge gateway system includes obtaining rule configuration information of the industrial IoT platform, collecting operating attribute data of industrial IoT devices, performing rule judgment, and executing corresponding system actions. It adopts a plug-in protocol architecture and TDengine time-series database for data storage and processing, supports multiple industrial protocols, and realizes local rule judgment and control.
It reduces the computing pressure on the cloud, improves the real-time performance and reliability of the system, enables local intelligent decision-making and control, reduces data processing latency, and improves the efficiency of rule calculation.
Smart Images

Figure CN120896816A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of industrial Internet of Things, and particularly relates to a data processing method and an industrial Internet of Things edge gateway system. BACKGROUND
[0002] In the technical field of industrial Internet of Things (IIoT), an edge gateway is responsible for collecting, processing and transmitting device working condition data to an industrial Internet of Things (IoT) platform in the cloud. The industrial IoT platform implements complex rule calculation by using hard coding or simple scripts. All rule calculations are completed in the industrial IoT platform, and the results of the rule calculations are issued to the edge gateway to realize device remote monitoring, operation and maintenance and intelligent control. Since all rule calculations are completed in the industrial IoT platform, the industrial IoT platform is under great computing pressure and the rule calculation efficiency is low. Moreover, when the edge gateway communicates with the industrial IoT platform, there is a problem of large data processing delay, which also leads to low rule calculation efficiency of the industrial IoT platform. SUMMARY
[0003] The technical scheme of the present application aims to provide a data processing method and an industrial Internet of Things edge gateway system to solve the problems of excessive computing pressure of the cloud and low rule calculation efficiency in the prior art.
[0004] To achieve the above-mentioned purpose, the present application is implemented as follows:
[0005] In a first aspect, an embodiment of the present application provides a data processing method applied to an industrial Internet of Things edge gateway system, and the method comprises the following steps:
[0006] obtaining rule configuration information issued by an industrial IoT platform;
[0007] collecting running attribute data of an industrial Internet of Things device;
[0008] performing rule judgment on the running attribute data according to the rule configuration information to obtain a judgment result;
[0009] executing an industrial Internet of Things system action indicated by the rule configuration information according to the judgment result.
[0010] Optionally, the data processing method, wherein the rule configuration information is further used to indicate at least one of the following:
[0011] a rule name;
[0012] a rule identifier;
[0013] a trigger;
[0014] time window;
[0015] trigger condition;
[0016] scheduling policy.
[0017] Optionally, the data processing method, wherein, after collecting the operation attribute data of the industrial Internet of Things device, the method further comprises:
[0018] storing the operation attribute data in a time series database;
[0019] performing rule judgment on the operation attribute data according to the rule configuration information to obtain a judgment result, comprising:
[0020] acquiring the operation attribute data from the time series database according to a rule name and / or a rule identifier indicated by the rule configuration information;
[0021] performing rule judgment on the operation attribute data according to at least one of a trigger, a time window and a trigger condition indicated by the rule configuration information to obtain a judgment result, in a case where a scheduling policy indicated by the rule configuration information is met.
[0022] Optionally, the data processing method, wherein, after storing the operation attribute data in the time series database, the method further comprises:
[0023] reporting the operation attribute data stored in the time series database to the industrial IoT platform.
[0024] Optionally, the data processing method, wherein the action of the industrial Internet of Things system comprises at least one of:
[0025] controlling the industrial Internet of Things device;
[0026] sending alarm information to the industrial IoT platform;
[0027] recording rule judgment logs.
[0028] Optionally, the data processing method, wherein, before collecting the operation attribute data of the industrial Internet of Things device, the method further comprises:
[0029] acquiring collection configuration information issued by the industrial IoT platform;
[0030] collecting the operation attribute data of the industrial Internet of Things device, comprising:
[0031] collecting the operation attribute data of the industrial Internet of Things device according to the collection configuration information.
[0032] In a second aspect, embodiments of the present application also provide an industrial IoT edge gateway system, comprising:
[0033] an acquisition module configured to acquire rule configuration information issued by an industrial IoT platform;
[0034] a collection module configured to collect running attribute data of an industrial IoT device;
[0035] a judgment module configured to perform rule judgment on the running attribute data according to the rule configuration information, to obtain a judgment result;
[0036] an execution module configured to execute an industrial IoT system action indicated by the rule configuration information according to the judgment result.
[0037] In a third aspect, embodiments of the present application also provide an industrial IoT edge gateway system, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the processor executes the program or instruction to implement the data processing method according to the first aspect.
[0038] In a fourth aspect, embodiments of the present application also provide a readable storage medium, wherein the readable storage medium stores a program, and the program is executable by a processor to implement the data processing method according to the first aspect.
[0039] In a fifth aspect, embodiments of the present application also provide a computer program product, comprising computer instructions, and the computer instructions are executable by a processor to implement the data processing method according to the first aspect.
[0040] The above technical solutions of the present application have the following advantages:
[0041] In the embodiments of the present application, the data processing method is applied to an industrial IoT edge gateway system, and comprises the following steps: acquiring rule configuration information issued by an industrial IoT platform; collecting running attribute data of an industrial IoT device; performing rule judgment on the running attribute data according to the rule configuration information, to obtain a judgment result; and executing an industrial IoT system action indicated by the rule configuration information according to the judgment result. In this way, the industrial IoT edge gateway system performs rule judgment on the running attribute data of the industrial IoT device according to the rule configuration information issued by the industrial IoT platform, thereby reducing the computing pressure of the cloud-side industrial IoT platform and improving the real-time performance and reliability of the system. BRIEF DESCRIPTION OF DRAWINGS
[0042] Figure 1 FIG. 1 is a flowchart of the data processing method according to the embodiments of the present application;
[0043] Figure 2An architecture diagram of a collection module in the industrial Internet of Things edge gateway system according to the embodiment of the present application is shown in the figure.
[0044] Figure 3 A timing diagram of rule configuration information issuing and executing according to the embodiment of the present application is shown in the figure.
[0045] Figure 4 A timing diagram of cloud-edge collaboration according to the embodiment of the present application is shown in the figure.
[0046] Figure 5 A structure diagram of the industrial Internet of Things edge gateway system according to the embodiment of the present application is shown in the figure.
[0047] Figure 6 An architecture diagram of the industrial Internet of Things edge gateway system interacting with an industrial IoT platform according to the embodiment of the present application is shown in the figure.
[0048] Figure 7 A hardware block diagram of the industrial Internet of Things edge gateway system according to the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION
[0049] To make the technical problems, technical solutions and advantages of the present application clearer, the following will be described in detail with reference to the drawings and specific embodiments.
[0050] In various embodiments of the present application, it should be understood that the size of the serial number of the following processes does not mean the order of execution, and the execution order of the processes should be determined according to their functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0051] In addition, the terms "system" and "network" are often used interchangeably in this document.
[0052] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be exchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second" are usually a class, and the number of objects is not limited, for example, the first object can be one or more. In addition, "and / or" in the specification and claims means at least one of the connected objects, and the character " / " generally represents an "or" relationship between the associated objects before and after.
[0053] Please refer to Figure 1 The embodiment of the present application provides a data processing method applied to an industrial Internet of Things edge gateway system, and the method comprises the following steps:
[0054] In step 101, rule configuration information issued by an industrial IoT platform is acquired.
[0055] It should be noted that the rule configuration information is configured by the industrial IoT platform. Specifically, the industrial IoT platform provides a visualization interface for creating, editing, and managing rule configuration information corresponding to each of the plurality of industrial IoT edge gateways.
[0056] Optionally, the rule configuration information is used to indicate at least one of the following:
[0057] a rule name;
[0058] a rule identifier;
[0059] a trigger;
[0060] a time window;
[0061] a trigger condition;
[0062] a scheduling strategy;
[0063] an industrial IoT system action.
[0064] The trigger is used to indicate a triggering manner of the rule indicated by the rule name and / or the rule identifier, which is either periodic triggering or event triggering.
[0065] The time window is used to indicate an aggregated calculation value within the time window.
[0066] The trigger condition includes multi-condition combination, range judgment, and trend judgment.
[0067] Optionally, the industrial IoT system action includes at least one of the following:
[0068] controlling an industrial IoT device;
[0069] sending alarm information to the industrial IoT platform;
[0070] recording rule judgment logs.
[0071] It should be noted that controlling an industrial IoT device is used to indicate setting at least one attribute parameter of an industrial IoT device. The controlled industrial IoT device and the industrial IoT device that collects the running attribute data can be different. For example, the industrial IoT device that collects the running attribute data is a temperature sensor, and the controlled industrial IoT device is an air conditioner, thereby achieving a closed-loop control effect.
[0072] Step 102, collecting running attribute data of an industrial IoT device;
[0073] In the embodiment of the present application, the industrial Internet of Things edge gateway system supports multiple industrial protocols, such as Modbus, OPC UA, PLC-S7, etc., realizes efficient collection of running attribute data of industrial Internet of Things devices, and supports broken line continuous transmission and adaptive sampling.
[0074] It should be noted that after collecting the running attribute data, the industrial Internet of Things edge gateway system can preprocess the running attribute data, at least including data analysis and format conversion.
[0075] Specifically, the industrial Internet of Things edge gateway system includes a data collection module, which can be designed with a modular and plug-in architecture to meet the unified access needs of different manufacturers and different communication protocol devices in the industrial field. The data collection module has good scalability, maintainability and pluggability, and can load or unload protocol drivers on demand without interrupting system operation, thereby realizing flexible collection and management of industrial Internet of Things devices.
[0076] Next, the data collection module is described from the following four aspects.
[0077] (I) Overall architecture design
[0078] As shown in Figure 2 , the overall architecture of the data collection module includes the following three layers:
[0079] Protocol Manager (Protocol Manager), responsible for unified management of loading, unloading, life cycle maintenance and protocol resource configuration of various protocol drivers;
[0080] Protocol Factory (Protocol Factory), which realizes dynamic instantiation of protocol driver objects and supports runtime creation of corresponding protocol driver instances according to name or configuration file;
[0081] Protocol Driver Abstraction Layer (Protocol Driver Abstraction Layer), which defines a unified protocol driver interface, and all protocol drivers (such as Modbus driver, OPC UA driver, S7 driver, etc.) need to implement this interface to ensure the universality and decoupling of the upper logic.
[0082] (II) Unified definition of driver interface
[0083] To realize the plug-in and unified calling mechanism of the driver, all protocol drivers need to follow the unified interface specification, including but not limited to the following functions:
[0084] Connect(params): Establish a connection with the industrial IoT device, parameters include IP address, port, station number, etc.
[0085] disconnect(): Disconnect the current device connection and release resources.
[0086] read(address): Read data at the specified address, address supports point table mapping or structured identifier.
[0087] write(address, value): Write data to the specified address, support parameter verification and write confirmation mechanism.
[0088] The interface of the data collection module allows the reuse of upper-layer collection logic among different protocol drivers and seamless switching between protocol drivers.
[0089] (Three) Hot plug and dynamic loading mechanism of driver
[0090] The hot loading function of the protocol driver module is realized through dynamic link library (such as.so file). The protocol driver is loaded into memory by the protocol factory as needed at runtime, without the need to restart the edge system service, which can extend support for new protocol types or upgrade existing protocol logic, including the following advantages:
[0091] Support runtime dynamic expansion to adapt to future additions of industrial protocols;
[0092] Ensure stable operation of the main program to avoid affecting the overall system due to protocol updates;
[0093] Independent running between drivers, no interference, improve system robustness and maintainability.
[0094] (Four) Configuration of driving parameter management
[0095] The running parameters of each protocol driver are managed through centralized configuration. Users can adjust them through configuration files (such as JSON or YAML) or industrial IoT platform command issuance. Typical configuration items include:
[0096] Communication parameters, including IP address, port, slave station number, channel number;
[0097] Sampling frequency, supporting flexible sampling period from milliseconds to seconds;
[0098] Register mapping, support address mapping table / point table automatic conversion to standard structure;
[0099] Fault reconnection strategy, such as retry interval after connection failure, maximum number of attempts, etc.
[0100] After the configuration parameter is changed, the protocol manager can dynamically reload the corresponding drive instance and refresh the configuration thereof through the protocol factory to achieve hot updating of the runtime parameter.
[0101] In an embodiment, after the operation attribute data of the industrial internet of things device is collected, the method further includes:
[0102] storing the operation attribute data in a time series database.
[0103] It should be noted that the time series database includes a TDengine time series database, which is a data landing storage system and is specially used for storing the operation attribute data of the industrial internet of things device to support efficient data storage writing, querying, rule judging and data backtracking.
[0104] Next, the TDengine time series database is described from the following four aspects.
[0105] (I) TDengine advantages
[0106] TDengine is a high-performance time series database optimized for the internet of things, including the following characteristics:
[0107] Supports writing of millions of data points;
[0108] Provides millisecond-level query delay;
[0109] Built-in data compression and archiving;
[0110] Natively supports SQL queries and REST interfaces;
[0111] Supports super table and tag structures to facilitate unified modeling of device data.
[0112] (II) Data model design
[0113] In the industrial internet of things edge gateway system, each industrial internet of things device or logical channel corresponds to a super table, and the structure of the super table is as follows:
[0114]
[0115] Data writing example:
[0116] INSERT INTO d1001 USING device_data TAGS('dev001', 'Line1', 'S7') VALUES(NOW, 101, 'temperature', 27.5, 1, 0).
[0117] (III) Write and read mechanism
[0118] Write mechanism, the data processing module writes data into the TDengine time series database in batches at fixed periods or variable events. The system uses a queue buffer mechanism to improve write throughput.
[0119] Read mechanism, the rule engine module filters data by time range, label or specific data point from the TDengine time series database through the SQL query interface. The following operations are supported:
[0120] Near 10-minute average value query;
[0121] Maximum / minimum value of a specified time period, etc.
[0122] Latest value of a specific device attribute;
[0123] (IV) Data retention policy and partition management
[0124] The system supports automatic data archiving and cleaning mechanism:
[0125] Support automatic creation of sub-tables by month / week / day;
[0126] Support cleaning of historical data at a set period (e.g., retain for 7 days);
[0127] Support exporting historical data to local or cloud storage.
[0128] Due to the limited storage space of the industrial IoT edge gateway system, it is set to retain data for 7 days, and data outside of 7 days is automatically cleaned by the system.
[0129] In one embodiment, after storing the running attribute data in the time series database, the method further comprises:
[0130] Reporting the running attribute data stored in the time series database to the industrial IoT platform.
[0131] It should be noted that after storing the collected running attribute data in the local time series database, the industrial IoT edge gateway system reports the running attribute data to the industrial IoT platform for data backup.
[0132] In one embodiment, before collecting the running attribute data of the industrial IoT device, the method further comprises:
[0133] Obtaining the collection configuration information issued by the industrial IoT platform;
[0134] Collecting the running attribute data of the industrial IoT device, including:
[0135] According to the collection configuration information, the running attribute data of the industrial Internet of Things device is collected.
[0136] In the embodiment of the application, the running attribute data of the industrial Internet of Things device, such as temperature data and humidity data, is collected according to the collection configuration information issued by the industrial IoT platform.
[0137] The collection configuration information can be point table configuration information, which is used to indicate the identification or name of the industrial Internet of Things device and the running attribute data of the industrial Internet of Things device that needs to be collected.
[0138] In step 103, the running attribute data is subjected to rule judgment according to the rule configuration information, and a judgment result is obtained.
[0139] In one embodiment, the running attribute data is subjected to rule judgment according to the rule configuration information, and a judgment result is obtained, including:
[0140] According to the rule name and / or rule identification indicated by the rule configuration information, the running attribute data is obtained from the time series database.
[0141] In the case of meeting the scheduling strategy indicated by the rule configuration information, the running attribute data is subjected to rule judgment according to at least one of the trigger, the time window and the trigger condition indicated by the rule configuration information, and a judgment result is obtained.
[0142] In the embodiment of the application, the industrial Internet of Things edge gateway system includes a rule engine module. Based on the running attribute data that has been collected and stored in the TDengine time series database, periodic triggering or event triggering data calculation, condition judgment and action execution are performed according to the rule configuration information, which breaks through the closed loop path of data collection, processing, analysis and control, and realizes real edge intelligent decision control.
[0143] The rule engine module includes a rule parser, a rule scheduler, a condition evaluator and an action dispatcher, which complete the complete process from rule configuration to trigger judgment to response execution.
[0144] The rule parser is used to structurally parse the rule configuration information configured and issued by the user through the industrial IoT platform or defined in the local configuration file, and construct a logical representation structure executable in the system, including at least one of rule identification, rule name, trigger, time window, trigger condition, scheduling strategy and industrial Internet of Things system action.
[0145] The language example of rule configuration information is as follows: the rule id is rule 1; the rule description (desc) is to start the air conditioner if the temperature is between 30 and 40 DEG C; the time window (window) is 50 s; the trigger (trigger) is periodic trigger; the trigger condition (conditions) includes: the calculation type (type) is average value; the industrial internet of things device (device) is d1001; the attribute (property) is temperature; the operation condition (operator) is greater than; the trigger value (value) is [30.0]; the industrial internet of things system action includes: controlling the industrial internet of things device and sending alarm information to the industrial IoT platform.
[0146]
[0147] The rule scheduler is used to periodically execute the rule judgment process according to the scheduling strategy defined by the rule configuration information, and supports the following trigger modes:
[0148] Periodic scheduling (for example, checking whether the rule is satisfied once every 1 minute or 5 minutes);
[0149] Event triggered type (for example, checking the associated rule immediately when a certain data point changes);
[0150] Manual trigger (for debugging and testing stage);
[0151] The rule scheduler will schedule the condition calculation engine to judge the rule condition when the trigger period arrives each time.
[0152] The condition evaluator is used to extract the running attribute data associated with the rule from the TDengine time series database, and to calculate and judge, supporting the following operations:
[0153] Time window function calculation, including average value avg(x, 5min), maximum value max(x, 10min), slope slope(x, 3min);
[0154] Logical expression judgment, such as x>50&&y<20, (a-b)>10;
[0155] Multi-point combination analysis, such as "high temperature and low pressure" to trigger;
[0156] The calculation result is a Boolean value, indicating whether the trigger condition is satisfied.
[0157] The data acquisition mode adopts SQL query to access the TDengine time series database, for example:
[0158] SELECT avg(temperature) FROM d1001 WHERE ts > now-5m AND dpId=101;
[0159] Once the rule is determined to be "satisfied", the action executor will complete the corresponding operation according to the action content preset in the rule configuration information. The supported action types include:
[0160] Device control, including calling control interfaces (such as Modbus write, PLC-S7 write, OPC UA method call) to change device state;
[0161] Platform alarm, generating alarm information and reporting to the industrial IoT platform through the Message Queuing Telemetry Transport (MQTT) protocol;
[0162] Local log: write rule trigger records into local log or event database;
[0163] The action execution has idempotency control and failure retry mechanism to ensure control stability and consistency.
[0164] Figure 3 The timing diagram for the rule configuration information in the embodiment of the present application is issued for execution. As shown in Figure 3 The process of issuing the rule configuration information for execution includes:
[0165] Step 301, rule issuing:
[0166] The user configures the rule through the industrial IoT platform, and after the configuration is completed, the industrial IoT platform issues the rule configuration information to the cloud-edge collaboration module of the industrial IoT edge gateway system through the MQTT protocol, and the cloud-edge collaboration module forwards the rule configuration information to the rule engine module.
[0167] Step 302, data collection:
[0168] The data collection module establishes a connection with the field device through the communication interface (for example, Ethernet port and serial port), supports multiple industrial protocols, including PLC-S7, Modbus RTU / TCP, and OPC UA, etc. During the data collection process, point table data will be read from the industrial IoT device in batches, and the collected running attribute data will be sent to the data processing module.
[0169] Step 303, data storage and reporting:
[0170] The data processing module stores the running attribute data into the TDengine time series database after analyzing the running attribute data transmitted by the data acquisition module, and encapsulates the running attribute data according to a reporting strategy and sends the running attribute data to an industrial IoT platform through an MQTT protocol by the cloud-edge collaboration module for data storage, real-time monitoring and analysis by the cloud.
[0171] Step 304, query data:
[0172] The rule engine module queries the running attribute data from the TDengine time series database through a sql statement, and can query the latest value of a certain attribute, or query the average value, maximum value, minimum value and the like of a past event.
[0173] Step 305, return result:
[0174] The TDengine time series database returns the queried running attribute data to the rule engine module.
[0175] Step 306, condition judgment:
[0176] The rule engine module performs condition judgment on the queried running attribute data to determine whether a trigger action or an alarm is met.
[0177] Step 307, trigger action or alarm:
[0178] After the trigger condition is met, a corresponding action is performed on the industrial IoT device or an alarm information is reported to the industrial IoT platform.
[0179] Step 104, according to the judgment result, performing an industrial IoT system action indicated by the rule configuration information.
[0180] Here, taking the running attribute data of the industrial IoT device as temperature data as an example, if the judgment result is that the average temperature in a preset time period exceeds a temperature threshold value, and the air conditioner needs to be started, the rule configuration information indicates that the air conditioner is controlled to be turned on, and temperature alarm information is sent to the industrial IoT platform, and rule judgment logs are recorded.
[0181] In an embodiment, the method further includes at least one of the following:
[0182] In the case that the industrial IoT edge gateway is started or reset for the first time, a device registration request is sent to the industrial IoT platform, and registration confirmation information sent by the industrial IoT platform is obtained;
[0183] In the case that the rule engine module performs an alarm action indicated by the rule configuration information, an alarm information is reported to the industrial IoT platform;
[0184] Receive the firmware upgrade task issued by the industrial IoT platform, and perform an upgrade operation according to the firmware upgrade task.
[0185] It should be noted that, in order to realize the data interaction, rule configuration synchronization, device management and remote operation and maintenance between the industrial Internet of Things edge gateway system and the industrial IoT platform in the embodiment of the application, the industrial Internet of Things edge gateway includes a cloud-edge collaboration module, which can serve as a bridge between the industrial Internet of Things edge gateway system and the industrial IoT platform, and is responsible for completing device registration, configuration issuing, alarm reporting and Over-the-Air Technology (OTA) upgrade functions, realizing cloud-edge collaboration, data interconnection and control unification. Specifically, the cloud-edge collaboration module includes a registration and authentication submodule, a configuration and command issuing submodule, a data and alarm reporting submodule and an OTA upgrade management submodule.
[0186] The registration and authentication submodule is configured to, in the case that the industrial Internet of Things edge gateway is started or reset for the first time, send a device registration request to the industrial IoT platform through an https protocol, and obtain registration confirmation information sent by the industrial IoT platform, for subsequent communication between the industrial Internet of Things edge gateway system and the industrial IoT platform, to ensure the security of device identity and data transmission. The device registration request includes at least one of a device serial number (SN), a manufacturer ID, a manufacturer secret (ProductSecret) and a manufacturer identifier; and the registration confirmation information includes a device identifier and a device secret.
[0187] The configuration and command issuing submodule is configured to receive and analyze configuration instructions and control instructions issued by the industrial IoT platform, wherein the configuration instructions at least include point table configuration information, acquisition protocol parameters, rule configuration information and reporting strategies; and the control instructions at least include device parameter setting instructions and control operation instructions (such as Modbus write register). The above instructions are forwarded to the corresponding submodule through an internal task scheduling mechanism, to ensure timely configuration effectiveness, clear logic and efficient operation.
[0188] The data and alarm reporting submodule is configured to report running attribute data collected by the industrial Internet of Things edge gateway system and alarm information triggered by rule judgment to the industrial IoT platform. Periodic or change reporting modes are supported, and a compression algorithm can be enabled to save bandwidth. The reporting mode adopts an MQTT protocol, and the QoS level, encryption mode and disconnection retransmission strategy can be configured to ensure stable and reliable transmission of key data in a complex network environment.
[0189] The OTA upgrade management submodule is configured to receive a firmware upgrade task issued by the industrial IoT platform and perform an upgrade operation according to the firmware upgrade task. Specifically, the OTA upgrade management submodule supports whole package and differential package downloading. After receiving the firmware upgrade task, the OTA upgrade management submodule first performs SHA-256 signature and data integrity verification, and then performs an upgrade operation according to a preset upgrade strategy. The preset upgrade strategy includes at least one of timing upgrade, user triggering, and unattended operation. During the upgrade operation, mechanisms such as breakpoint resume, log recording, and rollback protection are supported to ensure the stability and security of the industrial IoT edge gateway system during the upgrade operation, thereby effectively reducing remote maintenance costs.
[0190] Figure 4 A timing diagram of cloud-edge collaboration in the embodiments of the present application is shown in FIG. 4. As shown in FIG. 4, the process of cloud-edge collaboration includes the following steps. Figure 4
[0191] Step 401: Configuration Issuance
[0192] The industrial IOT platform sends configuration instructions to the industrial IoT edge gateway system, including point table configuration information, protocol parameters, and rule configuration information. These configurations are transmitted through the MQTT protocol and encapsulated into standard instruction formats.
[0193] Step 402: Instruction Forwarding
[0194] After receiving the instructions, the cloud-edge collaboration module performs format analysis and verification, and forwards the analyzed instructions to the corresponding modules. If the instructions are point table configuration information, they are sent to the data acquisition module. If the instructions are rule configuration information, they are sent to the rule engine module. If the instructions are control instructions (for example, write register), they are sent to the protocol driver module.
[0195] Step 403: Instruction Execution
[0196] The instructions are executed to update the configurations or perform control actions.
[0197] Step 404: Feedback of Results
[0198] The execution results (success / failure, status code, error information, etc.) are returned to the cloud-edge collaboration module, which encapsulates the processing results of the instruction execution and feeds them back to the industrial IOT platform, so that the industrial IOT platform can confirm whether the instructions are executed successfully.
[0199] Step 405: Reporting of Data and Alarms
[0200] According to the reporting strategy, the industrial IoT edge gateway system reports the collected data to the industrial IOT platform, and the rule engine module judges whether the data meet the triggering conditions, generates alarm information, and reports it.
[0201] In summary, the data processing method described in the embodiment of the present application deploys data acquisition, processing, rule judgment and response action in the industrial Internet of Things edge gateway system, and the industrial IoT platform that is independent of the cloud can also run independently, has complete local closed-loop control capability, effectively avoids the intermediate delay and fault points in the cloud rule issuance, network transmission and gateway response, and realizes "edge intelligence"; moreover, the plug-in protocol architecture is adopted, the unified drive interface definition and factory registration mechanism are defined, the protocol drive can be dynamically added, the on-site complex device connection demand is met; the new protocol drive only needs to realize the interface, without changing the main program, which greatly improves the maintainability and life cycle of the system; and the TDengine time series database is adopted, which has the advantages of high write performance, high compression rate and high query efficiency, and can exhibit significant advantages in time series data scenarios, and is particularly suitable for deployment in ARM-Linux resource-limited environments.
[0202] The advantages of the data processing method described in the embodiment of the present application compared with the prior art include:
[0203] The time series data processing efficiency is high, compared with the B+ tree index structure of the relational database in the prior art, the embodiment of the present application adopts a time series database suitable for efficient write and range query of time series data, has an effective data compression mechanism, saves storage space occupation, and avoids performance bottlenecks when writing frequently;
[0204] The rule engine has real-time performance, compared with the rule checking method based on polling in the prior art, the embodiment of the present application adopts rule configuration information, has fast response speed, and the data is stored locally, and has real-time performance;
[0205] The degree of intelligence is high, the definition of the rule configuration information in the embodiment of the present application is flexible, complex industrial logic can be easily expressed, trend analysis and predictive rules based on historical data can be supported, and a rule management and update mechanism can be supported;
[0206] It has reliability and stability, the data processing method described in the embodiment of the present application can avoid data loss after system power failure, ensures that the long-running system will not have memory leaks, and has an effective self-monitoring and recovery mechanism;
[0207] Supports multi-protocol acquisition;
[0208] Cloud edge collaboration, the cloud configuration in the embodiment of the present application can be dynamically issued to the edge and combined with local computing.
[0209] Please refer to Figure 5 The embodiment of the present application also provides an industrial Internet of Things edge gateway system, which comprises:
[0210] The acquisition module 501 is configured to acquire rule configuration information issued by an Internet of Things platform.
[0211] The collection module 502 is configured to collect running attribute data of an industrial Internet of Things device.
[0212] The judgment module 503 is configured to perform rule judgment on the running attribute data according to the rule configuration information, to obtain a judgment result.
[0213] The execution module 504 is configured to perform an industrial Internet of Things system action indicated by the rule configuration information according to the judgment result.
[0214] Optionally, the industrial Internet of Things edge gateway system, wherein the rule configuration information is further configured to indicate at least one of the following:
[0215] a rule name;
[0216] a rule identifier;
[0217] a trigger;
[0218] a time window;
[0219] a trigger condition;
[0220] a scheduling strategy.
[0221] Optionally, the industrial Internet of Things edge gateway system, wherein the system further comprises:
[0222] a storage module configured to store the running attribute data in a time series database;
[0223] The judgment module 503 is specifically configured to:
[0224] acquire the running attribute data from the time series database according to a rule name and / or a rule identifier indicated by the rule configuration information;
[0225] perform rule judgment on the running attribute data according to at least one of a trigger, a time window and a trigger condition indicated by the rule configuration information, to obtain a judgment result, in a case where a scheduling strategy indicated by the rule configuration information is met.
[0226] Optionally, the industrial Internet of Things edge gateway system, wherein the system further comprises:
[0227] a reporting module configured to report the running attribute data stored in the time series database to the Internet of Things platform.
[0228] Optionally, the industrial Internet of Things edge gateway system, wherein the industrial Internet of Things system action comprises at least one of the following:
[0229] controlling industrial internet of things devices;
[0230] sending alarm information to the internet of things platform;
[0231] record rule judgment log.
[0232] Optionally, the industrial internet of things edge gateway system, wherein the system further comprises:
[0233] an acquisition configuration module for acquiring the collection configuration information issued by the internet of things platform;
[0234] the collection module 502, specifically for:
[0235] collecting the running attribute data of the industrial internet of things devices according to the collection configuration information.
[0236] Figure 6 The industrial internet of things edge gateway system in the embodiment of the application and the architecture schematic diagram of the interaction with the industrial IoT platform are shown in the figure. Figure 6 As shown in the figure, the industrial IoT platform is used for a device monitoring and alarm module and a configuration and instruction management module, wherein the device monitoring and alarm module is used for real-time display of device running state, receiving and analyzing the alarm reported by the edge gateway, supporting alarm grading, notification and work order linkage; the configuration and instruction management module is used for providing a visual interface for creating, editing and managing the rule logic, point table configuration information and the like of the edge gateway.
[0237] The edge gateway system comprises a data collection module, a data processing module, a cloud-edge collaboration module, a TDengine database and a rule engine module, wherein the data collection module is used for supporting multi-protocol data collection, such as Modbus, OPC UA, PLC-S7 and the like industrial protocols, realizing efficient collection of the running attribute data of the industrial internet of things devices, supporting broken line continuous transmission and adaptive sampling; the data processing module is used for data analysis, format conversion and time series data storage of the collected raw data; the cloud-edge collaboration module is used as a bridge between the industrial internet of things edge gateway system and the industrial IoT platform, responsible for completing device registration, configuration issuing (collection point table configuration, rule configuration), alarm reporting, device data reporting (periodic reporting, change reporting, offline supplement), OTA upgrade and the like core interaction functions; the TDengine database is used for high-performance time series data storage, supporting fast writing, compressed storage and time range query, optimizing rule calculation efficiency; the rule engine module is used for analyzing and executing user-defined rules, performing data query and statistical analysis (such as moving average, trend prediction) based on the running attribute data, supporting threshold alarm, composite condition judgment, controlling devices or cloud alarm.
[0238] It should be noted that the industrial internet of things edge gateway system provided by the embodiment of the present application can execute the data processing method described above, and all embodiments of the data processing method described above are applicable to the industrial internet of things edge gateway system and can achieve the same or similar technical effects.
[0239] As shown in Figure 7 , the embodiment of the present application also provides an industrial internet of things edge gateway system, comprising: a processor 701; and a memory 702 connected to the processor 701 through a bus interface, the memory 702 being used to store programs and data used by the processor 701 in executing operations, and the processor 701 calling and executing the programs and data stored in the memory 702.
[0240] The processor 701 is used to read the programs in the memory 702 and execute the following processes:
[0241] Obtain the rule configuration information issued by the internet of things platform;
[0242] Collect the running attribute data of the industrial internet of things device;
[0243] According to the rule configuration information, the running attribute data is subjected to rule judgment to obtain a judgment result;
[0244] According to the judgment result, the industrial internet of things system action indicated by the rule configuration information is executed.
[0245] Among them, in Figure 7 , the bus architecture can include any number of interconnected buses and bridges, and various circuits of the processor 701 representing one or more processors and the memory 702 representing the memory are connected together. The bus architecture can also connect various other circuits such as peripheral devices, voltage stabilizers and power management circuits, which are well known in the art, and therefore, they will not be further described herein. The bus interface provides an interface. The transceiver 703 can be a plurality of elements, i.e. including a transmitter and a transceiver, providing a unit for communicating with various other devices on a transmission medium. The user interface 704 can also be an interface that can be connected to the required device, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.
[0246] The processor 701 is responsible for managing the bus architecture and general processing, and the memory 702 can store data used by the processor 701 in executing operations.
[0247] Optionally, the rule configuration information is also used to indicate at least one of the following:
[0248] Rule name;
[0249] rule identifier;
[0250] trigger;
[0251] time window;
[0252] trigger condition;
[0253] scheduling strategy.
[0254] Optionally, the processor 701 is further configured to read a program and perform the following steps:
[0255] store the running attribute data in a time series database;
[0256] perform rule judgment on the running attribute data according to the rule configuration information, to obtain a judgment result, including:
[0257] obtain the running attribute data from the time series database according to a rule name and / or a rule identifier indicated by the rule configuration information;
[0258] perform rule judgment on the running attribute data according to at least one of a trigger, a time window, and a trigger condition indicated by the rule configuration information, to obtain a judgment result, in a case where a scheduling strategy indicated by the rule configuration information is met.
[0259] Optionally, the processor 701 is further configured to read a program and perform the following steps:
[0260] report the running attribute data stored in the time series database to the Internet of Things platform.
[0261] Optionally, the action of the industrial Internet of Things system includes at least one of:
[0262] controlling an industrial Internet of Things device;
[0263] sending alarm information to the Internet of Things platform;
[0264] recording a rule judgment log.
[0265] Optionally, the processor 701 is further configured to read a program and perform the following steps:
[0266] obtain collection configuration information issued by the Internet of Things platform;
[0267] collect running attribute data of an industrial Internet of Things device, including:
[0268] collect running attribute data of an industrial Internet of Things device according to the collection configuration information.
[0269] The embodiment of the present application further provides a computer readable storage medium, and the computer readable storage medium stores a computer program.
[0270] The embodiment of the present application further provides a computer program product, which comprises computer instructions, and the computer instructions are executed by a processor to realize each process of the data processing method embodiment and achieve the same technical effects.
[0271] It should be noted that, in this document, the term "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that processes, methods, articles, or devices including a series of elements not only include those elements, but also include other elements not explicitly listed, or further include elements inherent to such processes, methods, articles, or devices. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article, or device including the element.
[0272] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be realized by means of software and necessary general hardware platforms, and of course, they can also be realized by hardware, but in many cases, the former is a better embodiment. Based on this understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a plurality of instructions for making a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) execute the methods described in each embodiment of the present application.
[0273] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above-mentioned specific embodiments, and the above-mentioned specific embodiments are only illustrative, not restrictive. Those skilled in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope of protection of the claims, and all of them belong to the protection of the present application.
Claims
1. A data processing method, characterized in that, The method, applied to an industrial IoT edge gateway system, includes: Obtain rule configuration information issued by the industrial IoT platform; Collect operational attribute data from industrial IoT devices; The runtime attribute data is subjected to rule judgment based on the rule configuration information to obtain the judgment result; Based on the judgment result, the industrial IoT system actions indicated by the rule configuration information are executed.
2. The method according to claim 1, characterized in that, The rule configuration information is also used to indicate at least one of the following: Rule name; Rule identifier; trigger; Time window; Triggering conditions; Scheduling strategy.
3. The method according to any one of claims 1 or 2, characterized in that, After collecting the operational attribute data of industrial IoT devices, the method further includes: The runtime attribute data is stored in a time-series database; The runtime attribute data is subjected to rule judgment based on the rule configuration information to obtain the judgment result, including: Based on the rule name and / or rule identifier indicated by the rule configuration information, the runtime attribute data is obtained from the time series database; When the scheduling strategy indicated by the rule configuration information is satisfied, the running attribute data is judged according to at least one of the trigger, time window and trigger condition indicated by the rule configuration information, and the judgment result is obtained.
4. The method according to claim 3, characterized in that, After storing the runtime attribute data in a time-series database, the method further includes: The runtime attribute data stored in the time-series database is reported to the industrial Internet of Things platform.
5. The method according to any one of claims 1 or 2, characterized in that, The industrial IoT system operation includes at least one of the following: Controlling industrial IoT devices; Send alarm information to the industrial IoT platform; Record rule judgment logs.
6. The method according to claim 1, characterized in that, Before collecting operational attribute data from industrial IoT devices, the method further includes: Obtain the data collection configuration information issued by the industrial IoT platform; Collect operational attribute data of industrial IoT devices, including: Based on the aforementioned data collection configuration information, operational attribute data of industrial IoT devices are collected.
7. An industrial Internet of Things (IoT) edge gateway system, characterized in that, include: The acquisition module is used to acquire rule configuration information issued by the industrial IoT platform; The data acquisition module is used to collect operational attribute data from industrial IoT devices. The judgment module is used to perform rule judgment on the running attribute data according to the rule configuration information and obtain the judgment result; The execution module is used to execute the industrial IoT system actions indicated by the rule configuration information based on the judgment result.
8. An industrial Internet of Things (IoT) edge gateway system, characterized in that, include: A processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the processor, when executing the program or instructions, implements the data processing method as described in any one of claims 1 to 6.
9. A readable storage medium, characterized in that, The readable storage medium stores a program that, when executed by a processor, implements the data processing method as described in any one of claims 1 to 6.
10. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the data processing method as described in any one of claims 1 to 6.