Data transmission method, device, equipment, medium and product based on internet of things

Abstract

The application discloses a data transmission method and device based on an Internet of Things, equipment, a medium and a product. An edge device converts collected monitoring data according to a preset monitoring index identification format to generate a monitoring index. Then, according to the monitoring index, target monitoring data is generated according to a preset data protocol. Finally, the converted target monitoring data is reported to an Internet of Things platform. In the embodiment of the application, the monitoring data to be reported is converted into binary data stream in a unified data format and transmission format through a unified data protocol and index, so that the monitoring data of the edge terminal is reported in a unified standardized package. After receiving the target monitoring data, the subsequent Internet of Things platform only needs to analyze the data through a data protocol authenticated by both parties to obtain the original monitoring data, thereby effectively reducing the management difficulty of the Internet of Things platform for the monitoring data reported by the edge terminal.

Description

Technical Field

[0001] This invention relates to the field of edge computing technology for the Internet of Things (IoT), and more particularly to a data transmission method, apparatus, device, medium, and product based on the Internet of Things. Background Technology

[0002] With the development of edge computing in the Internet of Things (IoT), the types of edge terminals under IoT platforms are increasing, and the various edge applications carried on these terminals are also rapidly growing. This presents greater challenges to the stable operation of edge terminals and applications. To monitor the operational status of edge terminals and applications in real time, IoT platforms need to quickly acquire operational monitoring data for all types of edge terminals and applications, and promptly issue warnings and make adjustments for any abnormal edge terminals or applications.

[0003] Currently, there is no unified standard for the monitoring data indicators collected by various edge terminals, and the formats for assembling monitoring data are also inconsistent. This makes it impossible for IoT platforms to parse the monitoring data reported by various edge terminals according to a unified protocol format, increasing the difficulty for IoT platforms to uniformly manage the monitoring data of edge terminals or edge applications. Summary of the Invention

[0004] To address the problems existing in the prior art, embodiments of the present invention provide a data transmission method, apparatus, device, medium, and product based on the Internet of Things (IoT). By encapsulating and reporting monitoring data from edge terminals through a unified data protocol and indicators, the management difficulty of monitoring data reported by edge terminals by the IoT platform can be effectively reduced.

[0005] In a first aspect, embodiments of the present invention provide a data transmission method based on the Internet of Things (IoT), applied to an edge terminal, comprising:

[0006] The collected monitoring data is converted according to the preset monitoring indicator identifier format to generate monitoring indicators;

[0007] Based on the monitoring indicators, target monitoring data is generated according to a preset data protocol;

[0008] The target monitoring data is sent to the Internet of Things platform.

[0009] As an improvement to the above solution, the monitoring indicators include monitoring indicator identifiers and their corresponding monitoring indicator values;

[0010] The process of converting the currently acquired monitoring data according to a preset monitoring indicator identifier format to generate monitoring indicators includes:

[0011] The monitoring data is converted using the aforementioned monitoring indicator identifier format to generate monitoring indicator identifiers.

[0012] The monitoring indicator identifiers are converted into data according to a preset monitoring indicator value format to generate corresponding monitoring indicator values.

[0013] As an improvement to the above scheme, the target monitoring data includes a data security identifier, a data storage identifier, a reporting time identifier, monitoring indicators, and a checksum.

[0014] As an improvement to the above scheme, the monitoring indicator identifier includes an indicator type identifier indicating the type of the monitoring object to which the monitoring data belongs, a monitoring resource identifier indicating the monitoring resource, a resource information type identifier indicating the type of resource information, and a type combination identifier indicating the combination of information types.

[0015] As an improvement to the above solution, the step of using the monitoring indicator identifier format to perform identifier conversion on the monitoring data and generate monitoring indicator identifiers includes:

[0016] Based on the monitoring object type to which the monitoring data belongs, generate the indicator type identifier according to the monitoring indicator identifier format, and fill the indicator type identifier at the end of the reporting time identifier;

[0017] Based on the monitoring resource, generate the monitoring resource identifier according to the monitoring indicator identifier format, and fill the monitoring resource identifier into the end of the indicator type identifier;

[0018] Based on the resource information type, generate the resource information type identifier according to the monitoring indicator identifier format, and fill the end of the monitoring resource identifier with the resource information type identifier;

[0019] Based on the information type combination, the information type combination is generated according to the monitoring indicator identifier format, and the information type combination identifier is filled into the end of the resource information type identifier.

[0020] As an improvement to the above solution, before converting the currently acquired monitoring data according to a preset monitoring indicator identifier format to generate monitoring indicators, the following steps are also included:

[0021] Based on the data verification rules and data encryption rules of the monitored data, a data security identifier is generated;

[0022] Generate a data storage identifier based on the byte order and version number of the monitored data;

[0023] A reporting time identifier is generated based on the reporting time of the monitoring data.

[0024] As an improvement to the above solution, the step of generating target monitoring data according to the monitoring indicators and a preset data protocol includes:

[0025] The data storage identifier, the reporting time identifier, and the monitoring indicator are used to generate a first byte sequence according to the data format defined by the data protocol;

[0026] The first byte sequence is verified and encrypted using the data security identifier to generate the second byte sequence;

[0027] The data security identifier is inserted into the preceding position of the second byte sequence to generate the target monitoring data.

[0028] As an improvement to the above scheme, the step of verifying and encrypting the first byte sequence using the data security identifier to generate the second byte sequence includes:

[0029] The first byte sequence is verified and confirmed using the data verification rules defined by the data security identifier.

[0030] When the verification is confirmed and passes, the verification code generated during the verification process is added to the end of the first byte sequence to obtain the verified first byte sequence.

[0031] The first byte sequence after verification is encrypted and confirmed using the data encryption rules defined by the data security identifier.

[0032] When encryption is confirmed, the byte sequence after successful verification is encrypted to obtain the second byte sequence.

[0033] As an improvement to the above solution, inserting the data security identifier into the preceding position of the second byte sequence to generate the target monitoring data includes:

[0034] Based on the data length of the data security identifier, determine the amount to shift the second byte sequence backward, and shift the second byte sequence backward according to the stated amount.

