IOT data processing method based on defined template variables, computer equipment and medium

Abstract

The invention discloses an IOT data processing method based on definition template variables, computer equipment and a medium, and relates to the technical field of data processing.The method comprises the steps that a message sent by target equipment is obtained; judging whether the target equipment is associated with a preset protocol template or not according to the information message, wherein the protocol template is used for defining a mapping relationship among a template, equipment, a bit number, a driver, a driver configuration, a bit number acquisition rule and a bit number acquisition rule configuration; if yes, executing the information message according to the protocol template; and if not, updating the protocol template according to the information message, and executing the information message according to the new protocol template. According to the invention, the data template can be constructed through free definition to analyze and process the Internet of Things equipment data of various different types of protocols.

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular to an IOT data processing method, a computer device and a medium based on defining template variables. Background Art

[0002] At present, there are various device communication protocols in the market, such as MQTT, JT808, TCP ModBUS, etc. These protocols are often independently developed by different manufacturers. Therefore, the existing technologies mainly have the following problems and defects:

[0003] (1) Poor interoperability: The device protocols used by different manufacturers are different, making it difficult to achieve seamless connection between devices;

[0004] (2) Complex integration: The secondary development and integration work is cumbersome. Developers need to spend a lot of time and resources for adaptation, reducing the development efficiency;

[0005] (3) Lack of unified standard: Due to the lack of a unified industry standard, some manufacturers have even extended on the basis of common protocols. Devices often face compatibility problems in actual applications, increasing the complexity of enterprise device management and data integration.

[0006] Therefore, the industry urgently needs a unified solution to improve the compatibility and integration efficiency between devices, as well as the information transmission efficiency of short messages. Summary of the Invention

[0007] The technical problem to be solved by the present invention is to provide an IOT data processing method, a computer device and a medium based on defining template variables, which can parse and process the data of Internet of Things devices of various different types of protocols by freely defining and constructing data templates.

[0008] To solve the above technical problem, the present invention provides an IOT data processing method based on defining template variables, including: obtaining a message packet sent by a target device; judging whether the target device is associated with a preset protocol template according to the message packet, where the protocol template is used to define the mapping relationship between a template, a device, a tag number, a driver, a driver configuration, a collection rule of the tag number and a collection rule configuration of the tag number; when the judgment is yes, executing the message packet according to the protocol template; when the judgment is no, updating the protocol template according to the message packet, and executing the message packet according to the new protocol template.

[0009] As an improvement of the above solution, the step of updating the protocol template according to the message packet includes: converting the message packet into configurable values and collection rules to form a protocol template for driving the message packet.

[0010] As an improvement to the above solution, the protocol template includes a template table, a tag number table, a driver table, a device table, a template association table, a tag number configuration table, a driver configuration table, a device tag number configuration table, and a device driver configuration table; the template table is used to define the basic information of the template, the tag number table is used to define the basic information of the tag number and the mapping relationship between the tag number and the template, the tag number configuration table is used to define the mapping relationship between the driver and the acquisition rule of the tag number, the driver table is used to define the main basic information of the driver, the driver configuration table is used to define the sub-basic information of the driver, the device table is used to define the basic information of the device and the mapping relationship between the device and the driver, the template association table is used to define the mapping relationship between the template and the device, the device tag number configuration table is used to define the mapping relationship between the device, the driver, and the acquisition rule configuration of the tag number, and the device driver configuration table is used to define the driver configuration information and the mapping relationship between the device and the driver configuration.

[0011] As an improvement to the above solution, the tag number table includes a tag number ID field, a name field, a number code field, a data type field, a read / write flag field, a scale factor field, a data precision field, a unit field, a base value field, a description remarks field, and a template ID field.