[0035] Starting from the beginning of the second byte sequence before the shift, the data security identifier is filled in before the second byte sequence after the shift to generate the target monitoring data.

[0036] As an improvement to the above scheme, the step of verifying and confirming the first byte sequence using the data verification rules defined by the data security identifier includes:

[0037] Based on the verification code in the data security identifier, determine whether to verify the first byte sequence;

[0038] When the verification code is the second character, it is confirmed that the first byte sequence will not be verified.

[0039] When the verification code is the first character, it is confirmed that the data verification rules defined by the data security identifier are used to verify the first byte sequence.

[0040] Secondly, embodiments of the present invention provide a data transmission method based on the Internet of Things (IoT), applied to an IoT platform, comprising:

[0041] Receive target monitoring data reported by edge devices; wherein the target monitoring data is generated according to a preset data protocol based on monitoring indicator identifiers, and the monitoring indicators are generated after converting the monitoring data collected by the edge devices according to a preset monitoring indicator identifier format;

[0042] The target monitoring data is parsed according to the data protocol to obtain the monitoring data.

[0043] Thirdly, embodiments of the present invention provide a data transmission device based on the Internet of Things (IoT), applied to an edge terminal, comprising:

[0044] The monitoring indicator generation module is used to convert the currently acquired monitoring data according to the preset monitoring indicator identifier format to generate monitoring indicators.

[0045] The target monitoring data generation module is used to generate target monitoring data according to the monitoring indicator identifier and a preset data protocol.

[0046] The monitoring data sending module is used to send the target monitoring data to the Internet of Things platform.

[0047] Fourthly, embodiments of the present invention provide a data transmission device based on the Internet of Things (IoT), applied to an IoT platform, comprising:

[0048] The monitoring data receiving module is used to receive target monitoring data reported by edge devices; wherein the target monitoring data is generated according to a preset data protocol based on monitoring indicator identifiers, and the monitoring indicators are generated after converting the monitoring data collected by the edge devices according to a preset monitoring indicator identifier format.

[0049] The monitoring data parsing module is used to parse the target monitoring data according to the data protocol to obtain the monitoring data.

[0050] Fifthly, embodiments of the present invention provide an Internet of Things (IoT)-based data transmission device, comprising: a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor executes the computer program to implement an IoT-based data transmission method as described in any one of the first aspects or an IoT-based data transmission method as described in the second aspect.

[0051] In a sixth aspect, embodiments of the present invention provide a computer-readable storage medium storing a computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the Internet of Things-based data transmission method as described in any one of the first aspects or the Internet of Things-based data transmission method as described in the second aspect.

[0052] In a seventh aspect, embodiments of the present invention provide a computer program product, including a computer program / instructions, which, when executed by a processor, implement the Internet of Things-based data transmission method as described in any one of the first aspects or the Internet of Things-based data transmission method as described in the second aspect.

[0053] Compared to existing technologies, this invention provides a data transmission method, apparatus, device, medium, and product based on the Internet of Things (IoT). In this invention, an edge terminal converts collected monitoring data according to a preset monitoring indicator identifier format to generate monitoring indicators. Then, based on the monitoring indicators, target monitoring data is generated according to a preset data protocol. Finally, the converted target monitoring data is reported to the IoT platform. This invention uses a unified data protocol and indicators to convert the monitoring data to be reported into a binary data stream with a unified data and transmission format. This enables the edge terminal's monitoring data to be reported in a unified and standardized manner. Subsequently, after receiving the target monitoring data, the IoT platform only needs to parse it through a data protocol authenticated by both parties to obtain the original monitoring data, thereby effectively reducing the management difficulty of the monitoring data reported by the edge terminal for the IoT platform. Attached Figure Description

[0054] To more clearly illustrate the technical solution of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0055] Figure 1 This is a flowchart of a data transmission method based on the Internet of Things provided in Embodiment 1 of the present invention;

[0056] Figure 2 This is a flowchart illustrating the generation of target monitoring data provided in an embodiment of the present invention;

[0057] Figure 3 This is a schematic diagram of the JSON format data content of the alarm information provided in the embodiments of the present invention;

[0058] Figure 4This is a flowchart of CRC-16 / CCITT-FALSE code calculation provided in an embodiment of the present invention;

[0059] Figure 5 This is a schematic diagram of the key Java code for CRC-16 / CCITT-FALSE code calculation provided in an embodiment of the present invention;

[0060] Figure 6 This is a flowchart of a data transmission method based on the Internet of Things provided in Embodiment 2 of the present invention;

[0061] Figure 7 This is a structural block diagram of a data transmission device based on the Internet of Things provided in Embodiment 3 of the present invention;

[0062] Figure 8 This is a structural block diagram of a data transmission device based on the Internet of Things provided in Embodiment 4 of the present invention;

[0063] Figure 9 This is a structural block diagram of a data transmission device based on the Internet of Things provided in Embodiment 5 of the present invention. Detailed Implementation

[0064] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0065] Example 1

[0066] Please see Figure 1 , Figure 1 This is a flowchart illustrating a data transmission method based on the Internet of Things (IoT) provided in an embodiment of the present invention. Applied to an edge terminal, it includes:

[0067] S11: Convert the collected monitoring data according to the preset monitoring indicator identifier format to generate monitoring indicators;

[0068] S12: Generate target monitoring data according to the monitoring indicators and a preset data protocol;

[0069] S13: Send the target monitoring data to the Internet of Things platform.

[0070] The target monitoring data is a binary data stream, including a data security identifier, a data storage identifier, a reporting time identifier, monitoring indicators, and a checksum.

[0071] In this embodiment of the invention, the data protocol is created based on a binary format. The edge terminal converts the collected monitoring data according to a preset monitoring indicator identifier format to generate monitoring indicators. Then, the monitoring indicators to be reported are assembled into target monitoring data in the form of a binary data stream through the data protocol and reported to the IoT platform. Thus, through a unified data protocol and indicators, the monitoring data to be reported is converted into a binary data stream with a unified data format and transmission format, realizing the unified and standardized encapsulation and reporting of monitoring data from the edge terminal. Subsequently, after receiving the target monitoring data, the IoT platform only needs to parse it through the data protocol authenticated by both parties to obtain the original monitoring data, thereby effectively reducing the management difficulty of the monitoring data reported by the edge terminal for the IoT platform.

[0072] For example, the data format defined by the data protocol is shown in the table below;

[0073]

[0074] It should be understood that the data storage identifier shown in the table above is also called the byte order and version number identifier. The data protocol defines that the target monitoring data reported to the IoT platform must be at least 14 bytes, with the data security identifier occupying 1 byte, the data storage identifier occupying 1 byte, the reporting time identifier occupying 8 bytes, the monitoring indicator identifier occupying 2 bytes, the checksum occupying 2 bytes, and the monitoring indicator value occupying N bytes, where N depends on the amount of monitoring data. The data protocol also defines the data structure of the target monitoring data reported to the IoT platform as: data security identifier + data storage identifier + reporting time identifier + monitoring indicator identifier + monitoring indicator value + checksum. All these identifiers are closely linked, forming a complete binary data stream.

[0075] Specifically, before converting the currently acquired monitoring data according to a preset monitoring indicator identifier format to generate monitoring indicators, the process also includes:

[0076] Based on the data verification rules and data encryption rules of the monitored data, a data security identifier is generated;

[0077] Generate a data storage identifier based on the byte order and version number of the monitored data;

[0078] A reporting time identifier is generated based on the reporting time of the monitoring data.

[0079] For example, such as Figure 2 As shown, when the edge segment reports monitoring data to the IoT platform, the data filling process according to the data protocol is as follows:

[0080] First, generate a 1-byte data security identifier corresponding to the data verification rules and data encryption rules required for the monitoring data, according to the preset data security identifier format; wherein, the data format defined by the data security identifier format is shown in the table below;

[0081]

[0082] It should be understood that the data security identifier specifies whether the data in this document is encrypted and the encryption method, as well as whether it is verified and the verification method. The data security identifier is filled into the first byte of the binary data stream defined by the data protocol. The highest bit (bit 7) of this byte indicates whether the other data following this byte (such as data storage identifier (and byte order and version number identifier), reporting time identifier, monitoring indicator identifier, and monitoring indicator value) is encrypted. When this bit is 0, it indicates no encryption; when it is 1, it indicates encryption. Bits 6-4 of this byte indicate the encryption algorithm, such as supporting RSA (an asymmetric encryption algorithm) and DES (Data Encryption Standard), etc., which are not specifically limited in this embodiment of the invention. When encryption is required, the edge terminal will encrypt the other data following this byte. After the encrypted data is transmitted to the IoT platform, the IoT platform will decrypt the received data and then parse the data according to the data format defined in the data protocol to obtain the original monitoring data. Bit 3 of this byte indicates whether other data following this byte needs to be checked for integrity. When this bit is 0, it means no check is needed, and when it is 1, it means check is needed. Bits 2-0 following this byte indicate the integrity check algorithm, such as CRC (Cyclic Redundancy Check) 8, CRC16, etc., which are not specifically limited in this embodiment of the invention. The check code generated based on the check algorithm is filled into the last two bytes of the binary data stream defined by the data protocol.

[0083] After generating the data security identifier, a 1-byte data storage identifier (i.e., byte order and version number identifier) ​​is generated according to a preset byte order and version number identifier format. The data format defined by the byte order and version number identifier format is shown in the table below.

[0084]

[0085] It should be understood that the data storage identifier (i.e., byte order and version number identifier) ​​specifies the byte order (big-endian or little-endian) and version number of this data; the data storage identifier (i.e., byte order and version number identifier) ​​is filled in the second byte of the binary data stream defined by the data protocol. The highest bit 7 of this byte identifies the byte order of the byte stream; when this bit is 0, it indicates little-endian byte order, and when it is 1, it indicates big-endian byte order. Bits 6-0 of this byte, after being parsed into integers, represent the version number of this message, i.e., the version number ranges from [0x1-0x3f].

[0086] After generating the data storage identifier (i.e., byte order and version number identifier), an 8-byte reporting time identifier is generated according to the preset reporting time identifier format; wherein, the data format defined by the reporting time identifier format is shown in the table below;

[0087]

[0088] It should be understood that the reporting time identifier indicates the reporting time of this data; the reporting time identifier is filled in bytes 3-10 of the binary data stream defined by the data protocol, occupying a total of 8 bytes. The reporting time is taken as the edge terminal time at the time this data is reported, and is a long integer in milliseconds. Specifically, it can be calculated based on the byte order in the data storage identifier (i.e., byte order and version number identifier). It should be noted that calculating the terminal time based on byte order is existing technology, and will not be explained in detail here.

[0089] Specifically, the monitoring indicators include monitoring indicator identifiers and their corresponding monitoring indicator values;

[0090] The process of converting the currently acquired monitoring data according to a preset monitoring indicator identifier format to generate monitoring indicators includes:

[0091] The monitoring data is converted using the aforementioned monitoring indicator identifier format to generate monitoring indicator identifiers.

[0092] The monitoring indicator identifiers are converted into data according to a preset monitoring indicator value format to generate corresponding monitoring indicator values.

[0093] Furthermore, the step of using the monitoring indicator identifier format to perform identifier conversion on the monitoring data and generate monitoring indicator identifiers includes:

[0094] Based on the monitoring object type to which the monitoring data belongs, generate the indicator type identifier according to the monitoring indicator identifier format, and fill the indicator type identifier at the end of the reporting time identifier;

[0095] Based on the monitoring resource, generate the monitoring resource identifier according to the monitoring indicator identifier format, and fill the monitoring resource identifier into the end of the indicator type identifier;

[0096] Based on the resource information type, generate the resource information type identifier according to the monitoring indicator identifier format, and fill the end of the monitoring resource identifier with the resource information type identifier;

[0097] Based on the information type combination, the information type combination is generated according to the monitoring indicator identifier format, and the information type combination identifier is filled into the end of the resource information type identifier.

[0098] For example, after generating the reporting time identifier, the monitoring data is converted into an identifier according to the monitoring indicator identifier format to generate the monitoring indicator identifier.