[0012] As an improvement to the above solution, the step of updating the protocol template according to the message packet includes: reading the message packet and dividing the message packet into different data fields, where the data fields include a device name field, a keyword field, and an attribute field; constructing the basic information of the template and writing the basic information of the template into the template table; constructing the basic information of the tag number according to the attribute field and writing the basic information of the tag number and the mapping relationship between the tag number and the template into the tag number table; constructing the main basic information of the driver and writing the main basic information of the driver into the driver table; constructing the basic information of the device according to the device name field and writing the basic information of the device and the mapping relationship between the device and the driver into the device table; constructing the acquisition rule of the tag number and writing the mapping relationship between the driver and the acquisition rule of the tag number into the tag number configuration table; constructing the acquisition rule configuration of the tag number according to the keyword field, the attribute field, and the position feature of the attribute field in the message packet and writing the mapping relationship between the device, the driver, and the acquisition rule configuration of the tag number into the device tag number configuration table; writing the mapping relationship between the template and the device into the template association table; constructing the driver configuration information and writing the main basic information of the driver into the driver configuration table; constructing the driver configuration information and writing the driver configuration information and the mapping relationship between the device and the driver configuration into the device driver configuration table.

[0013] As an improvement of the above solution, there is a one-to-many relationship between the template table and the item number table, and a one-to-many relationship between the item number table and the device item number configuration table; there is a one-to-many relationship between the template table and the template association table, and a many-to-one relationship between the template association table and the device table; there is a one-to-many relationship between the device table and the device item number configuration table, a one-to-many relationship between the device table and the device driver configuration table, and a many-to-many relationship between the device table and the driver table; there is a one-to-many relationship between the driver table and the device item number configuration table; there is a one-to-many relationship between the driver table and the driver configuration table, and a one-to-many relationship between the driver configuration table and the device driver configuration table; there is a one-to-many relationship between the driver table and the item number configuration table, and a one-to-many relationship between the item number configuration table and the device item number configuration table.

[0014] Correspondingly, the present invention also provides a computer device, including a memory and a processor, the memory stores a computer program, and is characterized in that when the processor executes the computer program, the steps of the above IOT data processing method based on defining template variables are implemented.

[0015] Correspondingly, the present invention also provides a computer-readable storage medium, on which a computer program is stored, and is characterized in that when the computer program is executed by a processor, the steps of the above IOT data processing method based on defining template variables are implemented.

[0016] Implementing the present invention has the following beneficial effects:

[0017] The IOT data processing method based on defining template variables in the present invention quantifies different device protocols, and can parse and process the data of Internet of Things devices of various different types of protocols by freely defining and constructing data templates. Specifically:

[0018] In the present invention, item numbers are introduced, and associations between templates and item numbers, between devices and drivers, and between item numbers and drivers are constructed; also, through templated configuration, collection rule configuration of item numbers, more flexible device driver configuration, basic configuration file management, and targeted device association, the configuration efficiency is greatly improved, the effective construction of protocol templates is realized, and a perfect strategy is provided for the automatic execution of message packets.

[0019] At the same time, the present invention effectively reduces the need for secondary development, makes device access more efficient and flexible; reduces the human and time costs of enterprises in device integration and management, enables enterprises to respond to market demands faster, and improves operation efficiency; also improves the efficiency and flexibility of device access, reduces technical obstacles caused by protocol incompatibility, and contributes to the continuous innovation and development of technology. Description of the Drawings

[0020] Figure 1 It is a flowchart of an embodiment of the IOT data processing method based on defining template variables according to the present invention;

[0021] Figure 2 It is a schematic diagram of the association between tables in the present invention;

[0022] Figure 3 It is a flowchart of an embodiment of updating the protocol template according to the message packet in the present invention. Detailed implementation manners

[0023] To make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings.

[0024] Refer to Figure 1 , Figure 1 which shows a flowchart of an embodiment of the IOT data processing method based on defining template variables according to the present invention, and includes:

[0025] S101, obtaining a message packet sent by a target device;

[0026] S102, judging whether the target device is associated with a preset protocol template according to the message packet;

[0027] The protocol template is used to define the mapping relationship between the template, device, tag number, driver, driver configuration, acquisition rule of the tag number and acquisition rule configuration of the tag number;

[0028] The following will respectively elaborate on the template, device, tag number and driver in the present invention:

[0029] I. Device