[0099] The monitoring indicator identifier, which is 2 bytes long, is used to describe the specific monitoring indicator reported in this data. The monitoring indicator identifier includes an indicator type identifier indicating the type of the monitoring object to which the monitoring data belongs, a monitoring resource identifier indicating the monitoring resource, a resource information type identifier indicating the type of resource information, and a type combination identifier indicating the combination of information types.

[0100] The data format defined by the monitoring indicator identifier format is shown in the table below;

[0101]

[0102] It should be understood that the monitoring indicator identifier is filled into bytes 11-12 of the binary data stream defined by the data protocol after the reporting time identifier. Specifically, bits 7-4 of the 11th byte represent the indicator class of the monitoring data, including terminal system indicators and application service indicators; bits 3-0 represent the monitoring resources, i.e., the monitoring resources under the terminal system indicators or application service indicators, including metadata, central processing unit (CPU), memory, disk, etc. Bits 7-4 of the 12th byte represent the resource information type, including basic information, operational information, alarm information, and combined information. When the resource information type is 1111-combined information, bits 3-0 indicate that the combined information consists of several resource information classes, and the terminal can freely combine resource information types. For example, the binary representation of bytes 11-12 as [00100010, 00010001] indicates that the monitoring indicator identifier of this data is basic information of CPU resources under the application service indicator.

[0103] The monitoring metrics for edge terminals are designed primarily based on metric categories, monitoring resources, and resource information types. Metric categories include two main types: terminal system metrics and application service metrics. Terminal system metrics refer to the operational monitoring data of the terminal system itself, while application service metrics refer to the monitoring data of applications running on the terminal. Different monitoring resources are set according to different metric categories. Resources under system metrics include metadata, CPU, memory, disk, network, and logged-in users, etc. Resources under application system metrics include metadata, memory, disk, network, and JVM (Java application-related metrics), etc. Monitoring resources are further divided into resource information types, including basic information, operational information, alarm information, and combined information. Combined information represents any combination of the first three types of information. The data content format of alarm information is JSON, and a specific example is shown below. Figure 3 As shown, it includes the terminal's custom alarm rule description for this resource, the alarm information, and the time when the alarm occurred.

[0104] The specific information type fields for monitored resources are designed as follows:

[0105] The monitoring resources under the terminal system indicators include:

[0106] Meta resources define the basic monitoring information of the terminal system. The specific resource information is shown in the table below.

[0107]

[0108] CPU resources define the basic, operational, and alarm monitoring information of the terminal system's CPU. Specific resource information is shown in the table below.

[0109]

[0110] The memory resource defines the monitoring information such as the operation and alarms of the terminal system's memory. The specific resource information is shown in the table below.

[0111]

[0112] Disk resources define the basic, operational, and alarm monitoring information of the terminal system disk (disk or partition). Specific resource information is shown in the table below.

[0113]

[0114] The network resource defines the monitoring information such as the operation and alarms of the terminal system network. The specific resource information is shown in the table below.

[0115]

[0116] User resources define the monitoring information such as operation and alarms of users in the terminal system. The specific resource information is shown in the table below.

[0117]

[0118] The monitoring resources under the application service metrics include:

[0119] Meta resources define the basic monitoring information for application services running on edge terminals. Their specific resource information is as follows:

[0120]

[0121] CPU resources define monitoring information such as CPU usage and alarms for application services running on the terminal. Specific resource information is as follows:

[0122]

[0123] Memory resources define monitoring information such as memory operation and alarms for application services running on the terminal. Specific resource information is as follows:

[0124]

[0125] Disk resources define monitoring information such as disk operation and alarms for application services running on the terminal. Specific resource information is as follows:

[0126]

[0127] The network resource defines monitoring information such as network operation and alarms of application services running on the terminal. Its resource information is as follows:

[0128]

[0129] JVM resources define monitoring information such as JVM runtime and alerts for application services (Java applications) running on the terminal. Specific resource information is as follows:

[0130]

[0131] After generating the monitoring indicator identifier, the monitoring indicator value corresponding to the current monitoring indicator identifier is generated according to the monitoring indicator value format.

[0132] In this invention, the monitoring indicator value represents the value of a specific monitoring indicator. Its content is assembled in key-value pairs, where the key is a specific field defined in the terminal monitoring indicator, and the value is the corresponding key's value. Multiple key-value pairs may exist. Both the key and value conform to the TLV protocol format specification. It should be noted that the TLV protocol is an existing communication protocol and will not be described in detail here. In this embodiment of the invention, the data protocol uses a binary format, and the terminal monitoring value is filled using the TLV format, which can reduce network resource overhead and improve data security.

[0133] The data format defined by the monitoring indicator value format is shown in the table below;

[0134]

[0135] It should be understood that the monitoring indicator value, following the monitoring indicator identifier, is filled starting from the 13th byte of the binary data stream defined by the data protocol, occupying multiple bytes. This part follows the TLV protocol format specification, is based on binary encoding, and includes three parts: data type (T), value length (L), and value (V), providing high flexibility. The data type (T) and value length (L) occupy at least 1 byte and at most 5 bytes. Bits 7-4 of the first byte of each TLV represent the data type (0001b-1000b). Bit 1111b is designed as a data separator identifier, used to separate different resource information type data when the resource information type is 1111-combined type, as shown in the data type comparison table below.

[0136]

[0137] The first byte of each TLV (bits 3-0) contains bits 0001b-0100b, which describe the length of the value in bytes. This indicates the number of bytes that follow to represent the length of the value. The minimum length is 0 bytes, and the maximum length is 4 bytes. The specific values ​​are shown in the table below. (Value Length Reference Table).

[0138]

[0139] The value (V) can be determined based on the data type (T) and the value length (L).

[0140] For example, the byte sequence of the monitoring indicator value key is [00100001b, 00000011b, 01100001b, 01100010b, 01100011b]. According to the format of the monitoring indicator value, the data type of this key is 0010b (string). The length of the value is 0001b, which means that the following 1 byte is used to calculate the length of the value, i.e., 0000011 (decimal 3). This means that the value occupies 3 bytes (01100001b, 01100010b, 01100011b), which is parsed into the string "abc". Similarly, if the byte order of a key-value pair is [00100001b, 00000011b, 01100001b, 01100010b, 01100011b, 00100001b, 00000001b, 01100001b], after parsing, the key is the string "abc", and the value corresponding to this key is the string "a".

[0141] When an edge terminal needs to report multiple information types for a resource, i.e., the resource information type in the data format table corresponding to the above monitoring indicator identifier format is 1111b-combined information, the first TLV value of the monitoring indicator value for each resource information type is the resource information type number. The data filled in afterward is the monitoring data corresponding to that resource information type. When the data for that resource information type is filled in, the data separator identifier (11110000b) is filled in, and the next resource information type number and its corresponding monitoring data are filled in. This process is repeated until the monitoring data for all information types of the reported resource is filled in. After the last resource information type data is filled in, the data separator identifier (11110000b) is no longer filled in.

[0142] Specifically, generating target monitoring data according to the monitoring indicators and a preset data protocol includes:

[0143] The data storage identifier, the reporting time identifier, and the monitoring indicator are used to generate a first byte sequence according to the data format defined by the data protocol;

[0144] The first byte sequence is verified and encrypted using the data security identifier to generate the second byte sequence;

[0145] The data security identifier is inserted into the preceding position of the second byte sequence to generate the target monitoring data.

[0146] Furthermore, the step of verifying and encrypting the first byte sequence using the data security identifier to generate the second byte sequence includes:

[0147] The first byte sequence is verified and confirmed using the data verification rules defined by the data security identifier.

[0148] When the verification is confirmed and passes, the verification code generated during the verification process is added to the end of the first byte sequence to obtain the verified first byte sequence.

[0149] The first byte sequence after verification is encrypted and confirmed using the data encryption rules defined by the data security identifier.

[0150] When encryption is confirmed, the byte sequence after successful verification is encrypted to obtain the second byte sequence.

[0151] Furthermore, the step of verifying and confirming the first byte sequence using the data verification rules defined by the data security identifier includes:

[0152] Based on the verification code in the data security identifier, determine whether to verify the first byte sequence;

[0153] When the verification code is the second character, it is confirmed that the first byte sequence will not be verified.

[0154] When the verification code is the first character, it is confirmed that the data verification rules defined by the data security identifier are used to verify the first byte sequence.

[0155] Further, the step of inserting the data security identifier into the preceding position of the second byte sequence to generate the target monitoring data includes:

[0156] Based on the data length of the data security identifier, determine the amount to shift the second byte sequence backward, and shift the second byte sequence backward according to the stated amount.

[0157] Starting from the beginning of the second byte sequence before the shift, the data security identifier is filled in before the second byte sequence after the shift to generate the target monitoring data.

[0158] For example, after generating the monitoring indicator value, the value of bit 7 in the data security identifier is used to determine whether verification is required. If the value of this bit is 0, it means that no verification is required, and no verification code is generated. The last two bytes in the binary data stream are empty. If they are 1, it means that verification is required. Then, a 2-byte verification code is generated for the first byte sequence generated by the data storage identifier (byte order and version number identifier), the reporting time identifier, the monitoring indicator identifier, and the monitoring indicator identifier, according to the verification rules specified by the data security identifier, and the generated verification code is filled after the first byte sequence.

[0159] The checksum used is Cyclic Redundancy Check (CRC), one of the most commonly used error-checking codes in data communication. Its characteristic is that the lengths of the information field and the check field can be arbitrarily selected. Cyclic Redundancy Check (CRC) is a data transmission error detection function that performs polynomial calculations on the data and appends the result to the end of the frame to ensure the correctness and integrity of data transmission. There are several types of CRC, such as CRC-4 / ITU, CRC-8, and CRC-16 / CCITT-FALSE. The following uses CRC-16 / CCITT-FALSE as an example. The calculation parameters for the CRC are shown in the table below.

[0160]

[0161] The calculation parameters for the Cyclic Redundancy Check (CRC) code include the width, the initial value of the polynomial POLY (INIT), etc. The initial value of the CRC-16 / CCITT-FALSE register is 0xffff, with the high byte first and the low byte last. The values ​​of each parameter are shown in the table below.

[0162]

[0163] like Figure 4 The CRC-16 / CCITT-FALSE code calculation process shown includes the following steps:

[0164] Step a: At the beginning, the CRC bit register value is set to the initial CRC value (0xffff).

[0165] Step b: Read one 8-bit data from the binary stream sequentially, starting from the most significant bit.

[0166] Step c: Take the 8-bit data from step b and check whether each bit is equal to 1, starting from the most significant bit.

[0167] Step e: Determine if the highest bit of the CRC register value is 1.

[0168] Step d: Shift the CRC register value one bit to the left and fill the lower bits with 0.

[0169] Step e: If only one of the highest bits is 1 in step c or step d, then XOR the CRC register value with the polynomial POLY, and store the XORed value in the CRC register.

[0170] Step f: Repeat steps c through e until each bit of the 8-bit data has been processed.

[0171] Step g: Repeat steps b through f until all data processing is complete.

[0172] Step h: XOR the value in the CRC register with the result to obtain the final CRC value, and then convert the CRC value into a hexadecimal string. The Java code for some key calculations in the verification process is as follows: Figure 5 As shown.

[0173] After the verification is completed, the value of bit 3 in the data security identifier is used again to determine whether the first byte sequence with the added check code needs to be encrypted. When it is 0, no encryption is required; when it is 1, encryption is required, and the first byte sequence with the added check code is encrypted according to the encryption rules specified in the data security identifier.

[0174] Finally, after verification and encryption, the second byte sequence is shifted one byte to the right, and the data security identifier byte is filled into the beginning of the second byte sequence to obtain the final target monitoring data in binary data stream form. The generation process of the target monitoring data is as follows: Figure 2 As shown.

[0175] By encrypting and verifying the data to be uploaded, this invention can effectively ensure data security, integrity, and correctness.