[0030] A device is a broad concept. Mobile phones, computers, servers, gateways, hardware devices, and even a certain software program that can be connected to the Internet of Things platform can all be collectively referred to as devices.

[0031] II. Tag number

[0032] In the Internet of Things platform, the tag number is used to define certain attributes of the device. A tag number can define the basic parameters required for a certain attribute of the device. For example: a certain device has attributes such as temperature, pressure, direction, speed, etc., and these are collectively referred to as tag numbers.

[0033] III. Template

[0034] A template is a set of tag numbers. When a template is inherited by a certain device, the device also has all the tag numbers under this template at the same time. A template can be inherited by multiple devices, and a device can inherit multiple templates at the same time.

[0035] IV. Driver

[0036] In the Internet of Things platform, the so-called driver mainly means actively acquiring or receiving device data and controlling the device (provided that the device supports being controlled by a program). It is actually a set of program logics. The present invention calls the set of program logics for actively acquiring (passively receiving) device data and controlling different types of devices a driver, and classifies this set of program logics into different drivers according to different types of devices.

[0037] As Figure 2 shown, the protocol templates in the present invention include a template table (template), a tag table (signal), a driver table (driver), a device table (device), a template association table (template_ralation), a tag configuration table (signal_config), a driver configuration table (driver_config), a device tag configuration table (device_signal_config), and a device driver configuration table (device_driver_config).

[0038] Among them:

[0039] The template table is used to define the basic template information;

[0040] The tag table is used to define the basic tag information and the mapping relationship between the tag and the template;

[0041] The tag configuration table is used to define the mapping relationship between the driver and the acquisition rules of the tag;

[0042] The driver table is used to define the main basic information of the driver;

[0043] The driver configuration table is used to define the sub-basic information of the driver;

[0044] The device table is used to define the basic device information and the mapping relationship between the device and the driver;

[0045] The template association table is used to define the mapping relationship between the template and the device;

[0046] The device tag configuration table is used to define the mapping relationship between the device, the driver, and the acquisition rule configuration of the tag;

[0047] The device driver configuration table is used to define the driver configuration information and the mapping relationship between the device and the driver configuration.

[0048] It should be noted that the collection rule can be represented as "collect_rule_key", and the collection rule configuration can be represented as "collect_rule_value". For example, for a certain driver, it has four collection rules, namely: collection start bit, collection end bit, type, and keyword, but the collection rules do not have specific values. When it is necessary to refine and configure a bit number, it is necessary to configure the values of these four collection rules (i.e., the collection rule configuration):

[0049] For example, for bit number 1: collection start bit (value: 0), collection end bit (value: 4), type (value: int), keyword (value: 66);

[0050] Another example, for bit number 2: collection start bit (value: 4), collection end bit (value: 8), type (value: doube), keyword (value: 65).

[0051] In the prior art, usually only the simple association between the configuration file and the device is considered, without refining the association between the bit number and the driver level. Different from the prior art, in the present invention, the bit number is introduced, and the association between the template and the bit number, the association between the device and the driver, and the association between the bit number and the driver are constructed.

[0052] As Figure 2 shown, in the present invention, there is a one-to-many relationship between the template table and the bit number table, and a one-to-many relationship between the bit number table and the device bit number configuration table; there is a one-to-many relationship between the template table and the template association table, and a many-to-one relationship between the template association table and the device table; there is a one-to-many relationship between the device table and the device bit number configuration table, a one-to-many relationship between the device table and the device driver configuration table, and a many-to-many relationship between the device table and the driver table; there is a one-to-many relationship between the driver table and the device bit number configuration table; there is a one-to-many relationship between the driver table and the driver configuration table, and a one-to-many relationship between the driver configuration table and the device driver configuration table; there is a one-to-many relationship between the driver table and the bit number configuration table, and a one-to-many relationship between the bit number configuration table and the device bit number configuration table.

[0053] Therefore, through template-based configuration, collection rule configuration of bit numbers, more flexible device driver configuration, basic configuration file management, and targeted device association, the present invention greatly improves the configuration efficiency, realizes the effective construction of the protocol template, and provides a perfect strategy for the automatic execution of message packets.