[0176] Compared to existing technologies, this invention generates monitoring indicators for the monitoring data to be reported through a monitoring indicator format. This standardizes various monitoring data of edge terminals at the data level, defines the specific monitoring content under various monitoring resources, and facilitates edge terminals to collect data according to the specified fields. By generating target monitoring data in binary data streams with sequentially connected data security identifiers, data storage identifiers (i.e., byte order and version number identifiers), reporting time identifiers, monitoring indicator identifiers, monitoring indicator values, and checksums through a predefined data protocol, this invention unifies the way edge terminals fill monitoring data. This facilitates various edge terminals to assemble and transmit monitoring data to the IoT platform according to a unified protocol format, enabling the monitoring data to be parsed, stored, analyzed, and displayed on the IoT platform according to a unified data format. The collected monitoring data is standardized and unified at both the protocol and data levels, greatly reducing the complexity of the IoT platform in parsing various terminal monitoring data, thereby effectively reducing the management difficulty of the monitoring data reported by edge terminals on the IoT platform.

[0177] Secondly, the data protocol specifies the use of binary format, and the terminal monitoring value is filled with TLV format, which can reduce network resource overhead and improve data security. Through the data protocol, encryption and verification algorithms can be flexibly selected at the data protocol level to ensure the security, integrity and correctness of the data. Edge terminals no longer need to consider the security and integrity of data transmission.

[0178] Example 2

[0179] See Figure 6 , Figure 6 This invention provides a structural block diagram of a data transmission device based on the Internet of Things (IoT), and the IoT-based data transmission method, applied to an IoT platform, includes:

[0180] S21: Receive target monitoring data reported by the edge device; wherein the target monitoring data is generated according to a preset data protocol based on the monitoring indicator identifier, and the monitoring indicator is generated after converting the monitoring data collected by the edge device according to a preset monitoring indicator identifier format;

[0181] S22: Parse the target monitoring data according to the data protocol to obtain the monitoring data.

[0182] It should be noted that the generation and reporting process of target monitoring data in the data transmission method based on the Internet of Things described in the embodiments of the present invention is the same as the working process of the data transmission method based on the Internet of Things described in Embodiment 1, and the technical effects achieved are the same as those of the data transmission method based on the Internet of Things described in Embodiment 1, and will not be repeated here.

[0183] Example 3

[0184] See Figure 7 , Figure 7 This invention provides a structural block diagram of an IoT-based data transmission device, which is applied to an edge terminal and includes:

[0185] The monitoring indicator generation module 11 is used to convert the currently acquired monitoring data according to the preset monitoring indicator identifier format to generate monitoring indicators.

[0186] The target monitoring data generation module 12 is used to generate target monitoring data according to the monitoring indicator identifier and a preset data protocol.

[0187] The monitoring data sending module 13 is used to send the target monitoring data to the Internet of Things platform.

[0188] In one optional embodiment, the monitoring indicator includes a monitoring indicator identifier and its corresponding monitoring indicator value;

[0189] The monitoring indicator generation module includes:

[0190] The monitoring indicator identifier generation unit is used to perform identifier conversion on the monitoring data using the monitoring indicator identifier format to generate monitoring indicator identifiers.

[0191] The monitoring indicator value generation unit is used to convert the monitoring indicator identifier according to a preset monitoring indicator value format to generate the corresponding monitoring indicator value.

[0192] In one optional embodiment, the target monitoring data includes a data security identifier, a data storage identifier, a reporting time identifier, monitoring indicators, and a checksum.

[0193] In one optional embodiment, the monitoring indicator identifier includes an indicator type identifier indicating the type of the monitoring object to which the monitoring data belongs, a monitoring resource identifier indicating the monitoring resource, a resource information type identifier indicating the type of resource information, and a type combination identifier indicating the combination of information types.

[0194] In one optional embodiment, the monitoring indicator identifier generation unit includes:

[0195] The indicator type identifier generation subunit is used to generate the indicator type identifier according to the monitoring object type to which the monitoring data belongs, and according to the monitoring indicator identifier format, and fill the indicator type identifier into the end of the reporting time identifier;

[0196] A monitoring resource identifier generation subunit is used to generate a monitoring resource identifier according to the monitoring resource and the monitoring indicator identifier format, and to fill the monitoring resource identifier into the end of the indicator type identifier;

[0197] The resource information type identifier generation subunit is used to generate the resource information type identifier according to the resource information type and the monitoring indicator identifier format, and to fill the resource information type identifier into the end of the monitoring resource identifier;

[0198] The information type combination identifier generation subunit is used to generate the information type combination according to the monitoring indicator identifier format based on the information type combination, and to fill the information type combination identifier into the end of the resource information type identifier.

[0199] In an optional embodiment, the device further includes:

[0200] The data security identifier generation module is used to generate a data security identifier based on the data verification rules and data encryption rules of the monitored data;

[0201] The data storage identifier generation module is used to generate a data storage identifier based on the byte order and version number of the monitoring data;

[0202] The reporting time identifier generation module is used to generate a reporting time identifier based on the reporting time of the monitoring data.

[0203] In one optional embodiment, the target monitoring data generation module includes:

[0204] The first byte sequence generation unit is used to generate a first byte sequence from the data storage identifier, the reporting time identifier, and the monitoring indicator according to the data format defined by the data protocol;

[0205] The second byte sequence generation unit is used to verify and encrypt the first byte sequence using the data security identifier to generate the second byte sequence.

[0206] A data security identifier insertion unit is used to insert the data security identifier into the preceding position of the second byte sequence to generate the target monitoring data.

[0207] In one optional embodiment, the second byte sequence generation unit includes:

[0208] The verification and confirmation subunit is used to verify and confirm the first byte sequence according to the data verification rules defined by the data security identifier;

[0209] The check code generation subunit is used to add the check code generated during the verification process to the end of the first byte sequence when the verification is confirmed and passed, so as to obtain the first byte sequence after verification.

[0210] The encryption confirmation subunit is used to perform encryption confirmation on the verified first byte sequence according to the data encryption rules defined by the data security identifier;

[0211] The encryption subunit is used to encrypt the byte sequence after verification when encryption is confirmed, so as to obtain the second byte sequence.

[0212] In one optional embodiment, the data security identifier insertion unit includes:

[0213] The byte sequence shift subunit is used to determine the shift amount of the second byte sequence based on the data length of the data security identifier, and shift the second byte sequence according to the shift amount;

[0214] The data security identifier filling subunit is used to fill the data security identifier before the second byte sequence after the shift, starting from the beginning position of the second byte sequence before the shift, to generate the target monitoring data.

[0215] In one optional embodiment, the verification confirmation subunit is specifically used to confirm whether to verify the first byte sequence based on the verification code in the data security identifier; when the verification code is a second character, confirm that the first byte sequence is not verified; when the verification code is a first character, confirm that the first byte sequence is verified using the data verification rules defined by the data security identifier.

[0216] It should be noted that the working process of each module in the IoT-based data transmission device described in the embodiments of the present invention can refer to the working process of the IoT-based data transmission method described in Embodiment 1 above, and the technical effects achieved are the same as those of the IoT-based data transmission method described in Embodiment 1 above, and will not be repeated here.

[0217] Example 4

[0218] See Figure 8 , Figure 8 This invention provides a structural block diagram of a data transmission device based on the Internet of Things (IoT). The IoT-based data transmission device is applied to an IoT platform and includes:

[0219] The monitoring data receiving module 21 is used to receive target monitoring data reported by the edge device; wherein the target monitoring data is generated according to a preset data protocol based on the monitoring indicator identifier, and the monitoring indicator is generated after converting the monitoring data collected by the edge device according to a preset monitoring indicator identifier format.

[0220] The monitoring data parsing module 22 is used to parse the target monitoring data according to the data protocol to obtain the monitoring data.

[0221] It should be noted that the working process of each module in the IoT-based data transmission device described in the embodiments of the present invention can refer to the working process of the IoT-based data transmission method described in Embodiment 2 above, and the technical effects achieved are the same as those of the IoT-based data transmission method described in Embodiment 2 above, and will not be repeated here.

[0222] Example 5

[0223] See Figure 9 , Figure 9 This is a structural block diagram of a data transmission device based on the Internet of Things (IoT) provided in an embodiment of the present invention. The IoT-based data transmission device includes a processor 31, a memory 32, and a computer program stored in the memory 32 and executable on the processor 31. When the processor 31 executes the computer program, it implements the steps in the various IoT-based data transmission methods described in Embodiment 1 / Embodiment 2, such as steps S11-S13 or steps S21-S22.

[0224] For example, the computer program can be divided into one or more modules / units, which are stored in the memory 32 and executed by the processor 31 to complete the present invention. The one or more modules / units can be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the Internet of Things-based data transmission device.

[0225] The IoT-based data transmission device may include, but is not limited to, a processor 31 and a memory 32. Those skilled in the art will understand that the schematic diagram is merely an example of an IoT-based data transmission device and does not constitute a limitation on the IoT-based data transmission device. It may include more or fewer components than illustrated, or combine certain components, or different components. For example, the IoT-based data transmission device may also include input / output devices, network access devices, buses, etc.

[0226] The processor 31 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. The processor 31 is the control center of the IoT-based data transmission device, connecting all parts of the IoT-based data transmission device via various interfaces and lines.

[0227] The memory 32 can be used to store the computer programs and / or modules. The processor 31 implements various functions of the IoT-based data transmission device by running or executing the computer programs and / or modules stored in the memory 32 and calling the data stored in the memory 32. The memory 32 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory 32 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0228] Wherein, if the modules / units integrated by the IoT-based data transmission device are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by the processor 31, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.

[0229] It should be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, in the accompanying drawings of the device embodiments provided by this invention, the connection relationships between modules indicate that they have communication connections, which can be specifically implemented as one or more communication buses or signal lines. Those skilled in the art can understand and implement this without any creative effort.

[0230] The above description is a preferred embodiment of the present invention. It should be noted that, for those skilled in the art, many improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications are also considered to be within the scope of protection of the present invention.

Claims

1. A data transmission method based on the Internet of Things, characterized in that, Applied to edge terminals, including: The collected monitoring data is converted according to the preset monitoring indicator identifier format to generate monitoring indicators; Based on the monitoring indicators, target monitoring data is generated according to a preset data protocol; Send the target monitoring data to the Internet of Things platform; The target monitoring data includes a data security identifier, a data storage identifier, a reporting time identifier, monitoring indicators, and a verification code; the data security identifier is used to indicate the data verification rules and data encryption rules of the monitoring data. The monitoring indicators include monitoring indicator identifiers and their corresponding monitoring indicator values; the monitoring indicator identifiers include indicator type identifiers indicating the type of monitoring object to which the monitoring data belongs, monitoring resource identifiers indicating the monitoring resources, resource information type identifiers indicating the type of resource information, and type combination identifiers indicating the combination of information types; The step of generating target monitoring data according to the monitoring indicators and a preset data protocol includes: The data storage identifier, the reporting time identifier, and the monitoring indicator are used to generate a first byte sequence according to the data format defined by the data protocol; The first byte sequence is verified and encrypted using the data security identifier to generate the second byte sequence; The data security identifier is inserted into the preceding position of the second byte sequence to generate the target monitoring data.

2. The data transmission method based on the Internet of Things as described in claim 1, characterized in that, The acquired monitoring data is converted according to a preset monitoring indicator identifier format to generate monitoring indicators, including: The monitoring data is converted using the aforementioned monitoring indicator identifier format to generate monitoring indicator identifiers. The monitoring indicator identifiers are converted into data according to a preset monitoring indicator value format to generate corresponding monitoring indicator values.

3. The data transmission method based on the Internet of Things as described in claim 2, characterized in that, Using the aforementioned monitoring indicator identifier format, the monitoring data is identified and converted to generate monitoring indicator identifiers, including: Based on the monitoring object type to which the monitoring data belongs, generate the indicator type identifier according to the monitoring indicator identifier format, and fill the indicator type identifier at the end of the reporting time identifier; Based on the monitoring resource, generate the monitoring resource identifier according to the monitoring indicator identifier format, and fill the monitoring resource identifier into the end of the indicator type identifier; Based on the resource information type, generate the resource information type identifier according to the monitoring indicator identifier format, and fill the end of the monitoring resource identifier with the resource information type identifier; Based on the information type combination, the information type combination is generated according to the monitoring indicator identifier format, and the information type combination identifier is filled into the end of the resource information type identifier.

4. The data transmission method based on the Internet of Things as described in claim 1, characterized in that, Before converting the currently acquired monitoring data according to the preset monitoring indicator identifier format to generate monitoring indicators, the process also includes: Based on the data verification rules and data encryption rules of the monitored data, a data security identifier is generated; Generate a data storage identifier based on the byte order and version number of the monitored data; A reporting time identifier is generated based on the reporting time of the monitoring data.