[0054] Furthermore, the tag table in the present invention includes a tag ID field, a name field, a number code field (for identification and classification at the business level), a data type field (for defining the data type stored by the tag), a read / write flag field (for distinguishing between data collection and control devices), a scale factor field (for data conversion), a data precision field (for controlling the precision of numerical values), a unit field (the measurement unit of the data), a base value field (the reference value of the data), a description and remarks field, and a template ID field; through the design of each field in the tag table, the accuracy of data collection and processing can be guaranteed to a limited extent.

[0055] Therefore, the present invention provides a more complete and practical solution in the industrial automation scenario, especially with good consideration in aspects such as tag management, data collection, and driver configuration.

[0056] S103, when the judgment is yes, execute the message packet according to the protocol template.

[0057] When the target device is associated with a preset protocol template, it means that the template definition has been performed on the target device, and the message packet can be executed according to the defined template.

[0058] S104, when the judgment is no, update the protocol template according to the message packet and execute the message packet according to the new protocol template.

[0059] When the target device is not associated with a preset protocol template, it means that the template definition has not been performed on the target device, and a corresponding template needs to be created according to the message packet to execute the message packet.

[0060] It should be noted that when updating the protocol template according to the message packet, the message packet can be converted into configurable numerical values and collection rules according to the table in the protocol template to form a new protocol template for driving the message packet, thereby simplifying the protocol docking process.

[0061] Therefore, the present invention can report the message packet to the platform in the form of a Message Queue (MQ), thereby realizing dynamic update of the configuration.

[0062] Furthermore, as Figure 3 shown, the method for updating the protocol template according to the message packet includes:

[0063] S201, read the message packet and divide the message packet into different data fields.

[0064] S202, the data fields include a device name field, a keyword field, and an attribute field.

[0065] S203, construct the template basic information and write the template basic information into the template table.

[0066] S204. Construct the basic tag information according to the attribute field, and write the basic tag information and the mapping relationship between the tag and the template into the tag table;

[0067] S205. Construct the main basic information of the driver, and write the main basic information of the driver into the driver table;

[0068] The present invention can define different protocol types through the driver table, that is, each driver represents a communication protocol (such as Modbus, OPC, etc.), so as to realize the abstract management of the protocol.

[0069] S206. Construct the device basic information according to the device name field, and write the device basic information and the mapping relationship between the device and the driver into the device table;

[0070] S207. Construct the acquisition rule of the tag, and write the mapping relationship between the driver and the acquisition rule of the tag into the tag configuration table;

[0071] S208. Construct the acquisition rule configuration of the tag according to the keyword field, the attribute field and the position characteristics of the attribute field in the message packet, and write the mapping relationship between the device, the driver and the acquisition rule configuration of the tag into the device-tag configuration table;

[0072] In the present invention, the acquisition rule template of each protocol is defined through the tag configuration table. The acquisition rules abstract the data acquisition rules in the protocol, and the special processing rules of different protocols can be realized through configuration parameters, so as to realize the quantification of the rules.

[0073] S209. Write the mapping relationship between the template and the device into the template association table;

[0074] S210. Construct the driver configuration information, and write the main basic information of the driver into the driver configuration table;

[0075] In the present invention, the configuration parameters of the driver are standardized and defined through the driver configuration table.

[0076] S211. Construct the driver configuration information, and write the driver configuration information and the mapping relationship between the device and the driver configuration into the device-driver configuration table.

[0077] The present invention realizes the protocol parameter configuration of specific devices through the device-driver configuration table, combines with the device-tag configuration table to realize the acquisition rule configuration of specific tags, and also stores the actual acquisition rule values through collect_rule_value, so as to realize the instance configuration.

[0078] The following describes in detail the method of "updating the protocol template according to the message packet" in the present invention with specific embodiments:

[0079] For example, the data structure of message packet A is: device name

[22] + keyword [1] + altitude [4] + speed [8] + liquid level [8] + direction [4] + lock [1] + longitude and latitude

[21] , where:

[0080] The device name contains 22 bytes: 4C 69 73 74 65 6E 69 6E 67 56 69 72 74 75 61 6C44 65 76 69 63 65;

[0081] The keyword contains 1 byte: 62;

[0082] The altitude contains 4 bytes: 44 C3 E7 5C;

[0083] The speed contains 8 bytes: 40 46 D5 C2 8F 5C 28 F6;

[0084] The liquid level contains 8 bytes: 00 00 00 00 00 00 00 0C;

[0085] The direction contains 4 bytes: 00 00 00 2D;

[0086] The lock contains 1 byte: 01;

[0087] The longitude and latitude contains 21 bytes: 31 33 31 2E 32 33 31 34 35 36 2C 30 32 31 2E 35 3638 32 31 31;

[0088] Correspondingly, according to the content of the message packet, a template named "simulated TU data template", a driver named "simulated Tcp / Udp driver", and a device named "ListeningVirtualDevice" can be constructed;

[0089] Tag numbers for six attributes including altitude, speed, liquid level, direction, lock, and longitude and latitude can be constructed. Among them, the basic information of the tag number for "altitude" is shown in Table 1 below:

[0090] Table 1

[0091] Designation Altitude Template to which it belongs Analog TU data template Scale factor 1 Data accuracy 3 Unit Data type Floating point number Base value 0 Processed value Y = 1X + 0, rounded to 3 decimal places Read / write flag Read-only

[0092] A collection rule configuration for the tag number "altitude" can be constructed. The specific collection rule configuration is shown in Table 2 below:

[0093] Table 2

[0094] Starting byte 23 Ending byte Type float Keyword 62

[0095] It should be noted that the starting byte represents the starting byte position for reading; the ending byte represents the ending byte position for reading. For non-variable-length attributes, the configuration can be ignored. In this embodiment, the starting byte position of the poster is 23, which is 4 standard bytes, so the ending byte configuration can be ignored; the type represents the true data type of the data; the keyword represents the business logic.

[0096] In summary, the present invention can summarize the above process into four parts: data acquisition, template construction, driver conversion, and execution processing. Among them, the data acquisition part mainly realizes the acquisition of device basic information (device ID, name, number, etc.) and tag basic information (variable ID, value, original value, etc.); the template construction part mainly defines template basic information (including name, number code, data type, etc.) according to the template table, and establishes a mapping relationship between the device and the corresponding template through the template association table; the driver conversion part mainly realizes the conversion of device driver configuration into standard configuration items (in the form of configuration key-value), and converts the acquisition rules of tags into standard acquisition rules (in the form of acquisition rule key-value), and uniformly manages the configuration parameters of different types of drivers through the driver configuration table; the execution processing part mainly performs device communication according to the driver configuration, performs data acquisition according to the acquisition rules, realizes the one-to-one correspondence between the acquisition rules and variables through the map mechanism, executes data parsing, and completes the actual processing logic.

[0097] As can be seen from the above, the IOT data processing method based on defining template variables in the present invention quantifies different device protocols, can parse and process the data of Internet of Things devices of various different types of protocols by freely defining and constructing data templates, thereby effectively reducing the need for secondary development, making device access more efficient and flexible; at the same time, it reduces the human and time costs of enterprises in device integration and management, enables enterprises to respond to market demands faster, and improves operational efficiency; it also improves the efficiency and flexibility of device access, reduces technical barriers caused by protocol incompatibility, and contributes to the continuous innovation and development of technology.

[0098] Correspondingly, the present invention also discloses a computer device, including a memory and a processor. The memory stores a computer program. Among them, when the processor executes the computer program, it implements the steps of the above IOT data processing method based on defining template variables.

[0099] At the same time, the present invention also discloses a computer-readable storage medium, on which a computer program is stored. Among them, when the computer program is executed by the processor, it implements the steps of the above IOT data processing method based on defining template variables.

[0100] The above is the preferred embodiment of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present invention, several improvements and refinements can be made, and these improvements and refinements are also regarded as the protection scope of the present invention.

Claims