5. The data transmission method based on the Internet of Things as described in claim 1, characterized in that, The step of verifying and encrypting the first byte sequence using the data security identifier to generate the second byte sequence includes: The first byte sequence is verified and confirmed using the data verification rules defined by the data security identifier. When the verification is confirmed and passes, the verification code generated during the verification process is added to the end of the first byte sequence to obtain the verified first byte sequence. The first byte sequence after verification is encrypted and confirmed using the data encryption rules defined by the data security identifier. When encryption is confirmed, the byte sequence after successful verification is encrypted to obtain the second byte sequence.

6. The data transmission method based on the Internet of Things as described in claim 1, characterized in that, The step of inserting the data security identifier into the preceding position of the second byte sequence to generate the target monitoring data includes: Based on the data length of the data security identifier, determine the amount to shift the second byte sequence backward, and shift the second byte sequence backward according to the stated amount. Starting from the beginning of the second byte sequence before the shift, the data security identifier is filled in before the second byte sequence after the shift to generate the target monitoring data.

7. The data transmission method based on the Internet of Things as described in claim 5, characterized in that, The verification and confirmation of the first byte sequence through the data verification rules defined by the data security identifier includes: Based on the verification code in the data security identifier, determine whether to verify the first byte sequence; When the verification code is the second character, it is confirmed that the first byte sequence will not be verified. When the verification code is the first character, it is confirmed that the data verification rules defined by the data security identifier are used to verify the first byte sequence.

8. A data transmission method based on the Internet of Things, characterized in that, Applications in IoT platforms, including: Receive target monitoring data reported by edge devices; wherein the target monitoring data is generated according to a preset data protocol based on monitoring indicator identifiers, and the monitoring indicators are generated after converting the monitoring data collected by the edge devices according to a preset monitoring indicator identifier format; The target monitoring data is parsed according to the data protocol to obtain the monitoring data; The target monitoring data includes a data security identifier, a data storage identifier, a reporting time identifier, monitoring indicators, and a verification code; the data security identifier is used to indicate the data verification rules and data encryption rules of the monitoring data. The monitoring indicators include monitoring indicator identifiers and their corresponding monitoring indicator values; the monitoring indicator identifiers include indicator type identifiers indicating the type of monitoring object to which the monitoring data belongs, monitoring resource identifiers indicating the monitoring resources, resource information type identifiers indicating the type of resource information, and type combination identifiers indicating the combination of information types; The process of generating the target monitoring data includes: The data storage identifier, the reporting time identifier, and the monitoring indicator are used to generate a first byte sequence according to the data format defined by the data protocol; The first byte sequence is verified and encrypted using the data security identifier to generate the second byte sequence; The data security identifier is inserted into the preceding position of the second byte sequence to generate the target monitoring data.

9. A data transmission device based on the Internet of Things, characterized in that, Applied to edge terminals, including: The monitoring indicator generation module is used to convert the currently acquired monitoring data according to the preset monitoring indicator identifier format to generate monitoring indicators. The target monitoring data generation module is used to generate target monitoring data according to the monitoring indicator identifier and a preset data protocol. A monitoring data sending module is used to send the target monitoring data to an Internet of Things (IoT) platform; The target monitoring data includes a data security identifier, a data storage identifier, a reporting time identifier, monitoring indicators, and a verification code; the data security identifier is used to indicate the data verification rules and data encryption rules of the monitoring data. The monitoring indicators include monitoring indicator identifiers and their corresponding monitoring indicator values; the monitoring indicator identifiers include indicator type identifiers indicating the type of monitoring object to which the monitoring data belongs, monitoring resource identifiers indicating the monitoring resources, resource information type identifiers indicating the type of resource information, and type combination identifiers indicating the combination of information types; The target monitoring data generation module includes: The first byte sequence generation unit is used to generate a first byte sequence from the data storage identifier, the reporting time identifier, and the monitoring indicator according to the data format defined by the data protocol; The second byte sequence generation unit is used to verify and encrypt the first byte sequence using the data security identifier to generate the second byte sequence. A data security identifier insertion unit is used to insert the data security identifier into the preceding position of the second byte sequence to generate the target monitoring data.

10. A data transmission device based on the Internet of Things, characterized in that, Applications in IoT platforms, including: The monitoring data receiving module is used to receive target monitoring data reported by the edge device; wherein, the target monitoring data is generated according to a preset data protocol based on the monitoring indicator identifier, and the monitoring indicator is generated after converting the monitoring data collected by the edge device according to a preset monitoring indicator identifier format; The monitoring data parsing module is used to parse the target monitoring data according to the data protocol to obtain the monitoring data; The target monitoring data includes a data security identifier, a data storage identifier, a reporting time identifier, monitoring indicators, and a verification code; the data security identifier is used to indicate the data verification rules and data encryption rules of the monitoring data. The monitoring indicators include monitoring indicator identifiers and their corresponding monitoring indicator values; the monitoring indicator identifiers include indicator type identifiers indicating the type of monitoring object to which the monitoring data belongs, monitoring resource identifiers indicating the monitoring resources, resource information type identifiers indicating the type of resource information, and type combination identifiers indicating the combination of information types; The process of generating the target monitoring data includes: The data storage identifier, the reporting time identifier, and the monitoring indicator are used to generate a first byte sequence according to the data format defined by the data protocol; The first byte sequence is verified and encrypted using the data security identifier to generate the second byte sequence; The data security identifier is inserted into the preceding position of the second byte sequence to generate the target monitoring data.

11. A data transmission device based on the Internet of Things, characterized in that, include: A processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor, when executing the computer program, implements the Internet of Things-based data transmission method as described in any one of claims 1 to 7 or the Internet of Things-based data transmission method as described in any one of claims 8.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the Internet of Things-based data transmission method as described in any one of claims 1 to 7 or the Internet of Things-based data transmission method as described in any one of claims 8.

13. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the Internet of Things-based data transmission method as described in any one of claims 1 to 7 or the Internet of Things-based data transmission method as described in any one of claims 8.

Images