1. An IOT data processing method based on defining template variables, characterized in that: include: Get the message sent by the target device; Determining whether the target device is associated with a preset protocol template according to the message, wherein the protocol template is used to define a mapping relationship between a template, a device, a bit number, a driver, a driver configuration, a bit number collection rule, and a bit number collection rule configuration; When the judgment is yes, executing the message according to the protocol template; When the judgment is no, the protocol template is updated according to the message message, and the message message is executed according to the new protocol template.

2. The IOT data processing method based on defining template variables as claimed in claim 1, characterized in that: The step of updating the protocol template according to the message message includes: converting the message message into configurable values ​​and collection rules to form a protocol template that drives the message message.

3. The IOT data processing method based on defining template variables as claimed in claim 1, characterized in that: The protocol template includes a template table, a bit number table, a driver table, a device table, a template association table, a bit number configuration table, a driver configuration table, a device bit number configuration table and a device driver configuration table; The template table is used to define the basic information of the template, the bit number table is used to define the basic information of the bit number and the mapping relationship between the bit number and the template, the bit number configuration table is used to define the mapping relationship between the driver and the bit number acquisition rule, the driver table is used to define the main basic information of the driver, the driver configuration table is used to define the sub-basic information of the driver, the device table is used to define the device basic information and the mapping relationship between the device and the driver, the template association table is used to define the mapping relationship between the template and the device, the device bit number configuration table is used to define the mapping relationship between the device, the driver and the bit number acquisition rule configuration, and the device driver configuration table is used to define the driver configuration information and the mapping relationship between the device and the driver configuration.

4. The IOT data processing method based on defining template variables as claimed in claim 3, characterized in that: The bit number table includes a bit number ID field, a name field, a number code field, a data type field, a read-write tag field, a scale factor field, a data precision field, a unit field, a basic value field, a description note field and a template ID field.

5. The IOT data processing method based on defining template variables as claimed in claim 3, characterized in that: The step of updating the protocol template according to the message includes: Read the message message and divide the message message into different data fields, wherein the data fields include a device name field, a key field and an attribute field; Constructing basic template information and writing the basic template information into the template table; Constructing basic information of the bit number according to the attribute field, and writing the basic information of the bit number and the mapping relationship between the bit number and the template into the bit number table; Constructing the main basic information of the driver, and writing the main basic information of the driver into the driver table; Construct basic device information according to the device name field, and write the basic device information and the mapping relationship between the device and the driver into the device table; Construct the bit number collection rules, and write the mapping relationship between the drive and the bit number collection rules into the bit number configuration table; Constructing a bit number collection rule configuration according to the key field, the attribute field and the position characteristics of the attribute field in the message, and writing the mapping relationship between the device, the driver and the bit number collection rule configuration into the device bit number configuration table; Write the mapping relationship between the template and the device into the template association table; Constructing driver configuration information, and writing the main basic information of the driver into a driver configuration table; The driver configuration information is constructed, and the driver configuration information and the mapping relationship between the device and the driver configuration are written into the device driver configuration table.

6. The IOT data processing method based on defining template variables as claimed in claim 2, characterized in that: There is a one-to-many relationship between the template table and the bit number table, and there is a one-to-many relationship between the bit number table and the device bit number configuration table; There is a one-to-many relationship between the template table and the template association table, and there is a many-to-one relationship between the template association table and the device table; There is a one-to-many relationship between the device table and the device bit number configuration table, a one-to-many relationship between the device table and the device driver configuration table, and a many-to-many relationship between the device table and the driver table; There is a one-to-many relationship between the driver table and the device bit number configuration table; There is a one-to-many relationship between the driver table and the driver configuration table, and there is a one-to-many relationship between the driver configuration table and the device driver configuration table; There is a one-to-many relationship between the driver table and the bit number configuration table, and there is a one-to-many relationship between the bit number configuration table and the device bit number configuration table.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the IOT data processing method based on defining template variables described in any one of claims 1 to 6 are implemented.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the IOT data processing method based on defining template variables described in any one of claims 1 to 6 are implemented.

Images